From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: linux-usb-devel@lists.sourceforge.net,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.10] ehci "hc died" on startup (chip bug workaround)
Date: Fri, 7 Jan 2005 10:05:43 -0800 [thread overview]
Message-ID: <200501071005.43520.david-b@pacbell.net> (raw)
In-Reply-To: <20050107174328.GB28878@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
On Friday 07 January 2005 9:43 am, Greg KH wrote:
> On Wed, Jan 05, 2005 at 02:35:42PM -0800, David Brownell wrote:
> > We seem to have tracked some annoying board-coupled EHCI startup
> > problems to a chip bug, with a simple workaround. Please merge.
>
> Hm, I get a reject from this:
> ...
>
> What kernel tree is it against?
Probably my gadget-2.6 tree; here's one that applies against
current 2.5 BK or your USB integration tree. Sorry!
- Dave
[-- Attachment #2: e0107.patch --]
[-- Type: text/x-diff, Size: 1840 bytes --]
This fixes OSDL bugid #3056 for at least some users, where the EHCI
driver gets a "fatal error" IRQ on startup ... only on certain boards,
starting with the 2.6.6 or 2.6.7 kernels. These IRQs normally indicate
that an invalid DMA address got passed to the controller, or something
equally nasty and unrecoverable.
But it turns out that some of these controllers (at least ALI and Intel)
are lying. They're issuing these IRQs without stopping, contrary to the
EHCI spec ... so these IRQs can be recovered from. Thanks to Christian
Iversen for noticing that his ALI controller would continue operating,
which was the first real break in this annoying case.
This patch tests for these bogus IRQs, and ignores them ... working around
what's clearly a chip bug. It's not clear why we started triggering that
bug, but at least EHCI is now usable on boards exhibiting this problem.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
--- xu26/drivers/usb/host/ehci-hcd.c 2004-12-20 15:07:23.000000000 -0800
+++ gadget-2.6/drivers/usb/host/ehci-hcd.c 2005-01-04 12:01:46.000000000 -0800
@@ -883,13 +903,20 @@
/* PCI errors [4.15.2.4] */
if (unlikely ((status & STS_FATAL) != 0)) {
- ehci_err (ehci, "fatal error\n");
+ /* bogus "fatal" IRQs appear on some chips... why? */
+ status = readl (&ehci->regs->status);
+ dbg_cmd (ehci, "fatal", readl (&ehci->regs->command));
+ dbg_status (ehci, "fatal", status);
+ if (status & STS_HALT) {
+ ehci_err (ehci, "fatal error\n");
dead:
- ehci_reset (ehci);
- /* generic layer kills/unlinks all urbs, then
- * uses ehci_stop to clean up the rest
- */
- bh = 1;
+ ehci_reset (ehci);
+ writel (0, &ehci->regs->configured_flag);
+ /* generic layer kills/unlinks all urbs, then
+ * uses ehci_stop to clean up the rest
+ */
+ bh = 1;
+ }
}
if (bh)
next prev parent reply other threads:[~2005-01-07 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 22:35 [patch 2.6.10] ehci "hc died" on startup (chip bug workaround) David Brownell
2005-01-07 17:43 ` Greg KH
2005-01-07 18:05 ` David Brownell [this message]
2005-01-07 18:29 ` Greg KH
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=200501071005.43520.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 \
/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