2009/7/2 Kostik Belousov <kostikbel_at_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, pluknetReceived on Thu Jul 02 2009 - 18:49:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:51 UTC