Created attachment 385743 [details] Oops message taken from dmesg for lirc_sir Description of problem: Loading the lirc modules lirc_sir and lirc_serial causes kernel oopses. Version-Release number of selected component (if applicable): 2.6.31.9-174.fc12.i686.PAE How reproducible: Allways Steps to Reproduce: 1. service irda stop 2. modprobe -rv irda 3. setserial /dev/ttyS0 uart none 4. setserial /dev/ttyS1 uart none 5. modprobe -v lirc_serial 6. rmmod lirc_serial 7. insmod /lib/modules/2.6.31.9-174.fc12.i686.PAE/kernel/drivers/input/lirc/lirc_sir.ko irq=3 io=0x2f8 Actual results: 5 and 7 causes kernel oopses and modules will not unload. Expected results: Starting "mode2" should print out numbers for pulses, when pressing keys on a remote control. Additional info: Works with the Fedora 8 LiveCD. I get the same results on different machines.
Created attachment 385744 [details] Oops message taken from dmesg for lirc_serial
Same happens to my x86_64 system, with the same kernel-version. Also tried to load the modules at runlevel 1, but that didn't help either. This system didn't have ir-hardware though. The Fedora 8 LiveCD works fine at this system as well.
I have no updated my system (yum update) and now have the kernel version kernel-PAE-2.6.31.12-174.2.19.fc12.i686, but the problem persists.
Yesterday I updated my system. The current kernel is kernel-PAE-2.6.32.9-70.fc12.i686. Problem persists.
Is this still a problem? lirc_serial at least works perfectly fine on my end under Fedora 12. Less certain about lirc_sir.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created attachment 459521 [details] Oops on F14 I've hit this on F14. Attaching the Oops.
Please try this kernel here, its got a few core lirc_dev fixes in it, one of which I think may fix this oops (they were targeted at similar oopses w/different hardware): http://kojipkgs.fedoraproject.org/packages/kernel/2.6.35.8/53.fc14/
Well no more Oops but still not working.(I get the same issue when I try git lirc drivers as well). [ 19.710406] lirc_dev: IR Remote Control driver registered, major 249 [ 19.753366] lirc_sir: module is from the staging directory, the quality is unknown, you have been warned. [ 19.756924] lirc_register_driver: dev pointer not filled in! [ 19.756934] lirc_sir: init_chrdev() failed.
In Fedora 14 the lirc_serial module seems to load fine now (haven't tested with hardware though). The two machines tested are the same as before. I also still get kernel oopses when I try to load the lirc_sir module.
I also tried the 2.6.35.8-53 kernel. I got the same result as ruskie for the lirc_sir module. The result for the lirc_serial is the same as for the current kernel (2.6.35.6-48). I only tested this on the i686-system with ir-hw, not on the x86_64-system.
I just committed some changes to the lirc git tree to get the dev pointer filled in by lirc_sir, but would like folks to test an out-of-tree build before I throw it into the Fedora kernel, just in case its still not functional and/or crashes. :)
Jarod, is this fixed now?
For what it is worth, I encountered the same problem ("lirc_register_driver: dev pointer not filled in!") using kernel 3.0.4 and found that the problem does not appear when using lirc_dev/lirc_sir compiled from the latest lirc git. I am using a vanilla kernel and Debian userspace, but since this appears to be a kernel-only issue, I thought the information might be useful.
given the info in comment #14, I'm going to move this to an f15 bug, because it's unlikely at this stage in its lifecycle that we'll make any big changes to it beyond security fixes. Jarod, you want to make sure that we've got the latest lirc in f15/f16 ?
Comment #14 suggests the fix I threw into the lirc out-of-tree tree did indeed fix the problem with lirc_sir (lirc_serial has long since been fixed), so yeah, I just need to push that fix upstream. A bit tied up with other things right now, but I'll put it on my upstream TODO list for 3.2, and can add a backport to fedora kernel builds if need be.
FIIIIIIIIXXXXXXXXXXXXXXXXXX MEEEEEEEEEEEEEEEEE. PPPAAAAAAAAATTTTTTTTTTTTCCCCCCCCCCCCHHHHHHHHHEEEEEEEEEEESSSSSSSSSSSSSSS
Finally got the patch sent upstream, hopefully gets into 3.5... http://patchwork.linuxtv.org/patch/11579/
Fixed in 3.6-rc1.