** Description changed:
+ SRU Justification:
+ ==
+
+ [ Impact ]
+
+ * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194
+are no longer able to IPL (boot) on IBM z14 or newer hardware.
+
+ * This issue got introduced by upstream commit e4f74400308c
+
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994601
Title:
[UBUNTU 18.04] Ubuntu 18.04 crashes during IPL
Status in Ubuntu on IBM z Systems:
Confirmed
Status
I just tried 20.04 (focal legacy image), just to be sure, but it's not
affected and worked fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994601
Title:
[UBUNTU 18.04] Ubuntu
Hi Christian, all,
both kernels are now ready:
1) with "s390/archrandom: simplify back to earlier design and initialize
earlier" reverted:
f98553359746 (HEAD -> master-next) Revert "s390/archrandom: simplify back to
earlier design and initialize earlier"
Another build is running right now at
https://launchpad.net/~fheimes/+archive/ubuntu/test2
with 's390/archrandom: simplify back to earlier design and initialize earlier'
still in and 's390/setup: init jump labels before command line parsing' on top.
This will take a while - will test it
A test kernel is being build at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/test
(will be available in some minutes)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994601
Hi Harald, see my previous comment - I could recreate this on z15 now (but it's
fine on z13).
So seems to be related to (z14) z15 and newer?!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ah - interesting.
I could recreate the situation on z15 / L1III:
$ virsh start bionic --console
Domain 'bionic' started
Connected to domain 'bionic'
Escape character is ^] (Ctrl + ])
ubuntu@z15test:~$
There is obviously a difference in the behavior of the z13 and z15.
I can create a test
Since the Ubuntu kernel team does for every kernel update and SRU regression
testing, a non-bootable kernel would have been identified and the kernel would
not have left -proposed, it would even not have landed in -proposed.
That makes me think that the issue is elsewhere - at the KVM host
Again, 18.04.5 installations for for me, I used this (latest) 18.04.5 ISO:
https://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.5-server-s390x.iso
If there is a reason to revert 's390/archrandom: simplify back to
earlier design and initialize earlier' we could consider that, but works
Btw. for the KVM guest install I used:
sudo qemu-img create -f qcow2 /var/lib/libvirt/images/bionic.qcow2 8G
sudo virt-install --name bionic --vcpus 2 --ram 1024 --disk
path=/var/lib/libvirt/images/bionic.qcow2,size=5,bus=virtio,format=qcow2
--os-type linux --os-variant generic --network
Trying to recreate, I was just able:
- to successfully complete an 18.04 installation on a 22.10 host (that what I
just had at hand) and
- a successful 18.04 installation on a z/VM 6.4 host
I selected in both cases the strongly recommended option 'Install security
updates automatically'.
(And
Thanks for reporting this.
What is the version of the Ubuntu host where you want to install the 18.04
guest onto?
So that I can try to properly recreate this.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994601
14 matches
Mail list logo
