Summary: | Crash in Minecraft due to a swp[chan] assertion fail in src/gallium/drivers/r600/sb/sb_ir.cpp alu_packed_node::update_packed_items | ||
---|---|---|---|
Product: | Mesa | Reporter: | Romain Diss <romain.diss> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | ijc, romain.diss, vanyasmart |
Version: | 18.3 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Minecraft crash log
minecraft log with MESA_GLSL=dump ST_DEBUG=tgsi R600_DEBUG=vs,gs,ps |
Description
Romain Diss
2019-02-02 19:49:39 UTC
Should I join some more informations. Please let me know. I've faced with same problem on following configuration:
> $ glxinfo | grep Device
> Device: AMD JUNIPER (DRM 2.50.0 / 4.18.0-15-generic, LLVM 7.0.0) (0x68ba)
> $ glxinfo | grep 'OpenGL version string'
> OpenGL version string: 3.1 Mesa 18.3.3
> $ lspci | grep 'VGA.*Radeon'
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770]
> $ lspci -vv -s 01:00.0 | grep driver
> Kernel driver in use: radeon
> $ . /etc/lsb-release ; echo $DISTRIB_DESCRIPTION
> Ubuntu 18.04.2 LTS
> $ uname -a
> Linux ivanhome 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
FYI: I've tried to rebuild Mesa packages for Ubuntu 18.04 from x-swat-team ppa, but on codebase of Mesa 18.3.4 (instead of 18.3.3 used there), and even with mesa 18.3.4 this problem has not gone. Created attachment 143606 [details] minecraft log with MESA_GLSL=dump ST_DEBUG=tgsi R600_DEBUG=vs,gs,ps I'm seeing this too, so far only when opening a chest. Based on this IRC snippet/log https://people.freedesktop.org/~cbrill/dri-log/?channel=dri-devel&date=2016-04-17 I tried running it with `MESA_GLSL=dump ST_DEBUG=tgsi R600_DEBUG=vs,gs,ps` and captured the attached. ``` $ lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] ``` I'm also running Debian Sid and there does seem to be some correlation with an `dist-upgrade` I did on 3 March. ``` $ grep -iE '(upgrade|install) .*(mesa|radeon|xorg)' /var/log/dpkg.log 2019-03-03 14:28:14 upgrade libdrm-radeon1:amd64 2.4.95-1 2.4.97-1 2019-03-03 14:28:14 upgrade libdrm-radeon1:i386 2.4.95-1 2.4.97-1 2019-03-03 14:28:25 upgrade libgl1-mesa-dev:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:25 upgrade libegl1-mesa-dev:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:26 upgrade mesa-common-dev:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:44 upgrade libosmesa6:i386 18.2.6-1 18.3.4-1 2019-03-03 14:28:45 upgrade libosmesa6:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:45 upgrade libglx-mesa0:i386 18.2.6-1 18.3.4-1 2019-03-03 14:28:46 upgrade libglx-mesa0:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:46 upgrade libglapi-mesa:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:47 upgrade libglapi-mesa:i386 18.2.6-1 18.3.4-1 2019-03-03 14:28:48 upgrade mesa-vdpau-drivers:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:49 upgrade mesa-vdpau-drivers:i386 18.2.6-1 18.3.4-1 2019-03-03 14:28:53 upgrade mesa-va-drivers:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:28:53 upgrade mesa-va-drivers:i386 18.2.6-1 18.3.4-1 2019-03-03 14:29:00 upgrade libgl1-mesa-dri:i386 18.2.6-1 18.3.4-1 2019-03-03 14:29:01 upgrade libgl1-mesa-dri:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:30:19 upgrade libegl-mesa0:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:32:09 upgrade libgl1-mesa-glx:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:32:09 upgrade libgl1-mesa-glx:i386 18.2.6-1 18.3.4-1 2019-03-03 14:45:26 upgrade libegl1-mesa:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:45:38 upgrade libgles2-mesa-dev:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:48:01 upgrade libwayland-egl1-mesa:amd64 18.2.6-1 18.3.4-1 2019-03-03 14:49:05 upgrade mesa-utils:amd64 8.4.0-1 8.4.0-1+b1 2019-03-03 14:49:05 install mesa-vulkan-drivers:i386 <none> 18.3.4-1 2019-03-03 14:56:28 upgrade xserver-xorg-video-amdgpu:amd64 18.1.0-1 18.1.99+git20190207-1 2019-03-03 14:56:29 upgrade xserver-xorg-video-radeon:amd64 1:18.1.0-1 1:18.1.99+git20190207-1 ``` Problem has gone with Mesa 19.0 (I've checked on OpenSUSE Tumbleweed): > $ glxinfo | grep Device Device: AMD JUNIPER (DRM 2.50.0 / 5.0.3-1-default, LLVM 7.0.1) (0x68ba) > $ glxinfo | grep 'OpenGL version string' OpenGL version string: 3.1 Mesa 19.0.0 > $ /sbin/lspci | grep 'VGA.*Radeon' 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] > $ /sbin/lspci -vv -s 01:00.0 | grep driver Kernel driver in use: radeon > $ cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190327" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190327" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190327" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" > $ uname -a Linux ivanhome 5.0.3-1-default #1 SMP Fri Mar 22 17:30:35 UTC 2019 (2a31831) x86_64 x86_64 x86_64 GNU/Linux I've again faced with this issue on Ubuntu 18.04 with Mesa 19.1.4 from x-swat-ppa. After some digging I've found that current problem may not be related to Mesa, but may be related to JVM (like in #33175, which has similar symptoms, but different exception). So I've tried to run Minecraft on latest Oracle JRE, and it seems like the problem has gone. Also, I think that problem may be not in OpenJRE code, but in the way how OpenJRE package built, because, as I said, everything worked for me on OpenSUSE Tumbleweed / Mesa 19.0 / OpenJRE 11, while on Ubuntu 18.04 / Mesa 19.1.4 / OpenJRE 11 doesn't. No, sorry. Still happening with Oracle JRE, but more rarely. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/651. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.