[EMAIL PROTECTED] wrote: >On Sat, Jan 07, 2006 at 09:34:41AM -0500, Al McIntosh wrote: > > >>>>Dec 15 07:28:27 mythbox kernel: ivtv0 warning: ENC Stream 0 OVERFLOW >>>>#2: >>>>Stealing a Buf >>>>fer, 512 currently allocated >>>> >>>> >>More memory does not appear to help. Did anyone manage a fix for this? >> >> > >In my case, it turned out that my network card was on the same IRQ as >all three IDE channels (software RAID-5), and while the box would >usually record OK, if I was doing something network-intensive (like >watching TV on the remote Myth frontend) the network card would >generate so many IRQs it was delaying the drives to the point where >the front-end would stutter, ivtv would overflow, and eventually the >RAID driver would fail a drive. That would have been fine, except >that the ethernet watchdog (tulip driver) would panic the kernel. I >tried forcing the cards to specific IRQs but the tulip driver >wouldn't behave. I switched to a different ethernet port and ALL of >the problems went away. > >
Todate, I have been running mythtv binaries. Last night I tried to compile mythtv svn and gcc crashed 3 times with segmentation faults. I began to think overheating or bad ram. I took out the older stick of ram and myth compiled twice cleanly. I ran memtest at work and it found errors in the ram. Hopefully, this was the cause of all my problems. I'll watch and see. _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
