linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Woody Suwalski <terraluna977@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andreas Mohr <andi@lisas.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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, 16 Jan 2013 21:25:57 -0500	[thread overview]
Message-ID: <50F76135.8010708@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1301160955450.1704-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Tue, 15 Jan 2013, Woody Suwalski wrote:
>
>>> Another important change is that the EHCI driver is now split into two
>>> modules.  That can slow down loading and affect the timing.
>>>
>>> Alan Stern
>>>
>> My testcase is a live initramfs + squash root.
>> The boot logic is as stable as can be - unchanged since 2.6.2x kernels.
>> And it was working fine till 3.8-rc1.
>>
>> The modules are insmoded in a fixed order:
>> usb-common, usbcore, xhci-hcd, ehci-hcd, uhci-hcd, ohci-hcd, usbhid,
>> usb_storage,...
> But apparently you don't insmod ehci-pci.  That could cause problems,
> if your EHCI controller is PCI-based.
>
>> If all USB is built as modules - I get read errors from USB drives when
>> accessing squash image, boot fails.
> What read errors?  What is the cause of these errors?
>
>> If usb-common and usbcore are built in, system seems to crawl with a
>> very slow USB, but boots. That could be caused by timing between hcd
>> modules.
> Do have a dmesg log with timestamps so we can see where things go slow?
> I suggest enabling CONFIG_PRINTK_TIME and CONFIG_USB_DEBUG.  You might
> even want CONFIG_USB_STORAGE_DEBUG, although that often logs too much
> information.
>
>> If usb-common, usbcore and ehci-hcd are built-in, all works OK like
>> "before 3.8".
> What about ehci-pci?
>
>
Alan, it took me 2 times re-reading the email to notice...
You were talking about ehci-pci, not ehci-hcd... Old assumptions die hard...
Yep, that was it.
Catch22 - I would have noticed new dependency if I could boot, but to 
boot I have had needed to notice the new dependency...

Case solved 8-)

Thanks, Woody


      reply	other threads:[~2013-01-17  2:25 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
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 [this message]

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=50F76135.8010708@gmail.com \
    --to=terraluna977@gmail.com \
    --cc=andi@lisas.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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).