[mythtv-users] HDPVR Causing Backend to Hard Freeze

Jason Sharpe mythtv.list at gmail.com
Tue May 25 14:41:38 UTC 2010


> Message: 7
> Date: Mon, 24 May 2010 15:26:51 -0500
> From: Johnny Walker <johnnyjboss at gmail.com>
> Subject: Re: [mythtv-users] HDPVR Causing Backend to Hard Freeze
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID:
>        <AANLkTiksBRmg2sDOdiVrnso0y5WVyCd2NVJwerVgoSIY at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Mon, May 24, 2010 at 3:16 PM, Jason Sharpe <mythtv.list at gmail.com>
> wrote:
> >
> >> Date: Mon, 24 May 2010 11:22:37 -0500
> >> From: Johnny Walker <johnnyjboss at gmail.com>
> >> Subject: Re: [mythtv-users] HDPVR Causing Backend to Hard Freeze
> >> To: Discussion about mythtv <mythtv-users at mythtv.org>
> >> Message-ID:
> >>        <AANLkTilPeoGbXxGRBAgfeFd6mhijMrsuzgmb-2LzLiZL at mail.gmail.com>
> >> Content-Type: text/plain; charset=ISO-8859-1
> >>
> >> On Mon, May 24, 2010 at 11:16 AM, Jason Sharpe <mythtv.list at gmail.com>
> >> wrote:
> >> >
> >> >>
> >> >> Message: 18
> >> >> Date: Mon, 24 May 2010 11:36:17 -0400
> >> >> From: Greg <greg12866 at nycap.rr.com>
> >> >> Subject: Re: [mythtv-users] HDPVR Causing Backend to Hard Freeze
> >> >> To: Discussion about mythtv <mythtv-users at mythtv.org>
> >> >> Message-ID: <4BFA9CF1.5040204 at nycap.rr.com>
> >> >> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> >> >>
> >> >> On 05/24/2010 09:47 AM, Jason Sharpe wrote:
> >> >> >
> >> >> >     Date: Sun, 23 May 2010 23:43:35 -0500
> >> >> >     From: <mythtv.list at gmail.com <mailto:mythtv.list at gmail.com>>
> >> >> >     Subject: [mythtv-users] HDPVR Causing Backend to Hard Freeze
> >> >> >     To: mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
> >> >> >     Message-ID:
> >> >> >     <AANLkTik9Zpyq8ZGeHXcEEKNrF8ZOXOqSYFqqVJguPivq at mail.gmail.com
> >> >> >
> >> >> >
> >> >> > <mailto:
> AANLkTik9Zpyq8ZGeHXcEEKNrF8ZOXOqSYFqqVJguPivq at mail.gmail.com>>
> >> >> >     Content-Type: text/plain; charset="iso-8859-1"
> >> >> >
> >> >> >     Hello,
> >> >> >
> >> >> >     I have been fighting this issue for a days now and I wanted to
> >> >> >     throw this
> >> >> >     out there to see if anyone else has seen/heard of anything like
> >> >> >     this. I can
> >> >> >     recreate the issue over and over but I am not sure what is
> >> >> > causing
> >> >> > it.
> >> >> >
> >> >> >     When one recording is ending on a tuner and another is
> beginning
> >> >> >     on my HDPVR
> >> >> >     my whole backend hard freezes requiring a push of the reset
> >> >> > button
> >> >> >     for the
> >> >> >     PC to come back up.
> >> >> >
> >> >> >     In Other Words:
> >> >> >     Tuner 1: HD Homerun Records from 09:00 - 10:00
> >> >> >     Tuner 2: HDPVR Has a show starting at 10:00
> >> >> >
> >> >> >     At 09:59 when the backend should start recording from the HDPVR
> >> >> >     the backend
> >> >> >     hard freezes.
> >> >> >
> >> >> >     Using that example above, if the HDPVR starts to record at
> 09:30
> >> >> >     everything
> >> >> >     is fine. It is only when 1 show is ending and another is
> >> >> > beginning
> >> >> >     on the
> >> >> >     HDPVR.
> >> >> >
> >> >> >     I can record from each tuner just fine for multiple shows back
> to
> >> >> >     back on
> >> >> >     the same tuner without issue, so the tuners work.
> >> >> >
> >> >> >     Here is the strange thing, the other way around, there is no
> >> >> > freezing.
> >> >> >
> >> >> >     Meaning:
> >> >> >     Tuner 1: HDPVR Records from 09:00 - 10:00
> >> >> >     Tuner 2: HD Homerun Has a show starting at 10:00
> >> >> >
> >> >> >     In that senerio, everything works just fine.
> >> >> >
> >> >> >     I have elimitated the HD Homerun as the source of the problem
> by
> >> >> >     trying a
> >> >> >     pcHDTV HD-3000 instead, still freezes.
> >> >> >
> >> >> >     Details:
> >> >> >     HD Homerun using Tuner 0 (Over the Air ATSC)
> >> >> >     HDPVR and a Dishnetwork ViP 211k receiver (Component and SPDIF)
> >> >> >
> >> >> >     Note: IR blasting is done via a homebrew serial blaster, I am
> >> >> >     _not_ using
> >> >> >     the HDPVR for blasting.
> >> >> >
> >> >> >     Both the HD Homerun and the HDPVR are running the latest
> >> >> > firmware.
> >> >> >     I was
> >> >> >     going to downgrade the firmware in the HDPVR, but I read that
> the
> >> >> >     previous
> >> >> >     version had its own problems.
> >> >> >
> >> >> >     I am running Mythdora 12.23, mythbackend version:
> >> >> > tags/release-0-23
> >> >> >     [0.23-1.md12 (r24509).
> >> >> >
> >> >> >     The backend log isn't much help, since when it freezes it can't
> >> >> >     write to it,
> >> >> >     heh (HW Tuner 44 is the HDPVR)
> >> >> >
> >> >> >     2010-05-23 21:58:00.784 Reschedule requested for id 0.
> >> >> >     2010-05-23 21:58:01.977 Scheduled 781 items in 1.2 = 0.01 match
> +
> >> >> >     1.17 place
> >> >> >     2010-05-23 21:58:01.991 scheduler: Scheduled items: Scheduled
> 781
> >> >> >     items in
> >> >> >     1.2 = 0.01 match + 1.17 place
> >> >> >     2010-05-23 21:58:29.861 TVRec(44): ASK_RECORDING 44 29 0 0
> >> >> >     2010-05-23 21:59:01.227 ProgramInfo(): Updated pathname '':''
> ->
> >> >> >     '5389_20100523215900.mpg'
> >> >> >     2010-05-23 21:59:01.346 TVRec(44): Changing from None to
> >> >> > RecordingOnly
> >> >> >     2010-05-23 21:59:01.358 TVRec(44): HW Tuner: 44->44
> >> >> >     2010-05-23 21:59:02.471 ret_pid(0) child(11739) status(0x0)
> >> >> >     2010-05-23 21:59:03.484 ret_pid(0) child(11739) status(0x0)
> >> >> >     2010-05-23 21:59:04.501 ret_pid(0) child(11739) status(0x0)
> >> >> >     2010-05-23 21:59:05.519 ret_pid(0) child(11739) status(0x0)
> >> >> >     2010-05-23 21:59:06.536 ret_pid(0) child(11739) status(0x0)
> >> >> >
> >> >> >     The next line of the log is the backend starting after I had to
> >> >> >     push the
> >> >> >     reset button.
> >> >> >
> >> >> >     I am at my wits end, any ideas?
> >> >> >
> >> >> >     Thanks in advance for any help.
> >> >> >
> >> >> >
> >> >> >
> >> >> > So I spent some more time working on the issue this morning.
> >> >> >
> >> >> > I downgraded the firmware of the HDPVR, no change, still hangs as
> >> >> > described.
> >> >> >
> >> >> > I reloaded the newest firmware of the HDPVR into it and changed the
> >> >> > USB port it was plugged into making sure it was on a different bus,
> >> >> > no
> >> >> > change, still hangs as described.
> >> >> >
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > mythtv-users mailing list
> >> >> > mythtv-users at mythtv.org
> >> >> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >> >> >
> >> >> Most people with this problem add a sleep to their channel changing
> >> >> script...Search this list for hdpvr channel script... I would guess
> >> >> that
> >> >> is your problem also..
> >> >
> >> >
> >> > Thanks for the reply.
> >> >
> >> > I had read that when I got the HDPVR, so since day 1 with the HDPVR I
> >> > have
> >> > had a 3 sec sleep at the end of the script. I just checked my script
> and
> >> > confirmed the 3.0 sec sleep at the end.
> >> >
> >> > Any other ideas?
> >> >
> >>
> >> Seeings as you're on Mythdora and I've not used it I was trying to
> >> stay out of this thread.
> >>
> >> However I am curious if you run the backend with '-v most' and
> >> pastebin the logs and post the link back here if we'd see something
> >> more meaningful.
> >>
> >> Also is .23-release in your version number indicative that you're NOT
> >> following the fixes branch? Someone with more experience with a fedora
> >> based OS might want to suggest how to get the fixes branch on your
> >> box.
> >>
> >> -Johnny
> >>
> >
> > Thanks all to who are replying, I have been troubleshooting all morning.
> >
> > I updated the kernel hoping it would become more stable, it now is. I am
> > running  kernel.i686 0:2.6.32.12-115.fc12.
> >
> > Now the backend computer doesn't freeze when I have the problem, so it
> does
> > provide more logging. (A side note: it doesn't hang however I lose
> network
> > connectivity when this happens, a reboot brings the network back)
> >
> > I am NOT running the fixes branch of mythtv.
> >
> > Checking the system log messages, I get this EVERY time the IR Blaster is
> > accessed, either on backend startup, manually sending commands, or normal
> > recordings:
> >
> > May 24 13:40:48 localhost lircd-0.8.6[1780]: accepted new client on
> > /dev/lircd1
> > May 24 13:40:48 localhost lircd-0.8.6[1780]: removed client
> > May 24 13:40:48 localhost lircd-0.8.6[1780]: buffer too small
> > May 24 13:40:49 localhost lircd-0.8.6[1780]: accepted new client on
> > /dev/lircd1
> > May 24 13:40:49 localhost lircd-0.8.6[1780]: removed client
> > May 24 13:40:49 localhost lircd-0.8.6[1780]: buffer too small
> > May 24 13:40:49 localhost lircd-0.8.6[1780]: accepted new client on
> > /dev/lircd1
> > May 24 13:40:50 localhost lircd-0.8.6[1780]: removed client
> > May 24 13:40:50 localhost lircd-0.8.6[1780]: buffer too small
> >
> > running:
> >
> > [root at mythtv storage] mythbackend -v most > crash.log
> > irsend: timeout
> > irsend: timeout
> > irsend: timeout
> > irsend: timeout
> >
> >
> > The timeouts don't appear when the backend starts, they show up when the
> > script runs to change the channel when another tuner is running.
> > Note: If no other tuner is recording, I can record from the HDPVR without
> > issue, that is the confusing part.
> >
> > You can view the crash.log at: http://pastebin.com/mMWVbrjn
> >
> > HW Tuner 44 is the HDPVR
> > The recording starts on line 4081
> > When this recording starts I am recording something on the HD Homerun
> >
> > My Channel Change Script is:
> >
> > #!/bin/bash
> > PATH=/bin:/usr/bin:/usr/sbin
> >
> > REMOTE=dish
> > irsend --device=/dev/lircd1 SEND_START $REMOTE SELECT
> > sleep 4.0
> > for digit in `echo $1 | sed 's/\(.\)/\1 \n/g'` ; do
> >         irsend --device=/dev/lircd1 SEND_START $REMOTE $digit
> >         sleep 0.2
> > done
> >
> > irsend --device=/dev/lircd1 SEND_START $REMOTE SELECT
> > sleep 0.2
> > irsend --device=/dev/lircd1 SEND_START $REMOTE CANCEL
> > sleep 3.0
> >
> >
> >
> > The first select is to wake up the receiver if it is asleep, the last
> cancel
> > is to get rid of the OSD from the receiver
> >
> > Thanks again, I would glady by someone a cold case of beer if they have
> the
> > answer..:)
> >
>
> as a troubleshooting idea - if you change your channel change command
> to "/bin/true" and make sure the cable box is already providing signal
> does the problem go away?
>
>
>
I followed your idea and changed the channel change script in mythtvsetup
to  /bin/true and YES the problem did go away I recorded on both tuners
about 20 times switching back and forth between tuners and it didn't freeze
once. It ALWAYS hung on the first time so I think it is safe to say that the
problem did go away using /bin/true.

So with the irsend time outs and the other clues, I think it does have
something with the way I am blasting.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100525/cd5896f9/attachment.htm>


More information about the mythtv-users mailing list