Re: Panic _at_r207433: "System call fork returning with the following locks held"

From: David Wolfskill <david_at_catwhisker.org>
Date: Fri, 30 Apr 2010 10:05:51 -0700
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_at_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_at_g1-190.catwhisker.org:/usr/obj/usr/src/sys/CANARY  i386

Thanks again for the timely fix!

Peace,
david
-- 
David H. Wolfskill				david_at_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.

Received on Fri Apr 30 2010 - 15:06:06 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:03 UTC