[pvrusb2] pvrusb2 timeout?

[Dan Bodoh]

On Thu, Aug 21, 2008 at 9:14 AM, Mike Isely <isely at isely.net> wrote:
>
> On Wed, 20 Aug 2008, Dan Bodoh wrote:
>
>> Any ideas?  This timeout has occurred occasionally, but now twice in
>> the last couple of days.  I'm running Ubuntu 8.04 with stock drivers
>> (2.6.24-19).
>>
>
> it simply got stuck and never recovered.  Unfortunately I've never seen
> the problem happen and nobody else has seen it either, so nothing ever
> developed from this.  But what you are saying here sounds like the same
> issue.

After sending this last night, I found that it actually happened
several times over the past few days, ending up with some recordings
at 0 length.  Every time in the past when I noticed this, I had
rebooted everything immediately, and the problem went away.  This
time, I hadn't rebooted, so the problem stuck around.  Strange thing
is, some recordings failed completely, some worked perfectly fine, and
some didn't record at all during this "flaky" time.  Last night, after
this post, I rebooted everything.

Prior to this most recent event, it's been months since I've seen this problem.

> Another thing to consider:  Has anything recently changed in your
> hardware / software?  Did this problem just suddenly start happening, or

No changes in the last few days that would directly correlate.  Within
the last month, I did updated Ubuntu, but that didn't include a kernel
or myth update.  I'm running on the stable 8.04 (no 'proposed' repo).

>> In the kernel logs - nothing at 20:00, but first message after 20:00
>> is at 20:41:
>>
>> Aug 20 20:41:05 mythbox kernel: [888366.618809] pvrusb2: Encoder timed
>> out waiting for us; arranging to retry
>> Aug 20 20:41:05 mythbox kernel: [888366.618820] pvrusb2: Encoder command: 0x82
>> Aug 20 20:41:05 mythbox kernel: [888366.619087] pvrusb2: Error
>> recovery initiated
>> Aug 20 20:41:05 mythbox kernel: [888366.619091] pvrusb2: Retrying
>> device reconfiguration
>
> Unfortunately that message is "normal".  Every once in a while the
> encoder chip will wedge itself when we try to stream with it.  This
> behavior has been observed for YEARS, and I've never been able to find
> out the trigger.  However the driver detects this and recovers by
> reloading and reconfiguring the encoder.  The whole recovery happens in
> a second or two.  This timeout only ever happens at all at the moment
> streaming is started.  Once it is going, I've never seen the encoder
> crash.  The upshot of all this is that while it's an interesting clue
> that this happened at the point when you got the backend timeout, this
> might not be the "smoking gun".


You may have misunderstood.  This message coincided with the point in
time when my failed recording successfully restarted (41 minutes in to
the program).  So whatever code is behind this message "fixed" the
problem.

Dan Bodoh