At 06:28 PM 12/6/2000 -0800, John Baldwin wrote:

>On 07-Dec-00 John Baldwin wrote:
>> On 07-Dec-00 Manfred Antar wrote:
>>> I've been trying to build a current kernel from current sources for a day
>>> now
>>> and I keep getting this:
>> I'm looking at this.  My initial guess is maybe a gcc bug, as mtx_exit()
>> compiles in dozens of other places just fine (and has for months now).
>Nope, it was a sublte bug in the 486 optimized mutex operations, which had
>invalid register constraints probably dating back to several older revisions in
>BSD/OS before we got the code.  It should be fixed now.

It compiles now fine but panics on booting:
Doing initial network setup: hostname.
panic: mutex sched lock owned at ../../kern/kern_mutex.c:322
cpuid = 0; = 00000000
boot() called on cpu#0

syncing disks... 
Fatal double fault:
eip = 0xc02b0e7d
esp = 0xcafce000
ebp = 0xcafce020
cpuid = 0; = 00000000

I built another one and got a different panic:
Initial rc.i386 panic: spin lock sched lock held by 0x0xc0390a01 for > 5 seconds
cpuid = 1; = 0c000000
boot() called on cpu#1

syncing disks...   Just frozen at this point
||      [EMAIL PROTECTED]           ||
||      Ph. (415) 681-6235      ||

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to