On Sat, Aug 05, 2006 at 12:46:49PM +0200, Simen Thoresen wrote: > Hi Michael, Rey, > > I have not seen any new replies to this, nor anything from any developers. > As I wrote in my problem report, I've been an ivtv-user for a while, but > only recently subscribed to the list - thus I don't know what to expect from > developer interest and such. > > Still - assuming the developers are reading the list and and are interested > in the problem, I thought I'd try to summarise our systems so that we can > get similarities or differences sorted out. > > My system (as previously written) is an Asus A8N-SLI Deluxe motherboard, > with an Athlon64 X2 chip, running in i386 mode, with ivtv 0.7.0 on a > 2.6.17.6 kernel. > > 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 > > 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
There was some discussion in the past (search for "DMA" or "ticket 49" in the archives), and I think someone said that it maybe had to do with CPU throttling. I've been running with the "fix" as shown in trac ticket #49 (http://ivtvdriver.org/trac/ticket/49) - although it's hardly a fix as it causes each encoder process to use alot of CPU - but my cpu can just barely handle 2 encoding processes and decoding then. I've been more concerned with a stable machine than trying various versions of this and that. It is quite annoying to watch anything after the error has occurred. I'd love to get the cards working properly without having to turn off CPU throttling. If there are configurations that people have working _without_ the intermittent DMA errors I would (and I'm sure others) would love to hear about them. Kristo _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
