dell precision t3400 resume after suspend not working ubuntu 9.10

[guentherk1]

Just installed Ubuntu 9.10 producton on Dell Precision t3400. I suspend machine and resume via power button. Resume goes to blank screen.

ProblemType: Bug
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: karl 1922 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfdffc000 irq 16'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,10280214,00100400'
   Controls : 21
   Simple ctrls : 14
Date: Sun Nov 1 02:28:47 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: Dell Inc. Precision WorkStation T3400
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=d7e46263-7a0d-46b0-a65d-7c8908c8590c ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1937): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1937): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2033): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1993): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 08/14/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0TP412
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/14/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T3400
dmi.sys.vendor: Dell Inc.

[guentherk1 (karl-guentherk)]

I am the one who submitted this bug.

Ubuntu 9.10: This is the first that have attempted to do a suspend and resume process on Ubuntu in a while on this machine. It does not work. The resume after suspend comes up to a blank screen and the computer locks up. This is true even waiting 10 minutes or more, the computer is still locked up.

Ubuntu 9.04: I did test on Ubuntu 9.04 with no updates applied on this same machine and suspend and resume don't work on the base 9.04 either.

Fedora 10: Suspend and Resume work fine on this same machine using Fedora 10.

[MarkJ (marker)]

I also have a dell t3400 workstation. When I come back to the machine after a long time... the screensaver is on... i use a screensaver password.... when i type it in and push enter... the following things have been known to happen:
1. machine wakes up from screensaver nicely
2. semi-freezes ctrl alt f1... then ctrl alt f7 wakes it up.
3. totally freezes

[MarkJ (marker)]

thats on 9.04 ... i'll be installing 9.10 soon.

[guentherk1 (karl-guentherk)]

I would appreciate it if someone at Ubuntu would give me some feedback on this failed suspend resume on Ubuntu 9.10.

I would think the open source code to make it work would be readily available since it works on Fedora 10.

Thank You,

Karl

[jimk (jim-by-the-bay)]

Neither suspend nor hibernate work for me on a fresh 9.10 install. In both cases it looks like the display is locked up somehow after restart. Once I tried sshing into the box from another system after the restart... that worked OK but running "top" from that ssh session showed that Xorg was taking 100% of one of the dual processors. Just for kicks I tried killing (with "sudo kill -9") the Xorg, but it kept showing up again with a new PID still taking 100% of a processor.

JimK

[jimk (jim-by-the-bay)]

Hibernate works for me now, after installing a proprietary nVidia hardware driver. The video card in my box (a Dell Precision T3400) is the 256MB PCIe x16 nVidia NVS 290, and the default driver was not up to the task... but the Ubuntu 9.10 installation came with two proprietary drivers for nVidia ready to activate: NVIDIA accelerated graphics driver versions 173 and 185 (under Applications->System->Hardware Drivers). A little web research indicated that 173 might be a bit more stable so I activated it first, and it seems totally sufficient for my needs (which admittedly do not include any 3D graphics or gaming, just a good screen resolution and adequate hibernate behavior).

[Jeremy Foshee (jeremyfoshee)]

Hi guentherk1,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]