All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: John Ogness <john.ogness@linutronix.de>,
	Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>
Subject: Re: [BUG] Threaded printk breaks early debugging
Date: Sun, 12 Jun 2022 11:57:51 +0900	[thread overview]
Message-ID: <YqVWL3gpfV9HJBLe@google.com> (raw)
In-Reply-To: <CAMdYzYr-Wo713Y4qjboTpoK6GcrYfKCfRJAEizwXw6-=dymVzg@mail.gmail.com>

On (22/06/10 11:34), Peter Geis wrote:
> > On 2022-06-10, Peter Geis <pgwipeout@gmail.com> wrote:
> > > However I've run into an issue debugging early boot issues. Anything
> > > that causes the kernel threading system to die (for example here, a
> > > NPE) causes the boot console to halt before it outputs the error.
> >
> > A null pointer exception should trigger a panic, which will cause printk
> > to enter direct mode for the oops. It should be just as effective as
> > before introducing the printing kthreads.
> 
> This might be a side effect of the fact that this is on a low powered
> arm64 board. I noticed with threading enabled during large bursts the
> console drops an excessive amount of messages. It's especially
> apparent during the handover from earlycon to the normal console.

How many CPUs does it have?

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: John Ogness <john.ogness@linutronix.de>,
	Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>
Subject: Re: [BUG] Threaded printk breaks early debugging
Date: Sun, 12 Jun 2022 11:57:51 +0900	[thread overview]
Message-ID: <YqVWL3gpfV9HJBLe@google.com> (raw)
In-Reply-To: <CAMdYzYr-Wo713Y4qjboTpoK6GcrYfKCfRJAEizwXw6-=dymVzg@mail.gmail.com>

On (22/06/10 11:34), Peter Geis wrote:
> > On 2022-06-10, Peter Geis <pgwipeout@gmail.com> wrote:
> > > However I've run into an issue debugging early boot issues. Anything
> > > that causes the kernel threading system to die (for example here, a
> > > NPE) causes the boot console to halt before it outputs the error.
> >
> > A null pointer exception should trigger a panic, which will cause printk
> > to enter direct mode for the oops. It should be just as effective as
> > before introducing the printing kthreads.
> 
> This might be a side effect of the fact that this is on a low powered
> arm64 board. I noticed with threading enabled during large bursts the
> console drops an excessive amount of messages. It's especially
> apparent during the handover from earlycon to the normal console.

How many CPUs does it have?

  reply	other threads:[~2022-06-12  2:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 12:48 [BUG] Threaded printk breaks early debugging Peter Geis
2022-06-10 12:48 ` Peter Geis
2022-06-10 15:05 ` John Ogness
2022-06-10 15:05   ` John Ogness
2022-06-10 15:34   ` Peter Geis
2022-06-10 15:34     ` Peter Geis
2022-06-12  2:57     ` Sergey Senozhatsky [this message]
2022-06-12  2:57       ` Sergey Senozhatsky
2022-06-12 13:30       ` Peter Geis
2022-06-12 13:30         ` Peter Geis
2022-06-12 23:08     ` John Ogness
2022-06-12 23:08       ` John Ogness
2022-06-12 23:30       ` Peter Geis
2022-06-12 23:30         ` Peter Geis
2022-06-13  2:23         ` John Ogness
2022-06-13  2:23           ` John Ogness
2022-06-13 15:11           ` Petr Mladek
2022-06-13 15:11             ` Petr Mladek
2022-06-13 22:20             ` Peter Geis
2022-06-13 22:20               ` Peter Geis
2022-06-14  8:38               ` Petr Mladek
2022-06-14  8:38                 ` Petr Mladek
2022-06-13 11:24         ` Petr Mladek
2022-06-13 11:24           ` Petr Mladek
2022-06-12  3:13   ` Sergey Senozhatsky
2022-06-12  3:13     ` Sergey Senozhatsky
2022-06-12 23:02     ` John Ogness
2022-06-12 23:02       ` John Ogness
2022-06-13  3:49       ` Sergey Senozhatsky
2022-06-13  3:49         ` Sergey Senozhatsky
2022-06-13  8:30         ` John Ogness
2022-06-13  8:30           ` John Ogness
2022-06-13  9:05           ` Sergey Senozhatsky
2022-06-13  9:05             ` Sergey Senozhatsky
2022-06-13 10:14             ` Petr Mladek
2022-06-13 10:14               ` Petr Mladek
2022-06-13 16:11               ` David Laight
2022-06-13 16:11                 ` David Laight
2022-06-14  8:37                 ` Petr Mladek
2022-06-14  8:37                   ` Petr Mladek

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=YqVWL3gpfV9HJBLe@google.com \
    --to=senozhatsky@chromium.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pgwipeout@gmail.com \
    --cc=pmladek@suse.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 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.