[intrepid][regression] Fujitsu Siemens Amilo 1650G fails to suspend

Bug #262594 reported by Pietro Battiston
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Intrepid by Wouter Stomp

Bug Description

I have a Fujitsu Siemens Amilo 1650 with 64 bit Hardy and Intrepid installed on it.

Under Gutsy, standby worked flawlessy (when using free graphic ati drivers instead of fglrx).

Under Hardy (I still use free graphic ati drivers), standby usually works; sometimes, instead, computer correctly goes in suspend mode but then doesn't wake up (power LED is on, fan is on but the screen doesn't come up and the system doesn't react to "Ctrl+Alt+Del" or "Ctrl+Alt+Sys+B").

Under Intrepid (still free graphic drivers), after suspend computer NEVER wakes up (same symptoms as when it doesn't under Hardy).

Though I cant' tell if the problem in Hardy and Intrepid is the same, it may be an interesting information to know that in Hardy, when the computer doesn't come up from suspend (I think it happens around one time out of 5 or 10), I can still wake it if I press many times (let's say something between 4 and 8) the power button. The system seems to load normally, and I can login, but it seems like the CPU gets stuck very easily (blocking everything, from the GUI to the clock, that becomes late) until I give some interrupt (i.e: moving the mouse); when I do, I can see with dmesg a message such

    soft lockup - CPU #1 stuck for 11s

, so system is practically unusable, and I have to shutdown it (still moving touchpad, or it will pause!).

That said, under Intrepid computer just doesn't get usable, no matter how many times I press the power button.

(Still under Intrepid) I did some testing: following the procedure given in https://wiki.ubuntu.com/DebuggingKernelSuspend, I gave the command:
    sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force
after reboot, I looked at the dmesg, but no hash was found (I'm attaching it anyway as useless_dmesg.txt, but I think it's useless).

So I tried to just manually remove any module I could remove: i gave the command:
    for i in `lsmod | sed 's# .*##'`; do rmmod $i; done
(two times, to also remove "dependencies blocking" modules). The modules left on are reported in the "modules_left_on.txt" file attached.

Finally, I tried to manually remove all removable modules, as above, and THEN give the
    sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force
command; this time, on reboot, I COULD find a pair of hash matches in dmesg:
 [ 4.188003] Magic number: 4:281:579
 [ 4.188003] mem kmem: hash matches
 [ 4.188003] pci_bus 0000:00: hash matches
so I'm reporting it as dmesg_lucky.txt.

That said, I have no idea what to do, but I can do any testing requested.

Notice that under Intrepid I'm using 2.6.27-1-generic kernel, but resume from suspend also used to fail with 2.6.26-5 (every time).

Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :

Notice that hibernation works perfectly

Revision history for this message
Pietro Battiston (toobaz) wrote :

I also noticed a strange behaviour (suspend didn't work in edgy and feisty, and occasionally doesn't under hardy, but what I'm describing had never happened before Intrepid): if I suspend the PC and then wake it up by pressing the button, as reported above, I hear the fan but the screen stays black; if I keep the power button pressed 5 seconds to reebot it, it does reboot (as can be noticed from the noise of the fan and of the CD-DVD reader), but is left in an unusable state, with screen black: I can again keep the power button pressed, and it again reboots with screen black; the only thing I can do is then unplug power cable and battery; then I just give power again, power it on and it boots up normally.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
atany (ye-gorshkov) wrote :

I also have the same issue on MSI L715 laptop under Intrepid. I had no luck getting hash match in dmesg even after uploading all removable modules. When I press power button after suspend I can hear CPU fan and HDD noise, but the screen remains black and the laptop cannot be accessed through the network (both wired and wireless). If I leave the system in this state for 15 or more seconds I can hear the CPU fan speed is increasing to its maximal value. If I press power button for 5 seconds the laptop turns off and after I turn it back on the system boots up normally (however, I have experienced occasional black screen gradually changing to gray on boot with earlier fglrx drivers under Gutsy and Hardy).

Under Hardy the suspend worked fine for me after a couple of changes to the process: I added scripts to unload wireless card (rt2500) and alsa drivers before suspend and load them back on wakeup.

Revision history for this message
Steve Beattie (sbeattie) wrote :

This bug was reported in the Intrepid development cycle; removing regression-potential and marking as regression-release.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Pietro Battiston (toobaz) wrote :

Problem was solved in Jaunty (beta 3), where suspend works flawlessy.

Changed in linux:
status: Triaged → 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.