From nobody@FreeBSD.ORG Sun Jan 2 05:14:57 2000 Return-Path: Received: by hub.freebsd.org (Postfix, from userid 32767) id 768FC14BCC; Sun, 2 Jan 2000 05:14:55 -0800 (PST) Message-Id: <20000102131455.768FC14BCC@hub.freebsd.org> Date: Sun, 2 Jan 2000 05:14:55 -0800 (PST) From: riccardo@torrini.org Sender: nobody@FreeBSD.ORG To: freebsd-gnats-submit@freebsd.org Subject: NIC: ex0: Intel EtherExpress Pro/10 stopped working X-Send-Pr-Version: www-1.0 >Number: 15837 >Category: kern >Synopsis: NIC: ex0: Intel EtherExpress Pro/10 stopped working >Confidential: no >Severity: critical >Priority: high >Responsible: mdodd >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 2 05:20:01 PST 2000 >Closed-Date: Sat Jul 21 23:10:11 PDT 2001 >Last-Modified: Sat Jul 21 23:11:24 PDT 2001 >Originator: Riccardo Torrini >Release: 4.0-CURRENT (make world on 31/12/1999) >Organization: >Environment: FreeBSD trudy.home.torrini.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 2 11:46:11 CET 2000 root@trudy.home.torrini.org:/usr/src/sys/compile/TRUDY i386 >Description: Intel EtherExpress Pro/10 does'n work on last month, on last 4 cvsup and make world (it was over than one year that works. It is well configured. The cable (RG58) is ok and correctly terminated. On the same machine win*** can use tcp/ip to connect to my Amiga. I cannot ping/telnet/ftp neither to nor from FreeBSD. I tryed with tcpdump to follow what happens and noticed that nothing but arp go bidirectional (tcpdump does not see any packets coming from Amiga but send and receive arp requests, gotting also mac-address of Amiga side) My network: ; 192.168.22.1 tip # Amiga ; 192.168.22.2 tap # Amiga ; 192.168.22.3 trudy # FreeBSD/Win*** dual boot # netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire 127.0.0.1 127.0.0.1 UH lo0 192.168.22 link#1 UC ex0 => 192.168.22.3 0:aa:0:ad:44:7c UHLW lo0 # ping -c 42 tip PING tip (192.168.22.1): 56 data bytes --- tip ping statistics --- 42 packets transmitted, 0 packets received, 100% packet loss # ping -c 42 tip PING tip (192.168.22.1): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available [...omissis...] --- tip ping statistics --- 42 packets transmitted, 0 packets received, 100% packet loss # tcpdump -i ex0 tcpdump: listening on ex0 [...doing a "ping trudy" from Amiga side...] 13:51:36.071943 arp who-has trudy tell tip 13:51:37.072352 arp who-has trudy tell tip 13:51:38.072756 arp who-has trudy tell tip 13:51:39.073148 arp who-has trudy tell tip 13:51:40.073541 arp who-has trudy tell tip 13:51:41.074616 arp who-has trudy tell tip 13:51:42.075009 arp who-has trudy tell tip ^C 7 packets received by filter 0 packets dropped by kernel # netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire 127.0.0.1 127.0.0.1 UH lo0 192.168.22 link#1 UC ex0 => 192.168.22.1 0:60:30:0:20:c2 UHLW ex0 1187 192.168.22.3 0:aa:0:ad:44:7c UHLW lo0 As you can see only ARP WHO-HAS packets runs on my network and after ping (or telnet/ftp, no matter) mac-address of Amiga-side shows on routing tables of FreeBSD-side. Kernel configuration follows: # Network card (Intel EtherExpress Pro/10) device ex0 at isa? port 0x300 irq 10 Boot messages shows NIC configured: ex0 at port 0x300 irq 10 on isa0 ex0: Intel EtherExpress Pro/10, address 00:aa:00:ad:44:7c, connector TPE Ifconfig show board up and running: # ifconfig ex0 ex0: flags=c43 mtu 1500 inet 192.168.22.3 netmask 0xffffff00 broadcast 192.168.22.255 ether 00:aa:00:ad:44:7c I am not using TPE but BNC, but I don't think this is the problem because how ARP can reach other side if the problem was the wrong connector? BTW: the board is forced with dos-boot-floppy to be _NO_ plug-and-play, _STAY_ on irq#10 and on I/O 0x300, connector auto-swith. I tryed also with an hub for TPE a couple of hour with the same results: no ping, no telnet, to ftp, only arp using FreeBSD 4.0-CURRENT, correct operation even with TPE using win*** :-( >How-To-Repeat: Buy an Intel EtherExpress Pro/10, install it on a 4.0-CURRENT :-( >Fix: Install 3.3-STABLE, 3.4-RC. With those release (on another machine) no problems found with the same NIC. >Release-Note: >Audit-Trail: From: "Matthew N. Dodd" To: riccardo@torrini.org Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/15837: NIC: ex0: Intel EtherExpress Pro/10 stopped working Date: Sun, 2 Jan 2000 17:23:54 -0500 (EST) On Sun, 2 Jan 2000 riccardo@torrini.org wrote: > >How-To-Repeat: > Buy an Intel EtherExpress Pro/10, install it on a 4.0-CURRENT :-( Someone was going to ship me one but I haven't seen it yet. :/ -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | State-Changed-From-To: open->feedback State-Changed-By: mdodd State-Changed-When: Wed Jan 12 23:34:44 PST 2000 State-Changed-Why: Fixes applied to -CURRENT. Does this solve the observed problem? Responsible-Changed-From-To: freebsd-bugs->mdodd Responsible-Changed-By: mdodd Responsible-Changed-When: Tue Jul 18 00:28:41 PDT 2000 Responsible-Changed-Why: 'ex' seems to be my problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=15837 From: Riccardo Torrini To: freebsd-gnats-submit@FreeBSD.org, riccardo@torrini.org Cc: Subject: Re: kern/15837: NIC: ex0: Intel EtherExpress Pro/10 stopped working Date: Mon, 11 Sep 2000 17:47:48 +0200 (METDST) I'm sorry for the delay but I forgot to reply to followup :-( After changes to -CURRENT of jan.2000 NIC worked again, thanks. You may consider PR kern/15837 closed. In the mean time I switched to 5.0-CURRENT =8-> Ciao, Riccardo. State-Changed-From-To: feedback->closed State-Changed-By: brooks State-Changed-When: Sat Jul 21 23:10:11 PDT 2001 State-Changed-Why: Originator says problem fixed. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15837 >Unformatted: