On 9/17/19 12:48 PM, Yurii Kolesnykov wrote:

Hello Lukas, 

Firstly, could you provide output of the following command (requires mesa-demos): 

`glxinfo|grep Rendering`

Or possibly glxinfo|grep rendering

I had an issue like this with KDE having huge lag problems. I checked htop and determined it was caused by applications dropping into uninterruptible sleep due to I/o wait. That in turn was caused by baloo file indexer running rampant in my huge music collection. Not sure if yours would be the same problem, but you could check htop and see if there applications that are lagging are in state D .. that would mean something is using the hard drive and they have to wait. (My apologies for top posting, on mobile) On Tue, Sep 17, 2019, 1:02 PM Yurii Kolesnykov wrote:

Correct command is `glxinfo|grep -I rendering` with *small* `i`, but mine spellchecker makes me nut.

На 17 вересня 2019 р. в 19:59:22, Genes Lists via arch-general ( arch-general@archlinux.org) написав:

...

On 9/17/19 12:48 PM, Yurii Kolesnykov wrote:

...

Hello Lukas,

Firstly, could you provide output of the following command (requires mesa-demos):

`glxinfo|grep Rendering`

Or possibly

glxinfo|grep rendering

On Thursday, 19 September 2019 11:37:34 CEST LuKaRo wrote:

[...]

...

glxinfo furthermore says:

Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) (0x1916) Version: 19.1.7 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2

So indeed the HD 520 seems to be doing all the work, with the NVIDIA Quadro idling around.

At least NVIDIA graphics cards can go bad in that they can cause temporary hangs, accompanied by log messages, indicating that the GPU is damaged. So perhaps if you were to stress-test the graphics card, or if you were to use the other card instead, you might be able to see some interesting results.

On Thursday, September 19, 2019 6:23:29 PM CEST L. Rose wrote:

On 19 September 2019 17:29:05 CEST, hw wrote:

...

At least NVIDIA graphics cards can go bad in that they can cause temporary hangs, accompanied by log messages, indicating that the GPU is damaged.

Where would I find such logs? I couldn't find anything in dmesg so far.

They were showing in /var/log/messages. I'll never understand why the invaluable feature of logging all kinds of messages was removed ... If you don't see any, it doesn't mean anything because unless do see them, you don't know. For all I know, all the software may have changed since and the message could have been removed. If there is an error message, you'd know.

...

So perhaps if you were to stress-test the graphics card, or if you were to use the other card instead, you might be able to see some interesting results.

What kind of stress test comes to your mind?

It had been noticeable when running an OpenGL program in that the program would freeze up for a second or two and then kept going as if nothing was wrong until it froze up again. I guess you could run a few games: The more it puts the GPU to work, the better, and there may be particular features of the graphics card that might trigger the problem while others don't. I don't know if there is a particular stress test available.

On Sun, 22 Sep 2019 19:32:37 +0200, Ralf Mardorf wrote:

On Sun, 22 Sep 2019 19:09:32 +0200, hw wrote:

...

On Thursday, September 19, 2019 6:23:29 PM CEST L. Rose wrote:

...

What kind of stress test comes to your mind?

It had been noticeable when running an OpenGL program in that the program would freeze up for a second or two and then kept going as if nothing was wrong until it froze up again. I guess you could run a few games: The more it puts the GPU to work, the better, and there may be particular features of the graphics card that might trigger the problem while others don't. I don't know if there is a particular stress test available.

I never used it myself, but perhaps it's helpful: https://wiki.archlinux.org/index.php/Benchmarking#GpuTest

After building gputest I run 'gputest_gui.py'. Here some tests don't run at all. However, at 1920x1080 'Julia FP32' runs nearly fluently, with a little bit of stutter, but 'Voloplosion' is completely stuttering, no flow at all and even the mouse cursor is sluggish. IOW a short 'freeze' (stuttering) not necessarily indicates a broken GPU. My GPU is probably just not powerful. $ hwinfo --memory|grep Size;hwinfo --cpu|grep Model|sort -u;hwinfo --gfxcard|grep Driver\ S;gputest_gui.py Memory Size: 7 GB + 512 MB Model: 6.60.3 "Intel(R) Celeron(R) CPU G1840 @ 2.80GHz" Driver Status: i915 is active Geeks3D GpuTest - GPU monitoring Num GPU(s): 1 - GPU0: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)