Date: Mon, 21 May 2001 14:52:32 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-alpha@freebsd.org Subject: RE: state of -current Message-ID: <15113.25584.137152.821338@grasshopper.cs.duke.edu> In-Reply-To: <XFMail.010521111146.jhb@FreeBSD.org> References: <15113.16250.74238.202983@grasshopper.cs.duke.edu> <XFMail.010521111146.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin writes: > > > 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: <...> > Well, my alpha is running a UP kernel that is after the last big SMP commmit > where I shuffled things around to MI places and what not. Right now I'm still > trying to review Alfred's patch. Once vm is back to working at all I'll try > and look at this one as it may be my fault. I think I may be going crazy. I can no longer get this to happen. Booting a kernel that triggered it yesterday no longer triggers it today. Ahhhhhhaa! Drew 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.25584.137152.821338>