From owner-freebsd-current Wed Feb 26 11:04:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA26181 for current-outgoing; Wed, 26 Feb 1997 11:04:26 -0800 (PST) Received: from watson.grauel.com (watson.grauel.com [199.233.104.36]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26175 for ; Wed, 26 Feb 1997 11:04:23 -0800 (PST) Received: (from rjk@localhost) by watson.grauel.com (8.8.5/8.7.3) id OAA15353; Wed, 26 Feb 1997 14:04:31 -0500 (EST) Date: Wed, 26 Feb 1997 14:04:31 -0500 (EST) Message-Id: <199702261904.OAA15353@watson.grauel.com> From: Richard J Kuhns To: freebsd-current@freebsd.org Subject: some recent panics Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The most recent (as of about 1000 EST 2/26/97) kernel seems to be extremely fragile; it takes very little disk activity on my ASUS P5-120/64 MB RAM to cause a panic (4 in the past 2 hours). I know -current is dangerous to run and being worked on, and I'm not complaining, I'm just sending this on the chance it may be useful to someone... === Panic message: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf23a2600 fault code = supervisor read, page not present instruction pointer = 0x8:0xf012dd48 stack pointer = 0x10:0xefbffd24 frame pointer = 0x10:0xefbffd30 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 = 265 (wish4.2) interrupt mask = panic: page fault syncing disks... === kernel info around instruction pointer: f012dcd0 F vfs_cache.o f012dcd0 t _sysctl___debug_vfscache f012dcf8 t ___set_sysctl__debug_sym_sysctl___debug_vfscache f012dcfc T _cache_lookup f012dfa8 T _cache_enter f012e0f0 T _nchinit f012e124 T _cache_purge f012e1fc T _cache_purgevfs -- Rich Kuhns rjk@grauel.com PO Box 6249 Tel: (317)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 /