Toshiba Laptop: Suspend and Resume fail sporadically

Bug #223930 reported by Farhad
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have a Hardy installed on my Toshiba laptop. Suspend used to work perfect with Gutsy, but now, it sometimes works and sometimes not. When it works I usually hear a couple of beeps when waking up from suspend. Sometimes after waking up I get the message "system failed to suspend". Some other times when I suspend, system halts and I just see the cursor in the empty screen. Sometimes, it suspends successfully, but it wake up, halts and I get the empty screen again. Finally, I have observed that sometimes when I suspend, after couple of seconds, it just locks the screen. I should mention that I think suspend works fine for the first time after each system restart, but I get problems suspending after the first wake up. I would appreciate it if someone could help me with these issues,

thanks,

Farhad

Revision history for this message
trollord (trollenlord) wrote :

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 requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Revision history for this message
Farhad (farhad-kh81) wrote :

Here are the files. System woke up successfully from suspend for the first time. The second time, when I suspended, it didn't work; it just locked the screen. I unlocked the screen and suspended again and it worked this time. After it woke up, I shut down the system but it halted during the shut down and I restarted the system by pressing ctl-alt-del. I had experienced system halt during the shut down couple of times before. I copied the kernel log file and acpi directory after the restart. Thank you very much.

Revision history for this message
Farhad (farhad-kh81) wrote :
Revision history for this message
Farhad (farhad-kh81) wrote :
Revision history for this message
Farhad (farhad-kh81) wrote :
Revision history for this message
Farhad (farhad-kh81) wrote :
Revision history for this message
pjfl (onl1ne) wrote :

Can I add that those two beeps that have appeared in Hardy bypass all software volume controls. Since my Thinkpad Z61m doesn't have a hardware volume control I have too keep unplugging my desktop speakers. If I forget I am rudely reminded when the cones of my speakers try to escape the cases. Too loud man, too loud

Revision history for this message
Nikolaus Rath (nikratio) wrote :

Marking as new, since the missing information has been included.

Note that the issue with the loud beeps upon resume is most likely an unrelated problem (also happens with Dell and Thinkpad laptops) and reported in bug #229936.

Changed in linux:
status: Incomplete → New
Revision history for this message
Farhad (farhad-kh81) wrote :

Well, every time I hear the beeps, I also see a error message that my computer has failed to sleep(although it has successfully gotten suspended and waken up). Thus, I thing there must be a relation. The other thing is that my computer never wakes up from the two new versions of headers (2.6.24-17-generic and 2.6.24-18-generic) therefore, I need to use 2.6.24-16 that although sometimes fails to work at least never halts. In 2.6.24-18, I can successfully suspend the computer but it never wakes up. Every time, I just see a blank screen with a cursor and computer is completely locked (even alt-sys req+ B does not work!). If you guys need any files or more information let me know.

thanks,

Farhad

Revision history for this message
Farhad (farhad-kh81) wrote :

I just installed 2.6.24-19-generic and suspend works much better than 17 and 18. I still get the beep plus the error message "your computer failed to suspend" sometimes after waking up. But it works most of the time.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Nikos Efthimiou (nikos-efthimiou) wrote :

 I am using the latest(untill now ) Ibex beta version. The bug isn't fixed.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Farhad,

Since you are the original bug reporter, would you be willing to test the latest pre-release of Jaunty (currently Alpha3) - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test suspend via a LiveCD. Please let us know if this issue remains. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Farhad (farhad-kh81) wrote :

The suspend/hibernate works now perfectly with 2.6.27 in ubuntu 8.10. The only minor bug is that randomly after resume from suspend, the networking gets disabled and I need to enable it manually. Should I cancel this bug or you still want me to test Jaunty alpha3?

thanks

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Farhad. It would seem this particular issue is fixed. I'll go ahead and close this report. However, if and when you do try Jaunty and still find that you have to manually enable netoworking after resuming, please open a new report. Thanks.

Changed in linux:
status: Incomplete → Fix Released
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.