All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Marek Olšák" <maraeo@gmail.com>,
	javierm@redhat.com, pjones@redhat.com, deller@gmx.de,
	ardb@kernel.org, dri-devel <dri-devel@lists.freedesktop.org>,
	linux-fbdev@vger.kernel.org, "Deucher,
	Alexander" <Alexander.Deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: "firmware/sysfb: Set firmware-framebuffer parent device" breaks lightdm on Ubuntu 22.04 using amdgpu
Date: Wed, 19 Jun 2024 15:50:18 +0200	[thread overview]
Message-ID: <5f4c828c-8564-4e4e-a418-3250fadb660a@suse.de> (raw)
In-Reply-To: <CAAxE2A7qK1-b5g1RR-GJ+QTLEr_OxEr9vcZGEOkZY9yLOFLb5w@mail.gmail.com>

Hi

Am 13.06.24 um 07:59 schrieb Marek Olšák:
> Hi Thomas,
>
> Commit 9eac534db0013aff9b9124985dab114600df9081 as per the title
> breaks (crashes?) lightdm (login screen) such that all I get is the
> terminal. It's also reproducible with tag v6.9 where the commit is
> present.

I was able to reproduce the problem with Ubutu 22.04 and later under 
qemu plus qxl, sort of. I login via gdm3 and then the quest machine 
switches off entirely.

>
> Reverting the commit fixes lightdm. A workaround is to bypass lightdm
> by triggering auto-login. This is a bug report.

The problem is that reverting the commit doesn't fix the issue for me. 
I'll try to do my own bisecting.

Best regards
Thomas

>
> (For AMD folks: It's also reproducible with amd-staging-drm-next.)
>
> Marek

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  parent reply	other threads:[~2024-06-19 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  5:59 "firmware/sysfb: Set firmware-framebuffer parent device" breaks lightdm on Ubuntu 22.04 using amdgpu Marek Olšák
2024-06-13  6:00 ` Marek Olšák
2024-06-13  7:23   ` Thomas Zimmermann
2024-06-13 14:20     ` Marek Olšák
2024-06-13 14:59       ` Thomas Zimmermann
2024-06-19 13:50 ` Thomas Zimmermann [this message]
2024-06-19 18:40   ` Marek Olšák
2024-06-20  6:40     ` Thomas Zimmermann
2024-06-21  9:50 ` Thomas Zimmermann

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=5f4c828c-8564-4e4e-a418-3250fadb660a@suse.de \
    --to=tzimmermann@suse.de \
    --cc=Alexander.Deucher@amd.com \
    --cc=ardb@kernel.org \
    --cc=christian.koenig@amd.com \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=maraeo@gmail.com \
    --cc=pjones@redhat.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 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.