[Bug 88301] [PNV] Kernel 3.16 boot hang

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=88301

--- Comment #18 from mfld.fr at gmail.com ---
Hello, I restarted the bisect from the latest known tags on the master
branch, and checked this time the path taken by the bisect to avoid the
previous miss.

c9eaa44  bad   3.15-rc1
455c6fd  good  3.14

Here is the bisect path I followed:

Using Git bisect and check that it stays on the master branch:

cd6362b  good
d2b150d  good
5fb6b95  good  last

Here Git escaped from the master branch, so back to manual bisect:

79d2d21  bad
4162877  bad
75ff24f  bad
e9f37d3  bad   first

Commit e9f37d3 is just after 5fb6b95, and is:
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
the merge of branch drm-next into master.

Branch 'drm-next' based on cfbf8d4 (tag 3.14-rc4) and merged from c39b069.

Manual bisect on the 'drm-next' branch:

cfbf8d4  good
c39b069  bad
8fa6a9e  good
d9961b2  bad
bfe8b57  good
66e514c  bad   first
2844ea3  good  last

Commit 66e514c is just after 2844ea3 and is:
Merge tag 'drm-intel-next-2014-03-21' of
git://anongit.freedesktop.org/drm-intel into drm-next

Branch 'drm-intel-next-queued' based on 319e2e3 (tag 3.13-rc4) and merged
from 698b313.

Manual bisect on the 'drm-intel-next-queued' branch:

319e2e3  good
698b313  bad
a0bae57  good
6a68735  good
6c7fba0  bad
6d129be  good
46f297f  good
ff2652e  bad
d978ef1  bad   first
4c6baa5  good  last

Commit d978ef1 is just after 4c6baa5 and is:
drm/i915: Wrap the preallocated BIOS framebuffer
and preserve for KMS fbcon v12

Same result as before... so double checked again:

4c6baa5  now bad !!!

Looks like there is another condition that triggers the failure...
Let us assume it is the cold or warm reboot after building the kernel,
and that warm reboot gives a false good for previous tests.

So now always testing from power off:

46f297f  good
1ad292b  good  last
4c6baa5  bad   first

Commit 4c6baa5 is just after 1ad292b and is:
drm/i915: get_plane_config support for ILK+ v3

I think this time we have a good candidate.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.