Maybe one reason I haven't had any problems with my rMB (or for that matter, my rMBP) is that I don't use the "sleep" function at all..... The machine is either on as I'm using it or it's shut down completely.
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
Yep, that'd do it! So you have "turn display off after" set to Never in your Power prefs for battery?
In my case, everything has been working fine now for a week. Maybe its just coincidence but I think disabling bluetooth is the key difference. Could you try that?
[doublepost=1473334905][/doublepost]
I can also confirm that my macbook wakes up exactly every 2 hours. Also with powernap and wake on wifi disabled.
Last edited:
Yes, that is correct. I decided a long time ago that I just didn't care for the "sleep" function and either I"m using my machine or I'm not. If I am going to be away from the machine for a significant time I simply go ahead and shut it down, and I shut it down each night at bedtime as well.
I really encourage those who are having "panics" to check closely the logs and look for drivers that aren't Apple.
While the Appple products do have issues and there are hardware flaws that make it past the testing process, most panics are not because of these. The logs are cryptic in that they list memory locations where the bad code hits and of course if there is a memory location which is physically bad a panic will occur.
It appears a large majority of issues seem to be because of the video and next in line are IO issues. Ask if you have anything loaded from a program which is causing the panic. Start with a clean OS X load and then slowly add back the programs you use (not from a backup) and see if the panics start again.
The only problem with this approach is, if you're like me, there is too big an investment in software and it may be impractical to not load from a backup.
Good luck to you all!
While the Appple products do have issues and there are hardware flaws that make it past the testing process, most panics are not because of these. The logs are cryptic in that they list memory locations where the bad code hits and of course if there is a memory location which is physically bad a panic will occur.
It appears a large majority of issues seem to be because of the video and next in line are IO issues. Ask if you have anything loaded from a program which is causing the panic. Start with a clean OS X load and then slowly add back the programs you use (not from a backup) and see if the panics start again.
The only problem with this approach is, if you're like me, there is too big an investment in software and it may be impractical to not load from a backup.
Good luck to you all!
I will certainly try disabling bluetooth once I've run for a while without standby. Trouble is, it takes so long to try any individual change because the panics happen only maybe once or twice a week.
[doublepost=1473369928][/doublepost]
Thanks for the comments. The only things in the backtrace in the panic logs are apple modules. Others here and on the reddit post have tried OS reinstalls with minimal additions and the problem persists. I think (hope) we're looking at a driver problem. The only solution is for us all to hit Apple support and ask for this problem to be escalated. I'm certainly intending to do that, along with the problem of these machines waking up every 2 hours, which just doesn't seem right (and might be part of the problem itself).
Last edited:
Well, yes and no. We should be reporting both the problems, which may end up being only one...
There may be three or more issues, some of which will be not for Apple to fix.
To properly tell, I'd need to see .panic files with (as previously demonstrated) address-to-symbol translation.
To properly tell, I'd need to see .panic files with (as previously demonstrated) address-to-symbol translation.
I have turned on symbols via sudo nvram boot-args="-v keepsyms=y". My plan is to try the Mac with standby off for at least another week to see if it at least bypasses the panic issue. But if I get another panic, I'll be sure to post the log here. When I rebooted after the command, I saw lots of console messages fly past. Is that normal? Also, how do I reverse the symbols? Just sudo nvram boot-args="-v keepsyms=n"?
Thanks for your interest in our problems...
@sddawson thanks, those may become frequently asked questions so I posted https://forums.macrumors.com/posts/23378363
Thanks. For some reason, I could enter the command without rebooting to recovery mode. Any idea why?
OK. https://forums.macrumors.com/posts/23378363 was based on:
(With all Apple operating systems after Mavericks, I have relatively little experience.)
- my limited experience with pre-release macOS Sierra (Mac OS X 10.12); and
- my assumption that SIP in Sierra will be no more, no less protective than SIP in El Capitan.
(With all Apple operating systems after Mavericks, I have relatively little experience.)
Oh well, chalk that one top to experience eh? El Capitan must be different I guess. BTW, never heard of TrueOS before. Sounds interesting...
2 weeks now and no more kernel panics so far. Also no more wakes every 2 hours and I didn't change anything, only disabled BT.
I had similar sleep/wake issues with my 2015 MacBook. Eventually traced the cause to Adobe Flash Player, once that was uninstalled problem went away completely.
Yep that's an old problem which I also had years ago. I never allow Adobe to auto update anything. They bury their update checker pretty deep and if I remember correctly I had to use terminal to remove the kext associated with it.
Basically nothing wrong with flash it's the updater they imbedded in the OS.
Good call/post mikelj!
Here's a link to remove it:
http://lifecs.likai.org/2011/02/real-way-to-disable-adobe-updater-from.html
The "wake every 2 hours" issue happens with a brand new OS install, with a brand new user. You only need to sign into iCloud on that user, and the machine wakes every 2 hours and, I believe, leaves wifi turned on. No Flash in sight. Others have reported the kernel panic occurs with a brand new install too. Good thought though!
I turned off Bluetooth overnight. The machine still wakes every 2 hours. Are you signed into iCloud, because that's what instigates the issue? If you are, would you mind posting a copy of the console log from the time just before you put it to sleep, to the time you woke it up, with that period covering preferably a bit over 5 hours (2 hours for the 2-hourly wake-up, another hour for it to go into standby, and another 2 hours to see if it wakes up again)? If you've managed to somehow stop it waking up, that will improve battery life while asleep and will probably also stop the panics, because they happen when the machine wakes itself up from standby (hibernation) during a long period asleep. I also presume you leave wifi turned on before you sleep there machine? Hopefully we can compare configurations and pin this down some more...
EDIT: I also have had no kernel panics with standby turned off for a bit over a week. Battery drains about 3% overnight when it just sleeps and never goes into standby, but of course, always wakes up super-quickly all the time. Still wakes up every 2 hours, but for a very short while because it doesn't have to read the sleep image and come out of standby all the time.
Your memory may be a little hazy … no mention of an extension or KEXT in that 2011 article.
I use both BlueTooth and Adobe Flash Player in my computers.....and never any problems with kernel panics. I still think the waking every two hours problem is related to the Energy settings.
Not at all. The only energy settings that affects sleep on battery is Power Nap, and we don't have that checked. The 12" Macbook is the ONLY machine I have tested that wakes like this. I've tried multiple later model Macbook Pros, an 11" Macbook and a Macbook Air. The only time I've seen anything like this is when on AC with wake for network access and power nap turned on in the Power settings for AC. On battery, it seems to behave as though wake for network access is turned on, especially since I sometimes see wake reasons of "network" even outside the periodic 2 hour wakes. When it's asleep on battery it just shouldn't be woken by things like this, unless Apple has changed something radically just for this particular model.
Yep my memory does fail me and that article is not the one I used in the past. I just found it by a simple search based on my memory and how I had to use terminal to get rid of the Adobe updater.
And it wasnt the flash player that caused the problems, it was the updater to be clear for Clix.
Here's another link:
https://forums.adobe.com/thread/1109590
And it wasnt the flash player that caused the problems, it was the updater to be clear for Clix.
Here's another link:
https://forums.adobe.com/thread/1109590
Hi there. Unfortunately you are right, I double checked my logs today and found that my computer is waking up every 2 hours again.
I can confirm that I'm signed into iCloud and seems to be the main reason for the wakes. Also, no more kernel panics if I shutdown BT before closing the lid (wifi is still on).
Also, take into account that tomorrow I may be updating to Sierra and this issue may "mysteriously" disappear
Anyway, I can hold the update and retrieve some logs for you. Do you still want me to post them and investigate further or we do make the jump to Sierra?