From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Jacobson <jidanni@jidanni.org>, linux-kernel@vger.kernel.org
Subject: Re: Say what the -[ cut here ]- lines are called
Date: Fri, 17 Aug 2018 13:22:12 -0700 [thread overview]
Message-ID: <47f50df3-1c46-cb84-50d7-99684d58772c@infradead.org> (raw)
In-Reply-To: <878t56rpc9.fsf@jidanni.org>
On 08/16/2018 02:09 PM, Dan Jacobson wrote:
> The kernel should really say what the
> ------------[ cut here ]------------
> lines are called, else users will say things like:
>
> "I discovered that the user needs to use xrandr in _two_ steps for
> certain resolutions, else he will trigger a
> kernel: ------------[ cut here ]------------ line."
>
> instead of
> "...will trigger a kernel problem."
> "...will trigger a kernel fault."
> "...will trigger a kernel oops."
> or whatever it is supposed to be called.
>
> So say e.g.,
> ------------[ cut here ]------------
> Kernel fault:
>
> etc. there in the syslog. Thanks.
>
My google search fu shows me:
------------[ cut here ]------------
(immediately followed by:)
kernel BUG at ...
(or)
WARNING: at
...
and ending with:
---[ end trace c228cd85b8ef2f99 ]---
Or are requesting more descriptive words immediately before "cut here", e.g.,
----------[ begin kernel trace report c228cd85b8ef2f99: cut here ]----------
See, I would prefer to see the hex "oops ID" at the beginning as well as the
end of the trace report.
--
~Randy
prev parent reply other threads:[~2018-08-17 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 21:09 Say what the -[ cut here ]- lines are called Dan Jacobson
2018-08-17 20:22 ` Randy Dunlap [this message]
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=47f50df3-1c46-cb84-50d7-99684d58772c@infradead.org \
--to=rdunlap@infradead.org \
--cc=jidanni@jidanni.org \
--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;
as well as URLs for NNTP newsgroup(s).