The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Douglas Schilling Landgraf <dougsland@gmail.com>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Morton <akpm@google.com>,
	Bongani Hlope <bonganilinux@mweb.co.za>
Subject: Re: 2.6.25-rc regression: bttv: oops on radio access (bisected)
Date: Tue, 1 Apr 2008 17:10:51 -0300	[thread overview]
Message-ID: <20080401171051.724a9f75@gaivota> (raw)
In-Reply-To: <20080330162006.GA6048@joi>

Hi Marcin

On Sun, 30 Mar 2008 18:20:49 +0200
Marcin Slusarz <marcin.slusarz@gmail.com> wrote:

> Hi
> 2.6.25-rc7 kernel oopses on exec of "radio -c /dev/radio0".
> I bisected it down to:
> 
> 402aa76aa5e57801b4db5ccf8c7beea9f580bb1b is first bad commit
> commit 402aa76aa5e57801b4db5ccf8c7beea9f580bb1b
> Author: Douglas Schilling Landgraf <dougsland@gmail.com>
> Date:   Thu Dec 27 22:20:58 2007 -0300
> 
>     V4L/DVB (6911): Converted bttv to use video_ioctl2
> 
>     Signed-off-by: Douglas Schilling Landgraf <dougsland@gmail.com>
>     Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
> 

There are three patches that are meant to fix the bugs with radio. On the tests
I did here, they worked, but the Bongani still points that the fixes didn't
solve for him.

On the tests I did here, the three patches seemed to work [1]. Maybe you could
test with those patches and post us some results.

There are three patches meant to fix several issues caused by the conversion: 

http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=bdd38d9b5c6365ea004df6d8a183dd1344b4801f
http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=055a6282cabd311cf010a5a83f0494558504f7d0
http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=6e07ff78274752fe812a1e8bddb6013a278e62e8

Could you test please and give us some feedback?

[1] Yet, I've discovered recently that the hardware I use for testing PCI
devices is broken. Probably, my motherboard chipset is damaged, since I'm
getting intermittent bugs on several parts of the machine - even with stable
kernels - so my tests with bttv aren't conclusive.

Cheers,
Mauro

  parent reply	other threads:[~2008-04-01 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30 16:20 2.6.25-rc regression: bttv: oops on radio access (bisected) Marcin Slusarz
2008-03-30 20:22 ` Bongani Hlope
2008-03-30 20:33   ` Marcin Slusarz
2008-04-01 20:10 ` Mauro Carvalho Chehab [this message]
2008-04-01 20:52   ` Marcin Slusarz
2008-04-01 20:58     ` Bongani Hlope
2008-04-02 17:14   ` Bongani Hlope
2008-04-02 19:34     ` Mauro Carvalho Chehab

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=20080401171051.724a9f75@gaivota \
    --to=mchehab@infradead.org \
    --cc=akpm@google.com \
    --cc=bonganilinux@mweb.co.za \
    --cc=dougsland@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=rjw@sisk.pl \
    --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