Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

bad_mutex error

Status
Not open for further replies.

ConnieK

MIS
Jan 7, 2002
1
US
I am not too familiar with SUN/Solaris stuff, so please bear with me...
I have a production Sparc Ultra V (256 MB Mem), running Sun 5.7. When I attempt a boot, the system hangs and gives me the following error:
panic [cpu0] /thread=300001e7420: mutex_enter: bad_mutex, lp=300151f28, owner=deadbeefdeadbee8, and repeats the error.

I have searched the Sun docs site and found something about having to apply patches, but only for Solaris 2.5.1 and 2.6 - not 2.7. And it says this happens while trying to install the OS. It also states that for a more in-depth look at this issue, ref SRDB 20149.

I have NO idea how to access the reference SRBD 20149.

I have had the disk and the mother board replaced by a Sun technician. Is it possible the there is not enough memory? Could the application that is running be poorly written (meaning that there is a mutex contention)? Any thoughts? Has anyone else run into this problem?

CK
 
I can tell you that mutex is Mutual Exclusion and is used to protect againist multiprocessing causing errors in a routine which NEED to have only one program in them at a time.

I may have many Processes all sharing memory, yet need one subroutine to have no more than one calling routine at once. mutex is a way of controlling that. all the rest of the code is multiprocessing, but that one subroutine. I tried to remain child-like, all I acheived was childish.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top