Date: Fri, 10 May 2002 14:57:03 -0500 From: Alan Cox <alc@cs.rice.edu> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: alpha@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: gcc3 & alpha kernels Message-ID: <20020510195703.GB13871@cs.rice.edu> In-Reply-To: <15580.9475.2695.221222@grasshopper.cs.duke.edu> References: <20020510194133.GA13871@cs.rice.edu> <15580.9475.2695.221222@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 10, 2002 at 03:52:35PM -0400, Andrew Gallatin wrote: > > Alan Cox writes: > > > I do NOT know if this was the fault of gcc3, but it smells like it. > > > According to nm, this address is in _vm_object_allocate(). A few > > > other times, it locked with an address in what looked like mlock(). > > > > A few days ago Jeff Robertson had a problem in this neighborhood > > on alpha triggered by an atomic_cmpset_int() that I had introduced > > in _vm_object_allocate(). He resolved with the following change > > to src/sys/alpha/include/atomic.h: > > > > Revision 1.12 / (download) - annotate - [select for diffs], Wed May 8 05:19:56 2002 UTC (2 days, 13 hours ago) by jeff > > Branch: MAIN > > CVS Tags: HEAD > > Changes since 1.11: +2 -1 lines > > Diff to previous 1.11 (colored) > > > > zapnot the signed bits in atomic_cmpset_32. Previously this did not work with > > negative values because the original value was sign extended but the compared > > value was not. > > > > If I'm not mistaken, prior to this change, he locked up > > in _vm_object_allocate() much as Andrew described. > > Did Jeff see a lockup at boot? Or was this on a running system? I believe it was at boot time. I can't swear to that, however. Alan 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?20020510195703.GB13871>