From owner-freebsd-current Sun May 7 2:14:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4D91537B671; Sun, 7 May 2000 02:14:41 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA57107; Sun, 7 May 2000 18:44:39 +0930 (CST) Date: Sun, 7 May 2000 18:44:39 +0930 From: Greg Lehey To: FreeBSD Committers , FreeBSD current users Subject: ed driver broken in today's -CURRENT? Message-ID: <20000507184439.H55316@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just built a new kernel, based on a cvsup at 2030 UTC on 6 May, and since then *some* Ethernet transactions don't work. I've checked that it's not just a dead card: the previous kernel works fine. I have the funny situation that I can send fine, and I can traceroute to the box, but I can't ping. NFS also objects strenuously: 18:36:47.508811 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:36:47.508946 freebie.lemis.com > panic.lemis.com: icmp: echo reply 18:36:48.512540 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:36:48.512669 freebie.lemis.com > panic.lemis.com: icmp: echo reply 18:36:49.522568 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:36:49.522691 freebie.lemis.com > panic.lemis.com: icmp: echo reply 18:36:50.532531 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:36:50.532664 freebie.lemis.com > panic.lemis.com: icmp: echo reply 18:36:51.542504 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:36:51.542636 freebie.lemis.com > panic.lemis.com: icmp: echo reply The above all looks good, but panic doesn't see the reply. 18:36:58.933420 freebie.lemis.com > panic.lemis.com: icmp: echo request 18:36:59.953879 freebie.lemis.com > panic.lemis.com: icmp: echo request 18:37:00.973929 freebie.lemis.com > panic.lemis.com: icmp: echo request 18:37:01.993996 freebie.lemis.com > panic.lemis.com: icmp: echo request 18:37:03.014053 freebie.lemis.com > panic.lemis.com: icmp: echo request 18:37:04.034119 freebie.lemis.com > panic.lemis.com: icmp: echo request panic seems to see nothing. 18:37:07.857977 freebie.lemis.com.57058 > panic.lemis.com.33435: udp 12 [ttl 1] 18:37:07.858318 panic.lemis.com > freebie.lemis.com: icmp: panic.lemis.com udp port 33435 unreachable 18:37:07.860258 freebie.lemis.com.57058 > panic.lemis.com.33436: udp 12 [ttl 1] 18:37:07.860584 panic.lemis.com > freebie.lemis.com: icmp: panic.lemis.com udp port 33436 unreachable 18:37:07.861455 freebie.lemis.com.57058 > panic.lemis.com.33437: udp 12 [ttl 1] 18:37:07.861767 panic.lemis.com > freebie.lemis.com: icmp: panic.lemis.com udp port 33437 unreachable This works fine! With the same kernel. After rebooting a kernel of a few days ago, panic can ping just fine: 18:39:17.258545 arp who-has panic.lemis.com tell panic.lemis.com 18:39:22.034446 arp who-has freebie.lemis.com tell panic.lemis.com 18:39:22.034543 arp reply freebie.lemis.com is-at 0:80:ad:b7:c9:c7 18:39:22.034875 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:39:22.034994 freebie.lemis.com > panic.lemis.com: icmp: echo reply 18:39:23.040705 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:39:23.040837 freebie.lemis.com > panic.lemis.com: icmp: echo reply 18:39:24.050692 panic.lemis.com > freebie.lemis.com: icmp: echo request 18:39:24.050815 freebie.lemis.com > panic.lemis.com: icmp: echo reply This is a Compex PCI-based NE2000 lookalike. It's on irq 3 (alone). Who gets the pointy hat? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message