From owner-freebsd-current@FreeBSD.ORG Sat Jun 26 13:59:44 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 4D2A616A4CE; Sat, 26 Jun 2004 13:59:44 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0564443D1D; Sat, 26 Jun 2004 13:59:44 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i5QDxQ2n011383; Sat, 26 Jun 2004 09:59:26 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i5QDxQD4011382; Sat, 26 Jun 2004 09:59:26 -0400 (EDT) Date: Sat, 26 Jun 2004 09:59:26 -0400 From: Ken Smith To: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040626135926.GA11221@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: HEADSUP - problem with -current on Alpha 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, 26 Jun 2004 13:59:44 -0000 This is just in case anyone is thinking about updating an Alpha box in the near future... The Alpha reference machine in the cluster has had problems with the kernel two days in a row. It basically spews a ton of messages about malloc(3) being called recursively when it tries to start the init process. I was able to track it down to a specific commit that causes it (sys/vm/vm_map.c rev 1.339) and I notified the people who would need to take a look at it. But at the moment we all kind of agree that what's happening doesn't make any sense given what the commit does. It's still being looked into but at the moment it seems possible this commit isn't the real cause of the problem, but it "aggravates" the issue(s) that have been causing some long-standing stability issues on Alpha (i.e. what Kris is seeing as instability on the ports building machines). This commit hasn't caused any problems we've seen on any architecture other than Alpha - the rest of the reference machines seem to be uneffected. Best to hold off on updating -current on an Alpha unless you want to help try to track down the problem... :-) -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |