[mythtv-users] Strange backend activity

jose rubio debian at nc.rr.com
Sat Feb 28 18:53:33 EST 2004


On Sat, 2004-02-28 at 04:33, Adam Biskobing wrote:
> Chaintech Motherboard
> Athlon XP 2000 Processor
> 256MB Memory
> 80GB & 120GB IDE Discs
> PVR-250
> Gentoo Linux
> Running CVS as of last week
> 
> The problem started with version .13, continued into .14 and also into
> the CVS.  As I came down this morning, I notice that it had done it
> again, The only entries in the backend log were: 
> 
> 2004-02-28 08:45:02 Started recording "The Sting" on channel: 1526 on
> cardid: 1,
>  sourceid 1
> 2004-02-28 08:45:02 External channel change:
> /usr/share/mythtv/channel/rca.pl 52
> 6 &
> 2004-02-28 08:45:02 Changing from None to RecordingOnly
> 2004-02-28 08:45:02 Using profile 'Default' to record
> Starting up as the master server.
> 2004-02-28 09:17:24 Probed: /dev/video0 - Composite 0
> 2004-02-28 09:17:24 Probed: /dev/video0 - Composite 1
> 2004-02-28 09:17:24 Probed: /dev/video0 - Composite 2
> 2004-02-28 09:17:24 Probed: /dev/video0 - Composite 3
> 
> Any help would be greatly appreciated.  I'm out of ideas, and this is
> really cutting into the usability of myth.
> 
OK, just a shot in the dark here.  I'm assuming you are running ivtv
0.1.9...  But I don't think it's an ivtv problem if it is the backend
running up the cpu.

Looking at your log, I'm curious why you get the msg "Starting up as the
master server" in the middle of the log when it should be at the
begining.  Unless you restarted the server between 8:45 and 9:17. (did
you?)

If not I do not see why myth would be probing for input in the middle of
recording.

I did a grep -r "Probed" * in the myth source tree to see where that msg
was coming from (I have never gotten that in my logs).  It seems to be
only when using v4l2.  Do you have your kernel patched with v4l2 or did
you just use the header in the ivtv/utils directory?

This could be the diff, I am _not_ using v4l2, just the header...

Anyway, if you did not restart the backend at about 9:00 then try
compiling a new kernel without v4l2... I told you it was a shot in the
dark...


Well I hope I was of some help.



-jose-




More information about the mythtv-users mailing list