licd suddenly stops working...
#1
The last week suddenly my remote stops working after a while (I have still not found what trickers it)

Anyway I can see that when the case is that I have not only the /dev/lirc0 but now a new /dev/lirc1. When I looked in my syslog I see:

Code:
Nov 16 11:35:19 Antec kernel: [ 1921.513987] imon usb_rx_callback_intf0: status(-75): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.537981] imon usb_rx_callback_intf0: status(-84): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.537994] lirc_imon: send_packet: packet tx failed (-71)
Nov 16 11:35:19 Antec kernel: [ 1921.537999] lirc_imon: vfd_write: send packet failed for packet #1
Nov 16 11:35:19 Antec kernel: [ 1921.561980] imon usb_rx_callback_intf0: status(-84): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.585977] imon usb_rx_callback_intf0: status(-84): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.609975] imon usb_rx_callback_intf0: status(-84): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.633972] imon usb_rx_callback_intf0: status(-84): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.649976] lirc_imon: send_packet: packet tx failed (-71)
Nov 16 11:35:19 Antec kernel: [ 1921.649981] lirc_imon: vfd_write: send packet failed for packet #0
Nov 16 11:35:19 Antec kernel: [ 1921.657969] imon usb_rx_callback_intf0: status(-84): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.672061] hub 8-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
Nov 16 11:35:19 Antec kernel: [ 1921.672067] usb 8-1: USB disconnect, address 2
Nov 16 11:35:19 Antec kernel: [ 1921.673968] imon usb_rx_callback_intf0: status(-108): ignored
Nov 16 11:35:19 Antec kernel: [ 1921.696297] imon_disconnect: iMON device (intf0) disconnected
Nov 16 11:35:19 Antec kernel: [ 1921.754654] lirc_imon: vfd_write: no iMON device present
Nov 16 11:35:19 Antec kernel: [ 1921.879685] lirc_imon: vfd_write: no iMON device present
Nov 16 11:35:20 Antec kernel: [ 1921.936022] usb 8-1: new low speed USB device using uhci_hcd and address 3
Nov 16 11:35:20 Antec kernel: [ 1922.004617] lirc_imon: vfd_write: no iMON device present
Nov 16 11:35:20 Antec kernel: [ 1922.092078] usb 8-1: configuration #1 chosen from 1 choice
Nov 16 11:35:20 Antec kernel: [ 1922.094992] lirc_dev: lirc_register_driver: sample_rate: 0
Nov 16 11:35:20 Antec kernel: [ 1922.095040] lirc_imon: Registered iMON driver (lirc minor: 1)
Nov 16 11:35:20 Antec kernel: [ 1922.095104] input: iMON PAD IR Mouse (15c2:ffdc) as /devices/pci0000:00/0000:00:1d.2/usb8/8-$
Nov 16 11:35:20 Antec kernel: [ 1922.106196] imon_set_ir_protocol: MCE IR protocol not supported on this device, using iMON p$
Nov 16 11:35:20 Antec kernel: [ 1922.106202] lirc_imon: iMON device (15c2:ffdc, intf0) on usb<8:3> initialized
Nov 16 11:35:20 Antec lircd-0.8.6[1664]: caught signal
Nov 16 11:35:20 Antec kernel: [ 1922.110458] lirc_imon: IR port closed
Nov 16 11:39:18 Antec kernel: [ 2160.308042] INFO: task LCDd:1157 blocked for more than 120 seconds.
Nov 16 11:39:18 Antec kernel: [ 2160.308046] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 16 11:39:18 Antec kernel: [ 2160.308050] LCDd          D 000015b6     0  1157      1 0x00000000
Nov 16 11:39:18 Antec kernel: [ 2160.308057]  eb67deec 00000086 c012a578 000015b6 00000000 c0848760 eb6228ec c0848760
Nov 16 11:39:18 Antec kernel: [ 2160.308066]  87d8d95d 000001bf c0848760 c0848760 eb6228ec c0848760 c0848760 eeb4ce00
Nov 16 11:39:18 Antec kernel: [ 2160.308076]  87d89602 000001bf eb622640 eebe9820 eebe9824 ffffffff eb67df18 c058c1f6
Nov 16 11:39:18 Antec kernel: [ 2160.308085] Call Trace:
Nov 16 11:39:18 Antec kernel: [ 2160.308095]  [<c012a578>] ? default_spin_lock_flags+0x8/0x10
Nov 16 11:39:18 Antec kernel: [ 2160.308101]  [<c058c1f6>] __mutex_lock_slowpath+0xd6/0x140
Nov 16 11:39:18 Antec kernel: [ 2160.308106]  [<c058c5e7>] ? do_nanosleep+0x97/0xc0
Nov 16 11:39:18 Antec kernel: [ 2160.308110]  [<c058c105>] mutex_lock+0x25/0x40
Nov 16 11:39:18 Antec kernel: [ 2160.308122]  [<f8863ed5>] vfd_write+0x45/0x1f0 [lirc_imon]
Nov 16 11:39:18 Antec kernel: [ 2160.308128]  [<c02f5914>] ? security_file_permission+0x14/0x20
Nov 16 11:39:18 Antec kernel: [ 2160.308135]  [<c0208942>] vfs_write+0xa2/0x1a0
Nov 16 11:39:18 Antec kernel: [ 2160.308141]  [<f8863e90>] ? vfd_write+0x0/0x1f0 [lirc_imon]
Nov 16 11:39:18 Antec kernel: [ 2160.308146]  [<c0354699>] ? copy_to_user+0x39/0x130
Nov 16 11:39:18 Antec kernel: [ 2160.308151]  [<c0209262>] sys_write+0x42/0x70
Nov 16 11:39:18 Antec kernel: [ 2160.308155]  [<c01033ec>] syscall_call+0x7/0xb
Nov 16 11:39:18 Antec kernel: [ 2160.308171] INFO: task lircd:1664 blocked for more than 120 seconds.
Nov 16 11:39:18 Antec kernel: [ 2160.308174] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 16 11:39:18 Antec kernel: [ 2160.308177] lircd         D 000027c2     0  1664      1 0x00000000
Nov 16 11:39:18 Antec kernel: [ 2160.308182]  ddab9e98 00000082 d78a6000 000027c2 00000000 c0848760 e8a0756c c0848760
Nov 16 11:39:18 Antec kernel: [ 2160.308191]  86de9fde 000001bf c0848760 c0848760 e8a0756c c0848760 c0848760 e8a80540
Nov 16 11:39:18 Antec kernel: [ 2160.308200]  00000000 000001bf e8a072c0 f8850ca8 f8850cac ffffffff ddab9ec4 c058c1f6

