Resume after suspend to RAM not working in Ubuntu 11.04 (Natty) on laptop Lenovo 3000 N200 with PAE linux kernel

[Alex]

(sorry for my English)

Problem:
On my laptop (Lenovo 3000 N200, Ubuntu 11.04, PAE kernel: linux-image-2.6.38-8-generic-pae) not working resume after suspend to RAM.
Suspend work fine.
Resume after suspend not working. The system appears to come back but is unresponsive: display is turned off, the system can't be pinged or accessed through the network, and keyboard key "CapsLock" not light LED (kernel is hung-up?).

When I booting to usual kernel (linux-image-2.6.38-8-generic) resume after suspend to RAM working fine.
And on Ubuntu 10.10 (Maverick) resume after suspend working fine with PAE kernel.

I made this steps:
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

My battery is good. And I using AC power.
I not using encruption for "swap" or "home" partition. Just for ~/Private directory via tool ecryptfs.

Did the machine break while going to sleep or waking up?
Machine break while waking up.

Is it reproducible?
Yes. It is repeated every time.

Did it work before?
Yes. It is work before, all time in Ubuntu 10.10 (Maverick)

Do you end up with flashing Caps Lock light or similar?
No. Caps Lock light not flashing.

I trying suspending from text mode with this steps:
- add to kernel parameters no_console_suspend;
- shut down X-server (servcie gdm stop);
- Set font: (setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz);
- Making suspend (sudo pm-suspend);
And restore not work with the same problem. No additional messages and other information was displayed.

I made this steps:
https://wiki.ubuntu.com/DebuggingKernelSuspend

""resume-trace" debugging procedure for finding buggy drivers" not helping for me.
on dmesg displayed only "Magic number *" but not "hash matches" lines.
After repeatable attempts, one time I found line:
[ 0.853200] Magic number: 11:870:490
[ 0.853249] acpi PNP0F13:00: hash matches
But i can't find module for this device (i8042) in lsmod. May be it is statically compiled in kernel.
And this message not displayed any time after...

$ dmesg | grep -i PNP0F13
[ 0.300332] pnp 00:09: Plug and Play ACPI device, IDs PNP0f13 (active)
[ 0.821151] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12

I tried to boot into single mode. And make steps for debugging from text mode and resume-trace, but it is not help.
I tried to boot with kernel parameter "init=/bin/bash" and make steps for debugging from text mode and resume-trace, but it is not help.
I tried to boot with kernel parameter "init=/bin/bash" and unloading _all_ as possible modules that showing by lsmod.
Commnd help me: lsmod | cut -f1 -d" " | grep -v Module | while read EACH; do modprobe -vr $EACH; done
A then lsmod show following modules:
jfs 174783 1
i915 450979 1
drm_kms_helper 40745 1 i915
drm 184133 2 i915,drm_kms_helper
ahci 21591 1
libahci 25548 1 ahci
i2c_algo_bit 13184 1 i915
video 18951 1 i915
and make steps for debugging from text mode and resume-trace, but it is not help.

And hibernate not working too for me.

Only work solution for me - is it not using PAE kernel...

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic-pae 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pramen 1895 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc300000 irq 47'
   Mixer name : 'Realtek ALC861-VD'
   Components : 'HDA:10ec0862,17aa3867,00100001'
   Controls : 20
   Simple ctrls : 13
Date: Tue May 3 13:51:25 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=05c76263-b470-4b39-9664-9864daea1c20
MachineType: LENOVO 0769AK3
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: root=UUID=70054f55-cb45-4fc8-b335-4002b7b58f79 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic-pae N/A
 linux-backports-modules-2.6.38-8-generic-pae N/A
 linux-firmware 1.52
SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-04-30 (2 days ago)
WpaSupplicantLog:

dmi.bios.date: 07/29/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 68ET37WW
dmi.board.name: IEL10
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd07/29/2008:svnLENOVO:pn0769AK3:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 0769AK3
dmi.product.version: 3000 N200
dmi.sys.vendor: LENOVO

[Ralph Finch (buggsy2)]

I have a similar though not identical problem. On resume from Suspend, my bluetooth USB dongle doesn't seem to work, and the BT control window doesn't show its full options, just a large Bluetooth On button. BT mouse doesn't work. Usually a full reboot fixes it.

HW: Acer Aspire One, 2GB RAM, SSD
Ubuntu 11.04

No problems with prior 10.x Ubuntu.

[Fabio Marconi (fabiomarconi)]

@Ralph
Please open another bug report typing in a terminal
ubuntu-bug linux

[Fabio Marconi (fabiomarconi)]

Hello Alexander
Can you please reporduce the bug then attach here:
/var/log/kern.log
/var/log/kern.log.1
Thanks
Fabio

[Fabio Marconi (fabiomarconi)]

temporarily assigned

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[michelD (michel-damiens)]

confirm : exactly same bug as described

[Fabio Marconi (fabiomarconi)]

Hello michelD
Can you please reproduce the bug then attach here:
/var/log/kern.log
/var/log/kern.log.1
Thanks
Fabio

[michelD (michel-damiens)]

Hello Fabiio

Thanks for your help
Attaching kern.log obtained just after suspend-to-disk not resuming
Hope it helps

Michel

[Fabio Marconi (fabiomarconi)]

Sep 13 23:30:54 cussol11 kernel: [10854.188075] usb 6-2: reset full speed USB device using uhci_hcd and address 3
Sep 13 23:30:54 cussol11 kernel: [10854.335123] btusb 6-2:1.0: no reset_resume for driver btusb?
Sep 13 23:30:54 cussol11 kernel: [10854.335127] btusb 6-2:1.1: no reset_resume for driver btusb?

===//===

Sep 13 23:30:54 cussol11 kernel: [10856.077221] ata3.00: unexpected _GTF length (8)
Sep 13 23:30:54 cussol11 kernel: [10856.089844] ata3.00: unexpected _GTF length (8)
Sep 13 23:30:54 cussol11 kernel: [10856.090250] ata3.00: configured for UDMA/100

[penalvch (penalvch)]

Alexander, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please attach the full information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]