From owner-freebsd-sparc64@FreeBSD.ORG Tue Mar 30 17:33:40 2010 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 1C8D51065678 for ; Tue, 30 Mar 2010 17:33:40 +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 83DFF8FC0A for ; Tue, 30 Mar 2010 17:33:39 +0000 (UTC) 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 o2UHXbto000154; Tue, 30 Mar 2010 19:33:37 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id o2UHXa3N000153; Tue, 30 Mar 2010 19:33:36 +0200 (CEST) (envelope-from marius) Date: Tue, 30 Mar 2010 19:33:36 +0200 From: Marius Strobl To: Craig Butler Message-ID: <20100330173336.GA99585@alchemy.franken.de> References: <201003292200.o2TM0IIV019575@freefall.freebsd.org> <1269900827.2048.7.camel@main.lerwick.hopto.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1269900827.2048.7.camel@main.lerwick.hopto.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: sparc64/144867: panic: trap: memory address not aligned booting Sunfire 280R 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, 30 Mar 2010 17:33:40 -0000 On Mon, Mar 29, 2010 at 11:13:47PM +0100, Craig Butler wrote: > > > On Mon, 2010-03-29 at 22:00 +0000, Rob Farmer wrote: > > The following reply was made to PR sparc64/144867; it has been noted by GNATS. > > > > cas0: mem 0x200000-0x3fffff at device > > 1.0 on pci1 > > panic: trap: memory address not aligned > > 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 0xc0a0e330 > > panic() at panic+0x198 > > trap() at trap+0x220 > > -- memory address not aligned sfar=0x7fd00200001 sfsr=0x1d007d %o7=0xc016f1c8 -- > > cas_pci_attach() at cas_pci_attach+0xb1c > > device_attach() at device_attach+0x68 > > bus_generic_attach() at bus_generic_attach+0x10 > > ofw_pcibus_attach() at ofw_pcibus_attach+0x2e4 > > device_attach() at device_attach+0x68 > > bus_generic_attach() at bus_generic_attach+0x10 > > schizo_attach() at schizo_attach+0xe04 > > device_attach() at device_attach+0x68 > > bus_generic_new_pass() at bus_generic_new_pass+0x130 > > bus_generic_new_pass() at bus_generic_new_pass+0xbc > > bus_set_pass() at bus_set_pass+0xc4 > > configure() at configure+0x4 > > mi_startup() at mi_startup+0xf0 > > btext() at btext+0x2c > > db> > > > > -- > > Rob Farmer > > > > > > Marius > > > > > cassini memory address trap.... same as on the b100s in the B1600 > chassis I think -- I bet if you compile a kernel without device cas > it'll get past that bit -- problem then is no network... Yes, at this point it appears to be the same problem as seen with the on-board NIC of b100. > > Marius- I'll have a look at setting up a netboot server and look at > getting terminal and blade access for you this weekend if your still > interested. That would be helpful. > I hope to help in anyway possible but me head exploded > after trying to debug the panic :) > > That is if they are related... IIRC you said something to do with the > way the BAR was getting assigned. > Treating BARs containing 0 as invalid was another issue preventing the on-board NICs of b100 from working but that has been fixed and now works as seen with other hardware. Marius