From owner-freebsd-stable Wed Feb 19 6:13:26 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E32537B401 for ; Wed, 19 Feb 2003 06:13:24 -0800 (PST) Received: from nippur.irb.hr (nippur.irb.hr [161.53.128.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1387243F3F for ; Wed, 19 Feb 2003 06:13:23 -0800 (PST) (envelope-from mario.pranjic@irb.hr) Received: from localhost (keeper@localhost) by nippur.irb.hr (8.9.3/8.9.3) with ESMTP id PAA10171 for ; Wed, 19 Feb 2003 15:13:21 +0100 (MET) Date: Wed, 19 Feb 2003 15:13:21 +0100 (MET) From: Mario Pranjic To: Subject: Fatal trap 12: page fault while in kernel mode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! For the last few days I'm expiriencing a strange crashes: when I try to cvsupdate+portsdb ports tree I get the weird errors and machine crashes (automatically rebooted) One I got this error: panic: ufsdirhash_lookup: bad offset in hash array. This time I got this one: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3c fault code = supervisor read, page not present instruction pointer = 0x8:0xc0309bca stack pointer = 0x10:0xcda58bf8 frame pointer = 0x10:0xcda58be8 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 = 1951 (make) interrupt masks = none trap number = 12 panic: page fault The system is Athlon 700 MHz, 256 MB ECC RAM, 2 Seagate IDE disks (40 and 80 gigs), 1 SCSI Seagate disk (36 GB). First I suspected that a power suply is malfunctioning, so I've changed it. Didn't help. though. I ran soime fsck on drives and it seems that disks are OK. What could possibly be so wrong? The machine is online for about a year and it worked fine till now. Is there a possibility that a memory chip is dead (or should I say deadish)? Thanks for your help! Mario Pranjic, dipl.ing. sistem administrator Knjiznica, Institut Rudjer Boskovic ------------------------------------- e-mail: mario.pranjic@irb.hr ICQ: 72059629 tel: +385 1 45 60 954 (interni: 1293) ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message