From: David Brownell <david-b@pacbell.net>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: 2.6.6-mm2, usb ehci warnings/error?
Date: Fri, 14 May 2004 10:04:26 -0700 [thread overview]
Message-ID: <40A4FC1A.20809@pacbell.net> (raw)
In-Reply-To: <40A47AC3.4010403@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Prakash K. Cheemplavam wrote:
> David Brownell wrote:
>
>>> 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.
>
> Ok, good. Thanks for the explanation of what is going on, though I don't
> can make too much out of it. ;-)
The short version is: it's missing this patch.
[ Greg, please merge! ]
- Dave
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 355 bytes --]
--- bk2/xu26/drivers/usb/host/ohci-hub.c 2004-05-11 18:03:30.000000000 -0700
+++ gadget-2.6/drivers/usb/host/ohci-hub.c 2004-05-13 09:15:18.000000000 -0700
@@ -385,6 +385,7 @@
) {
ohci_vdbg (ohci, "autosuspend\n");
(void) ohci_hub_suspend (&ohci->hcd);
+ ohci->hcd.state = USB_STATE_RUNNING;
up (&hcd->self.root_hub->serialize);
}
#endif
next prev parent reply other threads:[~2004-05-14 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 15:37 David Brownell
2004-05-14 7:52 ` Prakash K. Cheemplavam
2004-05-14 12:21 ` libata and write cache Prakash K. Cheemplavam
2004-05-14 17:04 ` David Brownell [this message]
2004-05-14 19:11 ` 2.6.6-mm2, usb ehci warnings/error? 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=40A4FC1A.20809@pacbell.net \
--to=david-b@pacbell.net \
--cc=PrakashKC@gmx.de \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®