All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Tesarik <ptesarik@suse.cz>
To: kexec@lists.infradead.org
Subject: Re: [PATCH] print kdump kernel loaded status in stack dump
Date: Fri, 19 Jan 2018 17:51:53 +0100	[thread overview]
Message-ID: <20180119175153.6c5aa1d2@ezekiel.suse.cz> (raw)
In-Reply-To: <20180119161604.GH7844@tassilo.jf.intel.com>

On Fri, 19 Jan 2018 08:16:04 -0800
Andi Kleen <ak@linux.intel.com> wrote:

> On Fri, Jan 19, 2018 at 02:45:38PM +0900, Sergey Senozhatsky wrote:
> > On (01/18/18 10:02), Andi Kleen wrote:  
> > > Dave Young <dyoung@redhat.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.  
> > 
> > true. I even ended up having a console_reflush_on_panic() function. it
> > simply re-prints with a delay [so I can at least read the oops] logbuf
> > entries every once in a while, staring with the first oops_in_progress
> > record.  
> 
> It would be better to make scrollback work even after panic (e.g. with a polled
> keyboard driver)

I ended up using a serial console on all my machines. Yes, even my
laptop has one (virtual, provided by Intel AMT).

Anyway, what do you mean by a polled keyboard driver? My keyboard is
connected with USB. A polling xhci driver? Surely possible, but is it
worth the effort?

Petr T

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2018-01-19 16:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17  4:50 [PATCH] print kdump kernel loaded status in stack dump Dave Young
2018-01-17  4:50 ` Dave Young
2018-01-17  8:57 ` Petr Mladek
2018-01-17  8:57   ` Petr Mladek
2018-01-17 12:32   ` Dave Young
2018-01-17 12:32     ` Dave Young
2018-01-17 13:42     ` Petr Mladek
2018-01-17 13:42       ` Petr Mladek
2018-01-17 15:48       ` Steven Rostedt
2018-01-17 15:48         ` Steven Rostedt
2018-01-18  1:57       ` Dave Young
2018-01-18  1:57         ` Dave Young
2018-01-18 18:02 ` Andi Kleen
2018-01-18 18:02   ` Andi Kleen
2018-01-18 18:57   ` Steven Rostedt
2018-01-18 18:57     ` Steven Rostedt
2018-01-19  4:47     ` Dave Young
2018-01-19  4:47       ` Dave Young
2018-01-19 13:06       ` Petr Tesarik
2018-01-26  7:37       ` Dave Young
2018-01-26  7:37         ` Dave Young
2018-01-26 12:17         ` Petr Mladek
2018-01-26 12:17           ` Petr Mladek
2018-01-27  3:57           ` Dave Young
2018-01-27  3:57             ` Dave Young
2018-01-19  5:45   ` Sergey Senozhatsky
2018-01-19  5:45     ` Sergey Senozhatsky
2018-01-19  8:16     ` Dave Young
2018-01-19  8:16       ` Dave Young
2018-01-19  8:28       ` Sergey Senozhatsky
2018-01-19  8:28         ` Sergey Senozhatsky
2018-01-19  8:42         ` Dave Young
2018-01-19  8:42           ` Dave Young
2018-01-19  9:46           ` Sergey Senozhatsky
2018-01-19  9:46             ` Sergey Senozhatsky
2018-01-19  8:32       ` Sergey Senozhatsky
2018-01-19  8:32         ` Sergey Senozhatsky
2018-01-19 16:16     ` Andi Kleen
2018-01-19 16:16       ` Andi Kleen
2018-01-19 16:51       ` Petr Tesarik [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=20180119175153.6c5aa1d2@ezekiel.suse.cz \
    --to=ptesarik@suse.cz \
    --cc=kexec@lists.infradead.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.