On Thu, Jul 5, 2018 at 5:47 PM, Jeff Backus <jeff.backus(a)gmail.com> wrote:
On Thu, Jul 5, 2018 at 5:07 PM, Zbigniew Jędrzejewski-Szmek <
zbyszek(a)in.waw.pl> wrote:
>
> Might be a problem in systemd code to select clock type
> (monotonic/realtime/etc.).
> You can try taking an older image, and compiling systemd, and running the
> tests.
> Even something as simple as
> sudo dnf build-dep systemd
> git clone
https://github.com/systemd/systemd
> cd systemd
> meson -Dman=false build && ninja -C build && ninja -C build test
>
> If that passes, then the next step would be to take that older image,
> install just the newer kernel, and repeat the tests.
>
> Zbyszek
>
Here's a quick update, since I may not be able to get back to this until
early next week. I was able to build the version of systemd that is in the
master branch of the GH repo, SHA: 8255430. All tests that were executed
pass under kernel 4.16.16-300. About 10 tests were skipped. The following
skipped tests seem to be of particular interest:
* test-udev
* test-boot-timestamps
I was able to insert an "assert_se(1==0)" after the line that triggered the
assertion when booting from the installer, and numerous tests fail. So that
code is at least getting exercised.
Installed the latest version of the kernel available for F28, 4.17.3-200,
and test results were the same. I am now trying to build 4.18.0-0.rc3,
since that appears to be the latest version in rawhide.
jeff
--
Jeff Backus
jeff.backus(a)gmail.com
http://github.com/jsbackus