Closed ngortheone closed 2 months ago
I can rule out mysysctl.conf
- crash happens with empty sysctl.conf
It looks like update to 5.13 fixes this, so far I didn't have a single crash
It looks like update to 5.13 fixes this, so far I didn't have a single crash
Can you test if there is no regression between 5.15 and the drm-515-kmod port ? Thanks.
@evadot I've been running 5.15 for several months now and I didn't have a single crash.
Closing as it's fixed
FreeBSD 14-Current most recent main branch build. CPU Ryzen 9 5950x GPU: AMD Radeon Pro W5700 (navi10),
amdgpu
kernel module WM: Sway, wayland, DPI scaling 2 (4k screen) DRM: 5.10.163Running a slightly buggy vulkan application results in a crash and reboot. I was unable to get the stacktrace, even with the following sysctls set the the computer hangs for a second or two and then reboots.
The way to reproduce: In project https://github.com/Yatekii/imgui-wgpu-rs run
cargo run --example hello-world
(rust is needed)The crash happens on certain desktop configurations (DPI scale, window sizes, layout..)
I strongly suspect this bug on Linux results in a crash on FreeBSD. The behavior exactly matches this bug description, with DPI scaling factor set to 1 or with some window configurations the crash does not happen (or happens less deterministically). DPI scaling factor changes the amount of "visible" pixels to the applications, and in certain cases FP operations do not fail....
(but I have no hard evidence of that, it may be something else)
Please advice on further debugging steps
P.S. I haven't tested this on X (and I don't have a good setup to do so), and I am not sure if it is relevant...
Details:
Standard generic kernel with debugging enabled
my
src.conf
sysctl.conf
Packages
pciconf