From owner-freebsd-arm@FreeBSD.ORG Tue Dec 31 18:23:42 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C178C826 for ; Tue, 31 Dec 2013 18:23:42 +0000 (UTC) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4DC571621 for ; Tue, 31 Dec 2013 18:23:42 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id q59so11154338wes.38 for ; Tue, 31 Dec 2013 10:23:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PhfA84vypmhoqe9MfYFkVBREzGipkNBP47Zqj3ONoYw=; b=yZdYL2tZqeqTEvgo9f/l4MgL9O+fIsbhI2rZJugwTDwDgisqMxnSRfW0cWID8RB4RG 7pkRaqPAUMvIToEaylVmQFQo4DawWofY3uuq4J7b6uLq6PmjIBPOlqHXLNaFTg2OuG9O efiZqaXWBtJ2hBUajVgY7wfw6WuzJCT6XkoefFIXymiSUuN2/hUg04uiKMZJ9ShO5p1z ogLAGLkevMZZdDlQbqack+iS96eOsuC6PrE5xa8r6jZBIop3L/L4ROZjINBCUQ2AjkKh k86ra8/S2TUPLe8IqR1s0QfhsuFp3AiLiD75o/+2/rYMS6ecEhJu5hIY/+7wWL80FcAG FkJA== MIME-Version: 1.0 X-Received: by 10.180.93.42 with SMTP id cr10mr24263107wib.11.1388514219787; Tue, 31 Dec 2013 10:23:39 -0800 (PST) Received: by 10.217.114.10 with HTTP; Tue, 31 Dec 2013 10:23:39 -0800 (PST) In-Reply-To: <20131229032733.GX99167@funkthat.com> References: <20131229015842.GC98282@cicely7.cicely.de> <20131229032733.GX99167@funkthat.com> Date: Tue, 31 Dec 2013 19:23:39 +0100 Message-ID: Subject: Re: AVILA NFS problem ? From: Berislav Purgar To: ticso@cicely.de, Berislav Purgar , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Dec 2013 18:23:42 -0000 On Sun, Dec 29, 2013 at 4:27 AM, John-Mark Gurney wrote: > Bernd Walter wrote this message on Sun, Dec 29, 2013 at 02:58 +0100: > > On Sat, Dec 28, 2013 at 01:59:49PM +0100, Berislav Purgar wrote: > > > Hello .. > > > I have problem with NFS on current. > > > > > > Timecounters tick every 10.000 msec > > > > > > ada0 at ata0 bus 0 scbus0 target 0 lun 0 > > > > > > ada0: CFA-0 device > > > > > > ada0: Serial Number 3ME3GRCZ > > > > > > ada0: 16.700MB/s transfers (PIO4, PIO 8192bytes) > > > > > > ada0: 3906MB (7999488 512 byte sectors: 16H 63S/T 7936C) > > > > > > ada0: Previously was known as ad0 > > > > > > bootpc_init: wired to interface 'npe1' > > > > > > Sending DHCP Discover packet from interface npe1 (00:d0:12:13:59:23) > > > > > > Received DHCP Offer packet on npe1 from 10.42.1.1 (accepted) > > > > > > npe1: link state changed to DOWN > > > > > > Sending DHCP Request packet from interface npe1 (00:d0:12:13:59:23) > > > > > > Received DHCP Ack packet on npe1 from 10.42.1.1 (accepted) (got root > path) > > > > > > npe1 at 10.42.1.15 server 10.42.1.1 boot file kernel-avila.nfs > > > > > > subnet mask 255.255.255.0 rootfs 10.42.1.1:/data/freebsd/gateworks > rootopts > > > nol > > > Adjusted interface npe1 > > > > > > krpc_call: sosend: 65 > > > > > > krpc_call: sosend: 65 > > > > > > panic: nfs_boot: mount root, error=65 > > > > > > KDB: enter: panic > > > > > > [ thread pid 0 tid 100000 ] > > > > > > Stopped at kdb_enter+0x48: ldrb r15, [r15, r15, ror r15]! > > > > EHOSTUNREACH 65 /* No route to host */ > > But I fail to see anything wrong in the setup. > > 10.42.1.1 should be reachable by 10.42.1.15/24 and network can't > > be down (AFAIK ARP timeout results in EHOSTUNREACH) since you've got > > a DHCP config, even from the same server. > > No idea, but I'm not familar with the AVILA or similar. > > Could you watch the link on the device? > > I have a different AVILA board that is VERY slow to link. If I try > to netboot from a u-boot script, or type the load command to early > it just fails... It could be that we are simply not waiting long > enough for the PHY to reestablish itself after reiniting the ethernet > device... > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > Hello Problem solved .. It was problem with PHY address of npe0 or 1 device.. Beri