On Wed, 15 Oct 2008, Kevin Diggs wrote:
> I cut a deal with my 8600 to get it to boot 2.6.27. It does not seem
> to work right either.
>
> The error message that shows up in dmesg is (the messages that show
> up for the gigE appear to be for two different busses (hubs?):
>
> hub 1-0:1.0: state 7
Benjamin Herrenschmidt wrote:
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
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
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 pair
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 ha
