lkml.org 
[lkml]   [2018]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Say what the -[ cut here ]- lines are called
From
Date
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

\
 
 \ /
  Last update: 2018-08-17 22:23    [W:0.025 / U:1.192 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site