-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
MacOS Sequoia 15.1 use bind service occur reboot #196028
Comments
What is the output of |
Please don't use screenshots when sharing the output of commands in your terminal. They're often difficult to read and impossible to reuse (e.g. when looking up error messages). They also typically can't be parsed by screen readers. Instead, copy the text here and wrap them in three back-ticks (```) on the line before and on the line after to format them properly. |
Does it behave the same way when you're not running in a VM? |
same |
|
This problem doesn't seem specific to macOS 15.1. There are other reports from macOS 14.7 and 15.0: |
It seems so, because I have been using this service for a long time, and it seems that this problem has appeared since the new system was launched this year. So has no one fixed this problem yet? I would like to ask whether this problem is a problem with the service itself or a problem with the system? |
It should be a kernel problem because a user space program should not cause a kernel panic like this. I wasn't able to reproduce this on x86_64 macOS 15.1, so this may be specific to Apple Silicon. I encourage you to report this to Apple (via the "Problem Report for macOS" window in the screenshot you provided at the beginning), with the commands to reproduce this. |
I was experiencing the same issue today after doing some updating. After some testing, it looks like reverting libuv from 1.49.2 to the previously working version 1.48.0 allows BIND to start for me at latest release (9.20.3)
I was able to do this by grabbing the libuv.rb formula file and installing manually:
I then pinned it to avoid breaking things again. I will likely do further testing Monday to see if 1.49.0 or 1.49.1 is stable as well. |
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
I want use dns server test
Because install bind service support my test
What happened (include all command output)?
Execute domain resolve command:
ping github.com
Occur Immediately reboot
What did you expect to happen?
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: