From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: Marc Haber <mh+linux-kernel@zugschlus.de>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.6.15 EHCI hang on boot
Date: Tue, 10 Jan 2006 00:27:48 -0800 [thread overview]
Message-ID: <200601100027.48372.david-b@pacbell.net> (raw)
In-Reply-To: <20060104220403.GC12778@kroah.com>
On Wednesday 04 January 2006 2:04 pm, Greg KH wrote:
> > I suspect an incompatibility with the i865 chipset. Is there anything
> > I can do to help debugging?
>
> I don't know, David, any ideas?
Such things are more often BIOS than chipset, so check for updates there.
Plus, you commented that the issue only shows up with your newest board,
and most folk don't have such hang-on-boot issues.
There were updates in 2.6.15 to how all the PCI based usb host controller
drivers handle their reset/init logic ... basically "handoff" from BIOS to
the OS kernel (Linux) is always done "early" now. Previously it wasn't
always done until late (too late for the input subsystem, given usb keyboards
and mice that the BIOS uses to emulate ps/2 ones), and wasn't done very
consistently. (The "early handoff" code didn't act identically to the
code inside the HCDs that did the bios handoff "later".)
If there's no BIOS update, one experiment would be to #ifdef out the call
to bios_handoff() in drivers/usb/host/ehci-pci.c ... the version of that
code in the .../usb/hosts/pci-quirks.c file _should_ eventually suffice,
though I think there are still differences between that version and the
one (in ehci-pci.c) that's better tested.
- Dave
prev parent reply other threads:[~2006-01-10 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 16:18 2.6.15 EHCI hang on boot Marc Haber
2006-01-04 16:27 ` Ben Dooks
2006-01-04 17:10 ` Marc Haber
2006-01-04 22:04 ` Greg KH
2006-01-10 8:27 ` David Brownell [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=200601100027.48372.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mh+linux-kernel@zugschlus.de \
/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