Any ideas to what is going on and where to look?

sudo service lirc restart does not change anything. Also I can not rmmod lirc_imon as module is still busy...

I'm running Ubuntu 10.04
Reply
#2
I'm pretty sure that it has todo with the usb.

When the lirc is stuck, I can not list usb (lsusb) - then the terminal just stucks with a blinking cursor...

I have tried to restart the whole usb with modproble -r uhci_hcd or ehci_hcd but that just gives me a:

Code:
FATAL: Module ehci_hcd is builtin
Reply
#3
The problem here is two drivers will be loaded:

imon: from kernel
lirc_imon: from lirc

you must blacklist one of the drivers, both together will never work.

There IR drivers will go all to the kernel in the future, so lirc will not more shipped with drivers, so i prefer to blacklist the lirc drivers and setup lirc to work with kernel drivers (devinput/ linux-input)
greetings, Stephan

Image

Image
Reply
#4
I have now blacklisted the imon driver, but the problem came back again?!?

I will try and switch to the imon driver instead of the lirc_imon driver, but I probably need to make a new remote configuration file... I will return with info on that.

Still weird to me that lsusb lucks up??
Reply
#5
I am using Ubuntu 10.04 and not 10.10 and as such the imon kernel module is not availble...

Code:
~$ modprobe imon
FATAL: Module imon not found.

https://bugs.launchpad.net/ubuntu/+sourc...bug/666493

So any new ideas??
Reply
#6
Murphys law, imon display just locked up again with the same syslog messages:

Code:
kernel: [ 7091.461995] imon usb_rx_callback_intf0: status(-75): ignored
kernel: [ 7091.480045] hub 8-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
...
[\CODE]

ORIGINAL MESSAGE:
[quote]
I have now been running the system for 2 days (Dharma RC1) with

[CODE]
<haslcd>false</haslcd>

in guisettings.xml and so far no lock up... So is this problem to do with the commands sent to LCDproc server by xbmc??

I have still LCDd service running and the display is now just showing the LCDproc server info on the display

If the problem is with the commands sent by xbmc, how can I then test it closer??
[/quote]
Reply
#7
Uhm, are you by any chance using an usb hub, maybe self powered? If so, try a direct port. If not, it seems the port is disabling itself: m/b issue?
Reply
#8
No hub - it's an imon VFD display directly connected to the usb connector on the motherboard...

It has worked just fine until maybe 14 days ago, but will try and look on the connection to the mb :/ I also tried to roll back to kernel 2.6.32.23 (which is from when I know that it was working fine...), but still same lock up
Reply
#9
I read somewhere else (Imon forum I think) about maybe the same problem, just on windows - and the supporter suggested to change usb connection.

Before trying that I tried to make a complete cold reboot - meaning to physical remove the power cord to the media center for more than 20 sec.. I did this because the usb still have a current even when shut down. And this seem to have solved the case?!?

I have got it ones, but did the complete power off again, and have not had it since (more than a week now), so I guess that the Soundgraph imon VFD module apparently is a bit tweaky in how it talks with the usb interface.

I hate periodic faults...
Reply

Logout Mark Read Team Forum Stats Members Help
licd suddenly stops working...0