canonical-ubuntu-qa team mailing list archive

[Tim Whisonant <1965937@xxxxxxxxxxxxxxxxxx>]

Seen on jammy:linux-gkeop 5.15.0-1057.64 during s2024.10.28

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/1965937

Title:
  raw_skew in timer from ubuntu_kernel_selftests failed on F-oem-5.14
  (Estimating clock drift: -144.976(est) 0.0(act)    [FAILED])

Status in ubuntu-kernel-tests:
  New

Bug description:
  Issue found on node vought and spitfire with:
    * F-oem 5.14.0-1028.31 (vought)
    * F-oem 5.14.0-1029.32 (spitfire)

  It's 100% reproducible if you run the whole ubuntu_kernel_selftests
  test via jenkins.

  But if you run this raw_skew test directly on it, it will pass

  It looks like a combination effect, I tried to run test suites before this "timers" suit where the raw_skew test is located. And then followed by this suit, e.g.:
  1. seccomp > timers
  2. ptrace > timers
  3. net > timers
  4. mount > timers
  5. memory-hotplug > timers
  6. memfd > timers

  Turns out the timers test will fail after the memfd test.

  Test log:
   Running 'make run_tests -C timers TEST_PROGS=raw_skew TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/timers'
   TAP version 13
   1..1
   # selftests: timers: raw_skew
   # Estimating clock drift: -49.574(est) 0.0(act)        [FAILED]
   # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0
   not ok 1 selftests: timers: raw_skew # exit=1 
   make: Leaving directory '/home/ubuntu/autotest/client

  syslog when this is failing:
  Mar 22 10:34:16 spitfire systemd[1]: Started ntp-systemd-netif.service.
  Mar 22 10:34:17 spitfire ntpd[3625]: ntpd exiting on signal 15 (Terminated)
  Mar 22 10:34:17 spitfire ntpd[3625]: 192.168.102.22 local addr 192.168.102.212 -> <null>
  Mar 22 10:34:17 spitfire systemd[1]: Stopping Network Time Service...
  Mar 22 10:34:17 spitfire systemd[1]: ntp.service: Succeeded.
  Mar 22 10:34:17 spitfire systemd[1]: Stopped Network Time Service.
  Mar 22 10:34:17 spitfire systemd[1]: Starting Network Time Service...
  Mar 22 10:34:17 spitfire kernel: [ 4816.731794] audit: type=1400 audit(1647945257.041:48): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=3673 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Mar 22 10:34:17 spitfire ntpd[3673]: ntpd 4.2.8p12@1.3728-o (1): Starting
  Mar 22 10:34:17 spitfire ntpd[3673]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /run/ntp.conf.dhcp -u 113:119
  Mar 22 10:34:17 spitfire systemd[1]: Started Network Time Service.
  Mar 22 10:34:17 spitfire ntpd[3676]: proto: precision = 0.171 usec (-22)
  Mar 22 10:34:17 spitfire systemd[1]: ntp-systemd-netif.service: Succeeded.
  Mar 22 10:34:17 spitfire ntpd[3676]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
  Mar 22 10:34:17 spitfire ntpd[3676]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
  Mar 22 10:34:17 spitfire ntpd[3676]: Listen and drop on 0 v6wildcard [::]:123
  Mar 22 10:34:17 spitfire ntpd[3676]: Listen and drop on 1 v4wildcard 0.0.0.0:123
  Mar 22 10:34:17 spitfire ntpd[3676]: Listen normally on 2 lo 127.0.0.1:123
  Mar 22 10:34:17 spitfire ntpd[3676]: Listen normally on 3 ens817f0 192.168.102.212:123
  Mar 22 10:34:17 spitfire ntpd[3676]: Listen normally on 4 lo [::1]:123
  Mar 22 10:34:17 spitfire ntpd[3676]: Listen normally on 5 ens817f0 [fe80::b696:91ff:fe61:dd30%2]:123
  Mar 22 10:34:17 spitfire ntpd[3676]: Listening on routing socket on fd #22 for interface updates
  Mar 22 10:34:17 spitfire ntpd[3676]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
  Mar 22 10:34:17 spitfire ntpd[3676]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
  Mar 22 10:34:39 spitfire systemd[1]: session-4.scope: Succeeded.

  Compare to a successful attempt, there is one extra "kernel reports
  TIME_ERROR: 0x41: Clock Unsynchronized" line in the syslog.

  A temporary workaroud is to swap the memfd test, run it after the
  timer test. But I think this should be investigated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1965937/+subscriptions