From: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Wed, 7 Feb 2024 12:16:56 +0100 [thread overview]
Message-ID: <ZcNmqBZhiQblg8aQ@grumpf.hope-2000.org> (raw)
In-Reply-To: <17073018880.aee415.22502@composer.illumos.topicbox-beta.com>
Hi Maurilio,
On Wed, Feb 07, 2024 at 05:31:28AM -0500, maurilio.longo via illumos-developer wrote:
> I'm using omnios bloody 20240111 to see if my HPE MR216i-p controller
> is recognized.
> It is, its pci id, pciex1000,10e2, is between the ones assigned to
> lmrc, but when booting I get a panic inside the driver which can be
> seen here
>
> https://imgur.com/a/qhRuYJ2
This is a panic stack I haven't seen before. Obviously it's running into
the default case at the end of lmrc_process_mpt_pkt(), meaning lmrc got
an unknown status from a command that completed and doesn't know how to
proceed from there.
Can you please send me the panic message? That should be included near
the end of the output of ::msgbuf, just before the panic stack. It
should look like this:
command failed, status = %x, ex_status = %x, cdb[0] = %x
(That being said, I realize starting a panic message with a ! is a bug
in itself. Sorry.)
Hans
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
next prev parent reply other threads:[~2024-02-07 11:16 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 [this message]
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
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=ZcNmqBZhiQblg8aQ@grumpf.hope-2000.org \
--to=rosenfeld@grumpf.hope-2000.org \
--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).