Bug 5291 - usb broken after S3 resume
usb broken after S3 resume
Status: REJECTED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: USB
i386 Linux
: P2 normal
Assigned To: acpi_power-sleep-wake
:
Depends on:
Blocks: USB
  Show dependency treegraph
 
Reported: 2005-09-21 10:59 UTC by Enry
Modified: 2006-07-10 13:30 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.14-rc4
Tree: Mainline
Regression: ---


Attachments

Description Enry 2005-09-21 10:59:08 UTC
Most recent kernel where this bug did not occur: none
Distribution:Ubuntu
Hardware Environment: Acer Travelmate 427LC
Software Environment: Ubuntu Breezy
Problem Description:
Following instruction from Documentation/power/video.txt, i got sleep s3 working
with a radeon 7500 mobility.. Main issue is that usbcore module don't want to
unload, if forced i got an Ooops.. Resuming without forcing unloading i obtain
two different situation:

[with mouse plugged in]Mouse goes slow, if unplugged it will be no more
recognized from the kernel.. no other usb perpherals will be recognized..

[without mouse plugged in]It seems controller is frozen.. no dmesg entry about
any usb action un plug/unplug action...

Steps to reproduce:

I have this configuration for my 2.6.14-rc1
http://www.cs.unibo.it/~ecataldi/config-2.6.14-rc1

I use vbestate to avoid radeon problems about S3...
Go S3 through /sys/power/state
and have successfull resume but usb managing is done..
Comment 1 David Brownell 2005-10-13 12:30:46 UTC
see also bug #5227 
Comment 2 Enry 2005-10-15 03:20:48 UTC
I read bug #5227 and applyed patches on comments #22,#13 over 2.6.14-rc4.
The situation didn't changed..

On www.cs.unibo.it/~ecataldi/log_resume there is a dmesg log divided in 3 zones:
after resuming - after unplugging usb mouse - after plugging usb mouse.

On www.cs.unibo.it/~ecataldi/config-2.6.14-rc4-exp there is the configuration
for this attempt.

Hope this can be helpfull.
Comment 3 Adrian Bunk 2006-04-07 05:36:28 UTC
What is the status of this issue in kernel 2.6.16.1?
Comment 4 Adrian Bunk 2006-07-10 13:30:12 UTC
Please reopen this bug if it's still present in kernel 2.6.17.

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