From: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
To: developer@lists.illumos.org
Subject: Re: [developer] panic inside lmrc driver
Date: Mon, 26 Aug 2024 17:23:01 +0200 [thread overview]
Message-ID: <Zsyd1cttcjiMCPw6@grumpf.hope-2000.org> (raw)
In-Reply-To: <17246754470.fe43.63050@composer.illumos.topicbox-beta.com>
On Mon, Aug 26, 2024 at 08:30:47AM -0400, manipm via illumos-developer wrote:
> I am also facing lmrc driver issue. I recently purchased DELL R750xs with PERC H755(in passthrough mode) consisting of 5disk.
>
> I am running latest DELL BIOS. Can someone help me on this.
I'm sorry that you ran into that problem.
https://www.illumos.org/issues/15935
This is a known problem with the DELL PERC H755 which already occured
during the late stages of the driver development. The HBA firmware
pretty much drops dead after a while for no apparent reason, whether the
HBA is under load or completely idle. After a warm reset, the UEFI firmware
complains that it doesn't even see the device on the bus, and a full
power cycle is required to get the controller going again.
We've tried to root-cause this with the help from DELL and Broadcom, but
they didn't ever tell us what really happened to their firmware, nor
what our driver did to cause this. (That is not to say that our driver
did anything wrong in particular, nor that anything a driver could
possibly do should ever be considered an excuse for the HBA firmware to
behave that way.)
That being said, the PERC H355 worked flawlessly with lmrc, and so did
HBAs from other vendors such as Intel.
Hans
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
next prev parent reply other threads:[~2024-08-26 15:23 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
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 [this message]
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=Zsyd1cttcjiMCPw6@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).