From owner-freebsd-alpha  Sat Jul 14 10:37:53 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180])
	by hub.freebsd.org (Postfix) with ESMTP id 9DB3137B401
	for <alpha@FreeBSD.ORG>; Sat, 14 Jul 2001 10:37:50 -0700 (PDT)
	(envelope-from peter@wemm.org)
Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3])
	by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f6EHboM05818
	for <alpha@FreeBSD.ORG>; Sat, 14 Jul 2001 10:37:50 -0700 (PDT)
	(envelope-from peter@wemm.org)
Received: from wemm.org (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 63A9F380B; Sat, 14 Jul 2001 10:37:50 -0700 (PDT)
	(envelope-from peter@wemm.org)
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4
To: mjacob@feral.com
Cc: alpha@FreeBSD.ORG
Subject: Re: For those with persistant alpha trouble.... 
In-Reply-To: <Pine.BSF.4.21.0107140934590.87022-100000@beppo> 
Date: Sat, 14 Jul 2001 10:37:50 -0700
From: Peter Wemm <peter@wemm.org>
Message-Id: <20010714173750.63A9F380B@overcee.netplex.com.au>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-alpha.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-alpha>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-alpha>
X-Loop: FreeBSD.org

Matthew Jacob wrote:
> 
> > > The other alpha I have access to right now (UP2000 - SMP 2x21264) doesn't
> > > seem to care either way - it seems to work ok.  beast.freebsd.org (Miata
> > > MX5 - PWS500au) absolutely will not build world without it.
> 
> What was the crash stack on the Miata?

Hmm.  I thought I had a firmware PC, but instead it appears to be in
kernel space... From the conserver log file:

halted CPU 0

halt code = 2
kernel stack not valid halt
PC = fffffc000056f2a0

CPU 0 booting

I'm not sure if I have the kernel that corresponds to that crash. :-(
I *think* it is this one:
fffffc000056f1a0 T XentRestart
fffffc000056f238 T exception_return
fffffc000056f23c t Ler1
fffffc000056f268 t Lkernelret
fffffc000056f268 t Lrestoreregs
fffffc000056f28c t Lnohae
fffffc000056f2a0 T exception_save_regs  <<<<
fffffc000056f310 T exception_restore_regs
fffffc000056f380 t fp_add
fffffc000056f400 t fp_sub

Actually, they are all at this PC.  No ra or anything though.

On the may 24th kernel, it died with this:

fatal kernel trap:

    trap entry     = 0x2 (memory management fault)
    faulting va    = 0x51
    type           = access violation
    cause          = store instruction
    pc             = 0xfffffc0000521e4c
    ra             = 0xfffffc0000521e60
    sp             = 0xfffffe000865d9f8
    curproc        = 0xfffffe0007a33f80
        pid = 16, comm = swi3: cambio

panic: trap

fffffc0000521840 t initiate_write_inodeblock
fffffc0000521d00 t softdep_disk_write_complete  <<<< in here
fffffc00005221a0 t handle_allocdirect_partdone
fffffc0000522300 t handle_allocindir_partdone

Which I am not sure is useful...  I think that was probably one of the
softupdates bugs.

Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
"All of this is for nothing if we don't go to the stars" - JMS/B5


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message