https://bugs.freedesktop.org/show_bug.cgi?id=98492
Bug ID: 98492
Summary: X-Plane 10 Core Dumping when using Real-Weather or any
clouds
Product: Mesa
Version: git
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: amarildo-geral(a)autistici.org
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 127609
--> https://bugs.freedesktop.org/attachment.cgi?id=127609&action=edit
journalctl
X-Plane crashes when using Real_weather or when setting up any kinds of clouds
for the Sim.
As per journalctl would suggest, libpthreads isn't the cause. I've isntalled it
here on Arch and the sim still crashes.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=96790
Bug ID: 96790
Summary: frame stuttering in ut2004
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: network723(a)rkmail.ru
QA Contact: dri-devel(a)lists.freedesktop.org
My hardware: HD7950 & Phenom II x6 1090
The problem: intensive frame stuttering and frame rate drops below 30 fps while
playing UT2004. Drops usually happen when there is intensive shooting, but it
may also happen on maps with complex geometry.
Also, in-game fps counter shows 'avg fps' about 90-200, with rare jumps to
300-400 fps, even with vblank_mode=0 set. 64 bit version of the game on Windows
shows stable 300+ fps with OpenGL renderer.
I wonder if this may be related to AMD CPU, since various test results on
Phoronix show much greater performance (up to 5 times) with Intel CPU and same
GPU.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101834
Bug ID: 101834
Summary: WebGL shaders cause system freeze
Product: Mesa
Version: 17.1
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: grmat(a)sub.red
QA Contact: dri-devel(a)lists.freedesktop.org
Hardware:
Radeon R9 290X (Hawaii)
Installed components:
Linux 4.11.9
Libdrm 2.4.81
Mesa 17.1.4
Running Arch Linux, using both radeon and amdgpu drm drivers, Chromium and
Firefox the system can freeze when running WebGL shaders. I've experienced this
on shadertoy.com before and now have a reproducible example:
https://threejs.org/examples/webgl_gpgpu_protoplanet.html
Sound keeps on playing and I can move the cursor but not interact with the
system any more. If I can provide any logs to help, please ask.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99994
Bug ID: 99994
Summary: Unreal Tournament 2016 segfaults with sisched
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: ernstp(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
The free to play Unreal Tournament under development segfaults with
R600_DEBUG=sisched.
Fully playable, with rendering issues, without it.
It segfaults very early, before the first graphics.
FIJI Fury card.
LLVM: 5.0~svn295460-0~y~padoka0
Mesa: 17.1~git170226151200.5b5ffb7~y~padoka0
(gdb) bt
#0 llvm::SIInstrInfo::isLowLatencyInstruction(llvm::MachineInstr const&) const
() at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/include/llvm/CodeGen/MachineInstr.h:273
warning: (Internal error: pc 0x7fffdc4858cf in read in psymtab, but not in
symtab.)
warning: (Internal error: pc 0x7fffdc4858cf in read in psymtab, but not in
symtab.)
#1 0x00007fffdc4858d0 in llvm::SIScheduleDAGMI::moveLowLatencies() () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/AMDGPU/SIMachineScheduler.cpp:1727
warning: (Internal error: pc 0x7fffdc48fc85 in read in psymtab, but not in
symtab.)
warning: (Internal error: pc 0x7fffdc48fc85 in read in psymtab, but not in
symtab.)
#2 0x00007fffdc48fc86 in llvm::SIScheduleDAGMI::schedule() () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/AMDGPU/SIMachineScheduler.cpp:1871
#3 0x00007fffdb5f50ef in (anonymous
namespace)::MachineSchedulerBase::scheduleRegions(llvm::ScheduleDAGInstrs&,
bool) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/CodeGen/MachineScheduler.cpp:480
#4 0x00007fffdb5fe789 in (anonymous
namespace)::MachineScheduler::runOnMachineFunction(llvm::MachineFunction&) ()
at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/CodeGen/MachineScheduler.cpp:344
#5 0x00007fffdb5a86a1 in
llvm::MachineFunctionPass::runOnFunction(llvm::Function&) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/CodeGen/MachineFunctionPass.cpp:62
#6 0x00007fffdb430b22 in llvm::FPPassManager::runOnFunction(llvm::Function&)
() at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/IR/LegacyPassManager.cpp:1513
#7 0x00007fffdb430bc3 in llvm::FPPassManager::runOnModule(llvm::Module&) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/IR/LegacyPassManager.cpp:1534
#8 0x00007fffdb431567 in llvm::legacy::PassManagerImpl::run(llvm::Module&) ()
at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/IR/LegacyPassManager.cpp:1590
#9 0x00007fffdc2b79c8 in LLVMTargetMachineEmit(LLVMOpaqueTargetMachine*,
LLVMOpaqueModule*, llvm::raw_pwrite_stream&, LLVMCodeGenFileType, char**) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/TargetMachineC.cpp:204
#10 0x00007fffdc2b7bc9 in LLVMTargetMachineEmitToMemoryBuffer () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/TargetMachineC.cpp:228
#11 0x00007fffdee3d8d5 in si_llvm_compile (M=0x7fffbc013db0,
binary=0x7fffbc009460, tm=0x75e140, debug=0x0) at
../../../../../../src/gallium/drivers/radeonsi/si_shader_tgsi_setup.c:224
#12 0x00007fffdee38528 in si_compile_llvm (sscreen=<optimized out>,
binary=0x7fffbc009460, conf=0x7fffbc0094c0, tm=0x75e140, mod=0x7fffbc013db0,
debug=0x0, processor=1, name=0x7fffdf001231 "TGSI shader")
at ../../../../../../src/gallium/drivers/radeonsi/si_shader.c:6159
#13 0x00007fffdee39389 in si_compile_tgsi_shader (sscreen=0x757480,
tm=0x75e140, shader=0x7fffbc009330, is_monolithic=<optimized out>, debug=0x0)
at ../../../../../../src/gallium/drivers/radeonsi/si_shader.c:7366
#14 0x00007fffdee4d39c in si_init_shader_selector_async (job=0x7fffa8b84d10,
thread_index=1) at
../../../../../../src/gallium/drivers/radeonsi/si_state_shaders.c:1416
#15 0x00007fffdeb77754 in util_queue_thread_func (input=<optimized out>) at
../../../../../src/gallium/auxiliary/util/u_queue.c:175
#16 0x00007fffdeb773d8 in impl_thrd_routine (p=<optimized out>) at
../../../../../include/c11/threads_posix.h:87
#17 0x00007ffff7bc16ca in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#18 0x00007ffff0f240af in clone () from /lib/x86_64-linux-gnu/libc.so.6
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101145
Bug ID: 101145
Summary: Wine game needs GLSL override for fullscreen
Product: Mesa
Version: git
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: wyrex(a)openmailbox.org
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 131437
--> https://bugs.freedesktop.org/attachment.cgi?id=131437&action=edit
bug
I have wine game that corrupts monitor after entering fullscreen. Windowed uses
GDI but fullscreen is DirectX. Overriding GL versions help as workaround.
MESA_GLSL_VERSION_OVERRIDE=110 (MUST be 110)
MESA_GL_VERSION_OVERRIDE=3.0 (must be <= 3.0)
This happens with softpipe and llvmpipe too and without override they show
black screen and output:
fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000
(using GL_RENDERER "Gallium 0.4 on softpipe").
Game enters fullscreen with something like IDirectDraw2::SetCooperativeLevel ->
IDirectDraw2::SetVideoMode.
Original bug: bugs.winehq.org/show_bug.cgi?id=41283.
Graphics: Card: Advanced Micro Devices [AMD/ATI] Tonga PRO [Radeon R9 285/380]
Display Server: X.Org 1.19.3 driver: amdgpu Resolution:
1920x1080(a)60.00hz, 1920x1080(a)60.00hz
GLX Renderer: Gallium 0.4 on AMD TONGA (DRM 3.15.0 /
4.12.0-rc1-g2ea659a9ef48, LLVM 5.0.0)
GLX Version: 3.0 Mesa 17.2.0-devel (git-1586768e74)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=96935
Bug ID: 96935
Summary: Trying to Mine Ethereum crashes the whole system.
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: lvella(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Related to bug #96934, if I try to use a fork of the original mining software,
hosted in https://github.com/Genoil/cpp-ethereum (my fork patching it to
compile in libclc: https://github.com/lvella/cpp-ethereum) my computer freezes
and requires a hard reboot in order to recover. One of the three times I tried,
what seemed to be an endless stream of kernel's error log was printed on the
screen, but it did not survive in /var/log/kern.log after the reboot.
To try it yourself, download, compile and run:
$ ethminer -G -F
mine.weipool.org:5555/0x7079a42c78d28ce9216c290d1bbc61e7b12d54a3/0.5
Note that this is a different OpenCL code than the one in #96934. The code used
there is from the official Ethereum repository. This one is from a fork, that
seems to be the most used version of the mining software.
Again, that command will mine on the public pool WeiPool and direct the
earnings to my address 0x7079a42c78d28ce9216c290d1bbc61e7b12d54a3. If you want
to try and don't risk sending me any money, change that number to you Ethereum
or Bitcoin address. Instructions in mine.weipool.org.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=96934
Bug ID: 96934
Summary: Mining Ethereum orders of magnitude slower than on
proprietary drivers.
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: lvella(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
By enabling a libclc extension on ethminer OpenCL code, I managed to run it
using Ubuntu 16.04 and Oibaf's PPA. The code has been merged into
https://github.com/ethereum/libethereum and you can benchmark it for yourself.
Using a Radeon r9 280X, I ran the following command:
$ ethminer -G -F
mine.weipool.org:5555/0x7079a42c78d28ce9216c290d1bbc61e7b12d54a3/0.5
and got in output, among other things:
...
miner 01:09:13.001|ethminer Mining on PoWhash #20c1b379… : 556569 H/s =
524288 hashes / 0.942 s
miner 01:09:13.875|ethminer Mining on PoWhash #20c1b379… : 599871 H/s =
524288 hashes / 0.874 s
miner 01:09:14.758|ethminer Mining on PoWhash #20c1b379… : 296878 H/s =
262144 hashes / 0.883 s
miner 01:09:15.624|ethminer Mining on PoWhash #20c1b379… : 606113 H/s =
524288 hashes / 0.865 s
miner 01:09:16.480|ethminer Mining on PoWhash #20c1b379… : 612485 H/s =
524288 hashes / 0.856 s
miner 01:09:17.353|ethminer Mining on PoWhash #20c1b379… : 601247 H/s =
524288 hashes / 0.872 s
miner 01:09:18.210|ethminer Mining on PoWhash #20c1b379… : 611771 H/s =
524288 hashes / 0.857 s
...
This reported rash rate is about 3% of the rate my GPU is supposed to deliver
(it should be in the order of 22 MH/s).
By the way, that command will mine on the public pool WeiPool and direct the
earnings to my address 0x7079a42c78d28ce9216c290d1bbc61e7b12d54a3. If you want
to try and don't send me money, change that number to you Ethereum or Bitcoin
address. Instructions in mine.weipool.org.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70910
Priority: medium
Bug ID: 70910
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi&r600g] wrong colors on radeonsi screen in
some places when radeonsi and r600g gpus are installed
Severity: minor
Classification: Unclassified
OS: All
Reporter: ptpzz(a)yandex.ru
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 88176
--> https://bugs.freedesktop.org/attachment.cgi?id=88176&action=edit
screenshot
Looks like in some cases there is RGB <-> BGR mismatch, so that red icons
become blue, etc. On the attached screenshot xchat icon on the xfce panel is
rendered normally - red/yellow, but the same icon on a tooltip below is blue.
Similar issues can be seen in some other places - e.g. window decorations,
icons on buttons in dialog windows, but in many other cases the colors are
correct - e.g. with glxgears.
AFAICS there is no such problem on r600g screen. Also, without r600g card there
is no such problem on radeonsi screen as well, it happens only when two cards
are installed.
r600g uses EXA in my config, but IIRC it was the same when both drivers use
glamor.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=66940
Priority: medium
Bug ID: 66940
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Mobility Radeon HD 5650 doesn't resume from suspend on
kernel 3.11 (linus and drm_next)
Severity: normal
Classification: Unclassified
OS: All
Reporter: mail(a)3v1n0.net
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 82459
--> https://bugs.freedesktop.org/attachment.cgi?id=82459&action=edit
dmesg
I've tried running linux 3.11 from both linus and drm_next branches, but when
using the radeon drivers it's impossible to resume from suspension.
It's quite sure that the problem is in radeon module, because unloading it (and
switching to my intel card with vgaswitcheroo) works fine.
Also, enabling the pm_trace sys-node it highlights that the radeon device
caused the freeze:
from dmesg:
[ 1.286810] Magic number: 0:660:725
[ 1.286815] hash matches
/home/marco/Dev/debs/linux/drivers/base/power/main.c:575
[ 1.286829] block loop5: hash matches
[ 1.286867] pci 0000:01:00.0: hash matches
^ This is the PCI id of my radeon card
cat /sys/power/pm_trace_dev_match:
block
radeon
This is a regression, since linux 3.10 works well.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=93216
Bug ID: 93216
Summary: Artifacts with DCC when render target also texture
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: axel.davy(a)ens.fr
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 120280
--> https://bugs.freedesktop.org/attachment.cgi?id=120280&action=edit
Before a buggy draw call
I noticed a few games had some strange artifacts on my tonga that I had not on
verde. Those artifacts are usually along lines.
These artifacts disappear with R600_DEBUG=nodcc.
I managed to determine the bug appears when the render target is also used as
input texture.
Attached is the render target content before and after such draw call. The draw
call draws two triangles. We can see the artifacts are along the border region
of the top right triangle with the bottom left triangle.
My guess is that it is some flush issue. That the bottom left triangle is drawn
first, the cache content of the texture cache updated, and the artifacts are at
locations where the dcc data was updated.
--
You are receiving this mail because:
You are the assignee for the bug.