Antti P Miettinen wrote:
The part of the log that should contain the disconnect (according to
above reasoning) is at
http://www.hut.fi/~apm/usb-disconnect.txt.gz
it should start about minute before and stop about a minute after the
disconnect.
I see the same sequence that you do. Here is the specific part that
matches what I see. Your trace has:
f764cd40 3276934748 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
f764cd40 3276935240 C Co:003:00 0 6 >
f764cd40 3276957395 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 6100
f764cd40 3276957995 C Co:003:00 0 6 >
f764cd40 3276958005 S Co:003:00 s 40 03 0000 0000 0004 4 = 03c20300
f764cd40 3276958744 C Co:003:00 0 4 >
f764cd40 3276958752 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
f764cd40 3276959241 C Co:003:00 0 6 >
f764cd40 3276981394 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 6100
f764cd40 3276981997 C Co:003:00 0 6 >
f764cd40 3276982007 S Ci:003:00 s c0 02 01c3 0800 0001 1 <
f764cd40 3276982871 C Ci:003:00 0 1 = ed
f764cd40 3276982880 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
f764cd40 3276983372 C Co:003:00 0 6 >
f764cd40 3276983382 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 6100
f764cd40 3276983873 C Co:003:00 0 6 >
f764cd40 3276984006 S Ci:003:00 s c0 02 01c3 0700 0001 1 <
f764cd40 3276984998 C Ci:003:00 0 1 = 77
f764cd40 3276985008 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
f764cd40 3276985496 C Co:003:00 0 6 >
I got:
dc7f2640 2090300427 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
dc7f2640 2090301048 C Co:003:00 0 6 >
dc7f2640 2090321797 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 6100
dc7f2640 2090322552 C Co:003:00 0 6 >
dc7f2640 2090322558 S Co:003:00 s 40 03 0000 0000 0004 4 = 03c20300
dc7f2640 2090323426 C Co:003:00 0 4 >
dc7f2640 2090323430 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
dc7f2640 2090324051 C Co:003:00 0 6 >
dc7f2640 2090344795 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 6100
dc7f2640 2090345556 C Co:003:00 0 6 >
dc7f2640 2090345562 S Ci:003:00 s c0 02 01c3 0800 0001 1 <
dc7f2640 2090346680 C Ci:003:00 0 1 = ee
dc7f2640 2090346685 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
dc7f2640 2090347429 C Co:003:00 0 6 >
dc7f2640 2090347435 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 6100
dc7f2640 2090348055 C Co:003:00 0 6 >
dc7f2640 2090348060 S Ci:003:00 s c0 02 01c3 0700 0001 1 <
dc7f2640 2090349179 C Ci:003:00 0 1 = 95
dc7f2640 2090349184 S Co:003:00 s 40 03 0000 0000 0006 6 = 03160301 0080
dc7f2640 2090349929 C Co:003:00 0 6 >
and mine is repeatable with separate traces. I have recent v4l-dvb
drivers, 2.6.20-rc4 kernel on FC5. I have only MythTV performing EIT
scanning when the oops occurs. A lower signal level helps generate the
problem more often.
The kernel logs shows an EPIPE error then EPROTO errors. This extract of
the kernel log may not exactly match my USB trace above:
localhost kernel: start pid: 0x0010, feedtype: 0
localhost kernel: setting pid (no): 16 0010 at index 1 'on'
localhost kernel: start pid: 0x0011, feedtype: 0
localhost kernel: setting pid (no): 17 0011 at index 2 'on'
localhost kernel: urb completition error -32.
localhost kernel: urb completition error -71.
localhost last message repeated 347 times
localhost kernel: usb 8-1: USB disconnect, address 2
localhost kernel: ehci_hcd 0000:02:02.2: qh f6902180 (#82) state 4(has tds)
localhost kernel: urb completition error -71.
localhost kernel: state before exiting everything: 3
localhost kernel: unregistering DVB part
localhost kernel: killing URB no. 0.
localhost kernel: killing URB no. 1.
localhost kernel: killing URB no. 2.
localhost kernel: killing URB no. 3.
localhost kernel: mt2060 I2C write failed
Regards
Chris
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
