ike help reviewing whether the crashed-kernel / panic-dump /
polled-I/O path can result in a malformed or incomplete SGL being attached =
to a
host write request issued.

In particular, could the panic-time environment, nofault state, or polled C=
AM
path cause the host command to carry an SGL that does not fully or correctly
describe the requested 64KB transfer, even though normal runtime I/O may not
visibly fail?

The firmware team=E2=80=99s position is that the write failure is due to a =
malformed
host SGL, and their validation log is pointing to the host-issued command
itself.

Steps to reproduce:

1. Configure a RAID1 virtual disk on an mrsas controller.
2. Install FreeBSD on the RAID1 VD.
3. Configure crash dumps.
4. Trigger a manual panic.
5. Observe that dump collection starts and then fails with WRITE(10) I/O
errors.
6. Firmware logs report invalidSgl=3D1 for the failing WRITE(10).

--=20
You are receiving this mail because:
You are the assignee for the bug.=