Date: Fri, 27 Aug 2004 15:01:35 +0200 From: Willem Jan Withagen <wjw@withagen.nl> To: Willem Jan Withagen <wjw@withagen.nl> Cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch Message-ID: <412F30AF.4050404@withagen.nl> In-Reply-To: <412E23F0.1010006@withagen.nl> References: <20040822115345.Y94593@carver.gumbysoft.com> <p0611040ebd4fe0bd637c@[128.113.24.47]> <20040826103652.F36995@carver.gumbysoft.com> <412E23F0.1010006@withagen.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> Signal 6 is SIGABRT, which is usually intentional. You'd have to >> check the >> output for a specific process that abended. I'd also have to scan the >> make code for any abort() calls. >> >> > I have not given it much attention yet, since I'm bussy doing other > things right now. > But on my dual AMD64 box compiling the current 5.3 Beta generated also > 'Abort Trap' while doing a > buildworld -j 32. Compiling without -j worked fine, and now I'm at 5.3 > B1, so I can test again. > It ws running a 5.3B1 kernel. > > I'll let you know if the problem persists The above was with last mondays kernel. This mornings 5.3B1 when running 'make -j 32 buildworld', did not generate any errors --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?412F30AF.4050404>