linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Vlastimil Babka <vbabka@suse.cz>, Donald Carr <sirspudd@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	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>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Subject: Re: [git pull] drm for 6.8
Date: Wed, 24 Jan 2024 10:41:49 -0600	[thread overview]
Message-ID: <a51ddb8c-cf11-4394-a2fe-ca855749ff02@amd.com> (raw)
In-Reply-To: <0a782904-bb19-4111-979a-31b52aa44ca9@suse.cz>

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've bisected the merge commits so far and now will try to dig into this
>>> one. I've noticed there was also a drm fixes PR later in the merge window but
>>> since it was also merged into rc1 and thus didn't prevent the issue for me,
>>> I guess it's not relevant here?
>>>
>>> Because the reproduction wasn't very deterministic I considered a commit bad
>>> even if it didn't lead to completely frozen desktop and a forced reboot.
>>> Even the multi-second hangs that resolved were a regression compared to 6.7
>>> anyway.
>>>
>>> If there are known issues and perhaps candidate fixes already, please do tell.
>>
>> I am experiencing the exact same symptoms; sddm (on weston) starts
>> perfectly, launching a KDE wayland session freezes at various points
>> (leading to plenty of premature celebration), but normally on the
>> handoff from sddm to kde (replete with terminal cursor on screen)
>>
>> Working perfectly as of the end of 6.7 final release, broken as of 6.8 rc1.
>> Sometimes sddm can be successfully restarted via ssh, other times
>> restarting sddm is slow and fails to complete.
> 
> 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.

> 
> Vlastimil
> 
>> Yours sincerely,
>> Donald
> 


  reply	other threads:[~2024-01-24 16:41 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 [this message]
2024-01-24 17:51         ` Thorsten Leemhuis
2024-01-24 17:52           ` Mario Limonciello
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=a51ddb8c-cf11-4394-a2fe-ca855749ff02@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).