From owner-freebsd-current Sun Dec 13 20:08:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21786 for freebsd-current-outgoing; Sun, 13 Dec 1998 20:08:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21781 for ; Sun, 13 Dec 1998 20:08:18 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40406>; Mon, 14 Dec 1998 15:07:29 +1100 Date: Mon, 14 Dec 1998 15:07:58 +1100 From: Peter Jeremy Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE To: freebsd-current@FreeBSD.ORG Message-Id: <98Dec14.150729est.40406@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri Dec 4 07:47:27 1998, I wrote: >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'. I've managed to track this down to a bug in the handling of SysV semaphore undo structures when non-default SEMxxx values are used. Look up kern/9068 for details. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message