Re: mpii zfs xen unstable on -current

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sat, 25 Jun 2022 01:04:04 +0200
    From:        "oskar%fessel.org@localhost" <oskar%fessel.org@localhost>
    Message-ID:  <056EBA16-27DC-42B3-80A4-7CEF3F10162D%fessel.org@localhost>


  | [ 236025.4127414] panic: kernel diagnostic assertion "xs->resid =3D=3D =
  | xs->datalen" failed: file "/hurz/src/sys/dev/pci/mpii.c", line 3207=20
  | [ 236025.4127414] cpu0: Begin traceback...
  | [ 236025.4227374] vpanic() at netbsd:vpanic+0x177
  | [ 236025.4227374] kern_assert() at netbsd:kern_assert+0x4b
  | [ 236025.4227374] mpii_scsi_cmd_done() at =
  | netbsd:mpii_scsi_cmd_done+0x30b
  | [ 236025.4227374] mpii_intr() at netbsd:mpii_intr+0x21e

  | The machine i want to fix is running NetBSD 9.99.97 (XEN3_DOM0) #4: Thu =
  | Jun 16 13:02:43 CEST 2022

Try updating to a very new -current, there have been fixes to the mpii
driver (I have observed happening, I don't have that hardware) in the
very recent past (June 16 is ages ago!).   There might be other issues
(there always is that possibility with very new code) but if so, they
might not affect you as much as this one does.

That you don't see issues with a non-Xen system and the same hardware
might be because of the way interrupts are delivered (a bit different
for Xen clients than it is for bare metal systems).

If this is the problem, then that might be an easy fix, and all of the
rest of your questions (if still material) can be considered without
imagining that they may alter this issue.

kre