From: Russell King <rmk@arm.linux.org.uk>
To: Ed L Cashin <ecashin@uga.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] do_wp_page: BUG on invalid pfn
Date: Fri, 15 Aug 2003 23:11:41 +0100 [thread overview]
Message-ID: <20030815231141.F21529@flint.arm.linux.org.uk> (raw)
In-Reply-To: <87smo27fqq.fsf@uga.edu>; from ecashin@uga.edu on Fri, Aug 15, 2003 at 05:50:05PM -0400
On Fri, Aug 15, 2003 at 05:50:05PM -0400, Ed L Cashin wrote:
> On i386 WARN_ON calls dump_stack, but BUG just prints some minimal
> helpful info on the console, like this:
>
> ------------[ cut here ]------------
> kernel BUG at kernel/any.c:36!
> invalid operand: 0000 [#1]
BUG causes an exception, which calls die(), which in turn calls
handle_BUG(), and this indeed does print the first two lines of the
above. die() goes on to print the 3rd line, but it also goes on
to call show_registers() which should print the registers and
calltrace as well.
Maybe you've found a bug in show_registers() ?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2003-08-15 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030815184720.A4D482CE79@lists.samba.org>
2003-08-15 21:15 ` [PATCH] do_wp_page: BUG on invalid pfn Ed L Cashin
2003-08-15 21:22 ` Mike Fedyk
2003-08-15 21:52 ` Ed L Cashin
2003-08-15 22:05 ` Mike Fedyk
2003-08-15 22:18 ` Ed L Cashin
2003-08-15 21:39 ` Russell King
2003-08-15 21:50 ` Ed L Cashin
2003-08-15 22:11 ` Russell King [this message]
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=20030815231141.F21529@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ecashin@uga.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.