Bug 388101 - nouveau triggers kernel oops on resume from hibernate
nouveau triggers kernel oops on resume from hibernate
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Dave Airlie
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-16 23:16 EST by Jack Spaar
Modified: 2008-01-15 14:27 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-15 14:27:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
crash syslog (26.18 KB, text/plain)
2007-11-16 23:16 EST, Jack Spaar
no flags Details
X server log (82.48 KB, application/octet-stream)
2007-11-16 23:18 EST, Jack Spaar
no flags Details
trivial xorg.conf using nouveau (569 bytes, text/plain)
2007-11-16 23:19 EST, Jack Spaar
no flags Details

  None (edit)
Description Jack Spaar 2007-11-16 23:16:57 EST
Description of problem:
When resuming from hibernation, kernel reports:
kernel BUG at lib/list_debug.c:67!

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install xorg-x11-drv-nouveau, and configure xorg.conf to use driver nouveau
2. From within an X11 session hibernate
3. Resume from hibernation
Actual results:
Console displays error kernel messages relating to nouveau -- see attachment

Expected results:

Additional info:
Comment 1 Jack Spaar 2007-11-16 23:16:57 EST
Created attachment 262091 [details]
crash syslog
Comment 2 Jack Spaar 2007-11-16 23:18:08 EST
Created attachment 262101 [details]
X server log
Comment 3 Jack Spaar 2007-11-16 23:19:00 EST
Created attachment 262111 [details]
trivial xorg.conf using nouveau
Comment 4 Jack Spaar 2008-01-15 14:27:36 EST
I won't have a chance to debug this further, if anyone else hits this they can
reopen it.

Note You need to log in before you can comment on or make changes to this bug.