after sleep+resume I can't restart the system

Bug #29695 reported by Nicolò Chieffo on 2006-01-25
42
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Expired
Medium
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Low
Unassigned
linux-source-2.6.17 (Ubuntu)
Low
Unassigned
linux-source-2.6.20 (Ubuntu)
Low
Unassigned

Bug Description

hello, I've noticed that my laptop (asus m6ne) after a suspend-to-ram + resume cycle is no more able to reboot... it hangs at the end of the progress after

Will now reboot
[4296094.430000] Restarting System

Nicolò Chieffo (yelo3) wrote :

again with this dapper flight 4 release I have this bug!!

Nicolò Chieffo (yelo3) wrote :

bug still confirmed, but now I can't see the messages, I think because of the splash screen...

Ben Collins (ben-collins) wrote :

Try booting with the reboot=h command line option, and see if that resolves things. If it does, please attach the output of "sudo dmidecode > dmi.txt".

Changed in linux-source-2.6.15:
status: Unconfirmed → Needs Info
Nicolò Chieffo (yelo3) wrote :

dear Ben, have you any ideas of why is this happening? I'm ready to help you as better as I can!

Nicolò Chieffo (yelo3) wrote :

are there any other reboot=? to try?

Running dapper. I boot to gnome, suspend, and get a blank screen on resume. I've added vga=normal to my kernel args. Resume worked once after that, but on a second suspend I get the same symptoms.

I'll try the reboot=h as a kernel arg tonight also.

I'm pretty keen to resolve this- suspend resume is a must have on a laptop. There is an old forum on m6n s3 issues here, which suggests a workaround.

http://m6n.ath.cx/forum/viewtopic.php?t=408

I haven't worked out yet whether it applies to dapper or not, or if it is the same issue. I'm still trying to work out what scripts clicking suspend in gnome kicks off.

I'm going to spend the weekend trying to sort this out. Any help appeciated.

John Cranney (john-cranney) wrote :

I've been playing with this all day. I started off with a clean dapper install. "out of the box" the laptop suspends OK. However on resume screen is blank, consoles are not available, and machine does not respond to pings.

I have tried the following:

Added vga=normal to kernel args (no change)
Removed splash from kernel args (no change)
In /etc/default/acpi-support, changed acpi_sleep=mem to acpi_sleep=stanbdy (machine does not suspend)
In /etc/default/acpi-support, commented out POST_VIDEO=true (no change)
In /etc/default/acpi-support, uncommented ACPI_SLEEP=TRUE (no change)
In /etc/default/acpi-support, uncommented save_video_pcistate (no change)
In /etc/default/acpi-support, commented oiut USE_DPMS=true (no change)
In /etc/default/acpi-support, uncommented disable_dms=true (no change)
In /etc/default/acpi-support, uncommented reset_drive=true (no change)
Added reboot=h to kernel args (no change)
Added noapic to kernel args (no change)
Added noalpic to kernel args (no change)
Added acpi_sleep=s3_mode to kernel args (no change)
Added acpi_sleep=s3_bios to kernel args. This definitely changes something- I get "inu" in yellow in the top left of the screen, then I get some messages saying "hbd: drive not ready for command". Console are available but do not respond to enter key. Occasionally when I resume using this option the desktop comes back OK, but it normally freezes after the second suspend.

Can I get some help with this please? I'm kinda just trying stuff without really understanding what I'm doing :) Can anyone suggest other things to try?

I have output of
sudo dmidecode > dmi.txt
dmesg >dmesg.txt
lspci -vn > lspcivn.txt
lspci -vvn > lspcivvn.txt

if anyone wants to take a look- just email me. I know this laptop will suspend OK because I had it working under slackware.

Help please!

John Cranney (john-cranney) wrote :

I got suspend to work. Upgraded BIOS to latest version (214a for m6n), added acpi_sleep=s3_bios to kernel args, works like a charm, even with ati driver.

Will confirm with Nicolò if it works for him.

well, in my case suspend works with no problems (I mean without any
kernel parameter) except the reboot problem (ths bug entry), and the
hibernate-after-suspend problem, which you can see here
https://launchpad.net/malone/38423

