Thanks Hans. Do you think the new DMA changes you provided in the beta version (b3490) will make any difference on my setup?
Also, with the PCI latency changes I made, I don't see the fatal errors any more, although it might just be a matter of time. I'm now getting about 2 or or 3 offset DMA Errors per hour on my setup, depending on the raid array usage. Thanks, -Todd On 10/27/06, Hans Verkuil <[EMAIL PROTECTED]> wrote: > Hi Todd, > > There are three reasons for this error based on our current knowledge: > 1) Cpu frequency changing, 2) graphics cards that use system memory (as > opposed to having there own memory) and 3) raid arrays. > > In your case I'd say it is number 3. > > I don't think there is much that can be done about it (except avoiding > raid setups) since the root cause is the crappy DMA engine of the > cx23415/6. > > Hans > > On Friday 20 October 2006 03:31, Todd Foggoa wrote: > > Hi Folks, > > > > I seem to be plagued with these DMA errors almost every time I try to > > record something now. These errors are happening on the latest ivtv > > driver 0.7.1 > > The errors look like the following: > > ivtv0 warning: ENC: (0) DMA Error 0x0000000b 00020001 > > ivtv0 warning: offset 8 -> 128 > > ivtv0 warning: offset 128 -> 120 > > ivtv0 warning: ENC: REG_DMAXFER 2 wait failed > > ivtv0 warning: ENC: (0) DMA Error 0x00000001 00000001 > > > > My Setup is: > > Linux dawg 2.6.17-gentoo-r8 #4 PREEMPT Tue Oct 3 06:48:59 EDT 2006 > > x86_64 AMD Athlon(tm) 64 Processor 3000+ GNU/Linux > > I am running on an ASUS AV8 Deluxe motherboard with 4 ide hard drives > > setup in raid5 with LVM configured on the raid array. I have an extra > > IDE controller card and 2 hauppage 250 cards and am using MythTV. > > > > I've read alot about people thinking these are due to cpu frequency > > changes or opengl related. However, I don't believe it is due to > > either of these. I can easily reproduce these DMA errors without > > MythTV and without cpu frequency scaling. To reproduce I cat both > > tuners to files on my lvm/raid5 array and then have another computer > > cat some large files to /dev/null via NFS. > > > > I'm thinking this must have something to due the amount of interrupts > > happening as in my test case above has interrupts going off for the > > network card, the HD access (for all 4 drives) and the two tuner > > cards. Do we know if the ivtv driver is spending a lot of time at > > interrupt level? Anyone have any comments about this? > > > > I've setup a page on the ivtvdriver.org wiki for this so hopefully we > > can get some more information to narrow down this problem. I've also > > updated it with information from others posts: > > http://ivtvdriver.org/index.php/DMA > > > > If there is any testing /debugging I can do on my setup I'm more than > > happy to help out. > > > > And my ivtv dmesg output is below. > > > > Thanks, > > -Todd > > > > ivtv: ==================== START INIT IVTV ==================== > > ivtv: version 0.7.1 (tagged release) loading > > ivtv: Linux version: 2.6.17-gentoo-r8 preempt mod_unload gcc-3.4 > > ivtv: In case of problems please include the debug info between > > ivtv: the START INIT IVTV and END INIT IVTV lines, along with > > ivtv: any module options, when mailing the ivtv-users mailinglist. > > ivtv0: Autodetected Hauppauge WinTV PVR-250 card (cx23415 based) > > tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) > > saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) > > msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) > > ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) > > ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) > > ivtv0: Encoder revision: 0x02050032 > > ivtv0: Decoder revision: 0x02020023 > > ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB > > total) ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers > > (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 > > buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: > > 455 x 4608 buffers (2048KB total) ivtv0: Initialized Hauppauge WinTV > > PVR-250, card #0 > > ivtv: ====================== NEXT CARD ====================== > > ivtv1: Autodetected Hauppauge WinTV PVR-250 card (cx23416 based) > > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1) > > saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #1) > > msp3400 1-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #1) > > ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) > > ivtv1: Encoder revision: 0x02050032 > > ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB > > total) ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers > > (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 > > buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream: > > 455 x 4608 buffers (2048KB total) ivtv1: Create encoder radio stream > > ivtv1: Initialized Hauppauge WinTV PVR-250, card #1 > > ivtv: ==================== END INIT IVTV ==================== > > > > _______________________________________________ > > ivtv-devel mailing list > > [email protected] > > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
