From: David Brownell <david-b@pacbell.net>
To: PrakashKC@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm2, usb ehci warnings/error?
Date: Thu, 13 May 2004 08:37:19 -0700 [thread overview]
Message-ID: <40A3962F.3020500@pacbell.net> (raw)
> There appear lines like
>
> usb usb2: string descriptor 0 read error: -108
>
> bug or feature? They weren't there with 2.6.6-mm1. I have no usb2.0
> stuff to actually test. My usb1 stuff seems to work though.
Bug; minor, since the only real symptom seems to be messages like
that. Ignore them for now, I'll make a patch soonish.
It's actually the OHCI driver managing your "usb2" bus,
this is nothing to do with EHCI:
> ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2)
> PCI: Setting latency timer of device 0000:00:02.1 to 64
> ohci_hcd 0000:00:02.1: irq 21, pci mem f88fe000
> ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 3 ports detected
What's happening? One of the USB patches makes OHCI suspend
its root hub when it's idle (no devices attached), much like
the UHCI driver has done for some time. Saves some power.
However, it wrongly marks the controller itself (vs just the
root hub part of it) as having suspended. That's what causes
the "-108" (-ESHUTDOWN) fault reports, as if the controller were
suspended too. When the controller is suspended, its registers
are inaccesible so requests to the root hub must fail.
- Dave
next reply other threads:[~2004-05-13 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 15:37 David Brownell [this message]
2004-05-14 7:52 ` 2.6.6-mm2, usb ehci warnings/error? Prakash K. Cheemplavam
2004-05-14 12:21 ` libata and write cache Prakash K. Cheemplavam
2004-05-14 17:04 ` 2.6.6-mm2, usb ehci warnings/error? David Brownell
2004-05-14 19:11 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
2004-05-13 10:53 ` 2.6.6-mm2, usb ehci warnings/error? Prakash K. Cheemplavam
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=40A3962F.3020500@pacbell.net \
--to=david-b@pacbell.net \
--cc=PrakashKC@gmx.de \
--cc=linux-kernel@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 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.