Simon Law (sfllaw) wrote :

Nicolò, you added linux-source-2.6.17. Does this also affect Edgy fo ryou?

Changed in linux-source-2.6.17:
assignee: nobody → sfllaw
status: Unconfirmed → Needs Info
Nicolò Chieffo (yelo3) wrote :

yes I'm using edgy right now!

Simon Law (sfllaw) wrote :

Please attach the output of:

sudo dmidecode > dmi.txt
dmesg >dmesg.txt
lspci -vn > lspcivn.txt
lspci -vvn > lspcivvn.txt

to this bug. Thanks!

Changed in linux-source-2.6.15:
status: Needs Info → Rejected
Nicolò Chieffo (yelo3) wrote :

here you are

Nicolò Chieffo (yelo3) wrote :
Nicolò Chieffo (yelo3) wrote :
Nicolò Chieffo (yelo3) wrote :
Simon Law (sfllaw) on 2006-08-31
Changed in linux-source-2.6.17:
assignee: sfllaw → nobody
status: Needs Info → Confirmed
Changed in linux:
status: Unknown → Confirmed
Nicolò Chieffo (yelo3) wrote :

May I do anything else to identify this bug?

Nicolò Chieffo (yelo3) wrote :

This but is issuing Feisty too!

Changed in linux-source-2.6.17:
importance: Undecided → Medium
Changed in linux-source-2.6.19:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Ben Collins (ben-collins) wrote :

Please retest against 2.6.20-2 when it is available in the feisty archive.

Changed in linux-source-2.6.19:
status: Confirmed → Needs Info
Nicolò Chieffo (yelo3) wrote :

2.6.20-1 has the same issue. I will wait for the version you told.

Ben Collins (ben-collins) wrote :

Ping. Latest version 2.6.20-3 is in the archive. Please test using this.

Nicolò Chieffo (yelo3) wrote :

still no luck. Oh, and that kernel hangs my pc immediately after the
graphical login. I had to do everything from the console!!!

P.S. the upstream bug seems a bit interested by this bug. I 'm helping
there too.

Nicolò Chieffo (yelo3) wrote :

again no luck in 2.6.20-5.
Ben, is there a way to display additional debugging infos in the kernel, so that I might see a more specific error before the hang?

Changed in linux-source-2.6.15:
status: Rejected → Needs Info
Ben Collins (ben-collins) wrote :

Mainly, letting it hang in console mode so you can see any output from the kernel.

Also, when it hangs, give it a few minutes to see if the kernel says anything, and also try some of the tips at:

https://wiki.ubuntu.com/DebuggingSystemCrash

Nicolò Chieffo (yelo3) wrote :

of course I did everything using the single user mode, to get rid of
usplash. the only thing I can visualize is that [123123.1232]
Rebooting system. Even the tricks in the site could not help me.

This occures on Asus V6J + Edgy too.

I can't risk testing Feisty, since the computer holds essential work data.

Tim Gardner (timg-tpi) on 2007-02-21
Changed in linux-source-2.6.15:
assignee: nobody → timg-tpi
Changed in linux-source-2.6.17:
assignee: nobody → timg-tpi
Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
Tim Gardner (timg-tpi) wrote :

Try booting the latest Herd4 i386 ISO: http://cdimage.ubuntu.com/daily-live/current/feisty-desktop-i386.iso

Then follow the suggestions in https://wiki.ubuntu.com/KernelSuspendDebugging. This might tell us what device driver is causing your suspend problem.

Nicolò Chieffo (yelo3) wrote :

Dear Tim. you told me to use the herd4 daily cd image. Do I have to
install it or should I just follow the instructions from the live cd?
is it the same if I use an updated feisty?

Tim Gardner (timg-tpi) wrote :

You shouldn't have to install the daily, though if you already have Feisty installed you can just run a Synaptic Package Manager update. Alternatively, just boot the live CD, open a terminal and login as root: 'sudo su -'.

Then execute the suspend debug suggestions at
https://wiki.ubuntu.com/KernelSuspendDebugging

Upon rebooting the live CD, use /tmp to capture dmesg output which you can then attach to this launchpad bug.

