From owner-freebsd-bugs  Fri Mar 27 18:30:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14063
          for freebsd-bugs-outgoing; Fri, 27 Mar 1998 18:30:06 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14049;
          Fri, 27 Mar 1998 18:30:04 -0800 (PST)
          (envelope-from gnats)
Date: Fri, 27 Mar 1998 18:30:04 -0800 (PST)
Message-Id: <199803280230.SAA14049@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Heikki Suonsivu <hsu@clinet.fi>
Subject: kern/4673 Two panics, now crash dumps, always in reassignbuf
Reply-To: Heikki Suonsivu <hsu@clinet.fi>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/4673; it has been noted by GNATS.

From: Heikki Suonsivu <hsu@clinet.fi>
To: freebsd-gnats-submit@freebsd.org
Cc: hsu@mail.clinet.fi
Subject: kern/4673 Two panics, now crash dumps, always in reassignbuf
Date: Sat, 28 Mar 1998 04:27:24 +0200 (EET)

 This was greatly reduced by removing writing over NFS.  We were running aub
 on our news server, and it was writing over NFS to save the files
 generated.  Problem mostly disappeared after this NFS load was removed.  It
 is not a fix, but might give a clue of what might be going on. 
 
 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/4673)
  > 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)
  > 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message