-
-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M1 Mac Mini Kernel Panic on Restart #2513
Comments
Since Karabiner-Elements v13.0.0, it is now not related with kernel. |
I understand what you are saying, but I do want to mention that the problem appears after installing karabiner, and resolves after uninstalling. I have done this twice to confirm. |
In that case, I guess that Karabiner-Elements triggers an issue of some other incompatible third-vendor apps with Big Sur (e.g., anti-virus software), and the issue causes kernel panic. |
I am also experiencing kernel panic when restarting my M1 MacBook Air (see #2517) and uninstalling Karabiner Elements seems to be the only way to fix it. I don't have any anti-virus software installed. Actually my first thought was that Dropbox and iStatMenu might be the cause as those are not yet fully compatible with M1 Mac, so I uninstalled them but the issue persisted. Then I uninstalled Karabiner-Elements, which fixed the issue. The issue did not reemerge after installing Dropbox and iStatMenu again. |
Same issue for myself - on a fresh setup, no issue without Karabiner, kernel panic with. Does anyone have an M1 Mac with Karabiner and not getting the kernel panic on reboot? (i.e. when you reboot, it doesn't show "your computer restarted because of a problem" after logging in). Hopefully we can narrow down who all this is affecting |
I get the same issue on my M1 Mac Mini. macOS Big Sur 11.0.1 (20B29) I have not yet installed most of the software other than the OS pre-installed. |
I just set up my Mac Mini M1 and am getting the same error message. Seems to consistently be triggered upon restart/shutdown. If I quit the app before shutting down, it still happens. My Mac was a migration tool setup from a 2013 15” MacBook Pro. |
I have the exact same issue with my MacBook Air M1 + Big Sur 11.0.1. Every time I shutdown or restart my MBA, I get a pop up after booting up and logging in saying "your computer restarted because of a problem". I don't have any issues if I uninstall Karabinar Elements, so I'm pretty sure this app is the culprit. |
Just a me too on this with 11.0.1 + Mac Mini M1. |
Me too on MBP M1 :( |
Same here :( Must use Karabiner Elements as I use a PC keyboard and want to invert Command/Alt.. |
I spent 2 hours checking my system with disk utility, removing Docker, Virtualbox and all software I thought could be the source of this crash, ended up being my lovely Karabiner Elements I use for years to remap Command and Alt. I confirm removing it fixes the issue, and I now use instructions available at https://superuser.com/questions/80976/how-to-re-map-command-and-option-keys-on-mac-os-x-with-a-pc-keyboard and MacOS settings to remap those, you can choose which keyboard you want those change on so I guess even laptop users will be happy. So long Karabiner, I liked you before! :) |
To confirm this is still happening with macOS Big Sur 11.1 (20C69) on a MacBook Pro (13-inch, M1, 2020). The kernel panic did not affect the install of the 11.1 update either. |
Same here... using m1 mac mini :( cannot use mac without Karabiner... but I had to uninstall it to shutdown my mac.. |
I have also had to uninstall Karabiner... what a pity!! |
To be clear, you shouldn’t have to uninstall Karabiner. Everything works correctly. It kernel panics at the very last step of restart and if you really want to shutdown but it keeps rebooting, click shutdown from the login screen. |
If I don't uninstall Karabiner, I cannot shut down my Mac since it always restarts after the LED indicator goes off. Even clicking shutdown from the login screen won't shut down the Mac, it keeps restarting. |
Same issue. Only thing that works for me is logging out first, then shutting down from the login screen. |
However, this IS the Karabiner issue, for so many people has proved that this crash happens and ONLY happens when Karabiner is installed on M1 Mac. The perfect solution is here: |
@windless0530 thanks for the suggestion. I've tested my environment with your solution. Are there more tricks or solution for this case? BR. |
Also have this issue. |
I agree, I am facing the same issue on Mac Mini M1, macOS 11.1 and Karabiner 13.1.0
:( I just need to remap one single key on a new Logitech keyboard... need to learn how to develop: had a look but too ,much complicated for me. I guess I will wait for a new version of Karabiner. thank you |
Not sure if anyone else experienced this, there was a few boots that froze my cursor entirely (both trackpad and external mouse). device: Macbook Pro m1 I uninstalled Karabiner for now, also no luck with hammerspoon. |
I just found this thread after experiencing this problem and was able to narrow down what seems to be causing the crash for me. I'm on a 13" 16GB M1 MacBook Pro, Big Sur 11.1. I installed the latest Karabiner-Elements 13.1.5 (Beta) and discovered that it only encounters kernel panic if I try to shutdown with an UNSAVED text document open (TextEdit, VSCode, etc.). It does not seem to matter if the document is left open; only that it be saved before shutting down. I know this sounds strange, but that seems to be the only condition that causes my machine to panic on shutdown. Otherwise, it shuts down completely normal. |
Hello Paul,
This is a great clue for the developer!
Let’s hope with the next version this bug will be definitely fixed =)
Thank you!
Ugo
On Sat, 9 Jan 2021 at 08:02, Paul Casavant ***@***.***> wrote:
I just found this thread after experiencing this problem and was able to
narrow down what seems to be causing the crash for me. I'm on a 13" M1
MacBook Air, Big Sur 11.1. I installed the latest Karabiner-Elements 13.1.5
(Beta) and discovered that it only encounters kernel panic if I try to
shutdown with an UNSAVED text document open (TextEdit, VSCode, etc.). It
does not seem to matter if the document is left open; only that it be saved
before shutting down.
I know this sounds strange, but that seems to be the only condition that
causes my machine to panic on shutdown. Otherwise, it shuts down completely
normal.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF7ORSATREODS6HWBWU3L3SY75ORANCNFSM4T22QMAQ>
.
--
Sent from a mobile device
|
@paulcasavant Does ticking the 'Settings > General > Close windows when quitting an app' have any bearing on the kernel panic for you? And how do you know if you have any unsaved documents? |
What I mean by "unsaved document" is that if I opened a text file in TextEdit or VSCode and tried to shutdown without first either saving or closing the file, I would encounter a panic. If I repeated the same steps, but saved the file before shutting down, the system would shutdown normally and I would not experience the sudden freeze, pink screen, and "system did not shutdown correctly...or whatever" message upon restarting. I should also add that I should not have said "TextEdit, VSCode" etc." as I only tested it with those two programs and nothing else. ALSO, I misspoke in previous comment and said I have a MacBook Air when I actually have the 13" 16GB M1 MacBook Pro. I verified that I could only replicate the bug if Karabiner was installed. I think you might be onto something, agentk. I have restarted my machine numerous times in an attempt to find a pattern. First of all, in most of my trials, I tried shutting down with an unsaved document, but I also threw in a few "normal" cases where I did not have an unsaved document open. As expected, across numerous trials I never encountered kernel panic unless there was an unsaved document open. I cannot explain the results, but I will try to recount what happened... The 'Close windows when quitting app' setting was ENABLED for me by default and so I tried DISABLING it. This resulted in the issue completely going away. I could shutdown with saved and unsaved documents open and would be unable to reproduce the bug. After a bunch of trials, I tried RE-ENABLING the setting and found that the bug was still gone. Here is where it gets weird... I then DISABLED the setting again and experienced one kernel panic with an unsaved document, but then it worked fine with unsaved documents on several subsequent trials and I was unable to reproduce it. Next I RE-ENABLED the setting again and experienced several kernel panics with unsaved files. Next I DISABLED it again and did not experience the issue at all with saved or unsaved documents. Except for that one case, the issue seems to be completely gone with that setting DISABLED. I cannot explain why it sometimes works with the setting ENABLED. Before messing with that setting, I had 100% consistency in kernel panic with an unsaved document. This is all very strange and I cannot explain it, but hopefully this helps someone. See my crash report below.
|
@paulcasavant I haven't been able to replicate any of your crash free restarts unfortunately. I uninstalled 13.1.0, rebooted a couple of times and verified it reboots cleanly. Installed 13.1.5 and rebooted, pink screen on initial reboot. Checked all apps I could find to verify I didn't have any unsaved document changes. Rebooted a few times with and without the 'Close windows when quitting an app' toggle checked. Kernel panic every time for me still. |
agreed
El El sáb, 16 ene 2021 a las 18:24, DumbGameMaker <notifications@github.com>
escribió:
… It's so sad when a must-have app on mac causing kernel panic, yet the
developer didn't bother to investigate and closed the issue right away. We
can do the tests all you want, just don't close it like this. The panic is
consistent, I don't understand why it's still there for over a month. I
guess it's time to say goodbye.
he is just trying to brush this under the rug so he doesn't have to deal
with it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4P75LT55JMG3CJMCFM3ATS2HDTZANCNFSM4T22QMAQ>
.
|
Here is how I map
More details at: https://www.nanoant.com/mac/macos-function-key-remapping-with-hidutil |
I installed karabiner a few days ago. Since then I have the kernel panics when waking up from sleep mode. :( |
Same problem on a Mac MINI M1. Please reopen. |
I don't experience this issue on 11.2 RC anymore |
really? |
yeah, using it over a day now with M1 Mac mini, no kernel panic and, as a bonus, boot up speed become almost twice as fast. |
where can I download it?
…On Sat, Jan 23, 2021 at 11:01 PM Tim Nedvyga ***@***.***> wrote:
I don't experience this issue on 11.2 RC anymore
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF7ORRTRR6D2JS7IXO3OOLS3NBM5ANCNFSM4T22QMAQ>
.
|
Thanks, It works for me. |
FYI, I partially achieve Hyper key with: https://gist.github.com/tvhung83/9f8240cb79c066d3b7b4a403c90a5018 |
The official version is coming out, so I want to upgrade in advance. |
Still kernel panics on 11.2 RC. I just uninstalled karabiner. I hope the crashes will stop now. Really annoying. Tried Hammerspoon but the inputs feels quite slow to me.... Are there any other ways to map |
karabiner-elements issue: pqrs-org/Karabiner-Elements#2513
Hi @patlux . I was using Karabiner Elements to map Here is a video explaining how I set it up. And here are the files if you want to try it: Note that when you import the macro group it will be disabled by default. You will need to enable the group for it to work. |
@jonpdw Man thank you a lot! Great video! Just installed Keyboard Maestro with your macros and it just works as fast as with karabiner. 💪 |
Yay, I am so glad it helped |
Can I use Keyboard Maestro to remap right control to right option? Or
is this something it can't do? Thanks.
…On 1/27/21, jonpdw ***@***.***> wrote:
Yay, I am so glad it helped
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#2513 (comment)
|
Hi @ogomez92 Keyboard Maestro can do it but its a little verbose. Here are the macros you see in the video Let me know if it works for you? |
Hi thanks very much for the video but this will not help, I need the
control key to act as option key, not change every shortcut. Thanks
though very much for the effort :)
…On 1/27/21, jonpdw ***@***.***> wrote:
Hi @ogomez92 Keyboard Maestro can do it but its a little verbose.
Here is a
[video](https://www.youtube.com/watch?v=zt9mY4S0TtM&feature=youtu.be)
explaining how to do it
[Here are the macros you see in the
video](https://github.com/pqrs-org/Karabiner-Elements/files/5880392/Right.Control.-.Right.Option.Macros.kmmacros.zip)
Let me know if it works for you?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#2513 (comment)
|
@ogomez92 I did it with hidutil property --set '{"UserKeyMapping":[{"HIDKeyboardModifierMappingSrc":0x0007000000e7,
"HIDKeyboardModifierMappingDst":0x0007000000e6}]}' You can also create a file which will execute the command on login. /edit: Oh sorry, you want to swap control with option. The snippet above maps the right cmd to right option. Just change the |
Oh I see. Haha that’s all good. What is the use case? There might still be
a way to do what you want.
On Thu, 28 Jan 2021 at 2:21 AM, ogomez92 ***@***.***> wrote:
Hi thanks very much for the video but this will not help, I need the
control key to act as option key, not change every shortcut. Thanks
though very much for the effort :)
On 1/27/21, jonpdw ***@***.***> wrote:
> Hi @ogomez92 Keyboard Maestro can do it but its a little verbose.
> Here is a
> [video](https://www.youtube.com/watch?v=zt9mY4S0TtM&feature=youtu.be)
> explaining how to do it
>
> [Here are the macros you see in the
> video](
https://github.com/pqrs-org/Karabiner-Elements/files/5880392/Right.Control.-.Right.Option.Macros.kmmacros.zip
)
>
> Let me know if it works for you?
>
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
>
#2513 (comment)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH27VAWPGXHGTJCKRF6YNPTS4AHNLANCNFSM4T22QMAQ>
.
--
-Jonathan de Wet
|
Just adding that I also encountered this kernel panic. I uninstalled Karabiner and it went away. |
Unchecking karabiner_grabber and karabiner_observer in Input Monitoring in Privacy & Security in System Preferences on my M1 Mac Mini stops the panic and the "restarted due to problem" messages after restarts. This of course renders Karabiner inoperable. When I rechecked them as a test, then restarted the Mac Mini, the "restarted due to problem" message reappeared. |
It’s incredible how the standardization of jobs made support a pain. The
Apple “advisor” should try it on his system rather than making you loose
time. At the end of the day you paid him already when buying the Mini.
Unfortunately this is happening more and more frequently, the support is
done by incompetent people and simply have a number of ready to use
answers...
Most of the time they it happens to me that they do not even read my email
and ask me for things that I have already explained when opening the ticket!
I think for big companies the most important thing is that they can state
that "support is available 24/7/365" but they should rather state how many
times they are able to really help a customer facing a problem – not a
problem like not having inserted the plug into the socket :)
As far as I understood the developer stated that this problem is generated
by other software so I do not see an attitude for him to try to find the
problem and fix the code.
In such cases it is better to find an alternative product.
Maybe, if the developer is wrong, when later all Macs will run on Apple
Silicon he will need to change his attitude, providing he is interested in
keeping developing software.
Good luck!
…On Mon, 1 Mar 2021 at 19:01, Semajk ***@***.***> wrote:
Unchecking karabiner_grabber and karabiner_observer in Input Monitoring in
Privacy & Security in System Preferences on my M1 Mac Mini stops the panic
and the "restarted due to problem" messages after restarts. This of course
renders Karabiner inoperable. When I rechecked them as a test, then
restarted the Mac Mini, the "restarted due to problem" message reappeared.
Before I came across this thread and realized Karabiner might be causing
the problem, an Apple advisor told me I should reinstall the operating
system on my brand new Mac Mini. I was reluctant to do that and I didn't,
and I'm glad I found this thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF7ORRAISP7JGQSPJUPMI3TBPI7DANCNFSM4T22QMAQ>
.
|
I just encountered this issue with a MacBook Air M1, and the only fix was to remove Karabiner. |
Mac Mini M1 having this issue kernel panic on restart |
karabiner crashes my m1 mac mini everytime it restarts |
Monterey 12.5.1 (21G83) on MacBook Pro (13-inch, M1, 2020) still has the bug . |
Might b isolated as i didn't experience anything like this. Maybe
provided the developers with some logs otherwise there isn't much they
can do.
…On 9/10/22, 漫者 ***@***.***> wrote:
Monterey 12.5.1 (21G83) on MacBook Pro (13-inch, M1, 2020) still has the
bug .
Karabiner-Elements-14.8.0
--
Reply to this email directly or view it on GitHub:
#2513 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
On machine restart, the dock hiding animation freezes midway, which to me indicates a hang. On booting back to desktop, the crash reporter appears with the below text. I cut off the long list of loaded kexts but can provide those if needed.
The text was updated successfully, but these errors were encountered: