From owner-freebsd-stable@FreeBSD.ORG Wed Jan 5 23:05:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7EB316A4CE for ; Wed, 5 Jan 2005 23:05:28 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 486D143D39 for ; Wed, 5 Jan 2005 23:05:28 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CmKDX-00022k-00; Thu, 06 Jan 2005 00:05:27 +0100 Received: from [217.83.0.78] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CmKDW-0000Pf-00; Thu, 06 Jan 2005 00:05:27 +0100 From: Max Laier To: freebsd-stable@freebsd.org Date: Thu, 6 Jan 2005 00:05:19 +0100 User-Agent: KMail/1.7.2 References: <20050105172615.CF820C32C@brugere.aub.dk> In-Reply-To: <20050105172615.CF820C32C@brugere.aub.dk> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5785812.cLcgL6yYMP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501060005.25343.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: netstat fails with memory allocation error and error in kvm_read X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 23:05:28 -0000 --nextPart5785812.cLcgL6yYMP Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 05 January 2005 18:26, J. Martin Petersen wrote: > > I just got another "netstat: kvm_read: Bad address". > > vm.kvm_free was 675278848 two seconds earlier and a couple of > > seconds later (and also currently). > > We just had another hard hang, and this time I managed to break to the > debugger on the serial console. I got this stack trace > , which seems to indicate that pf is > messing up somehow. This looks like pf.c, rev. 1.25 (HEAD) 1.18.2.6 (RELENG_5) and is an endles= s=20 loop, not a deadlock. I hope you can verify that updating to these revision= s=20 solves the issue. Please get back to me if not. Thanks in advance. > I of course didn't have the ddb man or the handbook section on kernel > debugging at hand, so I've just printed it for the next time it happens. > > Both 'show witness' and 'show locks' came up empty. What's the most > effective way to hunt down these deadlocks with the online kernel debugge= r? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart5785812.cLcgL6yYMP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB3HK1XyyEoT62BG0RArIkAJ9XgvRyfMYY1YKWCzkFpYO6YQwTiQCfS8VD ccnevkC8e2nBAdXtESUAiTU= =YXFW -----END PGP SIGNATURE----- --nextPart5785812.cLcgL6yYMP--