Public bug reported:
While working on something for checkbox, I tried running fwts to do some
s3 cycles like so:
sudo fwts s3 --s3-sleep-delay=30 -r suspend-test.log
After the system woke up and fwts completed its tests, I checked the log
and noted that there were no errors of any sort detected.
However, on checking syslog, I notice that there are stack traces thrown
after resuming from S3 on my machine (most likely these are due to
running bisection test kernels). But these stack traces are not caught
by fwts during the checks and I am not sure if they are supposed to be
and this is a bug with fwts, or they are safe to ignore.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: fwts 0.25.06precise1
Uname: Linux 3.3.0-030300rc1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Wed Oct 10 12:36:44 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: fwts
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: fwts (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise running-unity
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1065135/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
