From owner-freebsd-current@FreeBSD.ORG Fri Nov 21 16:19:33 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 C442916A4CE for ; Fri, 21 Nov 2003 16:19:33 -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 C4C3B43FEC for ; Fri, 21 Nov 2003 16:19:28 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5396866C55; Fri, 21 Nov 2003 16:19:28 -0800 (PST) Date: Fri, 21 Nov 2003 16:19:28 -0800 From: Kris Kennaway To: Jimmy Selgen Message-ID: <20031122001928.GA7633@xor.obsecurity.org> References: <1069446169.15019.46.camel@janitor> <20031121202949.GA5181@xor.obsecurity.org> <1069454437.15019.75.camel@janitor> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <1069454437.15019.75.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: Sat, 22 Nov 2003 00:19:33 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 21, 2003 at 11:40:37PM +0100, Jimmy Selgen wrote: > The box in question is my workstation, so I guess i'm not passing that > much traffic through ipfilter. Also, when I said that the NIC still > worked, I might have mislead you a bit. I had about 5-10 timeouts while > scp'ing the dmesg output to my other workstation. > Data seems to move from userland to the kernel, then get stuck in > buffers there for 10-15 seconds, "generating" timeouts, before they're > shipped off. I assume this is expected behaviour when a NIC isnt > behaving correctly. OK, it's still possible something is triggering a locking bug. Or your problem could be elsewhere. > > It would be helpful if you can do a binary search to narrow down when > > the problem started. > What would you have me search ? I'm a faily seasoned C programmer (12 > years experience, some of them doing RTOS kernel work), but dont know > much about FreeBSD kernel development, or the process of checking out > different kernel revisions. You have a couple of choices..if you update your sources by cvsup, there's a date keyword you can use in your cvsupfile to select sources from that date. If you're using cvsup to fetch a local repository and then cvs to check out from there, cvs also has the -D keyword you can use to update to a date string. Using cvs is better, because you can easily control it on the level of individual file revisions once you get down to testing a few specific changes. Setting up cvs and cvsup are both documented on the freebsd website. Basically, if you can iterate through different dates, halving the date between the last kernel you know worked and the first kernel you know did not, to push the boundaries down, it will narrow down the range of commits that caused the problem. =20 > I've tried a build without IPFILTER, and the problem still exists. > I've also tried booting with ACPI disabled, and the problem is still > there. OK, that probably rules them out. > I have attached a copy of my kernel config file, in case i'm doing > something wrong. Looked OK to me. Kris --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/vquQWry0BWjoQKURAjr4AKClHlpGqQZ6q7P1wGkEnNZpd1SSPwCeIKLC x0uN/FVHG6wDN2sva5k4xtA= =w6Mw -----END PGP SIGNATURE----- --ibTvN161/egqYuK8--