Re: NFS - arm/AVILA problem

On Fri, Dec 27, 2013 at 10:21 PM, Rick Macklem <rmacklem_at_uoguelph.ca> 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: <ST640211CF 3.07> 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