Date: Sat, 28 Aug 2004 11:28:54 +0200 From: Willem Jan Withagen <wjw@withagen.nl> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch Message-ID: <41305056.7030905@withagen.nl> In-Reply-To: <20040827190730.J51306@carver.gumbysoft.com> References: <20040822115345.Y94593@carver.gumbysoft.com> <p0611040ebd4fe0bd637c@[128.113.24.47]> <20040826103652.F36995@carver.gumbysoft.com> <412E23F0.1010006@withagen.nl> <412F30AF.4050404@withagen.nl> <412F6564.9080800@withagen.nl> <20040827190730.J51306@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
--WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41305056.7030905>