From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-media@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
laurent.pinchart@ideasonboard.com
Subject: Re: uvcvideo causes ehci_hcd to halt
Date: Wed, 21 Oct 2009 18:38:46 +0300 [thread overview]
Message-ID: <4ADF2B06.7090801@pardus.org.tr> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0910211052200.2847-100000@iolanthe.rowland.org>
Alan Stern wrote:
(Add uvcvideo maintainer to CC)
> [ 420.737748] usb 1-5: link qh1024-0001/f6ffe280 start 1 [1/0 us]
>
>
> The periodic schedule was enabled here.
>
>
>> [ 420.737891] usb 1-5: unlink qh1024-0001/f6ffe280 start 1 [1/0 us]
>>
>
> And it was disabled here. Do you have any idea why the uvcvideo driver
> submits an interrupt URB and then cancels it 150 us later? The same
> thing shows up in the usbmon traces.
>
>
>> [ 420.741605] usb 1-5:1.0: uevent
>> [ 420.741957] usb 1-5: uevent
>> [ 420.745592] usb 1-5:1.0: uevent
>> [ 420.807880] ehci_hcd 0000:00:1d.7: reused qh f6ffe280 schedule
>> [ 420.807894] usb 1-5: link qh1024-0001/f6ffe280 start 1 [1/0 us]
>>
>
> Now ehci-hcd tried to re-enable the periodic schedule. Note that
> this is 70 ms after it was supposed to be disabled.
>
>
>> [ 420.808780] ehci_hcd 0000:00:1d.7: force halt; handhake f7c6a024
>> 00004000 00000000 -> -110
>>
>
> This error message means that the disable request from 70 ms earlier
> hasn't taken effect. It looks like a nasty hardware bug -- the
> controller is supposed to disable the schedule no more than 2 ms after
> being told to do so.
>
> Has this device ever worked with any earlier kernels?
>
I only tried 2.6.30.9 and 2.6.31.4, both of them is affected by the same
problem but sometimes it works without a problem so I think that this
can be interpreted as *at-least-working* on those kernels from time to time.
> A little more debugging information could confirm this. After the
> error occurs, go into /sys/kernel/debug/usb/ehci/0000:00:1d.7 and post
> a copy of the "registers" file. If there's anything of interest in the
> other files, post them too.
>
OK I'll look at them tomorrow, Thanks.
next prev parent reply other threads:[~2009-10-21 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 6:55 uvcvideo causes ehci_hcd to halt Ozan Çağlayan
2009-10-13 14:53 ` Alan Stern
2009-10-14 8:16 ` Ozan Çağlayan
2009-10-20 8:29 ` Ozan Çağlayan
2009-10-20 15:07 ` Alan Stern
2009-10-21 8:22 ` Ozan Çağlayan
2009-10-21 15:07 ` Alan Stern
2009-10-21 15:38 ` Ozan Çağlayan [this message]
2009-10-21 17:27 ` Laurent Pinchart
2009-10-21 20:09 ` Ozan Çağlayan
2009-10-21 23:38 ` Laurent Pinchart
2009-10-22 1:36 ` Alan Stern
2009-10-22 10:31 ` Ozan Çağlayan
2009-10-22 14:05 ` Alan Stern
2009-10-22 15:56 ` Ozan Çağlayan
2009-10-22 20:03 ` Alan Stern
2009-10-23 7:18 ` Ozan Çağlayan
2009-10-23 22:14 ` Alan Stern
2009-10-24 7:49 ` Ozan Çağlayan
2009-10-24 12:04 ` Alan Stern
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=4ADF2B06.7090801@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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