Since it was me who initially raised that bug, I feel like I should comment on this.
My test case was and is to install Ubuntu on z/VM using (at least one) zFCP/SCSI devices for disk storage. That should be a proper end-2-end test since it includes the entire zFCP/SCSI stack (even incl. multipath) and with that covers the initially reported problem mentioned in the bug description. Please notice that all this happened to me on 16.04(.5) only with GA kernel 4.4 (hence the '4.4' still in the headline and even 16.04's HWE kernel 4.15 worked for me in the past - see comment above), but now it looks like we talk about 18.04 too, but I never saw that problem on 18.04. Nevertheless, I (re-)tested today on 18.04(.3) - so it's more a regression test than anything else. I used 18.04.3 default (means proposed disabled) as well as with proposed enabled. W/o proposed I see systemd 237-3ubuntu10.29 with propose I see 237-3ubuntu10.31. Means I wasn't able to use 237-3ubuntu10.30 - like mentioned in comment #30. But both tests worked fine for me and I didn't saw any anomalies (details see attachment). ** Attachment added: "verification bionic.txt" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+attachment/5293039/+files/verification%20bionic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
