mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabian Frederick <fabf@skynet.be>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, rdunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 1/1] kernel: panic: display reason at end + pr_emerg
Date: Wed, 12 Feb 2014 16:26:53 +0800	[thread overview]
Message-ID: <20140212162653.19dcded1d0249ce48c997db9@skynet.be> (raw)
In-Reply-To: <20140211153445.c03bf3b266880ff0a174cee6@linux-foundation.org>

On Tue, 11 Feb 2014 15:34:45 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Sat, 8 Feb 2014 15:45:22 +0800 Fabian Frederick <fabf@skynet.be> wrote:
> 
> > Currently, booting without initrd specified on 80x25 screen
> > gives a call trace followed by atkbd : Spurious ACK.
> > Original message ("VFS: Unable to mount root fs") is not available.
> > Of course this could happen in other situations...
> > 
> > -This patch displays panic reason after call trace which could help
> > lot of people even if it's not the very last line on screen.
> 
> Fair enough.  Hate it when that happens!
I was sure I was not the only one :)

> 
> > -Converting all panic.c printk(KERN_EMERG to pr_emerg(
> 
> You missed a couple.
Thanks a lot for addition and patch fix.
What a pleasure to see such professionalism !

> 
> --- a/kernel/panic.c~kernel-panicc-display-reason-at-end-pr_emerg-fix
> +++ a/kernel/panic.c
> @@ -275,8 +275,7 @@ unsigned long get_taint(void)
>  void add_taint(unsigned flag, enum lockdep_ok lockdep_ok)
>  {
>  	if (lockdep_ok == LOCKDEP_NOW_UNRELIABLE && __debug_locks_off())
> -		printk(KERN_WARNING
> -		       "Disabling lock debugging due to kernel taint\n");
> +		pr_warn("Disabling lock debugging due to kernel taint\n");
>  
>  	set_bit(flag, &tainted_mask);
>  }
> @@ -381,8 +380,7 @@ late_initcall(init_oops_id);
>  void print_oops_end_marker(void)
>  {
>  	init_oops_id();
> -	printk(KERN_WARNING "---[ end trace %016llx ]---\n",
> -		(unsigned long long)oops_id);
> +	pr_warn("---[ end trace %016llx ]---\n", (unsigned long long)oops_id);
>  }
>  
>  /*
> _
> 

      reply	other threads:[~2014-02-12 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08  7:45 Fabian Frederick
2014-02-11 23:34 ` Andrew Morton
2014-02-12  8:26   ` Fabian Frederick [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=20140212162653.19dcded1d0249ce48c997db9@skynet.be \
    --to=fabf@skynet.be \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®