[fm-discuss] fmsim

[Michael Shapiro]

> when I am using fmsim in root account. The fmsim can not be started.
> If I use my nis account, there is no problem.
> 
> bash-3.00# /usr/lib/fm/fmd/fmsim -i
> fmsim: creating simulation world /tmp/fmd.158697 ... done.
> fmsim: populating /var ... done.
> fmsim: populating /usr/lib/fm from / ... 7776 blocks
> fmsim: populating /usr/platform/i86pc/lib/fm from / ... 23904 blocks
> fmsim: populating /usr/lib/locale/ from / ... 61856 blocks
> fmsim: populating /usr/sbin from / ... 208 blocks
> fmsim: adding customizations: done.
> fmsim: generating script ... done.
> fmsim: simulation 158697 running fmd(1M) version 1.2 (DEBUG)
> fmd: [ loading modules ...
> *** _THREAD_ERROR_DETECTION: lock usage error detected ***
> mutex_unlock(0x8110318): calling thread does not own the lock
> calling thread is 0xfe822a00 thread-id 1
> the lock is unowned
> 
> fmsim: fmd terminated from signal IOT (see /tmp/fmd.158697)


This is a locking error being detected by the additional error checking
in libc that fmsim enables.  It could be in a module, a library, etc.
Look at the core file and the stack trace, or append the core file
to a bug report so we can see where the problem is.

-Mike

-- 
Mike Shapiro, Solaris Kernel Development. blogs.sun.com/mws/