Public bug reported:
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!
** Affects: apport (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870553
Title:
OopsText.txt does not contain stack trace
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870553/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
