From owner-freebsd-current@FreeBSD.ORG Wed Sep 10 13:51:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D38A116A4BF for ; Wed, 10 Sep 2003 13:51:08 -0700 (PDT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0A9143FA3 for ; Wed, 10 Sep 2003 13:51:07 -0700 (PDT) (envelope-from des@des.no) Received: from smtp.des.no (37.80-203-228.nextgentel.com [80.203.228.37]) by mail.broadpark.no (Postfix) with ESMTP id 8F85B78D67; Wed, 10 Sep 2003 22:51:06 +0200 (MEST) Received: by smtp.des.no (Pony Express, from userid 666) id 05E0B9821A; Wed, 10 Sep 2003 22:51:05 +0200 (CEST) Received: from dwp.des.no (dwp.des.no [10.0.0.4]) by smtp.des.no (Pony Express) with ESMTP id 88C6895D88; Wed, 10 Sep 2003 22:51:01 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 5295CB822; Wed, 10 Sep 2003 22:51:01 +0200 (CEST) To: Tomi.Vainio@Sun.COM References: <16222.8328.482125.571191@ultrahot.finland.sun.com> <16222.14948.423489.596523@ultrahot.finland.sun.com> <20030910112539.F53623@carver.gumbysoft.com> <16223.32410.556709.818592@ultrahot.finland.sun.com> <16223.35291.354753.437544@ultrahot.finland.sun.com> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Wed, 10 Sep 2003 22:51:01 +0200 In-Reply-To: <16223.35291.354753.437544@ultrahot.finland.sun.com> (Tomi Vainio's message of "Wed, 10 Sep 2003 23:30:19 +0300") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, hits=-3.0 required=8.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-current@freebsd.org Subject: Re: ufs related panic with latest current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2003 20:51:08 -0000 Tomi Vainio - Sun Finland writes: > Dag-Erling Sm=F8rgrav writes: > > Tomi Vainio - Sun Finland writes: > > > First maxusers was 0 then when changed it to 8. > > That's a regression. Keep it at 0. > I understood that there is a bug on new kmem allocator and this was an > attempt to reduce kmem allocations but it didn't help. Do you know if > this is going to fixed somehow or should people just install more > memory to get system stay up? Well, reducing maxusers isn't going to help much as it only controls a small part of kernel memory, and setting it too low may render the system unusable. The backtrace you showed seems to indicate that the panic happened somewhere in the softupdates code, but IIRC that code has a fairly conservative built-in limit on memory consumption and degrades gracefully when it hits that limit. It's likely that something else gobbled up all available kernel memory, and the mallloc() call from softupdates was simply the straw that broke the camel's back. If you have a serial console hooked up, you could try running while :; do vmstat -m ; sleep 1 ; done on the serial console while doing whatever it is you do that causes the problem. This will tell you how much kernel memory was in use at the time of the panic and what it was used for. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no