Date: Mon, 23 Aug 2004 21:28:50 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch Message-ID: <20040824022849.GE36920@dan.emsphone.com> In-Reply-To: <p06110410bd504a081165@[128.113.24.47]> References: <20040822115345.Y94593@carver.gumbysoft.com> <p0611040ebd4fe0bd637c@[128.113.24.47]> <20040824005149.GG77326@green.homeunix.org> <p06110410bd504a081165@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 23), Garance A Drosihn said: > At 8:51 PM -0400 8/23/04, Brian Fundakowski Feldman wrote: > >On Mon, Aug 23, 2004, Garance A Drosihn wrote: > > > [...] No panics, but in the second set I > > > did have one buildworld (-j9) which failed with four processes > >> apparently getting a "*** Signal 6". I am not sure what that > >> was about. Note that all these builds were done with a `make' > >> that was compiled to USE_KQUEUE , so maybe that's where the > >> Signal's came from. In any case, the machine is still running > >> fine, even after that heavy pounding. > > > >Are you watching system temperatures? > > I doubt that's a problem right now. Right now my office is pretty > chilly, and it was even cooler last night while these were running. > This is the first time I've seen these "*** Signal 6"s, and this is > also the first time I've tried a USE_KQUEUE verison of `make'. And > while the make-related processes died with the signal's, none of the > other processes on the system had any problems. (including the > folding-at-home client which is still running on the machine). Signal 6 (SIGABRT) is usually caused by an assert or other deliberate action. Scroll back up in the log and see if you can find any error messages. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040824022849.GE36920>