From owner-freebsd-bugs Thu Nov 2 07:32:25 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA03278 for bugs-outgoing; Thu, 2 Nov 1995 07:32:25 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA03261 for ; Thu, 2 Nov 1995 07:32:21 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id HAA17796 for ; Thu, 2 Nov 1995 07:29:53 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA15251; Thu, 2 Nov 1995 16:23:29 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id QAA10073; Thu, 2 Nov 1995 16:23:28 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id LAA25425; Thu, 2 Nov 1995 11:04:38 +0100 From: J Wunsch Message-Id: <199511021004.LAA25425@uriah.heep.sax.de> Subject: Re: "page fault" kernel panic To: pgrey@jamrock.esd.sgi.com (Paul Grey) Date: Thu, 2 Nov 1995 11:04:38 +0100 (MET) Cc: bugs@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199511020748.XAA02339@jamrock.esd.sgi.com> from "Paul Grey" at Nov 1, 95 11:48:47 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1051 Sender: owner-bugs@freebsd.org Precedence: bulk As Paul Grey wrote: > > (kgdb) up > #4 0xf019a407 in trap (frame={tf_es = -272695280, tf_ds = -260964336, > tf_edi = 2513652, tf_esi = 4308992, tf_ebp = -272641364, > tf_isp = -272629856, tf_ebx = 2510848, tf_edx = 815260928, > tf_ecx = 610000, tf_eax = 32, tf_trapno = 12, tf_err = -272695294, > tf_eip = -266792497, tf_cs = -272695288, tf_eflags = 65538, tf_esp = 0, > tf_ss = 0}) at ../../i386/i386/trap.c:290 > 290 (void) trap_pfault(&frame, FALSE); > (kgdb) frame frame->tf_ebp frame->tf_eip > Cannot access memory at address 0xefbfd2ac. Hmm, that's unfortunately not of much use. :-( Paul, next time it happens, can you please do the following: * note the EIP value that is printed in the panic message, and * perform an ``nm /kernel | sort | more'', look up the area around the failing EIP value, and post this? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)