Isolated case
$ sudo env SELECTED_TESTS="TEST-08-*" debian/tests/upstream
It runs a VM Guest to do init stuff and that seems to break:
There are suspicious logs like systemd crashing, but those also exist (to some extent) in the good case. I compared that:
$ grep -e "of user 0 dumped core" -e "^TEST-[0-9][0-9]-.* SETUP:" systemd-ppc-good.txt
Just one hit in TEST-17-UDEV
While the bad case has hits in exactly the list of not failing tests.
So these crashes are indeed related (root cause or symptom is not yet clear yet) to the problem.
The boot&stop itself is fine if you just start the same commands.
But the tests redirect the journal and process it, in there is the crash - I need to find how it does that.
Isolated case TESTS=" TEST-08- *" debian/ tests/upstream
$ sudo env SELECTED_
It runs a VM Guest to do init stuff and that seems to break:
There are suspicious logs like systemd crashing, but those also exist (to some extent) in the good case. I compared that:
$ grep -e "of user 0 dumped core" -e "^TEST- [0-9][0- 9]-.* SETUP:" systemd- ppc-good. txt
Just one hit in TEST-17-UDEV
While the bad case has hits in exactly the list of not failing tests.
So these crashes are indeed related (root cause or symptom is not yet clear yet) to the problem.
The boot&stop itself is fine if you just start the same commands.
But the tests redirect the journal and process it, in there is the crash - I need to find how it does that.