https://bugs.freedesktop.org/show_bug.cgi?id=88780
Bug ID: 88780
Summary: Several Unity3D-based games render with "foggy blueish
overlay"
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: kai(…
[View More]a)dev.carbon-project.org
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 112787
--> https://bugs.freedesktop.org/attachment.cgi?id=112787&action=edit
Blue overlay with Dreamfall Chapters in the lab scene
With the stack detailed below (AFAICT this is *NOT* a regression, because I
seem to remember having these hazy blue scenes with older versions of Mesa as
well) several Unity3D-based games (e.g. Jagged Alliance: Flashback or Dreamfall
Chapters) render either entirely or only some scenes as if there was some fog
overlay with a blue hue.
For Dreamfall Chapters (from which the attached screenshot originates), it's
only for some scenes, sometimes even dependant on the camera angle. For
example, in the Queenie scene only some camera angles exhibit this problem,
while in the lab scene, you have it constantly. With Dreamfall Chapters this
bug can be seen mostly indoors.
Games like Jagged Alliance render all 3D scenes with this blue hue overlay.
This is, every sector you go into shows this problem.
My current stack (Debian testing as a base):
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Mesa: Git:master/d2811c29da
libdrm: Git:master/libdrm-2.4.59
LLVM: SVN:trunk/r226934 (3.7 devel)
X.Org: Git:master/6672606420
Linux: Git:<git://people.freedesktop.org/~airlied/linux>:drm-fixes/67cf2d3912
Firmware: <http://people.freedesktop.org/~agd5f/radeon_ucode/>
> 9e05820da42549ce9c89d147cf1f8e19 hawaii_ce.bin
> c8bab593090fc54f239c8d7596c8d846 hawaii_mc.bin
> 3618dbb955d8a84970e262bb2e6d2a16 hawaii_me.bin
> c000b0fc9ff6582145f66504b0ec9597 hawaii_mec.bin
> 0643ad24b3beff2214cce533e094c1b7 hawaii_pfp.bin
> ba6054b7d78184a74602fd81607e1386 hawaii_rlc.bin
> 11288f635737331b69de9ee82fe04898 hawaii_sdma.bin
> 284429675a5560e0fad42aa982965fc2 hawaii_smc.bin
libclc: Git:master/d73f33b736
DDX: Git:master/c9f8f642fd
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=86357
Bug ID: 86357
Summary: [RadeonSI] GPU lockup with mesa 10.3.3 / kernel 3.17.2
Product: Mesa
Version: 10.3
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: madcatx(a)atlas.cz
Created …
[View More]attachment 109569
--> https://bugs.freedesktop.org/attachment.cgi?id=109569&action=edit
journalctl crash info, contains both dmesg and Xorg logs
After a recent update of my Fedora 21 box I've experienced this crash twice.
The entire desktop except for mouse freezes and I cannot even VT switch to
console. If the keypress gets registered I end up with a powered down display
and a switch back to X results in a completely corrupted screen. If I don't try
a VT switch I can still move the mouse but other than that the machine appears
dead. It eventually stops responding to ping and the only way out is a hard
reboot.
I have been using this machine for quite a while and I haven't experienced this
before until yesterday. I checked the yum logs but there doesn't seem to be
anything directly related to the graphics except maybe for this:
Updated xkeyboard-config-2.13-2.fc21.noarch
@updates-testing
Update 2.13-3.fc21.noarch
@updates-testing
Updated xorg-x11-font-utils-1:7.5-23.fc21.x86_64
@updates-testing
Update 1:7.5-25.fc21.x86_64
@updates-testing
Updated xorg-x11-fonts-Type1-7.5-11.fc21.noarch
@updates-testing
Update 7.5-14.fc21.noarch
@updates-testing
Updated xorg-x11-server-utils-7.7-9.fc21.x86_64
@updates-testing
Update 7.7-10.fc21.x86_64
@updates-testing
Updated xorg-x11-xkb-utils-7.7-10.fc21.x86_64
@fedora
Relevant packages installed:
xorg-x11-drv-ati - 7.5.0-1.fc21
xorg-x11-server-Xorg.x86_64 - 1.16.1-1.fc21
kernel.x86_64 - 3.17.2-300.fc21
Custom-built mesa 10.3.3 with "Fix v5" from "BUG 60879" applied
My card is a 7730 LE, PID:VID 1002:aab0
X and kernel apparently caught and logged the problem, relevant journalctl
output is attached. It usually takes a few hours for this to happen, the only
thing the two crashes I've had so far have in common is a Flash video playing
in the background when the system froze.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=89256
Bug ID: 89256
Summary: [radeonsi][CSGO] many rendering artifacts and more
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: sylvain.bertrand(a)gmail.com
…
[View More] QA Contact: dri-devel(a)lists.freedesktop.org
Got my hands on counter-strike Global Offensive.
I run an up-to-date fedora rawhide on x86_64 (3.20 kernel and mesa 10.5.0).
I get a lot of rendering artifacts, GPU lock ups (rare, on ring 0 and 5), VM
read faults from the TC block (texture cache I guess) for some VMs...
The video settings are set to the minimum (in a 1920x1080 window)
My GPU is a R9 280X (TAHITI XT).
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=80922
Priority: medium
Bug ID: 80922
Assignee: dri-devel(a)lists.freedesktop.org
Summary: XCOM :Enemy Unknown will crash and kill the output
after some time.
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: half-shot(a)molrams.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
…
[View More]Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 102280
--> https://bugs.freedesktop.org/attachment.cgi?id=102280&action=edit
glxinfo
Wish I could describe it better but there is no better words. The game will
lock up the card and the monitor output will go blank, although once I got
lucky and it crashed to the terminal spewing errors about radeon. Due to the
fact that the system crashes the only. This crash usually happens during a
gameplay sequence and has not happened in a menu as of yet. The crash also will
usually recover the first time after loosing visual output for 10 seconds but
then will cut out a second (or rarely a third) and not return to the game.
Due to it crashing randomly (no specific scene causing it) and always requiring
about a hour of play, would it make sense to be a memory issue?
It did not occur to me that I would need Dmesg output, if its needed then
remind me and I will reproduce another crash with the log file.
I also have a apitrace, but it totals 23GB and I do not know which bit would
need trimming.
System Specs:
AMD PhenomII X6 T55
AMD RadeonHD 7950
Mesa 10.3.0-devel (git-370184e)
LLVM 3.5.0 (svn)
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=85207
Bug ID: 85207
Summary: agd5f drm-next-3.19-wip + Unreal Elemental sometimes =
list_add corruption/hung task
Product: DRI
Version: XOrg CVS
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: adf.lists(…
[View More]a)gmail.com
Created attachment 108075
--> https://bugs.freedesktop.org/attachment.cgi?id=108075&action=edit
dmesg when Unreal Elemental hangs on start
R9270X Sometime running unreal elemental demo it hangs at startup with errors
in dmesg attached.
This doesn't always happen.
Mesa is currently on winsys/radeon: Use a single buffer cache manager again,
previously produced with slightly older.
Haven't seen on drm-next-3.18-wip (but really need to test more with current
mesa)
Possibly unrelated, but new for drm-next-3.19-wip I get below when running
Unigine Valley - it runs OK.
Oct 17 11:15:35 ph4 kernel: radeon 0000:01:00.0: GPU fault detected: 146
0x0af03504
Oct 17 11:15:35 ph4 kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00010E57
Oct 17 11:15:35 ph4 kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x10035004
Oct 17 11:15:35 ph4 kernel: VM fault (0x04, vmid 8) at page 69207, read from
VGT (53)
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=88211
Bug ID: 88211
Summary: [drm:radeon_gem_va_update_vm [radeon]] *ERROR*
Couldn't update BO_VA (-512) with linux-git
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.…
[View More]org
Reporter: commiethebeastie(a)gmail.com
Created attachment 111968
--> https://bugs.freedesktop.org/attachment.cgi?id=111968&action=edit
dmesg
Radeon R9 280X
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=73792
Priority: medium
Bug ID: 73792
Assignee: dri-devel(a)lists.freedesktop.org
Summary: UVD usage with HD makes X11 quite unstable on Samsung
ATIV Book Lite 9 (A4-1450 CPU, KABINI graphics))
Severity: normal
Classification: Unclassified
OS: All
Reporter: rvdb(a)cryptolab.net
Hardware: Other
Status: NEW
Version: …
[View More]git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 92387
--> https://bugs.freedesktop.org/attachment.cgi?id=92387&action=edit
Dmesg output
I have a Smasung ATIV Bool Lite 9 notebook on which I installed a
Slackware-current system which works roughly well except suspend and UVD
playback.
About the later, I run a Kernel 3.12.8 with less-than-a-week-ago git pulls of
libdrm, glamor, mesa, mesa-glu and xfree-video-ati.
Desktop graphic and compositing work well without glitch and no specific lag.
I use libvdpau 0.7 and less-than-a-week-ago git pulls of ffmpeg, x264 and vlc.
vlc is configured to use VDPAU and this the UVD chip in the processor.
When running SD h264 videos, everything works fine and the CPU usage is low
(less than 75% of total W11/KWin/vlc on a GHz core, that's fine with me).
I get issues when trying to run HD h264 videos. The CPU usage is still fine,
the video starts but after some time, the video hangs, the system becomes
unresponsive then the screen turns black, as displaying a black image, it's a
bit less black then when the screen is turned of.
At this point, either I need to reboot or at some point, the screen seems to
turn of, then light up again and resume where I was, though sometimes the video
remains black and I have to move the VLC slider to get some images. Then the
film can play several seconds then the whole pattern occurs again. And so on
until the system does not resume and I must reboot.
I've attached dmesg, syslog, glxinfo et vdpauinfo outputs.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=88458
--- Comment #3 from Marek Olšák <maraeo(a)gmail.com> ---
Does this issue will occur on current Mesa git?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=82886
Priority: medium
Bug ID: 82886
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [RadeonSI]GPU Lockup with Linux 3.16 & Mesa Git
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: mmstickman(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
…
[View More] Product: Mesa
My Radeon HD 7950 GPU locks up and/or Xorg completely crashes whenever the
system is graphics card is stressed slightly sometimes (even so much as
displaying a web page) -- forcing me to have to reboot the system. I've also
been able to trigger it simply by running a game like Tesseract, where it will
completely crash Xorg on the main menu.
[104725.380514] radeon 0000:01:00.0: ring 0 stalled for more than 10033msec
[104725.380524] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000085f665
last fence id 0x000000000085f65a on ring 0)
[104725.921526] radeon 0000:01:00.0: Saved 957 dwords of commands on ring 0.
[104725.921574] radeon 0000:01:00.0: GPU softreset: 0x00000068
[104725.921576] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028
[104725.921578] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
[104725.921580] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
[104725.921582] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[104725.921617] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[104725.921619] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[104725.921621] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000
[104725.921623] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002
[104725.921625] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243
[104725.921626] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[104725.921628] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44E84246
[104725.921630] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[104725.921632] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[104726.446215] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
[104726.446269] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000140
[104726.447426] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028
[104726.447428] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
[104726.447430] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
[104726.447432] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0
[104726.447467] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[104726.447469] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[104726.447470] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[104726.447472] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[104726.447474] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
[104726.447476] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[104726.447478] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[104726.447562] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[104726.496373] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[104726.496376] [drm] PCIE gen 2 link speeds already enabled
[104726.499844] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
[104726.499980] radeon 0000:01:00.0: WB enabled
[104726.499983] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x00000000c0000c00 and cpu addr 0xffff880420106c00
[104726.499985] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
0x00000000c0000c04 and cpu addr 0xffff880420106c04
[104726.499987] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
0x00000000c0000c08 and cpu addr 0xffff880420106c08
[104726.499989] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x00000000c0000c0c and cpu addr 0xffff880420106c0c
[104726.499990] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
0x00000000c0000c10 and cpu addr 0xffff880420106c10
[104726.500376] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffc90011cb5a18
[104726.672097] [drm] ring test on 0 succeeded in 1 usecs
[104726.672103] [drm] ring test on 1 succeeded in 1 usecs
[104726.672107] [drm] ring test on 2 succeeded in 1 usecs
[104726.672167] [drm] ring test on 3 succeeded in 2 usecs
[104726.672174] [drm] ring test on 4 succeeded in 1 usecs
[104726.869612] [drm] ring test on 5 succeeded in 2 usecs
[104726.869617] [drm] UVD initialized successfully.
[104736.885653] radeon 0000:01:00.0: ring 0 stalled for more than 10000msec
[104736.885663] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000085f66b
last fence id 0x000000000085f65a on ring 0)
[104736.885689] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[104736.885696] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
[104736.885700] radeon 0000:01:00.0: ib ring test failed (-35).
[104737.072553] radeon 0000:01:00.0: ring 0 stalled for more than 10186msec
[104737.072563] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000085f665
last fence id 0x000000000085f65a on ring 0)
[104737.395007] radeon 0000:01:00.0: GPU softreset: 0x00000048
[104737.395010] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028
[104737.395012] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
[104737.395014] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
[104737.395016] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[104737.395051] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[104737.395053] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[104737.395055] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000
[104737.395057] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00400002
[104737.395059] radeon 0000:01:00.0: R_008680_CP_STAT = 0x84010243
[104737.395061] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[104737.395062] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[104737.395065] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[104737.395067] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[104737.895759] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
[104737.895829] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[104737.896987] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028
[104737.896989] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
[104737.896991] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
[104737.896993] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
[104737.897027] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[104737.897067] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[104737.897071] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[104737.897073] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[104737.897075] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
[104737.897078] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[104737.897080] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[104737.897164] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[104737.914092] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[104737.914095] [drm] PCIE gen 2 link speeds already enabled
[104737.917563] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
[104737.917737] radeon 0000:01:00.0: WB enabled
[104737.917739] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x00000000c0000c00 and cpu addr 0xffff880420106c00
[104737.917741] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
0x00000000c0000c04 and cpu addr 0xffff880420106c04
[104737.917743] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
0x00000000c0000c08 and cpu addr 0xffff880420106c08
[104737.917745] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x00000000c0000c0c and cpu addr 0xffff880420106c0c
[104737.917747] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
0x00000000c0000c10 and cpu addr 0xffff880420106c10
[104737.918131] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffc90011cb5a18
[104738.088583] [drm] ring test on 0 succeeded in 1 usecs
[104738.088588] [drm] ring test on 1 succeeded in 1 usecs
[104738.088592] [drm] ring test on 2 succeeded in 1 usecs
[104738.088652] [drm] ring test on 3 succeeded in 2 usecs
[104738.088658] [drm] ring test on 4 succeeded in 1 usecs
[104738.286093] [drm] ring test on 5 succeeded in 2 usecs
[104738.286098] [drm] UVD initialized successfully.
[104738.286119] [drm] ib test on ring 0 succeeded in 0 usecs
[104738.286137] [drm] ib test on ring 1 succeeded in 0 usecs
[104738.286155] [drm] ib test on ring 2 succeeded in 0 usecs
[104738.286173] [drm] ib test on ring 3 succeeded in 0 usecs
[104738.286190] [drm] ib test on ring 4 succeeded in 0 usecs
[104738.457645] [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get destroy ib
(-22).
[104738.457650] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-22).
[104738.457665] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=65963
--- Comment #29 from Marek Olšák <maraeo(a)gmail.com> ---
Is this issue still happening on current Mesa git?
--
You are receiving this mail because:
You are the assignee for the bug.