From: Larry Finger <Larry.Finger@lwfinger.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: Regression in kernel 3.8-rc1 bisected to commit adfa79d: I now get many "unable to enumerate USB device" messages
Date: Thu, 27 Dec 2012 09:46:37 -0600 [thread overview]
Message-ID: <50DC6D5D.30806@lwfinger.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1212262251280.25450-100000@netrider.rowland.org>
On 12/26/2012 09:56 PM, Alan Stern wrote:
> This looks like a matter of getting modules to load in the right order.
> Apparently your OHCI controller doesn't work right if the EHCI driver
> isn't present. Before the troublesome commit, this meant ehci-hcd had
> to be loaded before ohci-hcd. Now it means ehci-hcd and ehci-pci both
> have to be loaded before ohci-hcd.
>
> In the dmesg log you provided, ehci-hcd was loaded before ohci-hcd but
> ehci-pci was loaded after. Of course, when everything is built into
> the kernel (not as modules) then questions of loading order don't
> arise.
>
> You can test this hypothesis by booting a kernel without that commit
> and blacklisting ehci-hcd, so that it doesn't get loaded automatically.
> See if the errors start to come, and see if they stop when you load
> ehci-hcd manually.
I could not do exactly the experiment that you wanted, as ehci-hcd was loaded
even though it was blacklisted. Rather than solve that problem, I generated a
kernel from just before commit adfa79d with ohci-hcd built in and ehci-hcd as a
module. This one generated the errors, but they stopped when ehci-hcd loaded. I
also tested a 3.8-rc1 kernel with ehci-hcd and ehcd-pci built in and ohci-hcd as
a module. No errors for that one. Your hypothesis looks correct.
I hope there is some way to force ehci-pci to load as soon as ehci-hcd is
loaded, and before ohci-hcd loads, but if there is not, I know how to prevent
the errors on my system even though this solution won't help the users of distro
kernels. At least this time the errors stop once all 3 modules are loaded, and
the number of error outputs is limited.
Thanks,
Larry
next prev parent reply other threads:[~2012-12-27 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 3:16 Larry Finger
2012-12-25 16:26 ` Alan Stern
2012-12-25 18:06 ` Larry Finger
2012-12-26 16:45 ` Alan Stern
2012-12-26 17:44 ` Larry Finger
2012-12-26 19:12 ` Larry Finger
2012-12-27 3:56 ` Alan Stern
2012-12-27 15:46 ` Larry Finger [this message]
2012-12-27 23:18 ` Alan Stern
2012-12-27 23:40 ` Larry Finger
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=50DC6D5D.30806@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®