[linux-dvb] dib0700 remote control support fixed

Devin Heitmueller devin.heitmueller at gmail.com
Wed Dec 3 17:35:53 CET 2008


On Wed, Dec 3, 2008 at 11:27 AM, petercarm
<linuxtv at hotair.fastmail.co.uk> wrote:
>
> On Wed, 3 Dec 2008 10:34:02 -0500, "Devin Heitmueller"
> <devin.heitmueller at gmail.com> said:
>> On Wed, Dec 3, 2008 at 10:30 AM, petercarm
>> <linuxtv at hotair.fastmail.co.uk> wrote:
>> > More testing.
>> >
>> > Moving on from the riser card issue, I've now got a fairly predictable
>> > case where warm restart of the box results in endless mt2060 i2c errors.
>> >
>>
>> Hello Peter,
>>
>> Just to be clear, this is in a box that doesn't have the riser card?
>>
>> Does it happen even before you start streaming video?  Or does it
>> occur when you do the first tune?
>>
>> Can you please provide a detailed explanation regarding what that
>> "fairly predictable case" is?
>>
>> Thanks,
>>
>> Devin
>
> This is the case without the riser.  The log showed the failure 8
> seconds after the driver initialized.  Mythtv backend may have started
> in the meantime, but had no current jobs.  It may be related to EIT
> scanning.
>
> So far three times out of four it has failed on issuing "reboot".  It
> has worked every time with a power down before restarting.  I'm doing a
> clean rebuild of the complete test environment to eliminate any cached
> results, just in case.  This will take about 8 hours.

Ok.  That's good to know.  It's possible that the driver does not
clear out all its state when being initialized and the reboot alone
doesn't cut power to the device so there is something that persists
across the reboot.  This would definitely make sense as to why we see
it with this device and not the USB based dib0700 devices.

There are two things that would be useful here I think:

If you can confirm whether the change on November 16th *really* has
anything to do with the failure (by trying snapshots of the v4l-dvb
tree before and after the change).

Add a call to dump_stack() right after the error line in the code, so
we can see what the stack looks like at the time of failure.

I'm glad it's readily reproducible, which will make it easier to
isolate the problem and validate any fix we come up with.

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller



More information about the linux-dvb mailing list