aac(4) can't produce/save crashdumps
This issue is related to
problem no. 2 but this is using an aac(4) RAID controller. This issue
is tested on an IBM x3650 machine with manually-generated panic
through ctrl-alt-escape method and an actual fatal trap error
(debugging an ixgb device driver).
dumpdev=/dev/aacd0s1b # swap device
With ctrl-alt-escape, calling a dumpsys will just hang my system.
db> call dumpsys
dumping to dev #aacd/0x20001, blockno 10486216
#1 Updated by alexh about 5 years ago
While introducing the whole new dumping infrastructure, I also disabled
dumping on aac(4). This at least avoids unexpected results by giving a
warning/error message, but the aac_dump stuff still needs to be ported from a
If anyone wants to do this, I can provide some help and/or guidance if needed;
although it should be rather straightforward.