Date: Fri, 30 Apr 2010 10:05:51 -0700 From: David Wolfskill <david@catwhisker.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: current@freebsd.org Subject: Re: Panic @r207433: "System call fork returning with the following locks held" Message-ID: <20100430170551.GA96847@bunrab.catwhisker.org> In-Reply-To: <20100430162732.GP2391@deviant.kiev.zoral.com.ua> References: <20100430161953.GW96847@bunrab.catwhisker.org> <20100430162732.GP2391@deviant.kiev.zoral.com.ua>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Apr 30, 2010 at 07:27:32PM +0300, Kostik Belousov wrote: > ... > Please try r207438. OK; that worked -- thanks! I actually merely hand-edited the one file & rebuilt the kernel; boot to multi-user mode was uneventful, and: FreeBSD freebeast.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #145 r207433M: Fri Apr 30 09:54:26 PDT 2010 root@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 I also completed the CURRENT build on my laptop, and despite what happened with the build machine, I tried booting r207433 ... and it came up just fine. Biggest salient difference that occurs to me is that the laptop is a single core, while the build machine is a pair of CPUs (with a single core each): FreeBSD d254.dwolf.juniper.net. 9.0-CURRENT FreeBSD 9.0-CURRENT #144 r207433: Fri Apr 30 09:06:04 PDT 2010 root@g1-190.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 Thanks again for the timely fix! Peace, david -- David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkvbDe4ACgkQmprOCmdXAD27iACeMEnbJSzx7V3Lma9yoSHmIkQl FmYAn29qsXFyrT54XP6zwY2UOKTamSzU =zCPV -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100430170551.GA96847>