From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kevin Diggs <kevdig@hypersurf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: gigE 2.6.27 USB
Date: Wed, 15 Oct 2008 15:45:59 +1100 [thread overview]
Message-ID: <1224045959.8157.424.camel@pasglop> (raw)
In-Reply-To: <48F479ED.1030500@hypersurf.com>
On Tue, 2008-10-14 at 03:52 -0700, Kevin Diggs wrote:
> Kevin Diggs wrote:
> > Hi,
> >
> > I managed to wrestle my gigE to the ground and get it to boot
> > 2.6.27. I have, however, noticed that some messages are showing up in
> > dmesg. There are alot of them. They are continuous. They appear to come
> > from drivers/usb/core/hub.c:2916. It looks like they come in pairs (this
> > beast has two ports (root hubs)). I plugged in a USB CF reader. It
> > appears to work. The keyboard and mouse (a Logitech wireless receiver)
> > seems to work. 2.6.24 did not do this.
> >
> > kevin
> >
> For what it is worth, I tricked a laptop into booting 2.6.27. It
> does not appear to generate these messages. The PowerMac is running
> Yellow Dog 4.
It would be a lot more useful if you included informations in your
report such as :
- The actual error output
- The full dmesg log
- Informations about the adapter including output of lsusb -v
- How do you actually trigger the problem
It would be even more useful if you CC'ed some relevant list such
as the linux-usb one too :-)
Cheers,
Ben.
next prev parent reply other threads:[~2008-10-15 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 10:34 gigE 2.6.27 USB Kevin Diggs
2008-10-14 10:52 ` Kevin Diggs
2008-10-15 4:45 ` Benjamin Herrenschmidt [this message]
2008-10-15 14:56 ` Kevin Diggs
2008-10-15 15:28 ` Alan Stern
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=1224045959.8157.424.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).