Steven Ellis wrote:
> Hans Verkuil wrote:
>   
>>> Hallo Hans!
>>>
>>>     
>>>       
>>>> I've started work on this problem yesterday. I discovered that the
>>>> MPEG data is placed at the correct memory location so the shift
>>>> happens either in the DMA handling (most likely) or in the internal
>>>> buffer handling of the driver. I can easily reproduce it, so that
>>>> helps a lot. I hope I can find the cause quickly. I have several
>>>> ideas, but it needs more debugging and tracing.
>>>>       
>>>>         
>>> Did you find the cause for the bug mentioned above? I don't want to
>>> rush, I'm just a bit curious...
>>>     
>>>       
>> I'm slowly closing in on it. It's not as easy to reproduce as I thought so
>> it is slow going. The bug is probably in the dma_from_device() function in
>> ivtv-irq.c and is probably related to somehow incorrect handling of a DMA
>> error. I have to wait for it to happen again before I can be more certain.
>>
>>  
>>     
>
> Did this problem get resolved. I am starting to see exactly the same
> problem with both PVR 150 and PVR 500 units that my customers are using.
> The cases are well ventilated and the cards don't appear to be at all hot.
>   
Just been trying to debug this. A simple re-boot won't fix the issues. I
need to power the box off for a couple of minutes and then all of the
artefacts go away. Is there a chance that the firmware isn't always
cleanly reloading.

Not seeing any DMA errors on the box at all.

Any recommendations on the best debug mode to run the drive in to get
some reasonable information about possible DMA issues?

Steve


_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to