OopsText.txt does not contain stack trace
Bug #1870553 reported by
Mauricio Faria de Oliveira
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Please refer to bug 1868388 attachment OopsText.txt.
The issue reported is a kernel cpu soft lockup.
The stack trace is essential to understand what was going on,
but it's _not included at_ all - actually, it's been cut off,
there's the beginning of the kernel messages, but ends there.
Unfortunately the output of dmesg (file CurrentDmesg.txt)
does not have the kernel error messages (maybe collected
at some other point in time?) - so the bug report has no
evidences of the stack trace to perform any debugging.
Is this behavior intentional/by design for some reason?
Can that be clarified/reviewed as there's at least one
(this) occurrence that didn't allow apport files to be
used for debugging?
Thanks!
| Changed in apport (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
