From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 08:44:10 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FAA7106566B; Wed, 19 Jan 2011 08:44:10 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221]) by mx1.freebsd.org (Postfix) with ESMTP id BE9598FC15; Wed, 19 Jan 2011 08:44:09 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id p0J8i6Ru082616; Wed, 19 Jan 2011 14:44:06 +0600 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <4D36A451.6070902@rdtc.ru> Date: Wed, 19 Jan 2011 14:44:01 +0600 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7 MIME-Version: 1.0 To: lev@freebsd.org References: <1321946168.20110119001248@serebryakov.spb.ru> In-Reply-To: <1321946168.20110119001248@serebryakov.spb.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 8-STABLE/amd64 semi-regular crash with "kernel trap 12 with interrupts disabled" in "process 12 (swi4: clock)" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 08:44:10 -0000 On 19.01.2011 03:12, Lev Serebryakov wrote: > Hello, Freebsd-stable. > > > One of my servers crashes about once a week, with always same > diagnostics: "kernel trap 12 with interrupts disabled" and in same > process: "swi4: clock" > > It doesn't look as memory failure, as memtest86+ can not find any > errors in 8 passes. > > Also, after this crash server refuse to auto-reboot, last message on > console is "cpu_reset: Stopping other CPUs", and it hangs. > > Kernel config, booting dmesg & results of "savecore" are attached > (bzipped). There is known instability in em(4) driver in 8.2-RELEASE, it may panic due to some lack of NULL pointer checks. You should update to RELENG_8 containting fix and retest. Eugene Grosbein