From owner-freebsd-amd64@FreeBSD.ORG Wed May 11 19:27:23 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 DF15316A4CE for ; Wed, 11 May 2005 19:27:23 +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 B737243D1D for ; Wed, 11 May 2005 19:27:23 +0000 (GMT) (envelope-from kwsn@earthlink.net) Received: from dialup-4.240.105.201.dial1.phoenix1.level3.net ([4.240.105.201] helo=jonnyv.kwsn.lan) by pop-a065c10.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DVwra-0000N6-00; Wed, 11 May 2005 12:27:23 -0700 From: Jon Kuster To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Wed, 11 May 2005 12:27:20 -0700 Message-Id: <1115839640.59966.12.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: 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: Wed, 11 May 2005 19:27:24 -0000 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 uname -a FreeBSD ni.kwsn.net 5.4-STABLE FreeBSD 5.4-STABLE #2: Wed May 11 01:06:43 EDT 2005 root@ni.kwsn.net:/usr/obj/usr/src/sys/NISMP amd64 Other than commenting out devices that we don't have, the only options I've added to GENERIC, are SMP, HZ=1000, and makeoptions DEBUG=-g options KDB options KDB_TRACE options DDB options GDB options KDB_UNATTENDED -Jon