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>,
"amd-gfx mailing list" <amd-gfx@lists.freedesktop.org>
Subject: Re: "firmware/sysfb: Set firmware-framebuffer parent device" breaks lightdm on Ubuntu 22.04 using amdgpu
Date: Thu, 13 Jun 2024 09:23:53 +0200 [thread overview]
Message-ID: <eb8223e2-9bea-416d-a412-0a291523a0ff@suse.de> (raw)
In-Reply-To: <CAAxE2A6971oJ3r-8UWhL0BUZBiYxq4K0-Q39MJnb7ZozX3da-A@mail.gmail.com>
Hi
Am 13.06.24 um 08:00 schrieb Marek Olšák:
> +amd-gfx
>
> On Thu, Jun 13, 2024 at 1:59 AM Marek Olšák <maraeo@gmail.com> wrote:
>> 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.
>>
>> Reverting the commit fixes lightdm. A workaround is to bypass lightdm
>> by triggering auto-login. This is a bug report.
I see. Do you know why it crashes? Or have any logs.
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)
next prev parent reply other threads:[~2024-06-13 7:23 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 [this message]
2024-06-13 14:20 ` Marek Olšák
2024-06-13 14:59 ` Thomas Zimmermann
2024-06-19 13:50 ` Thomas Zimmermann
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=eb8223e2-9bea-416d-a412-0a291523a0ff@suse.de \
--to=tzimmermann@suse.de \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox