So this is new. When I rebooted to check the boot process, it took the IP address immediately, started loading Uboot, but restarted around block 162. Wireshark shows multiple packets of the same number being send and acknowledged.
Yes, I'm using dnsmasq. U-Boot 2008.10-svn3231 (Jul 15 2010 - 14:58:38) CPU: AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133, OPB=66, EBC=66 MHz) No Security/Kasumi support Bootstrap Option C - Boot ROM Location EBC (16 bits) 32 kB I-Cache 32 kB D-Cache Board: Roach I2C: ready DTT: 1 is 27 C DRAM: (spd v1.2) dram: notice: ecc ignored 1 GB FLASH: 64 MB USB: Host(int phy) Device(ext phy) Net: ppc_4xx_eth0 Roach Information Serial Number: 030191 Monitor Revision: 8.3.1698 CPLD Revision: 8.0.1588 type run netboot to boot via dhcp+tftp+nfs type run soloboot to run from flash without network type run mmcboot to boot using filesystem on mmc/sdcard type run usbboot to boot using filesystem on usb type run bit to run tests Hit any key to stop autoboot: 2 \0x08\0x08\0x08 0 => run netboot Waiting for PHY auto negotiation to complete.. done ENET Speed is 100 Mbps - FULL duplex connection (EMAC0) BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.100.50 Using ppc_4xx_eth0 device TFTP from server 192.168.40.1; our IP address is 192.168.100.50 Filename 'uImage'. Load address: 0x400000 Loading: *\0x08###T T T #T ##T T ####T #T ##T T # Retry count exceeded; starting again BOOTP broadcast 1 DHCP client bound to address 192.168.100.50 Using ppc_4xx_eth0 device TFTP from server 192.168.40.1; our IP address is 192.168.100.50 Filename 'uImage'. Load address: 0x400000 Loading: *\0x08####T T T #T #T T T T T T Retry count exceeded; starting again BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 DHCP client bound to address 192.168.100.50 Using ppc_4xx_eth0 device TFTP from server 192.168.40.1; our IP address is 192.168.100.50 Filename 'uImage'. Load address: 0x400000 Loading: *\0x08##T #T T T Brad Dober Ph.D. Candidate Department of Physics and Astronomy University of Pennsylvania Cell: 262-949-4668 On Tue, May 26, 2015 at 11:17 PM, David MacMahon <dav...@astro.berkeley.edu> wrote: > Nothing obvious comes to mind (yet). Can you watch the roach1 boot > process via serial console? What does that show? Are you using dnsmasq > for the DHCP server? What if you try direct connect with mii-tool to set > the speed of eth1 to 100 Mbps? > > Dave > > On May 26, 2015, at 5:00 PM, Brad Dober wrote: > > > Hi Dave, > > > > Here is the configuration of the network. The host computer, a ROACH1 > and a working ROACH2 running in soloboot are the only ones connected. The > host is 192.168.40.1 and is offering 192.168.100.50 and the ROACH2 is > assigned to 192.168.40.50. Is there anything weird about how the ROACH1 > handles larger subnets like below? Or maybe infinite address leases? > > > > eth1 Link encap:Ethernet HWaddr 00:08:54:54:d3:f5 > > inet addr:192.168.40.1 Bcast:192.168.255.255 Mask:255.255.0.0 > > inet6 addr: fe80::208:54ff:fe54:d3f5/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:705 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1377 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:210574 (210.5 KB) TX bytes:302407 (302.4 KB) > > Interrupt:20 Base address:0x6000 > > > > Here is the tcpdump: > > > > tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size > 65535 bytes > > 19:46:49.968388 02:00:00:03:01:91 > ff:ff:ff:ff:ff:ff, ethertype IPv4 > (0x0800), length 343: (tos 0x0, ttl 255, id 225, offset 0, flags [DF], > proto UDP (17), length 329) > > 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from > 02:00:00:03:01:91, length 301, xid 0x144252, secs 1130, Flags [none] > > Client-Ethernet-Address 02:00:00:03:01:91 > > Vendor-rfc1048 Extensions > > Magic Cookie 0x63825363 > > DHCP-Message Option 53, length 1: Discover > > MSZ Option 57, length 2: 576 > > Parameter-Request Option 55, length 5: > > Subnet-Mask, Default-Gateway, Hostname, BS > > RP > > 19:46:49.968953 00:08:54:54:d3:f5 > 02:00:00:03:01:91, ethertype IPv4 > (0x0800), length 349: (tos 0x0, ttl 64, id 33388, offset 0, flags [none], > proto UDP (17), length 335) > > 192.168.40.1.67 > 192.168.100.50.68: BOOTP/DHCP, Reply, length 307, > xid 0x144252, secs 1130, Flags [none] > > Your-IP 192.168.100.50 > > Server-IP 192.168.40.1 > > Client-Ethernet-Address 02:00:00:03:01:91 > > file "uImage" > > Vendor-rfc1048 Extensions > > Magic Cookie 0x63825363 > > DHCP-Message Option 53, length 1: Offer > > Server-ID Option 54, length 4: 192.168.40.1 > > Lease-Time Option 51, length 4: 4294967295 > > Subnet-Mask Option 1, length 4: 255.255.0.0 > > Hostname Option 12, length 8: "roach1-4" > > RP Option 17, length 33: "192.168.40.1:/srv/roach_boot/etch" > > 19:46:52.971116 02:00:00:03:01:91 > ff:ff:ff:ff:ff:ff, ethertype IPv4 > (0x0800), length 343: (tos 0x0, ttl 255, id 226, offset 0, flags [DF], > proto UDP (17), length 329) > > 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from > 02:00:00:03:01:91, length 301, xid 0x144e0d, secs 1133, Flags [none] > > Client-Ethernet-Address 02:00:00:03:01:91 > > Vendor-rfc1048 Extensions > > Magic Cookie 0x63825363 > > DHCP-Message Option 53, length 1: Discover > > MSZ Option 57, length 2: 576 > > Parameter-Request Option 55, length 5: > > Subnet-Mask, Default-Gateway, Hostname, BS > > RP > > 19:46:52.971744 00:08:54:54:d3:f5 > 02:00:00:03:01:91, ethertype IPv4 > (0x0800), length 349: (tos 0x0, ttl 64, id 34083, offset 0, flags [none], > proto UDP (17), length 335) > > 192.168.40.1.67 > 192.168.100.50.68: BOOTP/DHCP, Reply, length 307, > xid 0x144e0d, secs 1133, Flags [none] > > Your-IP 192.168.100.50 > > Server-IP 192.168.40.1 > > Client-Ethernet-Address 02:00:00:03:01:91 > > file "uImage" > > Vendor-rfc1048 Extensions > > Magic Cookie 0x63825363 > > DHCP-Message Option 53, length 1: Offer > > Server-ID Option 54, length 4: 192.168.40.1 > > Lease-Time Option 51, length 4: 4294967295 > > Subnet-Mask Option 1, length 4: 255.255.0.0 > > Hostname Option 12, length 8: "roach1-4" > > RP Option 17, length 33: "192.168.40.1:/srv/roach_boot/etch" > > > > > > Brad Dober > > Ph.D. Candidate > > Department of Physics and Astronomy > > University of Pennsylvania > > Cell: 262-949-4668 > > > > On Tue, May 26, 2015 at 7:42 PM, David MacMahon < > dav...@astro.berkeley.edu> wrote: > > Weird. Are there any other hosts on the network that might be also > sending (non-netboot-aware) DHCP offers? > > > > What does "sudo tcpdump -i eth0 -n -e -v port bootps or port bootpc" > show (replacing eth0 with the actual network interface name where the DHCP > activity is). > > > > Dave > > > > On May 26, 2015, at 4:34 PM, Brad Dober wrote: > > > > > Hi Dave, > > > > > > I switched to a 100 Mbps switch, and now I'm still getting the ROACH1 > continuously sending DCHP discovers, and my host computer continuously > sending offers, but now the occasional request/acknowledge and uboot > download is no longer happening. > > > > > > For what it's worth, I am not using jumbo frames. > > > > > > > > > Brad Dober > > > Ph.D. Candidate > > > Department of Physics and Astronomy > > > University of Pennsylvania > > > Cell: 262-949-4668 > > > > > > On Tue, May 26, 2015 at 7:21 PM, David MacMahon < > dav...@astro.berkeley.edu> wrote: > > > Are you trying to run the ROACH1 on 1 GbE? ROACH1 is not reliable on > 1 GbE. You have to force it to be 100 Mbps. This can be done by using an > unmanaged non-gigabit switch (or hub), a managed switch that can force its > port for the ROACH1 to be 100 Mbsp only. For direct connect, you'll have > to use "mii-tool" on the server. > > > > > > Another thing that always gets me is MTU. I don't think the ROACH1 > u-boot supports jumbo frames, so you'll have to run the server with > MTU==1500 to netboot ROACH1. > > > > > > Dave > > > > > > On May 26, 2015, at 3:51 PM, Brad Dober wrote: > > > > > > > I've switched to NFS boot to avoid SD card corruptions. > > > > > > > > However, when attempting to run netboot, the roach will send an IP > discover, the host will offer one, and then the roach will send a discover > again. > > > > This goes on for 10-15 times when finally the roach will request the > correct IP, and the host will acknowledge. The roach will then begin the > tftp of the uboot image, but will request block 1 multiple times, gets sent > it, acknowledges once starts getting block 1 and 2 sent and then restarts > the whole process asking for an IP request. > > > > > > > > The whole process seems very strange and I'm having trouble wrapping > my head around what could be causing it. > > > > > > > > Has anyone encountered something similar??? > > > > > > > > > > > > Brad Dober > > > > Ph.D. Candidate > > > > Department of Physics and Astronomy > > > > University of Pennsylvania > > > > Cell: 262-949-4668 > > > > > > > > On Thu, May 21, 2015 at 3:32 AM, Marc Welz <m...@ska.ac.za> wrote: > > > > > > > > > > > > On Wed, May 20, 2015 at 5:19 PM, Brad Dober <do...@sas.upenn.edu> > wrote: > > > > Hi Casperites, > > > > > > > > I have a Roach1 which is booting from an SD card. > > > > I booted it up yesterday, and it was displaying the "STALE NFS > handle" error that other people have seen in the past (which suggested a > corrupt flash card). I ran fsck and fixed several errors, and when > rebooting, the stale nfs handle error went away. However, now the ROACH > could not connect to the network. > > > > > > > > When I run "ifconfig 128.91.46.20 netmask 255.255.248.0 gateway > 128.91.4", I get: > > > > "gateway: Host name lookup failure" > > > > > > > > root@(none):~# hostname -v > > > > (none) > > > > > > > > If you require a hostname, put it in /etc/hostname or similar and > then run > > > > > > > > hostname -f /etc/hostname > > > > > > > > regards > > > > > > > > marc > > > > > > > > > > > > > > > > > > > > > > > >
