From owner-freebsd-current@FreeBSD.ORG Sun Sep 14 09:10:53 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 47B4116A4BF for ; Sun, 14 Sep 2003 09:10:53 -0700 (PDT) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62AB843F75 for ; Sun, 14 Sep 2003 09:10:52 -0700 (PDT) (envelope-from ler@lerctr.org) Received: from lerlaptop.lerctr.org (lerlaptop.lerctr.org [207.158.72.14]) (authenticated bits=0)h8EGAn98022328 for ; Sun, 14 Sep 2003 11:10:49 -0500 (CDT) Date: Sun, 14 Sep 2003 11:10:46 -0500 From: Larry Rosenman To: freebsd-current@freebsd.org Message-ID: <8000000.1063555846@lerlaptop.lerctr.org> X-Mailer: Mulberry/3.1.0b7 (Linux/x86) X-PGP-Info: All other keys are old/dead. X-PGP-Key: 0x3c49bdd6 X-PGP-Fingerprint: D0D1 3C11 F42F 6B29 FA67 6BF3 AD13 4685 3C49 BDD6 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========B1D5A850C3C26A20C10D==========" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Subject: unable to get dumps? 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: Sun, 14 Sep 2003 16:10:53 -0000 --==========B1D5A850C3C26A20C10D========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Is there a known issue with recent -CURRENT (between September 10, 2003 and = today) where you can't get a panic dump? I have a kernel from yesterday's sources (modulo a reversion of=20 ata-lowlevel to version 1.10 because 1.11 won't boot), and some debugging code from Nate Lawson to=20 debug my ACPI issue. When I hit DDB, and type panic, it says it's dumping, but NO disk I/O=20 occurs. What can I get to help this? Also, when coming back up after the Panic on the same kernel, we get=20 unexpected soft-update inconsistencies, cannot write block type errors from FSCK. Going back to my September 9, 2003 kernel, fsck deals with the same exact=20 filesystem just fine. What can I get to help with this issue as well>? --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 --==========B1D5A850C3C26A20C10D========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/ZJMIrRNGhTxJvdYRAsC+AJwPNXnstqU6CK/GmpCdHpB3b8bpFQCgncAA q5JwxZ30/3QtXIIa7BwpEjg= =jCqL -----END PGP SIGNATURE----- --==========B1D5A850C3C26A20C10D==========--