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

Mailing List Archive: MythTV: Commits

Ticket #5278: Firewire Uses Bad Port Number and Fails

  

 
First page Previous page 1 2 3 Next page Last page  View All MythTV commits RSS feed   Index | Next | Previous | View Threaded


mythtv at cvs

Apr 30, 2008, 9:21 PM

Post #1 of 54 (3728 views)
Permalink
Ticket #5278: Firewire Uses Bad Port Number and Fails
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Mlocked: 0
---------------------------------+------------------------------------------
This occurs when using mythtv with a firewire connected HD cable box.
Specifically Motorola DCH3200.

Occasionally (often after performing a channel change), the backend will
no longer record or stream any channel via firewire - this condition
persists until the mythbackend is restarted at which point it works again.
Further, no error is displayed, rather (if in live tv mode) the screen
will simply remain blank for half a minute then return to the menu.

The issue is not related to channel changing or stable broadcast as it
will successfully change channels on the digital box and firewire_tester
indicates a stable connection. Rather, it seems like the firewire node or
port number is reverting to -1 for some reason (which presumably gets
cleared out when restarting the backend and corrects the problem).

Below are the relevant log entries from such an occurence:

TVRec(4): Changing from None to WatchingLiveTV
TVRec(4): HW Tuner: 4->4
LAVCInfo(), Error: Unable to get handle for port: -1
eno: Invalid argument (22)
ret_pid(0) child(9135) status(0x0)
ret_pid(9135) child(9135) status(0x0)
External Tuning program exited with no error
LAVCInfo(), Error: Unable to get handle for port: -1
eno: Invalid argument (22)
...
Preview Error: Previewer file
'/mnt/store/recordings/2212_20080430235337.mpg' is not valid.
Preview Error: Run() file not local:
'/mnt/store/recordings/2212_20080430235337.mpg'
Preview Error: Preview process not ok.
fileinfo(/mnt/store/recordings/2212_20080430235337.mpg.png)
exists: 0 readable: 0 size: 0

From reference after stopping and starting the mythbackend, the same
operation performs correctly and results in this log:

TVRec(4): Changing from None to WatchingLiveTV
TVRec(4): HW Tuner: 4->4
ret_pid(0) child(9471) status(0x0)
ret_pid(9471) child(9471) status(0x0)
External Tuning program exited with no error
AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
LFireDev(001C11FFFEA14FC5): Buffered packets 2000 (8000 KB)

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Apr 30, 2008, 9:24 PM

Post #2 of 54 (3610 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

Easier to read version of above log:

{{{
2008-05-01 00:06:12.775 TVRec(4): Changing from None to WatchingLiveTV
2008-05-01 00:06:12.778 TVRec(4): HW Tuner: 4->4
2008-05-01 00:06:12.779 LAVCInfo(), Error: Unable to get handle for port:
-1
eno: Invalid argument (22)
2008-05-01 00:06:13.788 ret_pid(0) child(9273) status(0x0)
2008-05-01 00:06:14.792 ret_pid(9273) child(9273) status(0x0)
2008-05-01 00:06:14.793 External Tuning program exited with no error
2008-05-01 00:06:15.904 LAVCInfo(), Error: Unable to get handle for port:
-1
eno: Invalid argument (22)
}}}

{{{
2008-05-01 00:06:17.171 Preview Error: Previewer file
'/mnt/store/recordings/2212_20080501000614.mpg' is not valid.
2008-05-01 00:06:17.173 Preview Error: Run() file not local:
'/mnt/store/recordings/2212_20080501000614.mpg'
2008-05-01 00:06:17.179 Preview Error: Preview process not ok.
fileinfo(/mnt/store/recordings/2212_20080501000614.mpg.png) exists: 0
readable: 0 size: 0
}}}

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:1>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

May 30, 2008, 11:18 AM

Post #3 of 54 (3547 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by foom [at] fuhm):

I had this same problem, also with a DCH3200. I worked around it by
telling myth to use broadcast mode instead of P2P, and I think myth is now
working reliably, but I've not been using it long enough to say that with
certainty.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:2>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

May 30, 2008, 11:22 AM

Post #4 of 54 (3543 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

Thanks for the comment. In this case, I however, already am using
broadcast mode for firewire (as P2P was consistently inconsistent so to
speak) so I don't think thats the root of the issue I've been seeing.
Especially as the firewire-tester confirms a valid broadcast connection.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:3>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jun 9, 2008, 6:27 AM

Post #5 of 54 (3511 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------
Changes (by danielk):

* owner: ijr => danielk
* status: new => assigned


--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:4>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jun 9, 2008, 6:28 AM

Post #6 of 54 (3510 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by danielk):

Does it work if you use the internal channel changer rather than an
external one?

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:5>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jun 9, 2008, 9:01 AM

Post #7 of 54 (3505 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

Yes, the behavior is the same when using either internal or external
channel changing (currently I'm using internal changing and it fails in
this manner). It seems to happen more readily if accidentally try to
change channels before it has acquired a full "LAM" lock on the current
one.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:6>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jun 10, 2008, 10:58 AM

Post #8 of 54 (3481 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by Mike Rice <mikerice1969 [at] gmail>):

I've seen this as well. I'm currently trying to get stable recordings
from a DCH3416 box. I am still trying to understand the code but I can
explain what I am seeing in hopes it helps.

