mutex_enter: bad mutex

From: DAUBIGNE Sebastien - BOR (SDaubigne@bordeaux-bersol.sema.slb.com)
Date: Thu Jan 15 2004 - 05:31:45 EST


Hi,

Last night our E6500 (Solaris 8) paniced with a "mutex_enter: bad mutex"
message. We never caught such an error in the last 3 years.
As we caught many hardware errors during the last months, especially
non-fatal (ECC corrected) memory errors, I wonder if this kind of mutex
error could be produced by a bad memory chip producing a non-detected memory
error, or a CPU error ?

In other words : is it a pure software error, or could it be a side effect
of any undetected hardware error ?

Here is the complete error messages written to the console :

panic[cpu5]/thread=3007c423140: mutex_enter: bad mutex, lp=3008573d750
owner=30020e35200 thread=3007c423140
000002a101837350 unix:mutex_panic+5c (10415eb0, 3008573d750, 0, 30082406278,
0,30082406278)
  %l0-3: 0000030020e35204 000003008573d750 0000030011fb2050 000002a10013df50
  %l4-7: 0000030020e35200 000003004d0ac040 0000000000000000 000002a101837350
000002a101837400 hsfs:hsfs_inactive+28 (3008573d750, 30082406278,
3008573d648, 30082406120, 3008573d648, 3008573d630)
  %l0-3: 00000000783f98ec 0000000000001840 0000000000000005 000000001000a408
  %l4-7: 000000000000ff00 0000000001000100 0000000000000000 000002a101837410
000002a1018374b0 bunyipmod:bunyip_mem_kstat_update+350 (780c67e8, 782934e8,
78293880, 1000, 12a524, 3100b800000)
  %l0-3: 0000000000000000 000000001041b128 0000000000000000 000003008573d648
  %l4-7: 00000310127ded20 0000000000000000 0000000000000000 0000000000000000
000002a101837570 kstat:read_kstat_data+1c4 (3005e39ed08, 1041c4e8, 100000,
2a101837aec, 7aae0, 6)
  %l0-3: 0000000078140ae0 0000000000000000 0000000000000040 0000000000000000
  %l4-7: 000000000015e000 0000000000160000 0000030025e98ba8 000002a101837af0
000002a101837780 kstat:kstat_ioctl+68 (5a00000000, 4b02, 7aae0, 100001,
300059c09c8, 2a101837aec)
  %l0-3: 0000000000000040 0000000000ff0000 000000000000ff00 00000000e2ff7273
  %l4-7: 0000000073740000 0000000000000000 000000007efefeff 0000000081010100
000002a101837830 genunix:cdev_ioctl+40 (5a00000000, 4b02, 7aae0, 100001,
300059c09c8, 2a101837aec)
  %l0-3: 00000000782a757c 0000000000000000 00000300493c5568 0000000000000000
  %l4-7: 0000000000010031 0000030083479900 0000000000000000 0000000000000002
000002a1018378e0 specfs:spec_ioctl+b0 (300190b6d78, 4b02, 7aae0, 100001,
300059c09c8, 2a101837aec)
  %l0-3: 0000000082001a04 0000000000000016 0000000000000000 0000000000000003
  %l4-7: 0000000000000000 00000000ff370124 000003007c423140 000002a101837ba0
000002a1018379a0 genunix:ioctl+1e4 (3004ac17e30, 3, 7aae0, 0, 4b02,
6d656d00)
  %l0-3: 00000000101524f8 0000000000010466 00000000ff3e91f8 0000000000000000
  %l4-7: 00000000ff380a04 00000000ff370124 00000000000106a4 0000000000000000

cheers,

---
Sebastien DAUBIGNE 
sdaubigne@bordeaux-bersol.sema.slb.com
<mailto:sdaubigne@bordeaux-bersol.sema.slb.com>  - (+33)5.57.26.56.36
SchlumbergerSema - SGS/DWH/Pessac
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers


This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:50 EDT