From owner-freebsd-current@FreeBSD.ORG Tue Oct 21 11:54:37 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 69D4F16A4B3 for ; Tue, 21 Oct 2003 11:54:37 -0700 (PDT) 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 5AD9743FB1 for ; Tue, 21 Oct 2003 11:54:36 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 24A6266C9E; Tue, 21 Oct 2003 11:54:36 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 0B8E7DB2; Tue, 21 Oct 2003 11:54:36 -0700 (PDT) Date: Tue, 21 Oct 2003 11:54:36 -0700 From: Kris Kennaway To: Dimitry Andric Message-ID: <20031021185435.GA66921@rot13.obsecurity.org> References: <13041066290.20031021201724@andric.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline In-Reply-To: <13041066290.20031021201724@andric.com> User-Agent: Mutt/1.4.1i cc: FreeBSD-Current List Subject: Re: MBR zapped when panicking? 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: Tue, 21 Oct 2003 18:54:37 -0000 --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 21, 2003 at 08:17:24PM +0200, Dimitry Andric wrote: > Hi, >=20 > Today I had a -CURRENT machine panic on me with a page fault, and > something happened that I have seen before: the machine refused to > come up afterwards. Closer inspection revealed that the MBR on the > boot disk was totally zapped, filled with seemingly random characters. This is a known bug in the ATA driver. Tor Egge provided a workaround patch here a few weeks ago. I didn't try it because I can't afford to trash my disks like that again. Kris --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/lYDrWry0BWjoQKURAvciAJ987wQ1YYR8e3yXz2jGvXATHjN+nACgqdjE uDDQKnrt/5n9IzIZGMAqxjw= =LM3P -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N--