systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash

Bug #1625100 reported by Andy Whitcroft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
systemd (Ubuntu)
Invalid
Undecided
Unassigned
Andy Whitcroft (apw)
tags: added: kernel-4.8
Revision history for this message
Martin Pitt (pitti) wrote :

amd64 failed in "upstream" tests during image preparation:

The file /dev/loop4p1 does not exist and no size was specified.
F: Failed to mkfs -t ext3

This might be just a rare race condition (I've never seen it). Does it reproduce on retry?

ppc64el:
 - One failure is due to linux-image-extra-4.8.0-11-generic losing scsi_debug (kernel bug)
 - The other is a regression in tmpfiles:
   Sep 18 22:23:56 autopkgtest systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=killed, status=11/SEGV
   That needs to be investigated more closely; the segfault is certainly a systemd bug, presumably a code path now triggered by different kernel behaviour.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1625100

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Martin Pitt (pitti)
summary: - systemd 231-6 ADT test failure with linux 4.8.0-11.12
+ systemd test failure with linux 4.8.0-11.12: scsi_debug missing in
+ ppc64el, systemd-tmpfiles crash
Revision history for this message
Martin Pitt (pitti) wrote :

I tried to reproduce the full boot-and-services test log on scalingstack, and upon rebooting into the 4.8 kernel I got the attached kernel oops. This does everytime, though.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

CONFIG_SCSI_DEBUG is now enabled for all arches in Ubuntu-4.8.0-12.13

Revision history for this message
Martin Pitt (pitti) wrote :

FTR, I ran the full boot-and-services test against the current PPA which has kernel -11.12 and could not reproduce the crash. Could it be that this was a regression in -10.11 (the test runs in the description) which got fixed in -11.12 again?

So the only concrete thing here that I can see is the missing scsi_debug module.

Revision history for this message
Martin Pitt (pitti) wrote :

> [kernel oops] This does everytime, though.

This was supposed to mean: This does *not happen* every time.

Martin Pitt (pitti)
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
status: Incomplete → New
Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Brad Figg (brad-figg) wrote :

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1625100

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in systemd (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

This was fixed in -14, scsi_debug is back.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/ppc64el passed a few times again, and that tmpfiles crash never reproduced.

Changed in systemd (Ubuntu):
status: Confirmed → Fix Released
status: Fix Released → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.