I have a DViCO HDTV5 PCI capture board.
It works great most of the time (thanks to the god like Michael
Krufky).
However, if I accidently run two copies of dvbstream (from a
crontab, for example), then it will kernel panic.
I get a similiar symptom with the USB version of this product as well.
I'm running Fedora Core 5, test 2 with all the latest updates. The
kernel is 2.6.16-rc-mumble
Here is a crash log from the HDTV5 PCI:
------------[ cut here ]------------
kernel BUG at include/linux/list.h:165!
invalid opcode: 0000 [#1]
last sysfs file: /block/hda/hda1/size
Modules linked in: netconsole netdump dvb_bt8xx nxt6000 mt352 dvb_pll sp887x
dst_ca dst dvb_core cx24110 or51211 lgdt330x ipv6 ppdev autofs4 rfcomm l2cap
bluetooth sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack
nfnetlink xt_tcpudp iptable_filter ip_tables x_tables loop video button battery
ac lp parport_pc parport floppy nvram uhci_hcd ehci_hcd e100 mii bt878 tuner
tda9887 bttv video_buf compat_ioctl32 v4l2_common btcx_risc ir_common tveeprom
videodev snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm
snd_timer i2c_i810 snd i2c_algo_bit soundcore snd_page_alloc i2c_i801 i2c_core
dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd
CPU: 0
EIP: 0060:[<c0129b2d>] Not tainted VLI
EFLAGS: 00010006 (2.6.15-1.1881_FC5) EIP is at remove_wait_queue+0x18/0x4f
eax: c380e784 ebx: ca59d00c ecx: 00000001 edx: ca59d018
esi: c380e774 edi: 00000292 ebp: c32894bc esp: cf0c4f50
ds: 007b es: 007b ss: 0068
Process dvbstream (pid: 20728, threadinfo=cf0c4000 task=c7da0000)
Stack: <0>ca59d008 ca59d000 bfda93c8 c01633d9 00000000 00000000 c016415f
cf0c4fb0
bfda93c8 bfda93c8 00000000 c32894bc 00000001 00000001 00000000 c32894b4
c01633fb ca59d000 00000000 bfda93c0 00000000 002d3ff4 cf0c4000 c0164382
Call Trace:
[<c01633d9>] poll_freewait+0x18/0x3a [<c016415f>] do_sys_poll+0x2e0/0x2ea
[<c01633fb>] __pollwait+0x0/0x94 [<c0164382>] sys_poll+0x44/0x4a
[<c0102ba9>] syscall_call+0x7/0xb <0>Code: 0c 89 7a 04 89 56 10 89 c2 89 f0
5b 5e 5f e9 6a 68 1b 00 57 56 53 89 c6 89 d3 e8 92 68 1b 00 89 c7 8d 53 0c 8b
42 04 39 10 74 08 <0f> 0b a5 00 26 cc 2f c0 8b 4b 0c 39 51 04 74 08 0f 0b a6 00
26
Continuing in 120 seconds....
Pid: 20728, comm: dvbstream
EIP: 0060:[<c0129b2d>] CPU: 0
EIP is at remove_wait_queue+0x18/0x4f
EFLAGS: 00010006 Not tainted (2.6.15-1.1881_FC5)
EAX: c380e784 EBX: ca59d00c ECX: 00000001 EDX: ca59d018
ESI: c380e774 EDI: 00000292 EBP: c32894bc DS: 007b ES: 007b
CR0: 8005003b CR2: 002b5c60 CR3: 05ab1000 CR4: 000006d0
[<c01633d9>] poll_freewait+0x18/0x3a
[<c016415f>] do_sys_poll+0x2e0/0x2ea [<c01633fb>] __pollwait+0x0/0x94
[<c0164382>] sys_poll+0x44/0x4a [<c0102ba9>] syscall_call+0x7/0xb
sibling
task PC pid father child younger older
init S C123EBC8 812 1 0 2 (NOTLB)
c123deac 00000286 00000009 c123ebc8 c123eaa0 a80c8a00 003d7397 00000000
00000286 c123deb4 4c884900 00000000 000004e2 01bf199c 0000000b c123dfa0
c02df0e1 d0c07e94 cbab9eb4 01bf199c c0120f44 c123eaa0 c0408a00 00000000
Call Trace:
[<c02df0e1>] schedule_timeout+0xb0/0xd2 [<c0120f44>]
process_timeout+0x0/0x5
[<c01637e9>] do_select+0x35a/0x3c0 [<c01633fb>] __pollwait+0x0/0x94
[<c0163ac8>] core_sys_select+0x279/0x297 [<c0163dbf>]
sys_select+0x9f/0x15f
[<c0102ba9>] syscall_call+0x7/0xb ksoftirqd/0 R running 3872 2
1 3 (L-TLB)
watchdog/0 S C123E128 3676 3 1 4 2 (L-TLB)
c1238f94 00200286 00000003 c123e128 c123e000 fd2a1700 003d7397 00000000
00200286 c1238f9c 00000000 00000000 000000fb 01bf171a c123df24 c0138bf6
c02df0e1 c0408ae8 c0408ae8 01bf171a c0120f44 c123e000 c0408a00 c1238000
Call Trace:
[<c0138bf6>] watchdog+0x0/0x66
[<c02df0e1>] schedule_timeout+0xb0/0xd2 [<c0120f44>]
process_timeout+0x0/0x5
[<c0121394>] msleep_interruptible+0x1e/0x3f [<c0138c33>]
watchdog+0x3d/0x66
[<c012988b>] kthread+0x91/0xbd [<c01297fa>] kthread+0x0/0xbd
[<c0101005>] kernel_thread_helper+0x5/0xb events/0 S CFE60BC8 3012
4 1 5 3 (L-TLB)
cfe5ff68 00000000 0000000a cfe60bc8 cfe60aa0 15f5bf00 003d7398 00000000
cfced9fc cfced9fc 003d0900 00000000 cfced9f4 cfced9dc cfced9fc c0127342
c0127407 00000000 00000000 00000000 00000000 00000000 c0342000 c02e037d
Call Trace:
[<c0127342>] worker_thread+0x0/0x11c
[<c0127407>] worker_thread+0xc5/0x11c [<c02e037d>]
_spin_unlock_irq+0x5/0x7
[<c02de817>] schedule+0x4a1/0x4ff [<c01176a3>]
default_wake_function+0x0/0xc
[<c012988b>] kthread+0x91/0xbd [<c01297fa>] kthread+0x0/0xbd
[<c0101005>] kernel_thread_helper+0x5/0xb khelper S CFE60678 3224
5 1 6 4 (L-TLB)
cfe5ef68 00000000 0000000a cfe60678 cfe60550 4c2f4e00 003d08c8 00000000
cfcd4858 cfcd4858 00f42400 00000000 cfcd4850 cfcd4838 cfcd4858 c0127342
c0127407 00000000 00000000 00000000 00000000 00000000 c0342000 c02e037d
Call Trace:
[<c0127342>] worker_thread+0x0/0x11c
[<c0127407>] worker_thread+0xc5/0x11c [<c02e037d>]
_spin_unlock_irq+0x5/0x7
[<c02de817>] schedule+0x4a1/0x4ff [<c01176a3>]
default_wake_function+0x0/0xc
[<c012988b>] kthread+0x91/0xbd [<c01297fa>] kthread+0x0/0xbd
[<c0101005>] kernel_thread_helper+0x5/0xb kthread S CFE60128 3220
6 1 8 127 5 (L-TLB)
cfe54f68 00000000 00000009 cfe60128 cfe60000 283cc200 003d08c5 00000000
cfe550b0 cfe550b0 00000000 00000000 cfe550a8 cfe55090 cfe550b0 c0127342
c0127407 00000000 00000000 00000000 00000000 00000000 cfe4ac24 c02e037d
Call Trace:
[<c0127342>] worker_thread+0x0/0x11c
[<c0127407>] worker_thread+0xc5/0x11c [<c02e037d>]
_spin_unlock_irq+0x5/0x7
[<c02de817>] schedule+0x4a1/0x4ff [<c01176a3>]
default_wake_function+0x0/0xc
[<c012988b>] kthread+0x91/0xbd [<c01297fa>] kthread+0x0/0xbd
[<c0101005>] kernel_thread_helper+0x5/0xb kblockd/0 S CFE4D678 3452
8 6 9 (L-TLB)
cf8bff68 00000000 0000000a cfe4d678 cfe4d550 0a840f00 003d7398 00000000
cfe55b14 cfe55b14 00000000 00000000 cfe55b0c
---------- Forwarded message ----------
Date: Thu, 12 Jan 2006 13:01:36 -0500
From: Michael Krufky <mkrufky@xxxxxxx>
To: Ken Harris <kharris@xxxxxxxxx>
Subject: Re: panic in dvb_dmx_swfilter
Ken Harris wrote:
Mike:
I've using the HDTV5 USB to record shows, and mostly it works OK, but I
had this traceback yesterday (some of it scrolled off the screen, let me know
if there is a way too get more info in the future):
dvb_dmx_swfilter
dvb_usb_urb_complete
usb_hcd_giveback_urb
ehcii_urb_done
qh_completions
scan_async
ehci_work
ehci_irq
usb_hcd_irq
Please paste the entire oops in an email addressed to the linux-dvb mailing
list.
LinuxDVB Mailing List <linux-dvb@xxxxxxxxxxx>
Also, All DViCO USB devices should now be supported in cvs, and will also be
supported in 2.6.16
Cheers,
Mike
--
Michael Krufky
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
