Thinkpad W500 suspend does not resume with 8.10

I can confirm the suspend/resume problem on ThinkPad W500 using 8.10 Intrepid Ibex. The system successfully suspends (to disk and to RAM), but resume does not work. On resume, the display always remains dark. Usually, the system seems to hang in this case, but sometimes it still accepts keyboard input and allows for shutdown.

The only way I found to avoid these problems is to turn off compiz. Without compiz, suspend/resume work.

Can you please try this with the Jaunty beta? Thanks.

Can't try this with the life CD, since compiz requires fglrx driver install + reboot. Since I am traveling and need the machine, can't install the beta either right now ... thanks for your work! Hans

I am running Jaunty release with W500 with fglrx driver. I see the same issue.

uname -a

Linux mpati-lnx 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

lsmod

Module Size Used by
binfmt_misc 16776 1
bridge 56340 0
stp 10500 1 bridge
bnep 20224 2
vboxnetflt 91016 0
vboxdrv 117544 1 vboxnetflt
vmnet 47812 13
ppdev 15620 0
parport_pc 40100 0
vmblock 21028 3
vmci 58452 0
vmmon 76912 0
input_polldev 11912 0
joydev 18368 0
lp 17156 0
parport 42220 3 ppdev,parport_pc,lp
snd_hda_intel 435636 2
snd_pcm_oss 46336 0
snd_mixer_oss 22656 1 snd_pcm_oss
snd_pcm 82948 2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy 10756 0
snd_seq_oss 37760 0
snd_seq_midi 14336 0
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 15104 2 snd_seq_oss,snd_seq_midi
snd_seq 56880 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
arc4 9856 2
uvcvideo 63240 0
snd_timer 29704 2 snd_pcm,snd_seq
snd_seq_device 14988 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
ecb 10752 2
pcmcia 44748 0
compat_ioctl32 9344 1 uvcvideo
snd 62628 13 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
iwlagn 100228 0
iwlcore 93184 1 iwlagn
thinkpad_acpi 66560 0
videodev 41600 1 uvcvideo
fglrx 2081540 37
intel_agp 34108 0
video 25360 0
soundcore 15200 1 snd
psmouse 61972 0
serio_raw 13316 0
pcspkr 10496 0
sdhci_pci 15232 0
mac80211 217208 2 iwlagn,iwlcore
yenta_socket 32396 1
rsrc_nonstatic 19328 1 yenta_socket
pcmcia_core 43540 3 pcmcia,yenta_socket,rsrc_nonstatic
led_class 12036 2 iwlcore,thinkpad_acpi
nvram 16396 1 thinkpad_acpi
v4l1_compat 21764 2 uvcvideo,videodev
agpgart 42696 2 fglrx,intel_agp
iTCO_wdt 19108 0
iTCO_vendor_support 11652 1 iTCO_wdt
output 11008 1 video
ricoh_mmc 11904 0
sdhci 23940 1 sdhci_pci
btusb 19608 2
snd_page_alloc 16904 2 snd_hda_intel,snd_pcm
cfg80211 38032 3 iwlagn,iwlcore,mac80211
reiserfs 236288 2
ohci1394 38576 0
ieee1394 94660 1 ohci1394
e1000e 121136 0
fbcon 46112 0
tileblit 10752 1 fbcon
font 16384 1 fbcon
bitblit 13824 1 fbcon
softcursor 9984 1 bitblit

lspci -vvnn

00:00.0 Host bridge [0...

[This is an automatic notification.]

Hi hansb,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 303083

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 303083 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/303083

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.