From owner-freebsd-alpha Thu Jan 28 06:46:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25037 for freebsd-alpha-outgoing; Thu, 28 Jan 1999 06:46:25 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA25031 for ; Thu, 28 Jan 1999 06:46:23 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 98853 invoked by uid 1000); 27 Jan 1999 20:52:35 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 27 Jan 1999 15:52:35 -0500 (EST) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Doug Rabson Subject: Re: Alpha/PCI Help Request Cc: freebsd-alpha@FreeBSD.ORG, Mark Salyzyn Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson, On 28-Jan-99 you wrote: ... > > * 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) > > This is quite normal for a 164LX based system. Good. One potential source of headache gone... ... > > > > halted CPU 0 > > > > halt code = 7 > > machine check while in PAL mode > > PC = 18400 > > boot failure > > >>> > > > > * Obviously the driver works under IA (i386), or I could not type this > > message :-) > > > > If this rings a bell, please let me know. I will try, in the meantime > > to > > isolate the exact line of code that blows up (1C resolution), and post > > some > > more information. > > This kind of error sometimes happens when accesses are made to i/o > memory > which isn't backed by a real device. The way I usually debug this is to > single step the code until I find exactly what the bogus address was. > The > answer is often obvious at that point. Are you using kernel-gdb for > this? > It makes this stuff a *lot* easier. This is the game plan... thanx! Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message