From owner-freebsd-current@FreeBSD.ORG Mon Dec 8 13:24:39 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 4196B16A4CF for ; Mon, 8 Dec 2003 13:24:39 -0800 (PST) Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [217.72.192.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D0EA43D29 for ; Mon, 8 Dec 2003 13:24:24 -0800 (PST) (envelope-from nakal@web.de) Received: from smtp.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) ESMTP id hB8LNWd22680 for ; Mon, 8 Dec 2003 22:23:32 +0100 Received: from [217.225.234.10] (helo=[217.225.234.10]) by smtp.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.99 #566) id 1ATSpr-0003PY-00 for current@freebsd.org; Mon, 08 Dec 2003 22:22:31 +0100 From: Martin To: current@freebsd.org Content-Type: text/plain Message-Id: <1070918549.702.22.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 08 Dec 2003 22:22:30 +0100 Content-Transfer-Encoding: 7bit Sender: nakal@web.de Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 21:24:39 -0000 Here is the result of a read access on a file, which is obviously unreadable: acd0: FAILURE - READ BIG status=51 sensekey=MEDIUM ERROR error=4 vm_fault: pager read error, pid 606 (cp) cp: filename: Bad address I want to report it, because of the "vm_fault", it sounds "scary". Is this a correct behaviour or a bug in the kernel? (FYI: With pre-BETA kernels I got a panic at this point. I recompiled with some debug options and I get just the message above.) Martin