From owner-freebsd-arm@FreeBSD.ORG Tue Mar 22 15:57:16 2011 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DABB1065673 for ; Tue, 22 Mar 2011 15:57:16 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from wilson.telenet-ops.be (wilson.telenet-ops.be [195.130.132.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7638FC0C for ; Tue, 22 Mar 2011 15:57:15 +0000 (UTC) Received: from jacques.telenet-ops.be (unknown [195.130.132.50]) by wilson.telenet-ops.be (Postfix) with ESMTP id 7947E70F2D for ; Tue, 22 Mar 2011 16:45:10 +0100 (CET) Received: from triton.sigsegv.be ([94.224.101.111]) by jacques.telenet-ops.be with bizsmtp id NFl81g0082QCY5q0JFl8Qa; Tue, 22 Mar 2011 16:45:08 +0100 Received: from nereid (nereid.neptune.sigsegv.be [IPv6:2001:470:c8f4:0:200:ff:fe00:8]) by triton.sigsegv.be (Postfix) with SMTP id 1092F1C269; Tue, 22 Mar 2011 16:45:07 +0100 (CET) Received: by nereid (sSMTP sendmail emulation); Tue, 22 Mar 2011 16:45:06 +0100 Date: Tue, 22 Mar 2011 16:45:05 +0100 From: Kristof Provost To: Marcin Jurczuk Message-ID: <20110322154505.GH1351@nereid> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-arm@freebsd.org Subject: Re: Iomega iConnect and FreeBSD (kirkwood) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2011 15:57:16 -0000 On 2011-03-22 14:20:06 (+0100), Marcin Jurczuk wrote: > Hello, > > I'm trying to setup FreeBSD 8.2 on iomega iConnect device which is > based on platform similar/(identical) to SheevaPlug and Segate > Dockstar. However not everything seems to beexactly the same bacause I > have problems with kernel boot and mge0 ethernet adapter. > I used DB-88F6XXX kernel conifig since this platform is CPU: Feroceon > 88FR131 rev 1 (Marvell core) > I'm able to boot system however kernel panic occurs with folowing message: > ---------------------------------------- > mge0: at mem > 0xf1072000-0xf1073fff irq 12,13,14,11,46 on mbus0 > mge0: Ethernet address: 00:d0:b8:0d:f6:5d > mge0: attaching PHYs failed > > vm_fault(0xc0bfcd18, 0, 1, 0) -> 1 > Fatal kernel mode data abort: 'Translation Fault (S)' > trapframe: 0xc0d7cc2c > FSR=00000005, FAR=00000008, spsr=600000d3 > r0 =00000016, r1 =f1020200, r2 =00000004, r3 =00080002 > r4 =00000000, r5 =00000000, r6 =0000000c, r7 =00000000 > r8 =c0b58b50, r9 =c229c080, r10=c22c7000, r11=c0d7cc90 > r12=c0d7cc78, ssp=c0d7cc78, slr=c0b30a00, pc =c0b30a00 > > [thread pid 0 tid 100000 ] > Stopped at arm_remove_irqhandler+0x28: ldr r3, [r5, #0x008] > db> > -------------------------------------------- > Is there anyone who have some experience with this platform ? I'm not familiar with that platform, but I remember seeing a very similar error when I was playing with an Orion based board. The driver should be the same (mge). The panic occurs because the cleanup code is incorrect. This problem is fixed in current I think. In this case you probably don't need to worry about the cleanup code though. It's only triggered when the PHY is not found. If you can fix the PHY detection you won't run into the panic any more. In 8.2 mge assumes a static mapping between interface number and PHY address (i.e. PHY address = interface number (0 here) + 8). You can overrule the offset by defining MII_ADDRESS_BASE. Of course, you'll need to know the correct offset first. Regards, Kristof