Skip to main content

Fix Your Stuff

Right to Repair


Released June 2012, Model A1278. Intel processor with Turbo Boost, Up to 512 MB DDR5 Video RAM

1621 Questions View all

Console message en3 promiscuous mode enable succeeded

I do not have wireshark that i know of. Have search spotlight, no luck. Have been hacked in the past, so concerned. Any one know what this promiscuous mode kernel task is?

Answered! View the answer I have this problem too

Is this a good question?

Score 0
Add a comment

2 Answers

Chosen Solution

That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:

A stale or corrupt kernel cache

A damaged OS X installation

A fault in a peripheral device, if any

Corrupt non-volatile memory (NVRAM)

An internal hardware fault (including incompatible memory)

An obscure bug in OS X

You may already have ruled out some of these.

Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.

You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation may solve a problem that isn't solved by reinstalling in place.

Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.

If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications of the machine.

Apple Diagnostics or the Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test, if applicable.

In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.

Connecting more than one display is another reported trigger for OS X bugs.

If your system is not fully up to date, running Software Update might get you a bug fix.

Credit to Linc Davis for this response

Was this answer helpful?

Score 2


Thank You so much, A lot of this explanation is a bit confusing. However I will research every point and problem solve, then get back. Also, I do have a firmware password set.


I have fire vault and a firmware password, but should that make me operate in promiscuous mode? I am extremely concerned that I am being sniffed.


Add a comment

This likely indicates a graphics chip failure and need for a new motherboard.

Very common in the 2011 Macbook Pro series, but apparently also affects some retina display models too.

Repair extension from Apple

Sadly they no longer repair the 2011’s.

Was this answer helpful?

Score 0
Add a comment

Add your answer

Jana will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 3

Past 30 Days: 13

All Time: 5,271