Mailinglist Archive: opensuse-bugs (4790 mails)

< Previous Next >
[Bug 1046962] radeonsi: 3D engines causing frequent GPU lockups
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 31 Jul 2017 12:32:40 +0000
  • Message-id: <bug-1046962-21960-x8JlJpDibL@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1046962
http://bugzilla.opensuse.org/show_bug.cgi?id=1046962#c34

--- Comment #34 from Max Staudt <mstaudt@xxxxxxxx> ---
I'm afraid my knowledge of OpenGL is not deep enough to follow you here. On the
other hand, if you have such deep insight, maybe that will help get upstream's
attention? If there's a common open source game that exhibits this problem, it
could serve as a minimal test case.

The question remains whether this is caused by a simple failure to free() some
memory, as you initially suspected, or something else. In any case, your new
comment sounds like you finally have a good reproducer, so that's great!

As for your report back in Comment 31:

The dmesg output is uneventful I'm afraid. If anything, it would be [radeon]
printing interesting messages.

I'm surprised the bash line didn't work - I suppose that's because the last
line is different? It seems like there is a summary being printed - maybe it's
enough to do the following:

watch -n 1 tail /sys/kernel/debug/dri/0/radeon_vram_mm
watch -n 1 tail /sys/kernel/debug/dri/0/radeon_gtt_mm

...and then run a game with skeletal meshes.

Can you please check whether supertuxkart exhibits this issue, too? That would
greatly simplify reproduction of the bug.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References