Closed Fibbicles closed 3 months ago
I've attached the dump log here also: https://gist.github.com/FlopsiBunny/d2337ccee9dfa1bb852773b95e0e1b75
AMD Opteron 6172
14 year old CPU without support for simd, oof
We need a way to detect this or at least a flag to disable natives (which thought we had tbh)
cc @lax1dude
AMD Opteron 6172
14 year old CPU without support for simd, oof
We need a way to detect this or at least a flag to disable natives (which thought we had tbh)
cc @lax1dude
Does this mean this specific CPU won't be able to support it ever or is there a potential fix for this? It may be old but part of the reason I'm using it is because it's 24 cores.
It'll be able to support bungee but not the optimised natives
cc @lax1dude
I'll see what I can do
Created #3718
Created #3718
Tried that pull request, built it out and used the arguments you added but still hitting the same problem:
>#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGILL (0x4) at pc=0x00007cf912e5a2e3, pid=1, tid=300
#
# JRE version: OpenJDK Runtime Environment Temurin-21.0.3+9 (21.0.3+9) (build 21.0.3+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (21.0.3+9-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C [bungeecord-native-compress10317505227738964399.so+0x102e3] adler32_simd_+0x247
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /home/container/core.1)
#
# An error report file with more information is saved as:
# /home/container/hs_err_pid1.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
[error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x00007cf931d2f898]
Unfortunately also my earlier comment (I deleted because it was false) of using a hypervisor with a virtualized CPU made no difference as this from a virtual machine on the physical machine I've got.
@FlopsiBunny Are you sure you did it right? The offset into the executable is still 0x102e3
where the illegal instruction is, I'm not saying it's completely impossible but I feel like it's unlikely the offset into the executable of the instruction would be exactly the same after I completely rebuilt the binary from scratch and also added new functions.
@FlopsiBunny Are you sure you did it right? The offset into the executable is still
0x102e3
where the illegal instruction is, I'm not saying it's completely impossible but I feel like it's unlikely the offset into the executable of the instruction would be exactly the same after I completely rebuilt the binary from scratch and also added new functions.
Possible I didn't build it right? Care to send me a build I could test.
Possible I didn't build it right? Care to send me a build I could test.
https://ftp.deev.is/cpuid-BungeeCord_3.jar
JAR from my test setup last night
@FlopsiBunny I gave you the wrong jar, the native-cipher binary was one I compiled against musl on alpine for a test instead of glibc, let me fix it
Edit: fixed
Edit: updated with latest changes
@FlopsiBunny I gave you the wrong jar, the native-cipher binary was one I compiled against musl on alpine for a test instead of glibc, let me fix it
Edit: fixed
Edit: updated with latest changes
Sorry I was away from home last couple of days but have confirmed this works and is fixed.
Bungeecord version
git:BungeeCord-Bootstrap:1.21-R0.1-SNAPSHOT:b64615e:1855
Server version
No response
Client version
No response
Bungeecord plugins
LuckPerms Geyser + Floodgate ForceResourcePacks BungeeReconnect
The bug
Upon trying to connect to the proxy the entire JVM crashes and lists the problematic frame as to do with bungeecord-compression.
Log output (links)
Checking