[Bug 1623383] Re: Some restarts fail due to missing base devices

[Stefan Bader]

I took a dump of another run that ended in the failed state. While not all messages that are in the journal show up in the dmesg log from a dump, there does not seem to be a message about systemd noticing the exit on systemd-modules-load, however I can not see the process listed in the ps output in crash. The ib_iser module is loaded.
So, with the previous info, it feels more like a communication issues between the systemd main process and the loader process. And also not always.

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

Title:
  Some restarts fail due to missing base devices

Status in udev package in Ubuntu:
  Confirmed

Bug description:
  Arch: s390x
  Release: Yakkety / 16.10

  This happens on some (but not all) system starts with Yakkety. In
  Xenial (which is using the same 4.4 kernel version the Yakkety systems
  were using when the problem was first observed) this did not happen.
  The system (LPAR) this was seen first was an upgrade from Xenial but
  since then has been freshly installed with Yakkety. The same behaviour
  is seen on a zVM guest running Yakkety.

  The attached syslog shows a failed boot, followed by one that did work. Note the "Found device .*(sclp|encc00).*" messages in the good boot. Those are missing in the bad attempt and as a result networking and console fail to be usable. Also note, those boots were 4.8 kernels but we saw this with 4.4 kernels, too.
  This might be a systemd problem / race, I just filed it into udev for now as that better matches the not finding basic devices symptom.

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