Date: Thu, 16 Nov 2006 12:00:15 +0300 From: Dmitriy Kirhlarov <dimma@higis.ru> To: freebsd-stable@freebsd.org Subject: Re: RELENG_6 panic under heavy load Message-ID: <20061116090014.GB1132@dimma.mow.oilspace.com> In-Reply-To: <20061115203740.GA31455@xor.obsecurity.org> References: <20061113084430.GE59604@dimma.mow.oilspace.com> <20061113184505.GA51659@xor.obsecurity.org> <20061114075020.GA1154@dimma.mow.oilspace.com> <20061114185344.GA89030@xor.obsecurity.org> <20061115182420.GA1132@dimma.mow.oilspace.com> <20061115203740.GA31455@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 15, 2006 at 03:37:40PM -0500, Kris Kennaway wrote: > On Wed, Nov 15, 2006 at 09:24:21PM +0300, Dmitriy Kirhlarov wrote: > > On Tue, Nov 14, 2006 at 01:53:45PM -0500, Kris Kennaway wrote: > > > > > From alc@: > > > > > > --- > > > I've never seen anything like this before. UMA is failing to allocate > > > the zone structure. This is unrelated to the large-swap scenario that > > > you ran into. Ask him to uncomment all of the UMA debugging #define's > > > at the start of uma_core.c. > > > > It was very painfull for me and I don't get result... > > > > #define UMA_DEBUG 1 > > #define UMA_DEBUG_ALLOC 1 > > #define UMA_DEBUG_ALLOC_1 1 > > > > in uma_core.c kill my machine. > > I get tons of crap to serial console. > > The "tons of crap" is what was necessary to proceed. Not shure. I can't find way for collect output of UMA_DEBUG* with current console server and it can't be replaced before Jan. But I think UMA* is a wrong idea. You suppose bad hardware (I'm right?). Possible. But it can be detected only under heavy load -- when I enabling nagios on this server. When nagios disabled, machine work perfectly. With enabled UMA_DEBUG* options server not operable, no one service starting, we don't have this load and can't reproduce this behaviour. WBR Dmitriy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061116090014.GB1132>