Hi,
As many people I'm having troubles with resuming from suspend. As I didn't find an existing bug report with the exact same symptoms I opened this one. So here it goes.
The laptop goes into stanby mode with no problem: screen is turned off, and after a few seconds the power led starts to repeatedly fade in/out, indicating that the machine is suspended.
The problem is when trying to resume. Sometimes it works perfectly fine, sometimes it doesn't. I've never been able to successfully suspend and resume more than twice, ie. it always fail to resume the third time, or sometimes the second or first time.
When it fails to resume, the symptoms are the following: a few seconds after I press the power on switch, the HDD led turns on for a fraction of a second, then off for a fraction of a second, and then turns on indefinitely. In this situation, the computer is responsive while I don't try to access the disk. Sometimes X even shows up and everything works fine until an application tries to access the HDD (at which point the app freezes but other apps are still responsive). Sometimes X doesn't show up but pressing the caps lock key turns on and off the caps led.
I have an ATI Mobility X600 card and I'm using the fglrx driver installed from the Dapper repository. But as X sometimes shows up on failed resumes, it seems fglrx has nothing to do here. Moreoever I also tried to suspend resume with kdm turned off, the results are the same.
I tried with almost every imagineable combination of settings in acpi-support, but the results are almost always the same. The only notable difference is that when I set ACPI_SLEEP_MODE to standby instead of mem, it fails to suspend, but then the computer is usable again. I get this error "eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full."
The error shows up briefly on the screen, and appears in dmesg. Note that eth1 is a wireless card using the ipw2200 driver.
Now, I noticed that with the usual sleep mode (mem), I sometimes see the same error on the screen. Resume never worked properly after this error showed up, but it also sometimes fails to work without me seeing this error.
What could I do to help hunt down the problem?
Regards,
g
Great news, suspend/resume is much more stable with the newly uploaded kernel (2.6.15-21-686).
Up to now I only experienced one failure out of a dozen attempts, once I commented out DISABLE_DMA=true and RESET_DRIVE=true.
In the failed attempt the symptoms were a bit different than those described in the original description: X showed up, apps were responsive, but HDD accesses throwed errors instead of freezing.
However, I loose the mouse wheel on resume. I have to unplug/replug the usb connector to get it back.
Thanks for the good work!!