linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/3] powerpc/watchdog: Print the NIP in soft_nmi_interrupt()
Date: Thu, 12 Oct 2017 18:18:56 +1000	[thread overview]
Message-ID: <20171012181856.3d88a5d9@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1507783474-28210-3-git-send-email-mpe@ellerman.id.au>

On Thu, 12 Oct 2017 15:44:34 +1100
Michael Ellerman <mpe@ellerman.id.au> wrote:

> When a CPU detects its locked up via soft_nmi_interrupt() we have
> pt_regs, so print the regs->nip, which points to where we took the
> soft-NMI.
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
>  arch/powerpc/kernel/watchdog.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
> index 2494cbe34132..4594ba0979e4 100644
> --- a/arch/powerpc/kernel/watchdog.c
> +++ b/arch/powerpc/kernel/watchdog.c
> @@ -235,7 +235,7 @@ void soft_nmi_interrupt(struct pt_regs *regs)
>  		}
>  		set_cpu_stuck(cpu, tb);
>  
> -		pr_emerg("CPU %d self-detected hard LOCKUP\n", cpu);
> +		pr_emerg("CPU %d self-detected hard LOCKUP @ %pS\n", cpu, (void *)regs->nip);
>  		print_modules();
>  		print_irqtrace_events(current);
>  		show_regs(regs);

These patches all look fine to me, but we should be printing nip
with show_regs, so why here too?

Thanks,
Nick

  reply	other threads:[~2017-10-12  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  4:44 [PATCH 1/3] powerpc/watchdog: Tweak watchdog printks Michael Ellerman
2017-10-12  4:44 ` [PATCH 2/3] powerpc/watchdog: regs can't be null in soft_nmi_interrupt() Michael Ellerman
2017-10-12  4:44 ` [PATCH 3/3] powerpc/watchdog: Print the NIP " Michael Ellerman
2017-10-12  8:18   ` Nicholas Piggin [this message]
2017-10-12 12:01     ` Michael Ellerman
2018-01-29  4:13 ` [1/3] powerpc/watchdog: Tweak watchdog printks 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=20171012181856.3d88a5d9@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).