[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130301162029.GB16393@logfs.org>
Date: Fri, 1 Mar 2013 11:20:29 -0500
From: Jörn Engel <joern@...fs.org>
To: Jeff Moyer <jmoyer@...hat.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 5/9] blockconsole: use CON_ALLDATA
On Fri, 1 March 2013 11:11:58 -0500, Jeff Moyer wrote:
> Joern Engel <joern@...fs.org> writes:
>
> > Blockconsole should really see every message ever printed. The
> > alternative is to try debugging with information like this:
> > [166135.633974] Stack:
> > [166135.634016] Call Trace:
> > [166135.634029] <IRQ>
> > [166135.634156] <EOI>
> > [166135.634177] Code: 00 00 55 48 89 e5 0f 1f 44 00 00 ff 15 31 49 80 00 c9 c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 0f 1f 44 00 00
> > [166135.634384] 48 8b 14 25 98 24 01 00 48 8d 14 92 48 8d 04 bd 00 00 00 00
>
> What was your log level set to at the time? By default, all of the
> information for a kernel panic should show up on the console, no?
I believe it was the distro default, which should be 4. We used to
play silly games with setting the loglevel to "just send everything".
But that applies equally to all consoles, so you could no longer type
on the console and retain your sanity at the same time.
If you and/or other people are strongly opposed to the CON_ALLDATA
patches, I can either keep them private (we will never drop them from
our kernel) or add a config option.
Jörn
--
Doubt is not a pleasant condition, but certainty is an absurd one.
-- Voltaire
--
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