From hsu@clinet.fi  Sat Mar  8 22:07:05 1997
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA28816
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 8 Mar 1997 22:07:02 -0800 (PST)
Received: from news.clinet.fi (root@news.clinet.fi [194.100.0.3]) by hauki.clinet.fi (8.8.5/8.6.4) with ESMTP id IAA22696 for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 Mar 1997 08:06:56 +0200 (EET)
Received: (root@localhost) by news.clinet.fi (8.8.5/8.6.4) id IAA01418; Sun, 9 Mar 1997 08:07:17 +0200 (EET)
Message-Id: <199703090607.IAA01418@news.clinet.fi>
Date: Sun, 9 Mar 1997 08:07:17 +0200 (EET)
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: panic: vm_fault: fault on nofault entry, addr: f6e21000
X-Send-Pr-Version: 3.2

>Number:         2923
>Category:       kern
>Synopsis:       panic: vm_fault: fault on nofault entry, addr: f6e21000
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    des
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar  8 22:10:02 PST 1997
>Closed-Date:    Sun May 27 15:40:30 PDT 2001
>Last-Modified:  Sun May 27 15:41:02 PDT 2001
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2-GAMMA i386
>Organization:
Clinet, Espoo, Finland
>Environment:

news server, 7 disks now (3G quantum), P150, 2*2940.  This also happened
with 4*seagate + P120 + 1*3940.

>Description:

hsu#news.clinet.fi Sun 3: gdb -k kernel.18 vmcore.18
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i386-unknown-freebsd), 
Copyright 1996 Free Software Foundation, Inc...
IdlePTD 272000
current pcb at 211dd8
panic: vm_fault: fault on nofault entry, addr: %lx
#0  boot (howto=256) at ../../kern/kern_shutdown.c:243
243                                     dumppcb.pcb_cr3 = rcr3();
(kgdb) up
#1  0xf01124e2 in panic (
    fmt=0xf01bab87 "vm_fault: fault on nofault entry, addr: %lx")
    at ../../kern/kern_shutdown.c:367
367             boot(bootopt);
(kgdb) up
#2  0xf01bacae in vm_fault (map=0xf3ce8f00, vaddr=4142010368, 
    fault_type=1 '\001', change_wiring=0) at ../../vm/vm_fault.c:201
201                     panic("vm_fault: fault on nofault entry, addr: %lx",
(kgdb) up
#3  0xf01cf7e4 in trap_pfault (frame=0xefbffc74, usermode=0)
    at ../../i386/i386/trap.c:642
642                     rv = vm_fault(map, va, ftype, FALSE);
(kgdb) up
#4  0xf01cf50f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 8191, 
      tf_esi = -190055168, tf_ebp = -272630456, tf_isp = -272630628, 
      tf_ebx = -152955599, tf_edx = -158953624, tf_ecx = 54577, tf_eax = 0, 
      tf_trapno = 12, tf_err = 0, tf_eip = -266652905, tf_cs = 8, 
      tf_eflags = 66178, tf_esp = -186717952, tf_ss = -272630396})
    at ../../i386/i386/trap.c:311
