From owner-freebsd-alpha Mon Sep 4 18:24:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8046137B424 for ; Mon, 4 Sep 2000 18:24:31 -0700 (PDT) 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 VAA03433; Mon, 4 Sep 2000 21:24:30 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e851OUL21790; Mon, 4 Sep 2000 21:24:30 -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 Date: Mon, 4 Sep 2000 21:24:30 -0400 (EDT) To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c (fwd) In-Reply-To: <8oui66$1faq$1@ganerc.mips.inka.de> References: <8oui66$1faq$1@ganerc.mips.inka.de> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14772.18965.506896.703230@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber writes: <..> > the kernel starts up--but as far as the PCI breakage is concerned, > the machine locks up solid here: > > ... > cia0: <2117x Core Logic chipset> > cia0: ALCOR/ALCOR2, pass 3 > cia0: extended capabilities: 21 > pcib0: <2117x PCI host bus adapter> on cia0 > Could you put some printfs in the top of cia_pcib_read_config() and cia_pcib_write_config() and print out the b, s, f, reg & width args? It would be interesting to see if it gets as far as the pci bus probe & where it locks. Also, if you've got a halt switch, can you press it & map the address the SRM console gives for the PC and RA ("ex pc" and "ex ra" at the >>> prompt should do it, then map those addresses using gdb on a debug kernel) Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message