MC-226654"Failed sysctl call" errors on start and F3 + L with certain devices
The bug
Whenever Minecraft starts with version 1.17 Prerelease 1 (on specific devices – see environment), the following errors are shown in the game log:
[Render thread/ERROR]: Failed syctl call: machdep.cpu.vendor, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.stepping, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.model, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.signature, Error code: 2
oshi.util.platform.mac.SysctlUtil is shown in the second column of the launcher's game log window.
This group of four errors is shown twice during the game start, a few seconds apart from each other.
This group of errors also is shown when pressing F3 + L.
I am unsure if this affects others.
This was not an issue in 1.16.5 or 21w20a.
Environment
macOS Big Sur (11.4)
MacBook Air 2020
ARM M1 chipset
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
LowCreated Issue:
"Failed sysctl call" error on start with certain devices
The bug
Whenever Minecraft starts with version 1.17 Prerelease 1 (on specific devices – see environment), the following errors are shown in the game log:
[Render thread/ERROR]: Failed syctl call: machdep.cpu.vendor, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.stepping, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.model, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.signature, Error code: 2oshi.util.platform.mac.SysctlUtil is shown in the second column of the launcher's game log window.
This group of four errors is shown twice during the game start, a few seconds apart from each other.
I am unsure if this affects others.
This was not an issue in 1.16.5 or 21w20a.
Environment
macOS Big Sur (11.4)
MacBook Air 2020
ARM M1 chipset
"Failed sysctl call" errors on start with certain devices
"Failed sysctl call" errors on start and F3 + L with certain devices
The bug
Whenever Minecraft starts with version 1.17 Prerelease 1 (on specific devices – see environment), the following errors are shown in the game log:
[Render thread/ERROR]: Failed syctl call: machdep.cpu.vendor, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.stepping, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.model, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.signature, Error code: 2oshi.util.platform.mac.SysctlUtil is shown in the second column of the launcher's game log window.
This group of four errors is shown twice during the game start, a few seconds apart from each other.
I am unsure if this affects others.
This was not an issue in 1.16.5 or 21w20a.The bug
Whenever Minecraft starts with version 1.17 Prerelease 1 (on specific devices – see environment), the following errors are shown in the game log:
[Render thread/ERROR]: Failed syctl call: machdep.cpu.vendor, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.stepping, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.model, Error code: 2 [Render thread/ERROR]: Failed sysctl call: machdep.cpu.signature, Error code: 2oshi.util.platform.mac.SysctlUtil is shown in the second column of the launcher's game log window.
This group of four errors is shown twice during the game start, a few seconds apart from each other.
This group of errors also is shown when pressing F3 + L.
I am unsure if this affects others.
This was not an issue in 1.16.5 or 21w20a.
![[Mod] Anthony Cicinelli](../../../data/avatars/users/10122.svg){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
This issue does not occur for me on a Mac with an Intel processor running macOS Catalina. However, it seems very plausible that this issue might affect all M1 Macs in 1.17 prerelease 1. Also, this might be related to
MC-226576becauseMC-226576was also reported in 1.17 prerelease 1 and bothMC-226576and this issue mention the OSHI library in their error messages.[Mod] markderickson, does the debug screen display your CPU info properly in 1.17 prerelease 1?
Hi [Helper] pine1needle! Yep, it seems to show fine. I'm guessing that this issue that I am experiencing is caused by the changes to debug profiling in this version, and due to the changes, it also affects others by not properly showing the CPU info. But for me, it just fails to get the CPU info in the errors, but nothing else seems to work incorrectly.
I can confirm this issue on Mac.
This has been fixed in 1.17 Pre-release 2
ARM M1 systems are not officially supported, but we will keep this issue open for when we do.