https://bugs.freedesktop.org/show_bug.cgi?id=75992
Priority: medium
Bug ID: 75992
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Display freezes & corruption with an r7 260x on
3.14-rc6
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: edt(a)aei.ca
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 95520
--> https://bugs.freedesktop.org/attachment.cgi?id=95520&action=edit
log of boot
I recently added a R7 260X to my system. While the card works with 3.13 its
supposed work much better with 14-rc. This is not the case. My system is
unstable without radeon.dpm=0 which was the default in .13.
linux 3.14-rc6 (with an up to date arch, stable X and mesa-git (10.2) mesa 10.1
and 10.0 also show very similar problems.
When X started I did notice some corruption. There are sets of two rectangles
about of a height of 2 or 3 mm, width of 25m or so with a second about a cm
below. The often occurs in chomium especially when scrolling. Runing the
unigine-sanctuary or unigine-tropics demo/benchmark programs also produce the
above problems and eventually stall.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105433
Bug ID: 105433
Summary: Unreliable Modesetting on Tonga with two DVI Screens
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: freedesktop-bugs(a)digital-trauma.de
Two devices connected via DVI, one not coming up (powersave, no signal). On
retry , they may swap their working state, or both go to energy save, or
rarely, both work. This happens regardless of resolutions set on the screens in
question.
Screens: 2 x Benq G2222HDL
Connected via DVI (both straight to card)
Card: ASUS Strix R9285 DC2OC 2GD5
Kernel: amd-staging-drm-next 6e62bc7a123b "drm/amdgpu:Always save uvd vcpu_bo
in VM Mode"
Bug report as discussed in bug 100919.
Possibly related to bug 91202.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105728
Bug ID: 105728
Summary: radeon_init takes longer than a few seconds
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop(a)molgen.mpg.de
On a Asus F2A85-M PRO with an AMD A6-6400K APU with Radeon HD Graphics and
Linux 4.14.13 `radeon_init`, according to `initcall_debug`, takes over two
seconds to execute. Init functions should not take longer than a few
milliseconds to load.
```
$ sudo dmesg | grep -i radeon
[ 18.767379] calling radeon_init+0x0/0xab [radeon] @ 292
[ 18.767382] [drm] radeon kernel modesetting enabled.
[ 18.809797] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 -
0x000000002FFFFFFF (768M used)
[ 18.809798] radeon 0000:00:01.0: GTT: 1024M 0x0000000030000000 -
0x000000006FFFFFFF
[ 18.811498] [drm] radeon: 768M of VRAM memory ready
[ 18.811499] [drm] radeon: 1024M of GTT memory ready.
[ 18.812019] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/ARUBA_pfp.bin
[ 18.812512] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/ARUBA_me.bin
[ 18.812674] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/ARUBA_rlc.bin
[ 18.812813] [drm] radeon: dpm initialized
[ 18.813730] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin
[ 18.814178] radeon 0000:00:01.0: firmware: direct-loading firmware
radeon/TAHITI_vce.bin
[ 18.867545] radeon 0000:00:01.0: WB enabled
[ 18.867549] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000030000c00 and cpu addr 0xffff8a5af9339c00
[ 18.867928] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffab8a01435a18
[ 18.888018] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr
0x0000000030000c18 and cpu addr 0xffff8a5af9339c18
[ 18.888021] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr
0x0000000030000c1c and cpu addr 0xffff8a5af9339c1c
[ 18.888022] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr
0x0000000030000c04 and cpu addr 0xffff8a5af9339c04
[ 18.888024] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr
0x0000000030000c08 and cpu addr 0xffff8a5af9339c08
[ 18.888025] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000030000c0c and cpu addr 0xffff8a5af9339c0c
[ 18.888026] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr
0x0000000030000c10 and cpu addr 0xffff8a5af9339c10
[ 18.916268] radeon 0000:00:01.0: radeon: MSI limited to 32-bit
[ 18.917088] radeon 0000:00:01.0: radeon: using MSI.
[ 18.917113] [drm] radeon: irq initialized.
[ 20.736792] [drm] Radeon Display Connectors
[ 21.035055] fbcon: radeondrmfb (fb0) is primary device
[ 21.152576] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[ 21.172202] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on
minor 0
[ 21.172314] initcall radeon_init+0x0/0xab [radeon] returned 0 after 2348527
usecs
[ 126.973651] radeon_dp_aux_transfer_native: 74 callbacks suppressed
```
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101213
Bug ID: 101213
Summary: Kernel 4.11: amdgpu regression causes artifacts OLAND
amd gpu gcn 1.0
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: eutychios23(a)gmail.com
The display Manager,part of the desktop and any graphics app i run get severe
artifacts on any kernel 4.11.x version with amdgpu enabled, whereas in 4.10.17
all is working good.
Reproduce:
Install kernel 4.11 and later with SIK=y, blacklist radeon, install
xf86-amdgpu, enable the amdgpu module and boot the kernel.
Same regression existed in kernels 4.10.2 and lower but was fixed after the
4.10.3 update
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105664
Bug ID: 105664
Summary: AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz
while it is supposed to be 1030MHz
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: yassine10suno(a)gmail.com
Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:
max_sclk = 75000;
instead of
max_sclk = 103000;
Why is that? I changed it and rebuilt the kernel, and I can say that
there are absolutely no issues when using the 1030MHz clock, **which is the
default frequency this GPU is designed for**.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105500
Bug ID: 105500
Summary: AMD Richland (ARUBA) no screen at DP output when using
three displays
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: vinibali1(a)gmail.com
Created attachment 138094
--> https://bugs.freedesktop.org/attachment.cgi?id=138094&action=edit
dmesg
Hello there!
After connecting and enabling the 3rd monitor in D-Sub, the one with DP becames
black. Most of the time I use 2 displays with (DVI-I and DP) without any
problem. The desired layout is the following, however I even tried to use HDMI
instead of DVI-I:
___ __ __
|DVI||DP||DS|
2 1 3
__ __ ____
|DS||DP||HDMI|
2 1 3
None of the options are working, however it's fine on Windows using the lastest
- official beta - Crimson Edition 15.7.1.
The motherboard had an ASMedia ASM1445 DVI/HDMI bridge, so I couldn't use these
outputs at the same time.
CPU: AMD A8-6500
GPU: AMD Radeon HD8570 (ATOMBIOSBK-AMD VER015.031.000.000.000000,
02/17/13,02:36:07)
MOBO: ASUS F2A85M-PRO (BIOS 6601)
OS: Arch Linux 4.13 AMD64
xf86-video-ati 1:18.0.0-1
xorg-server 1.19.6+13+gd0d1a694f-1
The logs/outputs were saved at 4.13, however it's not working with both the
up-to-date Arch (4.15) and Xubuntu 18.04 beta.
Thank you
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105221
Bug ID: 105221
Summary: kernel modeswitch fails on Fedora 27 on Evergreen
(Radeon HD5850)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: brouhaha(a)fedoraproject.org
With Fedora 26 I had sporadic problems with the system crashing at the first
kernel mode switch, before entering the LUKS passphrase at boot time, but I
could hit reset and usually the second time it would work. With Fedora 27 this
happens to me consistently every time. The only way I can successfully boot is
to use "nomodeset" on the kernel command line, which then causes issues for my
X session.
My system has Asus Sabertooth 990FX R2.0 motherboard, AMD FX-8350 CPU, and
Radeon HD 5850 graphics card. I'm running Fedora 27 with kernel
4.15.3-300.fc27.x86_64.
Fedora Bugzilla shows someone else having that problem with HD 5450. Maybe its
a general Evergreen problem.
https://bugzilla.redhat.com/show_bug.cgi?id=1474044
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105144
Bug ID: 105144
Summary: Recent mesa makes GPU temperature too hot with
GL/VDPAU/VAAPI
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: whatisthis.sowhat(a)gmail.com
With mesa 17.3 (and maybe kernel >= 4.13), using GL,VAAPI or VDPAU, GPU
temperature makes to be too hot.
Almost upper than 60℃ with RADEON HD7770 (less than 15℃ at room).
When not using GL etc, temperature upper than 50℃.
With earlier version of GL, VAAPI and VDPAU, temperature is less than 60℃ (at
worst, less than 70℃).
Regards,
Ohta.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105038
Bug ID: 105038
Summary: slight lags in youtube video 1080p since a change in
kernel 4.15 related to drm/ttm
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: mister.freeman(a)laposte.net
Created attachment 137264
--> https://bugs.freedesktop.org/attachment.cgi?id=137264&action=edit
dmesg
Hello,
I have a radeon HD4650 pcie, I use the radeon driver,
since a new algorithm for drm/ttm introduced in kernel 4.15.x then I notice a
performance loss in video playback, especially when the format is 1080p ( for
example youtube video ), some lags are visible ( for example travelling images,
vertical scroll of the credits in a video ),
the bug has been introduced since this commit :
commit 648bc3574716400acc06f99915815f80d9563783
Author: Christian König <christian.koenig(a)amd.com>
Date: Thu Jul 6 09:59:43 2017 +0200
drm/ttm: add transparent huge page support for DMA allocations v2
Try to allocate huge pages when it makes sense.
v2: fix comment and use ifdef
Signed-off-by: Christian König <christian.koenig(a)amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling(a)amd.com>
Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com>
reverting this patch solves the bug,
I have created a bug report in kernel's bugzilla :
https://bugzilla.kernel.org/show_bug.cgi?id=198511
Christian König advices me to open a bug report here for drm/radeon,
I have filmed my screen in order to demonstrate the effect of this bug, you can
see my video here :
https://www.youtube.com/watch?v=YqtleU5YBlA
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104963
Bug ID: 104963
Summary: MSI MoBo A88XM-E35 GPU Trinity A8-5600K (Aruba
HD7560D) Boot loop without radeon.dpm=0
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: f0rhum(a)free.fr
Hi
I was driven here by Ubuntu team :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746357
Only nomodeset and radeon.dpm=0 allow boot. Issue is here from kernel 3.13 to
4.15.1
--
You are receiving this mail because:
You are the assignee for the bug.