I think I found a Mac kernel bug (2018)
1–10 of 71 posts
Re: I think I found a Mac kernel bug (2018)
#2Re: I think I found a Mac kernel bug (2018)
#3Re: I think I found a Mac kernel bug (2018)
#4Is this fixed now ?
Re: I think I found a Mac kernel bug (2018)
#5Re: I think I found a Mac kernel bug (2018)
#6I distilled the problem in a repo so it can be reproduced with a single command: https://github.com/alin23/m1-panic
I found it while on Monterey and reported it 2 times through Feedback Assistant, but it still happens on Ventura.
NOTE: Don't try it without saving all your work, it has a very high chance of restarting your computer forcefully.
Re: I think I found a Mac kernel bug (2018)
#7Coincidentally, I also stumbled upon a way to make the kernel of Apple Silicon Macs panic and restart while developing the https://lowtechguys.com website. I distilled the problem in a repo so it can be reproduced with a single command: https://github.com/alin23/m1-panic I found it while on Monterey and reported it 2 times through Feedback Assistant, but it still happens on Ventura. NOTE: Don't try it without saving…
Re: I think I found a Mac kernel bug (2018)
#8Coincidentally, I also stumbled upon a way to make the kernel of Apple Silicon Macs panic and restart while developing the https://lowtechguys.com website. I distilled the problem in a repo so it can be reproduced with a single command: https://github.com/alin23/m1-panic I found it while on Monterey and reported it 2 times through Feedback Assistant, but it still happens on Ventura. NOTE: Don't try it without saving…
Re: I think I found a Mac kernel bug (2018)
#9Is this fixed now ?
Tested it on macOS 12.3. It's fixed.
Re: I think I found a Mac kernel bug (2018)
#10This was one call to kqueue with incorrect (but not particularly malicious, just normal C silliness) arguments, and boom!