From owner-freebsd-stable Tue May 22 12: 5:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 8334237B424 for ; Tue, 22 May 2001 12:05:30 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f4MJ5LU43175; Tue, 22 May 2001 13:05:27 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200105221905.f4MJ5LU43175@aslan.scsiguy.com> To: Matt Dillon Cc: stable@FreeBSD.ORG Subject: Re: Continuing ahc problems - also cause fxp failure In-Reply-To: Your message of "Tue, 22 May 2001 12:01:08 PDT." <200105221901.f4MJ18k07657@earth.backplane.com> Date: Tue, 22 May 2001 13:05:21 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I will buy a null-modem cable and hook the serial port up to another > box in the rack. I gave you the meat but I realize it wasn't as complete > as it could be. > > Oh yah, one thing I forgot... the machine was locked up for an hour > before I got to the office. When I got the office the console was > still producing periodic failure messages for both fxp0 and ahc0, > and I could break into the debugger. So I am certain that it isn't > a memory issue or anything like. The fact that *both* fxp0 and ahc0 > died should be telling. > > -Matt They aren't even on the same PCI bus. Do you know if there is a BIOS update for this box? Perhaps the chipset is not being setup correctly. I saw something similar on an IBM RCC 3.0LE system. The remote system monitor would trigger a lockup when dumping video memory over the serial port. IBM resolved this with a BIOS update. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message