From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 07:32:38 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 220D416A4CE for ; Wed, 13 Apr 2005 07:32:38 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCA4943D45 for ; Wed, 13 Apr 2005 07:32:37 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from [213.225.74.166] (helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1DLcMW-0000i3-WF for current@freebsd.org; Wed, 13 Apr 2005 09:32:37 +0200 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Wed, 13 Apr 2005 09:32:35 +0200 From: Eirik =?ISO-8859-1?B?2A==?=verby To: "current@freebsd.org" Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Panic after "in_cksum_skip: out of data by 260" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 13 Apr 2005 07:32:38 -0000 Hi, Today I received this message on my serial console: in_cksum_skip: out of data by 260 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 00 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc066ec33 stack pointer = 0x10:0xd5437974 frame pointer = 0x10:0xd5437998 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 36 (swi1: net) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#0 Uptime: 1d15h8m10s This server has been very stable for a very long time. This crash surprises me somewhat. Uname output: FreeBSD carnen.net 5.3-STABLE FreeBSD 5.3-STABLE #0: Wed Feb 2 21:02:44 CET 2005 root@carnen.net:/usr/obj/usr/src/sys/CARNEN i386 Any idea what could have caused this? Thanks, /Eirik