Thanks for your suggestion. Today morning I had another kernel panic and I surely will try to reinstall system next week.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Kernel Panics on MacBook 12" (9,1)
- Thread starter hidea
- Start date
- Sort by reaction score
Thanks for your suggestion. Today morning I had another kernel panic and I surely will try to reinstall system next week.
I'm having this issue too. But I also have another sleep/hibernate issue, and I wonder whether it is related and if others can confirm it happens on their MacBooks too...
I'm finding that the Mac wakes up exactly every 2 hours when on AC or battery, even without powernap or wake for wifi. This only starts happening once you sign into iCloud. From the logs, it looks like an issue with a TCP keepalive that's for the Apple Push Services Daemon. It also looks as though wifi is kept on even when on battery, which seems plain wrong. I've even seen the Mac wake up from standby with a wake reason of "network" (it's usually RTC/Maintenance), which proves wifi is left on all the time. Battery drain during sleep certainly seems worse than other laptops. Can anyone please look at their Console logs when the machine is left, say, overnight on battery power, and see if it regularly wakes up every 2 hours? Have to look at the logs from a user with admin privileges.
Be very interested in comparing notes...
I'm finding that the Mac wakes up exactly every 2 hours when on AC or battery, even without powernap or wake for wifi. This only starts happening once you sign into iCloud. From the logs, it looks like an issue with a TCP keepalive that's for the Apple Push Services Daemon. It also looks as though wifi is kept on even when on battery, which seems plain wrong. I've even seen the Mac wake up from standby with a wake reason of "network" (it's usually RTC/Maintenance), which proves wifi is left on all the time. Battery drain during sleep certainly seems worse than other laptops. Can anyone please look at their Console logs when the machine is left, say, overnight on battery power, and see if it regularly wakes up every 2 hours? Have to look at the logs from a user with admin privileges.
Be very interested in comparing notes...
I haven't experienced any kernel panics on my 2016 m7 MacBook but I did experience on overheating issue where I was literally forced to shut down. It happened after it woke up from when I was watching a video. I noticed it was surprisingly hot even though I closed the lid and was sleeping.
I have read people have had the machine replaced and the issue persisted. I am starting to wonder if this is some sort of design flaw in controlling for a corner case.
The nice man from Germany Dex~ user got a new machine and the issue continues. That is where i get this information from. I google translated his blog to reveal that sad nugget of news.
We are in the same boat. I want one. I also don't want to repeat the mess of dealing with Apple and the denial of
Issue wall they out up. It's the single worst part of Apple that I wished Tim would change
If it's not a kernel panic: almost certainly unrelated. Better to aim for a topic that's focused on the issue.
I'm reading some of you have kernel panics on multiple machines of different years which means one of two things; you are really unlucky and drew bad machines out of millions or there's something you are either doing, environment, software, or something consistent that causes these.
The only kernel panics I've had over several/many machines (5 different MB laptops and three different minis) and almost two decades of Mac OS X have been on hackintosh devices, and that's understandable.
With the exception of truly hardware related issues where could these panics be coming from? I would ask if you are running real time games from online sights? The software drivers, especially video, needed by these games may be at the heart of the panics.
The only Mac I ever had issues with was the early 2010 MB 11" Air and it would occasionally restart on its own when driving it hard MS Word and multiple windows and programs in use. It was a known issue and seemed to have something to do with the nvidia gpu used in that model.
Good luck and keep us informed.
*****
OK I went back and read you kern panic log and the same issue seems to pop up, VMWare.
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8bd0a9fa): "[IGPU] Failed to wake the ME.\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.14.73/Common/GLKernel/Intel/skl/sched3/IGGuC.cpp:1238
...
loaded kexts:
com.vmware.kext.vmioplug.12.2.9 12.2.9
and
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8c77a9d2): "[IGPU] Failed to wake the ME.\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.14.66/Common/GLKernel/Intel/skl/sched3/IGGuC.cpp:1238
...
System uptime in nanoseconds: 28298643087029
last loaded kext at 24105967081593: com.asix.driver.ax88179-178a 1.8.0 (addr 0xffffff7f8ce74000, size 53248)
last unloaded kext at 24210649561320: com.apple.driver.AppleMikeyHIDDriver 124 (addr 0xffffff7f8cdd0000, size 12288)
loaded kexts:
com.asix.driver.ax88179-178a 1.8.0
com.vmware.kext.vmioplug.12.2.9 12.2.9
It also looks like you have an outdated asix driver:
From Asix web site:
AX88179/AX88178A Mac OS X Driver Installation Guide
Revision History Revision
Date
Description
1.00
2012/09/10
Initial release.
2.00
2014/02/25
1. Modified to support Mac OS X 10.9 driver installer.
2. Modified some descriptions in Section 1.
3. Replaced Section 4-1 “Driver Installation Failure on OS X 10.8 Issue” with new Section 4-1 “How to identify the Vendor ID and Product ID of your USB dongle?”.
4. Added Section 4-2 and Section 4-3.
5. Removed “Appendix A. AX88179/AX88178A Script Files” section.
2.01
2014/06/10
1. Modified some descriptions in Section 2.
I believe the current driver is into version 2.0 and you still have version 1.8.0
worth a check out.
Have you updated your VMWare software recently? If it's an old version you may be having compatibility issues with the VMWare graphics drivers.
I checked VMWare site and found some issues so you might search through that site a bit for answers.
https://communities.vmware.com/message/2408568?tstart=0
This is an old discussion from the Apple site:
https://discussions.apple.com/docs/DOC-5403
The point is if a driver is not a native Apple one, or an Apple driver has been modified by a program it may be your problem, especially when graphics are involved, which it appears is the heart of your kernel panic.
Again good luck in solving the issue, I suggest starting with an update to VMWare (you might notice in the link to an old discussion it was "parallels" that caused the panics in that machine).
The only kernel panics I've had over several/many machines (5 different MB laptops and three different minis) and almost two decades of Mac OS X have been on hackintosh devices, and that's understandable.
With the exception of truly hardware related issues where could these panics be coming from? I would ask if you are running real time games from online sights? The software drivers, especially video, needed by these games may be at the heart of the panics.
The only Mac I ever had issues with was the early 2010 MB 11" Air and it would occasionally restart on its own when driving it hard MS Word and multiple windows and programs in use. It was a known issue and seemed to have something to do with the nvidia gpu used in that model.
Good luck and keep us informed.
*****
OK I went back and read you kern panic log and the same issue seems to pop up, VMWare.
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8bd0a9fa): "[IGPU] Failed to wake the ME.\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.14.73/Common/GLKernel/Intel/skl/sched3/IGGuC.cpp:1238
...
loaded kexts:
com.vmware.kext.vmioplug.12.2.9 12.2.9
and
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8c77a9d2): "[IGPU] Failed to wake the ME.\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.14.66/Common/GLKernel/Intel/skl/sched3/IGGuC.cpp:1238
...
System uptime in nanoseconds: 28298643087029
last loaded kext at 24105967081593: com.asix.driver.ax88179-178a 1.8.0 (addr 0xffffff7f8ce74000, size 53248)
last unloaded kext at 24210649561320: com.apple.driver.AppleMikeyHIDDriver 124 (addr 0xffffff7f8cdd0000, size 12288)
loaded kexts:
com.asix.driver.ax88179-178a 1.8.0
com.vmware.kext.vmioplug.12.2.9 12.2.9
It also looks like you have an outdated asix driver:
From Asix web site:
AX88179/AX88178A Mac OS X Driver Installation Guide
Revision History Revision
Date
Description
1.00
2012/09/10
Initial release.
2.00
2014/02/25
1. Modified to support Mac OS X 10.9 driver installer.
2. Modified some descriptions in Section 1.
3. Replaced Section 4-1 “Driver Installation Failure on OS X 10.8 Issue” with new Section 4-1 “How to identify the Vendor ID and Product ID of your USB dongle?”.
4. Added Section 4-2 and Section 4-3.
5. Removed “Appendix A. AX88179/AX88178A Script Files” section.
2.01
2014/06/10
1. Modified some descriptions in Section 2.
I believe the current driver is into version 2.0 and you still have version 1.8.0
worth a check out.
Have you updated your VMWare software recently? If it's an old version you may be having compatibility issues with the VMWare graphics drivers.
I checked VMWare site and found some issues so you might search through that site a bit for answers.
https://communities.vmware.com/message/2408568?tstart=0
This is an old discussion from the Apple site:
https://discussions.apple.com/docs/DOC-5403
The point is if a driver is not a native Apple one, or an Apple driver has been modified by a program it may be your problem, especially when graphics are involved, which it appears is the heart of your kernel panic.
Again good luck in solving the issue, I suggest starting with an update to VMWare (you might notice in the link to an old discussion it was "parallels" that caused the panics in that machine).
Last edited:
To anyone who suspects that a kernel panic may occur, a repeat of the earlier plea. With added emphasis:
Address-to-symbol translation will allow subsequent .panic files to include information that is more human-friendly.
- start Recovery OS
- in Terminal, enter the command below
- restart (macOS).
Address-to-symbol translation will allow subsequent .panic files to include information that is more human-friendly.
The last time i had a kernel panic issue it was the Dedicated GPU going bad and it was part of the warranty extension program from apple for 2012 machines. I wonder what the threshold is for them to go ok we have some issues lets capture these machines and figure out what we need to do is it 100 machines 1000 machines there has to be some sub-set of quantity that ticks the box for them to go oh we have an issue we need to address it. I am in hopes they can address this with a firmware update to the boxes as I highly doubt all the CPU dies are roached.
Not having any here, either -- then again I've only had my rMB M7 just over a week and have, after the initial setup and getting things organized to my satisfaction, used the machine sporadically on a daily basis since it is not my primary computer. I LOVE this thing! Cannot be beat for portability! Wow!
Does your log show non-Apple stuff at point of panic? I may have missed it but do you use VMware?
Are you using Apple adapter and cable for the monitor connection?
Have you tried plugging the monitor into a "clean" boot or booted in recovery mode with the monitor plug in?
Basically you have to keep eliminating what the problem isn't before you'll know what it is.
I was just at Apple getting a phone repair. I could find no logs of kernel panics on the display units. I found loads of minor software crashes so I tend to want to think they have not scrubbed the logs.
This machine definitely seems to be new Apple in the sense it has issues
This machine definitely seems to be new Apple in the sense it has issues
I do not use VMware or have it installed.
I have the LG 4k USB-C Type monitor so the cable that was provided by LG I plug directly to my rMB USB C port to the USB C port behind the monitor. No adapters are being used.
I've used the 4k @ 60hz patch as well so I'm pretty sure that is what it is that is causing this kernel panic.
Yep, probably. I have the 12" rMB since it came out last year, 1.2 512, and I basically understand Apple did not build it for 4K monitors. So, like the hackintosh, patches can be very unstable with foreign, non-Apple, hardware. I wonder if the provided cable may also have something to do with the panics using the monitor.
Just a brief update from my side. Kernel panics first appeared when I began to use VMWare horizon client (do not confuse with Fusion, this is a VDI client), MS Lync and a BT mouse.
In the past 4 days I haven't used any of these and everything seems to work fine now without reinstalling system.
Could other users having kernel panics share their daily use? Maybe its all about drivers and there is really no HW issue.
In the past 4 days I haven't used any of these and everything seems to work fine now without reinstalling system.
Could other users having kernel panics share their daily use? Maybe its all about drivers and there is really no HW issue.
/Library/Logs/DiagnosticReports/
The name of each .panic file will begin with the phrase Kernel_
Relatively unintelligible information: an example
In this photograph, the backtrace begins with six lines of 0xffffff… stuff, which is not meaningful to the average person:
From the same person, a comparable backtrace including words/phrases – at the tails of lines – that are more intelligible:
Backtrace (CPU 3), Frame : Return Address
0xffffff82068b3b40 : 0xffffff801c53a811 mach_kernel : _panic + 0xd1
0xffffff82068b3bc0 : 0xffffff801c61e80a mach_kernel : _kernel_trap + 0x84a
0xffffff82068b3d80 : 0xffffff801c63a443 mach_kernel : _return_from_trap + 0xe3
0xffffff82068b3da0 : 0xffffff801c30e11b
0xffffff82068b3ed0 : 0xffffff801c97d684 mach_kernel : _NodesAreContiguous + 0x1794
0xffffff82068b3f80 : 0x0
0xffffff82068b3b40 : 0xffffff801c53a811 mach_kernel : _panic + 0xd1
0xffffff82068b3bc0 : 0xffffff801c61e80a mach_kernel : _kernel_trap + 0x84a
0xffffff82068b3d80 : 0xffffff801c63a443 mach_kernel : _return_from_trap + 0xe3
0xffffff82068b3da0 : 0xffffff801c30e11b
0xffffff82068b3ed0 : 0xffffff801c97d684 mach_kernel : _NodesAreContiguous + 0x1794
0xffffff82068b3f80 : 0x0
Please note, what's above is not from a MacBook; I offer that example to demonstrate the value of setting keepsyms=y as a boot argument in NVRAM.
Getting more from kernel panics with keepsyms (address to symbol translation)
Last edited:
Well, anyone still wondering whether to try to get their Macbook swapped for a new one, don't bother. Like others, a new one exhibits the same behaviour. In fact, happened the first time I left it overnight! In my other post at https://forums.macrumors.com/threads/kernel-panics-on-macbook-12-9-1.1980359/page-4#post-23316896, I explained how these Macs wake themselves out of standby every 2 hours. Apart from wasting battery and shortening its life, it's also reading and writing a sleep image every time, which shortens the life of the SSD. My new Macbook, with its fresh OS install and just signing into iCloud on a new user, still does this so I'm guessing they all do. No other Macs do this when on battery. I reckon this is another bug.
I'm trying something now to see if it eliminates the panics. Macs have a standbydelay time. They go into normal sleep mode after whatever time you've set, then go into standby (aka hibernate) after standbydelay. On these Macs, standbydelay is by default set to 10800, which is 3 hours. So the Mac sleeps after the sleep time, wakes up after 2 hours because of the other possible bug, then an hour later goes into standby. Then every 2 hours after that it comes out of standby, reading the sleepimage, and a short while later goes back into standby. Standby is a much deeper state of sleep that turns most stuff off (I think part of the sleep bug is that it keeps wifi on, but that's another story). So I'm going to try disabling standby altogether. The machine will only ever sleep and never go into the deep standby state. Maybe this will stop the panics. Downside is that sleep using more battery than standby - but a lot less than the huge drain when the panic bug rears its ugly head! Disabling standby is pretty easy:
Start the Terminal app from a user with admin privileges.
Enter the command:
sudo pmset -b standby 0
Enter your password and that's it. The -b parameter says to only affect the battery settings. You can see all the power management settings using:
Pmset -g
To revert, use:
sudo pmset -b standby 1
Anyone else willing to give this a go?
I'm trying something now to see if it eliminates the panics. Macs have a standbydelay time. They go into normal sleep mode after whatever time you've set, then go into standby (aka hibernate) after standbydelay. On these Macs, standbydelay is by default set to 10800, which is 3 hours. So the Mac sleeps after the sleep time, wakes up after 2 hours because of the other possible bug, then an hour later goes into standby. Then every 2 hours after that it comes out of standby, reading the sleepimage, and a short while later goes back into standby. Standby is a much deeper state of sleep that turns most stuff off (I think part of the sleep bug is that it keeps wifi on, but that's another story). So I'm going to try disabling standby altogether. The machine will only ever sleep and never go into the deep standby state. Maybe this will stop the panics. Downside is that sleep using more battery than standby - but a lot less than the huge drain when the panic bug rears its ugly head! Disabling standby is pretty easy:
Start the Terminal app from a user with admin privileges.
Enter the command:
sudo pmset -b standby 0
Enter your password and that's it. The -b parameter says to only affect the battery settings. You can see all the power management settings using:
Pmset -g
To revert, use:
sudo pmset -b standby 1
Anyone else willing to give this a go?