lkml.org 
[lkml]   [2002]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
Subjectlinux-2.5.6-pre3 calls release_kernel_lock without holding lock
	When I boot an SMP linux-2.5.6-pre3 on a uniprocessor x86, I
consistently get a kernel panic at boot when the release_kernel_lock()
call at line 760 of kernel/sched.c apparently attempts to release
its kernel lock without holding it. I believe that this happens
when the kernel makes the first thread, but I'm not sure.

2.5.6-pre2 did not have this problem.

Just to rule out one thought that some of you may have about this,
I should mention that I am aware that the stock kernel now runs the
child of a fork() first (at least according to the comments in
kernel/fork.c), and I removed my run-child-first code some time ago.
So, that change is not the cause of this problem.

I will post a follow-up if I am able to diagnose this problem,
but I think I'm going to sleep now, so I thought I ought to mention this.

Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.028 / U:1.180 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site