From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 9 14:18:39 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 DF0FD16A4CE for ; Sun, 9 Jan 2005 14:18:39 +0000 (GMT) Received: from mithlond.org (polyphoto1.comites.polymtl.ca [132.207.115.71]) by mx1.FreeBSD.org (Postfix) with SMTP id 1034843D46 for ; Sun, 9 Jan 2005 14:18:39 +0000 (GMT) (envelope-from tikho@anor.net) Received: (qmail 16135 invoked from network); 9 Jan 2005 14:17:55 -0000 Received: from unknown (HELO valinor.mithlond.org) (60.25.0.73) by 0 with SMTP; 9 Jan 2005 14:17:55 -0000 Received: from [192.168.1.3] (unknown [192.168.1.3]) by valinor.mithlond.org (Postfix) with ESMTP id 737E6913A4; Sun, 9 Jan 2005 14:18:16 +0000 (UTC) Message-ID: <41E13CEE.4060701@anor.net> Date: Sun, 09 Jan 2005 22:17:18 +0800 From: Cyril Tikhomiroff User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marius Strobl References: <41E09473.6070106@anor.net> <20050109145433.A21246@newtrinity.zeist.de> In-Reply-To: <20050109145433.A21246@newtrinity.zeist.de> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 14:18:40 -0000 Hello, Thank you for your reply. Here it is: ok cd /pci@1f,4000 ok ls f0082474 SUNW,hme@2,1 f007c398 scsi@3 f0074bd0 network@1,1 f0074a34 pci108e,1000 f0060540 ebus@1 then ok cd pci108e,1000 ok .properties name pci108e,1000 fast-back-to-back devsel-speed 00000001 class-code 00068000 max-latency 00000019 min-grant 0000000a revision-id 00000001 device-id 00001000 vendor-id 0000108e This device lack the reg properties. I don't what device it is. All other devices have the reg properties. What should I do next ? Cyril Marius Strobl wrote: >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 > > >