From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 25 17:15:59 2005 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BF5516A41F for ; Thu, 25 Aug 2005 17:15:59 +0000 (GMT) (envelope-from mstorer@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25F8143D45 for ; Thu, 25 Aug 2005 17:15:58 +0000 (GMT) (envelope-from mstorer@gmail.com) Received: by wproxy.gmail.com with SMTP id i1so182219wra for ; Thu, 25 Aug 2005 10:15:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=swcHZQbLaENAVlNeAXY4BdLFyq/c2ZycgHcJjskUavhu+Yit7yF8PpLaS9nXxVZq7NKFWoyQKJCfbb2OnARSelILQmuwgdB+WgmQjCS/b+BQC+zAgwLpZNyMaSBT46RvEVvhSd2G9kEFI700fgPtsu9UpWh3b5iiz7Gr+rmjjPs= Received: by 10.54.44.30 with SMTP id r30mr2081742wrr; Thu, 25 Aug 2005 10:15:56 -0700 (PDT) Received: by 10.54.28.52 with HTTP; Thu, 25 Aug 2005 10:15:56 -0700 (PDT) Message-ID: <99ee2ecf05082510155a5c5222@mail.gmail.com> Date: Thu, 25 Aug 2005 13:15:56 -0400 From: Matt Storer To: freebsd-bugs@freebsd.org In-Reply-To: <99ee2ecf05082417149209411@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <99ee2ecf05082417149209411@mail.gmail.com> Subject: Re: kernel bug in uipc_syscalls.c X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Aug 2005 17:15:59 -0000 Hi again - OK, I think perhaps you can scratch that bug I found. It turns out that the box onto which I've been installing FreeBSD has memory that's really, really bit the dust. I believe that the corrupt memory could be the cause of not only the bug in uipc_syscalls, but is also responsible for numerous errors I've recently encountered while running fsck. We're replacing the memory now. Hopefully that will fix the problem. Sorry to cause any alarm - Matt On 8/24/05, Matt Storer wrote: > Hi - >=20 > I'm in the process of reinstalling FreeBSD 5.4-STABLE onto an i386 > box. I was in the process of recompiling my custom kernel when I came > upon an error during the "make" step, in uipc_syscalls.c. The error > looked basically like: >=20 > uipc_syscalls.c in function "socket" 176: error: structure has no > member named `f_gps' >=20 > I looked into it, and I came to the conclusion that f_gps was supposed > to be f_ops, a member of struct file. So I backed up uipc_syscalls.c > and made the change. The kernel has now been compiling just fine > through that bug. >=20 > sooo... I can't imagine you guys haven't found this yet, but in the > unlikely even you haven't, there ya go. I don't know how my copy of > uipc_syscalls.c could get foobar'd otherwise. >=20 > ... additionally, I'm quite interested to know if that bug exists on > your end of things. PLEASE let me know if it doesn't. >=20 > Thanks! >=20 > Matt >