Re: 5.2 install hangs
Hi, I have the same problem on my Fujitsu Siemens LifeBook E2010. I tried to boot FreeBSD from CDROM with ACPI disabled and no luck. I upgraded my kernel to 5.2 and the boot still hangs. 5.1 boots fine though I have the same problem on a Toshiba Tecra M1. I can try to send a dmesg (boot -v) from 5.0-R, if that would help... (It's good to know that I'm not the only person with this problem :) ) -- Brian C. Ledbetter brian at shadowcom.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Curious problem w/ 5.2-RELEASE su
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 [EMAIL PROTECTED] http://www.shadowcom.net/brian/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Curious problem w/ 5.2-RELEASE su
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 [EMAIL PROTECTED] http://www.shadowcom.net/brian/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] -- Brian C. Ledbetter [EMAIL PROTECTED] http://www.shadowcom.net/brian/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Curious problem w/ 5.2-RELEASE su
Thank you very much for the advice - it works perfectly after running mergemaster! I will slink away now, and remember to RTFM first next time. Sorry for the noise, all! :) On Wed, Jan 21, 2004 at 09:03:16AM +0800, Ganbold wrote: 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 [EMAIL PROTECTED] http://www.shadowcom.net/brian/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] -- Brian C. Ledbetter [EMAIL PROTECTED] http://www.shadowcom.net/brian/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] -- Brian C. Ledbetter [EMAIL PROTECTED] http://www.shadowcom.net/brian/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
