Bug 694917 - [NV92] Failure to resume from suspend properly with proprietary nvidia kernel driver.
Summary: [NV92] Failure to resume from suspend properly with proprietary nvidia kernel...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-08 20:38 UTC by Matěj Cepl
Modified: 2018-04-11 11:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 694898
Environment:
Last Closed: 2011-04-16 19:24:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg with drm debug flag set (123.90 KB, text/plain)
2011-04-08 22:51 UTC, D.S. Ljungmark
no flags Details
/var/log/messages for the relevant reboot. (100.52 KB, text/x-log)
2011-04-08 22:51 UTC, D.S. Ljungmark
no flags Details
Xorg.log for that reboot. (65.90 KB, text/x-log)
2011-04-08 22:52 UTC, D.S. Ljungmark
no flags Details
xorg.0.log after suspend (84.85 KB, text/plain)
2011-04-08 23:14 UTC, D.S. Ljungmark
no flags Details
/var/log/messages post suspend (134.02 KB, text/plain)
2011-04-08 23:15 UTC, D.S. Ljungmark
no flags Details
dmesg after suspend (124.18 KB, text/plain)
2011-04-08 23:16 UTC, D.S. Ljungmark
no flags Details

Description Matěj Cepl 2011-04-08 20:38:33 UTC
This cloned bug is only about this part:
> Note that at this time for some reason it auto-resumed as soon as it shut off,
> but I'm not sure that's me touching keyboard/mouse or something else.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* new output of the dmesg command (with more information because of the kernel parameter), and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.


+++ This bug was initially created as a clone of Bug #694898 +++

Created attachment 490858 [details]
dmesg post hang

Filing this because "suspend" is the default in gnome-shell, and I once again got trapped into pressing it :

The kernel resumes properly, I get to the "enter password" dialogue and that works, but once the password has been entered, graphics fall apart, get overlaid and garbled and input stops working.

Mouse no longer functions, and the keyboard takes ~10 seconds to respond to num-lock presses before toggling the led.


Toggling to a terminal (ctrl alt f2) works after a while (also ~10 seconds) then lets me get a dmesg log and shut the system down somewhat cleanly.

I'm well aware that this is a tainted kernel, but I'm also of the opinion that if you want to provoke kernel bugs by making suspend default in gnome-shell as a policy, you should also work to remove these bugs. My solution would be to make suspend _not_ be default on tainted kernels, but since you're just getting told "try a broken driver" when asking on IRC......


[root@Waves ~]# uname -a
Linux Waves.darkmere 2.6.38.2-9.fc15.x86_64 #1 SMP Wed Mar 30 16:55:57 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

NVRM version: NVIDIA UNIX x86_64 Kernel Module  270.30  Fri Feb 25 14:34:55 PST 2011
GCC version:  gcc version 4.6.0 20110331 (Red Hat 4.6.0-2) (GCC) 

Tail of xorg.0.log.old


[ 29938.835] (II) NVIDIA(0): Setting mode
[ 29938.835] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select+1920+0,DFP-1:nvidia-auto-select+0+0"
[ 29938.906] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 29938.906] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 29938.907] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 29938.907] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 29938.907] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 29938.907] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 29938.907] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 29938.907] (II) NVIDIA(0):     Config Options in the README.
[ 43759.354] (II) NVIDIA(0): Setting mode
[ 43759.354] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select+1920+0,DFP-1:nvidia-auto-select+0+0"
[ 43759.438] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 43759.438] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 43759.438] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 43759.438] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 43759.438] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 43759.438] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 43759.438] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 43759.438] (II) NVIDIA(0):     Config Options in the README.
[ 43790.329] (II) AT Translated Set 2 keyboard: Close
[ 43790.329] (II) UnloadModule: "evdev"
[ 43790.329] (II) Unloading evdev
[ 43790.329] (II) Logitech USB Receiver: Close
[ 43790.329] (II) UnloadModule: "evdev"
[ 43790.329] (II) Unloading evdev
[ 43790.329] (II) Power Button: Close
[ 43790.329] (II) UnloadModule: "evdev"
[ 43790.329] (II) Unloading evdev
[ 43790.329] (II) Power Button: Close
[ 43790.329] (II) UnloadModule: "evdev"
[ 43790.329] (II) Unloading evdev

--- Additional comment from spider on 2011-04-08 16:23:41 EDT ---

Created attachment 490869 [details]
dmesg with nouveau

Retrying this without nvidia drivers but with nouveau drivers instead causes other (bad) behaviour.  dmesg attached.

Note that at this time for some reason it auto-resumed as soon as it shut off, but I'm not sure that's me touching keyboard/mouse or something else.

Comment 1 D.S. Ljungmark 2011-04-08 22:51:09 UTC
Created attachment 490877 [details]
dmesg with drm debug flag set

No xorg.conf in this setup.

Comment 2 D.S. Ljungmark 2011-04-08 22:51:48 UTC
Created attachment 490878 [details]
/var/log/messages for the relevant reboot.

Comment 3 D.S. Ljungmark 2011-04-08 22:52:18 UTC
Created attachment 490879 [details]
Xorg.log for that reboot.

Comment 4 D.S. Ljungmark 2011-04-08 23:14:48 UTC
Created attachment 490886 [details]
xorg.0.log after suspend

Can't seem to get the hang to happen again post suspend. But here are the log files.

Comment 5 D.S. Ljungmark 2011-04-08 23:15:24 UTC
Created attachment 490887 [details]
/var/log/messages post suspend

Comment 6 D.S. Ljungmark 2011-04-08 23:16:40 UTC
Created attachment 490888 [details]
dmesg after suspend

dmesg doesn't show much, too spammed.

Comment 7 Adam Jackson 2011-04-14 21:36:20 UTC
Bugs in the nvidia driver's suspend support are nvidia's problem, not ours.  We can only attempt to support the nouveau driver.

Comment 8 dfavro 2011-06-06 13:56:07 UTC
This might be being worked on upstream: https://bugzilla.gnome.org/show_bug.cgi?id=647355

It's a real pain if you're a laptop user as the nouveau driver doesn't have much in the way of power management.  Very catch-22: use nouveau and you lose 30-50% runtime; use NVidia and you can't wake from suspend.

Comment 9 dfavro 2011-06-15 03:22:42 UTC
And it's fixed in nVidia's 275.09.07.


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