log_check test in ubuntu_boot will erroneously get error from previous session on manually provisioned systems

Bug #1937276 reported by Po-Hsu Lin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Po-Hsu Lin

Bug Description

Issue found on s390x node s2lp4, the log_check test erroneously report the error message reported in earlier runs (the uptime here is too old for a fresh reboot)

07:32:35 INFO | kernel: [196220.210597] BUG: non-zero pgtables_bytes on freeing mm: 16384
07:32:35 INFO | kernel: [196220.227126] BUG: non-zero pgtables_bytes on freeing mm: 16384
07:32:35 INFO | kernel: [196220.227476] BUG: non-zero pgtables_bytes on freeing mm: 16384
07:32:35 INFO | kernel: [196220.276436] BUG: non-zero pgtables_bytes on freeing mm: 16384
07:32:35 INFO | kernel: [196220.276775] BUG: non-zero pgtables_bytes on freeing mm: 16384

This is because we parse log from syslog. It's ok on other ones because they all got re-provisioned.

dmesg will be cleared out in autotest with dmesg -c before the test starts.

We need to find another way to get the boot dmesg

Po-Hsu Lin (cypressyew)
tags: added: sru-20210719 ubuntu-boot
tags: added: s390x
Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: New → In Progress
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
summary: - log_check test in ubuntu_boot will erroneously get error on manually
- provisioned systems
+ log_check test in ubuntu_boot will erroneously get error from previous
+ session on manually provisioned systems
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers