On Mon, 18 May 2009, Adam McDougall wrote: > I'm not sure if this is related to recent kernel memory code changes > or what, but it hasn't happened with code from earlier than a couple > days ago. I had this happen twice, I think the first time was with > arc max set to 1024M, the second time was when arc max was unset in > loader.conf and the system had been up a few hours but the arc hadn't > been squeezed down to a small number yet: > Mem: 719M Active, 12G Inact, 3413M Wired, 2608K Cache, 24M Buf, 3741M Free > > I've deleted the kernel since then but I did not change my sources, > I could build a new one and check where the pointers point to I think? > If needed. Or I could reproduce the panic if needed. It doesn't dump, > it just gets stuck after printing the panic. I wonder if this is the same crash I saw without getting all the info. What I saw was the wired memory getting to be most of the memory on the box, and then boom. see my post a few above this. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler_at_lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893Received on Mon May 18 2009 - 13:48:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:47 UTC