Intrepid: Suspend not working on Asus A6Km

[elele]

Using a fresh install of 64-bit Intrepid beta (kernels 2.6.27-4-generic and 2.6.27-5-generic), suspend to ram is not working on Asus A6Km notebook (Turion64, GeForce Go 7300, SiS chipset). This is regression from Hardy, where suspend to ram functioned perfectly.

Symptoms are: Black screen when resuming from suspend, keyboard unresponsive (no caps / num lock lights) and not reachable from the network. Seems like a kernel lockup. I tried various debugging methods, but none of them helped. First I stopped gdm, unloaded the Nvidia kernel module and then tried suspend using acpitool -s and /etc/acpi/sleep.sh. No luck there. I also did the same in plain VGA console (booted without usplash), but that didn't work either.

Following the Ubuntu Wiki DebuggingKernelSuspend "resume-trace" procedure did produce some information, but I'm not sure how useful it is. This is the the only match in dmesg:

[ 2.181273] Magic number: 12:946:505
[ 2.181277] i8042 i8042: hash matches

I also tested suspend in Fedora 10 Beta and openSUSE 11.1 Beta 2, which like Intrepid use the 2.6.27 kernel. Same lockup happened in both of them.

Please let me know if there's anything else I could try.

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information as separate attachments:
 * Output of uname -a
    * uname -a > uname.txt
 * Output of sudo lspci -vvnn
    * sudo lspci -vvnn > lspci.txt
 * Output of sudo dmidecode
    * sudo dmidecode > dmidecode.txt
 * Try to suspend/hibernate and then restart the system and attach /var/log/kern.log and /var/log/kern.log.0
 * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    * cp -r /proc/acpi /tmp
    * tar -cvjf ~/acpi.tar.bz /tmp/acpi
    * attach acpi.tar.bz from your home directory

[elele (elele-deactivatedaccount)]

Thanks Chris, here is the information you requested.

Please note that I didn't include kern.log.0, since kern.log contained the log entries from the attempted suspend and the freeze-forced reboot (at 00:51:17) that followed.

[Chris Coulson (chrisccoulson)]

Thanks for the information, but I can't see any suspend/resume attempt in your kernel log. Would you be able to try again, and annotate the start of suspend in your log?

Thanks in advance.

[elele (elele-deactivatedaccount)]

Chris,

I did a dozen suspend / resume / reboot cycles, but nothing got written to the kernel log. It appears that suspend information is dumped to kern.log only when resuming from suspend mode (it's the same with hibernate, which btw. works fine). And since the system freezes immediately after resume, this never happens and all the information is lost.

Any other ideas I could try? Debugging kernel problems is a bit out of my league, so all help is highly appreciated.

[Chris Coulson (chrisccoulson)]

Ok, could you try suspending and resuming from the console. Switch to TTY1 (CTRL+ALT+F1) and run the following:

sudo su
echo 8 > /proc/sys/kernel/printk
pm-suspend

When you resume the machine, what do you see on the screen? Could you take a photograph?

Thanks

[elele (elele-deactivatedaccount)]

Alright, here's what I got. It's not much but at least it's something. A digital camera proved very useful since these messages appeared just before the system entered suspend state. And when resuming from suspend the screen stays completely black.

[ 143.345342] PM: Syncing filesystems ... done.
[ 143.346184] PM: Preparing system for mem sleep
[ 143.347238] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 143.348487] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 143.348748] PM: Entering mem sleep
[ 143.348799] Suspending console(s) (use no_console_suspend to debug)

Also here are the contents of /var/log/pm-suspend.log in case it is usefull:

Initial commandline parameters: --quirk-none
Thu Oct 9 23:31:45 EEST 2008: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00clear suspend: success.
/usr/lib/pm-utils/sleep.d/05led suspend: not applicable.
/usr/lib/pm-utils/sleep.d/10NetworkManager suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend: not applicable.
/usr/lib/pm-utils/sleep.d/50modules suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90clock suspend: success.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend: success.
/usr/lib/pm-utils/sleep.d/95anacron suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend: not applicable.
/usr/lib/pm-utils/sleep.d/96laptop-mode suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend: success.
Thu Oct 9 23:31:47 EEST 2008: performing suspend

Hope this helps.

[Chris Coulson (chrisccoulson)]

Thanks, but there isn't much useful information there. Could you try booting with the 'no_console_suspend' option, and then attempting suspend/resume again, as described above (with a digital photograph of anything that appears on the screen). To boot with this option, press [ESC] when Grub loads, then press [E], select the line beginning 'kernel' with your arrow keys, press [E] to edit, add 'no_console_suspend' to the end of the line, press [RETURN] and then [B] to boot.

Thanks

[elele (elele-deactivatedaccount)]

I did a fresh install of Intrepid final 64-bit and tried the no_console_suspend boot option. Here are the results:

