From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: Kernel panic during SysRq-b on Alpha
Date: Thu, 22 Sep 2005 10:12:59 +0400 [thread overview]
Message-ID: <20050922101259.A29179@jurassic.park.msu.ru> (raw)
In-Reply-To: <43315BEB.3010909@ens-lyon.org>; from Brice.Goglin@ens-lyon.org on Wed, Sep 21, 2005 at 03:11:07PM +0200
On Wed, Sep 21, 2005 at 03:11:07PM +0200, Brice Goglin wrote:
> Kernel bug at kernel/printk.c:683
> swapper(0): Kernel Bug 1
> pc = [<fffffc000032706c>] ra = [<fffffc00004352d4>] ps = 0007 Not
> tainted
> pc is at acquire_console_sem+0x2c/0x90
Indeed, acquire_console_sem() does BUG() in interrupt context now,
as in the case of SysRq-b.
Ivan.
--- linux/arch/alpha/kernel/process.c.orig Mon Aug 29 03:41:01 2005
+++ linux/arch/alpha/kernel/process.c Thu Sep 22 09:51:26 2005
@@ -127,6 +127,10 @@ common_shutdown_1(void *generic_ptr)
/* If booted from SRM, reset some of the original environment. */
if (alpha_using_srm) {
#ifdef CONFIG_DUMMY_CONSOLE
+ /* If we've gotten here after SysRq-b, leave interrupt
+ context before taking over the console. */
+ if (in_interrupt())
+ irq_exit();
/* This has the effect of resetting the VGA video origin. */
take_over_console(&dummy_con, 0, MAX_NR_CONSOLES-1, 1);
#endif
next prev parent reply other threads:[~2005-09-22 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 13:11 Brice Goglin
2005-09-22 6:12 ` Ivan Kokshaysky [this message]
2005-09-22 6:42 ` Andrew Morton
2005-09-22 9:04 ` Ivan Kokshaysky
2005-09-22 9:21 ` Andrew Morton
2005-09-22 10:34 ` Ivan Kokshaysky
2005-09-22 10:13 ` Brice Goglin
2005-09-22 10:42 ` Ivan Kokshaysky
2005-09-23 22:03 ` Ivan Kokshaysky
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=20050922101259.A29179@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=Brice.Goglin@ens-lyon.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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®