Using the internal changer (and broadcast mode) things usually appear fine
directly after restarting the backend. A recording (or LiveTV) starts
recording and after some minutes 15-45 minutes typically there is no
longer any data available and the backend tries to recover with
SignalReset. That does the UpdateDeviceList() which goes through the
ports and nodes and gets the guid (get_guid). My problem is that get_guid
will no longer get the guid as it errors with "temporarily unavailable".
Once it gets into this state it usually stays unavailable but occasionally
it recovers. Of course I can run plugreport during the time the get_guid
read is "temporarily unavailable" and it will report the guid just fine so
I am not sure what to think here.

In any case once the guid goes offline the port and node are set to -1 and
then some odd things start happening. I don't understand the flow enough
to see how OpenPort gets called for one of these offline port/nodes but it
is occasionally appearing in my logs. I've been concentrating on figuring
out why get_guid is failing for me but I'll test any patches or ideas that
are generated.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:7>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jun 10, 2008, 11:17 AM

Post #9 of 54 (3492 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

It seems like allowing the firewire setup as in older versions (in which
the node number was specified manually) as an alternate option to using
GUID could be a work around to this problem, though not a true fix.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:8>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jul 25, 2008, 9:20 AM

Post #10 of 54 (3313 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by notivan):

I have the "same" problem with a Motorola 6200 STB using Mythtv 7.1 and
the "beta" mythprime. This happens quite often and seemingly at random.
Sometimes recording works for a day or two but stable periods rarely last
more than 5 -10 recordings

A typical log of the error is:

2008-07-24 22:59:29.435 TVRec(1): ASK_RECORDING 1 29 0 0
2008-07-24 23:00:02.343 TVRec(1): Changing from None to RecordingOnly
2008-07-24 23:00:02.376 TVRec(1): HW Tuner: 1->1
2008-07-24 23:00:02.377 LAVCInfo(), Error: Unable to get handle for port:
-1
eno: Invalid argument (22)
2008-07-24 23:00:02.409 TVRec(1) Error: Failed to set channel to 63.
Reverting to kState_None
2008-07-24 23:00:02.411 TVRec(1): Changing from RecordingOnly to None

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:9>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jul 27, 2008, 12:28 PM

Post #11 of 54 (3286 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by daver):

I'm seeing the same problem with a DCH3200 HD cable box using a Firewire
connection into a Ubuntu Hardy dedicated backend box running the mythtv-
backend package (0.21.0+fixes16838).

I have the Firewire Capture Card Setup configured using the built-in
DCH-3200 settings with a Broadcast connection at 100 Mbps and both signal
and tuning timeouts set at 4000 ms.

Similar to what others have reported above, every day or two (5-10
Firewire recordings, although there doesn't seem to be any consistency in
this) I get the above LAVCInfo() and TVRec() errors and the Reverting to
kState_None. I think this usually follows a long series of "Warning: No
Input in xxx msec..." warnings from LFireDev and subsequent "ResetBus" and
"SignalReset" messages. As has been reported by others above, simply
stopping and restarting the backend seems to fix the Firewire after it
fails.

I also have two pcHDTV cards for unencrypted cable signals that are rock
solid, so the rest of the system works great.

Please let me know if there has been any progress on this issue. Very
frustrating to miss recordings.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:10>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Oct 5, 2008, 9:01 PM

Post #12 of 54 (3097 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by scottadmi [at] gmail):

Lately a new (possibly related issue) has cropped up. The primary issue
described here remains. Additionally, though, sometimes when I am watching
live HD TV (via firewire) it will lock up when it reaches the end of the
show. In other words, if I'm watching the news on channel 10, and the show
the time hits 7:00PM (marking the end of that show) the backend will screw
up trying to continue watching that very channel live. This log output
does not occur when changing channels - which sometimes works - just when
a new show is starting while watching live HD. The following is a sample
log output:


008-10-05 23:00:01.492 Finished recording Planet Earth "Ice Worlds":
channel 2191
2008-10-05 23:00:04.083 AFD: Opened codec 0x82d6370, id(MPEG2VIDEO)
type(Video)
2008-10-05 23:00:04.090 AFD: codec AC3 has 6 channels
2008-10-05 23:00:04.092 AFD: Opened codec 0x82d6960, id(AC3) type(Audio)
2008-10-05 23:00:04.468 Preview: Grabbed preview
'/mnt/store/recordings/2191_20081005225519.mpg' 1920x1088 [at] 630
2008-10-05 23:00:05.738 LFireDev(001C11FFFEA14FC5), Warning: No Input in
600 msec...
2008-10-05 23:00:05.798 LFireDev(001C11FFFEA14FC5), Warning: No Input in
650 msec...
2008-10-05 23:00:05.858 LFireDev(001C11FFFEA14FC5), Warning: No Input in
700 msec...
2008-10-05 23:00:05.910 LFireDev(001C11FFFEA14FC5), Warning: No Input in
750 msec...
2008-10-05 23:00:05.962 LFireDev(001C11FFFEA14FC5), Warning: No Input in
800 msec...
2008-10-05 23:00:06.014 LFireDev(001C11FFFEA14FC5), Warning: No Input in
850 msec...
2008-10-05 23:00:06.066 LFireDev(001C11FFFEA14FC5), Warning: No Input in
900 msec...
2008-10-05 23:00:06.118 LFireDev(001C11FFFEA14FC5), Warning: No Input in
950 msec...
2008-10-05 23:00:06.170 LFireDev(001C11FFFEA14FC5), Warning: No Input in
1000 msec...
2008-10-05 23:00:06.222 LFireDev(001C11FFFEA14FC5), Warning: No Input in
1050 msec...
2008-10-05 23:00:06.223 LFireDev(001C11FFFEA14FC5): ResetBus() -- begin
2008-10-05 23:00:06.226 LFireDev(001C11FFFEA14FC5): ResetBus() -- end
2008-10-05 23:00:06.226 LFireDev(001C11FFFEA14FC5): SignalReset(157->158)
2008-10-05 23:00:06.227 LFireDev(001C11FFFEA14FC5): SignalReset(157->158):
Updating device list -- begin
2008-10-05 23:00:06.547 LFireDev(001C11FFFEA14FC5): SignalReset(157->158):
Updating device list -- end
2008-10-05 23:00:06.598 LFireDev(001C11FFFEA14FC5), Warning: No Input in
50 msec...
2008-10-05 23:00:06.650 LFireDev(001C11FFFEA14FC5), Warning: No Input in
100 msec...
libiec61883 warning: iec61883_cmp_create_bcast_output: Failed to set the
oPCR[0] plug for node 63.
2008-10-05 23:00:06.651 LFireDev(001C11FFFEA14FC5), Error: Bus Reset :
Failed to reconnect
2008-10-05 23:00:06.702 LFireDev(001C11FFFEA14FC5), Warning: No Input in
150 msec...


