Bug 87275 - Kernel panic when starting gdm on machine with intel hd4000
Summary: Kernel panic when starting gdm on machine with intel hd4000
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 10.3
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-13 08:16 UTC by Bob
Modified: 2014-12-16 23:27 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Stack trace for kernel oops. (10.61 KB, text/plain)
2014-12-13 08:16 UTC, Bob
Details

Description Bob 2014-12-13 08:16:03 UTC
Created attachment 110804 [details]
Stack trace for kernel oops.

I have a working system with gnome 3.12 and mesa 10.3 and intel drivers with Xorg on linux.

At circa kernel version 3.16 the machine stopped booting into gdm. At startup there was a kernel panic with almost every kernel version.

I waited a while and checked the kernel config but didn't find anything major that had changed between the two kernel versions. This still happens with 3.17.6. The two configs can be seen from  https://bugs.gentoo.org/show_bug.cgi?id=526522

I have the stack trace as an attachment. I could not get a stack trace until I started playing around with USB serial port drivers and kexecing. Kexecing is overkill as I don't want the whole state of the machine and USB serial was useless. Then I found the efi-pstore module. 

EFI-pstore - the only good thing that begins with EFI-.

I will look in the code and I will probably find there is some config missing with a null pointer being dereferenced and that my config is horribly wrong because its a config that I have used for 5 difference machines since 2008 and hasn't been cleaned up since....

Faithfully

Timbo
Comment 1 Bob 2014-12-16 23:27:16 UTC
Fixed in kernel 3.18.1


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.