From owner-freebsd-hackers Fri Aug 29 10:23:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA15769 for hackers-outgoing; Fri, 29 Aug 1997 10:23:59 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA15764 for ; Fri, 29 Aug 1997 10:23:56 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA10295; Fri, 29 Aug 1997 10:22:55 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010293; Fri Aug 29 17:22:54 1997 Message-ID: <34070560.7A79CB24@whistle.com> Date: Fri, 29 Aug 1997 10:22:40 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Thomas David Rivers CC: hackers@freebsd.org Subject: Re: 2.2.2+ kernel panic References: <199708291225.IAA03273@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thomas David Rivers wrote: > > I just saw this from Julien... > > > > > what's wrong with this picture? > > > > #0 boot (howto=260) at ../../kern/kern_shutdown.c:243 > > #1 0xf010cfd2 in panic (fmt=0xf017158f "page fault") > > at ../../kern/kern_shutdown.c:367 > > #2 0xf01720f6 in trap_fatal (frame=0xefbffb20) at > > ../../i386/i386/trap.c:742 > > #3 0xf0171be4 in trap_pfault (frame=0xefbffb20, usermode=0) > > at ../../i386/i386/trap.c:653 > > #4 0xf01718bf in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = > > -260688384, > > tf_esi = 0, tf_ebp = -272630932, tf_isp = -272630968, > > tf_ebx = -260578816, tf_edx = 0, tf_ecx = -260888576, > > tf_eax = -260286976, tf_trapno = 12, tf_err = -260505600, > > tf_eip = -267219466, tf_cs = -266797048, tf_eflags = 65606, tf_esp > > = 0, > > tf_ss = -260578816}) at ../../i386/i386/trap.c:311 > > #5 0xf0128df6 in vget (vp=0xf077e200, lockflag=1) at > > ../../kern/vfs_subr.c:817 > > > > See below.. > > > ... > > where he goes on to note an issues in vfs_subr.c (curproc was NULL). > > I was wondering if anything has come of this - 2.2.2+ fixes particularly. > This is in the area of my "daily panics" - and I always have questions > when something like this pops up. I have added extra diagnostics and am awaiting a re-occurance. julian > > - Thanks - > - Dave Rivers -