From owner-freebsd-hackers Tue Aug 26 23:53:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA14580 for hackers-outgoing; Tue, 26 Aug 1997 23:53:21 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA14574 for ; Tue, 26 Aug 1997 23:53:19 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id XAA28684; Tue, 26 Aug 1997 23:53:09 -0700 (PDT) Date: Tue, 26 Aug 1997 23:53:08 -0700 (PDT) From: Jaye Mathisen To: Mark Heath cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Status of the following bugs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 2 quick suggestions. 1) Get rid of MMAP (assuming INN). 2) Upgrade to 3.0. The bad dir panic's have disappeared with upgrading. On Wed, 27 Aug 1997, Mark Heath wrote: > > Im having frequent (once every 2-3 hours) crashes, on a news server due to > the following bugs: > > kern/2923: panic: vm_fault: fault on nofault entry, addr:f6e21000 > kern/2771 panic: bad dir > kern/3582 panic: bad dir (mangled entry) in 2.2-STABLE > > Does any one know what possible solutions or state of these bugs are. > > The relevant hardware & software for the machine is: > > FreeBSD 2.2-970819-RELENG #0 > CPU: Pentium Pro (199.43-MHz 686-class CPU) > real memory = 268435456 (262144K bytes) > ahc0 rev 0 int a irq 11 on pci1:4 > > (ahc0:0:0): "FUJITSU M2954Q-512 0147" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 4149MB (8498506 512 byte sectors) > Five drives, 3 on channel A, 2 on channel B > ccd0-3: Concatenated disk drivers > > Thanks for your responces. > > -- mark heath - Netspace Online Systems. http://www.netspace.net.au/ > :wq >