https://bugs.freedesktop.org/show_bug.cgi?id=101387
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #25 from Michel Dänzer ---
(In reply to Carlo Caione from comment #24)
> - Retrieve the gamma size from the kernel with drmModeGetCrtc()
This could be wrong if the currently set pixel format uses a different LUT
size. Plymouth can h
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #24 from Carlo Caione ---
> Sounds like there is also a bug somewhere in the kernel (driver), but
> even if that was fixed, it still wouldn't solve the plymouth issue
> in all cases.
Yeah, so what should be the right way of proceedin
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #23 from Michel Dänzer ---
Sounds like there is also a bug somewhere in the kernel (driver), but even if
that was fixed, it still wouldn't solve the plymouth issue in all cases.
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #22 from Carlo Caione ---
> Plymouth shouldn't get the values with drmModeCrtcGetGamma — there's no
> guarantee that the CLUT contains suitable values at that point (e.g. the
> hardware could currently be programmed for a different c
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #21 from Michel Dänzer ---
Plymouth shouldn't get the values with drmModeCrtcGetGamma — there's no
guarantee that the CLUT contains suitable values at that point (e.g. the
hardware could currently be programmed for a different colour
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #20 from Carlo Caione ---
> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.
Can you expand on this a little bit?
I
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #19 from Carlo Caione ---
Those patches do not solve the issue but I noticed that the visual corruption
at boot is not reproducible on the latest linus master. I bisected and found
out that the commit solving the problem is
https://p
el; amd-...@lists.freedesktop.org; Deucher, Alexander
>>> Cc: Chris Chiu; Linux Upstreaming Team
>>> Subject: amdgpu display corruption and hang on AMD A10-9620P
>>>
>>> Hi,
>>>
>>> We are working with new laptops that have the AMD Bristol Ri
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #18 from Alex Deucher ---
The VCE regression is fixed. If you want to try those patches, they are
available here:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.13-wip
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #17 from Alex Deucher ---
(In reply to Carlo Caione from comment #16)
> I see. The problem is that the garbage lines result in a very bad experience
> for the user. Do you have any idea how to fix / mitigate that?
If it's related to
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #16 from Carlo Caione ---
I see. The problem is that the garbage lines result in a very bad experience
for the user. Do you have any idea how to fix / mitigate that?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #15 from Alex Deucher ---
(In reply to Carlo Caione from comment #14)
>
> Fortunately it disappears after ~2 seconds when plymouth kicks in. My
> impression is that the visual corruption is triggered again when
> interpreting some a
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #14 from Carlo Caione ---
> not likely related.
Alright, any hint where to start looking? As I said before it looks like the
visual corruption (this https://pasteboard.co/qrC9mh4p.jpg) at boot starts at
[drm] amdgpu atom DIG backli
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #13 from Alex Deucher ---
(In reply to Carlo Caione from comment #12)
> Also (in case it is useful for the corruption issue):
>
not likely related.
> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Devi
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #12 from Carlo Caione ---
Also (in case it is useful for the corruption issue):
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Device 9874 (rev ca)
...
03:00.0 Display controller: Advanced Micro Devices, I
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #11 from Carlo Caione ---
Yes, that solves the panic issue, thank you. I still have the corruption at
boot though, any idea what that can be?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #10 from Alex Deucher ---
Created attachment 131982
--> https://bugs.freedesktop.org/attachment.cgi?id=131982&action=edit
possible fix
This patch should fix the issue.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #9 from Alex Deucher ---
Can you please attach a copy of your vbios?
(as root)
(use lspci to get the bus id)
cd /sys/bus/pci/devices/
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #8 from Carlo Caione ---
Just a better description of what's going on and a couple of questions.
When amdgpu_atombios_crtc_powergate_init() is called this triggers the parsing
of the command table with index == 13 (>> execute C5C0 (
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #7 from Carlo Caione ---
Just to be clear. I have already verified that the address of &args and ctx->ps
are the same, so this is definitely something we want to fix somehow.
--
You are receiving this mail because:
You are the assi
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #6 from Carlo Caione ---
Uhm, probably I have found something.
In amdgpu_atombios_crtc_powergate_init() we are declaring
ENABLE_DISP_POWER_GATING_PARAMETERS_V2_1 args;
so that args is basically a 32byte struct. We are passing down
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #5 from Carlo Caione ---
> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.
Yeah, it could be, I'll investigate the
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #4 from Michel Dänzer ---
(In reply to Carlo Caione from comment #3)
> > What kind of artifacts in plymouth?
> https://pasteboard.co/hWu18yPj0.jpg
That could be a plymouth bug. I've noticed that it doesn't seem to call
drmModeCrtcSe
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #3 from Carlo Caione ---
> Looks like amdgpu_atombios_crtc_powergate_init scribbles over the stack.
Yeah, and while this is causing the panic this is not related to the display
corruption.
The garbage lines we see at boot seem to be
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #2 from Michel Dänzer ---
Looks like amdgpu_atombios_crtc_powergate_init scribbles over the stack.
(In reply to Carlo Caione from comment #1)
> If I recompile the kernel forcing CONFIG_CC_STACKPROTECTOR_NONE == none I
> don't
> hav
https://bugs.freedesktop.org/show_bug.cgi?id=101387
Michel Dänzer changed:
What|Removed |Added
Attachment #131890|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=101387
Michel Dänzer changed:
What|Removed |Added
Attachment #131886|text/x-log |text/plain
mime type|
s Chiu; Linux Upstreaming Team
>> Subject: amdgpu display corruption and hang on AMD A10-9620P
>>
>> Hi,
>>
>> We are working with new laptops that have the AMD Bristol Ridge
>> chipset with this SoC:
>>
>> AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G
&
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #1 from Carlo Caione ---
Created attachment 131890
--> https://bugs.freedesktop.org/attachment.cgi?id=131890&action=edit
log no stack protection
Just an update on this. If I recompile the kernel forcing
CONFIG_CC_STACKPROTECTOR_NO
https://bugs.freedesktop.org/show_bug.cgi?id=101387
Bug ID: 101387
Summary: amdgpu display corruption and hang on AMD A10-9620P
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity
> -Original Message-
> From: Daniel Drake [mailto:dr...@endlessm.com]
> Sent: Tuesday, May 09, 2017 12:55 PM
> To: dri-devel; amd-...@lists.freedesktop.org; Deucher, Alexander
> Cc: Chris Chiu; Linux Upstreaming Team
> Subject: amdgpu display corruption and hang on AMD
Hi,
We are working with new laptops that have the AMD Bristol Ridge
chipset with this SoC:
AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G
I think this is the Bristol Ridge chipset.
During boot, the display becomes unusable at the point where the
amdgpu driver loads. You can see at least two ho
33 matches
Mail list logo
