Is this one a known issue on alpha or is it something new? While someone was using gdb on beast (alpha cluster ref machine) to trace a program beast crashes with this: panic: mutex process lock not owned at ../../../kern/kern_mutex.c:277 at line 719 in file ../../../kern/kern_mutex.c cpuid = 1; Stack backtrace: db_print_backtrace() at db_print_backtrace+0x18 backtrace() at backtrace+0x2c __panic() at __panic+0x210 _mtx_assert() at _mtx_assert+0xec _mtx_unlock_flags() at _mtx_unlock_flags+0xa4 ptrace_single_step() at ptrace_single_step+0x6c kern_ptrace() at kern_ptrace+0x3c4 ptrace() at ptrace+0xe8 syscall() at syscall+0x37c XentSys() at XentSys+0x64 --- syscall (26) --- --- user mode --- boot() called on cpu#1 It seems to be reproducible... -- Ken Smith - From there to here, from here to | kensmith_at_cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |Received on Mon Mar 29 2004 - 11:21:52 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:49 UTC