From owner-freebsd-current Wed Apr 30 23:07:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA12131 for current-outgoing; Wed, 30 Apr 1997 23:07:03 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA12124 for ; Wed, 30 Apr 1997 23:06:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id XAA25008; Wed, 30 Apr 1997 23:08:13 -0700 (PDT) Message-Id: <199705010608.XAA25008@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Christoph Kukulies cc: freebsd-current@freefall.FreeBSD.ORG Subject: Re: panic in vm In-reply-to: Your message of "Tue, 29 Apr 1997 18:00:03 +0200." <199704291600.SAA02644@gilberto.physik.rwth-aachen.de> From: David Greenman Reply-To: dg@root.com Date: Wed, 30 Apr 1997 23:08:13 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Apr 29 16:12:39 toots /kernel: Fatal trap 1: privileged instruction fault while in kernel mode >Apr 29 16:12:39 toots /kernel: instruction pointer = 0x8:0xf019f837 >Apr 29 16:12:39 toots /kernel: stack pointer = 0x10:0xefbff790 >Apr 29 16:12:39 toots /kernel: frame pointer = 0x10:0xefbff7dc >Apr 29 16:12:39 toots /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b >Apr 29 16:12:40 toots /kernel: = DPL 0, pres 1, def32 1, gran 1 >Apr 29 16:12:40 toots /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 >Apr 29 16:12:40 toots /kernel: current process = 106 (nfsd) >Apr 29 16:12:40 toots /kernel: interrupt mask = bio >Apr 29 16:12:40 toots /kernel: panic: privileged instruction fault >Apr 29 16:12:40 toots /kernel: >Apr 29 16:12:40 toots /kernel: syncing disks... 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 > >from kernel symbol table: >f019f7cc t _vm_map_entry_delete >f019f820 T _vm_map_delete <<<<<<<<< ip = f019f837 >f019f9a8 T _vm_map_remove >f019fa5c T _vm_map_check_protection > >Were there fixes or changes in 2.2.1R or 3.0-current in that area, >that would make it necessary upgrading the machine? The above smells strongly of a RAM or cache problem (or overclocked CPU?). The instruction that the CPU decoded within the function was invalid. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project