[linux-dvb] Re: Nebula installation and nxt6000 fault
Jamie Honan wrote: #modprobe bttv card=0x68 i2c_hw=1 dmesg output bttv: driver version 0.9.12 loaded bttv: snapshot date 2003-12-08 [e0c8612b] bttv_i2c_xfer+0x9b/0xc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92040] bttvs+0x40/0x4cc0 [bttv] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [c02ecf29] i2c_transfer+0x39/0x80 [kernel] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0ca61a4] master_xfer+0x34/0x50 [dvb-bt8xx] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0dcc269] pll_write+0x59/0xa0 [nxt6000] [e0dccf0b] nxt6000_attach+0x9b/0x200 [nxt6000] [e0c9cc78] try_attach_device+0x38/0x80 [dvb-core] [e0c9cded] probe_device_on_all_busses+0x1d/0x30 [dvb-core] [e0ca42e0] dvb_i2c_mutex+0x0/0x20 [dvb-core] [e0c9cfe9] dvb_register_i2c_device_Rde0504aa+0x59/0x90 [dvb-core] [e0dcd978] __ksymtab+0x0/0x20 [nxt6000] [e0dcd0f0] nxt6000_init+0x20/0x50 [nxt6000] [e0dcce70] nxt6000_attach+0x0/0x200 [nxt6000] [e0dcd070] nxt6000_detach+0x0/0x60 [nxt6000] [c01f5762] sys_init_module+0x652/0x6e0 [kernel] [e0dcd96c] .kmodtab+0x0/0xc [nxt6000] [e0dcc060] nxt6000_write+0x0/0xa0 [nxt6000] [c01e0683] system_call+0x33/0x40 [kernel] This bug is caused by the i2c hardware write routine in the bttv driver. It can't handle writing a zero length message to an i2c address. ough - that's an important issue; some of our frontend driver initiate their probing by a 'i2c ping' - they are looking whether a zero-length/adress-only message is properly acknowledged by the chip... Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Nebula installation and nxt6000 fault
That did the trick. Look forward to the HOWTO. Many thanks. Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian McKerr Sent: Thursday, 11 December 2003 2:57 PM To: [EMAIL PROTECTED] Subject: [linux-dvb] Re: Nebula installation and nxt6000 fault I am installing a Nebula DigiTV board but with a few issues. Have followed the various README's and sailed in the draught of a number of postings in this mailing list but seem stuck. Any help here is greatly appreciated. Thanks in advance. Robert Cook The version of Linux is Mandrake 9.2 with a 2.4.23 kernel (2.4.23-0.rc5.2mdk). Video 4 linux enabled. Installed Video4Linux from video4linux-20031208.tar.gz Installed dvb-kernel/build-2.4 from latest CVS archives Bit of a nightmare sorting out conflicting v4l1-compat.o and v4l2-common.o between V4L and dvb-kernel along with Mandrake installed dvb_mod libraries. Cleaned up stale modules and removed conflicting dvb-kernel modules with priority to V4L. Ran the following commands: #modprobe bttv card=0x68 i2c_hw=1 dmesg output bttv: driver version 0.9.12 loaded bttv: snapshot date 2003-12-08 bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). bttv0: Bt878 (rev 17) at 02:0a.0, irq: 22, latency: 64, mmio: 0xfbefe000 bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem ID is 0071:0101 bttv0: using: Nebula Electronics DigiTV [card=104,insmod option] bttv0: gpio: en=, out= in=00ff00cb [init] bttv0: using tuner=-1 bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 = 35468950 .. ok = #modprobe dvb-bt8xx dmesg output bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). bt878(0): Bt878 (rev 17) at 02:0a.1, irq: 22, latency: 64, memory: 0xfbeff000 DVB: registering new adapter (Neb). = #modprobe nxt6000 modprobe: insmod /lib/modules/2.4.23-0.rc5.2mdkcustom/misc/nxt6000.o failed modprobe: insmod nxt6000 failed dmesg | ksymoops output Unable to handle kernel NULL pointer dereference at virtual address e0c85d24 *pde = Oops: CPU:0 EIP: 0010:[e0c85d24]Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010a86 eax: ebx: 0001 ecx: c000 edx: dad1be60 esi: edi: 0001 ebp: dad1bde0 esp: dad1bdd4 ds: 0018 es: 0018 ss: 0018 Process insmod (pid: 1985, stackpage=dad1b000) Stack: 0001 0001 dad1be04 e0c8612b e0c92000 dad1be60 0001 e0c92000 e0c92040 e0c92004 dad1be60 dad1be24 c02ecf29 e0c92004 dad1be60 0001 dac42000 0014 dad1be74 dad1be3c e0ca61a4 e0c92004 dad1be60 Call Trace: [e0c8612b] bttv_i2c_xfer+0x9b/0xc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92040] bttvs+0x40/0x4cc0 [bttv] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [c02ecf29] i2c_transfer+0x39/0x80 [kernel] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0ca61a4] master_xfer+0x34/0x50 [dvb-bt8xx] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0dcc269] pll_write+0x59/0xa0 [nxt6000] [e0dccf0b] nxt6000_attach+0x9b/0x200 [nxt6000] [e0c9cc78] try_attach_device+0x38/0x80 [dvb-core] [e0c9cded] probe_device_on_all_busses+0x1d/0x30 [dvb-core] [e0ca42e0] dvb_i2c_mutex+0x0/0x20 [dvb-core] [e0c9cfe9] dvb_register_i2c_device_Rde0504aa+0x59/0x90 [dvb-core] [e0dcd978] __ksymtab+0x0/0x20 [nxt6000] [e0dcd0f0] nxt6000_init+0x20/0x50 [nxt6000] [e0dcce70] nxt6000_attach+0x0/0x200 [nxt6000] [e0dcd070] nxt6000_detach+0x0/0x60 [nxt6000] [c01f5762] sys_init_module+0x652/0x6e0 [kernel] [e0dcd96c] .kmodtab+0x0/0xc [nxt6000] [e0dcc060] nxt6000_write+0x0/0xa0 [nxt6000] [c01e0683] system_call+0x33/0x40 [kernel] Code: 8a 00 25 ff 00 00 00 c1 e0 10 09 c1 8b 45 10 89 ce 81 ce 8b EIP; e0c85d24 [bttv]bttv_i2c_sendbytes+14/1e0 = edx; dad1be60 _end+1a8c9d39/20585f39 ebp; dad1bde0 _end+1a8c9cb9/20585f39 esp; dad1bdd4 _end+1a8c9cad/20585f39 Trace; e0c8612b [bttv]bttv_i2c_xfer+9b/c0 Trace; e0c92000 [bttv].data.end+45/60a5 Trace; e0c92000 [bttv].data.end+45/60a5 Trace; e0c92040 [bttv].data.end+85/60a5 Trace; e0c92004 [bttv].data.end+49/60a5 Trace; c02ecf29 i2c_transfer+39/80 Trace; e0c92004 [bttv].data.end+49/60a5 Trace; e0ca61a4 [dvb-bt8xx]master_xfer+34/50 Trace; e0c92004 [bttv].data.end+49/60a5 Trace; e0dcc269 [nxt6000]pll_write+59/a0 Trace; e0dccf0b [nxt6000]nxt6000_attach+9b/200 Trace; e0c9cc78 [dvb-core]try_attach_device+38/80 Trace; e0c9cded [dvb-core]probe_device_on_all_busses+1d/30 Trace; e0ca42e0 [dvb-core]dvb_i2c_mutex+0/20 Trace; e0c9cfe9 [dvb-core]dvb_register_i2c_device+59/90 Trace; e0dcd978 [nxt6000].rodata.end+c9/5d1 Trace; e0dcd0f0 [nxt6000]nxt6000_init+20/50 Trace; e0dcce70 [nxt6000]nxt6000_attach+0/200 Trace; e0dcd070 [nxt6000]nxt6000_detach+0/60
[linux-dvb] Re: Nebula installation and nxt6000 fault
Holger Waechtler wrote: Jamie Honan wrote: #modprobe bttv card=0x68 i2c_hw=1 dmesg output bttv: driver version 0.9.12 loaded bttv: snapshot date 2003-12-08 [e0c8612b] bttv_i2c_xfer+0x9b/0xc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92040] bttvs+0x40/0x4cc0 [bttv] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [c02ecf29] i2c_transfer+0x39/0x80 [kernel] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0ca61a4] master_xfer+0x34/0x50 [dvb-bt8xx] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0dcc269] pll_write+0x59/0xa0 [nxt6000] [e0dccf0b] nxt6000_attach+0x9b/0x200 [nxt6000] [e0c9cc78] try_attach_device+0x38/0x80 [dvb-core] [e0c9cded] probe_device_on_all_busses+0x1d/0x30 [dvb-core] [e0ca42e0] dvb_i2c_mutex+0x0/0x20 [dvb-core] [e0c9cfe9] dvb_register_i2c_device_Rde0504aa+0x59/0x90 [dvb-core] [e0dcd978] __ksymtab+0x0/0x20 [nxt6000] [e0dcd0f0] nxt6000_init+0x20/0x50 [nxt6000] [e0dcce70] nxt6000_attach+0x0/0x200 [nxt6000] [e0dcd070] nxt6000_detach+0x0/0x60 [nxt6000] [c01f5762] sys_init_module+0x652/0x6e0 [kernel] [e0dcd96c] .kmodtab+0x0/0xc [nxt6000] [e0dcc060] nxt6000_write+0x0/0xa0 [nxt6000] [c01e0683] system_call+0x33/0x40 [kernel] This bug is caused by the i2c hardware write routine in the bttv driver. It can't handle writing a zero length message to an i2c address. ough - that's an important issue; some of our frontend driver initiate their probing by a 'i2c ping' - they are looking whether a zero-length/adress-only message is properly acknowledged by the chip... Holger By zero-length/adress-only message do you mean a single i2c write operation consisting only of an address byte with no further data bytes? Niklas -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Nebula installation and nxt6000 fault
This bug is caused by the i2c hardware write routine in the bttv driver. It can't handle writing a zero length message to an i2c address. The kernel shouldn't oops on that, but I think zero-length writes are not allowed. At least the bt878 can't do that in hardware and the specs say: An I2C write transaction consists of sending a START signal, 2 or 3 bytes of data ... (the 2 or 3 bytes include the i2c address, i.e. that means 1 or 2 data bytes). I can catch zero-length writes and return -EINVAL, would that help? Gerd -- You have a new virus in /var/mail/kraxel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Nebula installation and nxt6000 fault
Niklas Peinecke wrote: Holger Waechtler wrote: Jamie Honan wrote: #modprobe bttv card=0x68 i2c_hw=1 dmesg output bttv: driver version 0.9.12 loaded bttv: snapshot date 2003-12-08 [e0c8612b] bttv_i2c_xfer+0x9b/0xc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92040] bttvs+0x40/0x4cc0 [bttv] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [c02ecf29] i2c_transfer+0x39/0x80 [kernel] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0ca61a4] master_xfer+0x34/0x50 [dvb-bt8xx] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0dcc269] pll_write+0x59/0xa0 [nxt6000] [e0dccf0b] nxt6000_attach+0x9b/0x200 [nxt6000] [e0c9cc78] try_attach_device+0x38/0x80 [dvb-core] [e0c9cded] probe_device_on_all_busses+0x1d/0x30 [dvb-core] [e0ca42e0] dvb_i2c_mutex+0x0/0x20 [dvb-core] [e0c9cfe9] dvb_register_i2c_device_Rde0504aa+0x59/0x90 [dvb-core] [e0dcd978] __ksymtab+0x0/0x20 [nxt6000] [e0dcd0f0] nxt6000_init+0x20/0x50 [nxt6000] [e0dcce70] nxt6000_attach+0x0/0x200 [nxt6000] [e0dcd070] nxt6000_detach+0x0/0x60 [nxt6000] [c01f5762] sys_init_module+0x652/0x6e0 [kernel] [e0dcd96c] .kmodtab+0x0/0xc [nxt6000] [e0dcc060] nxt6000_write+0x0/0xa0 [nxt6000] [c01e0683] system_call+0x33/0x40 [kernel] This bug is caused by the i2c hardware write routine in the bttv driver. It can't handle writing a zero length message to an i2c address. ough - that's an important issue; some of our frontend driver initiate their probing by a 'i2c ping' - they are looking whether a zero-length/adress-only message is properly acknowledged by the chip... Holger By zero-length/adress-only message do you mean a single i2c write operation consisting only of an address byte with no further data bytes? yes. This is used when the probed chip has no known id register we can read and when the i2c address is unique. Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Nebula installation and nxt6000 fault
Gerd Knorr wrote: This bug is caused by the i2c hardware write routine in the bttv driver. It can't handle writing a zero length message to an i2c address. The kernel shouldn't oops on that, but I think zero-length writes are not allowed. At least the bt878 can't do that in hardware and the specs say: An I2C write transaction consists of sending a START signal, 2 or 3 bytes of data ... (the 2 or 3 bytes include the i2c address, i.e. that means 1 or 2 data bytes). I can catch zero-length writes and return -EINVAL, would that help? :) yes, - in any case the i2c driver should never hang just because somebody passed invalid messages... We don't know how to identify the sp8872 used in the Microtune frontend, the sp8870 in the Alps TDLB7 frontend and the cx22700 in the Alps TDMB7 - these don't have an id-register. At least the Microtune frontend is used in conjunction with the bt8xx on the Avermedia DVB-T cards. We could initiate a dummy-read and check whether this gets acknowledged, but then these 3 frontend drivers need to get changed. Anybody with an Avermedia DVB-T card willing to contribute this change? Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Nebula installation and nxt6000 fault
Holger Waechtler [EMAIL PROTECTED] writes: I can catch zero-length writes and return -EINVAL, would that help? :) yes, - Ok, I'll fix it that way. in any case the i2c driver should never hang just because somebody passed invalid messages... Of course it shouldn't, I was just not sure how to fix that best and whenever the not-supported zero length writes are in the i2c protocol specs or if that is actually a bt878 limitation. We could initiate a dummy-read and check whether this gets acknowledged, bttv tests for i2c chips (msp34xx, ...) using reads, and it works pretty well for ages. Gerd -- You have a new virus in /var/mail/kraxel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Nebula installation and nxt6000 fault
I am installing a Nebula DigiTV board but with a few issues. Have followed the various README's and sailed in the draught of a number of postings in this mailing list but seem stuck. Any help here is greatly appreciated. Thanks in advance. Robert Cook The version of Linux is Mandrake 9.2 with a 2.4.23 kernel (2.4.23-0.rc5.2mdk). Video 4 linux enabled. Installed Video4Linux from video4linux-20031208.tar.gz Installed dvb-kernel/build-2.4 from latest CVS archives Bit of a nightmare sorting out conflicting v4l1-compat.o and v4l2-common.o between V4L and dvb-kernel along with Mandrake installed dvb_mod libraries. Cleaned up stale modules and removed conflicting dvb-kernel modules with priority to V4L. Ran the following commands: #modprobe bttv card=0x68 i2c_hw=1 dmesg output bttv: driver version 0.9.12 loaded bttv: snapshot date 2003-12-08 bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). bttv0: Bt878 (rev 17) at 02:0a.0, irq: 22, latency: 64, mmio: 0xfbefe000 bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem ID is 0071:0101 bttv0: using: Nebula Electronics DigiTV [card=104,insmod option] bttv0: gpio: en=, out= in=00ff00cb [init] bttv0: using tuner=-1 bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 = 35468950 .. ok = #modprobe dvb-bt8xx dmesg output bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). bt878(0): Bt878 (rev 17) at 02:0a.1, irq: 22, latency: 64, memory: 0xfbeff000 DVB: registering new adapter (Neb). = #modprobe nxt6000 modprobe: insmod /lib/modules/2.4.23-0.rc5.2mdkcustom/misc/nxt6000.o failed modprobe: insmod nxt6000 failed dmesg | ksymoops output Unable to handle kernel NULL pointer dereference at virtual address e0c85d24 *pde = Oops: CPU:0 EIP: 0010:[e0c85d24]Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010a86 eax: ebx: 0001 ecx: c000 edx: dad1be60 esi: edi: 0001 ebp: dad1bde0 esp: dad1bdd4 ds: 0018 es: 0018 ss: 0018 Process insmod (pid: 1985, stackpage=dad1b000) Stack: 0001 0001 dad1be04 e0c8612b e0c92000 dad1be60 0001 e0c92000 e0c92040 e0c92004 dad1be60 dad1be24 c02ecf29 e0c92004 dad1be60 0001 dac42000 0014 dad1be74 dad1be3c e0ca61a4 e0c92004 dad1be60 Call Trace: [e0c8612b] bttv_i2c_xfer+0x9b/0xc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92040] bttvs+0x40/0x4cc0 [bttv] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [c02ecf29] i2c_transfer+0x39/0x80 [kernel] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0ca61a4] master_xfer+0x34/0x50 [dvb-bt8xx] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0dcc269] pll_write+0x59/0xa0 [nxt6000] [e0dccf0b] nxt6000_attach+0x9b/0x200 [nxt6000] [e0c9cc78] try_attach_device+0x38/0x80 [dvb-core] [e0c9cded] probe_device_on_all_busses+0x1d/0x30 [dvb-core] [e0ca42e0] dvb_i2c_mutex+0x0/0x20 [dvb-core] [e0c9cfe9] dvb_register_i2c_device_Rde0504aa+0x59/0x90 [dvb-core] [e0dcd978] __ksymtab+0x0/0x20 [nxt6000] [e0dcd0f0] nxt6000_init+0x20/0x50 [nxt6000] [e0dcce70] nxt6000_attach+0x0/0x200 [nxt6000] [e0dcd070] nxt6000_detach+0x0/0x60 [nxt6000] [c01f5762] sys_init_module+0x652/0x6e0 [kernel] [e0dcd96c] .kmodtab+0x0/0xc [nxt6000] [e0dcc060] nxt6000_write+0x0/0xa0 [nxt6000] [c01e0683] system_call+0x33/0x40 [kernel] Code: 8a 00 25 ff 00 00 00 c1 e0 10 09 c1 8b 45 10 89 ce 81 ce 8b EIP; e0c85d24 [bttv]bttv_i2c_sendbytes+14/1e0 = edx; dad1be60 _end+1a8c9d39/20585f39 ebp; dad1bde0 _end+1a8c9cb9/20585f39 esp; dad1bdd4 _end+1a8c9cad/20585f39 Trace; e0c8612b [bttv]bttv_i2c_xfer+9b/c0 Trace; e0c92000 [bttv].data.end+45/60a5 Trace; e0c92000 [bttv].data.end+45/60a5 Trace; e0c92040 [bttv].data.end+85/60a5 Trace; e0c92004 [bttv].data.end+49/60a5 Trace; c02ecf29 i2c_transfer+39/80 Trace; e0c92004 [bttv].data.end+49/60a5 Trace; e0ca61a4 [dvb-bt8xx]master_xfer+34/50 Trace; e0c92004 [bttv].data.end+49/60a5 Trace; e0dcc269 [nxt6000]pll_write+59/a0 Trace; e0dccf0b [nxt6000]nxt6000_attach+9b/200 Trace; e0c9cc78 [dvb-core]try_attach_device+38/80 Trace; e0c9cded [dvb-core]probe_device_on_all_busses+1d/30 Trace; e0ca42e0 [dvb-core]dvb_i2c_mutex+0/20 Trace; e0c9cfe9 [dvb-core]dvb_register_i2c_device+59/90 Trace; e0dcd978 [nxt6000].rodata.end+c9/5d1 Trace; e0dcd0f0 [nxt6000]nxt6000_init+20/50 Trace; e0dcce70 [nxt6000]nxt6000_attach+0/200 Trace; e0dcd070 [nxt6000]nxt6000_detach+0/60 Trace; c01f5762 sys_init_module+652/6e0 Trace; e0dcd96c [nxt6000].rodata.end+bd/5d1 Trace; e0dcc060 [nxt6000]nxt6000_write+0/a0 Trace; c01e0683 system_call+33/40 Code; e0c85d24 [bttv]bttv_i2c_sendbytes+14/1e0 _EIP: Code; e0c85d24 [bttv]bttv_i2c_sendbytes+14/1e0 = 0: 8a 00
[linux-dvb] Re: Nebula installation and nxt6000 fault
#modprobe bttv card=0x68 i2c_hw=1 dmesg output bttv: driver version 0.9.12 loaded bttv: snapshot date 2003-12-08 [e0c8612b] bttv_i2c_xfer+0x9b/0xc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92000] bttvs+0x0/0x4cc0 [bttv] [e0c92040] bttvs+0x40/0x4cc0 [bttv] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [c02ecf29] i2c_transfer+0x39/0x80 [kernel] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0ca61a4] master_xfer+0x34/0x50 [dvb-bt8xx] [e0c92004] bttvs+0x4/0x4cc0 [bttv] [e0dcc269] pll_write+0x59/0xa0 [nxt6000] [e0dccf0b] nxt6000_attach+0x9b/0x200 [nxt6000] [e0c9cc78] try_attach_device+0x38/0x80 [dvb-core] [e0c9cded] probe_device_on_all_busses+0x1d/0x30 [dvb-core] [e0ca42e0] dvb_i2c_mutex+0x0/0x20 [dvb-core] [e0c9cfe9] dvb_register_i2c_device_Rde0504aa+0x59/0x90 [dvb-core] [e0dcd978] __ksymtab+0x0/0x20 [nxt6000] [e0dcd0f0] nxt6000_init+0x20/0x50 [nxt6000] [e0dcce70] nxt6000_attach+0x0/0x200 [nxt6000] [e0dcd070] nxt6000_detach+0x0/0x60 [nxt6000] [c01f5762] sys_init_module+0x652/0x6e0 [kernel] [e0dcd96c] .kmodtab+0x0/0xc [nxt6000] [e0dcc060] nxt6000_write+0x0/0xa0 [nxt6000] [c01e0683] system_call+0x33/0x40 [kernel] This bug is caused by the i2c hardware write routine in the bttv driver. It can't handle writing a zero length message to an i2c address. Gerd ? A workaround is to set i2c_hw=0 on the modprobe bttv line. Jamie -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
