[mythtv-users] 9.10/0.22 playback causes drive problems

Stuart Larson halcyon at obfus.com
Wed Nov 25 16:20:07 UTC 2009


> On Mon, Nov 23, 2009 at 11:27 PM, Jonno <jonnojohnson at gmail.com> wrote:
>> On Mon, Nov 23, 2009 at 1:43 PM, Jonno <jonnojohnson at gmail.com> wrote:
>>> On Mon, Nov 23, 2009 at 11:47 AM, Jonno <jonnojohnson at gmail.com> wrote:
>>>> Since upgrading to Mythbuntu 9.10 I've been having major problems when
>>>> trying to watch recorded shows. I get occasional visual abberrations
>>>> combined with an audio distortion that sounds a bit like a light
>>>> saber. After a while the show will freeze and I get a message that
>>>> there were too many frame buffers or something like that. It also
>>>> makes the drive I store recordings on inaccessible and I find I have
>>>> to reboot.
>>>>
>>>> My setup is an ASUS P1-AH2 barebones system with on-board Nvidia 6150
>>>> graphics. There is an IDE drive which hosts the system and then a SATA
>>>> drive (xfs) which hosts the recordings. Everything ran fine on
>>>> Mythbuntu 9.04
>>>>
>>>> At first I noticed that the recordings drive was heavily (>90%)
>>>> fragmented so I've been working on that but now it is <12% fragmented
>>>> and the problems are still happening. It also happens on new
>>>> recordings which shouldn't be fragmented at all. I've run xfs_repair
>>>> also and it doesn't seem to come up with any error messages.
>>>>
>>>> Has there been a major change in 0.22 that could mean my 6150 chipset
>>>> can't keep up with the graphics display?
>>>> Is there a way to check that the problem is with playback rather than
>>>> in the recording process?
>>>> I could add a graphics card but this will mean removing the wireless
>>>> card which in turn means getting around to wiring ethernet cable to
>>>> the tv which I haven't found time to do. I'd like to first figure out
>>>> if that is really the problem.
>>>>
>>>> Any other suggestions would be welcome.
>>>
>>> I forgot the obvious. Will post front and backend logs this evening.
>>>
>> Ok so there is a lot of this in the backend log:
>> ----------
>> 2009-11-23 06:59:00.711 [mpeg2video @ 0x7f0cbd3c7820]ac-tex damaged at
>> 50 0
>> 2009-11-23 06:59:00.712 [mpeg2video @ 0x7f0cbd3c7820]00 motion_type at
>> 26 3
>> 2009-11-23 06:59:00.840 Reschedule requested for id 0.
>> 2009-11-23 06:59:00.902 [mpeg2video @ 0x7f0cbd3c7820]00 motion_type at
>> 44 29
>> 2009-11-23 06:59:00.925 [mpeg2video @ 0x7f0cbd3c7820]00 motion_type at
>> 11 30
>> 2009-11-23 06:59:01.150 [mpeg2video @ 0x7f0cbd3c7820]ac-tex damaged at 8
>> 23
>> 2009-11-23 06:59:01.331 [mpeg2video @ 0x7f0cbd3c7820]00 motion_type at
>> 60 59
>> 2009-11-23 06:59:01.592 [mpeg2video @ 0x7f0cbd3c7820]slice mismatch
>> ----------
>> Also in the frontend log is a lot of this:
>> Code:
>> ----------
>> 2009-11-22 21:55:10.790 [mpeg2video @ 0x7f35b0d89820]ac-tex damaged at
>> 84 25
>> 2009-11-22 21:55:10.790 [mpeg2video @ 0x7f35b0d89820]00 motion_type at
>> 43 26
>> 2009-11-22 21:55:10.792 [mpeg2video @ 0x7f35b0d89820]ac-tex damaged at
>> 91 28
>> 2009-11-22 21:55:10.796 [mpeg2video @ 0x7f35b0d89820]Warning MVs not
>> available
>> 2009-11-22 21:55:13.384 [ac3 @ 0x7f35b0d89820]frame CRC mismatch
>> 2009-11-22 21:55:13.415 [ac3 @ 0x7f35b0d89820]incomplete frame
>> 2009-11-22 21:55:13.416 [ac3 @ 0x7f35b0d89820]invalid frame size
>> 2009-11-22 21:55:13.914 [mpeg2video @ 0x7f35b0d89820]Warning MVs not
>> available
>> 2009-11-22 21:55:17.389 [ac3 @ 0x7f35b0d89820]frame CRC mismatch
>> 2009-11-22 21:55:17.425 [ac3 @ 0x7f35b0d89820]incomplete frame
>> 2009-11-22 21:55:17.425 [ac3 @ 0x7f35b0d89820]invalid frame size
>> ----------
>> and eventually:
>> ----------
>> 2009-11-22 22:13:27.954 NVP(0): prebuffering pause
>> 2009-11-22 22:13:27.999
>> RingBuf(/var/lib/mythtv/recordings/1181_20091121210000.mpg): Waited
>> 1.0 seconds for data to become available...
>> 2009-11-22 22:13:28.999
>> RingBuf(/var/lib/mythtv/recordings/1181_20091121210000.mpg): Waited
>> 2.0 seconds for data to become available...
>> 2009-11-22 22:13:29.287 NVP(0): Prebuffer wait timed out 10 times.
>> 2009-11-22 22:13:30.620 NVP(0): Prebuffer wait timed out 20 times.
>> 2009-11-22 22:13:31.001
>> RingBuf(/var/lib/mythtv/recordings/1181_20091121210000.mpg): Waited
>> 4.0 seconds for data to become available...
>> 2009-11-22 22:13:31.954 NVP(0): Prebuffer wait timed out 30 times.
>> 2009-11-22 22:13:33.287 NVP(0): Prebuffer wait timed out 40 times.
>> 2009-11-22 22:13:34.620 NVP(0): Prebuffer wait timed out 50 times.
>> 2009-11-22 22:13:35.003
>> RingBuf(/var/lib/mythtv/recordings/1181_20091121210000.mpg): Waited
>> 8.0 seconds for data to become available...
>> 2009-11-22 22:13:35.954 NVP(0): Prebuffer wait timed out 60 times.
>> 2009-11-22 22:13:37.287 NVP(0): Prebuffer wait timed out 70 times.
>> 2009-11-22 22:13:38.620 NVP(0): Prebuffer wait timed out 80 times.
>> 2009-11-22 22:13:39.954 NVP(0): Prebuffer wait timed out 90 times.
>> 2009-11-22 22:13:41.287 NVP(0): Prebuffer wait timed out 100 times.
>> 2009-11-22 22:13:41.287 NVP(0), Error: Timed out waiting for
>> prebuffering too long. Exiting..
>> 2009-11-22 22:13:41.414 TV: Attempting to change from Watching
>> WatchingPreRecorded to None
>> 2009-11-22 22:13:42.446
>> RingBuf(/var/lib/mythtv/recordings/1181_20091121210000.mpg): Waited
>> too long for ringbuffer pause..
>> 2009-11-22 22:13:43.452
>> RingBuf(/var/lib/mythtv/recordings/1181_20091121210000.mpg): Waited
>> too long for ringbuffer pause..
>> ----------
>>
> Anyone? I tried watching LiveTV last night and the picture really
> breaks up quite often. I'm guessing that since the backend shows
> errors that the problem is with recording rather than playing.
> I had top running while I was watching LiveTV and it didn't seem like
> the processor was under an undue burden. Also I didn't have any
> problems like this with 9.04.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

I didn't catch what you were using to record? (maybe I missed it)  I've
recently had a lot of the frame CRC mismatch errors and the pskew pskew
sounds that come with it.  I got those errors (recordings from my
HDHomeRun were unwatchable) while using the built-in ethernet NIC
(forcedeth driver).  I put in a 10/100 card which uses the tulip driver
(ADMtek NC100) and aside from occasional OTA reception issues, those
errors and sound effects are gone.



More information about the mythtv-users mailing list