It will then repeat this ad-infinidum, requiring me to exit mythtv or the
log will be filled in short order.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:11>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Oct 6, 2008, 7:28 PM

Post #13 of 54 (3068 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by eric [at] lisaneric):

I've seen this or a similar problem also with a Motorola DHC 3200.

What seems to be happening is that my cable box is actually jumping back
and forth between node 0 and node 1. I set up a cron job to run
plugreport hourly and dump the result to a log file. The box has GUID
0x001aadfffe47916e, which usually shows up as node 0, but sometimes as
node 1. Here's an excerpt:


{{{

Wed Oct 1 18:41:01 EDT 2008
libiec61883 error: error reading oMPR
libiec61883 error: error reading iMPR
Host Adapter 0
==============

Node 0 GUID 0x001aadfffe47916e
------------------------------
oMPR n_plugs=1, data_rate=2, bcast_channel=63
oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
channel=63, data_rate=0, overhead_id=0, payload=376
iMPR n_plugs=0, data_rate=2

Node 1 GUID 0x002d8f3600001fd0
------------------------------

Wed Oct 1 19:41:01 EDT 2008
libiec61883 error: error reading oMPR
libiec61883 error: error reading iMPR
Host Adapter 0
==============

Node 0 GUID 0x002d8f3600001fd0
------------------------------

Node 1 GUID 0x001aadfffe47916e
------------------------------
oMPR n_plugs=1, data_rate=2, bcast_channel=63
oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
channel=63, data_rate=0, overhead_id=0, payload=376
iMPR n_plugs=0, data_rate=2

Wed Oct 1 20:41:01 EDT 2008
libiec61883 error: error reading oMPR
libiec61883 error: error reading iMPR
Host Adapter 0
==============

Node 0 GUID 0x001aadfffe47916e
------------------------------
oMPR n_plugs=1, data_rate=2, bcast_channel=63
oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
channel=62, data_rate=0, overhead_id=0, payload=376
iMPR n_plugs=0, data_rate=2

Node 1 GUID 0x002d8f3600001fd0
------------------------------

}}}

The box appears as node 0 at 18:41 and 20:41, but at 19:41 it was on node
1. (That was the only time I captured it on node one since I set up the
script.)

It seems like whenever a node flip happens, the mythtv backend loses all
ability to control the box until the backend process is restarted and then
everything works fine after that for a few hours to a few days.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:12>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Oct 10, 2008, 8:49 AM

Post #14 of 54 (3057 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by Marc MERLIN):

Are you all using the firewire chipset from your MB, maybe a VIA one?
If so, that was the cause of my problems. I got a non VIA FW PCI card and
things worked a lot better after that.

Also, another reason for my problems was that my cable connection to the
DCH-3200 wasn't that good and sometimes I was getting errors that were
simply because it couldn't tune the channel. Once I changed the FW card
and recrimped my cable to the STB, it's been working near perfectly since
then (broadcast mode of course), all this with myth 0.21 with the
mythprime script as shipped on ubuntu hardy (version .55b beta)

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:13>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Oct 10, 2008, 9:05 AM

Post #15 of 54 (3060 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner: danielk
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

I am using a PCI based firewire card (though this has happened with too
different firewire boards). And as indicated in the description, this is
not a tuning issue. The channel will always change on the cable box.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:14>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Dec 23, 2008, 11:38 AM

Post #16 of 54 (2655 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------
Changes (by danielk):

* owner: danielk =>
* status: assigned => new


Comment:

I don't have a firewire STB anymore, unassigning ticket.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:15>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jan 27, 2009, 5:53 AM

Post #17 of 54 (2552 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by scottgprice [at] comcast):

I also am having this problem with my DCH-3200. The most frustrating
thing about this bug is that it makes my DCH unusable, because Myth as a
whole doesn't detect a problem. Once it goes into the mode described
above I get no shows recorded but Myth thinks everything is fine and
doesn't mark this tuner as "Unavailable". Because of this I end up with 8
to 10 empty files of our favorite shows instead of just 1 missed show and
nothing to give me a clue. I have even tried using a script to restart
Myth Backend but this only works about 50% of the time. The rest of the
time I have to completely reboot the machine or get behind the furniture
and unplug the firewire cable. At least marking the tuner "Unavailable"
when the data stops would be a big help. I have had this problem with 2
different firewire cards using different chip sets.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:16>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jan 27, 2009, 9:12 AM

Post #18 of 54 (2539 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

