From: "Gong, Richard" <richard.gong@amd.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Dave Airlie" <airlied@linux.ie>,
"Xinhui Pan" <xinhui.pan@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
"Alex Deucher" <alexdeucher@gmail.com>,
amd-gfx@lists.freedesktop.org, "Daniel Vetter" <daniel@ffwll.ch>,
"Alexander Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: Re: [PATCHv4] drm/amdgpu: disable ASPM on Intel Alder Lake based systems
Date: Mon, 2 May 2022 09:56:25 -0500 [thread overview]
Message-ID: <6977b3d5-0aa8-3d57-c9ad-0742bdd3dc8f@amd.com> (raw)
In-Reply-To: <543a9e76-ca90-984b-b155-a0647cdeacff@molgen.mpg.de>
Hi Paul,
On 5/1/2022 2:08 AM, Paul Menzel wrote:
> Dear Richard,
>
>
> Sorry for the late reply.
>
> Am 26.04.22 um 15:53 schrieb Gong, Richard:
>
>> On 4/21/2022 12:35 AM, Paul Menzel wrote:
>
>>> Am 21.04.22 um 03:12 schrieb Gong, Richard:
>>>
>>>> On 4/20/2022 3:29 PM, Paul Menzel wrote:
>>>
>>>>> Am 19.04.22 um 23:46 schrieb Gong, Richard:
>>>>>
>>>>>> On 4/14/2022 2:52 AM, Paul Menzel wrote:
>>>>>>> [Cc: -kernel test robot <lkp@intel.com>]
>>>>>
>>>>> […]
>>>>>
>>>>>>> Am 13.04.22 um 15:00 schrieb Alex Deucher:
>>>>>>>> On Wed, Apr 13, 2022 at 3:43 AM Paul Menzel wrote:
>>>>>>>
>>>>>>>>> Thank you for sending out v4.
>>>>>>>>>
>>>>>>>>> Am 12.04.22 um 23:50 schrieb Richard Gong:
>
> […]
>
>>>>>>>>> I am still not clear, what “hang during suspend/resume” means.
>>>>>>>>> I guess
>>>>>>>>> suspending works fine? During resume (S3 or S0ix?), where does
>>>>>>>>> it hang?
>>>>>>>>> The system is functional, but there are only display problems?
>>>>>> System freeze after suspend/resume.
>>>>>
>>>>> But you see certain messages still? At what point does it freeze
>>>>> exactly? In the bug report you posted Linux messages.
>>>>
>>>> No, the system freeze then users have to recycle power to recover.
>>>
>>> Then I misread the issue? Did you capture the messages over serial
>>> log then?
>>
>> I think so. We captured dmesg log.
make a correction, the previous 'dmesg log' description was not accurate.
I referred that to the kernel log captured via 'journalctl' after
recycling the power. I should use kernel log rather than 'dmesg log' to
avoid the confusion.
>
> Then the (whole) system did *not* freeze, if you could still log in
> (maybe over network) and execute `dmesg`. Please also paste the
> amdgpu(?) error logs in the commit message.
As mentioned in my "previous previous" reply, the user have to recycle
power to reset the system.
When issue occurred, keyboard/mouse didn't work. 'demsg' and ssh didn't
work either.
>
>> As mentioned early we need support from Intel on how to get ASPM
>> working for VI generation on Intel Alder Lake, but we don't know
>> where things currently stand.
>
> Who is working on this, and knows?
I have no idea.
>
> Kind regards,
>
> Paul
Regards,
Richard
next prev parent reply other threads:[~2022-05-02 14:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 21:50 Richard Gong
2022-04-13 4:29 ` Lazar, Lijo
2022-04-13 7:43 ` Paul Menzel
2022-04-13 13:00 ` Alex Deucher
2022-04-13 13:28 ` Limonciello, Mario
2022-04-14 7:52 ` Paul Menzel
2022-04-14 13:11 ` Alex Deucher
[not found] ` <94fd858d-1792-9c05-b5c6-1b028427687d@amd.com>
2022-04-20 20:29 ` Paul Menzel
2022-04-20 20:40 ` Alex Deucher
2022-04-20 20:48 ` Paul Menzel
2022-04-20 20:56 ` Gong, Richard
2022-04-20 21:02 ` Paul Menzel
2022-04-20 21:12 ` Gong, Richard
2022-04-20 21:15 ` Alex Deucher
2022-04-20 21:13 ` Alex Deucher
2022-04-20 21:16 ` Limonciello, Mario
2022-04-21 1:12 ` Gong, Richard
2022-04-21 5:35 ` Paul Menzel
2022-04-26 13:53 ` Gong, Richard
2022-05-01 7:08 ` Paul Menzel
2022-05-02 14:56 ` Gong, Richard [this message]
2022-05-03 12:25 ` Daniel Stone
2022-05-03 12:44 ` Paul Menzel
2022-04-13 15:40 ` Nathan Chancellor
2022-04-19 21:08 ` Gong, Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6977b3d5-0aa8-3d57-c9ad-0742bdd3dc8f@amd.com \
--to=richard.gong@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pmenzel@molgen.mpg.de \
--cc=xinhui.pan@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®