From owner-freebsd-current@FreeBSD.ORG Fri Aug 27 16:46:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0407B16A4CE for ; Fri, 27 Aug 2004 16:46:35 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7D2943D46 for ; Fri, 27 Aug 2004 16:46:33 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i7RGkSEg098187; Fri, 27 Aug 2004 18:46:28 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <412F6564.9080800@withagen.nl> Date: Fri, 27 Aug 2004 18:46:28 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Willem Jan Withagen References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> <412E23F0.1010006@withagen.nl> <412F30AF.4050404@withagen.nl> In-Reply-To: <412F30AF.4050404@withagen.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Aug 2004 16:46:35 -0000 Willem Jan Withagen wrote: > >>> >>> 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 I'm sorry to report that I was to fast with reporting good news..... 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 ===> usr.bin/checknr 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 -o devfs devfs.o rule.o cc -pipe -g -c /home2/src/usr.bin/checknr/checknr.c gzip -cn /home2/src/usr.bin/checknr/checknr.1 > checknr.1.gz ===> sbin/dhclient *** Error code 134 ===> sbin/dhclient/common ===> bin/expr *** Error code 134 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. --WjW