From: "Linux kernel regression tracking (#adding)" <regressions@leemhuis.info>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-efi@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Is there a known boot failure with 6.2-rc and the Intel SDV EFI systems?
Date: Sat, 21 Jan 2023 14:20:22 +0100 [thread overview]
Message-ID: <0eabbe98-db6e-b5db-ca5b-3f212bf2f734@leemhuis.info> (raw)
In-Reply-To: <f2503170d12dc567c00998d4e72ba806f7677730.camel@HansenPartnership.com>
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]
On 20.01.23 00:13, James Bottomley wrote:
> I've got a Rainbow Bridge SDV I mostly use for TPM work, and I haven't
> updated it in a while. Today I found that the recent 6.2-rc4 kernel
> won't boot and won't emit any kernel messages signalling a failure
> somewhere in the handoff code. I did put some EFI boot stub prints in
> and verified it gets all the way to exit_boot_services before the
> problem, so it smells like it fails initializing the EFI console for
> runtime. I've also verified that v6.1 release works just fine, so it
> looks like something that went into EFI in the recent merge window.
> I'm starting to bisect now, but thought I'd ask in case anyone else has
> already debugged this.
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:
#regzbot ^introduced v6.1..v6.2-rc4
#regzbot title boot failure with 6.2 on Intel SDV EFI systems
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.
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
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-01-21 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 23:13 Is there a known boot failure with 6.2-rc and the Intel SDV EFI systems? James Bottomley
2023-01-20 9:03 ` Ard Biesheuvel
2023-01-21 13:20 ` Linux kernel regression tracking (#adding) [this message]
2023-01-21 13:23 ` James Bottomley
2023-01-21 14:04 ` Linux kernel regression tracking (#update)
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=0eabbe98-db6e-b5db-ca5b-3f212bf2f734@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-efi@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).