From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Samuel Rydh <samuel@ibrium.se>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: USB, 2.6-test11 and hot flaming death
Date: Sun, 07 Dec 2003 12:09:39 +1100 [thread overview]
Message-ID: <1070759378.12499.15.camel@gaston> (raw)
In-Reply-To: <20031205233307.GA7462@ibrium.se>
On Sat, 2003-12-06 at 10:33, Samuel Rydh wrote:
> On Fri, Dec 05, 2003 at 10:35:26AM +1100, Benjamin Herrenschmidt wrote:
> >
> > > This problem has actually been present quite a while (at least
> > > since 2.6.0-test3). On my dual 1.25 GHz G4, it occurs once
> > > every four boots or so.
> >
> > Interesting. It happens with the NEC EHCI/OHCI or with the
> > KeyLargo OHCI's ? I suspect it's a problem of the NEC part,
> > and I think K2 actually contains that part built-in on the G5
>
> The USB devices are all hooked up on the NEC EHCI/OHCI. I don't think the
> KeyLargo OHCI cell is physically connected to any ports; it doesn't
> show up in the device tree...
Ok, so something is wrong between those old Apple kbds and the NEC
part... Interesting. Does MacOS X show any similar symptom ? Also,
I suppose we could fix the OHCI driver to at least try to recover
in this case... I don't have much time to play with this at the
moment, but I'll keep that in mind. I need to find one of those
bad kbds first ;)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-07 1:09 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 [this message]
2003-12-15 0:22 ` Benjamin Herrenschmidt
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=1070759378.12499.15.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=samuel@ibrium.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.