From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: disable "Call Trace:"
Date: Sat, 09 Aug 2014 12:36:52 +0800 [thread overview]
Message-ID: <87y4uyp9cr.fsf@jidanni.org> (raw)
In-Reply-To: 877g2jznnt.fsf@jidanni.org
>>>>> "RD" == Randy Dunlap <rdunlap@infradead.org> writes:
RD> When would you want to disable it? at kernel boot time (as a boot option)
RD> or sometime later?
RD> But would you only want to disable Call Trace: on panics or any time that a
RD> call trace might be printed? and would disabling call trace also disable
RD> the raw stack dump and Code: output, or literally just the call trace?
All I know is e.g., somehow something went wrong and the user finds
himself unable to boot and unable to read the reason, as Linux is famous
for not having a way to scroll messages that have flown off the screen
and boot_delay= doesn't work good and he doesn't own another terminal he
can plug into a port or even have a port etc. etc. etc.
And he is sitting there and there is the reason, the main body of which
has just flown off the screen.
All pushed off due to this (useless to him) "Call Trace:" and some other
hex stuff lying above "Call Trace".
So if only he could please be able to, there hitting "e" in Grub,
be able to add so "call_trace=no_thanks" "other_hex_stuff=no_thanks"
to that linux command line, so then on the next run there will be
something more left upon the screen! Thank you!
next prev parent reply other threads:[~2014-08-09 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 3:05 disable "Call Trace:" 積丹尼 Dan Jacobson
2014-08-09 4:24 ` Randy Dunlap
2014-08-09 4:36 ` 積丹尼 Dan Jacobson [this message]
2014-08-10 21:58 ` 積丹尼 Dan Jacobson
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=87y4uyp9cr.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 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.