[Bug 20894] New: [dapper] swsuspend fails with kernel 2.6.15-7-686 on Acer TM290 while it works with 2.6.14

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Mon Dec 12 17:13:18 UTC 2005


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

           Summary: [dapper] swsuspend fails with kernel 2.6.15-7-686 on
                    Acer TM290 while it works with 2.6.14
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: linux
        AssignedTo: ben.collins at ubuntu.com
        ReportedBy: lists at wikidev.net
         QAContact: kernel-bugs at lists.ubuntu.com


After upgrading from breezy to dapper suspend (to ram or disk) stopped working
using the new 2.6.15-7-686 Kernel while it does still work when booting to a
vanilla 2.6.14 kernel.

* screen blanks as usual early in the suspend process
* when supending to disk, heavier disk activity than in 2.6.14 starts (expected
given the changes in 2.6.15)
* cd activity led switches on and keeps that way, machine never powers down
* sysrq doesn't work, only hard power cycle helps
* in the suspend-to-disk case no suspend data is picked up on the next boot

There is little logging output available, the bit in the syslog looks not
suspicious (mysql and usb modules are configured to be stopped/unloaded in
/etc/default/acpi-support):
Dec 12 17:55:05 localhost gdm[3654]: Master suspending...
Dec 12 17:55:06 localhost mysqld[4917]: 051212 17:55:06 [Note] /usr/sbin/mysqld:
Normal shutdown
Dec 12 17:55:06 localhost mysqld[4917]:
Dec 12 17:55:06 localhost mysqld[4917]: 051212 17:55:06  InnoDB: Starting
shutdown...
Dec 12 17:55:08 localhost mysqld[4917]: 051212 17:55:08  InnoDB: Shutdown
completed; log sequence number 0 43634
Dec 12 17:55:08 localhost mysqld[4917]: 051212 17:55:08 [Note] /usr/sbin/mysqld:
Shutdown complete
Dec 12 17:55:08 localhost mysqld[4917]:
Dec 12 17:55:08 localhost mysqld_safe[5110]: ended
Dec 12 17:55:09 localhost kernel: [17179741.720000] ehci_hcd 0000:00:1d.7:
remove, state 1
Dec 12 17:55:09 localhost kernel: [17179741.720000] usb usb4: USB disconnect,
address 1
Dec 12 17:55:09 localhost kernel: [17179741.724000] ehci_hcd 0000:00:1d.7: USB
bus 4 deregistered
Dec 12 17:55:09 localhost kernel: [17179741.724000] ACPI: PCI interrupt for
device 0000:00:1d.7 disabled
Dec 12 17:55:09 localhost kernel: [17179741.728000] uhci_hcd 0000:00:1d.2:
remove, state 1
Dec 12 17:55:09 localhost kernel: [17179741.728000] usb usb3: USB disconnect,
address 1
Dec 12 17:55:09 localhost kernel: [17179741.728000] uhci_hcd 0000:00:1d.2: USB
bus 3 deregistered
Dec 12 17:55:09 localhost kernel: [17179741.728000] ACPI: PCI interrupt for
device 0000:00:1d.2 disabled
Dec 12 17:55:09 localhost kernel: [17179741.728000] uhci_hcd 0000:00:1d.1:
remove, state 1
Dec 12 17:55:09 localhost kernel: [17179741.728000] usb usb2: USB disconnect,
address 1
Dec 12 17:55:09 localhost kernel: [17179741.732000] uhci_hcd 0000:00:1d.1: USB
bus 2 deregistered
Dec 12 17:55:09 localhost kernel: [17179741.732000] ACPI: PCI interrupt for
device 0000:00:1d.1 disabled
Dec 12 17:55:09 localhost kernel: [17179741.732000] uhci_hcd 0000:00:1d.0:
remove, state 1
Dec 12 17:55:09 localhost kernel: [17179741.732000] usb usb1: USB disconnect,
address 1
Dec 12 17:55:09 localhost kernel: [17179741.736000] uhci_hcd 0000:00:1d.0: USB
bus 1 deregistered
Dec 12 17:55:09 localhost kernel: [17179741.740000] ACPI: PCI interrupt for
device 0000:00:1d.0 disabled
Dec 12 17:55:09 localhost kernel: [17179741.808000] ACPI: PCI interrupt for
device 0000:02:02.0 disabled
Dec 12 17:55:09 localhost kernel: [17179741.836000] ACPI: PCI interrupt for
device 0000:02:01.0 disabled
Dec 12 17:56:53 localhost syslogd 1.4.1#17ubuntu3: restart.

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