[mythtv-users] imon error floods my system logs

[Jarod Wilson]

On Jan 31, 2011, at 1:57 PM, Neil Salstrom wrote:

> On Mon, Jan 31, 2011 at 7:44 AM, Jarod Wilson <jarod at wilsonet.com> wrote:
>> On Jan 27, 2011, at 1:27 AM, Neil Salstrom wrote:
>> 
>>> I guess this is somewhat mythtv related...  My frontend / backend is
>>> in a Antec fusion case with a VFD.  I use the in kernel imon module
>>> (currently 2.6.35.10 which I compile) and I've had a nasty but that
>>> can cripple my system.  Once very few weeks my VFD will just show
>>> garbage and my system logs will fill up with this:
>>> 
>>> mythtv at htpc:~$ tail /var/log/messages
>>> Jan 21 23:26:45 htpc kernel: [317337.518350] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.526349] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.534348] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.542350] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.550348] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.558345] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.566347] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.574349] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.582346] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> Jan 21 23:26:45 htpc kernel: [317337.590350] imon 1-7:1.0: imon
>>> usb_rx_callback_intf0: status(-32): ignored
>>> 
>>> It will over the course of a day or so fill up several gigs and bring
>>> my system to its knees.  There is nothing in any of the logs that
>>> indicates what starts this.  Everything seems normal and then a flood
>>> of these messages.
>>> 
>>> Has anyone experienced this?  How can I prevent it from happening?
>> 
>> There was a fix for this issue committed at some point, but I think it
>> was after 2.6.35.x. Try a newer kernel or just newer imon driver code.
>> If its still broken, I can look into it further.
>> 
>> This applies for trying newer imon driver code:
>> 
>> http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
>> 
> 
> Thanks.  I'll up to a 2.6.36.x kernel and see if it clears things up.
> 
> If things go south I'll let you know!

If they do, please try the media_build directions and/or 2.6.37. I'm not
sure if the fix went into 2.6.36 or not. Its definitely there for 37 (and
the media_build bits) though.

-- 
Jarod Wilson
jarod at wilsonet.com