Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Jan 2004 19:50:52 -0500 (EST)
From:      Robert Watson <rwatson@freebsd.org>
To:        Stanislav Grozev <tacho@orbitel.bg>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: FreeBSD constantly crashing
Message-ID:  <Pine.NEB.3.96L.1040127194815.52216A-100000@fledge.watson.org>
In-Reply-To: <20040127053642.GA10191@octavo.daemonz.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Tue, 27 Jan 2004, Stanislav Grozev wrote:

> I have one FreeBSD server, that recently started to behave strangely. 
> It has been rock-solid for all of its existence (almost 2 years). 
> Recently I upgraded it to RELENG_4_9 and it started crashing with kernel
> panic approximately every 24 hours, but this varies.  I have tried
> downgrading to RELENG_4_8 and RELENG_4_7 - the same thing keeps
> happening. I have also moved the harddrives in a brand new, albeit
> identical machine - Duron 800 MHz, 512MB RAM, Adaptec 29160 Ultra 160
> SCSI, two Fujitsu disks in Vinum RAID1. 
> 
> Here is the kernel panic:
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x485974e2
> fault code              = supervisor read, page not present
> instruction pointer     = 0x8:0xc01cbfe3
> stack pointer           = 0x10:0xc0311854
> frame pointer           = 0x10:0xc0311858
> 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         = Idle
> interrupt mask          = 
> trap number             = 12
> panic: page fault
> 
> attached are the kernel configuration and the dmesg.  Please, can anyone
> shed any light on this? I thought it was the hardware, but I've changed
> everything except the hard disks - new case, new powersupply, new
> motherboard, new processor, new RAM, new Adaptec. 

Are you able to get a crash dump, or compile in DDB and get a stack trace?
Does seem odd that the problem would persist after a downgrade -- can you
confirm that you don't have any kernel modules that are out of sync with
your current kernel source?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research


> 
> Thanks in advance.
> 
> -tacho
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040127194815.52216A-100000>