Date: Mon, 19 Nov 2001 13:45:45 +0100 (CET) From: "Hartmann, O." <ohartman@klima.physik.uni-mainz.de> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FBSD4.4-STABLE SMP broken! Message-ID: <20011119133029.E17467-100000@klima.physik.uni-mainz.de> In-Reply-To: <20011110110055.A92378@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Nov 2001, Kris Kennaway wrote: Hello, and especially hello to Kris. Well, Krsi, you're in suspecting the hardware. The day before I did a new 'make world' I updated the firmware of the RAID controller to the most recent version of what LSI Logic offers (it seems that AMI got rid of their RAID part and LSI Logic do all the support now). The BIOS revision is 3.12, the firmware has revision F160. With the old BIOS 3.11 and firmware W159 no problems occured, but after the update, the system seems to have problems with shared IRQs. I swapped the RAID controller to another PCI slot (it's now plugged in into a PCI64/66 slot which is detected as another PCI bus in FBSD) and I left the Intel EtherExpress NIC in its previous PCI64/33 slot. After doing this, the system runs perfectly. The problem seems to be hardly related to the TYAN 2500 main PCB! Another machine with the ASUS CUV4X-D and the same RAID controller (AMI MegaRAID Enterprise/Elite 1600 series) and the same NIC do not have the problems, they also do not have 64 Bit PCI slots. TYAN's Thunder 2500 seems to be very sensitive. In the past I reported about sporadic crashes of the same system an no one was able to repruce these reboots, although several users of other high end main PCBs reported the same. It seems to me that IRQ routing/sharing is one of the main targets to be watched with those PCBs. In my case, I did a test with Linux on the same hardware (SuSE 7.1) and Linux has similar problems on the TYAN after the RAID's firmware upgrade. It is very suspicious that expensive high end main PCBs do have a lot of problems rather than those for low budgets ... I do not know whether these explorations of problems with the RAID systems I have helps for the next generation of FBSD users, but I hope I clear something which could affect FreeBSD's reliability. :>On Sat, Nov 10, 2001 at 05:25:20PM +0100, Hartmann, O. wrote: :>> I did a cvsupdate today, the target machine was running :>> stable for the last four days. :>> :>> After the update and make world today, the system run a few minutes and then :>> get stuck ... no keyboard input, nothing, no network response. :> :>With all the unreproducible crashes and hangs you seem to have, I've :>gotta wonder whether there's something wrong with your hardware. :> :>Kris :> -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institutes fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011119133029.E17467-100000>