Ubuntu
systemd package

systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1

Bug #1944712 reported by Tim Gardner
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-aws-5.4 (Ubuntu)
Confirmed
Undecided
Unassigned
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This is a scripted bug report about ADT failures while running systemd tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined.

Testing failed on:
    amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz

Revision history for this message
Tim Gardner (timg-tpi) wrote :

timedated PASS
hostnamed PASS
localed-locale PASS
localed-x11-keymap PASS
logind PASS
unit-config PASS
storage PASS
networkd-test.py PASS
build-login PASS
boot-and-services PASS
udev PASS
root-unittests PASS
upstream FAIL timed out
boot-smoke PASS
systemd-fsckd SKIP exit status 77 and marked as skippable

tags: added: kernel-adt-failure
Revision history for this message
Dan Bungert (dbungert) wrote :

I filed one like this as well, so let me merge with this one.
My notes:

Systemd amd64 autopkgtest runs, when triggered by non-linux-meta packages, usually pass. You can find some failures on a possible flaky TEST-29-PORTABLE. Ignore those for the moment.

Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually fail and hit the 20000 second timeout on the systemd upstream-1 (and sometimes upstream-2) test. I did find an outlier that hit the same timeout:
248.3-1ubuntu3 e2fsprogs/1.46.3-1ubuntu3 2021-09-05 15:02:56 UTC 6h 58m 46s

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-aws-5.4 (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
status: New → Confirmed
Dan Bungert (dbungert)
tags: added: update-excuse
Revision history for this message
Lukas Märdian (slyon) wrote :

In more recent kernels (i.e. linux-meta-aws/azure 5.13) I can see messages like this: " watchdog: BUG: soft lockup - CPU#3 stuck for 238s!" that seems to indicate the kernel is not giving back control to the userspace/systemd.

Also a message about a missing autofs4 module, that might be related: "systemd[1]: Failed to find module 'autofs4'"

Revision history for this message
Lukas Märdian (slyon) wrote :

Closing this bug for systemd, as it's not relevant anymore IMO and is a red herring in proposed-migration.

Changed in systemd (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.