From: Bert Karwatzki <spasswolf@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm for 6.1-rc1
Date: Fri, 07 Oct 2022 09:23:40 +0200 [thread overview]
Message-ID: <5c0092d617625a2acaf72c1f623b7349a1d666a8.camel@web.de> (raw)
On Thu, Oct 6, 2022 at 3:48 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Thu, Oct 6, 2022 at 12:28 PM Alex Deucher <alexdeucher@gmail.com>
> wrote:
> >
> > Maybe you are seeing this which is an issue with GPU TLB flushe
> > which
> > is kind of sporadic:
> > https://gitlab.freedesktop.org/drm/amd/-/issues/2113
>
> Well, that seems to be 5.19, and while timing changes (or whatever
> other software updates) could have made it start trigger, this
>
> machine
> has been pretty solid otgerwise.
>
> > Are you seeing any GPU page faults in your kernel log?
>
> Nothing even remotely like that "no-retry page fault" in that issue
> report. Of course, if it happens just before the whole thing locks
> up...
There's also this issue with the drm scheduler which causes a lockup
without messages (but with a flashing capslock LED). Going back to
checking the finished fence solves this for me on this device:
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi
23 [Radeon RX 6600/6600 XT/6600M] (rev c3)
https://gitlab.freedesktop.org/drm/amd/-/issues/2179
next reply other threads:[~2022-10-07 7:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 7:23 Bert Karwatzki [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 7:07 [git pull] drm for 6.1-rc1 Bert Karwatzki
2022-10-07 6:52 Bert Karwatzki
2022-10-05 3:41 Dave Airlie
2022-10-05 3:41 ` Dave Airlie
2022-10-05 18:38 ` Linus Torvalds
2022-10-05 18:38 ` Linus Torvalds
2022-10-05 20:56 ` Dave Airlie
2022-10-05 20:56 ` Dave Airlie
2022-10-05 18:40 ` pr-tracker-bot
2022-10-05 18:40 ` pr-tracker-bot
2022-10-06 18:47 ` Linus Torvalds
2022-10-06 18:47 ` Linus Torvalds
2022-10-06 19:28 ` Alex Deucher
2022-10-06 19:28 ` Alex Deucher
2022-10-06 19:47 ` Linus Torvalds
2022-10-06 19:47 ` Linus Torvalds
2022-10-06 20:14 ` Alex Deucher
2022-10-06 20:14 ` Alex Deucher
2022-10-06 20:24 ` Dave Airlie
2022-10-06 20:24 ` Dave Airlie
2022-10-06 21:41 ` Dave Airlie
2022-10-06 21:41 ` Dave Airlie
2022-10-06 21:52 ` Dave Airlie
2022-10-06 21:52 ` Dave Airlie
2022-10-06 23:45 ` Linus Torvalds
2022-10-06 23:45 ` Linus Torvalds
2022-10-07 2:45 ` Dave Airlie
2022-10-07 2:45 ` Dave Airlie
2022-10-07 2:54 ` Dave Airlie
2022-10-07 2:54 ` Dave Airlie
2022-10-07 3:03 ` Dave Airlie
2022-10-07 3:03 ` Dave Airlie
2022-10-07 6:11 ` Christian König
2022-10-07 6:11 ` Christian König
2022-10-07 8:16 ` Daniel Vetter
2022-10-07 8:16 ` Daniel Vetter
2022-10-07 9:28 ` Daniel Vetter
2022-10-07 9:28 ` Daniel Vetter
2022-10-06 19:29 ` Dave Airlie
2022-10-06 19:29 ` Dave Airlie
2022-10-06 19:41 ` Linus Torvalds
2022-10-06 19:41 ` Linus Torvalds
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=5c0092d617625a2acaf72c1f623b7349a1d666a8.camel@web.de \
--to=spasswolf@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.