From owner-freebsd-current  Tue Dec  8 23:01:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA11597
          for freebsd-current-outgoing; Tue, 8 Dec 1998 23:01:41 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11592
          for <freebsd-current@FreeBSD.ORG>; Tue, 8 Dec 1998 23:01:38 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA09365;
	Wed, 9 Dec 1998 18:01:31 +1100
Date: Wed, 9 Dec 1998 18:01:31 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812090701.SAA09365@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>I've just upgraded a Dell OptiPlex GXi from 32MB to 96MB.  When I
>>increase MAXUSERS from 20 to 40 and SEMMNU from 350 to 1000, the
>>system panics `getnewbuf: inconsistent EMPTY queue, qindex=0'
>>immediately after the message `changing root device to wd0s1a'.
>...
>Presumably, the real problem is that the buffer cache is either
>uninitialised (possibly due to lack of KVM), or has been corrupted.
>Unfortunately, it is not practical to have the system off-air for an
>extended period whilst I poke around with DDB.  Can anyone suggest
>which knobs to tweak to resolve the problem (or even where to look for
>the problem).

valloc() in machdep.c isn't robust.

Bruce

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