Toshiba Satellite M70-CL3 doesn't resume from suspend to RAM

Bug #64927 reported by Zack Weinberg
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Declined for Feisty by Leann Ogasawara
linux-source-2.6.15 (Ubuntu)
Won't Fix
Medium
Unassigned
Declined for Feisty by Leann Ogasawara
linux-source-2.6.17 (Ubuntu)
Won't Fix
Medium
Unassigned
Declined for Feisty by Leann Ogasawara
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned
Declined for Feisty by Leann Ogasawara

Bug Description

Binary package hint: acpi

My laptop (a brand new Toshiba Satellite M70-CL3) appears to suspend to RAM correctly - screen, fan, HD turn off, and the power-on light starts blinking amber, which is what it does when suspended to RAM from Windows - but when I try to resume it, the screen backlight doesn't turn on and the keyboard is unresponsive. I have to hold down the power button until it shuts off to unwedge it.

For comparison, suspend to disk ("hibernate") works correctly.

This is the case in both Dapper and Edgy. (I'm not 100% sure it got as far as the blinking amber power light in Dapper.)

Tags: cft-2.6.27
Revision history for this message
Matthew Garrett (mjg59) wrote :

Can you describe the hardware a little more? dmesg and lspci should help.

Revision history for this message
Zack Weinberg (zackw) wrote : Re: [Bug 64927] Re: Toshiba Satellite M70-CL3 doesn't resume from suspend to RAM
Download full text (22.3 KiB)

On 10/9/06, Matthew Garrett <email address hidden> wrote:
> Can you describe the hardware a little more? dmesg and lspci should
> help.

Attached.

[17179569.184000] Linux version 2.6.17-10-generic (root@vernadsky) (gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Mon Oct 9 18:57:16 UTC 2006 (Ubuntu 2.6.17-10.29-generic)
[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000] BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
[17179569.184000] BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000c2000 - 00000000000d0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000dc000 - 00000000000e0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[17179569.184000] BIOS-e820: 0000000000100000 - 000000001be90000 (usable)
[17179569.184000] BIOS-e820: 000000001be90000 - 000000001be9c000 (ACPI data)
[17179569.184000] BIOS-e820: 000000001be9c000 - 000000001bf00000 (ACPI NVS)
[17179569.184000] BIOS-e820: 000000001bf00000 - 000000001c000000 (reserved)
[17179569.184000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[17179569.184000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[17179569.184000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[17179569.184000] 0MB HIGHMEM available.
[17179569.184000] 446MB LOWMEM available.
[17179569.184000] found SMP MP-table at 000f6720
[17179569.184000] On node 0 totalpages: 114320
[17179569.184000] DMA zone: 4096 pages, LIFO batch:0
[17179569.184000] Normal zone: 110224 pages, LIFO batch:31
[17179569.184000] DMI present.
[17179569.184000] ACPI: RSDP (v000 TOSCPL ) @ 0x000f66f0
[17179569.184000] ACPI: RSDT (v001 TOSCPL RSDT 0x06040000 LTP 0x00000000) @ 0x1be97b57
[17179569.184000] ACPI: FADT (v001 TOSCPL SB400 0x06040000 ATI 0x000f4240) @ 0x1be9bef6
[17179569.184000] ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @ 0x1be9bf6a
[17179569.184000] ACPI: MCFG (v001 PTLTD MCFG 0x06040000 LTP 0x00000000) @ 0x1be9bfc4
[17179569.184000] ACPI: DSDT (v001 TOSCPL SB400 0x06040000 MSFT 0x0100000e) @ 0x00000000
[17179569.184000] ATI board detected. Disabling timer routing over 8254.
[17179569.184000] ACPI: PM-Timer IO Port: 0x8008
[17179569.184000] ACPI: Local APIC address 0xfee00000
[17179569.184000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[17179569.184000] Processor #0 6:13 APIC version 20
[17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[17179569.184000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[17179569.184000] IOAPIC[0]: apic_id 1, version 33, address 0xfec00000, GSI 0-23
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
[17179569.184000] ACPI: IRQ0 used by override.
[17179569.184000] ACPI: IRQ2 used by override.
[17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs
[17179569.184000] Using ACPI (MADT) for SMP configuration information
[17179569.184000] Allocating PCI resources starting at 20000000 (gap: 1c000000:e2c00000)
[17179569.18400...

Changed in linux-source-2.6.17:
status: Unconfirmed → Confirmed
Revision history for this message
Stéphane Graber (stgraber) wrote :

I have quite the same issue on my laptop.
It's a Toshiba A100-193 (quite hard to find, it only existed during 2 weeks) with all the ATI chips like above.
I tried with : 2.6.15, 2.6.17 (provided by Ubuntu), my own 2.6.17 and my own 2.6.18 (vanilla for both).

I also did a fixed DSDT for my laptop (there was one ACPI suspend to ram related error in it) and make it loaded by the kernel but I still have the bug.

Bug :
-I make it to sleep
-It went to sleep correctly, I have the orange led that means it's suspended
-I try to wake it up
-I hear my DVD drive starting, but that's all, nothing else start and I have to remove my battery to be able to restart it.

I also tried with a minimal kernel (no usb, no ethernet, no video driver, ...) but I'm still not able to suspend.
Of course all the tests were done without any proprietary driver loaded.

I attach : lspci, dmesg, dsdt.hex

Ask if you want anything else.

Revision history for this message
Stéphane Graber (stgraber) wrote :
Revision history for this message
Stéphane Graber (stgraber) wrote :
Revision history for this message
Stéphane Graber (stgraber) wrote :
Revision history for this message
Stéphane Graber (stgraber) wrote :
Revision history for this message
Ben Collins (ben-collins) wrote :

Needs testing against 2.6.20

Changed in linux-source-2.6.19:
status: Unconfirmed → Needs Info
Revision history for this message
Zack Weinberg (ubuntu-bugs-zackw) wrote :

Exactly the same problem with the linux-2.6.20-3-generic package (version 2.6.20-3.4) from feisty (and everything else from today's feisty, too).

I messed around with the s2ram program from suspend.sf.net a bit (running from single-user text console, to eliminate interactions with HAL and/or X), and I couldn't find any of its -f submodes that would make the screen turn back on. More worrisome still is that after resume (both from the normal suspend button and from s2ram) the keyboard is completely unresponsive, which makes me think the kernel never quite comes back up properly :(

zw

Changed in linux-source-2.6.20:
status: Needs Info → Confirmed
Changed in linux-source-2.6.20:
importance: Undecided → Medium
Revision history for this message
Stéphane Graber (stgraber) wrote :

Confirmed with 2.6.20-6-generic on A100-193

Tim Gardner (timg-tpi)
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
Revision history for this message
Tim Gardner (timg-tpi) wrote :

I've written a short discussion about how to tackle to normal resume problems.

https://wiki.ubuntu.com/KernelSuspendDebugging

Please try these suggestions and send the output of 'dmesg'.

Revision history for this message
Stéphane Graber (stgraber) wrote :

I personally have no more this laptop and then be no more able to help giving informations or test it against new kernels.

Revision history for this message
Zack Weinberg (zackw) wrote :

On 2/26/07, Tim Gardner <email address hidden> wrote:
> I've written a short discussion about how to tackle to normal resume
> problems.
>
> https://wiki.ubuntu.com/KernelSuspendDebugging
>
> Please try these suggestions and send the output of 'dmesg'.

I have gone back to Debian for this laptop in order to get working
wireless (the madwifi in Ubuntu does not work at all with 2.6.20); I
would still like to help you debug the suspend, but the page you
linked does not exist.

zw

Revision history for this message
Ben Collins (ben-collins) wrote :

Confirmed bugs need to be assigned to ubuntu-kernel-team.

Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
Changed in linux-source-2.6.17:
assignee: timg-tpi → ubuntu-kernel-team
importance: Undecided → Medium
Changed in linux-source-2.6.15:
assignee: timg-tpi → ubuntu-kernel-team
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Dawnrazor (dawnrazor-gmx) wrote :
Download full text (23.3 KiB)

Hi

I have the same error but only every 3 times i come back from Stand-By

I have the following debug output in feisty with newest Kernel

--------------------------------------------------------------------------------------
Apr 1 16:08:28 dawn kernel: [ 9290.952000] usbhid 3-2:1.0: suspend
Apr 1 16:08:28 dawn kernel: [ 9290.952000] usb 3-2: suspend, may wakeup
Apr 1 16:08:28 dawn kernel: [ 9290.972000] platform bluetooth: suspend
Apr 1 16:08:28 dawn kernel: [ 9290.972000] platform dock.0: suspend
Apr 1 16:08:28 dawn kernel: [ 9290.972000] iTCO_wdt iTCO_wdt: suspend
Apr 1 16:08:28 dawn kernel: [ 9290.972000] sr 1:0:0:0: suspend
Apr 1 16:08:28 dawn kernel: [ 9290.972000] sd 0:0:0:0: suspend
Apr 1 16:08:28 dawn kernel: [ 9291.684000] hub 5-0:1.0: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] usb usb5: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] hub 4-0:1.0: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] usb usb4: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] hub 3-0:1.0: suspend
Apr 1 16:08:28 dawn kernel: [ 9291.684000] usb usb3: suspend, may wakeup
Apr 1 16:08:28 dawn kernel: [ 9291.684000] hub 2-0:1.0: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] usb usb2: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] hub 1-0:1.0: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] usb usb1: PM: suspend 2-->2
Apr 1 16:08:28 dawn kernel: [ 9291.684000] platform vesafb.0: suspend
Apr 1 16:08:28 dawn kernel: [ 9291.684000] platform eisa.0: suspend
Apr 1 16:08:28 dawn kernel: [ 9291.684000] i8042 i8042: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] serial8250 serial8250: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:1c.2:pcie02: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:1c.2:pcie00: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:1c.1:pcie02: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:1c.1:pcie00: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:1c.0:pcie02: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:1c.0:pcie00: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pci_express 0000:00:01.0:pcie00: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] platform pcspkr: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] i8042 aux 00:09: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] i8042 kbd 00:08: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pnp 00:07: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] system 00:06: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pnp 00:05: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] system 00:04: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pnp 00:03: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pnp 00:02: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] system 00:01: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] pnp 00:00: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.464000] e100 0000:07:08.0: suspend
Apr 1 16:08:28 dawn kernel: [ 9292.480000] sdhci 0000:07:06.3: suspend
Apr 1 16:08:28 dawn kerne...

Revision history for this message
Detlef Lechner (detlef-lechner) wrote :

This description resembles very much the kern.log of Bug #129324.

Revision history for this message
dresnu (dresnu) wrote :

I have the same issue here on a toshiba a100-912 running Kubuntu 7.10 with 2.6.22-14-generic kernel

Revision history for this message
Kazik (kkazmierczyk) wrote :

The same with Asus f2hf with Ubuntu 2.6.22-14-generic. In previosu istributions it worked.

My lspci:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
01:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

My dmesg in attachment

Revision history for this message
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.

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-source-2.6.17:
status: Confirmed → Invalid
Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.17:
status: Invalid → Won't Fix
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
Detlef Lechner (detlef-lechner) wrote :

This error does not appear any longer in kernel 2.6.24-19.

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

Thanks, I'll go ahead and mark this "Fix Released" for Hardy. Zack, since you are the original bug reporter, if this is not the case please feel to reopen this bug report by changing the status back to "New". Against 2.6.15 and 2.6.20 this will be closed as it does not qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates .

Changed in linux:
status: Incomplete → Fix Released
Changed in linux-source-2.6.15:
status: Confirmed → Won't Fix
Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
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.

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.