From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Rashmica Gupta <rashmicy@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: Append linux_banner to exception information in xmon.
Date: Thu, 03 Dec 2015 09:43:33 +1100 [thread overview]
Message-ID: <87bna8ii96.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1448419585-5181-1-git-send-email-rashmicy@gmail.com>
Rashmica Gupta <rashmicy@gmail.com> writes:
> Currently if you are in xmon without an oops etc. to view the kernel
> version you have to type "d $linux_banner" - not necessarily obvious. As
> this is useful information, append to the output of "e" command.
>
> Example output:
> $mon> e
> cpu 0x1: Vector: 0 at [c0000000f879ba80]
> pc: c000000000081718: sysrq_handle_xmon+0x68/0x80
> lr: c000000000081718: sysrq_handle_xmon+0x68/0x80
> sp: c0000000f879bbe0
> msr: 8000000000009033
> current = 0xc0000000f604d5c0
> paca = 0xc00000000fdc0480 softe: 0 irq_happened: 0x01
> pid = 2467, comm = bash
> Linux version 4.4.0-rc2-00008-gc51af91c3ab3-dirty (rashmica@circle) (gcc
> version 5.1.1 20150629 (GCC) ) #45 SMP Wed Nov 25 10:25:12 AEDT 2015
>
> Signed-off-by: Rashmica Gupta <rashmicy@gmail.com>
+10,245,789
Acked-by: Stewart Smith <stewart@linux.vnet.ibm.com>
If I had a dollar for every time this would have helped *this morning*,
I'd at least be buying you enough coffee for it to be problematic.
I'd be keen in it heading to stable@ fixing the actual problem of
"people can't actually include the damn kernel version in their bug
report" - but maybe somebody else can work out if this is something
that's likely to be accepted.
next prev parent reply other threads:[~2015-12-02 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 2:46 [PATCH v2] powerpc: Append linux_banner to exception information in xmon Rashmica Gupta
2015-11-25 8:15 ` Denis Kirjanov
2015-11-25 11:15 ` Michael Ellerman
2015-12-02 22:43 ` Stewart Smith [this message]
2015-12-15 11:27 ` [v2] " Michael Ellerman
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=87bna8ii96.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rashmicy@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).