https://bugs.freedesktop.org/show_bug.cgi?id=84836
Bug ID: 84836
Summary: VERDE lockup with Unigine Valley/Heaven if
ARB_sample_shading is enabled
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: alexander(a)tsoy.me
Created attachment 107614
--> https://bugs.freedesktop.org/attachment.cgi?id=107614&action=edit
dmesg output
Unigine Valley 1.0 and Heaven 4.0 cause VERDE GPU lockup when
ARB_sample_shading is enabled. With kernel 3.14.19 I got immediate lockup.
3.14.20 allows Valley and Heaven to run for up to 1 min. GPU fails to resume
after lockup, screen becomes corrupted and I need to reboot the system.
If I disable ARB_sample_shading (via env variable
MESA_EXTENSION_OVERRIDE=-GL_ARB_sample_shading) then VERDE GPU do not hang at
all (currently valley is running on my system for more than two hours without
lockups).
I also have BONAIRE GPU and it does not hang.
Software versions:
kernel-3.14.20
mesa-10.3.0
llvm-3.5
xf86-video-ati 7.4.0
libdrm-2.4.56
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=93762
Bug ID: 93762
Summary: Entire system stutters every so often when running
proprietary game Minecraft
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: andre35822(a)yahoo.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 121117
--> https://bugs.freedesktop.org/attachment.cgi?id=121117&action=edit
dmesg output when freezing occurs
I have noticed that it occurs every once in a while, randomly, while playing
the game, mostly when I am moving around/entering new areas where chunks have
not loaded. I remember a few past mesa releases behind the game would have an
insane amount of stutter (mesa 10.5 or so) whenever new chunks would load and I
am guessing this is still the same issue just not as dramatic. I have no clue
what info to provide you guys except to give you a dmesg output immediately
after the stutter occurs.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76382
Priority: medium
Bug ID: 76382
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Mesa Gallium egllog _eglLog
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: f1r31c3r(a)gmail.com
Hardware: All
Status: NEW
Version: 9.0
Component: Drivers/Gallium/i915g
Product: Mesa
Hi all.
Sorry in advance for any spelling blurb as i am using match sticks to hold me
eyes open.
I found a bug in the mesa, particularly related to the include files used in
src/gallium/x11
files that contain the include egllog.h that define _elLog cant find the it.
Not sure if the environment variable set for the source code under the gallium
directory is not set right.
Put simply even though the include is specified in the source file it does not
actually include it and hence the compile fails due to "undefined reference
_eglLog"
Seems that it only ever fails to compile when gallium has been enabled. egl
enabled with gles1 and 2 is fine but enable gallium and the compile error
occurs.
Hope it helps.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=93050
Bug ID: 93050
Summary: Amdgpu, Tonga "IO_PAGE_FAULT" and "[amdgpu]] *ERROR*
amdgpu: ring 0 test failed" result in Kernel Panic
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: jahnkohl(a)web.de
Created attachment 120000
--> https://bugs.freedesktop.org/attachment.cgi?id=120000&action=edit
Logfile
Switched from catalyst to amdgpu, Kernel 4.2 and Kernel 4.3 with powerplay
fixes crash, wenn modesetting is enabled (which just has to be, to get
everything working..)
When booting without modesetting no Kernel Panic occurs, but just nothing else
works really good...
I'm using Archlinux with mesa/llvm etc build from git.
Kernel 4.2 is Archlinux vanilla kernel, 4.3 is build from
http://cgit.freedesktop.org/~agd5f/linux/?h=amdgpu-powerplay
Log files are attached.I've tried with disabled/enabled Iommu, it think this
Log is with disabled Iommu.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=92729
Bug ID: 92729
Summary: VDPAU: Maybe support H264_CONSTRAINED_BASELINE
Product: Mesa
Version: 11.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: andreaskem(a)web.de
QA Contact: dri-devel(a)lists.freedesktop.org
Hi,
I am not sure if this is the proper place to report this, so feel free to send
me somewhere else and I apologize in advance.
I am on the Mesa 11.0.4 r600 driver with the following device:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Wrestler [Radeon HD 7340]
and Xorg 1.17.3. (Arch Linux with testing repository enabled, everything
up-to-date).
vdpauinfo reports (see attachment) that the H.264 profiles H264_BASELINE,
H264_MAIN, and H264_HIGH are supported for VDPAU hardware acceleration.
However, H264_CONSTRAINED_BASELINE is marked "not supported". Now, if the
Wikipedia article about H.264 profiles is to be believed [1], the constrained
profile only needs a "subset of features that are in common between the
Baseline, Main, and High Profiles." Consequently, I would expect
H264_CONSTRAINED_BASELINE to be supported, as well.
See also the bug report I filed for mpv a few weeks ago [2].
Moreover, H264_PROGRESSIVE_HIGH and H264_CONSTRAINED_HIGH seem to be "Similar
to the High profile, but without support of field coding features." and
"Similar to the Progressive High profile, but without support of B
(bi-predictive) slices." respectively. However, vdpauinfo reports "not
supported" for both.
As I am writing this, I also notice that VC1_ADVANCED is supported, but
VC1_MAIN and VC1_SIMPLE are not. Reading [3], I would expect the same reasoning
to apply.
Is there something I am missing?
[1] https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Profiles
[2] https://github.com/mpv-player/mpv/issues/2347
[3] https://en.wikipedia.org/wiki/VC-1#Profiles
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76241
Priority: medium
Bug ID: 76241
Assignee: dri-devel(a)lists.freedesktop.org
Summary: System killed by 'Triangle of Death'
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: farmboy0+freedesktop(a)googlemail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
The demo 'Triangle of Death' from GPU Caps Viewer run under wine will freeze
the system.
Homepage of GPU Caps Viewer is
http://www.ozone3d.net/gpu_caps_viewer/
Kernel: 3.13.6
Mesa: git
LLVM: 3.4
Wine: git
Card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde PRO [Radeon HD 7750]
--
You are receiving this mail because:
You are the assignee for the bug.