Date: Sun, 29 Aug 2004 14:14:34 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Willem Jan Withagen <wjw@withagen.nl> Cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch Message-ID: <20040829141407.X69068@carver.gumbysoft.com> In-Reply-To: <41305056.7030905@withagen.nl> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> <412E23F0.1010006@withagen.nl> <412F30AF.4050404@withagen.nl> <20040827190730.J51306@carver.gumbysoft.com> <41305056.7030905@withagen.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 28 Aug 2004, Willem Jan Withagen wrote:
> Doug White wrote:
>
> >134 = 128 + signal number. Anyway, can you check your rev of
> >src/sys/kern/kern_lock.c? If its 1.74, please back up to a working
> >kernel, cvsup, and rebuild. That rev is bogus.
> >
> >
> But that has to take me beyond the RELENG_5 marker, right??
> Because after this mornings cvsup I still have:
> __FBSDID("$FreeBSD: src/sys/kern/kern_lock.c,v 1.74.2.1 2004/08/26
> 00:00:18 kan
>
> I'll get myself a -CURRENT tree as well just to track these kinds of things.
Thats correct for RELENG_5 -- thats the backout commit. HEAD has a
revised version of the original change, but RELENG_5 shouldn't be showing
corruption.
--
Doug White | FreeBSD: The Power to Serve
dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040829141407.X69068>