From: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pmladek@suse.com" <pmladek@suse.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"senozhatsky@chromium.org" <senozhatsky@chromium.org>
Subject: Re: [PATCH 0/1] printk: Yield console_sem to blocking waiters
Date: Fri, 11 Sep 2026 18:25:08 +0000 [thread overview]
Message-ID: <44239E18-2EE0-4451-9481-EC4283473AF0@oracle.com> (raw)
In-Reply-To: <87zexocir6.fsf@jogness.linutronix.de>
> On Sep 11, 2026, at 1:08 AM, John Ogness <john.ogness@linutronix.de> wrote:
>
> This Message Is From an External Sender
> This message came from outside your organization.
> Report Suspicious
> On 2026-09-10, Aruna Ramakrishna <aruna.ramakrishna@oracle.com> wrote:
> > Problem context:
> >
> > After a reboot, NetworkManager failed to bring up interfaces because
> > systemd was stalled, due to a flood of printk warnings.
>
> Note that kernel warnings are considered serious and will put the CPU
> into emergency state.
I apologize - I misspoke. These were not KERN_WARNs, rather KERN_INFOs
being used by RDS to warn of connection failures etc. A flood of these caused
the console_lock starvation.
>
> > Systemd was
> > blocked waiting on the console lock for over 122 seconds:
>
> Also note that the console lock is related to legacy consoles. Rather
> than trying to make the legacy console trainwreck more reliable and
> non-interfering, efforts should be spent converting legacy consoles to
> NBCON.
>
> What console driver are you using?
>
> For v7.3 the 8250 driver will be NBCON.
>
> John
>
This is for the legacy 8250 serial console.
Thanks,
Aruna
prev parent reply other threads:[~2026-09-11 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:33 Aruna Ramakrishna
2026-09-10 20:33 ` [PATCH 1/1] " Aruna Ramakrishna
2026-09-11 8:08 ` [PATCH 0/1] " John Ogness
2026-09-11 18:25 ` Aruna Ramakrishna [this message]
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=44239E18-2EE0-4451-9481-EC4283473AF0@oracle.com \
--to=aruna.ramakrishna@oracle.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--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
all inboxes | Powered by JetHome®