From: Eric Thomas <ethomas@claranet.fr>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: video4linux <video4linux-list@redhat.com>,
g.liakhovetski@pengutronix.de, Brandon Philips <bphilips@suse.de>
Subject: Re: kernel oops since changeset e3b8fb8cc214
Date: Sun, 09 Mar 2008 09:55:26 +0100 [thread overview]
Message-ID: <47D3A5FE.9000803@claranet.fr> (raw)
In-Reply-To: <20080308075929.3ccbd012@gaivota>
Mauro Carvalho Chehab wrote:
> On Sat, 08 Mar 2008 08:45:08 +0100
> Eric Thomas <ethomas@claranet.fr> wrote:
>
>> Eric Thomas wrote:
>>> Hi all,
>>>
>>> My box runs with kernel 2.6.24 + main v4l-dvb tree from HG.
>>> The card is a Haupauge HVR-3000 running in analog mode only. No *dvd*
>>> module loaded.
>>> Since this videobuf-dma-sg patch, I face kernel oops in several
>>> situations.
>>> These problems occur with real tv applications, but traces below come
>>> from the capture_example binary from v4l2-apps/test.
>
> Although I don't believe that this is related to the conversion to generic DMA
> API.
Indeed, or I wouldn't be the only one (?) to complain.
> Anyway, I'm enclosing a patch reverting the changeset. It is valuable if people
> can test to revert this and see if the issue remains.
It does, unsurprisingly to me.
Thanks for the patch.
> I suspect, however, that the bug is on some other place, and it is related to
> some bad locking. It seems that STREAMOFF processing here interrupted by a
> video buffer arrival, at IRQ code.
>
> PS.: I'm c/c Brandon, since he is working on fixing a bad lock on videobuf_dma.
I guess that the best thing I can do for now is waiting.
If Brandon or someone else wants me to test anything, feel free to
contact me.
Regards,
Eric
--
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-03-09 8:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 12:26 kernel oops since changeset e3b8fb8cc214 Eric Thomas
2008-03-08 7:45 ` Eric Thomas
2008-03-08 9:37 ` Guennadi Liakhovetski
2008-03-09 8:41 ` Eric Thomas
2008-03-09 11:32 ` Guennadi Liakhovetski
2008-03-11 22:04 ` Guennadi Liakhovetski
2008-03-12 0:23 ` hermann pitton
2008-03-12 7:34 ` Guennadi Liakhovetski
2008-03-12 22:28 ` hermann pitton
2008-03-13 16:07 ` Guennadi Liakhovetski
2008-03-08 10:59 ` Mauro Carvalho Chehab
2008-03-09 8:55 ` Eric Thomas [this message]
2008-03-11 9:45 ` Craig Whitmore
2008-03-11 17:39 ` Matthias Schwarzott
2008-03-12 0:26 ` hermann pitton
2008-03-13 15:55 ` Matthias Schwarzott
2008-03-13 17:59 ` Mauro Carvalho Chehab
2008-03-13 22:48 ` hermann pitton
2008-03-13 22:56 ` hermann pitton
2008-03-14 14:15 ` Mauro Carvalho Chehab
2008-03-14 14:33 ` Guennadi Liakhovetski
2008-03-14 16:16 ` Craig Whitmore
2008-03-15 7:22 ` Eric Thomas
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=47D3A5FE.9000803@claranet.fr \
--to=ethomas@claranet.fr \
--cc=bphilips@suse.de \
--cc=g.liakhovetski@pengutronix.de \
--cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox