Released in fwts V0.26.03
** Changed in: fwts (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065135
Title:
Stack traces found in logs after S3,
Fix committed, fwts commits 1ce5785bf91579b2695e583c967947d750853fca +
adcba1286e5d4a4754332904229cde44fc8eb16e
** Changed in: fwts (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix sent to fwts-devel mailing list pending review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065135
Title:
Stack traces found in logs after S3, but fwts checks don't catch it
To manage notifi
** Changed in: fwts (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065135
Title:
Stack traces found in logs after S3, but fwts checks don't catch it
To ma
Actually, S3 test calls: s3_check_log() which in turn checks:
Kernel log PM errors
Kernel log BIOS and ACPI related errors
Kernel log common errors
Kernel oopses
but it does not check for warning stack dumps such as the slowpaths. We
should add that too. I will pop that on my TODO list as we do
AHH... OK. I was mistaken in my understanding of what it was checking
for. Thanks for the pointer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065135
Title:
Stack traces found in logs after S3,
The fwts klog test only reports the dmesg error patterns added in
/usr/share/fwts/klog.json. It only contains the firmware related ones.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065135
Title:
Here's the log generated by fwts showing no errors encountered during
the S3 test
** Attachment added: "suspend-test.log"
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1065135/+attachment/3393239/+files/suspend-test.log
--
You received this bug notification because you are a member of
Here is a portion of syslog starting at the beginning of my fwts S3 run
through now. It shows two stack traces in the log, one while
suspending, the other while resuming. Neither of these were caught by
FWTS. They are what I am not sure of... should they have been caught or
no?
** Attachment ad
