Bug 5601 - acpi suspend regression for usb hub
acpi suspend regression for usb hub
Status: CLOSED PATCH_ALREADY_AVAILABLE
Product: Drivers
Classification: Unclassified
Component: USB
i386 Linux
: P2 normal
Assigned To: David Brownell
:
Depends on:
Blocks: USB
  Show dependency treegraph
 
Reported: 2005-11-13 08:21 UTC by Jon Sanchez
Modified: 2005-12-04 15:26 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.14 and up
Tree: Mainline
Regression: ---


Attachments
kernel messages after resume (7.03 KB, text/plain)
2005-11-13 08:23 UTC, Jon Sanchez
Details
lspic (9.30 KB, text/plain)
2005-11-13 08:24 UTC, Jon Sanchez
Details
kernel config (34.30 KB, text/plain)
2005-11-13 08:24 UTC, Jon Sanchez
Details

Description Jon Sanchez 2005-11-13 08:21:48 UTC
Most recent kernel where this bug did not occur:
Distribution: debian sarge
Hardware Environment: ibm T41
Software Environment: kernel 2.6.14.2
Problem Description: usb hub and attached devices not found after resume. it
worked perfect with 2.6.13.

Steps to reproduce:

acpi suspend and resume.
Comment 1 Jon Sanchez 2005-11-13 08:23:37 UTC
Created attachment 6554 [details]
kernel messages after resume
Comment 2 Jon Sanchez 2005-11-13 08:24:13 UTC
Created attachment 6555 [details]
lspic
Comment 3 Jon Sanchez 2005-11-13 08:24:54 UTC
Created attachment 6556 [details]
kernel config
Comment 4 David Brownell 2005-11-14 22:13:44 UTC
Please re-test against 2.6.15-rc1 *plus* the EHCI patches at  
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ 
 
Either see the "usb" subdirectory (use "quilt", or at least the 
apply in the order shown in the usb/series file) or the toplevel 
USB patches. 
 
One odd thing:  didn't look like EHCI was getting its PCI resume call. 
Comment 5 Jon Sanchez 2005-11-15 00:16:59 UTC
2.6.15-rc1 alone : same problem
2.6.15-rc1 +
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-usb-2.6.15-rc1.patch
: kernel panic

is it another patch ?

Comment 6 Jon Sanchez 2005-12-04 15:26:56 UTC
fixed in 2.6.15-rc4

Note You need to log in before you can comment on or make changes to this bug.