> > On Friday 19 August 2005 05:43 am, Pete Davis wrote: > > > Try setting the ivtv option ivtv_dynbuf=0? Maybe it's the buffer > > > allocation that is sometimes stalling? > > > > This caused all sorts of buffer allocation failures in ivtv and made the > > linux box pretty much unusable. It killed my vnc session, wouldn't let > me > > telnet in, couldn't bring the monitor out of sleep mode on the box > itself, > > and ended up having to do a cold reboot. > > > > Pete > > How about after the cold boot? How did it behave? If memory is an issue, > then I can sort of see why all that weird behavior happened. But after a > fresh cold boot, by using ivtv_dynbuf=0 it'll "reserve" its memory right > at > boot when the module is loaded, so there'll definitely be free memory > available. > > ~Lou
Lou, didn't try that. I'll give that a shot. After I rebooted, I changed it back :-( I figured the lockup indicated it was unhappy but it was probably just from the mix of changes I had done. The machine is busy transcoding some stuff now (and will be well into the night), but I'll give that a shot in the morning and see if that fixes it. Really, the delay isn't such a big deal since it's pretty easy to work around. The CPU hogging issue is what's really bugging me and I can't get around that. When it happens, my captures are basically crap because there are so many dropped frames and I have to redo them. Pete ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
