From owner-freebsd-current@FreeBSD.ORG Tue Sep 13 05:01:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 C58A316A41F for ; Tue, 13 Sep 2005 05:01:58 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A27643D48 for ; Tue, 13 Sep 2005 05:01:58 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: by xproxy.gmail.com with SMTP id i27so2153054wxd for ; Mon, 12 Sep 2005 22:01:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=sOUDDfHdyVvH570Cf6oOMwXkc+bdkD4mQaxlHr97D2fmcAp8pqFtR3bnPY7B5fmUhou8qfTs6eaypf/uDCelXIFHhzK37X73TobAJUzPiko95zWcfIMxL44vGkvIXt65SU+AXmioCG/vJChdLhmD09MFSPAevefY9yDXf5Ge9uU= Received: by 10.70.11.4 with SMTP id 4mr59857wxk; Mon, 12 Sep 2005 21:54:45 -0700 (PDT) Received: by 10.70.9.2 with HTTP; Mon, 12 Sep 2005 21:54:45 -0700 (PDT) Message-ID: <47d0403c050912215419c10132@mail.gmail.com> Date: Tue, 13 Sep 2005 04:54:45 +0000 From: Ben Kaduk To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: is dumping broken again on current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: minimarmot@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 05:01:58 -0000 Hi all,=20 I have been trying to track down a panic upon unload of snd_ich, and it=20 seems that something in the past week broke core dumps -- I got one useable= =20 dump from a week ago, but all the dumps I've gotten from today's current=20 have failed to load with an infinite loop of: kgdb: kvm_read: invalid address (0xf0) Is anyone else seeing this, or is it just my system that's messed up? Ben Kaduk