From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 20 08:09:11 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AADC416A4CE for ; Tue, 20 Jan 2004 08:09:11 -0800 (PST) Received: from lakemtao01.cox.net (lakemtao01.cox.net [68.1.17.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7492043D6A for ; Tue, 20 Jan 2004 08:08:44 -0800 (PST) (envelope-from brian@shadowcom.net) Received: from shadowcom.net ([68.100.212.237]) by lakemtao01.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20040120160844.ZMSI2413.lakemtao01.cox.net@shadowcom.net> for ; Tue, 20 Jan 2004 11:08:44 -0500 Received: (qmail 1607 invoked by uid 500); 20 Jan 2004 16:08:43 -0000 Date: Tue, 20 Jan 2004 11:08:43 -0500 From: Brian Ledbetter To: freebsd-hackers@freebsd.org Message-ID: <20040120160843.GA1289@shadowcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Curious problem w/ 5.2-RELEASE su X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 16:09:11 -0000 I have two systems which I recently upgraded from src to 5.2-RELEASE. (Both systems were upgraded from the same /usr/src tree) Everything seemed to be working fine until a little while ago this morning, when I started having this problem with /usr/bin/su: $ su - su in free(): error: chunk is already free Abort trap (core dumped) $ sudo sh $ id uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) $ su - su in free(): error: chunk is already free Abort trap (core dumped) Does anyone have any idea what would be causing this? The MD5 hash of /usr/bin/su and all linked libraries are identical between the two systems, but /usr/sbin/su works just fine on the other host. dmesg reports nothing unusual on system startup. What can I do to fix this? Thanks in advance! -- Brian C. Ledbetter http://www.shadowcom.net/brian/