Date: Thu, 29 Mar 2012 10:55:52 +0300 From: Volodymyr Kostyrko <c.kworr@gmail.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: stable@FreeBSD.org Subject: Re: trap 12 on 9.0 when memcache gets some load [resolved] ZERO_COPY trap Message-ID: <4F741588.9000202@gmail.com> In-Reply-To: <4F71E482.7060509@FreeBSD.org> References: <4F71E14A.8010605@gmail.com> <4F71E482.7060509@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andriy Gapon wrote: > on 27/03/2012 18:48 Volodymyr Kostyrko said the following: >> Hi all. >> >> I'm just puzzled with this. At first I though this happens because of some memory >> problems. But now project was moved to another server with some other brands for >> motherboard/memory and different cpu's. And still once in an hour this happens again: >> >> == screenshot >> current_process = 1935 (memcached) >> trap number = 12 >> panic: page fault >> cpuid = 2 >> KDB: stack backtrace: >> #0 0xffffffff8038ab38 at kdb_backtrace+0x58 >> #1 0xffffffff80358f80 at panic+0x190 >> #2 0xffffffff80567b15 at trap_fatal+0x395 >> #3 0xffffffff80567ce9 at trap_pfault+0x1c9 >> #4 0xffffffff80567536 at trap+0x3a6 >> #5 0xffffffff80552603 at calltrap+0x8 >> #6 0xffffffff803b2c90 at socow_setup+0xd0 > > I think that zero-copy sockets are not regarded as a reliable feature. > Not an expert, just my two cents. Disabling zero_zopy seems to work as server still runs after 12 hours. Before that one hour was enough to trigger error. kern.ipc.zero_copy.receive: 0 kern.ipc.zero_copy.send: 0 -- Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F741588.9000202>