This issue was successfully reproduced with the Cosmic kernel in -updates. Not 100% reproducible but this is what I did:
First successful attempt
1. Watch the syslog on SUT, run the ubuntu_cts_kernel on the SUT
2. Wait for a while, and this issue occurs (unfortunately I can't get the log, the initial error message got flushed away with the following destroy_worker+0x58/0x70 messages)
Second successful attempt:
1. Watch the syslog on SUT, run the ubuntu_cts_kernel on the SUT
2. Wait for a while
3. SSH to SUT
It looks like when the systemd kicks in, this will happen. Please refer to the attachment for the syslog output in this attempt.
This issue was successfully reproduced with the Cosmic kernel in -updates. Not 100% reproducible but this is what I did:
First successful attempt worker+ 0x58/0x70 messages)
1. Watch the syslog on SUT, run the ubuntu_cts_kernel on the SUT
2. Wait for a while, and this issue occurs (unfortunately I can't get the log, the initial error message got flushed away with the following destroy_
Second successful attempt:
1. Watch the syslog on SUT, run the ubuntu_cts_kernel on the SUT
2. Wait for a while
3. SSH to SUT
It looks like when the systemd kicks in, this will happen. Please refer to the attachment for the syslog output in this attempt.