From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: "John Ogness" <john.ogness@linutronix.de>,
"Jon Hunter" <jonathanh@nvidia.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
linux-kernel@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
"Kees Cook" <kees@kernel.org>,
"Stepan Ionichev" <sozdayvek@gmail.com>,
"Xin Zhao" <jackzxcui1989@163.com>,
"Osama Abdelkader" <osama.abdelkader@gmail.com>,
"Fushuai Wang" <wangfushuai@baidu.com>,
"Marco Felsch" <m.felsch@pengutronix.de>,
linux-serial@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH tty v11 1/2] serial: 8250: Switch to nbcon console, take 2
Date: Wed, 26 Aug 2026 09:59:25 +0200 [thread overview]
Message-ID: <20260826075925.WTEVoXWi@linutronix.de> (raw)
In-Reply-To: <ao6XVfmvV6HjBiEv@pathway.suse.cz>
On 2026-08-26 09:35:49 [+0200], Petr Mladek wrote:
> > As for this 8250 "switch to nbcon" series, I am uncertain how to
> > proceed. Is it really printk's job (and, by extension, the console
> > driver's job) to decipher when it is allowed to queue irq_work?
>
> I wonder how other architectures hanle this situation. I wonder
> if they just ignore the pending IRQs.
The interrupts should be disabled and the enqueued irq_work should be
delayed until after the interrupts are enabled again while entering
idle. An interrupt is probably what pulls the CPU out of idle.
Is it possible to get some kind of crash dump or anything else to figure
out the state of CPU while it hangs?
If that irq_work is the problem that making nbcon_irq_work LAZY should
delay it, masking the problem.
Either way, I don't see why raising irq_work should be a problem. That
interrupt has to trigger once interrupts are enabled again. However, if
this is missed then further irq_work enqueues won't trigger an
interrupt which might be a problem if something relies on it.
So the question what is doing while it makes no progress and does not
fully boot.
> Best Regards,
> Petr
Sebastian
next prev parent reply other threads:[~2026-08-26 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260729120439.281252-1-john.ogness@linutronix.de>
[not found] ` <20260729120439.281252-2-john.ogness@linutronix.de>
2026-08-18 6:25 ` [PATCH tty v11 1/2] serial: 8250: Switch to nbcon console, take 2 Jon Hunter
2026-08-18 7:01 ` Sebastian Andrzej Siewior
2026-08-18 7:51 ` Petr Mladek
2026-08-18 12:19 ` Jon Hunter
2026-08-18 15:53 ` Petr Mladek
2026-08-20 9:15 ` Jon Hunter
2026-08-20 12:40 ` John Ogness
2026-08-20 23:37 ` Jon Hunter
2026-08-22 0:32 ` John Ogness
2026-08-24 21:26 ` Jon Hunter
2026-08-25 13:58 ` John Ogness
2026-08-25 15:35 ` Jon Hunter
2026-08-25 22:02 ` John Ogness
2026-08-26 7:35 ` Petr Mladek
2026-08-26 7:59 ` Sebastian Andrzej Siewior [this message]
2026-08-20 11:20 ` John Ogness
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=20260826075925.WTEVoXWi@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hvilleneuve@dimonoff.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jackzxcui1989@163.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=jonathanh@nvidia.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=osama.abdelkader@gmail.com \
--cc=pmladek@suse.com \
--cc=sozdayvek@gmail.com \
--cc=wangfushuai@baidu.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