[mythtv-users] Re: PVR-350 or motherboard?

[Jay Goldberg]

Hi Folks

I wanted to share an interesting data point.  I turned off SMP & APIC
support in my 2.4.22 kernel and using either MythTV-0.12 & ivtv 031031A
*or* MythTV-CVS (yesterday) & ivtv 031116C -

Using MythTV to watch LiveTV reliably freezes up in exactly 1200 seconds.
Here are two elapsed runs as seen from syslog with a 10-second timestamp
logger running in the background:

Nov 17 08:17:27 tesla timestamp: elapsed 10
[...]
Nov 17 08:19:07 tesla timestamp: elapsed 110
Nov 17 08:19:12 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:19:17 tesla timestamp: elapsed 120
[...]
Nov 17 08:22:57 tesla timestamp: elapsed 340
Nov 17 08:23:04 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:23:07 tesla timestamp: elapsed 350
[...]
Nov 17 08:24:48 tesla timestamp: elapsed 450
Nov 17 08:24:55 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:24:58 tesla timestamp: elapsed 460
[...]
Nov 17 08:26:58 tesla timestamp: elapsed 580
Nov 17 08:27:03 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:27:08 tesla timestamp: elapsed 590
[...]
Nov 17 08:27:48 tesla timestamp: elapsed 630
Nov 17 08:27:48 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:27:58 tesla timestamp: elapsed 640
[...]
Nov 17 08:28:28 tesla timestamp: elapsed 670
Nov 17 08:28:30 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:28:38 tesla timestamp: elapsed 680
[...]
Nov 17 08:29:48 tesla timestamp: elapsed 750
Nov 17 08:29:53 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:29:58 tesla timestamp: elapsed 760
[...]
Nov 17 08:32:09 tesla timestamp: elapsed 890
Nov 17 08:32:12 tesla kernel: ivtv: DMA read error. Result=0x00000002
Nov 17 08:32:19 tesla timestamp: elapsed 900
[...]
Nov 17 08:37:09 tesla timestamp: elapsed 1190

...here the machine is completely locked up - no response at the console
or the network, and must be powered down.

Nov 17 08:44:22 tesla timestamp: elapsed 10
[...]
Nov 17 08:50:23 tesla timestamp: elapsed 370
Nov 17 08:50:32 tesla kernel: ivtv: Got DMA-done, but not expecting one
Nov 17 08:50:33 tesla timestamp: elapsed 380
[...]
Nov 17 08:56:04 tesla timestamp: elapsed 710
Nov 17 08:56:08 tesla kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting...
Nov 17 08:56:08 tesla kernel: ivtv: DMAP not set
Nov 17 08:56:14 tesla timestamp: elapsed 720
[...]
Nov 17 09:02:04 tesla timestamp: elapsed 1070
Nov 17 09:02:12 tesla kernel: ivtv: DMA read error. Result=0x00000002
[...]
Nov 17 09:04:04 tesla timestamp: elapsed 1190

...again, the machine is completely locked up - no response at the console
or the network, and must be powered down.

...at this time, the ring buffer is:

-rw-r--r--    1 root     root     773664704 Nov 17 09:04 /mnt/store/ringbuf1.nuv

There's *lots* (> 200GB) of free space on this disk...

Can this be an IDE issue?  Is there a simple way in MythTV to limit the
size of the ringbuffer to, say, 200MB?  If limiting the size of the ring
buffer eliminates the lockup, then I'll have to debug more along the IDE
path...

Any thoughts?

	Cheers
		Jay


-- 
Jay Goldberg
H: jay at ransdoc.com