Suspend problem with Maverick on ThinkPad W500

Bug #644223 reported by Thomas Dreibholz
206
This bug affects 43 people
Affects Status Importance Assigned to Milestone
pm-utils (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Maverick by Thomas Dreibholz

Bug Description

Binary package hint: pm-utils

Suspend with Maverick/64-bit on ThinkPad W500 is very unreliable. In about 1 of 3 cases, the system hangs with dark screen and suspend LED blinking. I have used pm_trace to track down the problem:
[ 0.963116] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:544
[ 0.963165] pci 0000:00:00.0: hash matches
The full dmesg output is attached.

lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

lsb_release -rd:
Description: Ubuntu maverick (development branch)
Release: 10.10

Tags: suspend
Revision history for this message
Thomas Dreibholz (dreibh) wrote :
Revision history for this message
Thomas Dreibholz (dreibh) wrote :

I have captured another dmesg output of a failed suspend:
[ 1.002034] Magic number: 0:248:190
[ 1.002091] acpi device:1c: hash matches

The full dmesg output is attached.

Revision history for this message
mycl (415fox) wrote :

I have the same symptoms on a Lenovo X200 with Maverick Beta.

Except, when I went through the suspend debug process I didn't get a device hash matches line. My Magic number was:

[ 0.681422] Magic number: 0:898:740
[ 0.681465] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:586

Thomas, could you please post the results of:
lspci -vvv

so we can see which device matches your hash?

Revision history for this message
mycl (415fox) wrote :

Oops. I see you did post your lspci. It looks like the kernel modules shpchp and pciehp. I tried adding the lines:

blacklist shpchp
blacklist pciehp

to /etc/modprobe.d/blacklist.conf

I've gone through a couple of suspend/resume cycles successfully. But, since this is an intermittent issue, I will have to continue to use it for a day or so to see if this really fixes it.

Revision history for this message
mycl (415fox) wrote :

Fail. The above does not prevent the problem.

Revision history for this message
Thomas Dreibholz (dreibh) wrote :

I have tried "blacklist btusb", since I noticed some error messages on btusb in /var/log/syslog. But no change, the suspend problem is still there.

A "lspci -vvv" output is now attached. May be the more verbose output can help somebody identifying the problem.

Changed in pm-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
mycl (415fox) wrote :

This might be the solution:

At some point, a few Ubuntu iterations back I put the following lines in my /etc/modules file:

thinkpad_ec force_io=1
tp_smapi

This was recommended by the thinkwiki x200 page to try to get the accelerometer-based active hard-drive protection working, as well as to set charge-discharge limits for longer battery life.

I've since upgraded to an Intel SSD (which is awesome!) and I guess I'm willing to throw battery life under the bus. After removing these two lines I've been able to suspend successfully for two days.

Revision history for this message
mycl (415fox) wrote :

Also, if you think that Bluetooth is causing problems you can disable it in BIOS setup at boot.

Revision history for this message
mycl (415fox) wrote :

Son of a bitch is back. Although it seems a lot more infrequent. It just happened for the first time in a few days.

Revision history for this message
Mark Cocker (mark-earth) wrote :

Re comment 8, the Thinkpad W500 BIOS (V3.15/3.17) configuration doesn't have an option to disable Bluetooth.

tags: added: suspend
Revision history for this message
mycl (415fox) wrote :

Since I can't trap this bug using the normal CMOS-clock-based method, and since so far it only seems to affect thinkpads, I'm going on a lark and blacklisting thinkpad_acpi. So far I'm not seeing any reduction in functionality. Suspend/resume has worked a few times successfully, but so it has in the past with other experiments. All LEDs, wifi, special keys, battery, powertop and sound are working correctly -- so who knows what functionality that module is even providing.

Revision history for this message
mycl (415fox) wrote :

One thing I am definitely seeing is a faster suspend/resume process. In the past, even when successful, it has taken about five seconds to suspend. Now, it's more like one.

Revision history for this message
mycl (415fox) wrote :

There. I just did 10 successful suspend/resumes in a row. If this is good for a couple of days, I'll try to figure out who owns thinkpad_acpi and send them the bug.

Revision history for this message
mycl (415fox) wrote :

No help. Still the occasional freeze up. I tried the kernel suspend debug thing again, and here is the message:

[ 0.701281] registered taskstats version 1
[ 0.701579] Magic number: 0:898:740
[ 0.701621] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:586

So, still no indication of a device to blame.

Revision history for this message
Dukai Gábor (gdukai) wrote :

I have a similar problem on a T500. The difference is that I rarely manage to make it suspend at all.

For sure it's not the bluetooth because I tried with bluetooth unloaded. I tried to unload thinkpad_acpi, hdaps, tp_smapi and thinkpad_ec. Only one time with all of them unloaded I managed to make it suspend. Next time it didn't work.

I didn't have suspend problems before maverick.

Revision history for this message
Thomas Dreibholz (dreibh) wrote :
Download full text (6.7 KiB)

I have tried the following blacklist entries:
blacklist btusb
blacklist thinkpad_acpi

Unfortunately, this has not been successful. The suspend problem still exists as before.

These are my loaded modules:
$ lsmod
Module Size Used by
btrfs 506518 0
zlib_deflate 21866 1 btrfs
crc32c 3007 1
libcrc32c 1268 1 btrfs
ufs 74447 0
qnx4 8101 0
hfsplus 78159 0
hfs 47396 0
minix 29289 0
ntfs 97516 0
vfat 10954 0
msdos 7960 0
fat 56244 2 vfat,msdos
jfs 183125 0
xfs 766115 0
exportfs 4226 1 xfs
autofs4 28170 3
binfmt_misc 7984 1
arc4 1497 2
snd_hda_codec_conexant 37356 1
snd_hda_intel 26019 2
snd_hda_codec 100919 2 snd_hda_codec_conexant,snd_hda_intel
snd_hwdep 6660 1 snd_hda_codec
snd_pcm 89104 2 snd_hda_intel,snd_hda_codec
iwlagn 202721 0
snd_seq_midi 5932 0
iwlcore 146875 1 iwlagn
snd_rawmidi 22207 1 snd_seq_midi
joydev 11363 0
pcmcia 40944 0
snd_seq_midi_event 7291 1 snd_seq_midi
mac80211 266657 2 iwlagn,iwlcore
snd_seq 57512 2 snd_seq_midi,snd_seq_midi_event
i915 330249 3
cfg80211 170293 3 iwlagn,iwlcore,mac80211
r852 11348 0
sm_common 4441 1 r852
nand 38430 2 r852,sm_common
nand_ids 4443 1 nand
snd_timer 23850 2 snd_pcm,snd_seq
snd_seq_device 6912 3 snd_seq_midi,snd_rawmidi,snd_seq
drm_kms_helper 32836 1 i915
lp 10201 0
drm 206161 4 i915,drm_kms_helper
yenta_socket 24279 0
psmouse 62080 0
nand_ecc 4406 1 nand
pcmcia_rsrc 10357 1 yenta_socket
mtd 21479 2 sm_common,nand
snd 64117 13 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
pcmcia_core 17677 3 pcmcia,yenta_socket,pcmcia_rsrc
soundcore 1240 1 snd
ppdev 6804 0
snd_page_alloc 8588 2 snd_hda_intel,snd_pcm
i2c_algo_bit 6208 1 i915
intel_agp 32080 2 i915
video 22176 1 i915
uvcvideo 62379 0
videodev 49359 1 uvcvideo
v4l1_compat 15519 2 uvcvideo,videodev
v4l2_compat_ioctl32 12646 1 videodev
serio_raw 4910 0
parport_pc 30086 1
parport 37032 3 lp,ppdev,parport_pc
output 2527 1 video
tpm_tis 9894 0
tpm 16013 1 tpm_tis
tpm_bios 6426 1 tpm
usbhid 42062 0
hid 84678 1 usbhid
reiserfs 244936 2
firewire_ohci 24679...

Read more...

Revision history for this message
Akagi (akagi010) wrote :

Hi,

in bug report #659668 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659668/comments/23) a workaround is given. This workaround stopped to work for me after todays update of my Ubuntu 10.10 installation.

Obviously there are at least two mechanism to suspend a T500 laptop: One for the session plugin of the top panel and another one if one uses the On/Off-Button of the laptop. The said workaround only worked for the session plugin.

Best regards!

Revision history for this message
timobaumann (timobaumann) wrote :

"me too" on a T500; I also have an SSD so may this be an indicator?

Revision history for this message
Ralph Meijer (ralphmeijer) wrote :

timobaumann: My T500 does not have an SSD, but does experience the reported issue.

Revision history for this message
Thomas Dreibholz (dreibh) wrote :

As a work-around, I have now self-compiled a 2.6.36-rc8 kernel from the kernel.org git repository, just using the configuration from /boot/config-2.6.35-22-generic. Suspend/resume works fine with the new 2.6.36 kernel and I have not seen any other problems yet.

Note: I am using the Intel graphics chipset of my W500, having the ATI one deactivated in the BIOS settings. Therefore, using the 2.6.36-rc8 kernel as work-around may not work for people using the ATI chipset (and closed-source fglrx drivers) instead.

Revision history for this message
Greg Tabor (gat92) wrote :

Referencing back to my comments on bug 659668, now marked as duplicate of this one...

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659668/comments/23

I believe this hack only works for lid close as reported by akagi above. The recent kernel updates did not fix the problem, but replacing my hack restored the workaround after the updates.

My experience has been that the bug only affects intel graphics on my W500. When I switch the BIOS config to the ATI graphics chip (and the open source ati driver) suspend works fine for me with Maverick and without my pm-suspend hack. Another poster to ubuntuforums (http://ubuntuforums.org/showthread.php?p=10009357#post10009357) reports that suspend works fine for him with a clean Maverick install using the ATI chip and the fglrx driver.

Glad to hear it's fixed in 2.6.38. Hopefully we can get the relevant fix, whatever it is, pushed out in a released Maverick kernel.

Revision history for this message
Akagi (akagi010) wrote :

I installed the mainline kernel v2.6.36-rc8-maverick and it fixes the problem also (at least for me). Now suspend works without Gregs workaround.

There might be still an issue if a docking station is involved: When I detach the notebook from the docking station (and go to battery) and suspend it fails. But this might be another issue.

Revision history for this message
Dukai Gábor (gdukai) wrote :

I have the same issue with a docking station and a T500.

Revision history for this message
ReneS (mail-03146f06) wrote :

Seems to be gone with 2.6.36 Maverick on my T500. Willl keep an eye on it.

Revision history for this message
Michal Smid (michalsmid) wrote :

I can confirm this bug on Toshiba U400. About one third of the suspendations just freezes the computer and the fan speed increases.

Revision history for this message
bofphile (bofphile) wrote :

Same issue on my T500 (model :2082-7SG). Suspend worked perfectly fine on previous versions of Ubuntu.

Revision history for this message
gdi2k (gdi2k) wrote :

In case it helps, I have the same on my ThinkPad X200 with Intel graphics, so it's not just the big ThinkPads.

Revision history for this message
Kapil Thangavelu (hazmat) wrote :

i can confirm the bug on a T400 with intel graphics as well. i get either blinking sleep light indefinitely (on lid close) with the cpu running hot, or on pressing suspend hot key, i'll sometimes get a reboot instead of a sleep.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

I am on an Acer Aspire 5734Z and I had the exact symptoms described above.

My dmesg only showed:

[ 0.964933] Magic number: 0:898:740
[ 0.964935] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:586

I updated to the 2.6.36 kernel and the issue seems to be resolved.

Revision history for this message
mycl (415fox) wrote :

I have a work-around that seems to be working.

Create the file:

/etc/pm/sleep.d/20_chvt_mjf

And make it executable with:

chmod a+x /etc/pm/sleep.d/20_chvt_mjf

And put the following inside:

#!/bin/sh

case "$1" in
  suspend) chvt 1; ;;
  resume) chvt 7; ;;
