From owner-freebsd-sparc64@FreeBSD.ORG Tue Dec 9 08:13:04 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5C1B1065672 for ; Tue, 9 Dec 2008 08:13:04 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 4CE398FC17 for ; Tue, 9 Dec 2008 08:13:04 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id mB98D0NX014749; Tue, 9 Dec 2008 09:13:01 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id mB98D0NV014748; Tue, 9 Dec 2008 09:13:00 +0100 (CET) (envelope-from marius) Date: Tue, 9 Dec 2008 09:13:00 +0100 From: Marius Strobl To: Beat =?unknown-8bit?Q?G=E4tzi?= Message-ID: <20081209081300.GK52382@alchemy.franken.de> References: <4935839E.4010000@chruetertee.ch> <20081204180726.GA19048@alchemy.franken.de> <26f6c7210812050014l5dac2871k7ca1db1677d0b7d0@mail.gmail.com> <20081205172112.GA52382@alchemy.franken.de> <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Booting of 200811 snapshot on Sun Fire V880 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 08:13:04 -0000 On Mon, Dec 08, 2008 at 11:59:50AM +0100, Beat Gtzi wrote: > > The new image solves the initial issue but now it fails at: > [...] > isp1: port 0x1000-0x10ff mem > 0x2000000-0x2000fff at device 4.0 on pci3 > pcib2: WARNING: using devices behind PCI-PCI bridges may cause data > corruptionisp1: [ITHREAD] > panic: trap: data access error > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x80: ta %xcc, 1 > db> bt > Tracing pid 0 tid 100000 td 0xc0848780 > panic() at panic+0x20c > trap() at trap+0x570 > -- data access error %o7=0xc01e6168 -- > isp_pci_rd_reg_1080() at isp_pci_rd_reg_1080+0x198 > isp_reset() at isp_reset+0x728 > isp_pci_attach() at isp_pci_attach+0x1f70 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcibus_attach() at ofw_pcibus_attach+0x72c > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcib_attach() at ofw_pcib_attach+0x38 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcibus_attach() at ofw_pcibus_attach+0x72c > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > schizo_attach() at schizo_attach+0x13b8 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > nexus_attach() at nexus_attach+0x4fc > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > root_bus_configure() at root_bus_configure+0x28 > configure() at configure+0x4 > mi_startup() at mi_startup+0x18c > btext() at btext+0x30 > db> > > I could provide remote access to the server but I may need some days > to set up a netboot environment. > If you haven't lost patience yet, could you please try (currently still uploading): http://people.freebsd.org/~marius/8.0-20081208-SNAP-sparc64-disc1.iso.gz ? Btw., sorry for the inconveniences, the drivers bugs you happen to hit aren't actually sparc64-specific though. Marius