mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: hermann pitton <hermann-pitton@arcor.de>,
	brandon@ifup.org, jasny@vidsoft.de, video4linux-list@redhat.com,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: 2.6.25 regression: vivi - scheduling while atomic
Date: Tue, 22 Apr 2008 11:35:39 -0300	[thread overview]
Message-ID: <20080422113539.0b3002f9@gaivota> (raw)
In-Reply-To: <20080422062938.0e491c0c.akpm@linux-foundation.org>

> > > > This happenes on a vanilla 2.6.25 with loaded nvidia graphics module.
> > > > System architecture is x86_64. If it matters I'll try to reproduce this
> > > > error on a non tainted kernel.
> > > 
> > > No need to reproduce on a non-tainted Kernel.  This is a known issue
> > > with patches merged into the v4l-dvb tree several weeks ago but it seems
> > > to not have made it into 2.6.25 :(
> > > 
> > >  http://linuxtv.org/hg/v4l-dvb/rev/06eb92ed0b18
> > >  http://linuxtv.org/hg/v4l-dvb/rev/c50180f4ddfc
> > > 
> > > I can rebase the patches for 2.6.25 but they are too big to go into the
> > > stable 2.6.25 tree...

Unfortunately, the tests for the patches fixing several videobuf issues
finished later on -rc9, when Linus were releasing 2.6.25. 

I should send the videobuf patches to Linus tree, together with other patches,
probably today. After that, I think we should backport the fixes for 2.6.25,
and test it again, with vanilla 2.6.25.

The issue here is that videobuf suffered several changes on this development
cycle. Probably, only a few of those patches are needed to fix the issue. So,
we need to handle this with care, to avoid the risk of damaging other drivers that
relies on videobuf.

Cheers,
Mauro

  reply	other threads:[~2008-04-22 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  8:16 Gregor Jasny
2008-04-21 22:37 ` Brandon Philips
2008-04-22  0:08   ` hermann pitton
2008-04-22 13:29     ` Andrew Morton
2008-04-22 14:35       ` Mauro Carvalho Chehab [this message]
2008-04-22 19:17       ` hermann pitton

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=20080422113539.0b3002f9@gaivota \
    --to=mchehab@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=brandon@ifup.org \
    --cc=hermann-pitton@arcor.de \
    --cc=jasny@vidsoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.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

all inboxes | Powered by JetHome®