I very hacked work around which has worked consistently for me was to
write a logsurfer script which basically monitors the backend for the
culprit error messages (there are two variations of this failure) and
reset the backend so at least recordings will try to resume. It doesn't
fix the problem, but it does help to catch recordings that would otherwise
be blank.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:17>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jan 27, 2009, 9:27 AM

Post #19 of 54 (2553 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by foom [at] fuhm):

Replying to [comment:17 anonymous]:
> I very hacked work around which has worked consistently for me was to
write a logsurfer script which basically monitors the backend for the
culprit error messages (there are two variations of this failure) and
reset the backend so at least recordings will try to resume. It doesn't
fix the problem, but it does help to catch recordings that would otherwise
be blank.


Me too. I use this script to run mythbackend for the last 4 months.

{{{
#!/bin/sh
sleep 3
echo -n "******* Restarting mythbackend at: " >>
/home/mythtv/logs/mythbackend.log
date >> /home/mythtv/logs/mythbackend.log

# restart mythbackend if it gets certain errors. and exit if a new
mythbackend is started.
tail -f -c0 /home/mythtv/logs/mythbackend.log| \
awk '/Error: Unable to get handle for port: -1/ {system("killall
mythbackend"); exit} '\
'/^\*\*\*\*\*\*\* Restarting mythbackend at:/ {exit}' &

/usr/bin/mythbackend --pidfile /var/run/mythtv/mythbackend.pid >>
/home/mythtv/logs/mythbackend.log
}}}

I also have a line:
{{{
m2:2:respawn:/usr/local/sbin/start-mythbackend
}}}
in /etc/inittab to monitor mythbackend and restart it if anything happens
(either it crashes by itself or I explicitly kill it, above)

It's been working reliably with that.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:18>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jan 27, 2009, 11:20 AM

Post #20 of 54 (2549 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by scottgprice [at] comcast):

Thanks, both of you, I will try it.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:19>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Feb 12, 2009, 6:57 AM

Post #21 of 54 (2498 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by Derek Atkins <warlord [at] MIT>):

I've been noticing this on my backend for the last few days. I have two
DCH3200 boxes and a PCI Firewire card with a TI Chipset (so it's not the
VIA problem). I dont want to just restart the backend because box #2
might still be recording something when box #1 "dies". I wonder if
something is losing a file descriptor somewhere or not properly closing a
connection?

It's too bad that Danielk isn't working on this anymore. Are there any
other Devs that are using Firewire? Or has everyone moved over to HD-
PVR?

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:20>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Feb 12, 2009, 9:35 AM

Post #22 of 54 (2488 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by eric [at] lisaneric):

The restart script wouldn't work for me, since I don't seem to get
anything in the log file when the problem happens.

What I've noticed is that the backend will always lose the ability to
control the box if it tries to tune to a channel that is (I believe) 5C
encrypted.

On the other hand, majoridiot's scanfw utility
(https://wiki.ubuntu.com/majoridiot) can scan the encrypted channels
without losing control of the box, so it still seems like a problem in the
backend, not something fundamentally wrong with the STB or firewire
connection.

I don't know who's working on firewire capture and who has moved on to the
HD-PVR. When it works, firewire capture should be the preferred solution,
since it avoids a digtial-analog-digital conversion step.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:21>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Feb 12, 2009, 9:43 AM

Post #23 of 54 (2482 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by foom [at] fuhm):

Replying to [comment:21 eric [at] lisaneric]:
> The restart script wouldn't work for me, since I don't seem to get
anything in the log file when the problem happens.
>
> What I've noticed is that the backend will always lose the ability to
control the box if it tries to tune to a channel that is (I believe) 5C
encrypted.

Seems likely you're running into a different bug, then.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:22>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Feb 12, 2009, 10:00 AM

Post #24 of 54 (2485 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

Replying to [comment:22 foom [at] fuhm]:
> Replying to [comment:21 eric [at] lisaneric]:
> > The restart script wouldn't work for me, since I don't seem to get
anything in the log file when the problem happens.
>
> Seems likely you're running into a different bug, then.

No I think the logging verbosity level has just been turned down in the
version I'm using.

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:23>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits


mythtv at cvs

Jun 24, 2009, 5:20 AM

Post #25 of 54 (2115 views)
Permalink
Re: Ticket #5278: Firewire Uses Bad Port Number and Fails [In reply to]
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi [at] gmail | Owner:
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.21
Severity: medium | Resolution:
Mlocked: 0 |
---------------------------------+------------------------------------------

Comment(by anonymous):

Same problem here with 2 DCT6200's. Happens every few days; usually while
I'm at work and my wife wants to watch some LiveTV.

From uname:
{{{
Linux tivvy 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64
GNU/Linux
}}}
From lspci:
{{{
05:03.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)
}}}
From plugreport:
{{{
Host Adapter 0
==============

Node 0 GUID 0x002210fffe6c0313
------------------------------
oMPR n_plugs=1, data_rate=2, bcast_channel=63
oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
channel=63, data_rate=2, overhead_id=0, payload=376
iMPR n_plugs=0, data_rate=2

Node 1 GUID 0x002374fffe3ccd32
------------------------------
oMPR n_plugs=1, data_rate=2, bcast_channel=63
oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
channel=62, data_rate=2, overhead_id=0, payload=376
iMPR n_plugs=0, data_rate=2

Node 2 GUID 0x001e8c00017d9557
------------------------------
libiec61883 error: error reading oMPR
libiec61883 error: error reading iMPR
}}}

