lirc 0.8.0 pre1 crashing with modprobe lirc_i2c on gentoo 2.6.15

[<do...@su...>]

Hello,

I'm trying to get lirc working on my HTPC system. It runs amd64 Gentoo 
with kernel 2.6.15. I'm using a Hauppauge PVR-150 non-MCE which I had 
working fine in my previous enironment.

It compiled fine from gentoo's portage, but it's kernel modules doesn't 
load as nice. modprobe lirc_dev works fine:

lirc_dev: IR Remote Control driver registered, at major 61

but modprobe lirc_i2c produces some kind of crash:

lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150))
ivtv0: i2c attach to card #0 ok [client=Hauppauge IR (PVR150), addr=71]
lirc_dev: lirc_register_plugin: sample_rate: 10
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
<ffffffff802404ce>{vsnprintf+145}
PGD 184ba067 PUD 1b3bd067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in: lirc_i2c lirc_dev snd_seq snd_hda_intel snd_hda_codec 
snd_pcm snd_timer snd snd_page_alloc ivtv i2c_algo_bit tda9887 wm8775 
cx25840 firmware_class tuner tveeprom i2c_core nvidia forcedeth
Pid: 6167, comm: modprobe Tainted: P      2.6.15-gentoo #7
RIP: 0010:[<ffffffff802404ce>] <ffffffff802404ce>{vsnprintf+145}
RSP: 0018:ffff810011893a08  EFLAGS: 00010206
RAX: 0000000000000000 RBX: ffff810011893a68 RCX: ffff810011893a68
RDX: 0000000000000000 RSI: 0000000000000014 RDI: ffff810018265a48
RBP: 00000000fffffff4 R08: 0000000000000000 R09: 0000000000000286
R10: 0000000000000000 R11: 0000000000000246 R12: ffff810018265a48
R13: 0000000000000000 R14: ffffffff88572ac2 R15: ffff810018265a5b
FS:  00000000005fd2a0(0000) GS:ffffffff80594800(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000012737000 CR4: 00000000000006e0
Process modprobe (pid: 6167, threadinfo ffff810011892000, task 
ffff81001af59780)
Stack: 0000000000000014 ffff810018265a48 0000000000000000 ffff810018265980
00000000fffffff4 ffff810015e08800 0000000000000000 ffffffff88572ac2
0000000003d00000 ffffffff802a590c
Call Trace:<ffffffff802a590c>{class_device_create+269} 
<ffffffff80138631>{printk+141}
<ffffffff801acf4c>{sysfs_make_dirent+25} 
<ffffffff801add2d>{sysfs_create_link+201}
<ffffffff8857163e>{:lirc_dev:lirc_register_plugin+877}
<ffffffff885769a0>{:lirc_i2c:ir_attach+690} 
<ffffffff88576a89>{:lirc_i2c:ir_probe+180}
<ffffffff884ac595>{:i2c_core:i2c_add_driver+176} 
<ffffffff88576caf>{:lirc_i2c:init_module+14}
<ffffffff80151a71>{sys_init_module+246} <ffffffff8010f8da>{system_call+126}


  Code: 80 38 00 0f 84 0a 05 00 00 48 8b 44 24 10 0f b6 00 3c 25 74
  RIP <ffffffff802404ce>{vsnprintf+145} RSP <ffff810011893a08>
  CR2: 0000000000000000


Don't know what this means, but some of you developers might...

I'd be glad to help you tracking this bug, I just don't know what to do 
about it. Please help me help you :-)

Best regards
Rickard Borgmäster
Sweden