Can anyone confirm that Ticket 2664 made it into 0.20.1?

Is anyone able to confirm that Ticket 2664 was put in the
0.20.1
release?  I am having a similar problem to what this ticket
describes
and before reporting it I want to be sure the fix has made
it?

2664 is not listed on
http://www.mythtv.org/wiki/index.php/Release_Notes_-_
0.20.1 so at
first glance even though it says on
http://svn.myt
htv.org/trac/ticket/2664 it has been put in the fixes
release it does not look like it made it?

Please help 

TIA
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 23/05/07, nospam312 <nospam312gmail.com> wrote:
> Is anyone able to confirm that Ticket 2664 was put in
the 0.20.1
> release?  I am having a similar problem to what this
ticket describes
> and before reporting it I want to be sure the fix has
made it?
>
> 2664 is not listed on
> http://www.mythtv.org/wiki/index.php/Release_Notes_-_
0.20.1 so at
> first glance even though it says on
> http://svn.myt
htv.org/trac/ticket/2664 it has been put in the fixes
> release it does not look like it made it?

Looking at the revision histories of the files referenced in
the
r12480_backported.diff patch and their content, this patch
has *not*
been applied to the 0.20-fixes branch - even though the SVN
ticket
message from 2007-01-12 says otherwise.

-- 
Nick

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
ht
tp://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best
interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

> > http://svn.myt
htv.org/trac/ticket/2664 it has been put in the fixes
> > release it does not look like it made it?
> Looking at the revision histories of the files
referenced in the
> r12480_backported.diff patch and their content, this
patch has *not*
> been applied to the 0.20-fixes branch - even though the
SVN ticket
> message from 2007-01-12 says otherwise.

Thanks Nick.  Any idea on the best procedure of getting this
put in as
this fix might address the problems / very similar problems
that
people have been reporting over the past couple of months
with certain
channels crashing the backend with reproducable segfaults?

I assume if its wasn't in 0.20-fixes it will not be in the
recent
0.20.1 release either.

Someone please help me/us 

TIA
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 23/05/07, nospam312 <nospam312gmail.com> wrote:
> > > http://svn.myt
htv.org/trac/ticket/2664 it has been put in the fixes
> > > release it does not look like it made it?
> > Looking at the revision histories of the files
referenced in the
> > r12480_backported.diff patch and their content,
this patch has *not*
> > been applied to the 0.20-fixes branch - even
though the SVN ticket
> > message from 2007-01-12 says otherwise.
>
> Thanks Nick.  Any idea on the best procedure of getting
this put in as
> this fix might address the problems / very similar
problems that
> people have been reporting over the past couple of
months with certain
> channels crashing the backend with reproducable
segfaults?
>
> I assume if its wasn't in 0.20-fixes it will not be in
the recent
> 0.20.1 release either.

Talking to Janne on #mythtv, the patch attached was
"too big" to be
applied and will "probably not" be backported to
0.20-fixes. I would
hope that since this is a fix it will be backported. It
fixes
something broken in 0.20, after all.

Are you using mythbackend logging other than
important,general? Janne
said non-standard logging could be causing some of the
problems. The
patch also reassigns some logging from IMPORTANT to RECORD.

-- 
Nick

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
ht
tp://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best
interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

> Talking to Janne on #mythtv, the patch attached was
"too big" to be
> applied and will "probably not" be backported
to 0.20-fixes. I would
> hope that since this is a fix it will be backported. It
fixes
> something broken in 0.20, after all.
> Are you using mythbackend logging other than
important,general? Janne
> said non-standard logging could be causing some of the
problems. The
> patch also reassigns some logging from IMPORTANT to
RECORD.

I experienced the problem with just the standard/default
logging.  I
then ran mythbackend using the -v all option to try to find
the cause
of the problem.

