mps(4) blocks panic-reboot

Harry Schmalzbauer freebsd at omnilan.de
Thu Jun 1 09:29:55 UTC 2017


 Hello,

I'm not sure if scsi@ is the correct list, but since my problem seems to
be mps(4) related, I thought asking here shouldn't be too wrong.

There's not much to add to the topic: If my stable/11 setup panics, the
system doesn't reboot (besides IPMI-watchdog takes over this task).
The machine stucks with these last lines:
Dumping 1669 out of 15734
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
Dump complete
mps0: Sending StopUnit: path (xpt0:mps0:0:2:ffffffff):  handle 12
mps0: Incrementing SSU count
mps0: Sending StopUnit: path (xpt0:mps0:0:3:ffffffff):  handle 11
mps0: Incrementing SSU count
mps0: Sending StopUnit: path (xpt0:mps0:0:4:ffffffff):  handle 10
mps0: Incrementing SSU count
mps0: Sending StopUnit: path (xpt0:mps0:0:5:ffffffff):  handle 9
mps0: Incrementing SSU count
mps0: Sending StopUnit: path (xpt0:mps0:0:6:ffffffff):  handle 13
mps0: Incrementing SSU count

Then, nothing happens. On a similar setup without mps(4), the machine
reboots after the panic.

Is this a known problem/feature?

Thanks,

-harry


More information about the freebsd-scsi mailing list