Hi I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the Tomahawk Desktop, a FreeBSD based desktop operating system (http://www.tomahawkcomputers.com/) which is free for personal use. Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we experienced a strange issue as follows: 1. The root cannot login from the console, child process forked die with ?uid 0: exited on signal 11?. 2. Normal users can log in, no issue. 3. Normal users can type ?su? and become root, but ?su -l? results child process forked die with ?uid 0: exited on signal 11?. 4. The /var/log/messages shows ?(cron), uid 0: exited on signal 11 (core dumped)? We use a different build method to create Tomahawk Core OS, therefore, we earlier decided not to complain about this issue till we release the beta version as we were thinking without having access to our OS it may be difficult to diagnose this issue. Then we saw ?Deadlock in a multi-threaded program during fork(2)? on FreeBSD website and upgraded our sources to the latest and rebuilt the Tomahawk Core OS but the problem we face did not go away. Appreciate if the FreeBSD community could give us a helping hand to identify the cause of the issue we are facing. Kind regards Sagara Wijetunga
On Wed, Jul 01, 2009 at 02:04:09AM -0500, Sagara Wijetunga wrote:> Hi > > I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the > Tomahawk Desktop, a FreeBSD based desktop operating system > (http://www.tomahawkcomputers.com/) which is free for personal use. > > Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we > experienced a strange issue as follows: > > 1. The root cannot login from the console, child process forked die with > ?uid 0: exited on signal 11?. > 2. Normal users can log in, no issue. > 3. Normal users can type ?su? and become root, but ?su -l? > results child process forked die with ?uid 0: exited on signal 11?. > 4. The /var/log/messages shows ?(cron), uid 0: exited on signal 11 > (core dumped)?Based on your symptoms, it looks like something in the restart commands file for root causes the shell to crash... What shell are you using for root? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090701/f5165597/attachment.pgp
Carlos A. M. dos Santos writes:> Try to debug the "login" program: > > (become root) > # cd /usr/src/usr.bin/login > # make clean > # make CFLAGS=-g > # gdb /usr/obj/usr/src/usr.bin/login/login > (supposing that "sagara" is your user name) > #run sagara > (fill-in the password name, if requested) > > If the signal 11 is caught, issue "bt" command in gcc. It will show > you where the break happened. >I tried to debug the login program, here are the results: 1. For normal users, gdb exists "Program exited normally." 2. For root, gdb says "Login incorrect". On /var/log/messages: login: pam_acct_mgmt(): authentication error login: 1 LOGIN FAILURE ON ttyp0 Btw, I have mentioned in my first post that I do not have an issue with normal user logins. Its only root has a problem. When try to "su -l" from a normal user, there is no "pam_acct_mgmt(): authentication error" on logs. Its only a "(su), uid 0: exited on signal 11". Regards Sagara
Dear all The issue was solved. It was a our side mistake. On a modification we made to libutils, we execute following line without checking whether the group is empty or not. In our case, it was empty, therefore, crashes: running = strdup(*(grp->gr_mem)); So that now login, su and cron work well. Thank you for all those who helped us. Best regards Sagara