PLEASE TEST: IPI deadlock avoidance patch
Dan Nelson
dnelson at allantgroup.com
Mon Aug 23 19:28:51 PDT 2004
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 at allantgroup.com
More information about the freebsd-current
mailing list