linux-kernel - Re: [BUG] workqueues and printk not playing nice since next-20240130

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 02 Feb 2024 15:18:48 +0106
From: John Ogness <john.ogness@...utronix.de>
To: paulmck@...nel.org, 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>
Cc: 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 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

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