[mythtv-users] kt133 problem question
Boyd II, Willy
wboyd at fulbright.com
Mon Sep 8 14:40:55 EDT 2003
Hello all...
I checked out Mythtv way back when, and just recently got it going once
again (my only hold off was getting the pvr250 'cause I didn't wanna deal
with software encoding).
My question is regarding the supposed problem with via kt133 chipsets --
what are the symptoms of such a problem?
Mythbackend 0.11 for me is segfaulting quite often. However, there usually
is nothing out-of-the-ordinary written to the log when this happens. And
usually nothing (again, error-related) from ivtv in /var/log/messages. It
just segfaults, anywhere from 10min to an hour of viewing. Sometimes I can
duplicate it easily by going to the guide, hitting Up (scrolling through the
guide) about 10 times, and bam it's gone. This is on a Abit KT7 board, with
said chipset. Looking at my *overnight* logs, I do see some entries like
"backend stuffed up" or "not enough free buffers" for ivtv, but when I'm
able to reproduce the crashes, these errors are printed out. Just a
segfault. (I'm able to get "overnight" logs because I have mythbackend
respawning inside a while[true] loop...)
I can provide debugging output later (I'm at work right now), but I'm just
curious if it's likely my problem is due to this problematic chipset, or
potentially a mythbackend bug. Others that have the kt133 problem: do you
see anything special in the logs? Does mythbackend segfault, freeze, or
what? Are mythbackend crashes fairly common right now even on stable
hardware?
Thanks!
==========================
William Boyd, II
Web Developer
Fulbright & Jaworski L.L.P.
713-651-5687
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20030908/9031949e/attachment.htm
More information about the mythtv-users
mailing list