Date: Thu, 2 Jul 2009 20:24:30 -0500 (CDT) From: Greg Rivers <gcr+freebsd-current@tharned.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: Panic during shutdown (cause identified) Message-ID: <alpine.BSF.2.00.0907021647001.1354@blue.tharned.org> In-Reply-To: <20090702194444.GK2884@deviant.kiev.zoral.com.ua> References: <alpine.BSF.2.00.0907011139490.75481@roadkill.tharned.org> <20090701192154.GW2884@deviant.kiev.zoral.com.ua> <alpine.BSF.2.00.0907011812490.1649@blue.tharned.org> <20090702084149.GE2884@deviant.kiev.zoral.com.ua> <alpine.BSF.2.00.0907020759300.1333@blue.tharned.org> <20090702194444.GK2884@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Jul 2009, Kostik Belousov wrote: > The information you provided about amd(8) causing the problem was > crusial. The issue is that amd locks its pages with mlockall(2), and > the code neglected to account the wired mappings, but did not forgot to > decrease their swap share on unmapping. > > Patch below fixed the issue for me. > [snip] > Confirmed: your patch fixes the issue for me as well. Thanks! -- Greg Rivers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0907021647001.1354>