This part is quite similar to the old text and just a placeholder for now. It and the referenced document afaics need to be revisited, as they seem outdated to me. But I'm not really familiar with the current state of things in that area and thus didn't feel qualified to write down anything better quickly.
So consider this a request for help for those that know this area. Could you maybe write something that would fit in here? Or outline the current situation roughly in a reply (when is scripts/decode_stacktrace.sh enough?), as that will make it easier for me or others to write something? It should answer questions like "when is this actually needed", "what .config options to ideally set to make this step easy or unnecessary (CONFIG_UNWINDER_ORC when available, otherwise CONFIG_UNWINDER_FRAME_POINTER)?". Signed-off-by: Thorsten Leemhuis <li...@leemhuis.info> --- Documentation/admin-guide/reporting-bugs.rst | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/Documentation/admin-guide/reporting-bugs.rst b/Documentation/admin-guide/reporting-bugs.rst index 7af4e7a6e797..be866dd1e6b6 100644 --- a/Documentation/admin-guide/reporting-bugs.rst +++ b/Documentation/admin-guide/reporting-bugs.rst @@ -839,6 +839,18 @@ issue you face. Use this knowledge and search again for existing reports instead you can join. +Decode failure messages +----------------------- + + *If the failure includes a stack dump, like an Oops does, consider decoding + it to find the offending line of code.* + +When the kernel detects an error, it will print a stack dump that allows to +identify the exact line of code where the issue happens. But that information +sometimes needs to get decoded to be readable, which is explained in +admin-guide/bug-hunting.rst. + + .. ############################################################################ .. Temporary marker added while this document is rewritten. Sections above .. are new and dual-licensed under GPLv2+ and CC-BY 4.0, those below are old. @@ -870,9 +882,7 @@ step-by-step instructions for how a user can trigger the bug. If the failure includes an "OOPS:", take a picture of the screen, capture a netconsole trace, or type the message from your screen into the bug -report. Please read "Documentation/admin-guide/bug-hunting.rst" before posting your -bug report. This explains what you should do with the "Oops" information -to make it useful to the recipient. +report. This is a suggested format for a bug report sent via email or bugzilla. Having a standardized bug report form makes it easier for you not to -- 2.28.0