esac

return 0

Revision history for this message
mycl (415fox) wrote :

The fact that this works tells me that this problems has something to do with the graphics driver, though I can't say what exactly. This is my graphics controller. Does yours match?

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device 20e4
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 45
        Region 0: Memory at f2000000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 1800 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

Revision history for this message
Russel Winder (russel) wrote :

For my T500, I see:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device 2114
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 31
 Region 0: Memory at f4400000 (64-bit, non-prefetchable) [size=4M]
 Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at 1800 [size=8]
 Expansion ROM at <unassigned> [disabled]
 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee0300c Data: 41c1
 Capabilities: [d0] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: i915

Although I get the suspend problem in Ubuntu Maverick (where the problem did not happen with Lucid), I get no problem with Debian Squeeze -- so until things are fixed in Maverick I am running Squeeze. Perhaps this triangle of version numbers of kernel and drivers can help discover what the problem is?

Revision history for this message
gervin23 (gervin23) wrote :

I just upgraded my Thinkpad T60 to 10.10 and experienced a similar problem (actually 2). First problem was the machine wouldn't suspend. The sleep light blinked but at the usual point of powering down it jumped back alive asking for login. I tracked it down to partport_pc failing to disable. I then tried unloading parport, parport_pc (and any other depending on partport) but got the unending blinking sleep light and had to pull the plug. Upon reboot I re-enabled parallel port in the BIOS which ended up fixing the problem.

