Kodi Community Forum

Full Version: XBMCubuntu irc reciver freeze up after some time of use
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
The irc reciver freeze up, and will not accept any command from my controll, only thing that helps is to restart xbmc.

the reciver is:
ID 1934:5168 Feature Integration Technology Inc. (Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiver


some errors from the syslog
Feb 13 19:37:23 xbmc-desktop lircd-0.9.0[596]: error reading from /dev/lirc0 (ret -1, expected 4)
Feb 13 19:37:23 xbmc-desktop lircd-0.9.0[596]: No such device
Feb 13 19:37:23 xbmc-desktop kernel: [13612.618490] hub 1-5:1.0: port 1 disabled by hub (EMI?), re-enabling...
Feb 13 19:37:23 xbmc-desktop kernel: [13612.618737] usb 1-5.1: USB disconnect, device number 3
Feb 13 19:37:23 xbmc-desktop kernel: [13612.634324] BUG: unable to handle kernel NULL pointer dereference at 00000034
Feb 13 19:37:23 xbmc-desktop kernel: [13612.634339] IP: [<f833b6de>] show_protocols+0x10e/0x160 [rc_core]
Feb 13 19:37:23 xbmc-desktop kernel: [13612.634356] *pde = 7f8dd067
Feb 13 19:37:23 xbmc-desktop kernel: [13612.634362] Oops: 0000 [#1] SMP


Thats what I remeber for now to put, just ask for more info if its something i have forgotten'


By the way, thanks for your awsome work

regards Alf Tonny
I was to quic to selebrate, the lirc0 device just disepair after some time when you wathing movies, sometime after 3-4 movies and sometime less, and the only thing that helps is restart
And I dont think its related to the Lirc Device Increment Bug after sustend, sins the box have not gone to sleep-.Wink

I think the problem is releated to this tread
http://forum.xbmc.org/archive/index.php/t-102435.html

Feb 16 18:21:47 xbmc-desktop lircd-0.9.0[614]: error reading from /dev/lirc0 (ret -1, expected 4)
Feb 16 18:21:47 xbmc-desktop lircd-0.9.0[614]: No such device
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.571223] hub 1-5:1.0: port 1 disabled by hub (EMI?), re-enabling...
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.571471] usb 1-5.1: USB disconnect, device number 3
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588190] BUG: unable to handle kernel NULL pointer dereference at 00000034
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588207] IP: [<f83316de>] show_protocols+0x10e/0x160 [rc_core]
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588229] *pde = 7e961067
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588237] Oops: 0000 [#1] SMP
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588247] Modules linked in: rfcomm bluetooth dm_crypt autofs4 snd_hda_codec_hdmi snd_hda_codec_realtek nvidia(P) arc4 ir_lirc_codec lirc$
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588344]
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588352] Pid: 1749, comm: cat Tainted: P 3.0.0-16-generic #28-Ubuntu To Be Filled By O.E.M. To Be Filled By O.E.M./To be fill$
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588365] EIP: 0060:[<f83316de>] EFLAGS: 00010202 CPU: 0
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588375] EIP is at show_protocols+0x10e/0x160 [rc_core]
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588381] EAX: 00000000 EBX: f3769c00 ECX: f1d09000 EDX: f0822000
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588387] ESI: f83315d0 EDI: c1570b6c EBP: f0823f10 ESP: f0823ed4
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588394] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588400] Process cat (pid: 1749, ti=f0822000 task=f3cfa640 task.ti=f0822000)
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588405] Stack:
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588409] c17b6184 00000000 f510c120 000080d0 00000028 c17b6180 f3769d90 f1d09000
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588424] f3a938c0 00020000 7f87f067 f6d85750 f83350ac f83315d0 c1570b6c f0823f20
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588439] c1344e2f f6d85750 f1ea9180 f0823f3c c1186f1e 00000000 f3769c08 f6e6e0c0
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588453] Call Trace:
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588469] [<f83315d0>] ? rc_g_keycode_from_table+0xd0/0xd0 [rc_core]
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588481] [<c1344e2f>] dev_attr_show+0x1f/0x50
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588492] [<c1186f1e>] fill_read_buffer.isra.7+0x4e/0xd0
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588500] [<c118701d>] sysfs_read_file+0x7d/0x90
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588509] [<c112964c>] vfs_read+0x8c/0x160
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588517] [<c1186fa0>] ? fill_read_buffer.isra.7+0xd0/0xd0
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588525] [<c112975d>] sys_read+0x3d/0x70
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588533] [<c152eaa4>] syscall_call+0x7/0xb
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588538] Code: 5e 5f 5d c3 90 8b 43 08 89 34 24 c7 44 24 04 c3 42 33 f8 89 44 24 08 e8 21 69 f5 c8 01 c6 e9 7c ff ff ff 66 90 8b 83 a8 0$
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588617] EIP: [<f83316de>] show_protocols+0x10e/0x160 [rc_core] SS:ESP 0068:f0823ed4
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588631] CR2: 0000000000000034
Feb 16 18:21:47 xbmc-desktop kernel: [ 7563.588644] ---[ end trace c285c2f3c09645a2 ]---
Feb 16 18:21:47 xbmc-desktop lircd-0.9.0[614]: caught signal
is it just me that experience this bug?

ill starting to think this is a bug with the lirc version, that make it crashing. Or something with the kernel.

im goint to invstigate abit more and if i find any solutions i get back with it here
Sorry, have not have had any luck to find out what happening with this, this bug is still in rc2.
Experience something simular here to. I have seen some errero regarding lirc when i shutdown the machine to. Sometimes it takes 5/10 clicks on my remote before i get a respons, usally only when i have booted the machine. Have not had the time to debug it more do.
Im starting to think this is a bug in this lirc version.

Maybe could try to upgrade the kernel?
Hai, i also thinks this is a lirc bug.

try the following.

cat /var/log/Xorg.0.log | grep "input device"

change in your lirc config your device

this is for me correct

DEVICE="/dev/input/event3"

also, sometimes the input changes after reboot, so if your remote does not work, check your input device again.

more info, look here: http://www.lirc.org/html/devinput.html
thctlo ty for your answer here, that unfortantly did not helt me so much.

I have now installet linux-image 3.2, and will do some testing, and I will give back here when i know more, the problem with this bug, is that is happening realy randomly. sometime its work in 2-3 days in a row with out crashing, and sometime its only work for 4-5 hours.

I hope upgrade the kernel helped me.


regards Alf Tonny
after some thinking, I belive the lircd driver crashing when you stressing the driver. So maybe to repoduse the bug, is to click allot on the remote controll, and I almost surten the driver crashing. Thats why the lircd crash is abit random. Still testing out the new kernel, have still not crased yet
Ok, after some time of testing with linux-image 3.2 installed, things looking promising, till now I have not experienced any lircd crash yet..

If thing changes, Ill report back here.

Regards Alf Tonny Bätz

(got the kernels from here:

update 7 mars, the update og kernel indeed fixed the problem with crashing lircd for me. This case is solved
(2012-03-06, 19:56)alfton Wrote: [ -> ]Ok, after some time of testing with linux-image 3.2 installed, things looking promising, till now I have not experienced any lircd crash yet..

If thing changes, Ill report back here.

Regards Alf Tonny Bätz

(got the kernels from here:

update 7 mars, the update og kernel indeed fixed the problem with crashing lircd for me. This case is solved

May I ask how you update the image? My own attempt didn't work and I had to roll back to 3.0.