Nicolò Chieffo (yelo3) wrote :

thank you. I will use my feisty install and post the results!

Nicolò Chieffo (yelo3) wrote :

I followed the procedure but didn't find any other
"hash matches"

I couldn't do the exact procedure since the system was crashing at resume time.
so I did

sync; echo 1 > /sys/power/pm_trace
then I selected susped from the gnome logout menu.

Tim Gardner (timg-tpi) wrote :

Unfortunately, this trace doesn't give me enough information. The pm_trace method is not always 100% effective.

Can you try the daily build which has a recently updated kernel (2.6.20-9)?
http://cdimage.ubuntu.com/daily-live/current/feisty-desktop-i386.iso

Alternatively, you can perform a Feisty update using Synaptic which will pull all recent updates including this kernel.

Nicolò Chieffo (yelo3) wrote :

I had to manually install the newer kernel because the metapackage linux-image-generic does not perform kernel upgrades.... anyway here's the dmesg! I've run everything from the "rescue mode" grub option

Nicolò Chieffo (yelo3) wrote :

Dear Tim, here you are the dmesg using 2.6.20-11. Tell me if you need anything else, please!

Tim Gardner (timg-tpi) wrote :

This appears to be a video resume bug and is not going to get fixed for Feisty. The upstream kernel guys are still working out some suspend/resume issues.

Changed in linux-source-2.6.20:
importance: Medium → Low
assignee: timg-tpi → ubuntu-kernel-acpi
status: Needs Info → Confirmed
Changed in linux-source-2.6.17:
assignee: timg-tpi → ubuntu-kernel-acpi
importance: Medium → Low
Changed in linux-source-2.6.15:
assignee: timg-tpi → ubuntu-kernel-acpi
importance: Medium → Low
Nicolò Chieffo (yelo3) wrote :

All right, I will wait! please tell me when should I do some other tests

Changed in linux:
status: Confirmed → Incomplete
Rebel (rebel-s) wrote :

I'm also affected by this annoying bug since few versions. Now, with Gutsy it is still not solved with the 2.6.22 kernel. What are the last news about it ?

Nicolò Chieffo (yelo3) wrote :

Upstream submitted 2 patches, but I'm don't know how to apply them to
the linux kernel.

Rebel (rebel-s) wrote :

Where can we find them ? I would be pleased to try in order to help resolving this bug which is present in our favorite dist for too long !! :)

Nicolò Chieffo (yelo3) wrote :

try here http://bugzilla.kernel.org/show_bug.cgi?id=6655#c8 look
around a bit and try the patches!

Rebel (rebel-s) wrote :

Ok...I'm compiling the new kernel with modified code, just to see if it helps...results in a few minutes, when the new kernel is ready to start ! ;)

Rebel (rebel-s) wrote :

In fact, it's too late for now, I have no time to compile the new kernel, I'm gonna search for another easier solution, and maybe try to compile the modified kernel tomorrow !

Nicolò Chieffo (yelo3) wrote :

Have you tried it?

Rebel (rebel-s) wrote :

Not for the moment ! :'( I had space problem...I'm gonna try again this evening as I deleted some old files ! ;)

Rebel (rebel-s) wrote :

I have tried to apply the "working patch" on my kernel, but when I restarted, I got a Kernel Panic...I think the initrd is not good for the "home-compiled" kernel...Moreover, the compilation was sooooooooo long on my laptop...I had no force to try again for today...I wish a simple working solution would exist !

Changed in linux:
status: Incomplete → Confirmed
Rebel (rebel-s) wrote :

Any news about it ?

Rebel (rebel-s) wrote :

I have found the solution !!!

In fact, I force the ACPI_OS_NAME to "Windows 2001" just to activate the same functions as in Windows. And now, that works like a charm. Would you please try the workaround ? It's easy, you just have to add

acpi_os_name="Windows 2001"

at the end of the line concerning your kernel in the menu.lst from /boot/grub/menu.lst.

Nicolò Chieffo (yelo3) wrote :

unfortunately this did not help my asus M6800Ne.

Rebel (rebel-s) wrote :

With acpi_os_name="Microsoft Windows NT" acpi_osi="Windows 2001" ? This one works for me too, but it seems to be more respectful with standards.

