-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Memory's a bit fuzzy, here, but I think I was referring to a BIOS
update for the RAID controller. This is using the onboard SCSI
controller for the physical connection, with an add-in Adaptec RAID
(with no physical ports: It's some crazy IBM card that turns the
onboard SCSI into a RAID setup.)

According to my photos, when mptbase caused a kernel panic, it was
"FwRev=01000e00h", and the current (working still) setup is
"FwRev=01032715h":

[ 136.187316] mptbase: ioc0: Initiating bringup
[ 136.914911] ioc0: LSI53C1030 B2: Capabilities={Initiator}
[ 137.587588] scsi4 : ioc0: LSI53C1030 B2, FwRev=01032715h, Ports=1,
MaxQ=222, IRQ=32

I still have some boot-time weirdness with this particular box,
though; for example, it seems to take a *very* long time for the RAID
to become available, which causes the kernel to think it is stuck:

BUG: soft lockup - CPU#3 stuck for 61s! [modprobe:671]
BUG: soft lockup - CPU#0 stuck for 61s! [modprobe:1477]

This happens at least twice during boot, for unknown (to me)
reasons... but this behavior can be observed on other kernels, too.
For example, if I boot knoppix (5?), the live environment is up and
settled for a minute or two before it "suddenly" notices a new disk.
Other than that, though, it's been solid for ~10 months now.

~Keith
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk81lK0ACgkQNYHf3mzWKbGaZwCfWzWW3ZHRpd h6WXql5jWMZT/y
s0UAn0DDT9YezgCYF32kIPszLR68Hbjo
=sT0U
-----END PGP SIGNATURE-----




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4F3594AD.5070304@lehigh.edu">http://lists.debian.org/4F3594AD.5070304@lehigh.edu