Bug 86671 - [BISECTED]Freeze at boot since 3.16 with console garbage
Summary: [BISECTED]Freeze at boot since 3.16 with console garbage
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-21 16:54 UTC by Christian Casteyde
Modified: 2014-12-09 09:56 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.16
Subsystem:
Regression: No
Bisected commit-id:

Attachments
bisection result (1.55 KB, text/plain)
2014-10-21 16:55 UTC, Christian Casteyde 		Details
bisect log output (2.86 KB, text/plain)
2014-10-21 16:55 UTC, Christian Casteyde 		Details
dmesg output (39.82 KB, text/plain)
2014-10-21 16:56 UTC, Christian Casteyde 		Details
lspci -v output (8.55 KB, text/plain)
2014-10-21 16:56 UTC, Christian Casteyde 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Christian Casteyde 2014-10-21 16:54:29 UTC 
Kernel 3.16
Slackware 14.37 32 bits
GCC 4.8.2

Since kernel 3.16 my laptop doesn't doesn't boot anymore. Just after boot, the console is filled with strange colored and blinking console characters, and the boot process stops there.
This bug is still present in 3.17.1.

I bisected the bug and give lspci and dmesg output (see attachments).
Comment 1 Christian Casteyde 2014-10-21 16:55:21 UTC 
Created attachment 154431 [details]
bisection result
Comment 2 Christian Casteyde 2014-10-21 16:55:46 UTC 
Created attachment 154441 [details]
bisect log output
Comment 3 Christian Casteyde 2014-10-21 16:56:05 UTC 
Created attachment 154451 [details]
dmesg output
Comment 4 Christian Casteyde 2014-10-21 16:56:24 UTC 
Created attachment 154461 [details]
lspci -v output
Comment 5 Paulo Zanoni 2014-10-23 18:34:42 UTC 
Possible duplicate: https://bugs.freedesktop.org/show_bug.cgi?id=81140
Comment 6 Christian Casteyde 2014-12-09 09:56:29 UTC 
Seems to be fixed in 3.18.0, closing it.
Note You need to log in before you can comment on or make changes to this bug.