From: Ingo Molnar <mingo@elte.hu>
To: Amit Shah <amit.shah@codito.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RT-V0.7.22 Bug with fbdev and e100
Date: Tue, 9 Nov 2004 13:13:30 +0100 [thread overview]
Message-ID: <20041109121330.GA23533@elte.hu> (raw)
In-Reply-To: <200411091623.51495.amit.shah@codito.com>
* Amit Shah <amit.shah@codito.com> wrote:
> drivers/video/console/fbcon.c:fbcon_cursor needs additional locking?
this issue is a bit different. The problem is that the irq warning
message (which is harmless) is printed from an atomic context. In the
next release i'll try something different: simply dont print to the
fbcon if the kernel is in an atomic context. This will reduce the
utility of fbcon when debugging kernel crashes, but it should avoid this
assert (and potential problems resulting out of it). Other types of
consoles (serial, text, netconsole) will still try to output everything,
independently of atomicity. (of these, only netconsole wants to
reschedule.)
Ingo
next prev parent reply other threads:[~2004-11-09 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 10:53 Amit Shah
2004-11-09 12:13 ` Ingo Molnar [this message]
2004-11-09 12:22 ` Ingo Molnar
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=20041109121330.GA23533@elte.hu \
--to=mingo@elte.hu \
--cc=amit.shah@codito.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®