[mythtv-users] New Myth/ivtv error

Marc Tousignant drayson at net1plus.com
Sun Jul 10 08:53:02 EDT 2005


> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
> bounces at mythtv.org] On Behalf Of sherpa 13
> Sent: Sunday, July 10, 2005 6:56 AM
> To: mythtv-users at mythtv.org; spugh at edenfx.com
> Subject: RE: [mythtv-users] New Myth/ivtv error
> 
> Hi,
> 
> Unfortunately I can't provide a solution however I have been having the
> same
> error for some time now (multiple versions of ivtv anyways), it always
> occurs when whatching Live Tv or a recorded program, thought a little more
> info from my setup might help.
> 
> The playback freezes and looking at /var/log/messages has the error you
> describe below.
> 
> Jul 10 11:36:12 faith kernel: ivtv: DEC: Decoder wants 0x00010000 bytes,
> bad
> mem
> Jul 10 11:36:43 faith last message repeated 7 times
> Jul 10 11:36:46 faith kernel: ivtv: DEC: Sched Buffer end reached
> 0x036f0fbd
> Jul 10 11:36:46 faith kernel: ivtv:  DEC: Mailbox 10: 0x00000000
> 0x036e0fbd
> 0x03
> Jul 10 11:36:46 faith kernel: ivtv: DEC: Sched Buffer end reached
> 0x036f0fbd
> Jul 10 11:36:46 faith kernel: ivtv:  DEC: Mailbox 10: 0x00000000
> 0x036e0fbd
> 0x03
> Jul 10 11:36:46 faith kernel: ivtv: DEC: Sched Buffer end reached
> 0x036f0fbd
> Jul 10 11:36:46 faith kernel: ivtv:  DEC: Mailbox 10: 0x00000000
> 0x036e0fbd
> 0x03
> Jul 10 11:36:46 faith kernel: ivtv: DEC: Sched Buffer end reached
> 0x036f0fbd
> Jul 10 11:36:46 faith kernel: ivtv:  DEC: Mailbox 10: 0x00000000
> 0x036e0fbd
> 0x03
> Jul 10 11:36:46 faith kernel: ivtv: DEC: Sched Buffer end reached
> 0x036f0fbd
> 
> Sometimes seems to coincide with the following in my mythfrontend.log
> 2005-07-09 20:00:43.772 Waited 4 seconds for data to become available,
> waiting again...
> 2005-07-09 20:00:47.774 Waited 4 seconds for data to become available,
> waiting again...
> 2005-07-09 20:00:51.775 Waited 4 seconds for data to become available,
> waiting again...
> 
> and this in mythbackend.log
> 2005-07-10 11:36:56.911 IOBOUND - blocking in ThreadedFileWriter::Write()
> 2005-07-10 11:43:03.390 IOBOUND - blocking in ThreadedFileWriter::Write()
> 2005-07-10 11:43:12.602 IOBOUND - blocking in ThreadedFileWriter::Write()
> 2005-07-10 11:43:12.625 IOBOUND - blocking in ThreadedFileWriter::Write()
> 2005-07-10 11:43:16.308 IOBOUND - blocking in ThreadedFileWriter::Write()
> 
> Skipping back will often unfreeze the picture an allow playback to
> continue,
> although I have noticed the audio getting out of sync after this.
> 
> I've spent a long time searching archives and have tried a few things. Any
> suggestions/solutions would be great as this is the only issue I have with
> an otherwise great system.
> 
> My config:
> P4 3.0 GHz
> 2GB RAM
> PVR350
> Fedora Core 3 2.6.11-1.27_FC3smp
> mythtv-0.18.1-113
> ivtv 0.3.6w
> recording on xfs
> 
> 
> >Date: Wed, 22 Jun 2005 09:22:49 -0700
> >From: Steve Pugh <spugh at edenfx.com>
> >Subject: [mythtv-users] New Myth/ivtv error
> >To: mythtv-users at mythtv.org
> >Message-ID: <42B99059.20702 at edenfx.com>
> >Content-Type: text/plain; charset=iso-8859-1; format=flowed
> >
> >Hello all,
> >
> >My Myth box, specs below, has been in "safe production" (the old Replay
> >TV is not yet unplugged) for about two weeks now.  Over the weekend, it
> >became unresponsive to remote and I could not get in via Mythweb.  SSH
> >was sluggish but I could get in.  Restarting gave me the 'GDM could not
> >write to your authorization file" error, and executing 'df -h' showed
> >that my hda / partition was 100% full.
> >
> >I traced the culprit to /var/log/syslog, which was almost 700MB.
> >Roughly 99% of it was the following, repeating and very frequent judging
> >from the timestamps:
> >
> >     mythtv kernel: ivtv: DEC: Decoder wants 0x00010000 bytes, bad memory
> >location 0x00010000.
> >     mythtv kernel ivtv: DEC: Decoder wants 0x00010000.
> >
> >The above lines repeat anywhere from eight to twelve times, sometimes
> >the shorter line will appear twice, sometimes the longer line within the
> >repeating block, then the following might appear, and then they repeat
> >some more:
> >
> >     mythtv kernel ivtv: DEC: Decoder w010000.
> >
> >I'm going to post this to the ivtv list as well, but y'all are pretty
> >smart people and so I thought I'd ask you as well.  Thanks for any
> >suggestions/ideas you can offer!
> >
> >     -Steve
> >     Dual 2.4GHz Intel
> >     Knoppmyth R5A16, Myth 0.18.1
> >     PVR-350, PVR-250, ivtv 0.3.6g
> >
> >
> 

Personally I would use the 0.2 branch of the ivtv driver for the
PVR-350/250. You only need the 0.3 branch if you are using the PVR-150/500
or the MCE cards.
If you are set on using the 0.3 try this from Jarod's guide
0.2 is considered the stable branch, 0.3 is the unstable/development branch.

echo 16384 > /proc/sys/vm/min_free_kbytes 
echo "# Fix ivtv memory allocation problems" >> /etc/sysctl.conf
echo "vm.min_free_kbytes=16384" >> /etc/sysctl.conf

The guide says something like, this is only needed for some people. If you
are able to load the ivtv module before these lines you don't need them.
However, in your situation it may help.

Also make note that this is not a problem with MythTV but a problem with
IVTV. So searching the Myth list historys will not always yield results. You
would have better luck going to he IVTV people and asking for help.




More information about the mythtv-users mailing list