311                             (void) trap_pfault(&frame, FALSE);
(kgdb) up
#5  0xf01b3317 in ufs_lookup (ap=0xefbffd84) at ../../ufs/ufs/ufs_lookup.c:279
279                     ep = (struct direct *)((char *)bp->b_data + entryoffsetinblock);
(kgdb) list
274                      * Full validation checks are slow, so we only check
275                      * enough to insure forward progress through the
276                      * directory. Complete checks can be run by patching
277                      * "dirchk" to be true.
278                      */
279                     ep = (struct direct *)((char *)bp->b_data + entryoffsetinblock);
280                     if (ep->d_reclen == 0 ||
281                         (dirchk && ufs_dirbadentry(vdp, ep, entryoffsetinblock))) {
282                             int i;
283
(kgdb)

This problem is exactly the same as bad dir panic, it just freaks out
differently.  The panic always occurs at the above point, with wrong data
(usually seems contents of a some file) in a block the directory lookup
routine thinks is part of a directory.

Access to this and 4-5 other dumps on the subject is available on request I
do not have space for more than 4-5 dumps on-line.  They seem to always be
from the same problem, so there should be good material to find
similarities from to solve this.

>How-To-Repeat:

Run a news server with 2.2.  Full feed and bunch of readers (around 100
max, but panics usually occur with less load).  Expire articles one-by-one
to keep the free disk space at certain limit instead of running traditional
expire.  The latter may contribute to the problem, as I got metoos for
this.

This same problem happens with all machines, but the problem is very rare
with unloaded machines.

>Fix:
	
>Release-Note:
>Audit-Trail:

From: Heikki Suonsivu <hsu@clinet.fi>
To: freebsd-gnats-submit@freebsd.org
Cc: hsu@clinet.fi
Subject: kern/2923 panic: vm_fault: fault on nofault entry, addr: , f6e21000
Date: Sat, 28 Mar 1998 04:25:35 +0200 (EET)

 This is probably related to the famous BAD/DUP inode problem, which
 certainly has not gone away.  It happens particularly often with intensive
 NFS writing.  See also 4673, might be related.
 
 Studded@dal.net writes:
  > Greetings, :)
  > 
  > 	I am writing to you in regards to your FreeBSD Problem
  > Report. The FreeBSD project is currently conducting a beta test on
  > version 2.2.6 and feedback as to whether you are still experiencing
  > your problem would be very valuable. 
  > 
  > 	If you are still experiencing the problem you reported, it
  > would help the project track the problem if you could upgrade to the
  > latest snapshot of 2.2.6-Beta (located at releng22.freebsd.org) and
  > test your problem again. 
  > 
  > 	If you have any feedback regarding this Problem Report,
  > whether you are still experiencing the problem or whether the PR can
  > be closed, please mail your response to
  > freebsd-gnats-submit@freebsd.org. Please do not respond directly to
  > me. I am merely a humble volunteer and have no official connection to
  > the FreeBSD project. Therefore I cannot make any changes to the status
  > of your Problem Report. It is also very important that you include 
  > the category and number of your Problem Report (kern/2923) in the 
  > subject line of your response.
  > 
  > 	Another option if you need a refresher on the details of your
  > problem or would like to submit a followup is to use the web page
  > interface and look up your PR by number.
  > http://www.freebsd.org/cgi/query-pr-summary.cgi
  > 
  > 	Thank you for helping to make this the greatest release of
  > FreeBSD ever.
  > 
  > Doug
  > 
  > 
  > -- 
  > ***         Chief Operations Officer, DALnet IRC network       ***
  > *** Proud operator, designer and maintainer of the world's largest
  > *** Internet Relay Chat server.  5,328 clients and still growing.
  > *** Try spider.dal.net on ports 6662-4    (Powered by FreeBSD)
  > 

From: Frank Ederveen <franke@nl.uu.net>
To: freebsd-gnats-submit@freebsd.org, hsu@clinet.fi, franke@nl.uu.net
Cc:  
Subject: Re: kern/2923: panic: vm_fault: fault on nofault entry, addr: f6e21000
Date: Thu, 04 Feb 1999 09:56:22 +0100

 Just want to point out that indeed the problem has not been solved
 yet. With 3.0-STABLE as of feb 1st 1999 this is still the case.
 
 We do not seem to be able to keep the newsserver up and running for
 more than a few hours, to sometimes a day or two if we get very
 lucky.
 
 Pitty we can no longer wait for a solution with FreeBSD; we received
 the sparc with solaris this morning :(
 
 Feel free to contact for more info and/or debugging stuff.
 
 With kind regards,
 
 Frank Ederveen

From: Dag-Erling Smorgrav <des@ofug.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: kern/2923
Date: 13 Mar 2001 03:36:42 +0100

 Is this still a problem in newer versions of FreeBSD? Quite a lot (to
 say the least) has happened in two years since the last update.
 
 DES
 -- 
 Dag-Erling Smorgrav - des@ofug.org
State-Changed-From-To: open->feedback 
State-Changed-By: dougb 
State-Changed-When: Sun May 27 15:23:40 PDT 2001 
State-Changed-Why:  

Let's give this one more chance before closing. 



Responsible-Changed-From-To: freebsd-bugs->des 
Responsible-Changed-By: dougb 
Responsible-Changed-When: Sun May 27 15:23:40 PDT 2001 
Responsible-Changed-Why:  

He was the last one to express interest, and quite capable of 
deciding to close it if that's the right thing to do. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=2923 
State-Changed-From-To: feedback->closed 
State-Changed-By: dougb 
State-Changed-When: Sun May 27 15:40:30 PDT 2001 
State-Changed-Why:  

Mail to originator bounces. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=2923 
>Unformatted:
