[Bug 14256] New: ACPI suspend to ram broken on IBM T40

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Sun Aug 28 09:17:33 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14256
Ubuntu | kernel-package

           Summary: ACPI suspend to ram broken on IBM T40
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: kernel-package
        AssignedTo: ben.collins at ubuntu.com
        ReportedBy: richard.kinder at gmail.com
         QAContact: kernel-bugs at lists.ubuntu.com


Trying suspend to ram via ACPI on an IBM T40 is a bad idea. The computer
attempts to suspend, but then comes straight out of suspend and presents the
locked screen dialog. Upon unlocking the screen, the system is very unstable,
sudo no longer works, and the only way to recover is hard reboot. The following
snippet of dmesg was seen directly after 'resume' from the suspend:

[4409968.415000] airo: Unregistering eth1
[4409971.980000] Stopping tasks:
======================================================================================
[4409978.405000]  stopping tasks failed (1 tasks remaining)
[4409978.405000] Restarting tasks...<6> Strange, syslogd not stopped
[4409978.408000]  done
[4409978.638000] =<6>airo:  Probing for PCI adapters
[4409979.837000] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 11
(level, low) -> IRQ 11
[4409979.838000] airo: Found an MPI350 card
[4409980.397000] airo: MAC enabled eth1 0:2:8a:ea:33:27
[4409980.397000] airo:  Finished probing for PCI adapters
[4409981.234000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[4409981.234000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
[4409981.234000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list