Date: Mon, 14 Dec 1998 06:55:39 +0100 (CET) From: List User <listuser@netspace.net.au> To: freebsd-current@FreeBSD.ORG Message-ID: <199812140555.GAA08973@doorway.home.lan>
next in thread | raw e-mail | index | archive | help
Newsgroups: freebsd.current Path: root From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au> Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE Received: by border.alcanet.com.au id <40406>; Mon, 14 Dec 1998 15:07:29 +1100 To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <98Dec14.150729est.40406@border.alcanet.com.au> Delivered-To: vmailer-current@freebsd.org X-Uidl: 46d110033e32e564767593b49f09054a X-Loop: FreeBSD.ORG Date: Mon, 14 Dec 1998 04:07:58 GMT 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812140555.GAA08973>