From owner-freebsd-alpha Wed Jul 17 14:32:30 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 E025D37B400 for ; Wed, 17 Jul 2002 14:32:25 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C4F843E3B for ; Wed, 17 Jul 2002 14:32:25 -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 RAA02902 for ; Wed, 17 Jul 2002 17:32:24 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6HLVsK53775; Wed, 17 Jul 2002 17:31:54 -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: <15669.57930.427134.220183@grasshopper.cs.duke.edu> Date: Wed, 17 Jul 2002 17:31:54 -0400 (EDT) To: freebsd-alpha@freebsd.org Subject: machine checks on a AlphaPC 164LX 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 I've got a PC164LX which will crash with a machine check under heavy disk IO to its on-board CMD 646 ATA controller. The panic's always look something like this: unexpected machine check: mces = 0x1 vector = 0x670 param = 0xfffffc0000006068 pc = 0xfffffc0000575624 ra = 0xfffffc000035e590 curproc = 0 panic: machine check panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe00176a7720> 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 ata_pci_intr() at ata_pci_intr+0x3a8 ata_intr() at ata_intr+0x24 isa_handle_intr() at isa_handle_intr+0x2c alpha_dispatch_intr() at alpha_dispatch_intr+0x8c interrupt() at interrupt+0x1d8 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- vm_page_zero_idle() at vm_page_zero_idle+0x20 Lpgzero() at Lpgzero+0x8 --- root of call graph --- If I look at what ATA is using for the call to cia_bwx_inb (via bus pio) in gdb, I don't see anything terribly wrong (like an out-of-range value): (kgdb) p *adp->device->channel->r_altio $7 = {r_link = {cqe_next = 0xfffffe0004db0300, cqe_prev = 0xfffffe0004db0380}, r_sharelink = {le_next = 0x0, le_prev = 0x0}, r_sharehead = 0x0, r_start = 1014, r_end = 1014, r_flags = 3, r_virtual = 0x0, r_bustag = 0, r_bushandle = 1014, r_dev = 0xfffffe0004db1100, r_rm = 0xfffffc000064e4b8} 1014 is in the range of IO-ports: atapci0: port 0x1110-0x111f irq 5 at device 11.0 on pci0 I'm starting to think that this might be just a sick motherboard. Does anybody else have any feelings about this? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message