From owner-freebsd-stable Tue Jun 20 2:42:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id E7B6A37BDE6 for ; Tue, 20 Jun 2000 02:42:27 -0700 (PDT) (envelope-from cj@hermite.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.10.2/2000060800) with ESMTP id LAA29843 for ; Tue, 20 Jun 2000 11:42:25 +0200 (CEST) Received: from hermite.cs.uni-sb.de (hermite.cs.uni-sb.de [134.96.247.171]) by cs.uni-sb.de (8.10.2/2000060800) with ESMTP id LAA03441; Tue, 20 Jun 2000 11:42:23 +0200 (CEST) Received: (from cj@localhost) by hermite.cs.uni-sb.de (8.9.3/8.9.3) id LAA13165; Tue, 20 Jun 2000 11:42:23 +0200 (CEST) (envelope-from cj) From: Christian Jacobi MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14671.15487.626878.801924@hermite.cs.uni-sb.de> Date: Tue, 20 Jun 2000 11:42:23 +0200 (CEST) To: hirbli@hermite.cs.uni-sb.de, cj@hermite.cs.uni-sb.de, freebsd-stable@freebsd.org Subject: Problems with vr X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, we have some problems on two machines running freebsd 4.0 with DLINK DFE-530TX. The problem on both machines is, that the vr0 hangs (no network traffic) after heavy network load (see messages output below). Often, the problem can be solved by ifconfig vr0 up, but sometimes even this does not help. Configurations of the machines: =============================== Both machines are Athlons 650, 256MB, Asus K7M 1.04 The first machine runs 4.0-RELEASE and a generic kernel. The machine is connected to a switch, 100 MBit full-duplex. Jun 20 11:24:03 goedel /kernel: chip1: at device 4.4 on pci0 Jun 20 11:24:03 goedel /kernel: vr0: port 0xd000-0xd07f mem 0xefffff80-0xefffffff irq 9 at device 14.0 on pci0 Jun 20 11:24:03 goedel /kernel: vr0: Ethernet address: 00:50:ba:08:4e:53 Jun 20 11:24:03 goedel /kernel: miibus0: on vr0 Jun 20 11:24:03 goedel /kernel: amphy0: on miibus0 Jun 20 11:24:03 goedel /kernel: amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jun 20 11:24:03 goedel /kernel: vr0: supplying EUI64: 00:50:ba:ff:fe:08:4e:53 Jun 19 19:19:22 goedel /kernel: vr0: promiscuous mode enabled Jun 19 19:19:44 goedel /kernel: vr0: no memory for tx list Jun 19 19:19:52 goedel last message repeated 12 times Jun 19 19:20:20 goedel /kernel: vr0: promiscuous mode disabled Jun 19 19:20:37 goedel /kernel: vr0: no memory for tx list Jun 19 19:20:44 goedel last message repeated 7 times Jun 19 19:22:17 goedel last message repeated 8 times ===================================================== The second machine runs 4.0-STABLE (2000-05-25) and a custom kernel. It is connected to a hub, 100 MBit half-duplex. Jun 8 14:05:30 hermite /kernel: vr0: port 0xc400-0xc47f mem 0xefffff80-0xefffffff irq 5 at device 14.0 on pci0 Jun 8 14:05:30 hermite /kernel: vr0: Ethernet address: 00:50:ba:08:46:01 Jun 8 14:05:30 hermite /kernel: miibus0: on vr0 Jun 8 14:05:30 hermite /kernel: amphy0: on miibus0 Jun 8 14:05:30 hermite /kernel: amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto May 26 19:15:38 hermite /kernel: vr0: watchdog timeout Has anyone seen similar behaviour? Any hints? Greetings, Chris -- ---------------------------------------------------------------- FB 14 - Informatik Christian Jacobi Im Stadtwald Computer Science Department D-66041 Saarbruecken University of Saarland Germany Phone: (+49) 681 3024490 Fax: (+49) 681 3024290 ---------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message