From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Fabio Erculiani <lxnay@sabayon.org>
Cc: linux-fbdev@vger.kernel.org, lethal@linux-sh.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbmem: fix race condition between register_framebuffer() and fb_open()
Date: Wed, 25 May 2011 20:46:48 +0200 [thread overview]
Message-ID: <20110525204648.58983270@neptune.home> (raw)
In-Reply-To: <BANLkTimxi-LZFzwv=z6RRBCX098hr-ViUg@mail.gmail.com>
On Wed, 25 May 2011 Fabio Erculiani <lxnay@sabayon.org> wrote:
> I'm not a fbdev expert. So I leave the real fix to real men ( ;-) ).
> It is causing deadlock during boot, so I would consider it quite critical.
> Users using any fb driver will get into troubles.
> The workaround is to boot with vga=normal.
What is your system doing during boot? I've never seen it here but maybe
my boot sequence is too simple.
Could you tell if it deadlocks before init gets started or afterwards,
which fb drivers (and extra kernel patches if any) are in use.
If you have the complete backtrace of the deadlocked processes it would
help getting a better idea of what is affected and how (and why just the
framebuffer's lock is not causing trouble with earlier kernel versions).
Bruno
> Cheers,
next prev parent reply other threads:[~2011-05-25 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 19:54 Fabio Erculiani
2011-05-24 20:45 ` Bruno Prémont
2011-05-25 16:19 ` Bruno Prémont
2011-05-25 18:17 ` Fabio Erculiani
2011-05-25 18:41 ` Anca Emanuel
2011-05-25 18:48 ` Fabio Erculiani
2011-05-25 18:51 ` Bruno Prémont
2011-05-25 18:53 ` Fabio Erculiani
2011-05-25 18:46 ` Bruno Prémont [this message]
2011-05-25 18:52 ` Fabio Erculiani
2011-05-25 18:57 ` Bruno Prémont
2011-05-25 19:04 ` Fabio Erculiani
2011-05-25 19:12 ` Bruno Prémont
2011-05-25 19:16 ` Fabio Erculiani
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=20110525204648.58983270@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxnay@sabayon.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
all inboxes | Powered by JetHome®