From: David Miller <davem@davemloft.net>
To: vijay.ac.kumar@oracle.com
Cc: sparclinux@vger.kernel.org, karl.volz@oracle.com,
rob.gardner@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] sparc64: Jump to boot prom from console on panic
Date: Wed, 01 Feb 2017 14:50:31 -0500 (EST) [thread overview]
Message-ID: <20170201.145031.295104986575080480.davem@davemloft.net> (raw)
In-Reply-To: <1485977680-203775-1-git-send-email-vijay.ac.kumar@oracle.com>
From: Vijay Kumar <vijay.ac.kumar@oracle.com>
Date: Wed, 1 Feb 2017 11:34:36 -0800
> Currently Stop-A (L1A) does not make the kernel switch to OBP on panic.
This is intentional, the kernel prints a message telling the user to
press break (L1-A) if they want to drop out of the kernel and we force
the break to be allowed by setting stop_a_enabled.
I'm wondering why there is so much effort being directed into BRK
behavior.
If you want to break into the OK prompt, have the reboot-cmd
environment variable set appropriately, and simply hit BRK and it will
work in both ldom and non-ldom environments.
next prev parent reply other threads:[~2017-02-01 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 19:34 Vijay Kumar
2017-02-01 19:34 ` [PATCH v3 1/4] sparc64: Set cpu state to offline when stopped Vijay Kumar
2017-02-01 19:34 ` [PATCH v3 2/4] sparc64: Migrate hvcons irq to panicked cpu Vijay Kumar
2017-02-01 19:34 ` [PATCH v3 3/4] sparc64: Send break twice from console to return to boot prom Vijay Kumar
2017-02-01 19:34 ` [PATCH v3 4/4] Documentation/sparc: Steps for sending break on sunhv console Vijay Kumar
2017-02-01 19:50 ` David Miller [this message]
2017-02-01 21:20 ` [PATCH v3 0/4] sparc64: Jump to boot prom from console on panic Vijay Kumar
2017-02-23 16:27 ` David Miller
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=20170201.145031.295104986575080480.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=karl.volz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.gardner@oracle.com \
--cc=sparclinux@vger.kernel.org \
--cc=vijay.ac.kumar@oracle.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
all inboxes | Powered by JetHome®