From owner-freebsd-current@FreeBSD.ORG  Mon Dec  8 13:41:06 2003
Return-Path: <owner-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 07A1C16A4CE
	for <current@freebsd.org>; Mon,  8 Dec 2003 13:41:06 -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 36FB643D28
	for <current@freebsd.org>; Mon,  8 Dec 2003 13:40:57 -0800 (PST)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id BBCCF66C8E; Mon,  8 Dec 2003 13:40:56 -0800 (PST)
Date: Mon, 8 Dec 2003 13:40:56 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Martin <nakal@web.de>
Message-ID: <20031208214056.GA52416@xor.obsecurity.org>
References: <1070918549.702.22.camel@klotz.local>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/"
Content-Disposition: inline
In-Reply-To: <1070918549.702.22.camel@klotz.local>
User-Agent: Mutt/1.4.1i
cc: current@freebsd.org
Subject: Re: Is "vm_fault" a kernel bug here?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2003 21:41:06 -0000


--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 08, 2003 at 10:22:30PM +0100, Martin wrote:
>=20
> Here is the result of a read access on a file, which is obviously
> unreadable:
>=20
> acd0: FAILURE - READ BIG status=3D51<READY,DSC,ERROR> sensekey=3DMEDIUM
> ERROR error=3D4<ABORTED>
> vm_fault: pager read error, pid 606 (cp)
> cp: filename: Bad address
>=20
> I want to report it, because of the "vm_fault", it sounds "scary".
> Is this a correct behaviour or a bug in the kernel?

That's just what happens when an error is detected by the disk driver.
This can be caused by hardware failure or incompatibility, or a driver
bug.

Kris

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/1O/oWry0BWjoQKURAl1MAJ0WgvolYgRDu4+Jh5KG2lJjdEnf5wCfYxTX
k//iLM4Hi0BvwS9XtzKbPAU=
=60mH
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--