Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

IMac shuts down and I cannot wake up with mouse or keyboard

Over the past couple days, the computer will shut down during the night (or day) after it hasn't been used for a while. I try and use the mouse or keyboard to wake the machine but it does not work, I end up using the power button in the back. Once the machine restarts I receive a notification that there was a problem. Please see below. I'm new to using a Mac and would appreciate any help. Thanks.




Interval Since Last Panic Report: 36504 sec

Panics Since Last Report: 1

Anonymous UUID: C97EF418-AB0A-490A-94D4-77312E1EBF5B



Thu Aug 29 15:39:45 2013

panic(cpu 3 caller 0xffffff80003484f1): "Failed mbuf validity check: mbuf 0xffffff807b0f0b00 len -9 " "type 1 flags 0x2 data 0xffffff807b0f0b86 rcvif en2 ifflags 0x8863"@/SourceCache/xnu/xnu-1699.32.7/bsd/net/dlil.c:1484

Backtrace (CPU 3), Frame : Return Address

0xffffff807f643e40 : 0xffffff8000220792

0xffffff807f643ec0 : 0xffffff80003484f1

0xffffff807f643f60 : 0xffffff8000343c79

0xffffff807f643fb0 : 0xffffff8000820057



BSD process name corresponding to current thread: kernel_task



Mac OS version:

11G63



Kernel version:

Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64

Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5

System model name: iMac12,1 (Mac-942B5BF58194151B)



System uptime in nanoseconds: 47314626953306

last loaded kext at 47310192200727: com.apple.driver.AppleUSBCDCACMData 4.1.22 (addr 0xffffff7f807b5000, size 36864)

last unloaded kext at 47150396886060: com.apple.driver.AppleUSBCDCACMData 4.1.22 (addr 0xffffff7f807b5000, size 28672)

loaded kexts:

com.apple.driver.AppleUSBCDCACMData 4.1.22

com.apple.driver.AppleBluetoothMultitouch 70.12

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.filesystems.autofs 3.0

com.apple.iokit.IOBluetoothSerialManager 4.0.8f17

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.driver.AppleUSBCDCECMData 4.1.22

com.apple.driver.AudioAUUC 1.59

com.apple.driver.AppleUpstreamUserClient 3.5.9

com.apple.driver.AppleMikeyDriver 2.2.5a5

com.apple.driver.AppleHDA 2.2.5a5

com.apple.kext.ATIFramebuffer 7.3.2

com.apple.driver.AGPM 100.12.75

com.apple.driver.AppleSMCPDRC 5.0.0d8

com.apple.driver.AppleSMCLMU 2.0.1d2

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AudioIPCDriver 1.2.3

com.apple.driver.ApplePolicyControl 3.1.33

com.apple.driver.ACPI_SMC_PlatformPlugin 5.0.0d8

com.apple.driver.AppleLPC 1.6.0

com.apple.driver.AppleBacklight 170.2.2

com.apple.driver.AppleMCCSControl 1.0.33

com.apple.driver.AppleUSBCDC 4.1.22

com.apple.ATIRadeonX3000 7.3.2

com.apple.driver.AppleIntelHD3000Graphics 7.3.2

com.apple.driver.BroadcomUSBBluetoothHCIController 4.0.8f17

com.apple.driver.AppleIRController 312

com.apple.iokit.IOAHCISerialATAPI 2.0.3

com.apple.iokit.SCSITaskUserClient 3.2.1

com.apple.driver.AppleUSBCardReader 3.0.6

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.1.0

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 33

com.apple.driver.AppleUSBHub 5.1.0

com.apple.driver.AppleFWOHCI 4.9.0

com.apple.iokit.AppleBCM5701Ethernet 3.2.4b8

com.apple.driver.AppleEFINVRAM 1.6.1

com.apple.driver.AppleAHCIPort 2.3.1

com.apple.driver.AirPort.Atheros40 505.67.1

com.apple.driver.AppleUSBEHCI 5.1.0

com.apple.driver.AppleACPIButtons 1.5

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.7

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.5

com.apple.driver.AppleAPIC 1.6

com.apple.driver.AppleIntelCPUPowerManagementClient 195.0.0

com.apple.nke.applicationfirewall 3.2.30

com.apple.security.quarantine 1.4

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleIntelCPUPowerManagement 195.0.0

com.apple.driver.AppleMultitouchDriver 231.4

com.apple.driver.AppleBluetoothHIDKeyboard 160.7

com.apple.driver.AppleHIDKeyboard 160.7

com.apple.driver.IOBluetoothHIDDriver 4.0.8f17

com.apple.kext.triggers 1.0

com.apple.iokit.IOSerialFamily 10.0.5

com.apple.driver.AppleUSBCDCECMControl 4.1.22

com.apple.driver.DspFuncLib 2.2.5a5

com.apple.iokit.IOFireWireIP 2.2.5

com.apple.iokit.IOSurface 80.0.2

com.apple.driver.AppleHDAController 2.2.5a5

com.apple.iokit.IOHDAFamily 2.2.5a5

com.apple.iokit.IOAudioFamily 1.8.6fc18

