Bug 205170
|
Description
Rodd Clarkson
2006-09-05 06:35:49 UTC
It turns out that what I thought was a updates-testing kernel, was actually just an 'updates' kernel, but it doesn't really change the nature of this bug report. Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Be also aware that Red Hat cannot support drivers which it doesn't provide, which includes nvidia binary-only driver from livna, so please report all information using only nv driver and make sure that neither service nvidia runs (service nvidia status), nor that there is present kernel module nvidia (i.e., lsmod | grep nvidia gives nothing). Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Sorry about the slow reply. I'll try to get this information to you as soon as possible. I'm no longer using FC5, so I'll have to test in FC6 and FC7. I haven't used the nv driver in FC6 for some time now, and suspend/resume isn't working in FC7 for me, but since I can't use the nvidia driver to test I can't tell you whether this is something to do with the nv driver, or whether suspend/resume is more generally borked. Don't worry about nvidia driver -- I would close you the bug as CANTFIX if you use it anyway. Okay, this is still borked in FC7t2. If I use the nv driver, FC7t2 does NOT resume after suspending. If I use the nvidia driver, FC7t2 does resume. I know you guys are not interested in the nvidia driver, but to be honest, it's hard to give the nv driver any serious testing if each time I shut my laptop lid, it suspends and then I have to force a reboot. I'll try to get you the information you require regarding this ASAP. Created attachment 149411 [details]
xorg.conf file
Created attachment 149412 [details]
Initial Xorg.0.log file before restarting and using 'nv' driver
Created attachment 149413 [details]
Initial Xorg.0.log.old file before restarting and using 'nv' driver
Created attachment 149414 [details]
Second Xorg.0.log file after restarting and using 'nv' driver.
This time when I tried to suspend, X crashed and threw me back to the log in
prompt.
Created attachment 149415 [details]
Second Xorg.0.log.old file after restarting and using 'nv' driver.
Created attachment 149416 [details]
Third Xorg.0.log file after restarting after failure to resume.
After a failure to resume I restarted in init 3 so that I didn't have X run.
Created attachment 149417 [details]
Third Xorg.0.log file after restarting after failure to resume.
Is this what you're after? Is the machine still alive when you try to suspend? IE, can you ping it from the network, ssh in, etc. If so this might just be failure to turn the backlight on. I haven't had time to test whether I can ping the machine but will try to do so. What I can tell you is the the keyboard also stops responding. The caps lock and num lock no longer show signs of toggling and pressing key combinations like <CTRL><ALT><DEL> and <CTRL><ALT><BKSP> don't reboot the system, or restart X (or show any signs of hard disk activity. I'll still try the ping thing, but the only response I can get from the system (without another machine, if that works) is to hold the OFF/ON button until it reboots. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. |