From: David Brownell <david-b@pacbell.net>
To: David Miller <davem@davemloft.net>
Cc: andre@tomt.net, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: USB OOPS 2.6.25-rc2-git1
Date: Tue, 19 Feb 2008 16:19:54 -0800 [thread overview]
Message-ID: <200802191619.55207.david-b@pacbell.net> (raw)
In-Reply-To: <20080219.142401.152827357.davem@davemloft.net>
On Tuesday 19 February 2008, David Miller wrote:
> From: Andre Tomt <andre@tomt.net>
> Date: Tue, 19 Feb 2008 16:19:08 +0100
>
> > Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
> > not doing anything interesting at the time, but has its / and kernel on
> > a usb-storage device (usb pen drive).
> >
> > Intel ICH8R chipset (and USB controller), running x86_64 kernel. I'll
> > post .config and some additional info when I get home later if it isn't
> > obvious what broke.
>
> FWIW, I've seen a near identical crash on my Niagara system.
Please try that diagnostic patch I sent ... with CONFIG_USB_DEBUG.
Near as I can tell this is caused by some hardware oddity that needs
to be worked around. We seem to be at stage where we've fixed some
problems, nudging code paths around so another one shows up, and have
incidentally had a new silicion-specific hardware erratum reported
in this area. So more info is needed...
A quick anti-oops patch is appended, it should work OK on top of that
diagnostic patch, but won't necessarily resolve the underlying problem.
- Dave
--- g26.orig/drivers/usb/host/ehci-q.c 2008-02-19 16:15:04.000000000 -0800
+++ g26/drivers/usb/host/ehci-q.c 2008-02-19 16:15:59.000000000 -0800
@@ -993,6 +993,11 @@ static void end_unlink_async (struct ehc
iaa_watchdog_done(ehci);
+ if (!qh) {
+ WARN_ON(1);
+ return;
+ }
+
// qh->hw_next = cpu_to_hc32(qh->qh_dma);
qh->qh_state = QH_STATE_IDLE;
qh->qh_next.qh = NULL;
next prev parent reply other threads:[~2008-02-20 0:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 15:19 USB OOPS 2.6.25-rc2-git1 Andre Tomt
2008-02-19 18:49 ` David Brownell
2008-02-19 23:04 ` Andre Tomt
2008-02-20 0:32 ` David Brownell
2008-02-20 20:33 ` Andre Tomt
2008-02-20 21:16 ` Alan Stern
2008-02-20 21:56 ` David Brownell
2008-02-20 22:33 ` Alan Stern
2008-02-20 22:54 ` David Brownell
2008-02-21 16:15 ` Alan Stern
2008-03-05 4:15 ` David Brownell
2008-03-05 17:04 ` Alan Stern
2008-03-05 17:39 ` David Brownell
2008-02-21 15:56 ` Alan Stern
2008-02-25 9:13 ` David Brownell
2008-02-20 21:24 ` David Brownell
2008-02-21 0:25 ` Andre Tomt
2008-02-21 0:53 ` David Brownell
2008-02-19 19:31 ` Alan Stern
2008-02-19 21:58 ` Andre Tomt
2008-02-19 22:24 ` David Miller
2008-02-20 0:19 ` David Brownell [this message]
2008-02-20 1:40 ` David Miller
2008-02-20 16:10 ` Alan Stern
2008-02-19 22:28 ` Andre Tomt
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=200802191619.55207.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=andre@tomt.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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