from mythbackend.log:
{{{
2009-06-22 14:15:23.689 LFireDev(002374FFFE3CCD32), Warning: No Input in
850 msec...
2009-06-22 14:15:23.745 LFireDev(002374FFFE3CCD32), Warning: No Input in
900 msec...
2009-06-22 14:15:23.796 LFireDev(002374FFFE3CCD32), Warning: No Input in
950 msec...
2009-06-22 14:15:23.848 LFireDev(002374FFFE3CCD32), Warning: No Input in
1000 msec...
2009-06-22 14:15:23.900 LFireDev(002374FFFE3CCD32), Warning: No Input in
1050 msec...
2009-06-22 14:15:23.900 LFireDev(002374FFFE3CCD32): ResetBus() -- begin
2009-06-22 14:15:23.903 LFireDev(002374FFFE3CCD32): ResetBus() -- end
2009-06-22 14:15:23.903 LFireDev(002210FFFE6C0313): SignalReset(208->209)
2009-06-22 14:15:23.909 LFireDev(002210FFFE6C0313): SignalReset(208->209):
Updating device list -- begin
2009-06-22 14:15:23.918 LFireDev(002210FFFE6C0313): SignalReset(208->209):
Updating device list -- end
2009-06-22 14:15:23.925 LFireDev(002374FFFE3CCD32): SignalReset(208->209)
2009-06-22 14:15:23.933 LFireDev(002374FFFE3CCD32): SignalReset(208->209):
Updating device list -- begin
2009-06-22 14:15:23.941 LFireDev(002374FFFE3CCD32): SignalReset(208->209):
Updating device list -- end
2009-06-22 14:15:23.999 LFireDev(002374FFFE3CCD32), Warning: No Input in
50 msec...
2009-06-22 14:15:24.051 LFireDev(002374FFFE3CCD32), Warning: No Input in
100 msec...
2009-06-22 14:15:24.328 LFireDev(002374FFFE3CCD32), Warning: No Input in
150 msec...
2009-06-22 14:15:24.380 LFireDev(002374FFFE3CCD32), Warning: No Input in
200 msec...
2009-06-22 14:15:24.432 LFireDev(002374FFFE3CCD32), Warning: No Input in
250 msec...
2009-06-22 14:15:24.484 LFireDev(002374FFFE3CCD32), Warning: No Input in
300 msec...
2009-06-22 14:15:24.536 LFireDev(002374FFFE3CCD32), Warning: No Input in
350 msec...
2009-06-22 14:15:24.588 LFireDev(002374FFFE3CCD32), Warning: No Input in
400 msec...
2009-06-22 14:15:24.640 LFireDev(002374FFFE3CCD32), Warning: No Input in
450 msec...
2009-06-22 14:15:24.692 LFireDev(002374FFFE3CCD32), Warning: No Input in
500 msec...
2009-06-22 14:15:24.744 LFireDev(002374FFFE3CCD32), Warning: No Input in
550 msec...
2009-06-22 14:15:24.796 LFireDev(002374FFFE3CCD32), Warning: No Input in
600 msec...
2009-06-22 14:15:24.849 LFireDev(002374FFFE3CCD32), Warning: No Input in
650 msec...
2009-06-22 14:15:24.900 LFireDev(002374FFFE3CCD32), Warning: No Input in
700 msec...
2009-06-22 14:15:24.952 LFireDev(002374FFFE3CCD32), Warning: No Input in
750 msec...
2009-06-22 14:15:25.004 LFireDev(002374FFFE3CCD32), Warning: No Input in
800 msec...
2009-06-22 14:15:25.055 LFireDev(002374FFFE3CCD32), Warning: No Input in
850 msec...
2009-06-22 14:15:25.109 LFireDev(002374FFFE3CCD32), Warning: No Input in
900 msec...
2009-06-22 14:15:25.160 LFireDev(002374FFFE3CCD32), Warning: No Input in
950 msec...
2009-06-22 14:15:25.211 LFireDev(002374FFFE3CCD32), Warning: No Input in
1000 msec...
2009-06-22 14:15:25.263 LFireDev(002374FFFE3CCD32), Warning: No Input in
1050 msec...
2009-06-22 14:15:25.264 LFireDev(002374FFFE3CCD32): ResetBus() -- begin
2009-06-22 14:15:25.267 LFireDev(002374FFFE3CCD32): ResetBus() -- end
2009-06-22 14:15:25.267 LFireDev(002210FFFE6C0313): SignalReset(209->210)
2009-06-22 14:15:25.273 LFireDev(002210FFFE6C0313): SignalReset(209->210):
Updating device list -- begin
2009-06-22 14:15:25.588 LFireDev(002210FFFE6C0313): SignalReset(209->210):
Updating device list -- end
2009-06-22 14:15:25.588 LFireDev(002374FFFE3CCD32): SignalReset(209->210)
2009-06-22 14:15:25.593 LFireDev(002374FFFE3CCD32): SignalReset(209->210):
Updating device list -- begin
2009-06-22 14:15:25.896 LFireDev(002374FFFE3CCD32): SignalReset(209->210):
Updating device list -- end
2009-06-22 14:15:25.947 LFireDev(002374FFFE3CCD32), Warning: No Input in
50 msec...
2009-06-22 14:15:26.000 LFireDev(002374FFFE3CCD32), Warning: No Input in
100 msec...
libiec61883 warning: iec61883_cmp_create_bcast_output: Failed to set the
oPCR[0] plug for node 63.
2009-06-22 14:15:26.001 LFireDev(002374FFFE3CCD32), Error: Bus Reset :
Failed to reconnect
2009-06-22 14:15:26.052 LFireDev(002374FFFE3CCD32), Warning: No Input in
150 msec...
2009-06-22 14:15:26.103 LFireDev(002374FFFE3CCD32), Warning: No Input in
200 msec...
2009-06-22 14:15:26.155 LFireDev(002374FFFE3CCD32), Warning: No Input in
250 msec...
2009-06-22 14:15:26.209 LFireDev(002374FFFE3CCD32), Warning: No Input in
300 msec...
2009-06-22 14:15:26.260 LFireDev(002374FFFE3CCD32), Warning: No Input in
350 msec...
2009-06-22 14:15:26.312 LFireDev(002374FFFE3CCD32), Warning: No Input in
400 msec...
2009-06-22 14:15:26.364 LFireDev(002374FFFE3CCD32), Warning: No Input in
450 msec...
2009-06-22 14:15:26.416 LFireDev(002374FFFE3CCD32), Warning: No Input in
500 msec...
2009-06-22 14:15:26.468 LFireDev(002374FFFE3CCD32), Warning: No Input in
550 msec...
2009-06-22 14:15:26.521 LFireDev(002374FFFE3CCD32), Warning: No Input in
600 msec...
2009-06-22 14:15:26.572 LFireDev(002374FFFE3CCD32), Warning: No Input in
650 msec...
2009-06-22 14:15:26.624 LFireDev(002374FFFE3CCD32), Warning: No Input in
700 msec...
2009-06-22 14:15:26.675 LFireDev(002374FFFE3CCD32), Warning: No Input in
750 msec...
2009-06-22 14:15:26.727 LFireDev(002374FFFE3CCD32), Warning: No Input in
800 msec...
2009-06-22 14:15:26.780 LFireDev(002374FFFE3CCD32), Warning: No Input in
850 msec...
2009-06-22 14:15:26.832 LFireDev(002374FFFE3CCD32), Warning: No Input in
900 msec...
2009-06-22 14:15:26.884 LFireDev(002374FFFE3CCD32), Warning: No Input in
950 msec...
2009-06-22 14:15:26.936 LFireDev(002374FFFE3CCD32), Warning: No Input in
1000 msec...
2009-06-22 14:15:26.988 LFireDev(002374FFFE3CCD32), Warning: No Input in
1050 msec...
2009-06-22 14:15:26.988 LFireDev(002374FFFE3CCD32): ResetBus() -- begin
2009-06-22 14:15:26.991 LFireDev(002374FFFE3CCD32): ResetBus() -- end
2009-06-22 14:15:26.991 LFireDev(002210FFFE6C0313): SignalReset(210->211)
2009-06-22 14:15:27.001 LFireDev(002210FFFE6C0313): SignalReset(210->211):
Updating device list -- begin
2009-06-22 14:15:27.011 LFireDev(002210FFFE6C0313): SignalReset(210->211):
Updating device list -- end
2009-06-22 14:15:27.017 LFireDev(002374FFFE3CCD32): SignalReset(210->211)
2009-06-22 14:15:27.025 LFireDev(002374FFFE3CCD32): SignalReset(210->211):
Updating device list -- begin
2009-06-22 14:15:27.035 LFireDev(002374FFFE3CCD32): SignalReset(210->211):
Updating device list -- end
2009-06-22 14:15:27.092 LFireDev(002374FFFE3CCD32), Warning: No Input in
50 msec...
2009-06-22 14:15:27.144 LFireDev(002374FFFE3CCD32), Warning: No Input in
100 msec...
2009-06-22 14:15:27.195 LFireDev(002374FFFE3CCD32), Warning: No Input in
150 msec...
2009-06-22 14:15:27.248 LFireDev(002374FFFE3CCD32), Warning: No Input in
200 msec...
2009-06-22 14:15:27.299 LFireDev(002374FFFE3CCD32), Warning: No Input in
250 msec...
2009-06-22 14:15:27.352 LFireDev(002374FFFE3CCD32), Warning: No Input in
300 msec...
2009-06-22 14:15:27.404 LFireDev(002374FFFE3CCD32), Warning: No Input in
350 msec...
2009-06-22 14:15:27.456 LFireDev(002374FFFE3CCD32), Warning: No Input in
400 msec...
2009-06-22 14:15:27.508 LFireDev(002374FFFE3CCD32), Warning: No Input in
450 msec...
2009-06-22 14:15:27.560 LFireDev(002374FFFE3CCD32), Warning: No Input in
500 msec...
2009-06-22 14:15:27.613 LFireDev(002374FFFE3CCD32), Warning: No Input in
550 msec...
2009-06-22 14:15:27.665 LFireDev(002374FFFE3CCD32), Warning: No Input in
600 msec...
2009-06-22 14:15:27.716 LFireDev(002374FFFE3CCD32), Warning: No Input in
650 msec...
2009-06-22 14:15:27.767 LFireDev(002374FFFE3CCD32), Warning: No Input in
700 msec...
2009-06-22 14:15:27.819 LFireDev(002374FFFE3CCD32), Warning: No Input in
750 msec...
2009-06-22 14:15:27.871 LFireDev(002374FFFE3CCD32), Warning: No Input in
800 msec...
2009-06-22 14:15:27.923 LFireDev(002374FFFE3CCD32), Warning: No Input in
850 msec...
2009-06-22 14:15:27.976 LFireDev(002374FFFE3CCD32), Warning: No Input in
900 msec...
2009-06-22 14:15:28.029 LFireDev(002374FFFE3CCD32), Warning: No Input in
950 msec...
2009-06-22 14:15:28.080 LFireDev(002374FFFE3CCD32), Warning: No Input in
1000 msec...
2009-06-22 14:15:28.132 LFireDev(002374FFFE3CCD32), Warning: No Input in
1050 msec...
2009-06-22 14:15:28.132 LFireDev(002374FFFE3CCD32): ResetBus() -- begin
2009-06-22 14:15:28.135 LFireDev(002374FFFE3CCD32): ResetBus() -- end
2009-06-22 14:15:28.135 LFireDev(002210FFFE6C0313): SignalReset(211->212)
2009-06-22 14:15:28.140 LFireDev(002210FFFE6C0313): SignalReset(211->212):
Updating device list -- begin
2009-06-22 14:15:28.456 LFireDev(002210FFFE6C0313): SignalReset(211->212):
Updating device list -- end
2009-06-22 14:15:28.456 LFireDev(002374FFFE3CCD32): SignalReset(211->212)
2009-06-22 14:15:28.461 LFireDev(002374FFFE3CCD32): SignalReset(211->212):
Updating device list -- begin
2009-06-22 14:15:28.764 LFireDev(002374FFFE3CCD32): SignalReset(211->212):
Updating device list -- end
2009-06-22 14:15:28.816 LFireDev(002374FFFE3CCD32), Warning: No Input in
50 msec...
2009-06-22 14:15:28.869 LFireDev(002374FFFE3CCD32), Warning: No Input in
100 msec...
libiec61883 warning: iec61883_cmp_create_bcast_output: Failed to set the
oPCR[0] plug for node 63.
2009-06-22 14:15:28.870 LFireDev(002374FFFE3CCD32), Error: Bus Reset :
Failed to reconnect
2009-06-22 14:15:28.920 LFireDev(002374FFFE3CCD32), Warning: No Input in
150 msec...
2009-06-22 14:15:28.972 LFireDev(002374FFFE3CCD32), Warning: No Input in
200 msec...
2009-06-22 14:15:29.023 LFireDev(002374FFFE3CCD32), Warning: No Input in
250 msec...
2009-06-22 14:15:29.076 LFireDev(002374FFFE3CCD32), Warning: No Input in
300 msec...
2009-06-22 14:15:29.127 LFireDev(002374FFFE3CCD32), Warning: No Input in
350 msec...
2009-06-22 14:15:29.179 LFireDev(002374FFFE3CCD32), Warning: No Input in
400 msec...
2009-06-22 14:15:29.231 LFireDev(002374FFFE3CCD32), Warning: No Input in
450 msec...
2009-06-22 14:15:29.284 LFireDev(002374FFFE3CCD32), Warning: No Input in
500 msec...
2009-06-22 14:15:29.336 LFireDev(002374FFFE3CCD32), Warning: No Input in
550 msec...
2009-06-22 14:15:29.389 LFireDev(002374FFFE3CCD32), Warning: No Input in
600 msec...
2009-06-22 14:15:29.439 LFireDev(002374FFFE3CCD32), Warning: No Input in
650 msec...
2009-06-22 14:15:29.492 LFireDev(002374FFFE3CCD32), Warning: No Input in
700 msec...
2009-06-22 14:15:29.544 LFireDev(002374FFFE3CCD32), Warning: No Input in
750 msec...
2009-06-22 14:15:29.596 LFireDev(002374FFFE3CCD32), Warning: No Input in
800 msec...
2009-06-22 14:15:29.648 LFireDev(002374FFFE3CCD32), Warning: No Input in
850 msec...
2009-06-22 14:15:29.700 LFireDev(002374FFFE3CCD32), Warning: No Input in
900 msec...
2009-06-22 14:15:29.752 LFireDev(002374FFFE3CCD32), Warning: No Input in
950 msec...
2009-06-22 14:15:29.803 LFireDev(002374FFFE3CCD32), Warning: No Input in
1000 msec...
2009-06-22 14:15:29.855 LFireDev(002374FFFE3CCD32), Warning: No Input in
1050 msec...
2009-06-22 14:15:29.856 LFireDev(002374FFFE3CCD32): ResetBus() -- begin
2009-06-22 14:15:29.859 LFireDev(002374FFFE3CCD32): ResetBus() -- end
2009-06-22 14:15:29.859 LFireDev(002210FFFE6C0313): SignalReset(212->213)
2009-06-22 14:15:29.865 LFireDev(002210FFFE6C0313): SignalReset(212->213):
Updating device list -- begin
2009-06-22 14:15:29.969 LFireDev(002210FFFE6C0313): SignalReset(212->213):
Updating device list -- end
2009-06-22 14:15:29.970 LFireDev(002374FFFE3CCD32): SignalReset(212->213)
2009-06-22 14:15:29.973 LFireDev(002374FFFE3CCD32): SignalReset(212->213):
Updating device list -- begin
2009-06-22 14:15:29.984 LFireDev(002374FFFE3CCD32): SignalReset(212->213):
Updating device list -- end
2009-06-22 14:15:30.039 LFireDev(002374FFFE3CCD32), Warning: No Input in
50 msec...
2009-06-22 14:15:30.092 LFireDev(002374FFFE3CCD32), Warning: No Input in
100 msec...
2009-06-22 14:15:30.144 LFireDev(002374FFFE3CCD32), Warning: No Input in
150 msec...
2009-06-22 14:15:30.196 LFireDev(002374FFFE3CCD32), Warning: No Input in
200 msec...
2009-06-22 14:15:30.249 LFireDev(002374FFFE3CCD32), Warning: No Input in
250 msec...
2009-06-22 14:15:30.299 LFireDev(002374FFFE3CCD32), Warning: No Input in
300 msec...
2009-06-22 14:15:30.351 LFireDev(002374FFFE3CCD32), Warning: No Input in
350 msec...
2009-06-22 14:15:30.403 LFireDev(002374FFFE3CCD32), Warning: No Input in
400 msec...
2009-06-22 14:15:30.456 LFireDev(002374FFFE3CCD32), Warning: No Input in
450 msec...
2009-06-22 14:15:30.508 LFireDev(002374FFFE3CCD32), Warning: No Input in
500 msec...
2009-06-22 14:15:30.561 LFireDev(002374FFFE3CCD32), Warning: No Input in
550 msec...
2009-06-22 14:15:30.612 LFireDev(002374FFFE3CCD32), Warning: No Input in
600 msec...
2009-06-22 14:15:30.663 LFireDev(002374FFFE3CCD32), Warning: No Input in
650 msec...
2009-06-22 14:15:30.715 LFireDev(002374FFFE3CCD32), Warning: No Input in
700 msec...
2009-06-22 14:15:30.767 LFireDev(002374FFFE3CCD32), Warning: No Input in
750 msec...
2009-06-22 14:15:30.819 LFireDev(002374FFFE3CCD32), Warning: No Input in
800 msec...
2009-06-22 14:15:30.871 LFireDev(002374FFFE3CCD32), Warning: No Input in
850 msec...
2009-06-22 14:15:30.923 LFireDev(002374FFFE3CCD32), Warning: No Input in
900 msec...
2009-06-22 14:15:30.975 LFireDev(002374FFFE3CCD32), Warning: No Input in
950 msec...
2009-06-22 14:15:31.028 LFireDev(002374FFFE3CCD32), Warning: No Input in
1000 msec...
2009-06-22 14:15:31.080 LFireDev(002374FFFE3CCD32), Warning: No Input in
1050 msec...
2009-06-22 14:15:31.080 LFireDev(002374FFFE3CCD32): ResetBus() -- begin
2009-06-22 14:15:31.082 LFireDev(002210FFFE6C0313): SignalReset(213->214)
2009-06-22 14:15:31.083 LFireDev(002374FFFE3CCD32): ResetBus() -- end
2009-06-22 14:15:31.084 LFireDev(002210FFFE6C0313): SignalReset(213->214):
Updating device list -- begin
2009-06-22 14:15:31.404 LFireDev(002210FFFE6C0313): SignalReset(213->214):
Updating device list -- end
2009-06-22 14:15:31.404 LFireDev(002374FFFE3CCD32): SignalReset(213->214)
2009-06-22 14:15:31.409 LFireDev(002374FFFE3CCD32): SignalReset(213->214):
Updating device list -- begin
2009-06-22 14:15:31.716 LFireDev(002374FFFE3CCD32): SignalReset(213->214):
Updating device list -- end
2009-06-22 14:15:31.769 LFireDev(002374FFFE3CCD32), Warning: No Input in
50 msec...
2009-06-22 14:15:31.821 LFireDev(002374FFFE3CCD32), Warning: No Input in
100 msec...
libiec61883 warning: iec61883_cmp_create_bcast_output: Failed to set the
oPCR[0] plug for node 63.
2009-06-22 14:15:31.822 LFireDev(002374FFFE3CCD32), Error: Bus Reset :
Failed to reconnect
2009-06-22 14:15:31.872 LFireDev(002374FFFE3CCD32), Warning: No Input in
150 msec...
2009-06-22 14:15:31.924 LFireDev(002374FFFE3CCD32), Warning: No Input in
200 msec...
2009-06-22 14:15:31.975 LFireDev(002374FFFE3CCD32), Warning: No Input in
250 msec...
2009-06-22 14:15:32.028 LFireDev(002374FFFE3CCD32), Warning: No Input in
300 msec...
2009-06-22 14:15:32.076 TVRec(1): Changing from WatchingLiveTV to None
2009-06-22 14:15:32.081 LFireDev(002374FFFE3CCD32), Warning: No Input in
350 msec...
2009-06-22 14:15:32.135 LFireDev(002374FFFE3CCD32), Warning: No Input in
400 msec...
2009-06-22 14:15:33.046 MainServer::HandleAnnounce Playback
2009-06-22 14:15:33.050 adding: tivvy3 as a client (events: 0)
2009-06-22 14:15:33.052 TVRec(1): Changing from None to WatchingLiveTV
2009-06-22 14:15:33.059 TVRec(1): HW Tuner: 1->1
2009-06-22 14:15:33.060 LAVCInfo(), Error: Unable to get handle for port:
-1
eno: Invalid argument (22)
2009-06-22 14:15:33.080 TVRec(1) Error: Failed to set channel to 13.
Reverting to kState_None
2009-06-22 14:15:33.080 TVRec(1): Changing from WatchingLiveTV to None
2009-06-22 14:15:33.832 MainServer::HandleAnnounce Playback
2009-06-22 14:15:33.838 adding: tivvy3 as a client (events: 0)
2009-06-22 14:15:33.839 TVRec(1): Changing from None to WatchingLiveTV
2009-06-22 14:15:33.842 TVRec(1): HW Tuner: 1->1
2009-06-22 14:15:33.845 LAVCInfo(), Error: Unable to get handle for port:
-1
eno: Invalid argument (22)
2009-06-22 14:15:33.850 TVRec(1) Error: Failed to set channel to 13.
Reverting to kState_None
2009-06-22 14:15:33.854 TVRec(1): Changing from WatchingLiveTV to None

}}}

--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:24>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits

First page Previous page 1 2 3 Next page Last page  View All MythTV commits 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.