Hello Alex,
like AMD...;-)
[Why]
5.3-rcX (-rc3)
- has broken (regressed) block layer (CD/DVD, games...) - fixed in 5.3
final
- ACPI (power management) regression - fixed in 5.3 final
- USB 3.1/3.2 regression (5.000 vs 10.000 Mbit/s mode, in use heavily
here)
even with AMD's partner ASMedia
Hello Alex et al.,
can you please have a look at this bug report and findings?
Sapphire Pulse RX 5700 XT power consumption
https://bugs.freedesktop.org/show_bug.cgi?id=111482
e.g.
https://bugs.freedesktop.org/show_bug.cgi?id=111482#c30
Thanks,
Dieter
Hello Yong,
this was your commit ;-)
Greetings,
Dieter
Originalnachricht
Betreff: [Bug 109650] [amd-staging-drm-next] - Polaris 20 dc - idle
power regession 3x [bisected]
Datum: 16.02.2019 00:42
Von: bugzilla-dae...@freedesktop.org
An: dri-de...@lists.freedesktop.org
Hello Andrey,
this series can't apply (brake on #3) on top of amd-staging-drm-next.
v2 works (Thu, 11 Apr 2019).
Dieter
Am 18.04.2019 17:00, schrieb Andrey Grodzovsky:
From: Christian König
Don't block others while waiting for the fences to finish, concurrent
submission is perfectly valid in
CC trimmed
Hello Alex and Harry,
any comments on this?
I'm running my Xeon X3470 (4c/8t) with this under amd-staging-drm-next
(as always ;-) ) and see no issues so far.
Thanks!
Dieter
Am 04.06.2019 22:21, schrieb Yrjan Skrimstad:
On Thu, May 30, 2019 at 02:08:21AM +0200, Yrjan Skrimstad wro
Hello Christian, AMD guys,
this one _together_ with these series
[PATCH 1/7] drm/amdgpu: use new scheduler load balancing for VMs
https://lists.freedesktop.org/archives/amd-gfx/2018-August/024802.html
on top of
amd-staging-drm-next 53d5f1e4a6d9
freeze whole system (Intel Xeon X3470, RX580) duri
Am 03.08.2018 13:09, schrieb Christian König:
Am 03.08.2018 um 03:08 schrieb Dieter Nützel:
Hello Christian, AMD guys,
this one _together_ with these series
[PATCH 1/7] drm/amdgpu: use new scheduler load balancing for VMs
https://lists.freedesktop.org/archives/amd-gfx/2018-August/024802.html
Am 04.08.2018 05:27, schrieb Dieter Nützel:
Am 03.08.2018 13:09, schrieb Christian König:
Am 03.08.2018 um 03:08 schrieb Dieter Nützel:
Hello Christian, AMD guys,
this one _together_ with these series
[PATCH 1/7] drm/amdgpu: use new scheduler load balancing for VMs
https
Am 04.08.2018 06:12, schrieb Dieter Nützel:
Am 04.08.2018 05:27, schrieb Dieter Nützel:
Am 03.08.2018 13:09, schrieb Christian König:
Am 03.08.2018 um 03:08 schrieb Dieter Nützel:
Hello Christian, AMD guys,
this one _together_ with these series
[PATCH 1/7] drm/amdgpu: use new scheduler load
Am 04.08.2018 06:18, schrieb Dieter Nützel:
Am 04.08.2018 06:12, schrieb Dieter Nützel:
Am 04.08.2018 05:27, schrieb Dieter Nützel:
Am 03.08.2018 13:09, schrieb Christian König:
Am 03.08.2018 um 03:08 schrieb Dieter Nützel:
Hello Christian, AMD guys,
this one _together_ with these series
Am 06.08.2018 02:13, schrieb Dieter Nützel:
Am 04.08.2018 06:18, schrieb Dieter Nützel:
Am 04.08.2018 06:12, schrieb Dieter Nützel:
Am 04.08.2018 05:27, schrieb Dieter Nützel:
Am 03.08.2018 13:09, schrieb Christian König:
Am 03.08.2018 um 03:08 schrieb Dieter Nützel:
Hello Christian, AMD
For the series
Tested-by: Dieter Nützel
on RX580,
amd-staging-drm-next
#5024f8dfe478
Dieter
Am 13.08.2018 11:58, schrieb Huang Rui:
The idea and proposal is originally from Christian, and I continue to
work to
deliver it.
Background:
amdgpu driver will move all PD/PT and PerVM BOs into
Hello Christian and David,
I've running Alex's 'amd-staging-drm-next' with it enabled.
Great numbers with vkmark (radv) and glmark2.
Sadly 'amd-staging-drm-next' still stands on 5.2.0-rc1 - no changes
during the last 2 weeks.
Is Alex on vacation/traveling?
Greetings,
Dieter
[-]
Zhou, David(C
Hello Alex,
after release of 5.3 my devel system was migrated to compressed firmware
files.
So current 'amd-staging-drm-next' can't boot any longer and I can't test
anything on it for you (AMD) ;-)
Greetings,
Dieter
PS I'm NOT on amd-gfx.
___
amd-g
Hello Alex,
after your latest Navi merge 'amd-staging-drm-next' is broken with
Polaris 20.
It hangs with very light gray (mostly black) screen after first mode
switch.
Tested commit:
317d5033ab6c (HEAD -> amd-staging-drm-next, origin/amd-staging-drm-next)
drm/amdgpu: add job->preamble_stat
19 15:53, schrieb Zhang, Hawking:
Ah, sorry, it has not landed yet. but the patch is in review list now.
[PATCH] drm/amdgpu: fix modprobe failure for uvd_4/5/6
Regards,
Hawking
-Original Message-
From: amd-gfx On Behalf Of
Zhang, Hawking
Sent: 2019年6月24日 21:50
To: Dieter Nützel ; Alex De
Hello Michel,
as this is for radeon, do you think this could/should fix
the wrong reported VRAM size with Unigine_Heaven/-Valley, too?
Maybe speed things up? ;-)
Unigine_Valley-1.0
GPU: Unknown GPU x1
System memory: 24102 MB
Video memory: 256 MB
Sync threads: 7
Async threads: 8
I'll try patc
Am 31.01.2017 16:43, schrieb Deucher, Alexander:
-Original Message-
From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf
Of Dieter Nützel
Sent: Tuesday, January 31, 2017 6:25 AM
To: Michel Dänzer
Cc: Alex Deucher; mesa-...@lists.freedesktop.org; amd-
g
Hello all,
since latest update
1d7da702e70d3c27408a3bb312c71d6be9f7bebe
drm/amd/powerplay: fix spelling mistake: "dividable" -> "divisible"
I didn't get fan info with my RX580 (Polaris21) any longer.
Worked with this commit:
786df0b89fe5a0b405d4de0a1ce03003c0743ec3
drm/amd/display: fix pflip
essage-
From: Alex Deucher [mailto:alexdeuc...@gmail.com]
Sent: Friday, September 29, 2017 10:11 PM
To: Dieter Nützel; Zhu, Rex
Cc: amd-devel; DRI Devel; Wentland, Harry; Michel Dänzer
Subject: Re: [amd-staging-drm-next] regression - no fan info (sensors)
on RX580
Rex, probably related to the recent
by: Alex Deucher
Signed-off-by: Rex Zhu
:04 04 72361654709479890586e383ec73088e535a1cf5
2b6d5a75ffc3b6fd48c63e79bf28faddcc734918 M drivers
Greetings,
Dieter
Am 09.10.2017 02:19, schrieb Dieter Nützel:
Sorry Rex,
after return from our vacation,
I've tested latest amd-sta
Hello,
next (regression) compilation error:
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c: In function
‘resource_map_pool_resources’:
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:1688:14:
error: implicit declaration of function ‘acquire_first_split_pipe’; did
you
Am 13.10.2017 18:44, schrieb Harry Wentland:
Acquire_first_split_pipe only makes sense for DCN.
Signed-off-by: Harry Wentland
Tested-by: Dieter Nützel
---
drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/display
Am 13.10.2017 21:22, schrieb Harry Wentland:
On 2017-10-12 08:22 PM, Dieter Nützel wrote:
Hello,
next (regression) compilation error:
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c: In
function ‘resource_map_pool_resources’:
drivers/gpu/drm/amd/amdgpu/../display/dc/core
Am 21.10.2017 23:22, schrieb Alex Deucher:
Hi Dave,
Last batch of new stuff for DC. Highlights:
- Fix some memory leaks
- S3 fixes
- Hotplug fixes
- Fix some CX multi-display issues
- MST fixes
- DML updates from the hw team
- Various code cleanups
- Misc bug fixes
Now this tree has the same f
Am 17.10.2017 16:59, schrieb Michel Dänzer:
On 17/10/17 04:53 PM, Harry Wentland wrote:
On 2017-10-17 10:47 AM, Michel Dänzer wrote:
On 13/10/17 09:22 PM, Harry Wentland wrote:
On 2017-10-12 08:22 PM, Dieter Nützel wrote:
next (regression) compilation error:
drivers/gpu/drm/amd/amdgpu
Am 22.10.2017 23:48, schrieb Dieter Nützel:
Am 21.10.2017 23:22, schrieb Alex Deucher:
Hi Dave,
Last batch of new stuff for DC. Highlights:
- Fix some memory leaks
- S3 fixes
- Hotplug fixes
- Fix some CX multi-display issues
- MST fixes
- DML updates from the hw team
- Various code cleanups
Hello Alex & Rex,
any progress?
The 'screen blank' (monitor standby mode) is really annoying.
Thanks,
Dieter
Am 23.10.2017 03:03, schrieb Dieter Nützel:
Am 22.10.2017 23:48, schrieb Dieter Nützel:
Am 21.10.2017 23:22, schrieb Alex Deucher:
Hi Dave,
Last batch of ne
Am 26.10.2017 19:26, schrieb Alex Deucher:
On Thu, Oct 26, 2017 at 10:10 AM, Dieter Nützel
wrote:
Hello Alex & Rex,
any progress?
The 'screen blank' (monitor standby mode) is really annoying.
Does this patch help?
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-stagi
Hello Christian,
is this for these warnings flooding my dmesg-log or do I have to open a
new ticket:
Current amd-staging-drm-next commit #7781a8c68a6a from you ;-)
[ 6588.429302] WARNING: CPU: 5 PID: 2957 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dm_services.h:132
generic_reg_update_ex+0x
Hello Christian,
I've running this since you've sent it on-top of amd-staging-4.11. But I
think my poor little FUJITSU PRIMERGY TX150 S7, Xeon X3470 (Nehalem),
PCIe 2.0, 24 GB is to old for this stuff...
[1.066475] pci :05:00.0: VF(n) BAR0 space: [mem
0x-0x0003 64bit] (co
ardware is perfectly capable of doing this, it's just
that the BIOS/Motherboard didn't enabled a PCIe window per default to
avoid problems with 32bit OSes.
Regards,
Christian.
Am 30.06.2017 um 01:51 schrieb Dieter Nützel:
Hello Christian,
I've running this since you've sent
Hello all,
got two kernel crahes in the last few days (both are the same) in
'drm_object_property_get_value' with 'amd-staging-drm-next' git commit
#94097b0f7f1b.
Greetings,
Dieter
[ 36.926007] [ cut here ]
[ 36.926031] WARNING: CPU: 1 PID: 2946 at
drivers/gpu/d
I've send a related kernel crash log to amd-devel some days ago without
any answer, yet...
Was:
[amd-staging-drm-next] kernel crash with amdgpu on RX580 in
'drm_object_property_get_value'
I get this in _all_ current 'amd-staging-drm-next' versions. ;-(
[16301.515079] [ cut here ]
Hello,
commit # 680acc64120cd7fe4fb21d816a0fc0854018fe59
drm/amd/display: Set disp clk in a safe way to avoid over high dpp clk.
makes CONFIG_DRM_AMD_DC_DCN1_0=y mandatory, again.
I think it was not intentional?
Without it I get:
Kernel: arch/x86/boot/bzImage is ready (#1)
ERROR: "dcn_find_dc
Ups,
you were faster than ever - my 'double post'
''CONFIG_DRM_AMD_DC_DCN1_0=y' mandatory, again'...;-)
Tested-by: Dieter Nützel
Dieter
Fixes: 680acc64120c (drm/amd/display: Set disp clk in a safe way to
avoid
over high dpp clk.)
Signed-off-by: Harry Went
Hello Harry and Alex,
Watt numbers are broken for some days (5 to 7).
Polaris 20 (RX580), Sapphire Nitro+, 8 GB
amdgpu-pci-0100
Adapter: PCI adapter
vddgfx: +0.75 V
fan1:1048 RPM
temp1:+28.0°C (crit = +94.0°C, hyst = -273.1°C)
power1:0.00 W (cap = 175.00 W)
Shou
Tested-by: Dieter Nützel
Even better 'idle' (KDE Plasma 5 desktop, single monitor) then _ever_:
amdgpu-pci-0100
Adapter: PCI adapter
vddgfx: +0.75 V
fan1: 900 RPM
temp1:+26.0°C (crit = +94.0°C, hyst = -273.1°C)
power1: 31.04 W (cap = 175.00 W)
But
For the series:
Tested-by: Dieter Nützel
on RX580
amd-staging-drm-next 85d09ce5e5039644487e9508d6359f9f4cf64427
with glmark2, DiRT Rally and F1 2017 (radv)
Dieter
Am 17.11.2017 11:49, schrieb Christian König:
Hi everyone,
Michel already reviewed this back in April, but I didn't found
m/amdgpu: remove VRAM size reduction v2
95d8c587cba5 drm/amd/pp: fix typecast error in powerplay.
[-]
amdgpu-pci-0100
Adapter: PCI adapter
fan1: 881 RPM
temp1:+29.0°C (crit = +0.0°C, hyst = +0.0°C)
Tested-by: Dieter Nützel
Thank you very much Alex!
Dieter
Am 20.11.2017 23:57, schr
c:33:
./include/drm/ttm/ttm_bo_api.h:334:5: note: declared here
int ttm_bo_validate(struct ttm_buffer_object *bo,
^~~
New version comming?
Thanks,
Dieter
Am 20.11.2017 05:35, schrieb Dieter Nützel:
For the series:
Tested-by: Dieter Nützel
on RX580
amd-staging-drm-next 85d09c
ex Deucher
Tested-by: Dieter Nützel
against 'amd-staging-drm-next' on RX580
---
drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c
index 3506758349dc..6f56f
Tested-by: Dieter Nützel
Dieter
Am 05.12.2017 13:54, schrieb Christian König:
When we detect consecutive allocation of pages swap them to avoid
accidentally freeing them as huge page.
v2: use swap
v3: check if it's really the first allocated page
v4: don't touch the loop variable
For the series:
Tested-by: Dieter Nützel
on RX580 8GB
with UH, UV, Blender 2.79, smoketest (Vulkan), glmark2 (parallel with
OpenCL (/opt/opencl-example>./run_tests.sh))
Dieter
Am 06.12.2017 17:49, schrieb Lucas Stach:
Hi all,
second try to move the AMDGPU scheduler into a com
Hello AMD team,
I got this since latest 'amd-staging-drm-next' git update
(#b956c586e58a) during boot with Polaris RX580 DC on:
[3.586342] [drm:dal_bios_parser_init_cmd_tbl [amdgpu]] *ERROR* Don't
have enable_spread_spectrum_on_ppll for v4
[3.586410] [drm:dal_bios_parser_init_cmd_tbl
Hello Rex,
is this expected on Polaris 20 (RX580)?
I get this in dmesg when I try to query some values.
[ 7948.845940] amdgpu: [powerplay] pp_get_power_profile_mode was not
implemented.
amd-staging-drm-next git
#f1182e58cded (HEAD -> amd-staging-drm-next,
origin/amd-staging-drm-next) drm/ttm
For the series:
COOL stuff!
RX580 (Polaris20) during 'idle' (single HD 1920x1080):
amd-staging-drm-next
amdgpu-pci-0100
Adapter: PCI adapter
vddgfx: +0.75 V
fan1: 904 RPM
temp1:+25.0°C (crit = +94.0°C, hyst = -273.1°C)
power1: 32.00 W
Thank you very much Alex et al
Am 03.01.2018 16:03, schrieb Harry Wentland:
On 2017-12-27 04:04 AM, Michel Dänzer wrote:
On 2017-12-27 05:43 AM, Dieter Nützel wrote:
Hello AMD team,
I got this since latest 'amd-staging-drm-next' git update
(#b956c586e58a) during boot with Polaris RX580 DC on:
[
48 matches
Mail list logo
