linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Soeren Moch <smoch@web.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
	USB list <linux-usb@vger.kernel.org>,
	Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-mm@kvack.org,
	Kernel development list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] USB: EHCI: fix for leaking isochronous data
Date: Fri, 15 Mar 2013 10:30:37 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1303151028100.1414-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <51426484.3000609@web.de>

On Fri, 15 Mar 2013, Soeren Moch wrote:

> > The log shows a 1-1 match between allocations and deallocations, except
> > for three excess allocations about 45 lines before the end.  I have no
> > idea what's up with those.  They may be an artifact arising from where
> > you stopped copying the log data.
> >
> > There are as many as 400 iTDs being allocated before any are freed.
> > That seems like a lot.  Are they all for the same isochronous endpoint?
> > What's the endpoint's period?  How often are URBs submitted?
> 
> I use 2 dvb sticks, capturing digital TV. For each stick 5 URBs on a 
> single endpoint are used, I think. I'm not sure, which endpoint in which 
> alternateSetting is active. I attached the output of 'lsusb -v' for the 
> sticks.
> How can I track down the other information you need?

Use usbmon (see Documentation/usb/usbmon.txt).

Alan Stern

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-03-15 14:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.1302211337580.1529-100000@iolanthe.rowland.org>
2013-03-10 18:45 ` Soeren Moch
2013-03-10 20:59   ` Alan Stern
2013-03-14 18:48     ` Soeren Moch
2013-03-14 20:22       ` Soeren Moch
2013-03-14 20:32       ` Alan Stern
2013-03-14 20:51         ` Soeren Moch
2013-03-14 21:33           ` Alan Stern
2013-03-15  0:00             ` Soeren Moch
2013-03-15 14:30               ` Alan Stern [this message]
2013-03-16  2:10             ` Soeren Moch
2013-03-16 17:39               ` Alan Stern
2013-03-17 16:56                 ` Soeren Moch
2013-03-17 17:36                   ` Alan Stern
2013-03-17 17:39                     ` Alan Stern
2013-03-21 17:04                     ` Soeren Moch
2013-03-21 17:33                       ` Jason Cooper
2013-03-21 19:10                         ` Arnd Bergmann
2013-03-21 19:34                           ` Michael Trimarchi
2013-03-21 21:52                           ` Soeren Moch
2013-03-21 21:06                       ` Alan Stern
2013-03-21 21:12                         ` Alan Stern
2013-03-21 21:20                           ` Andrew Lunn
2013-03-21 22:16                             ` Soeren Moch
2013-03-22 14:24                               ` Alan Stern
2013-03-21 21:45                           ` Soeren Moch

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=Pine.LNX.4.44L0.1303151028100.1414-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=smoch@web.de \
    /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