From: Dominik Brugger <ml.dominik83@gmx.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: OHCI problems with suspend/resume
Date: Thu, 24 Jul 2003 14:37:31 +0200 [thread overview]
Message-ID: <20030724143731.5fe40b4e.ml.dominik83@gmx.net> (raw)
In-Reply-To: <20030723220805.GA278@elf.ucw.cz>
> In 2.6.0-test1, OHCI is non-functional after first suspend/resume, and
> kills machine during secon suspend/resume cycle.
I experience similar problems with UHCI:
Before suspending to S3 I unload usb modules and afterwards I reload them, but it does not work again.
(For testing I also plugged in an USB card reader with an LED.
The LED is on except when I resume from S3)
Here is some dmesg output
After booting:
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci-hcd 0000:00:11.2: VIA Technologies, In USB
uhci-hcd 0000:00:11.2: irq 10, io base 0000dc00
uhci-hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
drivers/usb/host/uhci-hcd.c: detected 2 ports
uhci-hcd 0000:00:11.2: root hub device address 1
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: VIA Technologies, In USB
usb usb1: Manufacturer: Linux 2.6.0-test1-bk2 uhci-hcd
usb usb1: SerialNumber: 0000:00:11.2
drivers/usb/core/usb.c: usb_hotplug
usb usb1: usb_new_device - registering interface 1-0:0
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:0: usb_device_probe
hub 1-0:0: usb_device_probe - got id
hub 1-0:0: USB hub found
hub 1-0:0: 2 ports detected
hub 1-0:0: standalone hub
hub 1-0:0: ganged power switching
hub 1-0:0: global over-current protection
hub 1-0:0: Port indicators are not supported
hub 1-0:0: power on to power good time: 2ms
hub 1-0:0: hub controller current requirement: 0mA
hub 1-0:0: local power source is good
hub 1-0:0: no over-current condition exists
hub 1-0:0: enabling power on all ports
hub 1-0:0: port 1, status 100, change 3, 12 Mb/s
hub 1-0:0: port 2, status 301, change 3, 1.5 Mb/s
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x301
hub 1-0:0: new USB device on port 2, assigned address 2
usb 1-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: USB-PS/2 Optical Mouse
usb 1-2: Manufacturer: Logitech
drivers/usb/core/usb.c: usb_hotplug
usb 1-2: usb_new_device - registering interface 1-2:0
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:0: port 1 enable change, status 100
hid 1-2:0: usb_device_probe
hid 1-2:0: usb_device_probe - got id
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:11.2-2
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
rmmod uhci_hcd hid usbcore:
uhci-hcd 0000:00:11.2: remove, state 3
uhci-hcd 0000:00:11.2: roothub graceful disconnect
usb usb1: USB disconnect, address 1
usb 1-2: USB disconnect, address 2
drivers/usb/core/usb.c: nuking urbs assigned to 1-2
usb 1-2: unregistering interfaces
drivers/usb/core/usb.c: nuking urbs assigned to 1-2
usb 1-2: hcd_unlink_urb df5047c0 fail -22
usb 1-2: hcd_unlink_urb df504740 fail -22
drivers/usb/core/usb.c: usb_hotplug
usb 1-2: unregistering device
drivers/usb/core/usb.c: usb_hotplug
drivers/usb/core/usb.c: nuking urbs assigned to usb1
uhci-hcd 0000:00:11.2: shutdown urb df504940 pipe 40408180 ep1in-intr
usb usb1: unregistering interfaces
drivers/usb/core/usb.c: nuking urbs assigned to usb1
usb usb1: hcd_unlink_urb df504940 fail -22
drivers/usb/core/usb.c: usb_hotplug
usb usb1: unregistering device
drivers/usb/core/usb.c: usb_hotplug
uhci-hcd 0000:00:11.2: USB bus 1 deregistered
drivers/usb/core/usb.c: deregistering driver hid
drivers/usb/core/usb.c: deregistering driver usbfs
drivers/usb/core/hub.c: hub_thread exiting
drivers/usb/core/usb.c: deregistering driver hub
echo 3 > /proc/acpi/sleep
modprobe usbcore uhci_hcd
(Sometimes the optical mouse blinks for a moment)
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci-hcd 0000:00:11.2: VIA Technologies, In USB
uhci-hcd 0000:00:11.2: irq 10, io base 0000dc00
uhci-hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
drivers/usb/host/uhci-hcd.c: detected 2 ports
uhci-hcd 0000:00:11.2: root hub device address 1
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: VIA Technologies, In USB
usb usb1: Manufacturer: Linux 2.6.0-test1-bk2 uhci-hcd
usb usb1: SerialNumber: 0000:00:11.2
drivers/usb/core/usb.c: usb_hotplug
usb usb1: usb_new_device - registering interface 1-0:0
drivers/usb/core/usb.c: usb_hotplug
hub 1-0:0: usb_device_probe
hub 1-0:0: usb_device_probe - got id
hub 1-0:0: USB hub found
hub 1-0:0: 2 ports detected
hub 1-0:0: standalone hub
hub 1-0:0: ganged power switching
hub 1-0:0: global over-current protection
hub 1-0:0: Port indicators are not supported
hub 1-0:0: power on to power good time: 2ms
hub 1-0:0: hub controller current requirement: 0mA
hub 1-0:0: local power source is good
hub 1-0:0: no over-current condition exists
hub 1-0:0: enabling power on all ports
hub 1-0:0: port 1, status 100, change 3, 12 Mb/s
hub 1-0:0: port 2, status 301, change 3, 1.5 Mb/s
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x301
hub 1-0:0: new USB device on port 2, assigned address 2
drivers/usb/core/message.c: usb_control/bulk_msg: timeout
-Dominik Brugger
next prev parent reply other threads:[~2003-07-24 12:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 22:08 Pavel Machek
2003-07-24 1:19 ` [linux-usb-devel] " David Brownell
2003-07-24 10:24 ` Pavel Machek
2003-07-24 17:10 ` David Brownell
2003-07-24 22:10 ` Pavel Machek
2003-07-24 12:37 ` Dominik Brugger [this message]
2003-07-24 12:56 ` Dominik Brugger
2003-07-24 22:04 ` Pavel Machek
2003-07-24 22:46 ` Pavel Machek
2003-07-25 7:52 ` Dominik Brugger
2003-07-25 15:06 ` [linux-usb-devel] " Alan Stern
2003-07-25 17:20 ` Benjamin Herrenschmidt
2003-07-25 22:48 ` David Brownell
2003-07-26 16:02 ` Alan Stern
2003-07-26 21:01 ` Pavel Machek
2003-07-26 21:16 ` David Brownell
2003-07-27 14:57 ` Alan Stern
2003-07-31 3:27 ` David Brownell
2003-07-31 3:51 ` David Brownell
2003-07-31 9:42 ` Pavel Machek
2003-07-31 13:37 ` David Brownell
2003-07-31 14:09 ` Pavel Machek
2003-07-31 17:32 ` David Brownell
2003-07-31 17:31 ` Pavel Machek
2003-07-31 21:32 ` Benjamin Herrenschmidt
2003-07-31 21:30 ` Benjamin Herrenschmidt
2003-07-31 21:29 ` Benjamin Herrenschmidt
2003-07-31 9:47 ` Pavel Machek
2003-07-31 13:30 ` David Brownell
2003-07-31 16:06 ` Pavel Machek
2003-07-31 9:49 ` Pavel Machek
2003-07-31 13:23 ` David Brownell
2003-07-31 16:07 ` Pavel Machek
2003-07-31 21:25 ` Benjamin Herrenschmidt
2003-07-31 21:25 ` Benjamin Herrenschmidt
2003-07-31 22:08 ` Pavel Machek
2003-07-31 21:23 ` Benjamin Herrenschmidt
2003-07-31 21:55 ` David Brownell
2003-07-31 22:05 ` Benjamin Herrenschmidt
2003-07-31 22:09 ` Pavel Machek
2003-07-31 23:12 ` Oliver Neukum
2003-08-01 9:33 ` Pavel Machek
2003-07-31 22:03 ` Pavel Machek
2003-08-01 0:27 ` Benjamin Herrenschmidt
2003-08-04 19:25 ` Pavel Machek
2003-08-01 18:20 ` Dominik Brugger
2003-07-29 13:16 ` [linux-usb-devel] " David Brownell
2003-07-31 14:18 ` Pavel Machek
2003-08-01 17:41 ` David Brownell
2003-08-07 22:35 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030724143731.5fe40b4e.ml.dominik83@gmx.net \
--to=ml.dominik83@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®