Server error on CPU lacking SSSE3 instructions

[mrnoahfink]

Hello

Based on the thread I made - https://discord.com/channels/192358910387159041/1127298793818292365

After I update txAdmin to the latest version, it seems didn't fix the issue. Still looping crashing on Linux Pterodactyl

[gottfriedleibniz]

How is your server/VPS configured? With 66 0f 38 00 .. being SSE3, does /proc/cpuinfo contain sse3 under flags?

[mrnoahfink]

This is self-host under public IP address and pterodactyl Linux. I will check on that.

Only I know it is AMD process from 2008, lol.

[mrnoahfink]

Just checked, here my cpu info.

cpu_info.txt

The flags that pop up is - Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnow ext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalig sse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save

[gottfriedleibniz]

Yeah, this is a little gross. My previous message had a typo SSE3 -> SSSE3.

Your CPU is a bit dated and only supports the PNI/SSE3 bits. The server-hosting FAQ isn't particularly clear and the system requirements section in client-manual references AMD Phenom 9850, which suffers from the same issue.

A greater authority will have to speak on this.

[blattersturm]

Ah, so there's CPUs that do support POPCNT but not SSSE3, and SSSE3 is also required by some component.

This'd likely need the check on launch to be amended:

fivem/code/server/launcher/src/Main.cpp

Line 35 in 291d43c

if (!x86info.features.popcnt)

Documentation shouldn't need changing, the requirement for server binaries of 'x86-64-v2' apparently includes SSE3, SSSE3, SSE4.1 and SSE4.2 as well. It's plausible the Windows build has less painful requirements here due to compiler differences, but I don't have an archive of ancient CPUs lying around to verify this.

[gottfriedleibniz]

@RealStonerGamer you're going to have to provide a bit more information, e.g., the version of Windoze you are running (VPS configuration, etc). If you're running a processor without AVX, then XCR0 will not be reported. Without XCR0 then the cpu_features will depend on IsProcessorFeaturePresent which only recently added SSSE3 through AVX512 support (>= 20H1?)

[blattersturm]

If you're running a processor without AVX, then XCR0 will not be reported. Without XCR0 then the cpu_features will depend on IsProcessorFeaturePresent which only recently added SSSE3 through AVX512 support (>= 20H1?)

... seriously, this is an actual edge case?! It's indeed plausible enough the user here is running RS5 (Server 2019) in the VM which will not handle that state. Great, so detecting SSSE3 presence by running that check is just broken.

From an email the user sent, by the way:

I'm looking into the fact that I'm using a VM in further testing my physical Hardware on bear hardware no VM cfx servers load fine so yes it seems to be a VM issue

[blattersturm]

Fun check by the way: https://github.com/google/cpu_features/pull/220/files#diff-94a306e42066434db48f55e4330055dbf95059f5cd1157e28a43a8b3487f04aaR49

[RealStonerGamer]

If you're running a processor without AVX, then XCR0 will not be reported. Without XCR0 then the cpu_features will depend on IsProcessorFeaturePresent which only recently added SSSE3 through AVX512 support (>= 20H1?)

... seriously, this is an actual edge case?! It's indeed plausible enough the user here is running RS5 (Server 2019) in the VM which will not handle that state. Great, so detecting SSSE3 presence by running that check is just broken.

From an email the user sent, by the way:

I'm looking into the fact that I'm using a VM in further testing my physical Hardware on bear hardware no VM cfx servers load fine so yes it seems to be a VM issue

i am in deed runing windows server 2019 and i will be also checking out what you posted here

Fun check by the way: https://github.com/google/cpu_features/pull/220/files#diff-94a306e42066434db48f55e4330055dbf95059f5cd1157e28a43a8b3487f04aaR49

will just need to do some more research on the issue and the possible fix you have shown i do appreciate it and sorry again for any issue i have been ...

[gottfriedleibniz]

From an email the user sent, by the way:

I'm looking into the fact that I'm using a VM in further testing my physical Hardware on bear hardware no VM cfx servers load fine so yes it seems to be a VM issue

i am in deed runing windows server 2019 and i will be also checking out what you posted here

What operating system were you using on bare hardware? Windows Server 2019 as well or something more modern?

Fun check by the way: https://github.com/google/cpu_features/pull/220/files#diff-94a306e42066434db48f55e4330055dbf95059f5cd1157e28a43a8b3487f04aaR49

For posterity, this check was later updated (dropping the Westmere hardcode).

Edit: apologies for edits, I am half asleep at the moment.

[RealStonerGamer]

From an email the user sent, by the way:

I'm looking into the fact that I'm using a VM in further testing my physical Hardware on bear hardware no VM cfx servers load fine so yes it seems to be a VM issue

i am in deed runing windows server 2019 and i will be also checking out what you posted here

What operating system were you using on bare hardware? Windows Server 2019 as well or something more modern?

Fun check by the way: https://github.com/google/cpu_features/pull/220/files#diff-94a306e42066434db48f55e4330055dbf95059f5cd1157e28a43a8b3487f04aaR49

For posterity, this check was later updated (dropping the Westmere hardcode).

Edit: apologies for edits, I am half asleep at the moment.

I was using Windows 10 as the bare metal

[RealStonerGamer]

is running RS5 (Server 2019) in the VM which will not handle that state. Great, so detecting SSSE3

... seriously, this is an actual edge case?! It's indeed plausible enough the user here is running RS5 (Server 2019) in the VM which will not handle that state. Great, so detecting SSSE3 presence by running that check is just broken.

confirmed you can no longer use windows 2019 with xeon X5000 series CPUs with cfx servers

i updated to windows server 2022 fixes all issues and passes flags fully to the Vm used with these CPUs anyone using windows server 2019 will need to update

[RealStonerGamer]

just tested with my old system config that was messing up and now with this new check added today
adcce24
my old windows server 2019 VM i was using now loads cfx server fine with this new check seems to work with window server 2019 using xeon X5000 series cpu in VM now

i did update to server 2022 and have it al set up so not going to keep using the old config but nice to know its fixed it seems

thanks balattersturm for the hard work

[mrnoahfink]

Any update about this?

I just redownload fivem/build_proot_linux/master/ to 6594 and still nothing at this moment.

Thanks!

[blattersturm]

and still nothing at this moment

What do you mean by 'nothing'? It should properly show an error message stating your CPU is not supported.

[mrnoahfink]

I guess it is still not supported. I notice that you guys talking about Windows, This is for Linux, however seems CPU outdated.

[DaveInchy]

no flags for server.cfg to run it anyway knowing the dangers?