[Bug 1935617] Re: systemd autopkgtest broken on ppc64el with qemu 6.0

[Christian Ehrhardt ]

The service has a StartPre that is like
  ExecStartPre=rm -f /failed /testok

And that works to reproduce:

bash-5.1# rm -f /failed /testok
Segmentation fault (core dumped)

In fact this RM is very very sad:
-bash-5.1# rm /doesnotexist
Segmentation fault (core dumped)
-bash-5.1# touch /doesexist
-bash-5.1# rm /doesexist
Segmentation fault (core dumped)
-bash-5.1# rm -f /doesexist
Segmentation fault (core dumped)

Other commands (as far as I can see) work as usual albeit with the
restrictions of an emulated HVC console.

There is no ssh installed and no apt, so getting this into a better
debuggable state isn't easy.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1935617

Title:
  systemd autopkgtest broken on ppc64el with qemu 6.0

Status in qemu package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm not sure yet if this is flaky or a real issue, but I'm filing it
  to avoid multiple people analyzing the same.

  The Qemu 6.0 upload https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-1~ubuntu2 triggers a test failure like
  https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20210708_223311_e3bbb@/log.gz

  I have tested the new qemu on ppc64 and it worked fine for device emulation and migration cases.
  But this is suspicious.
  Of the last tests exactly and only those with the new qemu failed.

  
  impish
    ppc64el
      tests-in-lxd                   (F  5% f  0% S  0% B  0% => P 95%/) F.........F.............................
      systemd-fsckd                  (F  0% f  0% S 100% B  0% => P  0%/) SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
      upstream-1                     (F 15% f  0% S  0% B  0% => P 85%/) F..FFFF....F............................
      upstream-2                     (F 12% f  0% S  0% B  0% => P 87%/) F..FFFF.................................

  
  For an insight in flakyness/reproducibility I've retriggered the missing qemu and the non-qemu cases a few times. If those reproduce all-bad vs all-good again this would further indicate a real issue.

  Unfortunately the ppc maas seems down right now and canonistack also
  isn't too nice this week - overall that inhibits the testing a bit :-/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1935617/+subscriptions