[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 2 Feb 2024 07:58:06 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: John Ogness <john.ogness@...utronix.de>
Cc: Tejun Heo <tj@...nel.org>, Lai Jiangshan <jiangshanlai@...il.com>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel@...r.kernel.org, rcu@...r.kernel.org
Subject: Re: [BUG] workqueues and printk not playing nice since next-20240130
On Fri, Feb 02, 2024 at 03:18:48PM +0106, John Ogness wrote:
> On 2024-02-02, "Paul E. McKenney" <paulmck@...nel.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
This says no such command even though I do have CONFIG_GDB_SCRIPTS=y
in my .config.
> As an alternative, you could copy the contents of
> Documentation/admin-guide/kdump/gdbmacros.txt into your .gdbinit and
> then will have:
>
> (gdb) dmesg
This one hangs.
> There may be some hints in the kernel log as to why there is no console
> output.
On the other hand, next-20240202 doesn't show the problem. No idea
what might have changed. :-/
Thanx, Paul
Powered by blists - more mailing lists