From: Toomas Soome <tsoome@me.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Thu, 15 Feb 2024 10:11:58 +0200 [thread overview]
Message-ID: <66C1A001-169D-4532-BA88-974756FE8330@me.com> (raw)
In-Reply-To: <17079826860.4D09.392000@composer.illumos.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
> On 15. Feb 2024, at 09:38, Carsten Grzemba via illumos-developer <developer@lists.illumos.org> wrote:
>
> If it again the case try to force a crash dump on shutdown, e.g.
> add /etc/system:
>
> set pcplusmp:apic_panic_on_nmi = 1
>
> then if the system is frozen
> $ ipmitool -Ilanplus -U idrac-user -P password -H idrac-ip power diag
>
> Note that you probably won't have any luck with a crash dump if the dump device is controlled by lmrc (if lmrc is the reason for frozen system)
>
> long text:
> https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-running-system-using-only-nmi-x86
> illumos <https://illumos.topicbox.com/latest> / illumos-developer / see discussions <https://illumos.topicbox.com/groups/developer> + participants <https://illumos.topicbox.com/groups/developer/members> + delivery options <https://illumos.topicbox.com/groups/developer/subscription>Permalink <https://illumos.topicbox.com/groups/developer/Tf091423c9add514f-M400094e7f67a309bd7a2ce68>
in such case it is good idea to boot as:
ok set nmi=kmdb
ok boot -k
or
ok boot -kd
this way your nmi will get you to the kmdb.
And yes, we should document the ‘nmi’ property, it can have values ‘ignore’, ‘panic’ and ‘kmdb’, see https://src.illumos.org/source/xref/illumos-gate/usr/src/uts/i86pc/os/mlsetup.c?r=d32f26ee#159
rgds,
toomas
[-- Attachment #2: Type: text/html, Size: 2963 bytes --]
next prev parent reply other threads:[~2024-02-15 8:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:31 maurilio.longo
2024-02-07 11:14 ` [developer] " Peter Tribble
2024-02-07 11:16 ` Hans Rosenfeld
2024-02-07 11:46 ` maurilio.longo
2024-02-07 12:04 ` maurilio.longo
2024-02-07 12:29 ` Hans Rosenfeld
2024-02-07 13:01 ` maurilio.longo
2024-02-07 16:47 ` maurilio.longo
2024-02-07 17:01 ` Hans Rosenfeld
2024-02-07 21:35 ` Hans Rosenfeld
2024-02-08 7:59 ` maurilio.longo
2024-02-08 10:42 ` Hans Rosenfeld
2024-02-08 11:01 ` maurilio.longo
2024-02-09 8:06 ` maurilio.longo
2024-02-09 19:55 ` Hans Rosenfeld
2024-02-09 20:36 ` maurilio.longo
2024-02-12 8:11 ` maurilio.longo
2024-02-13 19:32 ` Hans Rosenfeld
2024-02-13 20:55 ` maurilio.longo
2024-02-13 21:03 ` maurilio.longo
2024-02-15 6:50 ` maurilio.longo
2024-02-15 7:38 ` Carsten Grzemba
2024-02-15 8:11 ` Toomas Soome [this message]
2024-02-15 9:44 ` maurilio.longo
2024-02-16 14:36 ` maurilio.longo
2024-02-16 15:20 ` maurilio.longo
2024-02-16 15:27 ` maurilio.longo
2024-02-16 15:42 ` Robert Mustacchi
2024-02-16 20:41 ` maurilio.longo
2024-02-19 21:14 ` maurilio.longo
2024-02-20 8:58 ` maurilio.longo
2024-02-22 17:44 ` maurilio.longo
2024-02-26 8:59 ` maurilio.longo
2024-02-26 9:30 ` Carsten Grzemba
2024-08-26 12:30 ` manipm
2024-08-26 15:23 ` Hans Rosenfeld
2024-02-13 19:23 ` Hans Rosenfeld
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=66C1A001-169D-4532-BA88-974756FE8330@me.com \
--to=tsoome@me.com \
--cc=developer@lists.illumos.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;
as well as URLs for NNTP newsgroup(s).