[Bug 82711] New: After update to kernel soft lockup and incomplete boot
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Mon Aug 18 02:51:54 PDT 2014
https://bugzilla.kernel.org/show_bug.cgi?id=82711
Bug ID: 82711
Summary: After update to kernel soft lockup and incomplete boot
Product: Drivers
Version: 2.5
Kernel Version: 3.16.1-1-ARCH
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri at kernel-bugs.osdl.org
Reporter: mike.cloaked at gmail.com
Regression: No
Created attachment 147021
--> https://bugzilla.kernel.org/attachment.cgi?id=147021&action=edit
Systemd journal log after rebooting from crashed system
After update to the kernel 3.16.1-1-ARCH the Lenovo Y510p with hybrid
Intel/Nvidia graphics fails to boot though occasionally boot does complete and
when it did then partial logs were available from the systemd journal despite
having to pull the power to shutdown the system which corrupts the journal
files.
CPU soft lockup is one part of the log, and it seems that the graphics card
fails to initialise properly also.
Aug 18 10:10:14 lenovo2 kernel: nouveau E[ PGRAPH][0000:01:00.0] init failed,
-16
Aug 18 10:10:14 lenovo2 kernel: nouveau E[
PGRAPH][0000:01:00.0][0x0300e417][ffff880263bcfc00] engine failed, -16
Aug 18 10:10:14 lenovo2 kernel: nouveau E[
PGRAPH][0000:01:00.0][0x0000a097][ffff880261d45700] parent failed, -16
Aug 18 10:10:14 lenovo2 kernel: nouveau E[Xorg.bin[439]] 0xdddddddd:0xcccc0000
init failed with -16
Aug 18 10:10:14 lenovo2 kernel: nouveau E[Xorg.bin[439]] 0xffffffff:0xdddddddd
init failed with -16
Aug 18 10:10:14 lenovo2 kernel: nouveau E[Xorg.bin[439]] 0xffffffff:0xffffffff
init failed with -16
Graphics cards are:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor
Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M]
(rev a1)
I was not sure which components to select for this report so chose non Intel
DRI - if necessary that can be changed.
Either way when the bug hits during boot the VTs fill with log output but it is
not clear that the logs contain all of the diagnostic information but the
attached log file is all that I was able to capture.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list