https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #21 from JerryD (jvdeli...@charter.net) ---
Created attachment 294599
--> https://bugzilla.kernel.org/attachment.cgi?id=294599&action=edit
dmesg from 5.10.5 kernel
I bummped up to the 5.10.5 kernel. The laptop suspends on lid close
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #20 from John Shand (jshand2...@gmail.com) ---
i am using the 5.10.3 kernel with the latest iso. I have installed it on my
machine. i have no issues with the amdgpu driver at all
--
You may reply to this email to add a comment.
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=208947
John Shand (jshand2...@gmail.com) changed:
What|Removed |Added
CC||jshand2...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=208947
JerryD (jvdeli...@charter.net) changed:
What|Removed |Added
CC||jvdeli...@charter.net
--
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #17 from Coleman Kane (ck...@colemankane.org) ---
Created attachment 292061
--> https://bugzilla.kernel.org/attachment.cgi?id=292061&action=edit
Proposed patch (add amdgpu.dp_cll_status bool, default: on)
Attaching a proposed patch
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #16 from Coleman Kane (ck...@colemankane.org) ---
Pulling the call / reassignment of "status" added in that commit seems to
revert the undesirable behavior, including in the latest "staging-testing" code
that I've tested on.
My hardwa
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #15 from Coleman Kane (ck...@colemankane.org) ---
Spoke too soon - that addition to the linux command line merely makes it work
intermittently. Sometimes I'll get the old behavior (max 1024x768), sometimes
I'll get the correct behavior
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #14 from Coleman Kane (ck...@colemankane.org) ---
So diving a bit further it looks like a contributor to this behavior might be
my misbehaving video hardware.
After some reading I did determine that I can add the following to my linux
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #13 from Coleman Kane (ck...@colemankane.org) ---
Interestingly enough, the description of a problem attempting to be addressed
with this fix sounds similar to behavior I experience with this system:
Namely, the Radeon RX 580M connect
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #12 from Coleman Kane (ck...@colemankane.org) ---
Ok I re-did the bisect and I think I found the actual commit that introduced
the regression. I have confirmed this by generating a reverse-patch and then
applying that to the latest sta
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #11 from Coleman Kane (ck...@colemankane.org) ---
Ok scratch those last three messages - I must have mislabeled one of the bisect
cycles, or some other screw up. I still narrowed my search space down, but it
looks like the commit it fi
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #10 from Coleman Kane (ck...@colemankane.org) ---
Trying to do that small change didn't seem to work, so I'm just going to try
seeing if it will work if I just remove that whole commit from the newer
staging-testing I've been working o
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #9 from Coleman Kane (ck...@colemankane.org) ---
I'm going to venture a guess that if I were to reverse the following part of
the change that it would likely "undo" the cause of the problem, but it doesn't
really solve the problem.
On
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #8 from Coleman Kane (ck...@colemankane.org) ---
Update - below is the finding from git bisect:
471c1dd9546df81d259664ac3e2ab0e99169f755 is the first bad commit
commit 471c1dd9546df81d259664ac3e2ab0e99169f755
Author: Reza Amini
Date:
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #7 from Coleman Kane (ck...@colemankane.org) ---
Thanks for the tip - I think I understand how this works now, so I will go
through the cycles of bisecting and follow up with what it finds, or a patch if
I think I'm able to address it
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #6 from Coleman Kane (ck...@colemankane.org) ---
Thanks Alex - I have added the four attachments you requested. I haven't done a
git bisect before, but I am very familiar with using git and understand the
concept of a bisect, so I coul
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #5 from Coleman Kane (ck...@colemankane.org) ---
Created attachment 292017
--> https://bugzilla.kernel.org/attachment.cgi?id=292017&action=edit
Xorg log from failure case (same 5.9-next kernel)
Xorg.log from trying to run Xorg under
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #4 from Coleman Kane (ck...@colemankane.org) ---
Created attachment 292015
--> https://bugzilla.kernel.org/attachment.cgi?id=292015&action=edit
Xorg.log from working case (Arch 5.8.1-1 kernel)
Xorg from working case on Arch 5.8.1-1
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #3 from Coleman Kane (ck...@colemankane.org) ---
Created attachment 292013
--> https://bugzilla.kernel.org/attachment.cgi?id=292013&action=edit
dmesg on faliure case from linux-next.git as of 2020-08-18 00:00:00
(pending-fixes branch
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #2 from Coleman Kane (ck...@colemankane.org) ---
Created attachment 292011
--> https://bugzilla.kernel.org/attachment.cgi?id=292011&action=edit
Working dmesg from Arch "linux" kernel 5.8.1-1
Working dmesg from Arch "linux" kernel 5.
https://bugzilla.kernel.org/show_bug.cgi?id=208947
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=208947
Coleman Kane (ck...@colemankane.org) changed:
What|Removed |Added
Regression|No |Yes
--
You are re
22 matches
Mail list logo
