Re: Latest git broken with stable kernel 2.6.36?

[Jarod W. <ja...@wi...>]

On Nov 7, 2010, at 1:33 AM, VDR User wrote:

> On Sat, Nov 6, 2010 at 3:58 PM, Jarod Wilson <ja...@wi...> wrote:
>>> Would appreciate if you can look into the lirc
>>> problem with the latest stable kernel when you get a free moment.
>>> Please let me know if I should provide any other info as well.
>> 
>> Well, I *am* curious why, if you're running 2.6.36, you aren't simply running lirc_serial as built from drivers/staging/lirc/...
> 
> The only drivers I prefer to build from kernel source are ones for
> mainboard support (ethernet, sata, etc).  Drivers for things such as
> remote control, DVB devices, and so on I prefer to build outside of
> the kernel since I find myself needing to patch or change these
> occasionally (which I'd rather do outside of the kernel).
> 
>> Regardless, lirc_serial in the git tree should behave now.
> 
> Just grabbed a fresh git and I'm still getting the same in dmesg:
> 
> lirc_dev: IR Remote Control driver registered, major 254
> BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/23996
> caller is init_timing_params+0x26/0xdc [lirc_serial]
> Pid: 23996, comm: modprobe Tainted: P            2.6.36.amd64-x2.102310.1 #1
> Call Trace:
>  [<c116b7a5>] ? debug_smp_processor_id+0xa1/0xb4
>  [<f8536371>] ? init_timing_params+0x26/0xdc [lirc_serial]
>  [<f853a0f9>] ? lirc_serial_init_module+0xf9/0x2c4 [lirc_serial]
>  [<f853a000>] ? lirc_serial_init_module+0x0/0x2c4 [lirc_serial]
>  [<c1001151>] ? do_one_initcall+0x68/0x106
>  [<c10460f9>] ? sys_init_module+0x77/0x196
>  [<c1002610>] ? sysenter_do_call+0x12/0x26
> lirc_serial: auto-detected active low receiver
> lirc_register_driver: dev pointer not filled in!
> lirc_serial: register_chrdev failed!
> 
> Could it be the fix wasn't adopted into git fully yet, or perhaps I'm
> using the wrong url?
> (git://lirc.git.sourceforge.net/gitroot/lirc/lirc)

I swear I committed and pushed the fix, but I was unable to find it, so
I just committed and pushed the fix a moment ago. This time, I actually
do see it on sf in git. :)

-- 
Jarod Wilson
ja...@wi...