Simen Thoresen wrote: > Hi Michael, Rey, Hi Michael, Rey, List
> This means > -NForce4 (I would not thing that mobo brand or chipset features matter > too much) > -SMP (This may be important. I've run my card with ivtv-0.4.x 'forever' > in UP-mode on older kernels without issues) > -kernel 2.6.17 + ivtv 0.7.0 I've built my 2.6.17.6 UP kernel, and after a night of grabbing, got this in my log; Aug 6 01:28:21 muhaha kernel: ivtv0 warning: ENC: (0) DMA Error 0x0000000b Aug 6 03:09:58 muhaha kernel: ivtv0 warning: ENC: (0) DMA Error 0x0000000b Aug 6 04:42:48 muhaha kernel: ivtv0 warning: ENC: (0) DMA Error 0x0000000b Aug 6 06:43:08 muhaha kernel: ivtv0 warning: ENC: (0) DMA Error 0x0000000b Aug 6 08:00:12 muhaha kernel: ivtv0: All encoder MPEG stream buffers are full. Dropping data. Aug 6 08:00:12 muhaha kernel: ivtv0: Cause: the application is not reading fast enough. The 110m encodes were scheduled to start every 2 full hours, so none of the errors above occured at the same time. I'll boot back to my Centos-original kernel (which I dropped as it did not support SMP well) and rerun this test from there. For now the conclusion for my system seems ot be that this is /not/ an SMP issue. Yours, -S > > Michael; > From your mail, I understand you are running an A8V board (That would > be a ViA K8T800pro-board, right?). Are you running an X2 CPU in SMP on > this? In i386 and not x86-64 mode? > Also, you're writing that ivtv 'crashes' - are we talking about the same > DMA error; > warning: ENC: (0) DMA Error 0x0000000b > reported some or many times during a capture? > The actual error number may be important, altho I don't know what it > signifies. > > Altho my errors were a lot less frequent that I have seen others report, > they never caused ivtv to stop working, nor impaired system stability. > > > > Rey; > You write that you have the same setup as I have. Could you please > expand on that? > Did the patch work for you as well as it does for me? > > > > So - assuming Michael is experiencing the same problem I am, it would > seem that his is /not/ a chipset issue (or, if it is, both NForce4 and > K8T800pro chipsets are affected), but the common line is that it applies > to Athlon64 CPUs, possibly SMP setups. > > From my own experience from my own setup, I feel pretty confident that > the the main change I introduced was the SMP CPU. I see others have > reported this issue with other kernels and ivtv-versions, but good > information is typically missing. > > With a little spare time, I will build an UP kernel and give that a spin > with an unmodified ivtv-driver. Given that my errors never were very > frequent, testing will take time to be conclusive. > > Yours, > -S -- Simen Thoresen, Dolphin ICS _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
