m convinced that it's hardware-
related, but I don't know which piece (I've already replaced both
memory and motherboard to no avail) to blame.
This morning, I received the following panic, and the machine
dropped into debug (Please forgive any spacing or form errors,
as I had to copy
On Wed, 30 Aug 2000, Evan Tsoukalas wrote:
> Hello all,
>
> In the past couple of weeks, I've been getting pretty regular
> crashes and reboots on one of my machines (dmesg attached). I
> tried to cvsup it to the latest -CURRENT, but I kept getting
> strange assembler and cc errors during make
On Thu, Aug 31, 2000 at 02:08:28PM -0700, Doug White wrote:
> This is usually indicitive of bad memory. Replace your memory modules.
I've seen some people have those same errors on the lists before,
so I did; twice. First, with a replacement set of the same manufacturer
256meg ECC dimms (Mic
On Thu, Aug 31, 2000 at 06:50:22PM -0400, Evan Tsoukalas wrote:
> The following morning, I came in to find the panic I described in
> my previous post. I was hoping that, to some far more
> knowledgeable than I, that panic and trace would point the finger
> at a specific piece of hardware. FWIW
On Thu, 31 Aug 2000, Evan Tsoukalas wrote:
> On Thu, Aug 31, 2000 at 02:08:28PM -0700, Doug White wrote:
>
> > This is usually indicitive of bad memory. Replace your memory modules.
>
> I've seen some people have those same errors on the lists before,
> so I did; twice. First, with a replace
Hello all,
Just wanted to thank everyone for their response to my August
30th EDT post. Especially to Doug White, who offered up the correct
solution in telling me to replace the CPU cache and saved me from
having to futilely swap RAID cards. After more than thirty straight
days without a cras
bento was running 5.1-BETA from May 5, and it crashed overnight with:
panic: pmap_release: pmap resident count 1 != 0
cpuid = 1; lapic.id =
Dumping 1024 MB
16 32[CTRL-C to abort] [CTRL-C to abort] 48 64 80 96 112 128 144 160 176 192 208 224
240 256 272 288 304 320 336 352 368 384 400
