From owner-freebsd-alpha Thu Jul 18 6:21:32 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB27637B400 for ; Thu, 18 Jul 2002 06:21:29 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AC6543E5E for ; Thu, 18 Jul 2002 06:21:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA21725 for ; Thu, 18 Jul 2002 09:21:28 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6IDKw154941; Thu, 18 Jul 2002 09:20:58 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15670.49338.264301.989244@grasshopper.cs.duke.edu> Date: Thu, 18 Jul 2002 09:20:58 -0400 (EDT) To: freebsd-alpha@FreeBSD.ORG Subject: Re: machine checks on a AlphaPC 164LX In-Reply-To: <15669.57930.427134.220183@grasshopper.cs.duke.edu> References: <15669.57930.427134.220183@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andrew Gallatin writes: > > I've got a PC164LX which will crash with a machine check under heavy > disk IO to its on-board CMD 646 ATA controller. <..> > db> tr > Debugger() at Debugger+0x2c > panic() at panic+0x100 > machine_check() at machine_check+0x1f0 > interrupt() at interrupt+0x198 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 4) --- > cia_bwx_inb() at cia_bwx_inb+0x24 > ata_dmastatus() at ata_dmastatus+0x30 <..> > I'm starting to think that this might be just a sick motherboard. Does > anybody else have any feelings about this? > The truely scary thing is that using swiz chipset access, rather the bwx chipset access seems to stablize the machine. I still think I'm going to put it down to a sick motherboard, but I wonder if there's a chance there's something wrong with our CIA bwx code.... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message