qemu-e2k/pc-bios/s390-ccw
Christian Borntraeger 5d739a4787 s390-ccw.img: Fix sporadic errors with ccw boot image - initialize css
We have to set the cssid to 0, otherwise the stsch code will
return an operand exception without the m bit. In the same way
we should set m=0.

This case was triggered in some cases during reboot, if for some
reason the location of blk_schid.cssid contains 1 and m was 0.
Turns out that the qemu elf loader does not zero out the bss section
on reboot.

The symptom was an dump of the old kernel with several areas
overwritten. The bootloader does not register a program check
handler, so bios exception jumped back into the old kernel.

Lets just use a local struct with a designed initializer. That
will guarantee that all other subelements are initialized to 0.

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
2014-02-27 09:51:26 +01:00
..
bootmap.c
cio.h s390/IPL: Allow boot from other ssid than 0 2013-07-29 12:02:00 +02:00
main.c s390-ccw.img: Fix sporadic errors with ccw boot image - initialize css 2014-02-27 09:51:26 +01:00
Makefile
s390-ccw.h s390/IPL: Allow boot from other ssid than 0 2013-07-29 12:02:00 +02:00
sclp-ascii.c
sclp.h
start.S S390: BIOS boot from given device 2013-05-06 17:30:01 +02:00
virtio.c s390-ccw.img: Fix sporadic reboot hangs: Initialize next_idx 2014-02-27 09:51:25 +01:00
virtio.h s390/ipl: Fix waiting for virtio processing 2013-09-20 12:46:53 +02:00