From: David <david@unsolicited.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dbrownell@users.sourceforge.net, leonidv11@gmail.com,
Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down
Date: Mon, 25 May 2009 19:44:21 +0100 [thread overview]
Message-ID: <4A1AE705.2050809@unsolicited.net> (raw)
In-Reply-To: <4A1AD62C.8070907@unsolicited.net>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
David wrote:
> Alan Stern wrote:
>
>> Okay, here's a patch for you to try. It refreshes the toggle setting
>> in a linked but otherwise idle QH when a new URB is queued.
>>
>> Alan Stern
>>
>>
>> Index: usb-2.6/drivers/usb/host/ehci-q.c
>> ===================================================================
>> --- usb-2.6.orig/drivers/usb/host/ehci-q.c
>> +++ usb-2.6/drivers/usb/host/ehci-q.c
>> @@ -88,7 +88,7 @@ static inline void
>> qh_update (struct ehci_hcd *ehci, struct ehci_qh *qh, struct ehci_qtd *qtd)
>> {
>> /* writes to an active overlay are unsafe */
>> - BUG_ON(qh->qh_state != QH_STATE_IDLE);
>> + BUG_ON(qh->qh_state != QH_STATE_IDLE && !list_empty(&qh->qtd_list));
>>
>> qh->hw_qtd_next = QTD_NEXT(ehci, qtd->qtd_dma);
>> qh->hw_alt_next = EHCI_LIST_END(ehci);
>> @@ -971,7 +971,13 @@ static struct ehci_qh *qh_append_tds (
>> /* can't sleep here, we have ehci->lock... */
>> qh = qh_make (ehci, urb, GFP_ATOMIC);
>> *ptr = qh;
>> + } else if (list_empty(&qh->qtd_list)) {
>> + /* There might have been a Clear-Halt while the QH
>> + * was linked but empty.
>> + */
>> + qh_refresh(ehci, qh);
>> }
>> +
>> if (likely (qh != NULL)) {
>> struct ehci_qtd *qtd;
>>
>>
>>
>>
> No luck I'm afraid (although there now appear to be 2 timeouts, not
> one). I'm going to follow up on the laptop and get a USB log.
>
USB log post-patch attached. Thanks for all the effort so far!
David
[-- Attachment #2: postpatch.log.bz2 --]
[-- Type: application/x-bzip, Size: 12697 bytes --]
next prev parent reply other threads:[~2009-05-25 18:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 21:32 USB/DVB - Old Technotrend TT-connect S-2400 regression tracked down David
2009-05-22 21:45 ` David
2009-05-23 8:25 ` Pekka Enberg
2009-05-23 15:15 ` Alan Stern
2009-05-23 18:20 ` David
2009-05-23 19:22 ` David
2009-05-23 21:02 ` Alan Stern
2009-05-24 0:15 ` David
2009-05-24 0:54 ` hermann pitton
2009-05-24 8:35 ` David
2009-05-24 14:33 ` Alan Stern
2009-05-24 15:28 ` David
2009-05-25 2:10 ` Alan Stern
2009-05-25 2:39 ` Pete Zaitcev
2009-05-25 9:00 ` David
2009-05-25 12:25 ` David
2009-05-26 0:48 ` Pete Zaitcev
2009-05-26 14:08 ` Alan Stern
2009-05-26 18:42 ` David
2009-05-26 19:01 ` Pete Zaitcev
2009-05-24 15:16 ` Alan Stern
2009-05-25 15:23 ` Alan Stern
2009-05-25 17:32 ` David
2009-05-25 18:44 ` David [this message]
2009-05-25 21:12 ` Alan Stern
2009-05-26 20:57 ` Alan Stern
2009-05-27 18:42 ` David
2009-05-27 20:20 ` Alan Stern
2009-05-27 21:28 ` David
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=4A1AE705.2050809@unsolicited.net \
--to=david@unsolicited.net \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=leonidv11@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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