From: Andy Walls <awalls@radix.net>
To: Brandon Jenkins <bcjenkins@tvwhere.com>, hverkuil@xs4all.nl
Cc: video4linux-list@redhat.com, ivtv-devel@ivtvdriver.org
Subject: Re: CX18 Oops
Date: Fri, 08 Aug 2008 10:18:28 -0400 [thread overview]
Message-ID: <1218205108.3003.44.camel@morgan.walls.org> (raw)
In-Reply-To: <de8cad4d0808070636q4045b788s6773a4e168cca2cc@mail.gmail.com>
On Thu, 2008-08-07 at 09:36 -0400, Brandon Jenkins wrote:
> On Wed, Aug 6, 2008 at 8:55 PM, Andy Walls <awalls@radix.net> wrote:
> > from the offending build to me. That way I can see the assembled
> > machine code and verify where in the function the NULL dereference is
> > happening.
> >
> > If you have the exact same problem as me, I can give you a "band-aid"
> > patch which will lessen the problem in short order. It'll be a band aid
> > because it won't fix the accounting problem though. I need to do more
> > extensive test and debug to find out where the accounting of buffers is
> > getting screwed up.
> >
> > Regards,
> > Andy
Brandon,
I have checked in a fix to defend against the Ooops we both encountered.
The fix will also generate a WARN dump and some queue stats when it runs
across the cause, but will otherwise try to clean up as best it can to
allow further operation.
The band-aid fix is the latest change at
http://linuxtv.org/hg/~awalls/v4l-dvb
Please provide the extra debug that happens if you encounter the warning
in your logs. I have only encountered the problem twice over a several
month period, so its hard to get insight into the root cause buffer
accounting error at that rate.
Hans,
The provided patch is a bit ugly, so I'm not sure I want it to go to the
main repo as is. Since the cx18_queue_move() and cx18_queue_move_buf()
functions are a bit general for how cx18 is using them (compared to
ivtv) and a bit confusing at first, I was going to rewrite them down to
the minimum needed for cx18. Do you have any objection?
I normally like the fact that cx18 mirrors ivtv in many aspects as it
provides an certain economy for common bug fixes. Here I think cx18 is
carrying complexity and unused code (and maybe bugs) for only that
reason.
Regards,
Andy
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-08-08 14:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 1:04 CX18 Oops Brandon Jenkins
2008-08-06 1:29 ` Andy Walls
2008-08-06 10:57 ` Brandon Jenkins
2008-08-07 0:55 ` Andy Walls
2008-08-07 10:16 ` Brandon Jenkins
2008-08-07 13:36 ` Brandon Jenkins
2008-08-08 0:46 ` Andy Walls
2008-08-08 14:18 ` Andy Walls [this message]
2008-08-08 14:35 ` Hans Verkuil
2008-08-08 14:44 ` Andy Walls
2008-08-09 17:43 ` Brandon Jenkins
2008-08-11 21:33 ` Brandon Jenkins
2008-08-17 2:13 ` Andy Walls
2008-08-17 9:41 ` Hans Verkuil
2008-08-17 19:12 ` Andy Walls
2008-08-17 20:01 ` Hans Verkuil
2008-08-18 2:53 ` Andy Walls
2008-08-18 10:35 ` Brandon Jenkins
2008-08-18 17:17 ` Brandon Jenkins
2008-08-19 0:34 ` Andy Walls
2008-08-23 21:44 ` Andy Walls
2008-08-25 19:14 ` Brandon Jenkins
2008-08-18 23:52 ` Andy Walls
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1218205108.3003.44.camel@morgan.walls.org \
--to=awalls@radix.net \
--cc=bcjenkins@tvwhere.com \
--cc=hverkuil@xs4all.nl \
--cc=ivtv-devel@ivtvdriver.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.