From owner-freebsd-amd64@FreeBSD.ORG Fri May 13 06:24:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2949716A4CE for ; Fri, 13 May 2005 06:24:53 +0000 (GMT) Received: from pop-a065c10.pas.sa.earthlink.net (pop-a065c10.pas.sa.earthlink.net [207.217.121.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F7143D5C for ; Fri, 13 May 2005 06:24:52 +0000 (GMT) (envelope-from kwsn@earthlink.net) Received: from dialup-4.240.6.32.dial1.phoenix1.level3.net ([4.240.6.32] helo=jonnyv.kwsn.lan) by pop-a065c10.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DWTbP-0007lZ-00; Thu, 12 May 2005 23:24:52 -0700 From: Jon Kuster To: freebsd-amd64@freebsd.org In-Reply-To: <1115839640.59966.12.camel@jonnyv.kwsn.lan> References: <1115839640.59966.12.camel@jonnyv.kwsn.lan> Content-Type: text/plain Date: Thu, 12 May 2005 23:24:50 -0700 Message-Id: <1115965490.59966.18.camel@jonnyv.kwsn.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: toby.murray@gmail.com Subject: Re: Panic while running jdk15 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kwsn@earthlink.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2005 06:24:53 -0000 On Wed, 2005-05-11 at 12:27 -0700, Jon Kuster wrote: > After we managed to get jdk15 built and then shipped our box to the > colo, it has started panicing. We haven't been able to reliably > reproduce this yet, but it always happens when our java program is doing > it's thing. > > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id=00 > fault virtual address = 0x1c0 > fault code = supervisor write, page not present > instruction pointer = 0x8 :0xffffffff80382348 > stack pointer = 0x10 :0xffffffff7935aa0 > frame pointer = 0x10 :0xffffffff7935ae0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 6503 (sh) > > I haven't been able to get a dump yet, or even a trace in ddb - our > remote management card apparently emulates a usb keyboard which doesn't > seem to work when the box is paniced. > > nm -n /boot/kernel/kernel |grep ffffffff803823 > ffffffff80382330 T cpu_throw > ffffffff80382380 T cpu_switch We've switched off Hyperthreading (we're running em64T xeons), and that seems to have worked around the problem. It's a little too early to say for sure, but we were seeing panics twice a day, and we haven't had a panic in about a day and a half. -Jon