From owner-freebsd-hackers Sat Mar 25 12:54:02 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA09133 for hackers-outgoing; Sat, 25 Mar 1995 12:54:02 -0800 Received: from vmbb.cts.com (vmbb.cts.com [192.188.72.18]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA09127 for ; Sat, 25 Mar 1995 12:54:01 -0800 Received: from io.cts.com by vmbb.cts.com with smtp (Smail3.1.28.1 #9) id m0rscqK-0000JeC; Sat, 25 Mar 95 12:53 PST Received: (from root@localhost) by io.cts.com (8.6.11/8.6.9) id MAA00179 for hackers@freebsd.org; Sat, 25 Mar 1995 12:53:22 -0800 From: Morgan Davis Message-Id: <199503252053.MAA00179@io.cts.com> Subject: ed1: device timeout on -current? To: hackers@FreeBSD.org Date: Sat, 25 Mar 1995 12:53:22 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 494 Sender: hackers-owner@FreeBSD.org Precedence: bulk 3/25 -current, NE1000 (used to work on 3/18 -current): Probing for devices on the ISA bus: ... ed1 at 0x300-0x31f irq 9 on isa ed1: address 00:00:1b:25:57:70, type NE1000 (8 bit) ... So far so good, but then later after all devices probed: ed1: device timeout ed1: device timeout Machines on the LAN are not reachable unless I watch netstat and wait for the timeouts. Then they're up and pingable. Is this some kind of cached carry over from the reboot after I installed 3/25 -current?