From: Christoph Hellwig <hch@lst.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, stable@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
christian.koenig@amd.com
Subject: Re: [PATCH v2] Revert "drm/radeon: handle PCIe root ports with addressing limitations"
Date: Wed, 16 Sep 2020 16:36:28 +0200 [thread overview]
Message-ID: <20200916143628.GA6894@lst.de> (raw)
In-Reply-To: <20200916132017.1221927-1-alexander.deucher@amd.com>
On Wed, Sep 16, 2020 at 09:20:17AM -0400, Alex Deucher wrote:
> This causes screen corruption when using the GPU which makes the
> system unusable.
You have not addressed any of my questions, especially if the commit
that fixed one of the reports (the only one with a recent kernel)
fixed most of the others as well. Nor that fact that the crash
one really looks like the symptom of an underlying issue that absolutely
needs to be fixed first.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
stable@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
christian.koenig@amd.com
Subject: Re: [PATCH v2] Revert "drm/radeon: handle PCIe root ports with addressing limitations"
Date: Wed, 16 Sep 2020 16:36:28 +0200 [thread overview]
Message-ID: <20200916143628.GA6894@lst.de> (raw)
In-Reply-To: <20200916132017.1221927-1-alexander.deucher@amd.com>
On Wed, Sep 16, 2020 at 09:20:17AM -0400, Alex Deucher wrote:
> This causes screen corruption when using the GPU which makes the
> system unusable.
You have not addressed any of my questions, especially if the commit
that fixed one of the reports (the only one with a recent kernel)
fixed most of the others as well. Nor that fact that the crash
one really looks like the symptom of an underlying issue that absolutely
needs to be fixed first.
next prev parent reply other threads:[~2020-09-16 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:20 [PATCH v2] Revert "drm/radeon: handle PCIe root ports with addressing limitations" Alex Deucher
2020-09-16 13:20 ` Alex Deucher
2020-09-16 13:20 ` Alex Deucher
2020-09-16 14:36 ` Christoph Hellwig [this message]
2020-09-16 14:36 ` Christoph Hellwig
2020-09-21 12:55 ` Sasha Levin
2020-09-21 12:55 ` Sasha Levin
2020-09-21 12:55 ` Sasha Levin
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=20200916143628.GA6894@lst.de \
--to=hch@lst.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.