The usual cause of instability-over-time when moving from an otherwise stable 0.2 setup to 0.3 is the new dynamic buffer allocation. This could bite anyone due to the fragmentation of kernel memory pools over time but appears to be more common on systems with small amounts of RAM (512Mb or less). Asking the kernel to kmalloc() a contiguous 8Mb chunk of memory can and does fail even if 100s of Mb is being used for buffers and cache and is generally available for kernel and user apps...
Use the ivtv_dynbuf=0 driver option as mentioned below. Should we perhaps change the *default* to static buffer allocation? This problem appears to crop up time and again... Cheers, Wilf. On 30/08/05, Adam Forsyth <[EMAIL PROTECTED]> wrote: > > I have a few theories, but unfortunately there's so many variables I'm > > not sure which way I should be pursing harder. > > > > 1) heat: I'm using an Antec Aria case, which is a small case and can > > get quite warm. The only card I have in the sytem is the 350, > > everything is onboard. Is it possible the new drivers are working the > > card harder and is generating more heat and causing random freezes? > > Note: 0.2.x series drivers never cause a complete system freeze for me ever. > > I think that the pvr350s are often much hotter than the mobo temp. I > mounted a case fan on the side of mine because last summer it was > overheating when the apartment got very warm, although the reported > temps were fine. I kind of doubt this is your issue though if you say > you didn't have any trouble with the 0.2 series. > > > 2) ivtv configuration: The relevant part of /etc/modules.conf looks like > > this: > > > > install ivtv /sbin/modprobe --ignore-install ivtv ; /sbin/modprobe ivtv-fb > > install ivtv /sbin/modprobe bttv; /sbin/modprobe --ignore-install ivtv > > The bttv line is only needed if you have a bttv based card in your > system, if you only have a pvr350 then you don't need it. > > > 3) mythtv configuration: I'm using the latest bleeding edge version of > > mythtv grabbed with svn. The freezing seems to occur when I'm moving > > around the menu's in myth, rarely when I'm just watching tv and not > > pressing anything - but it has happened as well. > > Try starting mythfrontend from a terminal and logging the output to > see if maybe it's having an error causing you to crash: > > mythfrontend > ~/mythfrontend.log 2>&1 > > Have you checked /var/log/messages to see if anything is logged by > ivtv or anything else when you crash? If you're seeing any memory / > buffer errors, try adding this to your /etc/modprobe.conf: "options > ivtv ivtv_dynbuf=0". > > > ------------------------------------------------------- > 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 > -- [EMAIL PROTECTED] ------------------------------------------------------- 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