I have posted my results on this message (
http://www.gossamer-threads.com/lists/mythtv/use
rs/269444#269444) and
then someone pointed me towards the 2664 ticket and it does
have
similar error messages to what I am getting so it might be
the same
problem.

I am worried that the fix is not going to be included in a
future
release so I will never get my HTPC to work.

As this problem is still ongoing should the trac ticked be
reopened to
make sure it continues to be tracked as a problem people
are
experiencing?

Thanks for your continued help.
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 24/05/07, nospam312 <nospam312gmail.com> wrote:

> As this problem is still ongoing should the trac ticked
be reopened to
> make sure it continues to be tracked as a problem
people are
> experiencing?

The patch has been committed to SVN trunk, so it *will* make
it into
0.21 The issue is whether any devs with commit rights deem
it
necessary to backport into 0.20-fixes. I would hope they do
based on
the number of HDHR backports (and asked as much on IRC) -
Janne even
sorted a suitable patch and attached it to the ticket, but
it was
never committed, and the consensus was that it may never
be.

Aside from upgrading to SVN, which is not a useful answer
for a user
following 0.20-fixes, there were no other useful suggestions
aside
from Janne's of changing logging verbosity to the standard
'important,general'.

-- 
Nick

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
ht
tp://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best
interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

> Aside from upgrading to SVN, which is not a useful
answer for a user
> following 0.20-fixes, there were no other useful
suggestions aside
> from Janne's of changing logging verbosity to the
standard
> 'important,general'.

Changing the logging verbosity does not seem to help with
the problem
for me so I am giving the SVN version a try.  I have managed
to svn
the latest version and get it compiled (revision 13500) and
done a
quick test leaving it on live tv for 45 minutes on an
affected channel
and no problems so far but that could just be coincidence as
sometimes
it can manage 60 minutes without a problem (15 minutes was
the average
time before segfault before however).  I will give it a
proper 2 hour
test tomorrow and report back.
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 26/05/07, nospam312 <nospam312gmail.com> wrote:
> > Aside from upgrading to SVN, which is not a useful
answer for a user
> > following 0.20-fixes, there were no other useful
suggestions aside
> > from Janne's of changing logging verbosity to the
standard
> > 'important,general'.
>
> Changing the logging verbosity does not seem to help
with the problem
> for me so I am giving the SVN version a try.  I have
managed to svn
> the latest version and get it compiled (revision 13500)
and done a
> quick test leaving it on live tv for 45 minutes on an
affected channel
> and no problems so far but that could just be
coincidence as sometimes
> it can manage 60 minutes without a problem (15 minutes
was the average
> time before segfault before however).  I will give it a
proper 2 hour
> test tomorrow and report back.

Please post exactly which capture card you are using (dmesg
output
might be useful) as there are known issues with some cards -
the
Hauppauge Nova-T 500 for example.

-- 
Nick

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
ht
tp://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best
interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

> Please post exactly which capture card you are using
(dmesg output
> might be useful) as there are known issues with some
cards - the
> Hauppauge Nova-T 500 for example.

Have spent the last few days doing some testing with the
trunk version
(revision 13500/13529) but it is still crashing.

When the crash occurs the only common item in the log near
where it
failed is a line "PESPacket: Failed CRC check 0x0 !=
0xffffffff for
StreamID = 0x0" note this is always with a 0x0 and
0xffffffff and not
more realistic values.

Could this be a case that has not been caught by the fix?

If this does not shed any light on the problem I would like
to create
a segfault report to try to help further - can anyone point
me to a
URL with what I need to do to help?

It still only appears to affect one multiplex so I do not
think it is
hardware related - it is like Mythtv does not like the way
one
multiplex is transmitting.

My cards are LifeView FlyDVB-T
(http://www.lifeview.com.tw/html/products/interna
l_tv/flydvbt.htm)
DVB: registering new adapter (saa7134[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)...

Any help greatly appreciated.
_______________________________________________
mythtv-users mailing list
mythtv-usersmythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users