From: John Ogness <john.ogness@linutronix.de>
To: paulmck@kernel.org, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [BUG] workqueues and printk not playing nice since next-20240130
Date: Fri, 02 Feb 2024 15:18:48 +0106 [thread overview]
Message-ID: <87le83ara7.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <410d6a87-bf34-457e-b714-1e6149d48532@paulmck-laptop>
On 2024-02-02, "Paul E. McKenney" <paulmck@kernel.org> wrote:
> So the system really did boot and is running just fine. It is just that
> there is no console output. Details, details!
>
> Is there anything I can do to some combination of workqueues and printk
> to help debug this?
The printk ringbuffer contents would certainly be interesting.
If you build the GDB scripts (CONFIG_GDB_SCRIPTS) then you will have:
(gdb) lx-dmesg
As an alternative, you could copy the contents of
Documentation/admin-guide/kdump/gdbmacros.txt into your .gdbinit and
then will have:
(gdb) dmesg
There may be some hints in the kernel log as to why there is no console
output.
John
next prev parent reply other threads:[~2024-02-02 14:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:04 [BUG] workqueues and printk not playing nice since next-20240130 Paul E. McKenney
2024-02-02 14:12 ` John Ogness [this message]
2024-02-02 15:58 ` Paul E. McKenney
2024-02-02 17:02 ` John Ogness
2024-02-02 17:35 ` Paul E. McKenney
2024-02-02 14:26 ` Jonas Oberhauser
2024-02-02 16:35 ` Paul E. McKenney
2024-02-02 16:56 ` Tejun Heo
2024-02-02 17:40 ` Paul E. McKenney
2024-02-05 13:07 ` Petr Mladek
2024-02-05 13:25 ` Sergey Senozhatsky
2024-02-05 17:45 ` Paul E. McKenney
2024-02-05 17:46 ` Tejun Heo
2024-02-05 19:41 ` Paul E. McKenney
2024-02-05 20:30 ` Tejun Heo
2024-02-05 21:17 ` Paul E. McKenney
2024-02-02 14:35 ` Petr Mladek
2024-02-02 16:07 ` Paul E. McKenney
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=87le83ara7.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.