You are not logged in.
Hello, I've found a weird issue with glxgears and lm_sensors
Reproduction steps (WARNING: this sometimes completely locks up the computer and requires a hard reset):
You need a recentish kernel, working Xorg with 3D graphics acceleration using a dedicated GPU (this issue doesn't seem to exist on iGPUs)
Ensure you have the packages mesa-demos and lm_sensors installed
If you've never done it, you should set up lm_sensors (so that it can read sensor info from ISA adapter) by running sensors-detect as root and leaving all the prompts blank (see wiki)
Next, you need to start up glxgears without vsync:
On mesa-based drivers:
vblank_mode=0 glxgearsOn nvidia's proprietary drivers:
__GL_SYNC_TO_VBLANK=0 glxgearsLeaving glxgears running and on screen, in another terminal emulator set up constant querying of lm_sensors:
watch -n 1 sensorsTry to focus the glxgears window as fast as you can, because if this works your system will begin freezing up and you'll have to hold the escape key in order to exit glxgears when the system briefly unfreezes
This seems to work on multiple different configurations, and I can't figure out any common denominator (outside of the outlined software) between these systems
Last edited by random-nick (2020-04-26 12:29:12)
Offline
I've been getting consistent display lock-ups and freezes at least ever few days (sometimes 10 minutes) since upgrading my desktop last, and oddly did install psensor/lm_sensors around then to monitor. Mine doesn't crash reproducing your steps on my xps15 with igpu only, but I suspect there are issues in xorg and/or kernel issues of late, which I'm using 5.5.9-arch1-2 currently. This is with kde, cinnamon, or mate - no more than 2 days uptime.
Last time I ssh'd in via another device and xorg was pegging the cpu as my desktop froze, I couldn't restart sddm via systemctl (hangs) and couldn't kill x in any other way, even reboot just disconnected me and remained hung. Nothing in logs, journalctl, or other as to an issue, just hung. I'm either going to try upgrading or downgrading soon as this is maddening.
Offline
Things seem to work fine here for me, but I'm currently trying the v5.7-rc2 Linux kernel as an experiment, not using the normal Arch kernel.
"Works fine here for me" means that I'm currently having that "vblank_mode=0 glxgears" running and in another terminal "watch -n1 sensors", and nothing bad seems to be happening. I can switch workspaces and focus different windows, can use the browser fine, can open programs. I can move windows around without stutter and the browser scrolls with "smooth scrolling" fine and without stutter. There's nothing that looks suspicious and like a problem here.
Here's the details about the setup that are perhaps important:
* Linux 5.7-rc2 mainline kernel
* AMD RX480 graphics card
* xfwm4 windows manager
* picom-git package from the AUR as the compositor, started with "--experimental-backends" and set to use glx backend plus vsync enabled
* 144Hz refresh rate on monitor
* Firefox with its "webrender" feature enabled
The "sensors" tool does find a lot of hardware on this computer here:
jc42-i2c-7-1b
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +36.2°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: N/A
amdgpu-pci-0d00
Adapter: PCI adapter
vddgfx: 987.00 mV
fan1: 4915 RPM (min = 0 RPM, max = 3200 RPM)
edge: +47.0°C (crit = +94.0°C, hyst = -273.1°C)
power1: 65.02 W (cap = 142.00 W)
nct6779-isa-0290
Adapter: ISA adapter
VRM VCore: 1.06 V (min = +0.54 V, max = +1.46 V)
VPPM: 2.54 V (min = +2.37 V, max = +2.62 V)
AVCC: 3.33 V (min = +2.98 V, max = +3.63 V)
3VCC: 3.33 V (min = +2.98 V, max = +3.63 V)
+12V: 12.04 V (min = +11.40 V, max = +12.62 V)
VDDCR_SOC (Data Fabric): 984.00 mV (min = +0.80 V, max = +1.20 V)
DRAM (VDDIO): 1.42 V (min = +1.10 V, max = +1.50 V)
3VSB: 3.46 V (min = +2.98 V, max = +3.63 V)
VBat: 3.28 V (min = +2.70 V, max = +3.63 V)
Null: 0.00 V (min = +0.00 V, max = +0.00 V)
Mem_VTT (VDDIO/2): 656.00 mV (min = +0.60 V, max = +0.75 V)
Chipset 1.05V: 1.08 V (min = +0.90 V, max = +1.20 V)
+5V: 5.02 V (min = +4.75 V, max = +5.26 V)
VDDP: 928.00 mV (min = +0.91 V, max = +1.07 V)
1.8V+: 1.84 V (min = +1.77 V, max = +1.84 V) ALARM
Chassis Fan 3 Speed: 771 RPM (min = 400 RPM)
CPU Fan 1 Speed: 542 RPM (min = 400 RPM)
CPU Fan 2 Speed: 579 RPM (min = 400 RPM)
Chassis Fan 1 Speed: 589 RPM (min = 400 RPM)
Chassis Fan 2 Speed: 654 RPM (min = 400 RPM)
Motherboard: +34.0°C (high = +60.0°C, hyst = +55.0°C) sensor = thermistor
CPU MB: +44.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
Auxiliary: +4.0°C sensor = thermistor
VRM: +45.0°C sensor = thermistor
AUXTIN2: +21.0°C sensor = thermistor
CPU (PECI): -28.0°C sensor = thermistor
CPU tCTL (offset included): +64.0°C
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
beep_enable: disabled
jc42-i2c-7-1a
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +38.0°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)
k10temp-pci-00c3
Adapter: PCI adapter
Vcore: 1.37 V
Vsoc: 975.00 mV
Tctl: +62.1°C
Tdie: +52.1°C
Icore: 48.00 A
Isoc: 10.00 A The "vblank_mode=0" seems to have worked as well, glxgears is printing fps numbers like this while I'm typing this text here:
72043 frames in 5.0 seconds = 14408.508 FPS
75500 frames in 5.0 seconds = 15099.942 FPS
76206 frames in 5.0 seconds = 15241.158 FPS
81942 frames in 5.0 seconds = 16388.324 FPS
74530 frames in 5.0 seconds = 14905.863 FPSOffline
I've found out that this issue does not actually exist. Every computer I've "reproduced" this on actually has its own issue which is triggered by theses steps, and only one of those seems to be related to lm_sensors (that computer seems to be stuttering when sensors get queried frequently).
Last edited by random-nick (2020-04-26 12:28:46)
Offline