[mythtv-users] imon error floods my system logs

Jarod Wilson jarod at wilsonet.com
Mon Feb 7 06:44:23 UTC 2011


On Feb 6, 2011, at 2:05 AM, Neil Salstrom wrote:

> On Mon, Jan 31, 2011 at 11:20 AM, Jarod Wilson <jarod at wilsonet.com> wrote:
>> 
>> 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.
> 
> I'm now running 2.6.37 and something similar happened tonight:
> 
> Feb  5 20:18:39 htpc kernel: [19219.920769] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:18:39 htpc kernel: [19219.928761] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:18:39 htpc kernel: [19219.936750] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> 
> There is nothing just before this flood of lines to indicate what
> happened.  This however eventually occurred:
> 
> Feb  5 20:28:02 htpc kernel: [19783.476962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.484960] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.485975] imon:send_packet: packet
> tx failed (-32)
> Feb  5 20:28:02 htpc kernel: [19783.490035] imon:vfd_write: send
> packet failed for packet #0
> Feb  5 20:28:02 htpc kernel: [19783.492962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.500962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.508961] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.516962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.524961] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.532962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.540962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.548962] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.556959] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.564961] imon 2-7:1.0: imon
> usb_rx_callback_intf0: status(-32): ignored
> Feb  5 20:28:02 htpc kernel: [19783.570716] usb 2-7: USB disconnect, address 2
> Feb  5 20:28:02 htpc kernel: [19783.605795] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:02 htpc kernel: [19783.730782] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:02 htpc kernel: [19783.855756] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:03 htpc kernel: [19783.980760] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:03 htpc kernel: [19784.061043] usb 2-7: new low speed USB
> device using ohci_hcd and address 3
> Feb  5 20:28:03 htpc kernel: [19784.105761] imon:vfd_write: no iMON
> device present

Hrm. Not sure what triggered the thing going out to lunch, but a disconnect
from usb isn't good.


> Feb  5 20:28:03 htpc kernel: [19784.197979] usb 2-7: New USB device
> found, idVendor=15c2, idProduct=ffdc
> Feb  5 20:28:03 htpc kernel: [19784.197988] usb 2-7: New USB device
> strings: Mfr=0, Product=0, SerialNumber=0
> Feb  5 20:28:03 htpc kernel: [19784.201256] input: iMON Panel, Knob
> and Mouse(15c2:ffdc) as
> /devices/pci0000:00/0000:00:0b.0/usb2/2-7/2-7:1.0/input/input4
> Feb  5 20:28:03 htpc kernel: [19784.217383] imon 2-7:1.0: Unknown
> 0xffdc device, defaulting to VFD and iMON IR (id 0x00)

And you're subject to the bug that doesn't properly configure ffdc devices,
and possibly one other buglet that was only recently fixed, so if you would,
try the imon driver using media_build. Not certain whether or not it will
actually make a difference though.


> Feb  5 20:28:03 htpc kernel: [19784.217406] Registered IR keymap rc-imon-pad
> Feb  5 20:28:03 htpc kernel: [19784.217696] input: iMON Remote
> (15c2:ffdc) as /devices/pci0000:00/0000:00:0b.0/usb2/2-7/2-7:1.0/rc/rc0/input5
> Feb  5 20:28:03 htpc kernel: [19784.217794] rc0: iMON Remote
> (15c2:ffdc) as /devices/pci0000:00/0000:00:0b.0/usb2/2-7/2-7:1.0/rc/rc0
> Feb  5 20:28:03 htpc kernel: [19784.225257] imon 2-7:1.0: iMON device
> (15c2:ffdc, intf0) on usb<2:3> initialized
> Feb  5 20:28:03 htpc kernel: [19784.230800] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:03 htpc kernel: [19784.355773] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:03 htpc kernel: [19784.480897] imon:vfd_write: no iMON
> device present
> Feb  5 20:28:03 htpc kernel: [19784.605757] imon:vfd_write: no iMON
> device present
> 
> The last four lines now repeat until the drive is full....

Weird. Wouldn't expect to see those still after the driver re-loaded, but that
actually *could* be a side-effect of one of the ffdc-specific bugs that was
fixed in 2.6.38-rc5 or so (and in the driver you'd get using media_build).

Could certainly rate-limit the warnings, but it'd be nice if we can figure out
why we're getting the warnings in the first place.

-- 
Jarod Wilson
jarod at wilsonet.com





More information about the mythtv-users mailing list