From: Peter Geis <pgwipeout@gmail.com> To: Petr Mladek <pmladek@suse.com> Cc: John Ogness <john.ogness@linutronix.de>, 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: Mon, 13 Jun 2022 18:20:03 -0400 [thread overview] Message-ID: <CAMdYzYr-oHp-EgNJxumsR+DrZS=U7dLpvHymkAHPYQO8FsrLrQ@mail.gmail.com> (raw) In-Reply-To: <YqdTsjRQiJUilSg6@alley> On Mon, Jun 13, 2022 at 11:11 AM Petr Mladek <pmladek@suse.com> wrote: > > On Mon 2022-06-13 04:29:50, John Ogness wrote: > > On 2022-06-12, Peter Geis <pgwipeout@gmail.com> wrote: > > > The buffer isn't an issue here, everything is available in dmesg when > > > userspace becomes available. Instead some messages bound for the > > > serial console are never output. > > > > OK. Good to know. > > > > > We run a serial console at 1.5m baud which is significantly higher > > > than most SoCs which default to 115200. I have noticed some timing > > > differences since the introduction of the threaded console. A > > > significant amount of information is dumped very early in the boot > > > process (between 0 and 4 seconds into boot), as most drivers are > > > probing during this time. It also happens to be when the earlycon > > > console hands over to the normal console. There is no abnormal > > > debugging enabled, the output is a standard (non-quiet) boot log. The > > > question is why is direct mode not triggering during a panic? > > > > Just to be clear, you are not losing any intermediate messages. Only the > > tail end of the kernel log was never printed. Is this correct? > > > > This may be the same issue being discussed here [0]. > > > > John Ogness > > > > [0] https://lore.kernel.org/all/87v8t5l39z.fsf@jogness.linutronix.de > > If the last messages are missing then it is most likely the same > issue. > > Peter, could you please try if the patch at > https://lore.kernel.org/r/YqdSw/fJvnkRbjvc@alley > would make any difference? This patch permits the panic to come through to the console port. Thank you! Tested-by: Peter Geis <pgwipeout@gmail.com> > > Best Regards, > Petr
WARNING: multiple messages have this Message-ID (diff)
From: Peter Geis <pgwipeout@gmail.com> To: Petr Mladek <pmladek@suse.com> Cc: John Ogness <john.ogness@linutronix.de>, 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: Mon, 13 Jun 2022 18:20:03 -0400 [thread overview] Message-ID: <CAMdYzYr-oHp-EgNJxumsR+DrZS=U7dLpvHymkAHPYQO8FsrLrQ@mail.gmail.com> (raw) In-Reply-To: <YqdTsjRQiJUilSg6@alley> On Mon, Jun 13, 2022 at 11:11 AM Petr Mladek <pmladek@suse.com> wrote: > > On Mon 2022-06-13 04:29:50, John Ogness wrote: > > On 2022-06-12, Peter Geis <pgwipeout@gmail.com> wrote: > > > The buffer isn't an issue here, everything is available in dmesg when > > > userspace becomes available. Instead some messages bound for the > > > serial console are never output. > > > > OK. Good to know. > > > > > We run a serial console at 1.5m baud which is significantly higher > > > than most SoCs which default to 115200. I have noticed some timing > > > differences since the introduction of the threaded console. A > > > significant amount of information is dumped very early in the boot > > > process (between 0 and 4 seconds into boot), as most drivers are > > > probing during this time. It also happens to be when the earlycon > > > console hands over to the normal console. There is no abnormal > > > debugging enabled, the output is a standard (non-quiet) boot log. The > > > question is why is direct mode not triggering during a panic? > > > > Just to be clear, you are not losing any intermediate messages. Only the > > tail end of the kernel log was never printed. Is this correct? > > > > This may be the same issue being discussed here [0]. > > > > John Ogness > > > > [0] https://lore.kernel.org/all/87v8t5l39z.fsf@jogness.linutronix.de > > If the last messages are missing then it is most likely the same > issue. > > Peter, could you please try if the patch at > https://lore.kernel.org/r/YqdSw/fJvnkRbjvc@alley > would make any difference? This patch permits the panic to come through to the console port. Thank you! Tested-by: Peter Geis <pgwipeout@gmail.com> > > Best Regards, > Petr _______________________________________________ Linux-rockchip mailing list Linux-rockchip@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-06-13 22:20 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 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 [this message] 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='CAMdYzYr-oHp-EgNJxumsR+DrZS=U7dLpvHymkAHPYQO8FsrLrQ@mail.gmail.com' \ --to=pgwipeout@gmail.com \ --cc=john.ogness@linutronix.de \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=pmladek@suse.com \ --cc=senozhatsky@chromium.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: linkBe 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.