[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <937e6c6b-7d98-4c9f-b3f7-47e1d6562963@leemhuis.info>
Date: Wed, 29 May 2024 16:04:25 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Genes Lists <lists@...ience.com>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
Adam Williamson <awilliam@...hat.com>, linux-kernel@...r.kernel.org
Cc: jforbes@...hat.com, rstrode@...hat.com
Subject: Re: Intermittent inability to type in graphical Plymouth on UEFI VMs
since kernel 6.9
On 29.05.24 15:35, Genes Lists wrote:
> On Wed, 2024-05-29 at 15:01 +0200, Linux regression tracking (Thorsten
> Leemhuis) wrote:
>>>
>>> cpu i9-12900K / Raptor Lake-P [Iris Xe Graphics]
> Sorry, this should be: 13th Gen Intel(R) Core(TM) i7-1360P
>>>
>>
>> Does this happen every boot or only sometimes? Could you maybe upload
>> the full dmesg from a boot where things worked and one where only the
> For me it is every boot
Ahh, good to know. Would you be able to bisect the problem? That would
help tremendously!
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
> - the first few key strokes are accepted but no
> asterisks are displayed - and it works fine even though fewer asterisks
> are displayed than characters typed.
Strange.
> full dmesg attached.
Do you by chance also have a dmesg at hand for a boot where everything
worked normally?
Adam, do you maybe have dmesg output for the affected cases somewhere?
>> P.S.: let me add this to the regression tracking
>>
>> #regzbot report: /
>> #regzbot introduced: v6.8..v6.9
>> #regzbot summary: Intermittent inability to type in graphical
>> Plymouth
>> on UEFI VMs since kernel 6.9
>
> Thank you.
np; but without a bisecting or at least locating the subsystem that is
causing this we might not get any further. :-/
Ciao, Thorsten
Powered by blists - more mailing lists