From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: "vgoyal@in.ibm.com" <vgoyal@in.ibm.com>
Cc: Haren Myneni <hbabu@us.ibm.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH/RFC: [kdump] fix APIC shutdown sequence
Date: Wed, 08 Aug 2007 20:07:13 +0200 [thread overview]
Message-ID: <46BA0651.5010708@fujitsu-siemens.com> (raw)
In-Reply-To: <20070808113834.GA26145@in.ibm.com>
Vivek Goyal wrote:
> Got this oops while testing your patch when I did
> "echo c > /proc/sysrq-trigger"
That's bad :-(
...
> Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
[<0000000000000000>]
> <IRQ> [<ffffffff8025afd0>] handle_edge_irq+0x5c/0x127
> [<ffffffff8020e1ae>] do_IRQ+0xf1/0x15f
> [<ffffffff8020c191>] ret_from_intr+0x0/0xa
> <EOI> <NMI> [<ffffffff80351ae3>] __delay+0x6/0x10
> [<ffffffff8021e328>] crash_nmi_callback+0x4b/0x77
Obviously, it the oops occurs after the IRQs are re-enabled in crash_nmi_callback().
It appears that desc->chip->mask (in mask_ack_irq(), kernel/irq/chip.c:462) was NULL.
I have no idea how my patch could cause that.
This proves that re-enabling IRQs in this situation is too dangerous :-(.
I really did hundreds of dumps in different ways (echo c>/proc/sysrq-trigger,
forcing Oops and panic(), actually hititng Alt-Sysrq) and this never happened to
me.
Martin
--
Martin Wilck
PRIMERGY System Software Engineer
FSC IP ESP DE6
Fujitsu Siemens Computers GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn
Germany
Tel: ++49 5251 8 15113
Fax: ++49 5251 8 20409
Email: mailto:martin.wilck@fujitsu-siemens.com
Internet: http://www.fujitsu-siemens.com
Company Details: http://www.fujitsu-siemens.com/imprint.html
next prev parent reply other threads:[~2007-08-08 18:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 15:08 Martin Wilck
2007-08-07 14:29 ` Vivek Goyal
2007-08-07 17:41 ` Martin Wilck
2007-08-08 1:04 ` Eric W. Biederman
2007-08-08 9:03 ` Martin Wilck
2007-08-08 9:33 ` Vivek Goyal
2007-08-08 12:04 ` Martin Wilck
2007-08-08 15:21 ` Eric W. Biederman
2007-08-08 17:35 ` Martin Wilck
2007-08-08 17:56 ` Eric W. Biederman
2007-08-08 18:22 ` Martin Wilck
2007-08-08 18:38 ` Martin Wilck
2007-08-08 10:36 ` Vivek Goyal
2007-08-08 14:06 ` Chip Coldwell
2007-08-08 14:42 ` Vivek Goyal
2007-08-08 18:15 ` Martin Wilck
2007-08-09 10:11 ` Vivek Goyal
2007-08-09 17:35 ` Martin Wilck
2007-08-07 19:44 ` Chip Coldwell
2007-08-08 0:29 ` Andrew Morton
2007-08-08 8:32 ` Martin Wilck
2007-08-08 11:38 ` Vivek Goyal
2007-08-08 18:07 ` Martin Wilck [this message]
2007-08-08 21:25 ` Eric W. Biederman
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=46BA0651.5010708@fujitsu-siemens.com \
--to=martin.wilck@fujitsu-siemens.com \
--cc=hbabu@us.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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
Powered by JetHome