From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Samuel Rydh <samuel@ibrium.se>, "tom_gall@mac.com" <tom_gall@mac.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: USB, 2.6-test11 and hot flaming death
Date: Mon, 15 Dec 2003 11:22:58 +1100 [thread overview]
Message-ID: <1071447777.12498.398.camel@gaston> (raw)
In-Reply-To: <20031205233307.GA7462@ibrium.se>
I'm having more reports of this USB problem on G5s, apparently
not always related to using old kbds...
In the dmesg log I have here, the problem starts with an error
in dl_resverse_done_list() where this case is triggered:
if (!td) {
ohci_err (ohci, "bad entry %8x\n", td_dma);
break;
}
It would be interesting, since you both have a 100% repro case,
to check out what URBs are filled in the lists and where do that
"bad" one comes from...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-15 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 19:07 USB, 2.6-test11 and hot flaming death tom_gall
2003-11-29 4:43 ` Benjamin Herrenschmidt
2003-12-01 14:09 ` tom_gall
2003-12-04 16:34 ` Samuel Rydh
2003-12-04 23:35 ` Benjamin Herrenschmidt
2003-12-05 23:33 ` Samuel Rydh
2003-12-07 1:09 ` Benjamin Herrenschmidt
2003-12-15 0:22 ` Benjamin Herrenschmidt [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=1071447777.12498.398.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=samuel@ibrium.se \
--cc=tom_gall@mac.com \
/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).