9bfc04f9ef
The POP states that for a list directed IPL the IPLB is stored into memory by the machine loader and its address is stored at offset 0x14 of the lowcore. ZIPL currently uses the address in offset 0x14 to access the IPLB and acquire flags about secure boot. If the IPLB address points into memory which has an unsupported mix of flags set, ZIPL will panic instead of booting the OS. As the lowcore can have quite a high entropy for a guest that did drop out of protected mode (i.e. rebooted) we encountered the ZIPL panic quite often. Signed-off-by: Janosch Frank <frankja@linux.ibm.com> Tested-by: Marc Hartmayer <mhartmay@linux.ibm.com> Message-Id: <20200304114231.23493-19-frankja@linux.ibm.com> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com> Reviewed-by: David Hildenbrand <david@redhat.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> |
||
---|---|---|
.. | ||
bootmap.c | ||
bootmap.h | ||
bswap.h | ||
cio.c | ||
cio.h | ||
dasd-ipl.c | ||
dasd-ipl.h | ||
helper.h | ||
iplb.h | ||
jump2ipl.c | ||
libc.c | ||
libc.h | ||
main.c | ||
Makefile | ||
menu.c | ||
netboot.mak | ||
netmain.c | ||
s390-arch.h | ||
s390-ccw.h | ||
sclp.c | ||
sclp.h | ||
scsi.h | ||
start.S | ||
virtio-blkdev.c | ||
virtio-net.c | ||
virtio-scsi.c | ||
virtio-scsi.h | ||
virtio.c | ||
virtio.h |