From owner-freebsd-current@FreeBSD.ORG Fri Nov 21 12:29:52 2003 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 4344A16A4CE for ; Fri, 21 Nov 2003 12:29:52 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC35043FDF for ; Fri, 21 Nov 2003 12:29:50 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 07A2F66C8E; Fri, 21 Nov 2003 12:29:49 -0800 (PST) Date: Fri, 21 Nov 2003 12:29:49 -0800 From: Kris Kennaway To: Jimmy Selgen Message-ID: <20031121202949.GA5181@xor.obsecurity.org> References: <1069446169.15019.46.camel@janitor> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <1069446169.15019.46.camel@janitor> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: xl0: 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: Fri, 21 Nov 2003 20:29:52 -0000 X-List-Received-Date: Fri, 21 Nov 2003 20:29:52 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote: > Hi >=20 > I'm getting some strange xl0 timeout messages on 5.1-CURRENT (synced > today). >=20 > I've searched the archives, and it seems that this problem is related to > ACPI > (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D608457+0+archive/2003/fre= ebsd-current/20031109.freebsd-current) > Strange thing is that this worked perfectly with FreeBSD-5.1-RELEASE. >=20 > The NIC still works, just get "xl0: watchdog timeout" every now and > then. I saw this with some of sam's locking changes that (temporarily) broke DUMMYNET. I see you're using ipfilter - it's possible that this configuration has not been well-tested. Are you passing much traffic through ipfilter on this box? It would be helpful if you can do a binary search to narrow down when the problem started. Kris --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/vnW9Wry0BWjoQKURAp4XAJ9yccnv3xsvKpGQGj7zlGMlz2LHRACg5gnK 2qoz3wgsIokb4eKoV/3KF1o= =Kt4k -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--