After a user has been running a proposed kernel for a couple days, I would
like to parse the logs of the system to detect what parts of the kernel
might have been tested implicitly during that period. These results could
then be uploaded to Launchpad, with the consent of the user of course,
without having to actually run tests manually. [1]
First, I would like to consider suspending. I looked in /var/log/syslog
where I found strings that could be parsed to detect a successful wakeup
from suspend:
kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
However, the problem is that syslog does not seem to contain the kernel
version to validate that the proposed kernel is effectively being tested.
So, I then discovered /var/log/pm-suspend.log which contained both the
kernel version and the result of resuming from suspend:
Second, I would also like to consider the same for hibernating. I looked
at /var/log/pm-suspend.log which also seemed to contain the result of
thawing from hibernate:
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 03:26 PM
Tim Gardner
Parsing log files for test results
On 12/05/2011 03:29 PM, Marc Tardif wrote:
Hi folks,
After a user has been running a proposed kernel for a couple days, I would
like to parse the logs of the system to detect what parts of the kernel
might have been tested implicitly during that period. These results could
then be uploaded to Launchpad, with the consent of the user of course,
without having to actually run tests manually. [1]
First, I would like to consider suspending. I looked in /var/log/syslog
where I found strings that could be parsed to detect a successful wakeup
from suspend:
kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
However, the problem is that syslog does not seem to contain the kernel
version to validate that the proposed kernel is effectively being tested.
So, I then discovered /var/log/pm-suspend.log which contained both the
kernel version and the result of resuming from suspend:
Second, I would also like to consider the same for hibernating. I looked
at /var/log/pm-suspend.log which also seemed to contain the result of
thawing from hibernate:
Marc - AFAIK those logs will continue to be created. However, I must
point out that the kernel team doesn't own the pm-utils package.
rtg
--
Tim Gardner tim.gardner@canonical.com
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 03:40 PM
Colin Ian King
Parsing log files for test results
On 05/12/11 22:29, Marc Tardif wrote:
Hi folks,
After a user has been running a proposed kernel for a couple days, I would
like to parse the logs of the system to detect what parts of the kernel
might have been tested implicitly during that period. These results could
then be uploaded to Launchpad, with the consent of the user of course,
without having to actually run tests manually. [1]
First, I would like to consider suspending. I looked in /var/log/syslog
where I found strings that could be parsed to detect a successful wakeup
from suspend:
kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
However, the problem is that syslog does not seem to contain the kernel
version to validate that the proposed kernel is effectively being tested.
So, I then discovered /var/log/pm-suspend.log which contained both the
kernel version and the result of resuming from suspend:
Second, I would also like to consider the same for hibernating. I looked
at /var/log/pm-suspend.log which also seemed to contain the result of
thawing from hibernate:
This kind of S3 success detection has implemented in fwts. I refer you
to the git
repo: git://kernel.ubuntu.com/lexical/fwts.git and the relevant source:
src/acpi/s3/s3.c - see s3_check_log()
src/lib/src/fwts_hwinfo.c - see fwts_hwinfo_get() and
fwts_hwinfo_lists_differ()
src/lib/src/fwts_klog.c and data/klog.json (containing >160 regexs
to scan the kernel log)
Colin
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 03:45 PM
Andy Whitcroft
Parsing log files for test results
On Mon, Dec 05, 2011 at 05:29:44PM -0500, Marc Tardif wrote:
> Hi folks,
>
> After a user has been running a proposed kernel for a couple days, I would
> like to parse the logs of the system to detect what parts of the kernel
> might have been tested implicitly during that period. These results could
> then be uploaded to Launchpad, with the consent of the user of course,
> without having to actually run tests manually. [1]
>
> First, I would like to consider suspending. I looked in /var/log/syslog
> where I found strings that could be parsed to detect a successful wakeup
> from suspend:
>
> kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
>
> However, the problem is that syslog does not seem to contain the kernel
> version to validate that the proposed kernel is effectively being tested.
>
> So, I then discovered /var/log/pm-suspend.log which contained both the
> kernel version and the result of resuming from suspend:
>
> Linux 200910-4253 3.0.0-12-generic #20-Ubuntu SMP Fri Oct...
> [snip]
> /var/lib/pm-utils/sleep.d/00kernel-change resume suspend: success.
>
> Second, I would also like to consider the same for hibernating. I looked
> at /var/log/pm-suspend.log which also seemed to contain the result of
> thawing from hibernate:
>
> /var/lib/pm-utils/sleep.d/000kernel-change thaw hibernate: success.
>
> Would you say that these are reliable ways to detect that suspend and
> hibernate were successful?
Cirtianly the other testing scripts I have seen use those same files
from pm-utils to work out if suspend-resume/hibernate-resume worked
correctly. As Tim points out they are not something we control however.
I would also expect to see the kernel version in syslog, prior to the
s/r, though if the machine has been up a long time it may be rolled out:
/var/log/syslog.6.gz:Nov 28 22:26:15 dm kernel: [ 0.000000] Linux version 3.2.0-2-generic (root@gomeisa) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-2ubuntu1) ) #4~pre1 SMP Thu Nov 24 16:42:07 UTC 2011 (Ubuntu 3.2.0-2.4~pre1-generic 3.2.0-rc3)
-apw
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 03:49 PM
Marc Tardif
Parsing log files for test results
* Colin Ian King <colin.king@canonical.com> [2011-12-06 16:40 +0000]:
> On 05/12/11 22:29, Marc Tardif wrote:
> >After a user has been running a proposed kernel for a couple days, I would
> >like to parse the logs of the system to detect what parts of the kernel
> >might have been tested implicitly during that period. These results could
> >then be uploaded to Launchpad, with the consent of the user of course,
> >without having to actually run tests manually. [1]
> >
> >First, I would like to consider suspending. I looked in /var/log/syslog
> >where I found strings that could be parsed to detect a successful wakeup
> >from suspend:
> >
> > kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
> >
> >However, the problem is that syslog does not seem to contain the kernel
> >version to validate that the proposed kernel is effectively being tested.
> >
> >So, I then discovered /var/log/pm-suspend.log which contained both the
> >kernel version and the result of resuming from suspend:
> >
> > Linux 200910-4253 3.0.0-12-generic #20-Ubuntu SMP Fri Oct...
> > [snip]
> > /var/lib/pm-utils/sleep.d/00kernel-change resume suspend: success.
> >
> >Second, I would also like to consider the same for hibernating. I looked
> >at /var/log/pm-suspend.log which also seemed to contain the result of
> >thawing from hibernate:
> >
> > /var/lib/pm-utils/sleep.d/000kernel-change thaw hibernate: success.
> >
> >Would you say that these are reliable ways to detect that suspend and
> >hibernate were successful?
> >
> >1. https://blueprints.launchpad.net/certify-planning/+spec/hardware-p-cert-sru-community
> >
> This kind of S3 success detection has implemented in fwts. I refer
> you to the git
> repo: git://kernel.ubuntu.com/lexical/fwts.git and the relevant source:
> src/acpi/s3/s3.c - see s3_check_log()
> src/lib/src/fwts_hwinfo.c - see fwts_hwinfo_get() and
> fwts_hwinfo_lists_differ()
> src/lib/src/fwts_klog.c and data/klog.json (containing >160
> regexs to scan the kernel log)
After looking at the code, I only noticed checking for S3 failure rather
than S3 success. The distinction is not strictly pedantic but rather to
make sure I understand correctly: s3_check_log and the patterns in
klog.json only really check if something went wrong, right?
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 04:52 PM
Colin Ian King
Parsing log files for test results
On 06/12/11 16:49, Marc Tardif wrote:
* Colin Ian King<colin.king@canonical.com> [2011-12-06 16:40 +0000]:
On 05/12/11 22:29, Marc Tardif wrote:
After a user has been running a proposed kernel for a couple days, I would
like to parse the logs of the system to detect what parts of the kernel
might have been tested implicitly during that period. These results could
then be uploaded to Launchpad, with the consent of the user of course,
without having to actually run tests manually. [1]
First, I would like to consider suspending. I looked in /var/log/syslog
where I found strings that could be parsed to detect a successful wakeup
>from suspend:
kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
However, the problem is that syslog does not seem to contain the kernel
version to validate that the proposed kernel is effectively being tested.
So, I then discovered /var/log/pm-suspend.log which contained both the
kernel version and the result of resuming from suspend:
Second, I would also like to consider the same for hibernating. I looked
at /var/log/pm-suspend.log which also seemed to contain the result of
thawing from hibernate:
This kind of S3 success detection has implemented in fwts. I refer
you to the git
repo: git://kernel.ubuntu.com/lexical/fwts.git and the relevant source:
src/acpi/s3/s3.c - see s3_check_log()
src/lib/src/fwts_hwinfo.c - see fwts_hwinfo_get() and
fwts_hwinfo_lists_differ()
src/lib/src/fwts_klog.c and data/klog.json (containing>160
regexs to scan the kernel log)
After looking at the code, I only noticed checking for S3 failure rather
than S3 success. The distinction is not strictly pedantic but rather to
make sure I understand correctly: s3_check_log and the patterns in
klog.json only really check if something went wrong, right?
Sure, one needs to define what success is I suppose.
Colin
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 05:02 PM
Marc Tardif
Parsing log files for test results
* Andy Whitcroft <apw@canonical.com> [2011-12-06 16:45 +0000]:
> On Mon, Dec 05, 2011 at 05:29:44PM -0500, Marc Tardif wrote:
> > First, I would like to consider suspending. I looked in /var/log/syslog
> > where I found strings that could be parsed to detect a successful wakeup
> > from suspend:
> >
> > kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
> >
> > However, the problem is that syslog does not seem to contain the kernel
> > version to validate that the proposed kernel is effectively being tested.
[snip]
> I would also expect to see the kernel version in syslog, prior to the
> s/r, though if the machine has been up a long time it may be rolled out:
>
> /var/log/syslog.6.gz:Nov 28 22:26:15 dm kernel: [ 0.000000] Linux version 3.2.0-2-generic (root@gomeisa) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-2ubuntu1) ) #4~pre1 SMP Thu Nov 24 16:42:07 UTC 2011 (Ubuntu 3.2.0-2.4~pre1-generic 3.2.0-rc3)
I would appreciate having a better understanding of what prints those
lines to syslog and when they should be expected to be printed. I have
recently installed a system running Oneiric which has been rebooted a
few times, dist-upgraded and rebooted again. I still get nothing when
attempting to grep the logs for the kernel version:
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-06-2011, 09:41 PM
Andy Whitcroft
Parsing log files for test results
On Tue, Dec 06, 2011 at 01:02:47PM -0500, Marc Tardif wrote:
> * Andy Whitcroft <apw@canonical.com> [2011-12-06 16:45 +0000]:
> > On Mon, Dec 05, 2011 at 05:29:44PM -0500, Marc Tardif wrote:
> > > First, I would like to consider suspending. I looked in /var/log/syslog
> > > where I found strings that could be parsed to detect a successful wakeup
> > > from suspend:
> > >
> > > kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
> > >
> > > However, the problem is that syslog does not seem to contain the kernel
> > > version to validate that the proposed kernel is effectively being tested.
> [snip]
> > I would also expect to see the kernel version in syslog, prior to the
> > s/r, though if the machine has been up a long time it may be rolled out:
> >
> > /var/log/syslog.6.gz:Nov 28 22:26:15 dm kernel: [ 0.000000] Linux version 3.2.0-2-generic (root@gomeisa) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-2ubuntu1) ) #4~pre1 SMP Thu Nov 24 16:42:07 UTC 2011 (Ubuntu 3.2.0-2.4~pre1-generic 3.2.0-rc3)
>
> I would appreciate having a better understanding of what prints those
> lines to syslog and when they should be expected to be printed. I have
> recently installed a system running Oneiric which has been rebooted a
> few times, dist-upgraded and rebooted again. I still get nothing when
> attempting to grep the logs for the kernel version:
>
> zgrep '3.0.0' /var/log/syslog*
Hmm I normally look for 'Linux ' when greping for these. The linux
line is generated by the kernel itself and pulled out of the kernel by
syslogd.
-apw
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-07-2011, 01:32 PM
Marc Tardif
Parsing log files for test results
* Andy Whitcroft <apw@canonical.com> [2011-12-06 22:41 +0000]:
> On Tue, Dec 06, 2011 at 01:02:47PM -0500, Marc Tardif wrote:
> > * Andy Whitcroft <apw@canonical.com> [2011-12-06 16:45 +0000]:
> > > On Mon, Dec 05, 2011 at 05:29:44PM -0500, Marc Tardif wrote:
> > > > First, I would like to consider suspending. I looked in /var/log/syslog
> > > > where I found strings that could be parsed to detect a successful wakeup
> > > > from suspend:
> > > >
> > > > kernel: [ 137.402845] ACPI: Waking up from system sleep state S3
> > > >
> > > > However, the problem is that syslog does not seem to contain the kernel
> > > > version to validate that the proposed kernel is effectively being tested.
> > [snip]
> > > I would also expect to see the kernel version in syslog, prior to the
> > > s/r, though if the machine has been up a long time it may be rolled out:
> > >
> > > /var/log/syslog.6.gz:Nov 28 22:26:15 dm kernel: [ 0.000000] Linux version 3.2.0-2-generic (root@gomeisa) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-2ubuntu1) ) #4~pre1 SMP Thu Nov 24 16:42:07 UTC 2011 (Ubuntu 3.2.0-2.4~pre1-generic 3.2.0-rc3)
> >
> > I would appreciate having a better understanding of what prints those
> > lines to syslog and when they should be expected to be printed. I have
> > recently installed a system running Oneiric which has been rebooted a
> > few times, dist-upgraded and rebooted again. I still get nothing when
> > attempting to grep the logs for the kernel version:
> >
> > zgrep '3.0.0' /var/log/syslog*
>
> Hmm I normally look for 'Linux ' when greping for these. The linux
> line is generated by the kernel itself and pulled out of the kernel by
> syslogd.
When I grep for 'Linux', I get lines like this:
# zgrep Linux /var/log/syslog*
Dec 6 13:00:54 200910-4253 kernel: [ 4.024835] Linux agpgart
interface v0.103
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
12-07-2011, 03:11 PM
Andy Whitcroft
Parsing log files for test results
On Wed, Dec 07, 2011 at 09:32:07AM -0500, Marc Tardif wrote:
> When I grep for 'Linux', I get lines like this:
>
> # zgrep Linux /var/log/syslog*
> Dec 6 13:00:54 200910-4253 kernel: [ 4.024835] Linux agpgart
> interface v0.103
I get the below, note teh ones at timestamp 0.000000 ... each is a boot
signature.
$ zgrep 'Linux ' /var/log/syslog*
/var/log/syslog.7.gz:Nov 26 17:36:58 localhost kernel: [ 0.000000] Linux version 3.2.0-2-generic-pae (root@gomeisa) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-2ubuntu1) ) #4~pre1 SMP Thu Nov 24 16:33:40 UTC 2011 (Ubuntu 3.2.0-2.4~pre1-generic-pae 3.2.0-rc3)
/var/log/syslog.7.gz:Nov 26 17:36:58 localhost kernel: [ 1.365195] Linux agpgart interface v0.103
/var/log/syslog.7.gz:Nov 26 17:36:59 localhost kernel: [ 12.547635] Linux video capture interface: v2.00
/var/log/syslog.7.gz:Nov 27 15:02:45 localhost kernel: [ 0.000000] Linux version 3.2.0-2-generic-pae (root@gomeisa) (gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-2ubuntu1) ) #4~pre1 SMP Thu Nov 24 16:33:40 UTC 2011 (Ubuntu 3.2.0-2.4~pre1-generic-pae 3.2.0-rc3)
/var/log/syslog.7.gz:Nov 27 15:02:45 localhost kernel: [ 1.361170] Linux agpgart interface v0.103
/var/log/syslog.7.gz:Nov 27 15:02:46 localhost kernel: [ 12.515165] Linux video capture interface: v2.00
-apw
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Parsing log files for test results
