Suspend fail on 780G/SB700 due to usb error

Bug #255607 reported by gobble
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Hi

this is on 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

[ 710.516027] PM: Preparing system for mem sleep
[ 710.516029] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 710.516534] Freezing remaining freezable tasks ... (elapsed 0.09 seconds) done.
[ 710.612058] PM: Entering mem sleep
[ 710.612059] Suspending console(s)
[ 710.612089] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[ 710.612252] sd 4:0:0:0: [sdb] Stopping disk
[ 711.078923] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 711.078972] sd 2:0:0:0: [sda] Stopping disk
[ 711.094448] hub 1-2.1:1.0: suspend error -16
[ 711.094450] suspend_device(): usb_suspend+0x0/0x30 [usbcore]() returns -16
[ 711.094480] Could not suspend device 1-2.1: error -16
[ 711.150746] sd 2:0:0:0: [sda] Starting disk
[ 711.875707] sd 4:0:0:0: [sdb] Starting disk
[ 714.202728] Some devices failed to suspend
[ 714.203067] PM: Finishing wakeup.
[ 714.203068] Restarting tasks ... done.
[ 714.302269] r8169 Gigabit Ethernet driver 2.2LK loaded
[ 714.302295] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 16
[ 714.302311] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 714.302770] eth0: RTL8168c/8111c at 0xf8e5e000, 00:1f:d0:56:bd:8b, XID 3c4000c0 IRQ 222
[ 714.316580] r8169: eth0: link down
[ 714.316870] r8169: eth0: link down
[ 714.317669] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 715.940098] r8169: eth0: link up
[ 715.941238] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

dpkg -s linux-ubuntu-modules-$(uname -r)
Package: linux-ubuntu-modules-2.6.24-19-generic
Status: install ok installed
Priority: optional
Section: base
Installed-Size: 15280
Maintainer: Ubuntu Kernel Team <email address hidden>
Architecture: i386
Source: linux-ubuntu-modules-2.6.24
Version: 2.6.24-19.28
Provides: ndiswrapper-modules-1.9
Depends: linux-image-2.6.24-19-generic
Pre-Depends: dpkg (>= 1.10.24)
Description: Ubuntu supplied Linux modules for version 2.6.24 on x86/x86_64
 This package contains modules supplied by Ubuntu for Linux kernel 2.6.24 on
 x86/x86_64.

attaching dmesg.0 and lspci output.

Tags: cft-2.6.27
Revision history for this message
gobble (gobbledegeek) wrote :
Revision history for this message
gobble (gobbledegeek) wrote :

Note: device referred to by 1-2.1:1.0 is not used on my system to my knowledge on any of the physical ports.

TIA

Revision history for this message
gobble (gobbledegeek) wrote :

Note: I was able to suspend after : sudo modprobe -r ehci_hcd

So the problem lies here somewhere.

TIA

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux the kernel package in Launchpad.

Revision history for this message
Nick Ellery (nick.ellery) wrote :

Thanks for your report. Confirming, as the necessary debugging files have been attached.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Low
status: New → Triaged
Revision history for this message
TJ (tj) wrote :

I suspect this could be related to bug #212660 "ehci-hcd causes failed suspends on kernel 2.6.24" for which a work-around is:

echo 'SUSPEND_MODULES="ehci-hcd"' | sudo tee /etc/pm/config.d/modules_unload

If possible please try this work-around and report progress to bug #212660 if successful.

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
Ralph Janke (txwikinger) wrote :

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

Changed in linux:
status: Triaged → Incomplete
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.

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

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

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