Linux 2.1.107, bootp and Miatas
Tramm Hudson
tbhudso@cs.sandia.gov
Tue Jul 7 09:50:50 1998
Tulip folks,
I have a rather specialized cluster of diskless DEC Miata's that
boot via bootp over a 100baseT network and mount their root filesystem
over NFS. We were running Linux 2.0.34 with Tulip 0.83 and have not
had any problems with the network drivers under that configuration.
I'm working to upgrade the system to Linux 2.1.x and have run into
several problems with the boot process. The bootprom retrieves the
kernel via bootp and starts it, follwed by the kernel sending another
bootp request for its IP address and root file system parameters.
The latest driver (0.89H) does not send any packets on the wire when
it says that it is broadcasting the bootp/rarp request. I've confirmed
that no packets are send with a packet sniffer.
Since we have had problems with the 21143 chips before, I went ahead
and downgraded the driver to 0.83. This is the last driver that we have
had work with our Miatas. Packets are properly sent, but do not appear
to be received. The bootp server acknowledges the request and sends its
response, but the client eventually just times out, never seeing the
answering packets. Again, I've confirmed that the bootp request and
response are both on the wire with a sniffer.
Here is the relevant portions of the boot log. Note that I have
turned TULIP_DEBUG up to 9 and also configured IPCONFIG_DEBUG on.
> ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.CPU 0 speed is 2.31 ns (433MHz)
>
> ef.ee.ed.ec.eb.f4.ea.e9.e8.e7.e6.e5.e4.
> Digital Personal WorkStation 433au Console V6.7-196
> built on Jan 22 1998 at 16:18:43
>
> CPU 0 booting
>
> (boot ewa0.0.0.3.0 -flags root=/dev/nfs)
>
> Trying BOOTP boot.
>
> Broadcasting BOOTP Request...
> Received BOOTP Packet File Name is: /cplant/kernels/vmlinux.th
> local inet address: 172.16.1.3
> remote inet address: 172.16.1.254
> TFTP Read File Name: /cplant/kernels/vmlinux.th
> netmask = 255.255.0.0
> Server is on same subnet as client.
> .........................
> bootstrap code read in
> base = 1f2000, image_start = 0, image_bytes = 1862d8
> initializing HWRPB at 2000
> initializing page table at 1e4000
> initializing machine state
> setting affinity to the primary CPU
> jumping to bootstrap code
> Linux/AXP bootp loader for Linux 2.1.107
> Switching to OSF PAL-code .. Ok (rev 1000000020116)
> Loading the kernel...'root=/dev/nfs'
> Linux version 2.1.107 (root@cplant-sss0.cs.sandia.gov) (gcc version 2.7.2.3) #40 SMP Mon Jul 6 17:11:41 MDT 1998
> Command line: root=/dev/nfs
> setup_smp: 1 CPUs probed, cpu_present_map 0x1, boot_cpu_id 0
> Calibrating delay loop... 428.87 BogoMIPS
> Memory: 190872k available
> POSIX conformance testing by UNIFIX
> smp_boot_cpus: Entering SMP Mode...
> Swansea University Computer Society NET3.039 for Linux 2.1
> NET3: Unix domain sockets 0.16 for Linux NET3.038.
> Swansea University Computer Society TCP/IP for NET3.037
> IP Protocols: ICMP, UDP, TCP
> Alpha PCI BIOS32 revision 0.04
> PCI: Probing PCI hardware
> Starting kswapd v 1.5
> Serial driver version 4.26 with no serial options enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> RAM disk driver initialized: 16 RAM disks of 4096K size
> loop: registered device at major 7
> Floppy drive(s): fd0 is 2.88M
> FDC 0 is a National Semiconductor PC87306
> tulip.c:v0.83 10/19/97 becker@cesdis.gsfc.nasa.gov
> eth0: Digital DS21142/3 Tulip at 0x8000, 00 00 f8 75 77 b0, IRQ 24.
> eth0: EEPROM default media type Autosense.
> eth0: Index #0 - Media 10baseT (#0) described by a 21142 non-MII PHY (2) block.
> eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 non-MII PHY (2) block.
> eth0: Index #2 - Media 10base2 (#1) described by a 21142 non-MII PHY (2) block.
> eth0: Index #3 - Media AUI (#2) described by a 21142 non-MII PHY (2) block.
> eth0: MII interface PHY 0, setup/reset sequences 2/0 long, capabilities 00 f0.
> eth0: Index #4 - Media MII (#11) described by a 21142 MII PHY (3) block.
> eth0: MII transceiver found at MDIO address 5.
> PCI latency timer (CFLT) is 0xff.
> IP-Config: Entered.
> IP-Config: Opened eth0
> BOOTP: XID=2372a18f
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> Sending BOOTP and RARP requests... timeout=5255
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf06f0004 new csr5=0xf06e0000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf06f0004 new csr5=0xf06e0000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf06f0004 new csr5=0xf06e0000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf06f0005 new csr5=0xf06e0000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf06f0004 new csr5=0xf06e0000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf0670044 new csr5=0xf0660000.
> BOOTP: Route lookup: 1:00000000 -> 0:ffffffff: Output
> .<7>eth0: interrupt csr5=0xf06f0004 new csr5=0xf06e0000.
> timed out (too many tries)!
> IP-Config: Auto-configuration of network failed.
> IP-Config: Downing eth0
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Insert root floppy and press ENTER
Thanks!
--
o hudson@cs.tulane.edu tbhudso@cs.sandia.gov O___|
/|\ http://www.cs.tulane.edu/~hudson/ H 505.266.59.96 /\ \_
<< KC5RNF @ N5YYF.NM.AMPR.ORG W 505.284.24.32 \ \/\_\
0 U \_ |