On Sun, 22 Jun 2025, Brian Buhrow wrote:
Hello. Given the word that this machine previously ran Linux and not
oldeer versions of
NetBSD, I'm more convinced you have an incompatibility between the the machines
implementation
of MSI/MSIX interrupt handling and NetBSD's implementation. Some suggestions
of things to try
to see if the behavior changes, either fixing the issue, or pointing at the
problem more
directly.
1. If the machine can boot in EFI mode or legacy mode, try switching the mode
and see if that
changes the behavior.
2. If you can turn off MSI/MSIX interrupt services in the BIOS, try doing that
and see if that
makes a difference.
3. If possible, update the BIOS on the motherboard to the latest version.
I think you should be able to do one or more of these things and while I don't
know if it will
fix the issue, I think it will give clues as to what is going on.
As to the question about killing init, even aafter hours of errors, no
you won't be able
to write a crash dump, but that's not the purpose of my suggestion. What I was
trying to
answer was whether doing a warm reset of the machine brings it back or if a
cold reset is
required. Killin init will cause the machine to reboot on its own, forcing a
warm reset when,
according to your reporting, only a cold reset was possible.
Since you asked so directly, I noticed that too. When the problem occurs
and you only perform a warm reboot, the netbsd driver for the Perc h330
doesn't recognize any disks or volumes. A cold reboot is always necessary.
However, after a cold reboot, all disks and volumes are always recognized.
Will that help solve the problem?
Thank you for your efforts
Regards
Uwe
Hope that helps.
-Brian
