From: Woody Suwalski <terraluna977@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
USB list <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.8-rc1 - another regression on USB :-(
Date: Wed, 02 Jan 2013 08:41:11 -0500 [thread overview]
Message-ID: <50E438F7.7040403@gmail.com> (raw)
In-Reply-To: <20121223232748.GA23804@kroah.com>
Greg Kroah-Hartman wrote:
> On Sun, Dec 23, 2012 at 02:35:49PM -0800, Linus Torvalds wrote:
>> Woody,
>> Any chance you can bisect this? It's not going to be hugely pleasant
>> (with 11k+ commits in between 3.7 and 3.8-rc1 you'll have to compile
>> and test at least 14 kernels), but it would help enormously. Of
>> course, maybe some USB person can guess what would cause the device to
>> go offline..
>>
>> Added Greg and the linux-usb mailing list to the participants list:
>> the images are in the original email on lkml, but there isn't anything
>> particularly interesting there, it really just seems to be an
>> unexpected and spurious USB disconnect, resulting in "USB disconnect,
>> device number 2" followed by "Rejecting I/O to offline device".
> I don't see any images on lkml, sorry.
>
> The kernel log for when the disconnect happened would be great to get.
>
> The kernel can't cause a device to disconnect, that's an electrical
> thing usually, is this perchance a flaky device/connection? Or has it
> always worked on older kernels?
>
> What host controller is being used here (xhci, ehci, etc.?)
>
> thanks,
>
> greg k-h
Greg, Linus,
It sounds insane, but after banging on the issue I have found out that
USB problem is caused (also in vanilla kernel) with a config change:
USB-all built as modules - bad USB
USB core built in, UHCI/EHCI modules - semi functional - but 1Mb/s transfer
USB core and UHCI EHCI built-in - bingo - no issues.
Could anybody duplicate that, or is it somehow my setup???
Thanks, Woody
next prev parent reply other threads:[~2013-01-02 13:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 2:00 Linux 3.8-rc1 Linus Torvalds
2012-12-22 2:57 ` Steven Rostedt
2013-01-16 9:25 ` David Nyström
2012-12-23 13:39 ` [Regression w/ patch] Media commit causes user space to misbahave (was: Re: Linux 3.8-rc1) Rafael J. Wysocki
2012-12-23 14:08 ` Mauro Carvalho Chehab
2012-12-23 17:36 ` Linus Torvalds
2012-12-23 20:21 ` Mauro Carvalho Chehab
2012-12-23 22:29 ` Linus Torvalds
2012-12-24 19:28 ` Mauro Carvalho Chehab
2012-12-23 20:39 ` Laurent Pinchart
2012-12-23 22:04 ` linux-next stats (Was: " Stephen Rothwell
[not found] ` <50D764BA.1030501@gmail.com>
2012-12-23 22:35 ` Linux 3.8-rc1 - another regression on USB :-( Linus Torvalds
2012-12-23 23:27 ` Greg Kroah-Hartman
2012-12-24 3:46 ` Woody Suwalski
2012-12-28 23:12 ` Woody Suwalski
2013-01-01 15:17 ` INVALID " Woody Suwalski
2013-01-02 13:41 ` Woody Suwalski [this message]
2013-01-12 13:16 ` Andreas Mohr
2013-01-12 16:54 ` Oliver Neukum
2013-01-12 17:38 ` Alan Stern
2013-01-16 4:26 ` Woody Suwalski
2013-01-16 8:25 ` Oliver Neukum
2013-01-16 15:00 ` Alan Stern
2013-01-17 2:25 ` Woody Suwalski
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=50E438F7.7040403@gmail.com \
--to=terraluna977@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).