From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Conor Dooley <conor@kernel.org>
Cc: pmladek@suse.com, senozhatsky@chromium.org, rostedt@goodmis.org,
john.ogness@linutronix.de, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [resend][bug] low-probability console lockups since 5.19
Date: Thu, 29 Sep 2022 11:06:01 +0200 [thread overview]
Message-ID: <98f62903-3d6f-30b4-82ef-3b0460824907@leemhuis.info> (raw)
In-Reply-To: <YzR8fzyjhggO+/tT@spud>
Hi Conor
On 28.09.22 18:55, Conor Dooley wrote:
> On Fri, Sep 23, 2022 at 05:24:17PM +0100, Conor Dooley wrote:
>>
>> Been bisecting a bug that is causing a boot failure in my CI & have
>> ended up here.. The bug in question is a low(ish) probability lock up
>> of the serial console, I would estimate about 1-in-5 chance on the
>> boards I could actually trigger it on which it has taken me so long
>> to realise that this was an actual problem. Thinking back on it, there
>> were other failures that I would retroactively attribute to this
>> problem too, but I had earlycon disabled
> [...]
> #regzbot introduced: 5831788afb17b89c5b531fb60cbd798613ccbb63 ^
> Hopefully I did this correctly...
Yes, you did, thx for this. I already had been watching this thread
manually and was a bit unsure what to do with it.
> I picked that commit as that's where things start going haywire.
There is one thing I wonder when skimming this thread: was there maybe
some other change somewhere in the kernel between the introduction and
the revert of the printk console kthreads patches that is the real
culprit here that makes existing, older races easier to hit? But I guess
in the end that would be very hard to find and it's easier to fix the
problem in the console driver... :-/
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
#regzbot backburner: tricky situation that might take some time to get
resolved
next prev parent reply other threads:[~2022-09-29 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 16:24 [resend][bug] low-probability console lockups since 5.19 Conor Dooley
2022-09-26 10:32 ` Petr Mladek
2022-09-26 13:07 ` Conor Dooley
2022-09-28 16:55 ` Conor Dooley
2022-09-29 9:06 ` Thorsten Leemhuis [this message]
2022-09-29 9:29 ` Conor Dooley
2022-09-29 10:12 ` Petr Mladek
2022-09-29 10:52 ` Conor Dooley
2022-09-29 14:13 ` John Ogness
2022-09-29 21:22 ` Conor Dooley
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=98f62903-3d6f-30b4-82ef-3b0460824907@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=conor@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
/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).