PLEASE TEST: IPI deadlock avoidance patch
Doug White
dwhite at gumbysoft.com
Fri Aug 27 19:09:34 PDT 2004
On Fri, 27 Aug 2004, Willem Jan Withagen wrote:
> make -j 64 buildworld did generate quite few errors on the second run.....
>
> This is AMD-64 on a dual opteron system:
> config, dmesg, uname =>
> htttp://withagen.dyndns.org/FreeBSD/cores/opteron.tyan.106.{config,dmesg,uname}
>
> Things are like:
> ===> sbin/devfs
> cc -pipe -g -Wsystem-headers -Wall -Wno-format-y2k -W
> -Wstrict-prototypes -Wmis
> sing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> -Wwrite-strings -Wswit
> ch -Wshadow -Wcast-align -c /home2/src/sbin/devfs/rule.c
> cc -pipe -g -Wsystem-headers -Wall -Wno-format-y2k -W
> -Wstrict-prototypes -Wmis
> sing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> -Wwrite-strings -Wswit
> ch -Wshadow -Wcast-align -c /home2/src/sbin/devfs/devfs.c
> gzip -cn /home2/src/sbin/devfs/devfs.8 > devfs.8.gz
> *** Signal 6
> cc -pipe -g -o chat chat.o
> *** Error code 134
Random signals are nice.
> Not shure who writes these Error code 134?? If it is make, then it
> should perhaps in the '-j X' version have the executed command (and
> working directory) appended. Gives a better indication where things go
> haywire.
> But in the current output there is no telling who aborted what.
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.
--
Doug White | FreeBSD: The Power to Serve
dwhite at gumbysoft.com | www.FreeBSD.org
More information about the freebsd-current
mailing list