My screen darkened, I got a message to restart my computer, and after I did, the problem details report came up. It begins with "panic trying to interlock destroyed mutex" 1. What does this mean? and 2. How can I copy and paste the report?

Question

Level 1

5 points

My screen darkened, I got a message to restart my computer, and after I did, the problem details report came up. It begins with "panic trying to interlock destroyed mutex" 1. What does this mean? and 2. How can I copy and paste the report?

My screen darkened, I got a message to restart my computer, and after I did, the problem details report came up.

It begins with "panic (cpu 2 caller, etc.): ... trying to interlock destroyed mutex"

1. What does this mean? and

2. How can I copy and paste the report? The editing functions do not work, nor can I print out this report of the details which is on my desktop. The only function available is to send the report to Apple, anonymously, for their info.

Further down in the report, there are references to Darwin Kernel version.

????

iMac, Mac OS X (10.7.5), Problem details report

Posted on Mar 28, 2013 4:34 PM

Reply

Answer 1

Mar 28, 2013 5:12 PM in response to Archlea

That is called a Kernal Panic - http://support.apple.com/kb/ts3742.

Kernel Panics can be caused by both Software issues, and Hardware issues. Also, they can be intermittent and only occur when they feel like it. This can make is difficult to diagnose.

Also, devices that we have connected to our computer, can also cause Kernel Panics. When troubleshooting, it is a good idea to disconnect all devices, so you can rule them out.

Running the Apple Hardware Test can help rule out Hardware issues. If they are intermittent, running the Hardware test in "Loop mode" overnight, can be very helpful.

10.5 or 10.6 - HT1509 - Intel-based Macs: Using Apple Hardware Test

10.7 - Apple Hardware Test - http://support.apple.com/kb/PH4510.

10.8 - Apple Hardware Test - http://support.apple.com/kb/PH11342.

Restart your computer, holding down the D key while the computer restarts.

After your computer restarts, you should see the Apple Hardware Test chooser screen. If you don’t, Apple Hardware Test may not be available on your computer. You may be able to start Apple Hardware Test from the Internet. Reconnect your computer to the network, and then restart your computer while holding down both the Option and D keys.

Many times, running the "quick" test, or the "extended" test, may not give you any error results. Many intermittent issues, may need to have the hardware test to run in loop mode, before it detects any error, and therefore running the Apple Hardware Test in Loop Mode overnight is an excellent troubleshooting step for finding intermittent hardware problems.

In continuous Loop Mode, the test will run continuously until a problem is found or is stopped by you, by clicking “Stop Test” or by using the Command-period keyboard shortcut. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure. Looping mode could be helpful in diagnosing a fault that may be heat related or when the fault occurs randomly.-------

-- Insert your install disk 1 into the optical drive

-- shut down computer

-- restart computer holding down the D key until you see a screen with an icon of a computer appear ***NOTE if this does not boot you to the apple hardware test, try restarting computer holding down the "option" key instead, then click the right arrow to get the hardware test

-- select English as your language and press enter

-- The Apple Hardware Test console appears. You can choose what sort of test or tests to perform: basic or select the "Perform extended testing"

-- press and hold down the option key and the "L" key...then select the extended test. This will make the test go into Loop mode

-- look over the test results and make notes of any errors that may be logged

-- to exit out of the test, press the escape key

Reply

Answer 2

Archlea Author

Level 1

5 points

Mar 28, 2013 5:34 PM in response to KarenSelena

Karen,

Thank you SO much for your advice and links. It put my mind at ease.

Thinking back, I had my camera connected to iphoto to download, and the import wasn't working. I turned the camera off, left it connected to the Mac, though, and perhaps that external action contributed to the problem. Who knows?

I wonder if you have any suggestions as to how I can preserve that problem details report for myself. Other people on this website seem to reproduce their reports but my edit functions and print functions become disabled when I try to apply them to the report, which now sits on my desktop.

You've been a great help.

Reply

Answer 3

babowa

Level 9

78,568 points

Mar 28, 2013 5:51 PM in response to Archlea

I turned the camera off, left it connected to the Mac,

You should always properly eject any external device before unplugging/turning it off - that is done by dragging the device icon to the trash. That saves whatever needs to be saved and you can then safely turn it off.

Reply

Answer 4

Linc Davis

Level 10

209,739 points

Mar 28, 2013 6:06 PM in response to Archlea

If you have more than one user account, you must be logged in as an administrator to carry out these instructions.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

Select the most recent panic log under the heading System Diagnostic Reports on the left. If you don't see that heading, select

View ▹ Show Log List

from the menu bar. Post the entire contents of the panic report — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

Reply

Answer 5

Archlea Author

Level 1

5 points

Mar 28, 2013 6:27 PM in response to Linc Davis

Many thanks, Linc.

Reply

Answer 6

Archlea Author

Level 1

5 points

Mar 28, 2013 7:19 PM in response to Linc Davis

Got to Console through Launchpad; in System Diagnostic reports, no panic report was listed in the log. (Reason may be that before I read your directions, I had followed directions on http://support.apple.com/kb/ts3742 to update software to prevent kernel panic . This necessitated "restart" and once updates were installed, and computer restarted, report was gone from my desktop.)

BUT, selecting kernel reports, I retrieved the info from tonight's event. Appears not to be the same kind of report as the one I lost, but has info that must mean something to the knowing eye, and I copied that material. I'll write more tomorrow.

Reply

Answer 7

Archlea Author

Level 1

5 points

Mar 28, 2013 7:31 PM in response to Linc Davis

ps How can I change 'this helped me' to 'this solved my problem' re your reply?

Reply

Answer 8

Linc Davis

Level 10

209,739 points

Mar 28, 2013 7:34 PM in response to Archlea

You can't change it, but since the problem doesn't seem to be solved, there's no reason to.

Reply

Answer 9

Archlea Author

Level 1

5 points

Mar 28, 2013 7:49 PM in response to Linc Davis

Oh, OK.

Here's what I salvaged from the kernel report. This excerpt consists of 2 portions that I think are relevant to the event. (Kernel reports are lengthy and take in several dates before today).

Mar 28 15:32:26 Janes-iMac kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)

