From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 9 13:54:54 2005 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D006F16A4CE for ; Sun, 9 Jan 2005 13:54:54 +0000 (GMT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 229D143D1D for ; Sun, 9 Jan 2005 13:54:54 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) j09Dsdha022013; Sun, 9 Jan 2005 14:54:39 +0100 (CET) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id j09DsYnB022012; Sun, 9 Jan 2005 14:54:34 +0100 (CET) (envelope-from marius) Date: Sun, 9 Jan 2005 14:54:34 +0100 From: Marius Strobl To: Cyril Tikhomiroff Message-ID: <20050109145433.A21246@newtrinity.zeist.de> References: <41E09473.6070106@anor.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <41E09473.6070106@anor.net>; from tikho@anor.net on Sun, Jan 09, 2005 at 10:18:27AM +0800 X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.5; VDF: 6.29.0.52; host: newtrinity.zeist.de) cc: freebsd-sparc64@freebsd.org Subject: Re: 5.3 cd installation panic X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 13:54:54 -0000 On Sun, Jan 09, 2005 at 10:18:27AM +0800, Cyril Tikhomiroff wrote: > Hello, > > When i boot a minimal 5.3 installation CD on my Ultra 30 station, i got > a kernel panic: > > Sun Ultra 30 UPA/PCI (UltraSPARC-II 296MHz), No Keyboard > OpenBoot 3.11, 512 MB memory installed, Serial #10115596. > Ethernet address 8:0:20:9a:5a:c, Host ID: 809a5a0c. > <...> > pcib0 dvma: DVMA map: 0xfc000000 to 0xffffffff > pci0: on pcib0 > panic: ofw_pci_attach: OF_getprop failed > cpuid = 0 > Uptime: 1s > Automatic reboot in 15 seconds - press a key on the console to abort > > I have a PCI sun network card in the box. > The panic is triggered by at least one of the PCI device nodes not having a "reg" property which isn't expected for PCI devices. This could be the result of a broken device, connection problems of the network add-on card but also a bug in the firmware revision you're using which might make sense to work around if possible. Could you therefore please check which of the PCI device nodes doesn't have a "reg" property? To do so enter `show-devs` at the boot monitor prompt. You will get a list of all device nodes including two PCI bridges which will look like "/pci@1f,2000" and "/pci@1f,4000". For both of them do `cd `, e.g. `cd /pci@1f,2000`, followed by a `ls` and the devices on that PCI bus will be listed (this is a device tree and you can navigate with file-system like commands). For one of the two PCI busses probably no device will be listed for the other one it will look like "scsi@3" etc., please past this/these list(s). `cd` into each of the PCI devices nodes with e.g. `cd scsi@3` and enter `.properties`, you will get a list of the properties of the device node and their values. At least one of the PCI device nodes should be missing a "reg" property. Please paste the whole `.properties` output of this/ these node(s). From the level of a PCI device node you can go back to the PCI bridge node with a `cd ..`. There's no need to descend further than the PCI device nodes, i.e. you don't need to check all of the devices in the Ebus bridge node. Marius