Date: Thu, 2 Jul 2009 20:49:19 +0000 From: pluknet <pluknet@gmail.com> To: Kostik Belousov <kostikbel@gmail.com> Cc: alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: Panic during shutdown (cause identified) Message-ID: <a31046fc0907021349n5a891ae3qbde2adb22f460225@mail.gmail.com> 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
2009/7/2 Kostik Belousov <kostikbel@gmail.com>: > On Thu, Jul 02, 2009 at 11:37:01AM -0500, Greg Rivers wrote: >> Please let me know if I can help with further testing/debugging. BTW, I >> did not customize the amd configuration; I was using the stock >> configuration from the base system. > > 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. I can confirm that simply staring amd(8) daemon and then reboot would cause such panic in swap accounting. I saw a dozen messages "negative vmsize for uid = 0" in time just before panic. This patch fixes that for me. my 2c. -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0907021349n5a891ae3qbde2adb22f460225>