Could you send your DSDT tables ?

cat /proc/acpi/dsdt > dsdt
and send the dsdt file here ! ;)

Nicolò Chieffo (yelo3) wrote :

I will try. I also have the "nolapic" boot parameter (that prevent the
system to hang when pressing fn+f7). Might this option interfer?

Rebel (rebel-s) wrote :

Arf...no in fact you're right ! That doesn't work...I'm quite dumb, as I tested with Suspend-to-disk and not Suspend-to-ram...
I've just tested again and that's not OK. Damn, I was really confident...

I'll continue searching !

Rebel (rebel-s) wrote :

To be sure that it is a general problem concerning the kernel I have just tried with Knoppix 5.1 and the result is exactly the same...I can't understand what is wrong with this computer !!!

Changed in linux:
status: Confirmed → Incomplete
xor2003 (xorrezerv2) wrote :

I think this bug is related to proprietary drivers for ATI video card. Try builtin opensource or newer proprietary. I think it's work for me.

Nicolò Chieffo (yelo3) wrote :

I don't have proprietary drivers installed

xor2003 (xorrezerv2) wrote :

ATI proprietary drivers don't support SLUB. Try this dpkg -l | grep xorg-driver-fglrx

Nicolò Chieffo (yelo3) wrote :

I don't have this driver installed

Kaur Männamaa (kaurman) wrote :

Hi!

I don't think that this bug has something to do with ati drivers as I am using an intel mobile graphics controller and do suffer from the current bug.

gombi (capolihux) wrote :

I don't think there is anything to do with Ati because I have intel integrated chipset and still not works.

Rebel (rebel-s) wrote :

I only have the open source driver too. I don't use the proprietary one ! :(

Changed in linux:
status: Incomplete → In Progress
Changed in linux:
status: In Progress → Incomplete
Changed in linux:
status: Incomplete → In Progress
Changed in linux:
status: In Progress → Incomplete
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux:
status: Incomplete → Invalid
am28111 (am28111) wrote :

I still have this problem with Hardy Heron. I will continue to research this until I can find a solution.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Ralph Janke (txwikinger) on 2008-10-08
Changed in linux:
status: Incomplete → Won't Fix
Sandro Mani (sandromani) wrote :

Bug still present in kernel 2.6.27.7 (intrepid).

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. However, this will remain open against the actively developed kernel. Thanks.

Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux:
status: Won't Fix → New

Additionally, it doesn't seem this qualifies for a Dapper SRU - https://wiki.ubuntu.com/StableReleaseUpdates so closing the 2.6.15 task as well.

Changed in linux-source-2.6.15:
status: Incomplete → Won't Fix
Gergely Csépány (cheoppy) wrote :

Running Hardy, with kernel 2.6.24-21.43 and this problem is still present. (I'm not planning to switch to Intrepid soon, since hardy is a LTS release.)
How may I help fixing this bug? I can give you logs, dmidecode, lspci outputs, etc, but which one is useful?

Amit Kucheria (amitk) wrote :

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . Let us know your results. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
CallMeKT (us5turners) wrote :

I am running the 9.04 Jaunty release on a desktop machine. I have scanned through the above comments and it seems to be the same issue I am having. When I leave the computer and allow it to sleep/hibernate, it will not restart. It will act like it is restarting but nothing ever comes up. The monitor never even wakes up but the processor runs and it tries to read the CD/DVD drives. Never makes it past that. I have to shut it down (holding the power button in) and unplug it for the machine to boot back up as normal. I am running a dual boot system on the desktop with Ubuntu 9.04 and Windows Vista Business. Thanks.

KT

Boniek (boniek12p) wrote :

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Lucid Lynx 10.04 release - http://cdimage.ubuntu.com/releases/lucid/alpha-2/. If the issue remains in Lucid, please test the latest 2.6.32 upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . Let us know your results. Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux:
status: Invalid → Expired
Changed in linux:
importance: Unknown → Medium
Curtis Hovey (sinzui) on 2012-04-09
Changed in linux-source-2.6.15 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
Changed in linux-source-2.6.17 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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