[ 87.922074] PM: Syncing filesystems ... done.
[ 87.922763] PM: Preparing system for mem sleep
[ 87.923755] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 87.924956] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 87.925210] PM: Entering mem sleep
[ 87.926296] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 88.099034] sd 0:0:0:0: [sda] stopping disk
[ 89.589225] parport_pc 00:08 disabled
[ 89.605093] ACPI handle has no context!
[ 89.605156] sdhci-pci 0000:00:0a.2: PCI INT C disabled
[ 89.605210] ACPI handle has no context!
[ 89.640065] eth1: Going into suspend...
[ 89.640280] ipw2200 0000:00:09.0: PCI INT A disabled
[ 89.656050] ehci_hcd 0000:00:03.3: PCI INT D disabled
[ 89.672042] ohci_hcd 0000:00:03.2: PCI INT C disabled
[ 89.672114] ohci_hcd 0000:00:03.1: PCI INT B disabled
[ 89.672185] ohci_hcd 0000:00:03.0: PCI INT A disabled
[ 89.672409] Intel ICH 0000:00:02.7: PCI INT C disabled
[ 89.688244] PM: suspend devices took 1.764 seconds
[ 89.688439] ACPI: Preparing to enter system sleep state S3

These messages appeared just before the system entered sleep state. When resuming from suspend the computer still completely locks up. Nothing works - the LCD backlight is off, there is no signal to external monitor, no power to USB devices, no network connection, no hard disc activity, no keyboard response, nothing. Only signs of life are spinning system fan and lit power led.

I also installed Intrepid final 32-bit on my test partition and suspend to mem works fine there. So whatever is causing this problem, it seems to be 64-bit only.

[Zohar (zohar)]

I have the same exact issue with Asus A8sc.
On top of that, when an external monitor is attached at boot time, the computer freezes. I wouldn't mention that here normally, as it seems as another issue, but it makes me think it's part of the same problem - maybe something with X not functioning well.

[Thomas Winteler (Win-Soft) (thomi)]

hi all

i have exact same problem.. if i do the command (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279156/comments/9) i don't see anything, black screen.. need to hard poweroff my notebook.

My NOtebook: ASUS VX2

uname -a
Linux hercules 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Thomas Winteler (Win-Soft) (thomi)]

more informatio about my notebook
https://wiki.ubuntu.com/LaptopTestingTeam/AsusVX2

[supernova_hq (supernova-hq)]

I am also experiencing these issues with suspend.
This is a serious issue for me (along with the broken volume buttons).

If this isn't fixed in the next 2 weeks, I am downgrading back to hardy!

[Chris Coulson (chrisccoulson)]

Thomas - Would you mind opening a separate bug report for your problems please. Your hardware is very different Antti's, and so your problem might not be related.

Antti - Could you please try running the following in a terminal with the latest Intrepid kernel (2.6.27-10) and then attach your /var/log/kern.log:

sudo su -
sync
echo 1 > /sys/power/pm_trace
echo mem > /sys/power/state

Thanks

[Thomas Winteler (Win-Soft) (thomi)]

Hey Chris

Done :)

https://bugs.launchpad.net/bugs/304291

cheers
thomi

[supernova_hq (supernova-hq)]

Open your sources, enable "Proposed", then run the updater and get 2.6.27-10
This update fixed my suspend (YEEEAAAAY).

Note: using the command line does not work (packages ... held back), you must do it via the GUI updater.

Hope this helps other people.
Now if I can only fix the volume button rapid-fire problem...

[Chris Coulson (chrisccoulson)]

Yes, 2.6.27-10 is a pretty significant stable-update, which is why I suggested to run it, as it contains some changes which may improve suspend/resume issues for some people.

[elele (elele-deactivatedaccount)]

Yes indeed!

I installed kernel 2.6.27-10 from the intrepid-proposed repository and suspend is working again on my Asus A6Km. Thank you so much Chris and everyone for your kind help and wonderful work!

If anyone doesn't object, this bug can now be marked as resolved.

[Vince (vkhannon-gmail)]

It still exists in the 64-bit version of 2.6.27-11 on my Latitude D630 (NVidia). Same exact symptoms, clean install, except for the use of the NVidia 177 (tried 173) drivers. It sounds from what I'm reading here that the system doesn't even get to the point where the video driver would matter much, though. :-( My Inspiron 1525 (Intel chipset) has the same setup as my Latitude, but suspend works fine. I'm certainly not an expert at these kinds of things, but my thoughts were to offer whatever I could.

[supernova_hq (supernova-hq)]

Are you sure you are using that kernel version?
try:
uname -r
to see you current version.

The reason I ask is that I am running 64 bit and 2.6.27-10 worked fine (and all subsequent versions).

[Thomas Winteler (Win-Soft) (thomi)]

Just one little information.

If i put my Notebook over the function keyboard shortcut Fn+F1 into suspend mode, i can't get it back.. black screen after resume. But if i do the same over guidance-powermanager (right click and suspend) it works fine.

I don't know whats the different of this two methods.

greetings
thomi