From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 20 16:59:36 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 7A63016A4CE for ; Tue, 20 Jan 2004 16:59:36 -0800 (PST) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0482243D6D for ; Tue, 20 Jan 2004 16:59:20 -0800 (PST) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with asmtp (Exim 4.30; FreeBSD) id 1Aj6em-0008gC-3E; Wed, 21 Jan 2004 08:55:44 +0800 Message-Id: <6.0.1.1.2.20040121090157.02977fd0@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Wed, 21 Jan 2004 09:03:16 +0800 To: Brian Ledbetter From: Ganbold In-Reply-To: <20040120161913.GB1289@shadowcom.net> References: <20040120160843.GA1289@shadowcom.net> <20040120161913.GB1289@shadowcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: 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: Wed, 21 Jan 2004 00:59:36 -0000 Did you run mergemaster? I had this problem recently and when I run mergemaster everything worked fine. hth, Ganbold At 12:19 AM 21.01.2004, you wrote: >Additionally, I am seeing this message in syslog: > >Jan 20 10:48:26 tokyo su: in openpam_load_module(): no pam_wheel.so found > >though /usr/lib/pam_wheel.so -> /usr/lib/pam_wheel.so.2 exists, and has >the same md5 hash as on the working host. What am I missing here? > > > > > >On Tue, Jan 20, 2004 at 11:08:43AM -0500, Brian Ledbetter wrote: > > 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/ > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >-- >Brian C. Ledbetter >http://www.shadowcom.net/brian/ >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"