Date: Tue, 24 Jul 2007 01:23:29 +0200 From: "Attilio Rao" <attilio@freebsd.org> To: "Jeff Roberson" <jroberson@chesapeake.net> Cc: current@freebsd.org, Matt <datahead4@gmail.com> Subject: Re: ULE status, invalid load, buildkernel times. Message-ID: <3bbf2fe10707231623r1390b1a2r52c2830831621245@mail.gmail.com> In-Reply-To: <46A52B19.9060909@FreeBSD.org> References: <20070721174631.S561@10.0.0.1> <cd6b4a5b0707231313o1256c80aj596e32a1ff9e50f6@mail.gmail.com> <20070723152212.O561@10.0.0.1> <46A52B19.9060909@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2007/7/24, Attilio Rao <attilio@freebsd.org>: > Jeff Roberson wrote: > > > > I suspect that this is unrelated to my patch but I can't say for > > certain. There have been some kse locking problems that Attilio has a > > patch for. I believe it went in today. Hopefully he will comment. > > This is exactly the same bug pav@ experienced on amd64 machines some > weeks ago. > Basically, there is a race with ku_owner accesses which make it > unconsistent in SMP / PREEMPTION systems. > I committed a fix for that, but since I broke buildkernel too with that > commit I would suggest to wait until the fix for a correct kernel > building won't be committed (it should be rather soon though) and than > to CVSup again sources. Ok, this is the good moment for a CVSup. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10707231623r1390b1a2r52c2830831621245>