From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
linux-mm@kvack.org, kernel@avr32linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.30] Bad page map in process
Date: Mon, 13 Jul 2009 12:56:17 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0907131236320.20647@sister.anvils> (raw)
In-Reply-To: <Pine.LNX.4.64.0907122151010.13280@axis700.grange>
On Sun, 12 Jul 2009, Guennadi Liakhovetski wrote:
>
> 2. the specific BUG that I posted originally wasn't very interesting,
> because it wasn't the first one. Having read a few posts I wasn't quite
> sure how really severe this BUG was, i.e., whether or not it requiret a
> reboot. There used to be a message like "reboot is required" around this
> sort of exceptions, but then it has been removed, so, I thought, it wasn't
> required any more. But the fact is, that once one such BUG has occurred,
> new ones will come from various applications and eventually the system
> will become unusable.
I replaced Bad page state's reboot is needed message by just the BUG
prefix: partly because the bad page handling _is_ now more resilient;
but more because I don't like wasting screenlines which could hold
vital info, and because I didn't see how this BUG differs from others
in whether or not you need a reboot.
A BUG means the kernel is in unknown territory: if you're brave and
want to gather more info, you try to keep on running after a BUG;
if you're cautious, you reboot as soon as possible.
(Hmm, but perhaps I should wire these in to panic_on_oops??)
You did the right thing: kept on running, then decided it wasn't
worth it. (But you've only sent the one pair of messages gathered:
okay, let's forget the rest until you've sorted the hardware angle.)
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-07-13 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:07 Guennadi Liakhovetski
2009-07-08 11:23 ` Hans-Christian Egtvedt
2009-07-08 12:28 ` Guennadi Liakhovetski
2009-07-10 18:34 ` Hugh Dickins
2009-07-12 7:57 ` Haavard Skinnemoen
2009-07-12 19:59 ` Guennadi Liakhovetski
[not found] ` <1DC0FF5051B91B4D88A15F21F1A27F417ABDE6@dware1013.doorway.loc>
2009-07-13 11:14 ` SV: " Guennadi Liakhovetski
2009-07-13 11:56 ` Hugh Dickins [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=Pine.LNX.4.64.0907131236320.20647@sister.anvils \
--to=hugh.dickins@tiscali.co.uk \
--cc=g.liakhovetski@gmx.de \
--cc=haavard.skinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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