Skip to contentSkip to conversation

Say what the -[ cut here ]- lines are called

DISCUSSION Dan Jacobson 2 participants 2 messages Aug 17, 2018

lore
Share & tools
lore
#0 lore raw

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.

#1 lore raw
Quoted 14 lines · Dan Jacobson

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.

Quoted 6 lines

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.

Signature · 1 line
~Randy