We're attempting to make a very large RAID.
I got a smaller one working for a while, but then we got
more disks and kernel 2.0.35 came out, so we upgraded to
it & put 4 more disks in the RAID box. Now we can get up
to about 1/3 of the way through our e2fsck and then some-
is fairly standard:
- 2 adaptec aic7881U (fast ultra wide) SCSI controlers
- 2 PII/266s
- 1 EtherExpress 100B or DEC Tulip 21140 ethernet card
- 1 Matrox Millenium II PCI (but no X on that host)
- 7 Quantum 17.4 GB fast/wide SCSI disks
+ 3 on one AIC, 4 on the other
- 265 MB RAM
- 3 IDE disks for /, /tmp, swap
It looked like it was an SMP / EtherExpress conflict (we
saw an `aieee' from the eepro100 driver and then an `irq
deadlock detected by cpu 1', separated by some icky dump
of stack / register info, which of course we'd neglected
to write down.) So we replaced the ethernet card, but it
keeps panic'ing. The one constant is a message ``invalid
operand 0000''.
What information can we provide to help trace this bug?
- Josh & the RLab
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html