Edgy: Suspend to RAM doesn't resume on Toshiba Tecra M3

[Brad]

I've done a fresh install of Edgy (final build) on my Toshiba Tecra M3. The system does not resume from Suspend to Ram. It appears to resume from Hibernate the couple of times that I tried.

Very occasionally it will show me the lock screen, but afterwards I cannot use anything that tries to use the disk.

This is a SATA system. I've seen some rumblings about suspend and SATA, but it looks like they were fixed in previous kernel versions.

I'm almost certain that the resume problem is SATA related, but don't know where to begin to collect data.

[Timothy Smith (tas50)]

Can you attach the output of lspci

[Brad (brad-lackey)]

Here is the output of lspci:

00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV43 [Geforce Go 6600TE/6200TE] (rev a2)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15)
05:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
05:0b.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
05:0b.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
05:0b.4 Class 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller

[sedd (sedillard)]

May be a duplicate of this

https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/63840

I have similar problems with an hp nw9440. Suspend almost works, except that the sata hard drive doesn't come back. If I fidget around with ctrl-alt-fkeys I can get back into X, and anything that's cached (menus, etc) works fine, but running new apps just freezes. If I leave it alone when resuming, it will sit there for a while, throw out some meaningless kernel messages, then it will really start to complain about ata and IO block device errors and it will try to switch the drive to read-only and that will fail. I don't have the exact errors, but they are definitely sata related.

[sedd (sedillard)]

Ok I wrote down the exact errors:

First it says "ata1: failed to set xfer mode (err mask=0x4)" when it resumes.

Then, when I try to do something (for instance, switch to vt1 and try to login) it gives a lot these errors:

"Buffer I/O error on device sda1 ... " and gives a specific block.
Then it the ext3 layer throws some kind of journal-commit error, and there are some more various errors at higher-level drivers, but I think the main error is the "failed to set xfer mode" error.

[Brad (brad-lackey)]

I see these exact same errors in the messages file. Basically, the resume code doesn't reset the SATA hardware, so we are getting these device errors when reading or writing to the HD.

I don't think that it's a dup of https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/63840
but hay be related.

Mine suspends completely, but does not resume.

[Peter Whittaker (pwwnow)]

Marked as confirmed based on Brad and Sedd seeing same error messages.

[Peter Whittaker (pwwnow)]

To assist with this bug report, could the various folks who've seen it (Brad, sedd, Saulius) attach to the bug report the output of the following commands:

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please and thank you!

It would also be helpful if everyone could try to hibernate/suspend and after that fails, restart their system and attach /var/log/kern.log.0 as well.

[Brad (brad-lackey)]

Here you go....

uname -a

Linux bhlackey 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux

I have also attached the other requested output to this message

[Saulius Menkevičius (saulius-menkevicius)]

here is mine

[Michael Nelson (michael.nelson)]

Hi! I've got the same issue on a Toshiba A120. I've attached the info requested for my system.

[EsbenMoseHansen (kde-mosehansen)]

Same problem on a Toshiba A120. Anything else we can do to help? For suspend, it doesn't even appear to get to the turn off state. For hibernate, it seems that it is the usual, tricky and very last part of hibernate that goes wrong.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Sergio Zanchetta (primes2h)]

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.

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.

[Leann Ogasawara (leannogasawara)]

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)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

[Michael Nelson (michael.nelson)]

For what it's worth, I've got it on my list of TODOs when I install Ibex to check the suspend on my Toshiba A120 above..., but I don't know that the issue I experienced was related to Brad and Sedd's original (theirs seemed to be SATA related).

[EsbenMoseHansen (kde-mosehansen)]

I just found out today that suspend-to-ram works on Debian unstable, so there is hope.

[Launchpad Janitor (janitor)]

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.