public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <righi.andrea@gmail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [BISECTED] x11 fbdev on intelfb hangs hard after 66c1ca019078220dc1bf968f2bb18421100ef147
Date: Fri, 10 Apr 2009 10:14:29 +0200	[thread overview]
Message-ID: <20090410081428.GA5595@linux> (raw)
In-Reply-To: <1239314524.7390.14.camel@mj>

On Thu, Apr 09, 2009 at 06:02:04PM -0400, Pavel Roskin wrote:
> Hello!
> 
> I'm running the latest wireless-testing.git kernel, which is 2.6.30-rc1
> plus some wireless bits.  I use intelfb with kernel mode switching and
> X11 using fbdev.  This runs on Fedora 10, fbdev driver is
> xorg-x11-drv-fbdev-0.3.1-7.fc9.x86_64.
> 
> This worked fine with Linux 2.6.29, but after upgrading to 2.6.30-rc1
> X11 hangs hard.
> 
> Bisecting found commit 66c1ca019078220dc1bf968f2bb18421100ef147 to be
> responsible.  It can be reverted on top of 2.6.30-rc1, and the resulting
> kernel is working fine.  The commit is called:
> 
> fbmem: fix fb_info->lock and mm->mmap_sem circular locking dependency
> 
> I'm especially concerned to see stable@kernel.org in the cc in the log.
> This patch fails on two systems for me, so it's hardly ready for stable
> kernels.
> 
> The kernel config (very minimal, I used it to speed up bisecting),
> xorg.conf and lspci output are attached.

Thanks for reporting Pavel. I agree to revert 66c1ca ASAP.

See also http://lkml.org/lkml/2009/4/9/177.

-Andrea

  reply	other threads:[~2009-04-10  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 22:02 [BISECTED] x11 fbdev on intelfb hangs hard after 66c1ca019078220dc1bf968f2bb18421100ef147 Pavel Roskin
2009-04-10  8:14 ` Andrea Righi [this message]
2009-04-21 18:34   ` [stable] " Chris Wright
2009-04-21 20:59     ` Andrea Righi
2009-04-21 21:10       ` Chris Wright

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=20090410081428.GA5595@linux \
    --to=righi.andrea@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=stable@kernel.org \
    /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