[linux-dvb] Kernel Oops with saa7134 (v4l / analogue) + dvb-ttusb-budget

[Richard Taylor <richard@artaylor.co.uk>]

Hi all, 

I have been trying to get my WinTV Nova-T USB Digital receiver to work alongside an saa7134 fly-view / video based analogue receiver. 

Insmodding, and using these drivers independantly is no problem, however when inserting them together causes my kernel to get upset. 

I am using the current (04/Sept/2004) CVS for dvb-kernel, and have tried both the kernel saa7134, and the latest v4l release (saa7134-0.2.12). 

Two Kernels tried: 
linux-2.6.7-gentoo-r9
linux-2.6.9-rc2

The 2.6.7 took some mods to get the dvb-kernel to compile (kvect?)


That's another story :) 

As stated above, on their own, both drivers work, together they fail. 
The result is similar for both 2.6.7 and 2.6.9

---- begin dmseg output ----

saa7130/34: v4l2 driver version 0.2.11 loaded
saa7134[0]: found at 0000:00:0e.0, rev: 1, irq: 17, latency: 32, mmio: 0xe4000000
saa7134[0]: subsystem: 1043:0210, board: KNC One TV-Station RDS / Typhoon TV Tuner RDS [card=7,insmod option]
saa7134[0]: board init: gpio is 10700
tuner: chip found at addr 0xc0 i2c-bus saa7134[0]
tuner: type set to 10 (Alps TSBE1) by saa7134[0]
tda9887: chip found @ 0x86
Unable to handle kernel paging request at virtual address 2d646c2f
 printing eip:
 cea116c5
 *pde = 00000000
 Oops: 0000 [#1]
 Modules linked in: saa7134 video_buf v4l2_common v4l1_compat ir_common videodev skystar2 dvb_dibusb ttusb_dec dvb_ttusb_budget budget_ci budget budget_core ttpci_eeprom saa7146 mt312 cx22702 cx24110 grundig_29504_491 grundig_29504_401 dib3000mb tda1004x ves1820 stv0299 alps_tdmb7 alps_tdlb7 ves1x93 dvb_core evdev firmware_class ipt_limit ipt_REJECT ipt_state iptable_filter ipt_MASQUERADE iptable_nat ip_conntrack ip_tables rfcomm l2cap tda9887 tuner lirc_it87 lirc_dev ide_cd hci_usb bluetooth eth1394 sbp2 ohci1394 ieee1394 usb_storage
 CPU:    0
 EIP:    0060:[<cea116c5>]    Not tainted
 EFLAGS: 00010246   (2.6.7-gentoo-r9)
 EIP is at dvb_register_frontend+0x19f/0x264 [dvb_core]
 eax: 2d646c2f   ebx: cd0f1c00   ecx: 00000000   edx: c25ec9c4
 esi: 2d646c2f   edi: cd0f1e10   ebp: cea1b3d0   esp: c835ddc0
 ds: 007b   es: 007b   ss: 0068
 Process modprobe (pid: 16030, threadinfo=c835c000 task=c7090cb0)
 Stack: cdffb580 000000d0 ce9fbb60 cdfe2818 ceb481bd 00000000 cdfe2818 c0491668
        c04150df 00000003 cdfe2800 00000000 cdfe291c c0c23a28 ce9faa74 ce9fa691
        2d646c2f c0c23a28 ce9fbb60 ce9fbe80 07ce0000 00000043 00000001 c835de13
 Call Trace:
  [<ceb481bd>] attach_inform+0x0/0x35 [saa7134]
  [<ce9faa74>] attach_adapter+0x123/0x183 [alps_tdmb7]
  [<ce9fa691>] tdmb7_ioctl+0x0/0x2c0 [alps_tdmb7]
  [<c032f6c3>] i2c_add_adapter+0x1c8/0x1cc
  [<c03d6b65>] schedule_timeout+0x6d/0xb7
  [<ceb483fe>] saa7134_i2c_register+0x5e/0xa3 [saa7134]
  [<c011fa32>] process_timeout+0x0/0x9
  [<ceb47334>] saa7134_initdev+0x316/0x7ed [saa7134]
  [<ceb46a58>] saa7134_irq+0x0/0x1be [saa7134]
  [<c0261917>] pci_device_probe_static+0x52/0x61
  [<c0261961>] __pci_device_probe+0x3b/0x4e
  [<c02619a0>] pci_device_probe+0x2c/0x4a
  [<c02ad8d1>] bus_match+0x3f/0x6a
  [<c02ad9e3>] driver_attach+0x56/0x80
  [<c02adc67>] bus_add_driver+0x91/0xa3
  [<c02ae089>] driver_register+0x2f/0x33
  [<c01191f8>] printk+0xfe/0x12f
  [<c0261bdf>] pci_register_driver+0x5c/0x84
  [<ceb479ba>] saa7134_init+0x47/0x55 [saa7134]
  [<c012b7d0>] sys_init_module+0x106/0x1cf
  [<c0105d4f>] syscall_call+0x7/0xb

Code: 8b 00 c7 04 24 e0 57 a1 ce 89 44 24 04 e8 23 7a 70 f1 89 34
				    
---- end dmesg output ----

Any ideas? 

Richard.