From: Nir Lichtman <nir@lichtman.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: add boot param to disable stack dump on panic
Date: Thu, 8 Feb 2024 08:14:25 +0000 [thread overview]
Message-ID: <20240208081425.GA1511946@lichtman.org> (raw)
In-Reply-To: <ZcLmjrBxE2BA_hLG@archie.me>
In a lot of cases when there is a kernel panic it obscures on the display the previous problem that caused it and the main
reason is that the call stack prints a lot of lines on the display - and there is no way to scroll back up.
What led me to make this patch is that I was working on running the kernel on my old computer and when I passed root=/dev/sda
to the kernel there was a panic and it could not start init, but since the call stack took almost all the space on the screen,
I couldn't see the available partitions the kernel does detects.
After this patch, I could just pass in the new boot parameter I added here and then it would not print the call stack,
and I saw the line in which the kernel prints the available partitions.
On Wed, Feb 07, 2024 at 09:10:22AM +0700, Bagas Sanjaya wrote:
> On Tue, Feb 06, 2024 at 09:39:02PM +0000, Nir Lichtman wrote:
> > From: Nir Lichtman <nir@lichtman.org>
> > Date: Sat, 3 Feb 2024 10:19:30 +0200
> > Subject: [PATCH] kernel: add boot param to disable stack dump on panic
> >
>
> Can you describe why this patch is needed (or beneficial)?
>
> Confused...
>
> --
> An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2024-02-08 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 21:39 [PATCH] kernel: add boot param to disable stack dump on panic Nir Lichtman
2024-02-07 2:10 ` Bagas Sanjaya
2024-02-08 8:14 ` Nir Lichtman [this message]
2024-02-09 9:22 ` Bagas Sanjaya
2024-02-09 9:50 ` Nir Lichtman
2024-02-09 23:13 ` Randy Dunlap
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=20240208081425.GA1511946@lichtman.org \
--to=nir@lichtman.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox