Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


brian at interlinx

Apr 19, 2012, 3:43 AM

Post #1 of 6 (784 views)
Permalink
DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried

Running 0.25-fixes, I was doing a 3 program multirec last night on an
HVR-950Q and all three recordings just stopped suddenly. During the
window of the recordings (1 @ 20:00 and 2 @ 20:30 all ending at 21:00)
the backend log reports:

Apr 18 20:01:18 pvr mythbackend[1857]: I ProcessRequest recorderbase.cpp:386 (GetKeyframePositions) RecBase(2:/dev/dvb/adapter0/frontend0): GetKeyframePositions(1813,9223372036854775807,#10) out of 93
Apr 18 20:01:18 pvr mythbackend[1857]: I ProcessRequest recorderbase.cpp:386 (GetKeyframePositions) RecBase(6:/dev/dvb/adapter1/frontend0): GetKeyframePositions(1936,9223372036854775807,#3) out of 133

And similar:

Apr 18 20:30:32 pvr mythbackend[1857]: I ProcessRequest recorderbase.cpp:386 (GetKeyframePositions)
RecBase(3:/dev/dvb/adapter0/frontend0): GetKeyframePositions(634,9223372036854775807,#21) out of 72
Apr 18 20:30:32 pvr mythbackend[1857]: I ProcessRequest recorderbase.cpp:386 (GetKeyframePositions) RecBase(1:/dev/dvb/adapter0/frontend0): GetKeyframePositions(808,9223372036854775807,#4) out of 73

And then this:

Apr 18 20:32:04 pvr mythbackend[1857]: E DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried

At the end of the recording the following messages were reported:

Apr 18 20:59:59 pvr mythbackend[1857]: I TVRecEvent tv_rec.cpp:812 (FinishedRecording) TVRec(2): FinishedRecording(2917_2012-04-18T20:00:00) damaged recq:<RecordingQuality overall_score="0" key="2917_2012-04-18T20:00:00" countinuity_error_count="0" packet_count="3257088">#012 <Gap start="2012-04-18T20:32:03" end="2012-04-18T21:00:00" duration="1677" />#012</RecordingQuality>
Apr 18 20:59:59 pvr mythbackend[1857]: I TVRecEvent tv_rec.cpp:812 (FinishedRecording) TVRec(3): FinishedRecording(3776_2012-04-18T20:30:00) damaged recq:<RecordingQuality overall_score="0" key="3776_2012-04-18T20:30:00" countinuity_error_count="0" packet_count="278934">#012 <Gap start="2012-04-18T20:32:01" end="2012-04-18T21:00:00" duration="1679" />#012</RecordingQuality>
Apr 18 20:59:59 pvr mythbackend[1857]: I TVRecEvent tv_rec.cpp:812 (FinishedRecording) TVRec(1): FinishedRecording(4097_2012-04-18T20:30:00) damaged recq:<RecordingQuality overall_score="0" key="4097_2012-04-18T20:30:00" countinuity_error_count="0" packet_count="228902">#012 <Gap start="2012-04-18T20:32:01" end="2012-04-18T21:00:00" duration="1679" />#012</RecordingQuality>

Notice that all three of those report a RecordingQuality that includes
a "Gap" that starts at 20:32:01-03 which is within a second or two of
the above "AssemblePSIP" error.

Additionally, the following is logged at the end of those three
recordings:

Apr 18 20:59:59 pvr mythbackend[1857]: W DeviceReadBuffer DeviceReadBuffer.cpp:525 (Poll) DevRdB(/dev/dvb/adapter0/frontend0): Poll took an unusually long time 1674946 ms

There is nothing in my kernel log buffer during that window other than
a firmware load for the HVR-950Q device.

Any ideas what happened at 20:32:04?

Cheers,
b.
Attachments: signature.asc (0.26 KB)


dekarl at spaetfruehstuecken

Apr 20, 2012, 12:10 AM

Post #2 of 6 (715 views)
Permalink
Re: DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried [In reply to]

On 19.04.2012 12:43, Brian J. Murrell wrote:
> (AssemblePSIP) Error: offset>181, pes length& current cannot be queried

This message is likely a red herring.
It sounds like the reception had issues for "some reason" which
resulted in data that was not valid which led to the message.

Are there related messages around the same time in other logs? Maybe USB
disconnects or issues with interrupts?

Regards,
Karl
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


brian at interlinx

Apr 20, 2012, 6:56 AM

Post #3 of 6 (715 views)
Permalink
Re: DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried [In reply to]

On Fri, 2012-04-20 at 09:10 +0200, Karl Dietz wrote:
> This message is likely a red herring.

Seriously? All hell breaks loose and within 1-2 seconds of all hell
breaking loose there is a non-usual message and you don't think it's
related?

> Are there related messages around the same time in other logs? Maybe USB
> disconnects or issues with interrupts?

No. I think I provided the entire dmesg for the time window covering
this event and it only included the firmware loading of the device at
the top of the (time) window.

Cheers,
b.


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dheitmueller at kernellabs

Apr 20, 2012, 7:07 AM

Post #4 of 6 (714 views)
Permalink
Re: DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried [In reply to]

On Fri, Apr 20, 2012 at 9:56 AM, Brian J. Murrell <brian [at] interlinx> wrote:
> On Fri, 2012-04-20 at 09:10 +0200, Karl Dietz wrote:
>> This message is likely a red herring.
>
> Seriously?  All hell breaks loose and within 1-2 seconds of all hell
> breaking loose there is a non-usual message and you don't think it's
> related?

I think what Karl is suggesting is that the message in the log is a
side-effect of data not being delivered from the device. It's not the
cause of the failure but rather an effect of it.

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


brian at interlinx

Apr 20, 2012, 10:58 AM

Post #5 of 6 (705 views)
Permalink
Re: DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried [In reply to]

On Fri, 2012-04-20 at 10:07 -0400, Devin Heitmueller wrote:
>
> I think what Karl is suggesting is that the message in the log is a
> side-effect of data not being delivered from the device. It's not the
> cause of the failure but rather an effect of it.

Ahhh. Apologies for my misinterpretation. I most certainly would buy
that it could be just another affect of the problem though.

Cheers,
b.


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dekarl at spaetfruehstuecken

Apr 20, 2012, 2:20 PM

Post #6 of 6 (745 views)
Permalink
Re: DVBRead mpeg/mpegstreamdata.cpp:362 (AssemblePSIP) Error: offset>181, pes length & current cannot be queried [In reply to]

On 20.04.2012 19:58, Brian J. Murrell wrote:
> On Fri, 2012-04-20 at 10:07 -0400, Devin Heitmueller wrote:
>>
>> I think what Karl is suggesting is that the message in the log is a
>> side-effect of data not being delivered from the device. It's not the
>> cause of the failure but rather an effect of it.
>
> Ahhh. Apologies for my misinterpretation. I most certainly would buy
> that it could be just another affect of the problem though.

no worreis. That's what I was trying to say. The message is an effect,
not the root cause.

Regards,
Karl
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.