Revision history for this message
Michal Smid (michalsmid) wrote :

On my Toshiba U400 I have the same (or similar) graphics card as mentioned above (Intel Mobile 4 Series Chipset Integrated Graphics Controller), so the problem may be related to it.

As a temporary workaround I use the command (as proposed somewhere)
acpitool -s
to suspend the computer, which works fine.

Attaching graphics card info:
hwinfo --gfxcard
08: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_2a42
  Unique ID: _Znp.f7oS7PcORP3
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x2a42 "Mobile 4 Series Chipset Integrated Graphics Controller"
  SubVendor: pci 0x1179 "Toshiba America Info Systems"
  SubDevice: pci 0xff50
  Revision: 0x07
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xf4000000-0xf43fffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  I/O Ports: 0x1800-0x1807 (rw)
  IRQ: 46 (1321571 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00002A42sv00001179sd0000FF50bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

09: PCI 02.1: 0380 Display controller
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_2a43
  Unique ID: ruGf.Aa951Fv2j09
  SysFS ID: /devices/pci0000:00/0000:00:02.1
  SysFS BusID: 0000:00:02.1
  Hardware Class: graphics card
  Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller"
  SubVendor: pci 0x1179 "Toshiba America Info Systems"
  SubDevice: pci 0xff50
  Revision: 0x07
  Memory Range: 0xf4400000-0xf44fffff (rw,non-prefetchable)
  Module Alias: "pci:v00008086d00002A43sv00001179sd0000FF50bc03sc80i00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Revision history for this message
Akagi (akagi010) wrote :

After I used two of the workarounds (1. a script /usr/sbin/pm-suspend and 2. mainline kernel 2.6.36 with drm-next) for two weeks I come to the conclusion that both are not reliable. To be honest: They fail in 30-50 %.

In some cases the notebook (Lenovo T500) fails to suspend as usual, in other cases the notebook fails to resume. In this case the moon and battery LEDs are on, but nothing happens. Normally the "flash" and disk LEDs are also active shortly afterwards.

Revision history for this message
Robert Entner (robertentner) wrote :

For me using the kernel of Ubuntu 10.04 works perfectly fine and reliable. The same on my daughter's Laptop (Lenovo with Intel graphics).

Dell Latitude E6400 with Intel graphics.
Linux bdell 2.6.32-25-generic-pae #44-Ubuntu SMP Fri Sep 17 21:57:48 UTC 2010 i686 GNU/Linux

Revision history for this message
Edward Parker (bontano) wrote :

Same problem here on a T400, 64 bit Ubuntu desktop. Suspend worked fine until upgrade, now locks up and must be forced to reboot.

Revision history for this message
gervin23 (gervin23) wrote :

Scratch my comment (#33). The bios settings seemed to work a few times but now stays in sleep mode and requires power down. Greg Tabor's pm-suspend workaround is working so far (ATI with open source driver).

Revision history for this message
Michael A. Phillips (maphilli14) wrote :

I had all the symptoms above, flashing moon, power off as the only soltuion. My W500 was using 10.10 after upgrade form 10.4. I switched the BIOS from integrated to descrete (Intel to ATI) and haven't done anything else. Things are 100% so far. I'm up to 3day uptime now! Before, it was totally unusable, now, works but my battery suffers! :(

Revision history for this message
mo (deez) wrote :

The solution by mycl (comment #30) solved this for me on a Thinkpad X200 with a Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller. Constant success for over two weeks now.

Revision history for this message
Mihai (udev) wrote :

Using the 2.6.36 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/linux-image-2.6.36-020636-generic_2.6.36-020636.201010210905_amd64.deb seems to have fixed it for me. (T400, Intel 4500MHD graphics)

Revision history for this message
Michal Smid (michalsmid) wrote :

The kernel update proposed by Mihai (#41) did not worked for me.

Revision history for this message
gervin23 (gervin23) wrote :

Scratch my comment #39. None of these workarounds are working consistently. This is extremely annoying.

Revision history for this message
Alin Trăistaru (alindt) wrote :

This problem seems to have dissapeared (at least for me on a T500) from 2.6.35-23 on with parport and tpm_tis modules blacklisted:

blacklist parport
blacklist parport_pc
blacklist ppdev
blacklist lp
blacklist tpm_tis

Revision history for this message
Tomas Kliegr (klieto) wrote :

Same issue on my T510i 4313-8AG with Intel HD Graphics on Ubuntu 10.10 with kernel 2.6.35-24-generic. Suspend and hibernate are both very unreliable (literally stopped working). It worked fine recently, it could be perhaps blamed to the recent kernel update.
The system freezes during suspend or hibernate, with the sleep indicator blinking indefinitely.

Revision history for this message
ReneS (mail-03146f06) wrote :

This problem occurred once so far with 2.6.37 on my T500. Interestingly not even the TFT was switched off. The login screen came back on, the system was frozen, and the moon flashing.

Revision history for this message
Nils Fredrik Gjerull (nfg) wrote :

I can confirm this bug on my Dell Latitude E5400, which also uses a Intel Mobile 4 Series chipset (rev 07).

I have installed the 32-bit version of Ubuntu Maverick running kernel 2.6.35-24-generic. The laptop has a 64-bit CPU.

I ran through the pm_trace procedure and got this message:
[ 0.653986] Magic number: 0:608:321
[ 0.653988] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:545
[ 0.654000] tty tty46: hash matches
[ 0.654012] pci 0000:00:02.0: hash matches

The pci number is:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 0262
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 45
        Region 0: Memory at f6c00000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at efe8 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c Data: 4199
        Capabilities: [d0] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: i915
        Kernel modules: i915

Revision history for this message
Michal Smid (michalsmid) wrote :

None of the proposed workarouds work for me, except for to use "acpitool -s" which works fine to suspend.

The only problem was that it needed root privilegies, which was very annoying.
But it can be bypassed by adding line "%michal ALL=NOPASSWD: /usr/bin/acpitool"
using "sudo visudo"

Revision history for this message
Thomas Dreibholz (dreibh) wrote :

I am using kernel 2.6.37 since more than two weeks now. Using this kernel version, suspend to RAM and hibernation work fine on my Thinkpad W500 running 64-bit Maverick.

Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 644223] Re: Suspend problem with Maverick on ThinkPad W500

On Friday 21,January,2011 09:52 PM, Thomas Dreibholz wrote:
> I am using kernel 2.6.37 since more than two weeks now. Using this
> kernel version, suspend to RAM and hibernation work fine on my Thinkpad
> W500 running 64-bit Maverick.
>

In that case, let's close this bug. Please file a new bug if suspend still fails
for anybody using this model -- it's probably not the same bug.

  affects ubuntu/pm-utils
  status fixreleased

--
Kind regards,
Loong Jin

Changed in pm-utils (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.