From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
greg@kroah.com, linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.6.11-rc[23]: swsusp & usb regression
Date: Sat, 5 Feb 2005 00:23:02 +0100 [thread overview]
Message-ID: <20050204232302.GA1060@elf.ucw.cz> (raw)
In-Reply-To: <20050204231649.GA1057@elf.ucw.cz>
Hi!
> In 2.6.11-rc[23], I get problems after swsusp resume:
>
> Feb 4 23:54:39 amd kernel: Restarting tasks...<3>hub 3-0:1.0:
> over-current change on port 1
> Feb 4 23:54:39 amd kernel: done
> Feb 4 23:54:39 amd kernel: hub 3-0:1.0: connect-debounce failed, port
> 1 disabled
> Feb 4 23:54:39 amd kernel: hub 3-0:1.0: over-current change on port 2
> Feb 4 23:54:39 amd kernel: usb 3-2: USB disconnect, address 2
>
> After unplugging usb bluetooth key, machine hung. Sysrq still
> responded with help but I could not get any usefull output.
I tried deselecting CONFIG_USB_EHCI_HCD, and got repeating stream of
Feb 5 00:21:17 amd kernel: Restarting tasks... done
Feb 5 00:21:17 amd kernel: hub 3-0:1.0: over-current change on port 1
Feb 5 00:21:18 amd kernel: hub 3-0:1.0: connect-debounce failed, port
1 disabled
Feb 5 00:21:18 amd kernel: hub 3-0:1.0: over-current change on port 2
Feb 5 00:21:20 amd kernel: hub 3-0:1.0: connect-debounce failed, port
2 disabled
Feb 5 00:21:20 amd kernel: hub 1-0:1.0: over-current change on port 1
Feb 5 00:21:21 amd kernel: hub 1-0:1.0: connect-debounce failed, port
1 disabled
Feb 5 00:21:21 amd kernel: hub 1-0:1.0: over-current change on port 2
Feb 5 00:21:23 amd kernel: hub 1-0:1.0: connect-debounce failed, port
2 disabled
Feb 5 00:21:23 amd kernel: hub 2-0:1.0: over-current change on port 1
Feb 5 00:21:24 amd kernel: hub 2-0:1.0: connect-debounce failed, port
1 disabled
Feb 5 00:21:24 amd kernel: hub 2-0:1.0: over-current change on port 2
Feb 5 00:21:24 amd kernel: usb 2-2: USB disconnect, address 2
Feb 5 00:21:26 amd kernel: hub 2-0:1.0: connect-debounce failed, port
2 disabled
Feb 5 00:21:26 amd kernel: hub 3-0:1.0: over-current change on port 1
Feb 5 00:21:28 amd kernel: hub 3-0:1.0: connect-debounce failed, port
1 disabled
Feb 5 00:21:28 amd kernel: hub 3-0:1.0: over-current change on port 2
Feb 5 00:21:29 amd kernel: hub 3-0:1.0: connect-debounce failed, port
2 disabled
Feb 5 00:21:29 amd kernel: hub 1-0:1.0: over-current change on port 1
Feb 5 00:21:31 amd kernel: hub 1-0:1.0: connect-debounce failed, port
1 disabled
Feb 5 00:21:31 amd kernel: hub 1-0:1.0: over-current change on port 2
Feb 5 00:21:32 amd kernel: hub 1-0:1.0: connect-debounce failed, port
2 disabled
Feb 5 00:21:32 amd kernel: hub 2-0:1.0: over-current change on port 1
Feb 5 00:21:34 amd kernel: hub 2-0:1.0: connect-debounce failed, port
1 disabled
Feb 5 00:21:34 amd kernel: hub 2-0:1.0: over-current change on port 2
Feb 5 00:21:35 amd kernel: hub 2-0:1.0: connect-debounce failed, port
2 disabled
Feb 5 00:21:35 amd kernel: hub 3-0:1.0: over-current change on port 1
...in syslog.
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-02-05 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 23:16 Pavel Machek
2005-02-04 23:23 ` Pavel Machek [this message]
2005-02-05 15:19 ` [linux-usb-devel] " Alan Stern
2005-02-05 23:14 ` Pavel Machek
2005-02-06 0:08 ` David Brownell
2005-02-06 0:26 ` Pavel Machek
2005-02-06 1:59 ` Alan Stern
2005-02-06 9:18 ` 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=20050204232302.GA1060@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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®