My Oracle Support Banner

Reboot After Panic: mutex_destroy: Not Owner from kom_capture_fini() (Doc ID 2180517.1)

Last updated on JUNE 25, 2018

Applies to:

Solaris Operating System - Version 11.2 and later
Information in this document applies to any platform.
Reboot After Panic: mutex_destroy: Not Owner from kom_capture_fini()

Symptoms

 System will panic with: mutex_destroy: Not Owner in kom_capture_fini()

Changes

The panic stack will look similar to:

The rm is transition, and capturing is set. This indicates that someone already called kom_backend_free_physmem() before us!
Given that the DRAINED bit is set, it has to have been postprocess that did the free.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.