From: Mario Limonciello <mario.limonciello@amd.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
Donald Carr <sirspudd@gmail.com>
Subject: Re: [git pull] drm for 6.8
Date: Wed, 24 Jan 2024 11:52:27 -0600 [thread overview]
Message-ID: <05ddb2da-b182-4791-8ef7-82179fd159a8@amd.com> (raw)
In-Reply-To: <e7eb12a9-67ed-45b1-aaf6-e1df52a247bd@leemhuis.info>
On 1/24/2024 11:51, Thorsten Leemhuis wrote:
> Linus, if you have a minute, I'd really like to know...
>
> On 24.01.24 17:41, Mario Limonciello wrote:
>> On 1/24/2024 10:24, Vlastimil Babka wrote:
>>> On 1/24/24 16:31, Donald Carr wrote:
>>>> On Wed, Jan 24, 2024 at 7:06 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>>>>> When testing the rc1 on my openSUSE Tumbleweed desktop, I've started
>>>>> experiencing "frozen desktop" (KDE/Wayland) issues. The symptoms are
>>>>> that
>>>>> everything freezes including mouse cursor. After a while it either
>>>>> resolves,
>>>>> or e.g. firefox crashes (if it was actively used when it froze) or it's
>>>>> frozen for too long and I reboot with alt-sysrq-b. When it's frozen
>>>>> I can
>>>>> still ssh to the machine, and there's nothing happening in dmesg.
>>>>> The machine is based on Amd Ryzen 7 2700 and Radeon RX7600.
>>>> [...]
>>>> I am experiencing the exact same symptoms;
>>>
>>> Big thanks to Thorsten who suggested I look at the following:
>>>
>>> https://lore.kernel.org/all/20240123021155.2775-1-mario.limonciello@amd.com/
>>> https://lore.kernel.org/all/CABXGCsM2VLs489CH-vF-1539-s3in37=bwuOWtoeeE+q26zE+Q@mail.gmail.com/
>>>
>>> Instead of further bisection I've applied Mario's revert from the
>>> first link
>>> on top of 6.8-rc1 and the issue seems gone for me now.
>>
>> Thanks for confirming. I don't think we should jump right to the revert
>> right now.
>>
>> I posted it in case that is the direction we need to go
>> (simple git revert didn't work due to contextual changes).
>>
>> Let's give the folks who work on GPU scheduler some time to understand
>> the failure and see if they can fix it.
>
> ...how you think about this and other situations like this. Given that
> we have
>
> * two affected people in this thread
> * one earlier thread about it
> * the machine that made Mario write the patch
> * and I have someone in #fedora-kernel that likely is affected as well
>
> it seems that this is not some corner case very few people run into.
> Hence I tend to say that this should be dealt with rather sooner than
> later. Maybe before rc2? Or is this asking too much?
>
> The thing from my point of view is, that each such problem might
> discourage testers from testing again or lead to thoughts like "I only
> start testing after -rc4". Not to mention that other people will try to
> bisect the problem like Vlastimil did, which will cost them quite some
> time and effort -- only to find out that we known about the problem
> already and did not quickly fix it. That is discouraging for them as
> well and thus bad for field testing I'd assume.
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
A test patch was just posted. I haven't gotten a chance to try it yet.
I will this afternoon.
next prev parent reply other threads:[~2024-01-24 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 19:49 [git pull] drm for 6.8 Dave Airlie
2024-01-12 19:33 ` Linus Torvalds
2024-01-14 20:00 ` Dave Airlie
2024-01-12 19:40 ` pr-tracker-bot
2024-01-24 15:01 ` Vlastimil Babka
2024-01-24 15:31 ` Donald Carr
2024-01-24 15:33 ` Donald Carr
2024-01-24 16:24 ` Vlastimil Babka
2024-01-24 16:41 ` Mario Limonciello
2024-01-24 17:51 ` Thorsten Leemhuis
2024-01-24 17:52 ` Mario Limonciello [this message]
2024-01-24 18:23 ` Mario Limonciello
2024-01-25 17:23 ` Donald Carr
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=05ddb2da-b182-4791-8ef7-82179fd159a8@amd.com \
--to=mario.limonciello@amd.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sirspudd@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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).