From owner-freebsd-alpha Wed Jan 27 16:10:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06486 for freebsd-alpha-outgoing; Wed, 27 Jan 1999 16:10:34 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06473 for ; Wed, 27 Jan 1999 16:10:28 -0800 (PST) (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.1/8.9.1) with ESMTP id TAA01460; Wed, 27 Jan 1999 19:10:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id TAA95762; Wed, 27 Jan 1999 19:10:15 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 27 Jan 1999 19:10:15 -0500 (EST) To: shimon@simon-shapiro.org Cc: freebsd-alpha@FreeBSD.ORG, Mark Salyzyn Subject: Re: Alpha/PCI Help Request In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13999.42675.900087.538238@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon Shapiro writes: > Hi Y'll > * The PCI probe banner announces that the card is on int a, irq 0. this > does not look good to me. I have no idea how to set the IRQ, other than > what is done already in the driver (sys/pci/dpt_pci.c, and > sys/dev/dpt/dpt_scsi.c) I assume you're on a machine that treats pci interrupts differently than ISA interrupts (nearly everything but an AS200 or a multia)? If so, then all's well. But the message should probably either have 16 added to it so that it matches the output from vmstat -i, or it should read 'int a PCI irq 0'... > > * The system abort booting at this point, dropping back to the SRM which > says: > > halted CPU 0 > > halt code = 7 > machine check while in PAL mode > PC = 18400 > boot failure > >>> You *might* be able to get a meaningful ra out of the SRM console. Try something like: >>>e -virtual ra gpr: 1A ( R26) FFFFFC0000498560 Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message