search

any1 / neatvnc

A liberally licensed VNC server library with a clean interface
ISC License
118 stars 29 forks source link

Trying to build causes general protection fault (CPU instruction usage?) #31

Closed ilya-zlobintsev closed 4 years ago

ilya-zlobintsev commented 4 years ago

I'm trying to build the package with makepkg, the build itself hangs, and the whole system becomes half-unusable(only some programs launch, some running ones hang). Dmesg shows a general protection fault. Full log: https://pastebin.com/raw/F4n3L9kj

I've also tried to use a package built on a different system, and it crashes with "illegal hardware instruction".

I'm running an i5 750 on Arch Linux with the 5.6.8-zen kernel. Perhaps wayvnc tries to use some instructions my CPU doesn't support (AVX)?

any1 commented 4 years ago

See any1/wayvnc#34

any1 commented 4 years ago

Never mind that last comment. What you have is a kernel panic which seems to have been somehow triggered by makepkg or meson. Is the zen kernel perhaps compiled with a SIMD extension? A userspace program with an illegal instruction should never affect the kernel in this way.

ilya-zlobintsev commented 4 years ago

I've tried building wayvnc manually from git, it builds and works properly. The wayvnc-git AUR package builds successfully, but it still crashes with "illegal hardware instruction" when running it. Seems like the PKGBUILDs are enabling AVX?

zcat /proc/config.gz | grep SIMD output, just in case: CONFIG_CRYPTO_SIMD=m

Not sure if this should be closed as it's a packaging issue (and the non -git package predates the any1/wayvnc#34 fix)

any1 commented 4 years ago

The wayvnc-git AUR is not maintained and is in fact older than the wayvnc AUR

Edit: It seems to be up to date now.

any1 commented 4 years ago

I set the default SIMD extension to sse2 now. I hope that's old enough for everyone. :)