public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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 18:32:28 +0100	[thread overview]
Message-ID: <4A1AD62C.8070907@unsolicited.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0905251121370.23874-100000@netrider.rowland.org>

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.

[  118.017016] usb 1-10: new high speed USB device using ehci_hcd and
address 5
[  118.148589] usb 1-10: configuration #1 chosen from 1 choice
[  118.452964] dvb-usb: found a 'Technotrend TT-connect S-2400' in cold
state, will try to load a firmware
[  118.452972] usb 1-10: firmware: requesting dvb-usb-tt-s2400-01.fw
[  118.488474] dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
[  118.550946] usbcore: registered new interface driver dvb_usb_ttusb2
[  118.552553] usb 1-10: USB disconnect, address 5
[  118.561083] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[  120.313020] usb 1-10: new high speed USB device using ehci_hcd and
address 6
[  120.444942] usb 1-10: configuration #1 chosen from 1 choice
[  120.445886] dvb-usb: found a 'Technotrend TT-connect S-2400' in warm
state.
[  120.446672] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[  120.447014] DVB: registering new adapter (Technotrend TT-connect S-2400)
[  120.455026] DVB: registering adapter 0 frontend 129197120 (Philips
TDA10086 DVB-S)...
[  120.458383] LNBx2x attached on addr=8<3>dvb-usb: recv bulk message
failed: -110
[  122.457126] ttusb2: there might have been an error during control
message transfer. (rlen = 0, was 0)
[  124.456109] dvb-usb: recv bulk message failed: -110
[  124.456117] ttusb2: there might have been an error during control
message transfer. (rlen = 0, was 0)
[  124.456122] dvb-usb: Technotrend TT-connect S-2400 successfully
initialized and connected.


David


  reply	other threads:[~2009-05-25 17:35 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 [this message]
2009-05-25 18:44                 ` David
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=4A1AD62C.8070907@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