Machine automately reboots after login System 10 mins
zhxiyao opened this issue · comments
Describe the bug
Machine automatically reboots after kernel panic. It occurs about 10 mins after logging into system every time.
This issue exists a long time since Hacmini v 2.x.
message on the screen:
"BIOS has detected unsuccessful POST attempt(s).
Possible causes include recent changes to BIOS Performance Options or recent hardware change.
Press "y" to enter Setup or "N' to cancel and attempt to boot with previous settings."
Expected behavior
No reboots in longrun.
Configuration
HaC Mini version [e.g: 2.0]: v3.11
OSX version [e.g: 10.14.6]: 10.16
NUC model [e.g: NUC8i7HNK]: NUC8i7HVK
Boot SSD model and protocol [e.g: Samsung EVO 860 1TB, SATA]: WD Black SN750 512MB [NVMe] with both Mac and Win 10
Second SSD model and protocol (if installed) [e.g: HP EX920 1TB, NVMe]: Intel 660P 1T
DIMM model [e.g: Patriot DDR4-2666 16GB]: Kingston HyperX KHX2666C15S4/16G x 2
Display port(s) used [e.g: USB-C, mini DP]: mini DP
Display resolution(s) [e.g: 4K, 5K]: 4K monitor
Any TB3 devices: NA
Any USB devices: mouse, keyboard
Any Wi-Fi/Bluetooth devices [e.g:DW1820A, BCM94360CS2, Intel 8265]: DW1820A
Modifications
No
Panic log
Include a screenshot of the panic message if applicable.
Interesting, the same rebooting occurred during I upgraded Win11. It just rebooted without any sign, same with that in MacOS. After the rebooting, the BIOS error msg presented: "BIOS has detected unsuccessful POST attempt(s).
Possible causes include recent changes to BIOS Performance Options or recent hardware change.
Press "y" to enter Setup or "N' to cancel and attempt to boot with previous settings."
Then press "N", System went back to win10. It told that The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation. Error No. 0xC1900101 - 0x2000D.
The system log before and after the rebooting:
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0200-0000-0000-000000000000[1584]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0100-0000-0000-000000000000[1583]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0000-0000-0000-000000000000[1586]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0200-0000-0000-000000000000[1585]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0300-0000-0000-000000000000[1582]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0100-0000-0000-000000000000[1580]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:43 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0000-0000-0000-000000000000[1587]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0500-0000-0000-000000000000[1560]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0100-0000-0000-000000000000[1577]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0400-0000-0000-000000000000[1568]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0300-0000-0000-000000000000[1569]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0300-0000-0000-000000000000[1578]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0000-0000-0000-000000000000[1581]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0700-0000-0000-000000000000[1567]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:44 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0400-0000-0000-000000000000[1570]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:20:45 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0300-0000-0000-000000000000[1579]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:21:47 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0500-0000-0000-000000000000[1591]): Service exited due to SIGKILL | sent by mds[85]
Oct 16 12:21:52 Mini com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0400-0000-0000-000000000000[1590]): Service exited due to SIGKILL | sent by mds[85]
Reboot with no sign
Oct 16 20:42:32 localhost bootlog[0]: BOOT_TIME 1634388152 0
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.cdscheduler" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.install" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/asl" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.authd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.eventmonitor" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.mail" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.performance" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.iokit.power" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.contacts.ContactsAutocomplete" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.mkb" sharing output destination "/private/var/log/keybagd.log" with ASL Module "com.apple.mkb.internal".
Output parameters from ASL Module "com.apple.mkb.internal" override any specified in ASL Module "com.apple.mkb".
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.mkb" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.AddressBookLegacy" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.MessageTracer" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost syslogd[55]: Configuration Notice:
ASL Module "com.apple.clouddocs" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Oct 16 20:42:34 localhost com.apple.xpc.launchd[1]: launchd logging initialized
Another 2 times of Panic log:
1st:
panic(cpu 0 caller 0xffffff80105b3b9f): "32KHz LPO Clock not running"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AirPortDriverBrcmNIC/AirPortDriverBrcmNIC-1675.1/src/shared/macosx_osl.cpp:2138
Backtrace (CPU 0), Frame : Return Address
0xffffffa0a8363760 : 0xffffff800eabab4d
0xffffffa0a83637b0 : 0xffffff800ebfd7e3
0xffffffa0a83637f0 : 0xffffff800ebede1a
0xffffffa0a8363840 : 0xffffff800ea5fa2f
0xffffffa0a8363860 : 0xffffff800eaba3ed
0xffffffa0a8363980 : 0xffffff800eaba6d8
0xffffffa0a83639f0 : 0xffffff800f2bef9a
0xffffffa0a8363a60 : 0xffffff80105b3b9f
0xffffffa0a8363ae0 : 0xffffff801087e135
0xffffffa0a8363b20 : 0xffffff801087dc1f
0xffffffa0a8363b40 : 0xffffff8010695158
0xffffffa0a8363b70 : 0xffffff80106b8110
0xffffffa0a8363c50 : 0xffffff80105c1809
0xffffffa0a8363c70 : 0xffffff80105c718d
0xffffffa0a8363d10 : 0xffffff80105c29f4
0xffffffa0a8363d40 : 0xffffff800f21964f
0xffffffa0a8363da0 : 0xffffff80105c6487
0xffffffa0a8363df0 : 0xffffff800f1fcda1
0xffffffa0a8363e60 : 0xffffff800f1fcb3a
0xffffffa0a8363e80 : 0xffffff800eaff725
0xffffffa0a8363ef0 : 0xffffff800eb00634
0xffffffa0a8363fa0 : 0xffffff800ea5f13e
Kernel Extensions in backtrace:
com.apple.driver.AirPort.BrcmNIC(1400.1.1)[729DC69F-0B01-3807-B946-AE96C4584DA1]@0xffffff8010591000->0xffffff8010aebfff
dependency: com.apple.driver.corecapture(1.0.4)[DDCF23B4-962A-3A18-B089-CD07BDAD9A35]@0xffffff8011be4000->0xffffff8011bfafff
dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[35ABC470-4743-30AC-9BA8-4A62CFA2296D]@0xffffff8011419000->0xffffff801141dfff
dependency: com.apple.iokit.IO80211Family(1200.12.2b1)[27EDE1C0-32A1-3BC9-A93A-49B4E7AD2167]@0xffffff8010440000->0xffffff8010579fff
dependency: com.apple.iokit.IONetworkingFamily(3.4)[CEA28E53-3048-362D-B58E-3A02FFC20EA9]@0xffffff8011196000->0xffffff80111acfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[BF2C5E86-1E8F-3FD4-9874-7738178FA73B]@0xffffff801141f000->0xffffff8011446fff
dependency: com.apple.iokit.IOSkywalkFamily(1)[882D8199-A1D6-3A53-9A83-1D11A15DECFA]@0xffffff80114e9000->0xffffff8011526fff
Process name corresponding to current thread: kernel_task
Boot args: alcid=11 -disablegfxfirmware shikigva=32 shiki-id=Mac-BE088AF8C5EB4FA2 -radcodec igfxmetal=1
Mac OS version:
20D64
2nd:
panic(cpu 0 caller 0xffffff80029b3b9f): "32KHz LPO Clock not running"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AirPortDriverBrcmNIC/AirPortDriverBrcmNIC-1675.1/src/shared/macosx_osl.cpp:2138
Backtrace (CPU 0), Frame : Return Address
0xffffffa09ca1b760 : 0xffffff8000ebab4d
0xffffffa09ca1b7b0 : 0xffffff8000ffd7e3
0xffffffa09ca1b7f0 : 0xffffff8000fede1a
0xffffffa09ca1b840 : 0xffffff8000e5fa2f
0xffffffa09ca1b860 : 0xffffff8000eba3ed
0xffffffa09ca1b980 : 0xffffff8000eba6d8
0xffffffa09ca1b9f0 : 0xffffff80016bef9a
0xffffffa09ca1ba60 : 0xffffff80029b3b9f
0xffffffa09ca1bae0 : 0xffffff8002c7e135
0xffffffa09ca1bb20 : 0xffffff8002c7dc1f
0xffffffa09ca1bb40 : 0xffffff8002a95158
0xffffffa09ca1bb70 : 0xffffff8002ab8110
0xffffffa09ca1bc50 : 0xffffff80029c1809
0xffffffa09ca1bc70 : 0xffffff80029c718d
0xffffffa09ca1bd10 : 0xffffff80029c29f4
0xffffffa09ca1bd40 : 0xffffff800161964f
0xffffffa09ca1bda0 : 0xffffff80029c6487
0xffffffa09ca1bdf0 : 0xffffff80015fcda1
0xffffffa09ca1be60 : 0xffffff80015fcb3a
0xffffffa09ca1be80 : 0xffffff8000eff725
0xffffffa09ca1bef0 : 0xffffff8000f00634
0xffffffa09ca1bfa0 : 0xffffff8000e5f13e
Kernel Extensions in backtrace:
com.apple.driver.AirPort.BrcmNIC(1400.1.1)[729DC69F-0B01-3807-B946-AE96C4584DA1]@0xffffff8002991000->0xffffff8002eebfff
dependency: com.apple.driver.corecapture(1.0.4)[DDCF23B4-962A-3A18-B089-CD07BDAD9A35]@0xffffff8003fe4000->0xffffff8003ffafff
dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[35ABC470-4743-30AC-9BA8-4A62CFA2296D]@0xffffff8003819000->0xffffff800381dfff
dependency: com.apple.iokit.IO80211Family(1200.12.2b1)[27EDE1C0-32A1-3BC9-A93A-49B4E7AD2167]@0xffffff8002840000->0xffffff8002979fff
dependency: com.apple.iokit.IONetworkingFamily(3.4)[CEA28E53-3048-362D-B58E-3A02FFC20EA9]@0xffffff8003596000->0xffffff80035acfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[BF2C5E86-1E8F-3FD4-9874-7738178FA73B]@0xffffff800381f000->0xffffff8003846fff
dependency: com.apple.iokit.IOSkywalkFamily(1)[882D8199-A1D6-3A53-9A83-1D11A15DECFA]@0xffffff80038e9000->0xffffff8003926fff
Process name corresponding to current thread: kernel_task
Boot args: alcid=11 -disablegfxfirmware shikigva=32 shiki-id=Mac-BE088AF8C5EB4FA2 -radcodec igfxmetal=1
Mac OS version:
20D64
Kernel version:
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
KernelCache slide: 0x0000000000c00000
KernelCache base: 0xffffff8000e00000
Kernel slide: 0x0000000000c10000
Kernel text base: 0xffffff8000e10000
__HIB text base: 0xffffff8000d00000
System model name: Macmini8,1 (Mac-7BA5B2DFE22DDD8C)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 6095495356582
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000058b37d5e857
Sleep : 0x00000589a8bb2653 0x0000000303b5afc0 0x0000057a5840a78c
Wake : 0x0000058ae3bb299e 0x0000000305dcece2 0x00000589ac20e513
Update: After disabled bluetooth in BIOS (DW1820A), the system got stable. So it might results from the bluetooth. I am not sure but It said the windows driver could update a firmware of the bluetooth which is not compatible with the MacOS.
Hello zhxiyao
I need to write this down somewhere. I have NUC8I7HVK. I'm not running MAC stuff in in, instead I'm running VMware ESXi 7.something. I have recently seen a couple of strange lock-ups. Latest was yesterday.
My wife was vacuum-cleaning nearby. Suddenly remotely I experienced total disconnection to my virtual machines on the host. I tried to put in HDMI cable to any of the 2 ports => no picture whatsoever. There was HDMI "carrier" signal but picture was black. Tried with keyboard => nothing. Tried with another port on switch => nothing. It was totally dead. QNAP NAS on same router, same UPS was totally fine. (QNAP had also direct connection to NUC. QNAP logs showed still a connection from NUC, but it might have been waiting for a timeout.)
I rebooted the NUC machine. I dunno what happened, but I got that "BIOS detected unsuccessful POST attempt(s)" thingy. And I have exactly the same HW. I have been running userspace memtest program from SystemRescueCD the whole night; it seems no problems.
I suspect some kind of ground level disturbance or ESD discharge caused my box to go haywire. As strange as it is.
Update: After disabled bluetooth in BIOS (DW1820A), the system got stable. So it might results from the bluetooth. I am not sure but It said the windows driver could update a firmware of the bluetooth which is not compatible with the MacOS.
Since 3.21 I got random kernel panics. The affected process name is different every time. I now noticed that the issue only seems to occur if I reboot to MacOS (now Ventura but was the same for Monterey before) after running Windows 11. If I boot directly to MacOS without running Windows first, there are no issues.
I am running a DW1820A and this does indeed remind me of the times when support for DW1820A just started and the bluetooth firmware version in Windows had to match the bluetooth firmware version in MacOS.
What logging can I do to help narrowing down this issue?
the same observation here. After booting into windows 11 (and updating windows), the random kernel panic appears. I tried to reinstall hac-mini and bless partition again, sometimes the system gets stable.
And I'm not using DW1820A, I'm using a BCM
Just an update. I notice that the issues usually happen when there is incomplete upgrade in windows, e.g, windows need reboot to install upgrades, but I boot into Mac.
Once the window upgrade process is finished, it seems Mac system would get stable ...
More info about my setup, I have two SSDs, install Mac and Windows seperately
One more update, I just checked the secure boot opinion in BIOS (with secure values with defaults). The kernel panic never happens again so far.