From owner-freebsd-questions@FreeBSD.ORG Thu Mar 11 17:07:37 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD6E516A50C for ; Thu, 11 Mar 2004 17:07:37 -0800 (PST) Received: from buh.cameradicommercio.ro (buh.cameradicommercio.ro [81.196.25.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F3F643D31 for ; Thu, 11 Mar 2004 17:07:37 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: from it.buh.cameradicommercio.ro (it.buh.cameradicommercio.ro [192.168.0.10]) by buh.cameradicommercio.ro (Postfix) with ESMTP id 32FC76299; Fri, 12 Mar 2004 01:07:05 +0000 (GMT) Received: from it.buh.cameradicommercio.ro (localhost.buh.cameradicommercio.ro [127.0.0.1]) by it.buh.cameradicommercio.ro (Postfix) with SMTP id F37971EC; Fri, 12 Mar 2004 03:09:37 +0200 (EET) Date: Fri, 12 Mar 2004 03:09:37 +0200 From: Ion-Mihai Tetcu To: eodyna Message-Id: <20040312030937.644eeeea@it.buh.cameradicommercio.ro> In-Reply-To: <20040312003308.38285.qmail@web41705.mail.yahoo.com> References: <20040312020732.035f18e9@it.buh.cameradicommercio.ro> <20040312003308.38285.qmail@web41705.mail.yahoo.com> X-Mailer: Sylpheed version 0.9.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: libfreetype.a: Bad address --> hard error reading X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 01:07:38 -0000 [ please don't post on top, it's hard to read ] On Fri, 12 Mar 2004 11:33:08 +1100 (EST) eodyna wrote: > Hello, > > Thanks for your response. > I dont think they are totally unrelated, because when > i try to install XFree86-4 and that particular library > it gets the error messages stated below (one to stdout > and the other to dmesg). All other port installations > work fine. (Before and after the XFree86-4 install) > > I orginally thought it was a hardware problem as well. > but to have it fail on two disks with the same sort of > error? that is highly unlikely, and installing > 4.8-RELEASE yeilds no errors. fsck doesn't produce any > errors either. > > And i dont think it is a ports problem > because XFree86-4.3.0,1 works on 4.8-RELEASE. So this > has left me thinking its either a bios thingy or > something in 4.9-RELEASE kernel that doesn't like my > laptop. This happen when an error is detected by the disk driver. This can be caused by hardware failure or incompatibility, or a driver bug. You get a vm_fault if the kernel is trying to page in a block of memory for a process but it can't. You probably get this instead of a regular read error because AFAIR cp and install uses mmap() on files smaller than 8 MB. Since you changed the HDD it's probably a driver bug. However I would be curios if you get the always the same fsbn xxxx numbers. I would be very strange. Stage also is that it's failing on the same file. > or maybe i jump to too many conculsions? > Hence why i would like some advice on how to trouble > shoot this. Aside from posting this + boot -v on mobile, I don't know. > This is the post from yesterday with the main error > msg: missed that, sorry. -- IOnut Unregistered ;) FreeBSD user