From owner-freebsd-current@FreeBSD.ORG Sat Aug 28 02:09:34 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 317F616A4CE for ; Sat, 28 Aug 2004 02:09:34 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 231A343D2D for ; Sat, 28 Aug 2004 02:09:34 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 102DF72DD4; Fri, 27 Aug 2004 19:09:34 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 0BDE672DCB; Fri, 27 Aug 2004 19:09:34 -0700 (PDT) Date: Fri, 27 Aug 2004 19:09:34 -0700 (PDT) From: Doug White To: Willem Jan Withagen In-Reply-To: <412F6564.9080800@withagen.nl> Message-ID: <20040827190730.J51306@carver.gumbysoft.com> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> <412E23F0.1010006@withagen.nl> <412F30AF.4050404@withagen.nl> <412F6564.9080800@withagen.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Sat, 28 Aug 2004 02:09:34 -0000 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@gumbysoft.com | www.FreeBSD.org