Mar 28 15:32:26 Janes-iMac kernel[0]: 6650.024304: ar9300WowWakeUp: Skip PCIE WA programming

Mar 28 15:32:26 Janes-iMac kernel[0]: 6650.024324: setDISASSOC from ATH_INTERFACE_CLASS disconnectVap

Mar 28 15:32:26 Janes-iMac kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

Mar 28 15:32:26 Janes-iMac kernel[0]: 6650.038022: setDISASSOCIATE ****STA SYNC DISASSOC SUCCESS

Mar 28 15:32:26 Janes-iMac kernel[0]: The USB device BRCM2046 Hub (Port 1 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)

Mar 28 15:32:26 Janes-iMac kernel[0]: TBT W (1): 0 [x]

Mar 28 15:32:26 Janes-iMac kernel[0]: The USB device Bluetooth USB Host Controller (Port 1 of Hub at 0xfa110000) may have caused a wake by issuing a remote wakeup (3)

Mar 28 15:32:26 Janes-iMac kernel[0]: 6650.212216: performCountryCodeOperation: Not connected, scan in progress[0]

Mar 28 15:32:26 Janes-iMac kernel[0]: HID tickle 212 ms

Mar 28 15:32:32 Janes-iMac kernel[0]: en1: BSSID changed to e0:91:f5:b7:03:bb

Mar 28 15:32:32 Janes-iMac kernel[0]: AirPort: Link Up on en1

Mar 28 15:32:32 Janes-iMac kernel[0]: en1: BSSID changed to e0:91:f5:b7:03:bb

Mar 28 15:32:32 Janes-iMac kernel[0]: en1: 802.11d country code set to 'US '.

Mar 28 15:32:32 Janes-iMac kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165

Mar 28 15:32:33 Janes-iMac kernel[0]: en1: BSSID changed to e0:91:f5:b7:03:bb

Mar 28 16:33:59 Janes-iMac kernel[0]: IOSurface: buffer allocation size is zero

Mar 28 16:35:04: --- last message repeated 1 time ---

Mar 28 16:35:04 Janes-iMac kernel[0]: IOSurface: buffer allocation size is zero

Mar 28 16:35:34: --- last message repeated 5 times ---

Mar 28 16:35:49 Janes-iMac kernel[0]: IOSurface: buffer allocation size is zero

Mar 28 16:37:26: --- last message repeated 1 time ---

Mar 28 16:37:42 Janes-iMac kernel[0]: IOSurface: buffer allocation size is zero

Mar 28 16:38:12: --- last message repeated 3 times ---

Mar 28 16:38:15 Janes-iMac kernel[0]: IOSurface: buffer allocation size is zero

Mar 28 17:38:24: --- last message repeated 1 time ---

Mar 28 17:38:24 Janes-iMac kernel[0]: AppleSRP started.

Mar 28 17:44:03 Janes-iMac kernel[0]: (default pager): [KERNEL]: ps_allocate_cluster - send HI_WAT_ALERT

Mar 28 17:44:03 Janes-iMac kernel[0]: macx_swapon SUCCESS

Mar 28 17:44:07 Janes-iMac kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT

Mar 28 17:44:07 Janes-iMac kernel[0]: macx_swapon SUCCESS

and later...

Mar 28 20:41:51 localhost kernel[0]: Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64
Mar 28 20:41:51 localhost kernel[0]: vm_page_bootstrap: 1004875 free pages and 35509 wired pages
Mar 28 20:41:51 localhost kernel[0]: kext submap [0xffffff7f80736000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000736000]
Mar 28 20:41:51 localhost kernel[0]: zone leak detection enabled
Mar 28 20:41:51 localhost kernel[0]: standard timeslicing quantum is 10000 us
Mar 28 20:41:51 localhost kernel[0]: mig_table_max_displ = 73
Mar 28 20:41:51 localhost kernel[0]: TSC Deadline Timer supported and enabled

Reply

Answer 10

Linc Davis

Level 10

209,739 points

Mar 28, 2013 8:01 PM in response to Archlea

You know, an isolated kernel panic that's never repeated is nothing very unusual and not a cause for concern. As far as I can tell, you've had only one. If it's not repeated in a few thousand hours of use, forget it. If it is repeated, post the panic report. If you don't get a response, start a new thread.

Reply

Answer 11

Archlea Author

Level 1

5 points

Mar 28, 2013 8:22 PM in response to Linc Davis

That's good news. Thanks again. Now I know how to post a report, anyway.

There's a lot of repetition of a 'wake' being caused by a remote wakeup from USB port 1 which is where my printer cable is continually plugged in. Maybe not significant, but I took the cable out.

It's not clear to me from this version of events what the cause of the kernel panic was. Do you see it? I assume it's clearer in the details report that I lost.

Reply

Answer 12

Archlea Author

Level 1

5 points

Mar 28, 2013 9:20 PM in response to Linc Davis

p.s. Would you know what "interlocking damaged mutex" means? That was the event, as I understand it.

Reply