Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 May 2001 12:16:58 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        freebsd-alpha@freebsd.org
Subject:   state of -current
Message-ID:  <15113.16250.74238.202983@grasshopper.cs.duke.edu>

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

I just committed some fixes which should get alpha booting again after
Alfred's vm_mtx introduction.   Alpha has not been heavily tested with
the vm_mtx.

Note that I did not remove Giant from the fault path in trap -- my
goal was to get the system to boot and be stable, not to improve
performance.  If somebody else would like to do this, please go ahead.

When doing this, I noticed that non-SMP alpha kernels will no longer
boot multi-user due to a recently forked process showing up a
'curproc' during a hardclock intr.  The process hasn't been fully
setup and accessing some fields in its proc struct causes a trap with
a stack like this:

hardclock_process() at hardclock_process+0xc0
hardclock() at hardclock+0x11c
handleclock() at handleclock+0x22c
alpha_clock_interrupt() at alpha_clock_interrupt+0x48
interrupt() at interrupt+0xa8
XentIntlgp() at XentIntlgp+0x14

The fault in hardclock_process is from accessing
&pstats->p_timer[ITIMER_PROF].it_value.  Many fields in this proc are
null, including p->p_addr (which causes an essentially recursive fault
in trap, leading to a KSP not valid halt).

This is almost certainly due to some of the SMP integration work.  I
just noticed it yesterday and don't have time to track it down more
than this.  So, if you're going to use alpha on -current, use an SMP
kernel for now :-(

Drew

------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer	http://www.cs.duke.edu/~gallatin
Duke University				Email: gallatin@cs.duke.edu
Department of Computer Science		Phone: (919) 660-6590


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15113.16250.74238.202983>