Re: ktr/alq/witness failure.

From: Julian Elischer <julian_at_elischer.org>
Date: Mon, 27 Sep 2004 12:27:41 -0700
John Baldwin wrote:

>On Monday 27 September 2004 02:15 am, Julian Elischer wrote:
>  
>
>>I'm not going to stop and debug this now because I'm chasing another
>>problem but I can probably stash a corefile somewhere if people want it..
>>    
>>
>
>Looks like the process mutex is busted or some such.
>
>  
>
>>ref4# sysctl debug.ktr.mask=0x2fffffff
>>debug.ktr.mask: 262144
>>  ->
>>805306367
>>ref4#
>>ref4#
>>ref4# sysctl debug.ktr.mask=0x0
>>kernel trap 12 with interrupts disabled
>>
>>Fatal double fault:
>>eip = 0xc053336e
>>esp = 0xcbaa3ff4
>>ebp = 0xcbaa401c
>>cpuid = 0; apic id = 00
>>panic: double fault
>>cpuid = 0
>>KDB: enter: panic
>>[thread 100027]
>>Stopped at      kdb_enter+0x2b: nop
>>db> tr
>>kdb_enter(c069adef) at kdb_enter+0x2b
>>panic(c06b581a,c06b59c4,0,0,0) at panic+0x127
>>dblfault_handler() at dblfault_handler+0x7a
>>--- trap 0x17, eip = 0xc053336e, esp = 0xcbaa3ff4, ebp = 0xcbaa401c ---
>>witness_checkorder(c111776c,9,c06b5972,2bb) at witness_checkorder+0x6a
>>    
>>
>
>Can you pull up 'gdb kernel.debug' and do 'l *0xcbaa401c' and 'l 
>

unfortunatly  when I tryied to save a coredump it failed.. dumpdev was 
not set.. .. DUH!

>*witness_checkorder+0x6a'?
>
>  
>
Received on Mon Sep 27 2004 - 17:27:44 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:14 UTC