From owner-freebsd-current@FreeBSD.ORG Thu May 20 12:05:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33DB416A4CF for ; Thu, 20 May 2004 12:05:41 -0700 (PDT) Received: from enigma.whacky.net (enigma.whacky.net [217.148.161.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D91243D1D for ; Thu, 20 May 2004 12:05:40 -0700 (PDT) (envelope-from stephanb@whacky.net) Received: from localhost (localhost.whacky.net [127.0.0.1]) by enigma.whacky.net (Postfix) with ESMTP id 05BBE20F37 for ; Thu, 20 May 2004 21:05:29 +0200 (CEST) Received: from enigma.whacky.net ([127.0.0.1]) by localhost (enigma.whacky.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 47440-07 for ; Thu, 20 May 2004 21:05:24 +0200 (CEST) Received: by enigma.whacky.net (Postfix, from userid 1000) id 4014120F29; Thu, 20 May 2004 21:05:24 +0200 (CEST) Date: Thu, 20 May 2004 21:05:23 +0200 From: Stephan van Beerschoten To: freebsd-current@freebsd.org Message-ID: <20040520190523.GA48603@enigma.whacky.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at whacky.net Subject: ethernet watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2004 19:05:41 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm reading all these mails online about network interfaces hanging with 'w= atchdog timeout' messages. I myself have the same problem with 5.2.1-RELEASE-p6 on a faily old laptop = (p2-266/32MB ram) that I use as a small DMZ server at home. I have not however read any reply on any of these cry-for-helps with any us= efull info. I does not seem to happen when I run my system with a wi0 card. Currently t= his happends when I run it with a 3com cardbus adapter: xl0: <3Com 3c575C Fast Etherlink XL> port 0x1080-0x10ff mem 0x88000000-0x88= 00007f,0x88000080-0x880000ff irq 11 at device 0.0 on cardbus0 xl0: Ethernet address: 00:50:da:d9:d4:dc miibus0: on xl0 tdkphy0: on miibus0 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto FreeBSD dmz.whacky.net 5.2.1-RELEASE-p6 FreeBSD 5.2.1-RELEASE-p6 #0: Wed Ma= y 19 04:55:50 CEST 2004 root@dmz.whacky.net:/usr/obj/usr/src/sys/GENERI= C i386 The laptop runs, and then after a slight increase in the network load, it l= ocks up: May 20 14:53:49 dmz kernel: xl0: watchdog timeout I would love to get some debugging going on on this problem, but I never ha= d the pleasure to do so, so I would need some help. But then again, I am no= t the only one with this problem so I'm genuinly hoping somebody has at lea= st a workaround for this problem yet. Thanks, /Stephan --=20 Stephan van Beerschoten [KeyID: 0x08F12864] "If you are adminstering UNIX systems and don't master tools such as make, shell, and perl, then you are working too hard." -- Wietse Venema. Fri, 12 Dec 2003 --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFArQFzJliZ6wjxKGQRArgGAKCuRve4kee7Qz3xltA1h2UjtBO06wCfSKuu P0oLeEPIiCjgKZrl9mhrNvQ= =tolw -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5--