From owner-freebsd-current@FreeBSD.ORG Thu Apr 30 16:09:31 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5BD510656C1 for ; Thu, 30 Apr 2009 16:09:31 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0675C8FC1A for ; Thu, 30 Apr 2009 16:09:30 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA03989; Thu, 30 Apr 2009 19:09:09 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <49F9CD25.70102@icyb.net.ua> Date: Thu, 30 Apr 2009 19:09:09 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: David Wolfskill , current@freebsd.org References: <20090429161626.GQ1387@albert.catwhisker.org> <20090430151830.GW1387@albert.catwhisker.org> <49F9C544.3060509@icyb.net.ua> <20090430155817.GY1387@albert.catwhisker.org> In-Reply-To: <20090430155817.GY1387@albert.catwhisker.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: Subject: Re: Panic "Fatal trap 18: integer divide fault while in kernel mode" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2009 16:09:32 -0000 on 30/04/2009 18:58 David Wolfskill said the following: > On Thu, Apr 30, 2009 at 06:35:32PM +0300, Andriy Gapon wrote: >> on 30/04/2009 18:18 David Wolfskill said the following: >>> On Wed, Apr 29, 2009 at 09:16:26AM -0700, David Wolfskill wrote: >>>> Is there anything of use I might get from DDB? >>> I can still poke around there for a bit, if that would be useful. >> In general the stack trace[*] should be provided at the very least, otherwise >> people have hard figuring out where the problem occurred, so right people may just >> not notice a report. > > Sorry; it happened so quickly, I wasn't at all certain there would be > enough to show: > > db> bt > Tracing pid 0 tid 100000 td 0xc0d43610 > cpu_topo(2,c1420d34,c081ff07,c1420d58,c0820042,...) at cpu_topo+0x43 > smp_topo(c0804378,2,c4145a5c,fffffff,0,...) at smp_topo+0x10b > sched_setup(0,141ec00,141ec00,141e000,1425000,...) at sched_setup+0x1a > mi_startup() at mi_startup+0x96 > begin() at begin+0x2c My guess is that (cpu_cores * cpu_logical) somehow equals to zero. Have you by a chance saved this crash dump? I think that t would be interesting to look at it in kgdb. -- Andriy Gapon