From owner-freebsd-ppc@FreeBSD.ORG Wed Feb 25 16:21:06 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D95361065674 for ; Wed, 25 Feb 2009 16:21:06 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id AE0128FC22 for ; Wed, 25 Feb 2009 16:21:06 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) id <0KFM00A1EQR6C400@smtpauth2.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Wed, 25 Feb 2009 10:21:06 -0600 (CST) Received: from trantor.tachypleus.net (adsl-99-154-1-172.dsl.mdsnwi.sbcglobal.net [99.154.1.172]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0KFM001S7QQW1X90@smtpauth2.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Wed, 25 Feb 2009 10:20:57 -0600 (CST) Date: Wed, 25 Feb 2009 10:21:52 -0600 From: Nathan Whitehorn To: FreeBSD PowerPC ML Message-id: <49A57020.1080603@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=99.154.1.172 X-Spam-PmxInfo: Server=avs-11, Version=5.5.1.360522, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2009.2.25.155236, SenderIP=99.154.1.172 User-Agent: Thunderbird 2.0.0.19 (X11/20090126) Subject: Brokenness in HEAD X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 16:21:07 -0000 Something seems to currently be quite broken in HEAD for PowerPC, at least on the AIM platform. I'm getting almost immediate panics all over the place in the kernel, usually indicating memory corruption somehow (faults on bogus addresses, illegal instructions, etc...). This is a heads-up to those thinking of updating systems or who might know what happened. The change is on order a week old, and I believe newer than the 20th. I have not done a full binary search yet, but it is not related to the following (checked by selective reversion of bits of the tree, or disabling bits): - USB code - ATA code - Anything in sys/powerpc (the Altivec import in particular) - Any changes to kernel compile flags or the contents of /usr/src/share/mk The panics seem to correlated with file system use (either UFS or NFS), but that may just be testing more code paths than a pure computational load. -Nathan