https://bugzilla.kernel.org/show_bug.cgi?id=62541
Bug ID: 62541 Summary: Kernel oops/panic during system boot with systemd - "Unable to handle kernel NULL pointer dereference" Product: Drivers Version: 2.5 Kernel Version: 3.11 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: a.byszuk@elka.pw.edu.pl Regression: No
Created attachment 110251 --> https://bugzilla.kernel.org/attachment.cgi?id=110251&action=edit dmesg, lswh, .config outputs
Hello,
I have a bug (100 % repeatable) that prevents booting Linux when systemd is used as an init system. However, booting with traditional init works fine. I'm posting this bug to the DRI subsystem because I was (barely) able to capture to capture kernel message before the screen becomes blank. I can verify that this problem happens in all 3.11.x kernels and in Debian's 3.10 kernel. The hardware is Dell Vostro 3560 - Intel Ivy Bridge, hybrid graphics (Intel + Radeon), OCZ Vertex 4 SSD. My suspicion is that maybe the system bootup is too fast for the kernel; I was able to boot kernel once even with systemd, but that was when I turned on all the debugging messages which flooded console a bit.
Photo of captured BUG message: http://s23.postimg.org/qgk843rzv/vga1.png dmesg, lshw and .config outputs attached.
Kind regards, Adrian