[karmic, intel] Laptop locks up moments after resuming from suspend

Architecture: i386
DistroRelease: Ubuntu 9.10
Package: xorg 1:7.4~5ubuntu20
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.30-6.7-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4~5ubuntu20
 libgl1-mesa-glx 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt
 libdrm2 2.4.9+git20090502.r1.68103b27-0ubuntu0sarvatt
 xserver-xorg-video-intel 2:2.7.99.1+git20090505.r1.a8a771a8-0ubuntu0sarvatt
 xserver-xorg-video-ati 1:6.12.2-1ubuntu1
Uname: Linux 2.6.30-6-generic i686
UserGroups:

system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.30-6-generic

Architecture: i386
DistroRelease: Ubuntu 9.10
MachineType: Acer Aspire 3690
Package: xorg 1:7.4~5ubuntu20
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.30-6-generic root=UUID=681fabcf-a526-481f-9858-80d1901cdcb4 ro single
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.30-6.7-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4~5ubuntu20
 libgl1-mesa-glx 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt
 libdrm2 2.4.9+git20090502.r1.68103b27-0ubuntu0sarvatt
 xserver-xorg-video-intel 2:2.7.99.1+git20090505.r1.a8a771a8-0ubuntu0sarvatt
 xserver-xorg-video-ati 1:6.12.2-1ubuntu1
Uname: Linux 2.6.30-6-generic i686
UserGroups:

Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 02/13/2007
dmi.bios.vendor: Acer
dmi.bios.version: V3.50
dmi.board.name: Grapevine
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV3.50:bd02/13/2007:svnAcer:pnAspire3690:pvrV3.50:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 3690
dmi.product.version: V3.50
dmi.sys.vendor: Acer
fglrx: Not loaded
fglrx-loaded: Error: command ['grep', 'fglrx', '/var/log/kern.log', '/proc/modules'] failed with exit code 1:
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.30-6-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

dmesg after the oops

dmesg from a working suspend: jaunty's 2.6.28

Linux cwillu-acer 2.6.30-999-generic #1243674012 SMP Sat May 30 09:44:52 UTC 2009 i686 GNU/Linu

I just completed 20 suspend cycles:

>>> for x in range(20):
... print x
... time.sleep(60)
... os.system('pm-suspend')

That completed without any errors, dmesg from the process is attached.

Just had a hang with BUG: unable to handle kernel paging request under 2.6.30-999-..., although it was certainly up longer than the mainline -rc kernels. Don't know if that means anything beyond "git bisect is going to be painfully probabilistic".

@Carey -- did you get a panic stack for that? Given it no longer occurs right after resume its just as likely to be a different issue. Your resume issue is quite likely related to bug for which a patch was included in the kernel you tested there. So if we do have a stack it would be good to get it pasted in here, so we can try and determine if it is related or not.

2.6.29 from the mainline kernel repo works as well.

Released 2.6.30 and latest 2.6.31rc4 still show the issue.

Conveniently, 2.6.31rc4 fixed another suspend issue re: intel hanging on resume, which helpfully eliminates a confounding factor.

Resume still hangs in the same manner with all karmic updates applied up to Monday.

2.6.32 ext3/4 rootfs still has the usual hangs.

I finally got a chance to try a different rootfs entirely; a btrfs root resumes from suspend and runs stable.

Carey, was there any heavy disk activity when this bug occured? My laptop also seem to hang with seemingly heavy disk i/o on resume, but would finish if I give it long enough time (like 10 minutes?). I'm suspecting mlocate/updatedb to be the culprit, but I haven't got a concrete evidence.

Ahmad, that issue you mention could be caused by the fglrx driver if you are using it. That would be bug #391628

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.