com.apple.kext.OSvKernDSPLib 1.3

com.apple.driver.AppleSMC 3.1.3d10

com.apple.driver.IOPlatformPluginLegacy 5.0.0d8

com.apple.driver.AppleSMBusPCI 1.0.10d0

com.apple.driver.IOPlatformPluginFamily 5.1.1d6

com.apple.driver.AppleGraphicsControl 3.1.33

com.apple.driver.AppleThunderboltEDMSink 1.1.8

com.apple.driver.AppleThunderboltEDMSource 1.1.8

com.apple.driver.AppleBacklightExpert 1.0.4

com.apple.driver.AppleSMBusController 1.0.10d0

com.apple.kext.ATI6000Controller 7.3.2

com.apple.kext.ATISupport 7.3.2

com.apple.iokit.IONDRVSupport 2.3.4

com.apple.driver.AppleIntelSNBGraphicsFB 7.3.2

com.apple.iokit.IOGraphicsFamily 2.3.4

com.apple.driver.AppleUSBBluetoothHCIController 4.0.8f17

com.apple.iokit.IOBluetoothFamily 4.0.8f17

com.apple.driver.AppleThunderboltDPOutAdapter 1.8.5

com.apple.driver.AppleThunderboltDPInAdapter 1.8.5

com.apple.driver.AppleThunderboltDPAdapterFamily 1.8.5

com.apple.driver.AppleThunderboltPCIDownAdapter 1.2.5

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.2.1

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOUSBHIDDriver 5.0.0

com.apple.iokit.IOSCSIBlockCommandsDevice 3.2.1

com.apple.iokit.IOUSBMassStorageClass 3.0.3

com.apple.iokit.IOSCSIArchitectureModelFamily 3.2.1

com.apple.driver.AppleUSBMergeNub 5.1.0

com.apple.driver.AppleUSBComposite 5.0.0

com.apple.driver.AppleThunderboltNHI 1.6.0

com.apple.iokit.IOThunderboltFamily 2.0.3

com.apple.iokit.IOUSBUserClient 5.0.0

com.apple.iokit.IOFireWireFamily 4.4.8

com.apple.iokit.IOEthernetAVBController 1.0.1b1

com.apple.iokit.IOAHCIFamily 2.0.8

com.apple.iokit.IO80211Family 420.3

com.apple.iokit.IONetworkingFamily 2.1

com.apple.iokit.IOUSBFamily 5.1.0

com.apple.driver.AppleEFIRuntime 1.6.1

com.apple.iokit.IOHIDFamily 1.7.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 177.11

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.DiskImages 331.7

com.apple.iokit.IOStorageFamily 1.7.2

com.apple.driver.AppleKeyStore 28.18

com.apple.driver.AppleACPIPlatform 1.5

com.apple.iokit.IOPCIFamily 2.7

com.apple.iokit.IOACPIFamily 1.4

Model: iMac12,1, BootROM IM121.0047.B1F, 4 processors, Intel Core i5, 2.5 GHz, 4 GB, SMC 1.71f22

Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 512 MB

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3230554638424353302D444A2D4620

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3230554638424353302D444A2D4620

AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.67.5-P2P

Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

Network Service: Thomson USB CDC Device, Ethernet, en2

Serial ATA Device: ST3500418AS, 500.11 GB

Serial ATA Device: HL-DT-STDVDRW GA32N

USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 3

USB Device: Thomson USB CDC Device, 0x069b (Thomson Consumer Electronics), 0x0705, 0xfa130000 / 5

USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 6

USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x850b, 0xfa200000 / 2

USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfd110000 / 4

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3

iMac

Posted on Aug 29, 2013 8:22 PM

Reply
Question marked as Best reply

Posted on Aug 30, 2013 8:46 AM

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


  1. A stale or corrupt kernel cache
  2. A damaged OS X installation
  3. A fault in a peripheral device, if any
  4. Corrupt non-volatile memory (NVRAM)
  5. An internal hardware fault (including incompatible memory)
  6. 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 on some models, or if a firmware password is set, or if the boot volume is 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 (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.


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 for your model. Memory that is either slower or faster than specified may be incompatible.


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


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.


In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.


If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


Print the first page of the panic report and bring it with you.


Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least two independent backups.) Don’t erase the recovery partition, if present.


Keeping your confidential data secure during hardware repair


*An SSD doesn't need to be zeroed.

2 replies
Question marked as Best reply

Aug 30, 2013 8:46 AM in response to rpa022166

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


  1. A stale or corrupt kernel cache
  2. A damaged OS X installation
  3. A fault in a peripheral device, if any
  4. Corrupt non-volatile memory (NVRAM)
  5. An internal hardware fault (including incompatible memory)
  6. 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 on some models, or if a firmware password is set, or if the boot volume is 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 (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.


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 for your model. Memory that is either slower or faster than specified may be incompatible.


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


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.


In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.


If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


Print the first page of the panic report and bring it with you.


Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least two independent backups.) Don’t erase the recovery partition, if present.


Keeping your confidential data secure during hardware repair


*An SSD doesn't need to be zeroed.

IMac shuts down and I cannot wake up with mouse or keyboard

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.