From owner-freebsd-stable Mon Jun 14 8:33:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id AF45315275 for ; Mon, 14 Jun 1999 08:33:52 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA27628; Mon, 14 Jun 1999 08:33:52 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda27624; Mon Jun 14 08:33:40 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA88281; Mon, 14 Jun 1999 08:33:40 -0700 (PDT) Message-Id: <199906141533.IAA88281@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdi88273; Mon Jun 14 08:33:06 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.1-RELEASE X-Sender: cschuber To: Martti Kuparinen Cc: stable@FreeBSD.ORG Subject: Re: Lockups: should I go back to 2.2.8 In-reply-to: Your message of "Mon, 14 Jun 1999 10:23:01 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jun 1999 08:33:06 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Martti Kuparinen writes: > While running tripwire in our server, the system locked up (well, > in fact the load went up to 600+ and the whole system became unusable, > so it was not a panic or dead-lock). The operating system is 3.2-STABLE > and "make world" was performed last friday. The host is NFS server > with small average load. > > The question is: if I need a rock-solid system as it is our main > server for 20 people, should I downgrade to 2.2.8-STABLE? > > I think I can't afford to wait for the VM thing to be fixed, but I > don't know if 228-S has similar symptoms, i.e. do I win something by > going back to 228-S? I had system hangs, until 1.23.2.3 of kern_lock.c was committed. Since then, I've had what appeared to be a hang that became a panic after waiting 19 minutes. See PR 11993 (panic: getnewbuf: inconsistent EMPTY queue, qindex=0). This has only occurred once, on June 2. Before anyone can debug this we will need some additional information like a description of you hardware, uname -a output, dmesg output, a copy of your kernel config file, and a bactrace listing from your vmcore dump. Once you have the required information, the best way to report bugs of this kind is through send-pr(1). You may still wish to post to this list to provide the rest of us with some kind of heads-up notification and maybe flush out comments about similar experiences into the open. Best of luck. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message