https://bugs.freedesktop.org/show_bug.cgi?id=81620
Priority: medium
Bug ID: 81620
Assignee: dri-devel(a)lists.freedesktop.org
Summary: radeon: fence wait failed (-35) after hybrid suspend
on 3.15
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: iive(a)yahoo.com
Hardware: x86 (IA32)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 103217
--> https://bugs.freedesktop.org/attachment.cgi?id=103217&action=edit
dmesg of suspend/resume session with radeon.ko dpm debug turned on
My hardware is Radeon HD5670 (Redwood).
To reproduce the problem boot vanilla 3.15.x kernel. Run in KMS mode (no Xorg
server needed). Then suspend to ram-and-disk with the following command:
`echo suspend > /sys/power/disk; echo disk > /sys/power/state`
Resume from the power button. In `dmesg` you can find:
[ 83.997399] [drm] ring test on 5 succeeded in 1 usecs
[ 83.997403] [drm] UVD initialized successfully.
[ 83.997450] [drm] ib test on ring 0 succeeded in 0 usecs
[ 83.997494] [drm] ib test on ring 3 succeeded in 1 usecs
[ 94.137259] radeon 0000:01:00.0: ring 5 stalled for more than 10000msec
[ 94.137263] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x0000000000000002 on ring 5)
[ 94.137265] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 94.137268] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).
At this point if Xorg server is started any attempt to vdpau hardware decoding
would fail.
If the computer is left working, without reboot, at some point timeout would
trigger and GPU restart might be attempted, usually hanging the system. (I took
the following log from older GPU restart, probably successful).
[ 0.000000] Linux version 3.15.2 (root) (gcc version 4.8.3 (GCC) ) #2 SMP
[12398.387691] radeon 0000:01:00.0: ring 5 stalled for more than 242796msec
[12398.387699] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000005
last fence id 0x0000000000000004 on ring 5)
[12398.425151] radeon 0000:01:00.0: Saved 23 dwords of commands on ring 0.
[12398.425167] radeon 0000:01:00.0: GPU softreset: 0x00000009
[12398.425169] radeon 0000:01:00.0: GRBM_STATUS = 0xF5703828
[12398.425171] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000007
[12398.425173] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[12398.425175] radeon 0000:01:00.0: SRBM_STATUS = 0x200800C0
[12398.425177] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[12398.425179] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[12398.425181] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40000000
[12398.425183] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00008004
[12398.425185] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80228647
[12398.425187] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[12398.441572] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[12398.441626] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[12398.442782] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828
[12398.442783] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007
[12398.442785] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007
[12398.442787] radeon 0000:01:00.0: SRBM_STATUS = 0x200800C0
[12398.442789] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
[12398.442791] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[12398.442793] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[12398.442795] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[12398.442796] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
[12398.442798] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[12398.442813] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[12398.512161] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[12398.516583] [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000).
The bug vanishes if only suspend to ram or suspend to disk is used.
I tried to do a bisect, but a number of rc kernels seem to hang on me, long
before radeon module is loaded. At this point bisect
I suspected that the new async suspend/resume code might be at fault, as I was
seeing video card been turned off (aka monitor going off) and then turning on
a moment before shutting down completely.
So I found the commits of the async suspend (from an article) and reverted
them.
Reverting 200421a80f6e0a9e39d698944cc35cba103eb6ce,
3c31b52f96f7b559d950b16113c0f68c72a1985e seems to avoid the above effect about
monitor turning off, on, then off again. But it does not fix the bug.
Reverting
7cd0602d7836c0056fe9bdab014d5ac5ec5cb291,
92858c476ec4e99cf0425f05dee109b6a55eb6f8 and
9e5e7910df824ba02aedd2b5d2ca556426ea6d0b,
76569faa62c46382e080c3e190c66e19515aae1c,
de377b3972729f00ee236ae4a97393e282ffe391,
28b6fd6e37792b16a56d324841bdb20ab78e4522,
a59ffb2062df3a5c346dbed931fa1e587fd0f0f3
doesn't affect the bug either, so I assume that this bug is not related to
suspend/resume async changes.
If you cannot reproduce the problem, please advice me what commits to revert.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=72785
Priority: medium
Bug ID: 72785
Assignee: dri-devel(a)lists.freedesktop.org
Summary: bfgminer --scrypt on 7xxx+
Severity: normal
Classification: Unclassified
OS: All
Reporter: haagch.christoph(a)googlemail.com
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
bfgminer --benchmark without scrypt seems to be working fine now.
But I think many people would rather compute scrypt right now on their 7xxx+
GPUs, just considering the recent rumors that the radeon 7950 is getting sold
out because of litecoin miners.
With mesa/llvm it doesn't work yet.
llvm 3.5 197392, mesa and stuff are very recent git builds.
The kernel is https://github.com/luke-jr/bfgminer/blob/bfgminer/scrypt130511.cl
bfgminer is started with
bfgminer -v1 --scrypt -S opencl:auto --url=<pool> --userpass=<user:worker:pass>
The error is:
Initialising kernel scrypt130511.cl without bitalign, 1 vectors and worksize
256
[...]
LLVM ERROR: Cannot select: 0x7f0b7cbd40a0: ch = br_cc 0x7f0b7cd32bb0,
0x7f0b7cc28c20, 0x7f0b7cd32fb0, 0x7f0b7cc2bc30, 0x7f0b7cc2ad30 [ORD=19251]
[ID=4253]
0x7f0b7cd32fb0: i1,ch = llvm.SI.loop 0x7f0b7cc2c030:1, 0x7f0b7cd333b0,
0x7f0b7cc2c030 [ORD=19250] [ID=4250]
0x7f0b7cd333b0: i64 = TargetConstant<3431> [ID=132]
0x7f0b7cc2c030: i64,ch = llvm.SI.if.break 0x7f0b7cf2f3e0, 0x7f0b7cc2b530,
0x7f0b7cc2c530, 0x7f0b7cd339b0 [ORD=19249] [ID=4249]
0x7f0b7cc2b530: i64 = TargetConstant<3428> [ID=129]
0x7f0b7cc2c530: i1 = setcc 0x7f0b7cc7dd60, 0x7f0b7cc80760, 0x7f0b7cd337b0
[ORD=19248] [ID=212]
0x7f0b7cc7dd60: i64 = add 0x7f0b7cc81560, 0x7f0b7cc81360 [ORD=13153]
[ID=187]
0x7f0b7cc81560: i64,ch = CopyFromReg 0x7f0b7c0535d8, 0x7f0b7cc81660
[ORD=13147] [ID=149]
0x7f0b7cc81660: i64 = Register %vreg53 [ID=1]
0x7f0b7cc81360: i64 = Constant<1> [ID=2]
0x7f0b7cc80760: i64 = Constant<4> [ID=4]
0x7f0b7cd339b0: i64,ch = CopyFromReg 0x7f0b7c0535d8, 0x7f0b7cd342b0
[ORD=19249] [ID=185]
0x7f0b7cd342b0: i64 = Register %vreg52 [ID=130]
0x7f0b7cc2bc30: i1 = Constant<-1> [ID=133]
In function: search
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101262
Bug ID: 101262
Summary: Mesa reports no Video Memory
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: noonetinone(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
When trying to run Dying Light. It seg faults.
I compiled Mesa-git well past the patches written
by Brooks. Plus, I am using the overrides.
In common/Dying Light/DW/out/logs/ there are some
logs to examine.
I see this:
{21:54:20.616} INFO: [INFO] > [OpenGL] Video memory detected: 0 [MB]!
{21:54:20.620} INFO: [INFO] > Caught signal 11 (Segmentation fault).
{21:54:20.622} INFO: [INFO] > /lib64/libc.so.6(+0x336e0) [0x7f2472ceb6e0]
{21:54:20.622} INFO: [INFO] | /lib64/libpthread.so.0(pthread_join+0x1e)
[0x7f247a2d06de]
{21:54:20.622} INFO: [INFO] | /usr/lib64/dri/radeonsi_dri.so(+0x303b90)
[0x7f24674fbb90]
{21:54:20.622} INFO: [INFO] | /usr/lib64/dri/radeonsi_dri.so(+0x303be8)
[0x7f24674fbbe8]
I have 4 gig's on my card. All other native linux games run fine.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91808
Bug ID: 91808
Summary: trine1 misrender r600g
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: serafean(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 117987
--> https://bugs.freedesktop.org/attachment.cgi?id=117987&action=edit
misrendered scene
Trine 1 misrenders sometimes on HD6950, with mesa 11.0 rc
OpenGL renderer string: Gallium 0.4 on AMD CAYMAN (DRM 2.42.0, LLVM 3.6.2)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.0-rc1
OpenGL core profile shading language version string: 3.30
See attached screenshot.
I also made an apitrace, but am unsure as to where to post it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99403
Bug ID: 99403
Summary: Graphical glitches in witcher-1 with wine nine and
r600g (rv740).
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: roman.elshin(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 128941
--> https://bugs.freedesktop.org/attachment.cgi?id=128941&action=edit
screenshot
Very similar (but visually not exactly identical) glitches exists without nine,
but there are workaround in wine:
[HKEY_CURRENT_USER\Software\Wine\Direct3D]
CheckFloatConstants="enabled"
which helps with it. This key does not make a difference with nine.
There are no such problem with nouveau (750ti) here, os ubuntu-16.04 with oibaf
and commendsarnex ppa.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99549
Bug ID: 99549
Summary: pp: Failed to translate a shader
Product: Mesa
Version: git
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: lonewolf(a)xs4all.nl
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 129162
--> https://bugs.freedesktop.org/attachment.cgi?id=129162&action=edit
glxinfo > glxinfo.txt
Many applications including glxinfo show these messages in console :
pp: Failed to translate a shader for depth1fs
pp: Failed to translate a shader for blend2fs
pp: Failed to translate a shader for color1fs
pp: Failed to translate a shader for blend2fs
I was unable to figure out what component pp belongs to, so choose the driver
for my card.
mesa-git master, commit f8f7ea508b .
./autogen.sh --prefix=/usr \
--sysconfdir=/etc \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-gallium-drivers=i915,ilo,r300,r600,radeonsi,nouveau,svga,swrast,virgl \
--with-dri-drivers=i915,i965,r200,radeon,nouveau,swrast \
--with-egl-platforms=x11,drm,wayland \
--with-vulkan-drivers=intel,radeon \
--with-sha1=libnettle \
--enable-texture-float \
--enable-osmesa \
--enable-xa \
--enable-nine \
--disable-xvmc \
--enable-vdpau \
--enable-omx \
--enable-opencl \
--enable-opencl-icd \
--enable-glx-tls
glxinfo output (without the pp messages) attached
--
You are receiving this mail because:
You are the assignee for the bug.
Hi everyone,
This serie introduces the support in the sun4i-drm driver for the A33.
Beside the new IPs and special cases for the A33 new IPs, there's
nothing really outstanding, and is now at feature parity with the A13.
This serie is based on my A33 CCU patches posted earlier today here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-September/453208…
Let me know what you think,
Maxime
Changes from v1:
- Changed the TCON pins label
- Changed the TCON compatible as it's different from A23's
- Merged the SAT into the backend, as it really is part of the same
block in hardware.
- Reworded the DRC bindings description
- Added the backend interrupt to the DT
- Changed the name of the LCD panel to the actual brand and model
found on the ribbon
Maxime Ripard (9):
drm/sun4i: support TCONs without channel 1
drm/sun4i: support A33 tcon
drm/sun4i: backend: Handle the SAT
drm/sun4i: Add a DRC driver
of: Add vendor prefix for Netron DY
drm/panel: Add Netron DY E231732
ARM: sun8i: a33: Add display pipeline
ARM: sun8i: a23/a33: Add RGB666 pins
ARM: sun8i: sina33: Enable display
.../bindings/display/sunxi/sun4i-drm.txt | 39 +++++-
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/boot/dts/sun8i-a23-a33.dtsi | 10 ++
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts | 34 +++++
arch/arm/boot/dts/sun8i-a33.dtsi | 152 +++++++++++++++++++++
drivers/gpu/drm/panel/panel-simple.c | 26 ++++
drivers/gpu/drm/sun4i/Makefile | 2 +-
drivers/gpu/drm/sun4i/sun4i_backend.c | 61 +++++++++
drivers/gpu/drm/sun4i/sun4i_backend.h | 3 +
drivers/gpu/drm/sun4i/sun4i_drv.c | 8 +-
drivers/gpu/drm/sun4i/sun4i_tcon.c | 42 ++++--
drivers/gpu/drm/sun4i/sun4i_tcon.h | 2 +
drivers/gpu/drm/sun4i/sun6i_drc.c | 118 ++++++++++++++++
13 files changed, 479 insertions(+), 19 deletions(-)
create mode 100644 drivers/gpu/drm/sun4i/sun6i_drc.c
--
2.9.3
https://bugzilla.kernel.org/show_bug.cgi?id=176311
Bug ID: 176311
Summary: Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed
to get vblank before flip
Product: Drivers
Version: 2.5
Kernel Version: 4.7.5-200.fc24.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: vedran(a)miletic.net
Regression: No
As said in bug 176301, I have a Fiji card
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Fiji
[Radeon R9 FURY / NANO Series] (rev ca)
with two LG DisplayPort 27" 4K monitors. Locking screen while GNOME is running
on X makes both monitors go to sleep, all fine. Upon moving a mouse or pressing
a key, only one of them will wake up, and always the same one. Dmesg shows:
[drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* failed to get vblank before flip
The other monitor will wake up if one switches to a console (e.g. Ctrl+Alt+F3)
and back or one powers any of the monitors off and back on.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=48424
Bug #: 48424
Summary: Fix warnings/errors reported by clang's scan-build
tool
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86 (IA32)
URL: https://gitorious.org/jobermayr/scan-build-mesa
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Mesa core
AssignedTo: mesa-dev(a)lists.freedesktop.org
ReportedBy: johannesobermayr(a)gmx.de
CC: dri-devel(a)lists.freedesktop.org,
nouveau(a)lists.freedesktop.org
https://gitorious.org/jobermayr/scan-build-mesa
~ 8 MB to download, 680 MB on disk.
Please report false positives here. I will forward them.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.