linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Richard Gong" <richard.gong@amd.com>,
	"Dave Airlie" <airlied@linux.ie>,
	"Xinhui Pan" <xinhui.pan@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	amd-gfx@lists.freedesktop.org,
	"Alexander Deucher" <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org,
	"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: Tue, 3 May 2022 13:25:53 +0100	[thread overview]
Message-ID: <CAPj87rOERk-kNa6n-UdjQsDKXP9zzm8=an=FHcM+33yebW6ECw@mail.gmail.com> (raw)
In-Reply-To: <543a9e76-ca90-984b-b155-a0647cdeacff@molgen.mpg.de>

On Sun, 1 May 2022 at 08:08, Paul Menzel <pmenzel@molgen.mpg.de> wrote:
> Am 26.04.22 um 15:53 schrieb Gong, Richard:
> > I think so. We captured dmesg log.
>
> 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 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?

This has gone beyond the point of a reasonable request. The amount of
detail you're demanding is completely unnecessary.

  parent reply	other threads:[~2022-05-03 12:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 21:50 [PATCHv4] drm/amdgpu: disable ASPM on Intel Alder Lake based systems 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
2022-05-03 12:25                   ` Daniel Stone [this message]
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='CAPj87rOERk-kNa6n-UdjQsDKXP9zzm8=an=FHcM+33yebW6ECw@mail.gmail.com' \
    --to=daniel@fooishbar.org \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=richard.gong@amd.com \
    --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;
as well as URLs for NNTP newsgroup(s).