Robert Riches
2018-05-23 03:43:33 UTC
Attempted a Slackware 14.2 installation on a physical machine
with RAID10 filesystems, including the root filesystem, but with
/boot on a plain (non-RAID) partition. A similar test VM had
worked beautifully for months--with initrd and such. A second
installation on the same physical machine but with the root
filesystem on a plain partition works fine, at least to the point
of running X, launching an xterm, and from the xterm launching
xclock.
The problematic machine gets to about 5 seconds into booting,
past the point where the system tries (unsuccessfully) to find
RAID v0.90 superblocks/signatures. Then, there's a kernel panic
with a long backtrace taking up the whole screen. Everything in
between flies by on the screen so quickly there's no way for
human eyes to detect what messages happen right before the panic
and backtrace. The backtrace has function names that seem to
indicate attempts to mount the real root filesystem and functions
that have "APIC" in their names.
Sorry about so few details at this point, but it's getting close
to nightfall. I'll try to post more details tomorrow.
Meanwhile, if anyone has pointers to how-to documents for either
finding the root cause of a panic like this or solving (working
around) this sort of thing, I'd be extremely grateful.
(I'm _SOOOOO_ glad I structured the machine's partition scheme to
allow me to fall back to the previous OS installation with a few
spare partitions for experimenting. It saved my bacon this
time.)
Thanks.
with RAID10 filesystems, including the root filesystem, but with
/boot on a plain (non-RAID) partition. A similar test VM had
worked beautifully for months--with initrd and such. A second
installation on the same physical machine but with the root
filesystem on a plain partition works fine, at least to the point
of running X, launching an xterm, and from the xterm launching
xclock.
The problematic machine gets to about 5 seconds into booting,
past the point where the system tries (unsuccessfully) to find
RAID v0.90 superblocks/signatures. Then, there's a kernel panic
with a long backtrace taking up the whole screen. Everything in
between flies by on the screen so quickly there's no way for
human eyes to detect what messages happen right before the panic
and backtrace. The backtrace has function names that seem to
indicate attempts to mount the real root filesystem and functions
that have "APIC" in their names.
Sorry about so few details at this point, but it's getting close
to nightfall. I'll try to post more details tomorrow.
Meanwhile, if anyone has pointers to how-to documents for either
finding the root cause of a panic like this or solving (working
around) this sort of thing, I'd be extremely grateful.
(I'm _SOOOOO_ glad I structured the machine's partition scheme to
allow me to fall back to the previous OS installation with a few
spare partitions for experimenting. It saved my bacon this
time.)
Thanks.
--
Robert Riches
***@jacob21819.net
(Yes, that is one of my email addresses.)
Robert Riches
***@jacob21819.net
(Yes, that is one of my email addresses.)