AVILA NFS problem ?

[Adrian Chadd]

Can you be more clearer?


-a


On 31 December 2013 10:23, Berislav Purgar <bpurgar at gmail.com> wrote:
> On Sun, Dec 29, 2013 at 4:27 AM, John-Mark Gurney <jmg at funkthat.com> 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: <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
>> > >
>> > > 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
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"