From owner-freebsd-current@FreeBSD.ORG Tue Dec 31 18:29:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BE72A05 for ; Tue, 31 Dec 2013 18:29:51 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D79021647 for ; Tue, 31 Dec 2013 18:29:50 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id z12so11081040wgg.3 for ; Tue, 31 Dec 2013 10:29:49 -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 :cc:content-type; bh=v2fR/sf+/2FhbfEnB/68AxU1rIEHy6qmfNGJEACT5Ko=; b=dHBluJxf79SVI2vUQlUrY/8ZBNrrvFwi6MhFOisACSVFL4Kj3lgtP5tcrhEdWnnR40 Te9qv6pVvwWLMmk6etH0wJ4rsCBMOY/P2ShoBAEU3vCi59IoANgJbupJmW91Ii/c4sMn t5G4fRg6iFHnwQ+MOq0VDZ2BmgcjcVf7agT7zTcXzHuNqhlZoKavqTre1gNzsZ76oMnT hX3OFREhUjcXc/xf6hmyF0cT/7Y9rzhdxrc7uu4HqGoO1GyqwBc5aNy8cXmVcQ+iuqPj ckE0+k0zdjpbqfpumuFkK+FDh6J235K2cWaBKfya2IIy2mvvqAciA6dQQR6bvrpt+BI3 Sc9w== MIME-Version: 1.0 X-Received: by 10.194.77.106 with SMTP id r10mr578041wjw.91.1388514589141; Tue, 31 Dec 2013 10:29:49 -0800 (PST) Received: by 10.217.114.10 with HTTP; Tue, 31 Dec 2013 10:29:49 -0800 (PST) In-Reply-To: <32489914.1893157.1388179282164.JavaMail.root@uoguelph.ca> References: <32489914.1893157.1388179282164.JavaMail.root@uoguelph.ca> Date: Tue, 31 Dec 2013 19:29:49 +0100 Message-ID: Subject: Re: NFS - arm/AVILA problem From: Berislav Purgar To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Dec 2013 18:29:51 -0000 On Fri, Dec 27, 2013 at 10:21 PM, Rick Macklem wrote: > 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 > > > Well, 65 is EHOSTUNREACH, but since they appear to be on the same subnet, > I don't know why the sosend() into the socket layer would reply that. > > I'd say it is related to network configuration (or how DHCP is setting > up the net interface) and is not really an NFS problem. (ie. The sosend() > of an RPC request is failing. NFS can't do anything if packets can't > be sent to the server.) > > You might want to re-post with a subject line mentioning EHOSTUNREACH > errors from sosend() after DHCP sets up the interface. (And you might > want to post to an ARM related list, because I suspect it might be > ARM specific?) > > rick > > Hello problem solved .. it was invalid PHY address od npe0/1 device .. Beri