From owner-freebsd-current@FreeBSD.ORG Tue Apr 22 22:42:06 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 AAFDB37B401 for ; Tue, 22 Apr 2003 22:42:06 -0700 (PDT) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C6EC43FA3 for ; Tue, 22 Apr 2003 22:42:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0352.cvx22-bradley.dialup.earthlink.net ([209.179.199.97] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 198D16-0003NY-00; Tue, 22 Apr 2003 22:42:01 -0700 Message-ID: <3EA6275D.540C710C@mindspring.com> Date: Tue, 22 Apr 2003 22:40:45 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Craig Reyenga References: <000501c30943$9535dda0$0200000a@fireball> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4da3d45f2a53477a42c79365194744ea6666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Makefile in /usr/src/lib/libdisk WARNS change? PLEASE READ! 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, 23 Apr 2003 05:42:06 -0000 Craig Reyenga wrote: > I know how you feel, boss. I just started a thread about how my computer > dies if I run out of memory, and all I got was a "me too" from another > fellow user. No developers jumped in. It seems like unless you have a LOR or > a laptop, you get no attention. And no, don't bother filing a bug report > because it will stagnate further. If you are getting a problem about running out of memory, and you have at least some swap, that is a lot different than a problem that happens when you run out of memory, and you have no swap. Assuming you have *some* swap, then the problem is probably related to the new allocator. If you can post a stack traceback for the problem, then I can likely help you resolve it. Be aware that if your system is under either memory pressure or KVA pressure, the problem is only going to pop up somewhere else, so you will need to iterate the problem a number of times. If this problem is on 4.x instead of 5.x, and related to the change from 1G of KVA to 2G of KVA, be aware that I recently posted a patch to -stable that resolves the most common case for that problem, even if people insist on not committing it because they don't understand why it works (for me, it's enough that it does work; the traceback that I used to come up with the patch was unambiguous about why the crash was occurring; poeple with the problem shouldn't really give a damn about "why", IMO). -- Terry