On Thursday, January 13, 2011 11:26:46 am Michael Jung wrote: > Links to crash info below. > http://216.26.153.6/msgbuf.txt This might be a hardware problem. The panic you got is a "should never happen" panic. Note that in the code line sourced, the second argument to mtx_assert() is MA_OWNED. The panic is saying that it is some invalid value (i.e. something other than MA_OWNED). Given that is a constant, that's not very likely at all barring some hardware glitch. You do have a somewhat scary looking machine check logged before your panic: MCA: Bank 1, Status 0xd000000000000171 MCA: Global Cap 0x0000000000000105, Status 0x0000000000000000 MCA: Vendor "AuthenticAMD", ID 0x20fc2, APIC ID 0 MCA: CPU 0 COR OVER ICACHE L1 EVICT error It is a correctable error, but given the nature of the panic I'd suspect a hardware problem. mcelog doesn't provide many more details: HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 0 1 instruction cache bit62 = error overflow (multiple errors) memory/cache error 'evict mem transaction, instruction transaction, level 1' STATUS d000000000000171 MCGSTATUS 0 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 44 -- John BaldwinReceived on Fri Jan 14 2011 - 20:14:09 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:10 UTC