[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180118135704.62d0f79f@gandalf.local.home>
Date: Thu, 18 Jan 2018 13:57:04 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Dave Young <dyoung@...hat.com>, pmladek@...e.com,
sergey.senozhatsky@...il.com, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, kexec@...ts.infradead.org
Subject: Re: [PATCH] print kdump kernel loaded status in stack dump
On Thu, 18 Jan 2018 10:02:17 -0800
Andi Kleen <ak@...ux.intel.com> wrote:
> Dave Young <dyoung@...hat.com> writes:
> > printk("%sHardware name: %s\n",
> > log_lvl, dump_stack_arch_desc_str);
> > + if (kexec_crash_loaded())
> > + printk("%skdump kernel loaded\n", log_lvl);
>
> Oops/warnings are getting longer and longer, often scrolling away
> from the screen, and if the kernel crashes backscroll does not work
> anymore, so precious information is lost.
>
> Can you merge it with some other line?
>
> Just a [KDUMP] or so somewhere should be good enough.
Or perhaps we should add it as a TAINT. Not all taints are bad.
-- Steve
Powered by blists - more mailing lists