usbdev4.1_ep00: PM: suspend 0->1, parent usb4 already 2

Bug #78634 reported by Matt Zimmerman
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

When hibernating or suspending my laptop (ThinkPad T42, Feisty), I see messages like this:

[ 5026.180000] usbdev4.1_ep81: PM: suspend 0->2, parent 4-0:1.0 already 2
[ 5026.180000] hub 4-0:1.0: PM: suspend 2->2, parent usb4 already 2
[ 5026.180000] usbdev4.1_ep00: PM: suspend 0->2, parent usb4 already 2
[ 5026.180000] usbdev3.1_ep81: PM: suspend 0->2, parent 3-0:1.0 already 2
[ 5026.180000] hub 3-0:1.0: PM: suspend 2->2, parent usb3 already 2
[ 5026.180000] usbdev3.1_ep00: PM: suspend 0->2, parent usb3 already 2
[ 5026.180000] usbdev2.1_ep81: PM: suspend 0->2, parent 2-0:1.0 already 2
[ 5026.180000] hub 2-0:1.0: PM: suspend 2->2, parent usb2 already 2
[ 5026.180000] usbdev2.1_ep00: PM: suspend 0->2, parent usb2 already 2
[ 5026.180000] usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
[ 5026.180000] hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
[ 5026.180000] usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2

and when resuming:

[ 5031.932000] usbdev4.1_ep00: PM: resume from 0, parent usb4 still 2
[ 5031.932000] usbdev4.1_ep81: PM: resume from 0, parent 4-0:1.0 still 2

The system has no external USB devices connected at present, and I didn't see these messages under earlier kernels. Apart from the messages, the system seems to resume OK.

Revision history for this message
Matt Zimmerman (mdz) wrote :
Download full text (11.2 KiB)

Upon trying to use a USB device on this system (a DVD writer), it has become apparent that there are further problems. Even on a clean boot where no suspend/resume has taken place, the device doesn't work properly:

[ 84.432000] usb 4-4: new high speed USB device using ehci_hcd and address 122
[ 84.692000] ehci_hcd 0000:00:1d.7: port 4 reset error -110
[ 84.692000] hub 4-0:1.0: hub_port_status failed (err = -32)
[ 89.028000] usb 4-4: new high speed USB device using ehci_hcd and address 124
[ 92.052000] usb 4-4: new high speed USB device using ehci_hcd and address 9
[ 92.312000] ehci_hcd 0000:00:1d.7: port 4 reset error -110
[ 92.312000] hub 4-0:1.0: hub_port_status failed (err = -32)
[ 97.404000] usb 4-4: new high speed USB device using ehci_hcd and address 14
[ 98.412000] usb 4-4: new high speed USB device using ehci_hcd and address 17
[ 107.988000] usb 4-4: new high speed USB device using ehci_hcd and address 54
[ 108.744000] usb 4-4: new high speed USB device using ehci_hcd and address 56
[ 110.256000] usb 4-4: new high speed USB device using ehci_hcd and address 61
[ 113.532000] usb 4-4: new high speed USB device using ehci_hcd and address 73
[ 113.792000] ehci_hcd 0000:00:1d.7: port 4 reset error -110
[ 113.792000] hub 4-0:1.0: hub_port_status failed (err = -32)
[ 120.144000] usb 4-4: new high speed USB device using ehci_hcd and address 83
[ 120.900000] usb 4-4: new high speed USB device using ehci_hcd and address 85
[ 123.168000] usb 4-4: new high speed USB device using ehci_hcd and address 93
[ 124.176000] usb 4-4: new high speed USB device using ehci_hcd and address 96
[ 126.192000] usb 4-4: new high speed USB device using ehci_hcd and address 103
[ 126.452000] ehci_hcd 0000:00:1d.7: port 4 reset error -110
[ 126.452000] hub 4-0:1.0: hub_port_status failed (err = -32)
[ 130.536000] usb 4-4: new high speed USB device using ehci_hcd and address 104
[ 131.544000] usb 4-4: new high speed USB device using ehci_hcd and address 107
[ 138.852000] usb 4-4: new high speed USB device using ehci_hcd and address 9
[ 141.624000] usb 4-4: new high speed USB device using ehci_hcd and address 19
[ 142.632000] usb 4-4: new high speed USB device using ehci_hcd and address 22
[ 155.988000] usb 4-4: new high speed USB device using ehci_hcd and address 74
[ 157.752000] usb 4-4: new high speed USB device using ehci_hcd and address 80
[ 158.508000] usb 4-4: new high speed USB device using ehci_hcd and address 82
[ 167.076000] usb 4-4: new high speed USB device using ehci_hcd and address 115
[ 181.692000] usb 4-4: new high speed USB device using ehci_hcd and address 46
[ 183.204000] usb 4-4: new high speed USB device using ehci_hcd and address 51
[ 183.708000] usb 4-4: new high speed USB device using ehci_hcd and address 52
[ 183.968000] ehci_hcd 0000:00:1d.7: port 4 reset error -110
[ 183.968000] hub 4-0:1.0: hub_port_status failed (err = -32)
[ 190.320000] usb 4-4: new high speed USB device using ehci_hcd and address 62
[ 191.580000] usb 4-4: new high speed USB device using ehci_hcd and address 66
[ 191.840000] ehci_hcd 0000:00:1d.7: port 4 reset error -110
[ 191.840000] hub 4-0:1.0: hub_port_status failed (...

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

Can you try unloading ehci_hcd module and see if that changes anything?

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 78634] Re: usbdev4.1_ep00: PM: suspend 0->1, parent usb4 already 2

On Wed, Jan 10, 2007 at 07:42:16PM -0000, Ben Collins wrote:
> Can you try unloading ehci_hcd module and see if that changes anything?

I unloaded ehci_hcd, then did a suspend/resume cycle, and I still got the
messages.

--
 - mdz

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for reporting this bug. To make any progress with it, some more information will be needed. Please add (by commenting on the bug) to the bug report the output of the following commands: 'uname -a' 'sudo lspci -vvn' 'sudo dmidecode'. It would also be helpful if you could try to hibernate/suspend and after that fails, restart your system and attach /var/log/kern.log.0 as well. Thanks again for your contribution.

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

There's no further info needed. Basically this is just new output from the USB core for sanity checks on the pm code.

Not sure if stopping this output is ideal, but we'll try to clean it up.

Changed in linux-source-2.6.20:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
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
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Matt Zimmerman (mdz) wrote :

This went away with one upgrade or another. Now I only get over-current messages instead of these.

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