On Sunday 18 February 2007 09:00, Rich Kadel wrote:
> I have to agree. This could end up being a real a problem...for me
> or anyone else. The syslog will group some log messages if they are
> similar enough, but since I had the messages coming on the 8 tuners,
> it was rare to get consecutive messages for the same tuner, and
> hence, no grouping of messages.
>
> It would be good to limit the amount of logging in case the driver
> gets into this kind of state.
I thought it strange that it kept reporting these errors continuously,
since I was pretty sure I had implemented a mechanism where the message
is only shown once until the application is reading again. Turns out to
be a bug in the condition. It's fixed in the ivtv trunk code, this
message now no longer repeats unnecessarily.
I've also improved the v4l2-ctl --log-status output a bit: it shows how
many bytes have been read from /dev/videoX. You can use this
information, together with the buffer full information in the same log
to see what is happening when you get these errors.
An alternative method is to turn on debugging: ivtvctl -D19 is a good
setting: it shows you each read() call, both the start and return. You
can use it to check if a read() is blocking somehow (in which case the
problem is probably a driver bug after all) or if the application isn't
reading. You will get a huge log, though. So that's for debugging only.
Regards,
Hans
>
> Rich
>
> --
>
> Rich Kadel
> Appeligo, Inc.
> (858) 433-1747
> www.appeligo.com
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Matthias
> Urlichs Sent: Saturday, February 17, 2007 12:56 AM
> To: Discussion list for development of the IVTV driver
> Subject: Re: [ivtv-devel] System (practically) non-responsive after
> several hours...no clues
>
> Hi,
>
> Rich Kadel:
> > I got about 200,000 lines of these messages between 09:00:48
> > (local) and 09:07:38
>
> That's a bit excessive (to put it mildly). Can we please rate-limit
> them?
>
> Is there a way for the application to find out that it's been too
> slow?
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
