From owner-freebsd-current Wed Jun 12 05:13:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA28440 for current-outgoing; Wed, 12 Jun 1996 05:13:03 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA28434 for ; Wed, 12 Jun 1996 05:13:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id FAA00941; Wed, 12 Jun 1996 05:13:06 -0700 (PDT) Message-Id: <199606121213.FAA00941@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: Brian Tao cc: Matt Day , freebsd-current@FreeBSD.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-reply-to: Your message of "Tue, 11 Jun 1996 23:28:25 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 12 Jun 1996 05:13:05 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >On Tue, 11 Jun 1996, Matt Day wrote: >> >> Sorry for the false alarm on yesterday's patch. I saw "NULL >> dereference" and "fsync" and I immediately thought of that fsync >> dereferencing NULL bug... but that was ffs_fsync(), not plain old >> fsync()! I think appropriate punishment for my error would be to >> find this other bug. :-) > > Could you, pretty please? ;-) I've built emacs 19.31 linked with >the 2.2 libs to see if that was a problem, but I just saw one of the >shell servers die again tonight. :( I'm going to try your patch >anyway to see how it goes. Thanks. > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x18 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xf012afc3 Since this is -current, I would strongly suggest SUPing the latest stuff. There were a great deal of serious VM system bugs in the 0501 snapshot that have just recently been worked out. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project