Thinkpad X31 fails to resume after suspend

Bug #561926 reported by Roland Dreier
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

With Lucid (kernel 2.6.32-20, also tried 2.6.32-19 as well as 2.6.34-020634rc3-generic from the upstream repository), my X31 goes to sleep fine but fails to resume; 2.6.32 wakes up part of the way but has a black screen, while the upstream kernel wakes up to a corrupted screen.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-20-generic 2.6.32-20.30
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: garry 1257 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1QHT23WW-1.08'
   Mixer name : 'ThinkPad EC 1QHT23WW-1.08'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 14 [100%] [off]
Date: Mon Apr 12 19:55:02 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a5eb2a2c-0b9e-4bcb-936d-66242a4c8c0b
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 2884JUU
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=923321a0-41ad-4cb4-a376-df67ceb7bea0 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
SourcePackage: linux
dmi.bios.date: 09/22/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1QET97WW (3.02 )
dmi.board.name: 2884JUU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1QET97WW(3.02):bd09/22/2005:svnIBM:pn2884JUU:pvrThinkPadX31:rvnIBM:rn2884JUU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2884JUU
dmi.product.version: ThinkPad X31
dmi.sys.vendor: IBM

Revision history for this message
Roland Dreier (roland.dreier) wrote :
Revision history for this message
Roland Dreier (roland.dreier) wrote :

FWIW, with 2.6.32-20, if I set "modeset=0" for the radeon module, then resume appears to work fine.

Unfortunately with modesetting disabled, the desktop (at least the UNR launcher interface) appears quit flickery; with KMS the interface was not flickery at all.

Revision history for this message
Roland Dreier (roland.dreier) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Roland,

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.]

tags: added: kernel-suspend
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Roland Dreier (roland.dreier) wrote :

Unfortunately I don't have access to the system at the moment; will retest when I get a chance. However note that I did test 2.6.34-020634rc3-generic as described in the original report, and I don't see anything that promising in the post-2.6.34-rc3 changes to drivers/gpu/drm/radeon in the upstream kernel.

tags: removed: needs-upstream-testing
Revision history for this message
Martin Reiche (grimsrud) wrote :

1) I have the same problem and can confirm that my X31 has the same problem. I tried also the last possiple kernel (2.6.34-020634rc6-generic) with the same result: fail.

2) Over here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550401 we try to solve the same problem. Maybe this reports should be merged or one marked as duplicate?

Revision history for this message
Paul Gear (paulgear) wrote :

I can do whatever testing is necessary to get this bug fixed if someone can point me to the right process. It worked perfectly on karmic, and when i reinstalled on lucid, it is broken.

Revision history for this message
Paul Gear (paulgear) wrote :

Suspend/resume still fails on linux-image-2.6.35-999-generic (2.6.35-999.201007241005), from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-image-2.6.35-999-generic_2.6.35-999.201007241005_i386.deb

Revision history for this message
Paul Gear (paulgear) wrote :

I've confirmed that this bug is not present on linux-image-2.6.31-11-rt (2.6.31-11.154) from lucid universe - suspend/resume works well, and very quickly. Is there anything else i need to do to demonstrate the regression between 2.6.31 and 2.6.32?

Revision history for this message
Martin Reiche (grimsrud) wrote :

Problem still persists in 10.10 alpha3.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.