Rich,
Thanks for the report, I've been able to reproduce this and I'm now
investigating.
Regards,
Hans
On Friday 16 February 2007 02:11, Rich Kadel wrote:
> OK... Some more data for you, based on your questions:
>
> 1. It is sliced. I am reading it from /dev/vbi[x].
>
> 2. I tried some tests. If I just cat /dev/video >/dev/null, no
> messages appear. In fact, I ran "cat /dev/video[x] >/dev/null"
> simultaneously with 5 tuners and saw no messages.
>
> But, then I added "cat /dev/vbi0 >/dev/null" and the following
> messages showed up:
>
> Feb 15 17:03:10 server2 kernel: ivtv0 warning: Starting VBI after
> starting an en
> coding, seems to not work.
> Feb 15 17:03:10 server2 kernel: ivtv0 warning: encoder VBI: Couldn't
> find start
> of buffer within the first 256 bytes
> Feb 15 17:03:18 server2 last message repeated 18 times
>
> I stopped all but one tuner (/dev/video0), and started "cat
> /dev/vbi0" again, and got the same message.
>
> Feb 15 17:03:35 server2 kernel: ivtv0 warning: Starting VBI after
> starting an en
> coding, seems to not work.
> Feb 15 17:03:36 server2 kernel: ivtv0 warning: encoder VBI: Couldn't
> find start
> of buffer within the first 256 bytes
>
> Then I tried starting "cat /dev/vbi0" first, followed by "cat
> /dev/video0", and I got only the message:
>
> Feb 15 17:03:36 server2 kernel: ivtv0 warning: encoder VBI: Couldn't
> find start
> of buffer within the first 256 bytes
>
> (Ignore the timestamps)
>
> So, the bottom line is, these messages appear when I read /dev/vbi
> and /dev/video at the same time.
>
> Very reproducible, and fairly constant as I said.
>
> Thanks,
> Rich
>
> --
>
> Rich Kadel
> Appeligo, Inc.
> (858) 433-1747
> www.appeligo.com
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Hans Verkuil
> Sent: Thursday, February 15, 2007 3:42 PM
> To: Discussion list for development of the IVTV driver
> Subject: Re: [ivtv-devel] System (practically) non-responsive after
> several hours...no clues
>
> On Thursday 15 February 2007 17:42, Rich Kadel wrote:
> > So far so good with 0.10.0rc1. At least, it hasn't crashed in a
> > couple of days of continuous reading, 3 video streams, and 8 VBI.
> >
> > Now I have a new problem I'd like to resolve. My logs are getting
> > filled up with the following message:
> >
> > Feb 12 16:00:00 server2 kernel: ivtv2 warning: encoder VBI:
> > Couldn't find start
> > of buffer within the first 256 bytes
> >
> > Occasionally, I'll notice some dropped characters in the VBI. Not
> > often. But it could be a symptom.
> >
> > I'd like to fix the VBI problem if there's a way to do that. If
> > not, is there a way to reduce the log messages?
>
> How are you capturing VBI? Is it sliced VBI or raw VBI? And if it is
> sliced VBI, is it embedded in the MPEG stream or captured as a
> separate stream?
>
> Do you always have these messages, or do they appear suddenly? It is
> reproducable with a simple 'cat /dev/video0 >x.mpg' command?
>
> BTW, there is no need to increase the mpeg buffers, it's not related
> to that. Basically this message indicates that something weird is
> going on with the VBI transfers. It can occur once in a while, but it
> shouldn't happen continuously.
>
> Regards,
>
> Hans
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
