From: Laurence Oberman <loberman@redhat.com>
To: Mateusz Nowicki <mateusz.nowicki@posteo.net>, don.brace@microchip.com
Cc: martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, storagedev@microchip.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] scsi: smartpqi: fix PCIe hot reset recovery
Date: Wed, 06 May 2026 18:21:41 -0400 [thread overview]
Message-ID: <9624a8d152197522d353ef7bb2b4928d1c6238ae.camel@redhat.com> (raw)
In-Reply-To: <cover.1778075755.git.mateusz.nowicki@posteo.net>
On Wed, 2026-05-06 at 14:01 +0000, Mateusz Nowicki wrote:
> A PCIe bus reset (e.g. "echo 1 > /sys/bus/pci/devices/<bdf>/reset")
> on a
> controller without FLR support leaves the HPE SR932i-p Gen10+
> unusable
> until reboot: smartpqi registers no pci_error_handlers, so the driver
> is not notified, firmware reverts to SIS mode, and all queue mappings
> are dropped while the driver still drives PQI.
>
> Patch 1 adds .reset_prepare / .reset_done reusing
> pqi_ofa_ctrl_quiesce() / _unquiesce() / pqi_ctrl_init_resume().
>
> Patch 2 raises SIS_CTRL_READY_RESUME_TIMEOUT_SECS from 90s to 180s,
> matching the cold-boot path; without this patch 1 fails at the SIS
> ready check because firmware boot after reset takes ~125s on the
> SR932i-p Gen10+.
>
> Tested on HPE SR932i-p Gen10+ against Linus' master at 74fe02ce122a.
>
> Note: the From: header is my Posteo address because my employer's
> SMTP
> is unavailable for external mailing lists. The Signed-off-by carries
> the Microchip attribution.
>
> Mateusz Nowicki (2):
> scsi: smartpqi: add pci_error_handlers for bus reset recovery
> scsi: smartpqi: increase SIS ctrl ready resume timeout to 180s
>
> drivers/scsi/smartpqi/smartpqi_init.c | 47
> +++++++++++++++++++++++++++
> drivers/scsi/smartpqi/smartpqi_sis.c | 2 +-
> 2 files changed, 48 insertions(+), 1 deletion(-)
>
> --
> 2.43.0
>
>
>
Hello
I did reproduce this so I am testing the patches as well.
They look correct to me, I will reply again after testing with a
review.
Thanks
Laurence
[2513778.140012] smartpqi 0000:64:00.0: no heartbeat detected - last
heartbeat count: 4207808511
[2513778.140031] smartpqi 0000:64:00.0: controller offline: reason code
0x4 (no controller heartbeat detected)
[2513778.141346] sd 1:0:0:0: [sda] tag#549 FAILED Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=18s
[2513778.141355] sd 1:0:0:0: [sda] tag#550 FAILED Result:
"xfs_buf_ioend_handle_error+0xd5/0x3f0 [xfs]" at daddr 0x9f78 len 8
error 5
[2513778.141526] XFS (dm-0): log I/O error -5
next prev parent reply other threads:[~2026-05-06 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 14:01 [PATCH 0/2] scsi: smartpqi: fix PCIe hot reset recovery Mateusz Nowicki
2026-05-06 14:01 ` [PATCH 1/2] scsi: smartpqi: add pci_error_handlers for bus " Mateusz Nowicki
2026-05-06 14:01 ` [PATCH 2/2] scsi: smartpqi: increase SIS ctrl ready resume timeout to 180s Mateusz Nowicki
2026-05-06 22:21 ` Laurence Oberman [this message]
2026-05-07 1:45 ` [PATCH 0/2] scsi: smartpqi: fix PCIe hot reset recovery Laurence Oberman
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=9624a8d152197522d353ef7bb2b4928d1c6238ae.camel@redhat.com \
--to=loberman@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=don.brace@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mateusz.nowicki@posteo.net \
--cc=storagedev@microchip.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