https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #19 from Gordon (gor...@gordonite.tech) ---
Never mind I was wrong:
Canvas score - Test 1: 1235 - Test 2: 2115
WebGL score - Test 1: 911 - Test 2: 1005
Total score: 5266
Your results compared to other users
You score better than 97%
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #18 from Gordon (gor...@gordonite.tech) ---
With a single display connected and those options still enabled:
Canvas score - Test 1: 901 - Test 2: 2049
WebGL score - Test 1: 903 - Test 2: 1020
Total score: 4873
Your results compared
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #17 from Gordon (gor...@gordonite.tech) ---
Update:
- discord is crashing due to OpenGL problems
- Random video output in the bottom right corner of screen bug in driver level
code most likely
- no info about it in dmesg
- benchmarks
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #16 from Gordon (gor...@gordonite.tech) ---
Those settings both work to solve the problems.
Running on: 5.8.7-200.fc32.x86_64 with those options only.
Performance is almost what I'd expect now too. I can consistently across
distros
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #15 from Alex Deucher (alexdeuc...@gmail.com) ---
Does setting amdgpu.dpm=0 on the kernel command line in grub fix the issue? If
so, remove that and try setting amdgpu.ppfeaturemask=0xbffd on the kernel
command line in grub.
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #14 from Gordon (gor...@gordonite.tech) ---
more info:
echo 'auto' has the flickering problem
echo 'low' seems to work fine
echo 'high' seems to work fine
transitioning between 'high' and 'low' makes the problem appear / light
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #13 from Gordon (gor...@gordonite.tech) ---
To fix this problem after boot on the RX 5700 XT Red Devil I had to run this as
root, can we make a patch for that to be the default?
- echo "high" >
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #12 from Gordon (gor...@gordonite.tech) ---
I'm not certain but:
- uint32_t cur_value, i, timeout = adev->usec_timeout * 10;
if adev_usec_timeout is the microseconds timeout, then most likely the * 10 is
wrong, as the below for loop
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #11 from Gordon (gor...@gordonite.tech) ---
(In reply to Alex Deucher from comment #10)
> Do things work correctly if you attach the second monitor after the system
> is up and running?
Yep they do indeed.
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=208893
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #9 from Gordon (gor...@gordonite.tech) ---
nvm rebooted and the problem came back.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #8 from Gordon (gor...@gordonite.tech) ---
not getting any symptoms of the problem now.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #7 from Gordon (gor...@gordonite.tech) ---
[ 18.764922] snd_hda_intel :0c:00.1: refused to change power state from
D3hot to D0
[ 18.869351] snd_hda_intel :0c:00.1: CORB reset timeout#2, CORBRP = 65535
[ 19.090949]
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #6 from Gordon (gor...@gordonite.tech) ---
Created attachment 290871
--> https://bugzilla.kernel.org/attachment.cgi?id=290871=edit
this is the log from after my patch is applied
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #5 from Gordon (gor...@gordonite.tech) ---
The problem: the GPU card / seems to make a difference here, some seem to
require a bigger delay? and some just work.
Would be nice to know why.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #4 from Gordon (gor...@gordonite.tech) ---
Found a fix for the issue.
My card is a PowerColor Red Devil 5600 XT.
diff --git a/drivers/gpu/drm/amd/powerplay/smu_cmn.c
b/drivers/gpu/drm/amd/powerplay/smu_cmn.c
index
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #3 from Gordon (gor...@gordonite.tech) ---
The Diff from the log file - clearly showing the problem:
[ 51.925494] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 54.442825] amdgpu: Msg issuing
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #2 from Gordon (gor...@gordonite.tech) ---
Created attachment 290869
--> https://bugzilla.kernel.org/attachment.cgi?id=290869=edit
added logfile for when single display is connected - notice no ERROR from
AMDGPU anymore!
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #1 from Gordon (gor...@gordonite.tech) ---
Created attachment 290867
--> https://bugzilla.kernel.org/attachment.cgi?id=290867=edit
added logfile for system has some AMD GPU errors in it, this is when both
displays are connected.
19 matches
Mail list logo
