[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091012110954.67d7d8d8.akpm@linux-foundation.org>
Date: Mon, 12 Oct 2009 11:09:54 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Simon Kagstrom <simon.kagstrom@...insight.net>,
Ingo Molnar <mingo@...e.hu>,
Artem Bityutskiy <dedekind1@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
"Koskinen Aaro (Nokia-D/Helsinki)" <aaro.koskinen@...ia.com>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] panic.c: export panic_on_oops
On Mon, 12 Oct 2009 08:36:38 -0700 (PDT) Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> I agree with the "save kernel buffer on panic" thing, but I disagree with
> making it anything new, and hooking into "printk()" or the console
> subsystem AT ALL. That's just bogus, stupid, and WRONG.
>
> What you can do is to just flush the 'log_buf' buffer (or as much of it as
> you want - the buffer may be a megabyte in size, and maybe you only want
> to flush the last 8kB or something like that) on oops. And _not_ mix this
> up with anything else.
What he said. I did it that way in the Digeo kernel back in 2002.
Worked good.
Doing it via a console is rather weird. It will need core kernel
changes to do it properly.
Perhaps oops_enter() is a good place to mark the start of the log, and
flush it within oops_exit().
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists