Date: Tue, 31 Dec 2013 14:18:03 -0800 From: Berislav Purgar <bpurgar@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, "ticso@cicely.de" <ticso@cicely.de> Subject: RE: AVILA NFS problem ? Message-ID: <1504801126410582043@unknownmsgid>
next in thread | raw e-mail | index | archive | help
Yes... Default avila.hints configure phy 0 for npe0 and npe1 phy 1 and that work with gw-2348 board (i think). But i have gw-2345-F board which have 4 lan and one wan port. Wan port is attached to PHY 5 and lan ports are attached to switch chip KS8995. We dont have driver for this chip so i figured that if i put 2 for PHY port 2 works on switch. So i forget to change these in avila.hints and that reproduce kernel panic on nfs boot.. Beri Sent from my Windows Phone From: Adrian Chadd Sent: 12/31/2013 19:35 To: Berislav Purgar Cc: ticso@cicely.de; freebsd-arm@freebsd.org Subject: Re: AVILA NFS problem ? Can you be more clearer? -a On 31 December 2013 10:23, Berislav Purgar <bpurgar@gmail.com> wrote: > On Sun, Dec 29, 2013 at 4:27 AM, John-Mark Gurney <jmg@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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1504801126410582043>