This problem has been busting my buttons since I purchased my Dell Studio XPS 8000. Ubuntu 9.10 and now 10.04. Here is the hardware:
i7-860 processor
8 GB RAM
nVidia GT220 video card, 1 GB RAM
a couple of hard drives
I am running the "current" nVidia drivers 195.36.08-0ubuntu2 from the Ubunto repository
The problem...
I execute System; Shutdown; Suspend - and it does just that with no problem.
I press the power button and sometimes it resumes to a locked screen with whatever programs were running still running - just what it should do.
Other times it comes up to a login screen. I put in my credentials and find that all programs which were running are no longer running. Just as if I had killed my X session.
Some minor editorial comments: I have looked at Unity and don't want to go there. So I decided to try back on the Hat side of things. I installed CentOS 5.6 on a temporary hard drive in this machine. To install nVidia drivers from nVidia required the OS to be in run level 3. Based on limited usage of CentOS the suspend/resume function seems stable. So I thought I might try installing the nVidia drivers from the nVidia web site on Ubuntu. I have NOT done so yet. I did, after too much searching, find out how to get Ubuntu 10.04 to load to run level 3 (well at least what every other Linux distro calls run level 3) a command interface. End of editorial.
I booted Ubuntu to a command line, logged in and did startx. I worked around a while and did a suspend. Pressed the power button and it resumed OK. I adopted this way of doing things for a while. Within a day I had a resume failure. I arrived at command prompt and was still logged in. I saw the following messages on screen
Quote:
...
10: /usr/bin/X (0x400000+0x43ea2) [0x443ea2]
11: /usr/bin/X (0x400000+0x261aa) [0x4261aa]
12: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f60c9a16c4d]
13: /usr/bin/X (0x400000+0x25d59) [0x425d59]
Segmentation fault at address (nil)
Caught signal 11 (Segmentation fault). Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
|
WOW!!! My first evidence as to what is happening. So I looked at the log file mentioned and compared it to the one for a successful resume. Let me try and show the differences.
Successful resume
Quote:
|
(II) XKB: reuse xkmfile /tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
|
Failed resume
Quote:
|
(II) XKB: generating xkmfile /tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
|
The end of the failed resume log contains the following which is not in the successful log
Quote:
(II) XKB: generating xkmfile /tmp/server-F8D9B4EE1D9075AF4B1C23C75362EE93E14954A0.xkm
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Jun 02 15:51:27 NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select+0+0"
(II) Jun 02 15:51:27 NVIDIA(1): Setting mode "DFP-1:nvidia-auto-select+0+0"
(II) Power Button: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) CHESEN PS2 to USB Converter: Device reopened after 1 attempts.
(II) CHESEN PS2 to USB Converter: Device reopened after 1 attempts.
(II) Logitech Trackball: Device reopened after 1 attempts.
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Jun 02 18:25:27 NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select+0+0"
(II) Jun 02 18:25:27 NVIDIA(1): Setting mode "DFP-1:nvidia-auto-select+0+0"
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x45fcc8]
1: /usr/bin/X (0x400000+0x5dfbd) [0x45dfbd]
2: /lib/libpthread.so.0 (0x7f60cad1f000+0xf8f0) [0x7f60cad2e8f0]
3: /usr/bin/X (dixLookupPrivate+0x12) [0x427be2]
4: /usr/bin/X (0x400000+0x14c994) [0x54c994]
5: /usr/bin/X (0x400000+0x149658) [0x549658]
6: /usr/bin/X (0x400000+0x1498e2) [0x5498e2]
7: /usr/bin/X (xf86Wakeup+0x43f) [0x4707ef]
8: /usr/bin/X (WakeupHandler+0x4b) [0x43a8db]
9: /usr/bin/X (WaitForSomething+0x1d7) [0x467817]
10: /usr/bin/X (0x400000+0x43ea2) [0x443ea2]
11: /usr/bin/X (0x400000+0x261aa) [0x4261aa]
12: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f60c9a16c4d]
13: /usr/bin/X (0x400000+0x25d59) [0x425d59]
Segmentation fault at address (nil)
Caught signal 11 (Segmentation fault). Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) Logitech Trackball: Close
(II) UnloadModule: "evdev"
(II) CHESEN PS2 to USB Converter: Close
(II) UnloadModule: "evdev"
(II) CHESEN PS2 to USB Converter: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
ddxSigGiveUp: Closing log
|
It appears that whatever the xkmfile /tmp/server-xxxxxxxxx is gets lost, deleted, corrupted or something in the event where resume fails. If I look in /tmp I see three of these server files. The "generating" one described in the logs is there and dated yesterday. The "reuse" file is also there and dated yesterday. The third file is dated today.
I have searched around the X.org wiki as recommended in the log however, I am not finding any answers (at least that I understand or seem to relate to the problem). X.org indicates that the current version of X11 is 7.6. I have 7.5 from the Ubuntu repository.
So my real question is... do I report this bug to X.org, Ubuntu or nVidia?
TIA,
Ken
