5:41 a.m.
After various travails I have apparently successfully installed Fedora 23 s390x on
Hercules. However, when I start the installed system I get:-
<--snipped-->
12:33:56 HHC01603I * IPL Fedora
12:33:56 HHC00811I Processor CP00: architecture mode ESA/390
12:33:56 MAN=0
12:33:56 HHC00814I Processor CP00: SIGP Set architecture mode (12) CP00, PARM
00000002: CC 0
12:33:56 HHC00811I Processor CP00: architecture mode z/Arch
12:33:56 HHC01541I HDL: dyngui.dll initiated
12:33:56 Error: undefined configuration
12:33:56 HHC00809I Processor CP00: disabled wait state 0002000080000000 0000000000004511
If I try to use a system I dnf system-upgrade'd from Fedora 21 to Fedora 23 I get:-
10:41:39 HHC00809I Processor CP00: disabled wait state 0002000080000000 0000000000004510
Where are the wait state codes documented?
Ian
12:06 p.m.
On Fri, 20 Nov 2015 11:41:55 -0000
mcisho(a)yahoo.com wrote:
After various travails I have apparently successfully installed
Fedora 23 s390x on Hercules. However, when I start the installed
system I get:-
<--snipped-->
12:33:56 HHC01603I * IPL Fedora
12:33:56 HHC00811I Processor CP00: architecture mode ESA/390
12:33:56 MAN=0
12:33:56 HHC00814I Processor CP00: SIGP Set architecture
mode (12) CP00, PARM 00000002: CC 0 12:33:56 HHC00811I
Processor CP00: architecture mode z/Arch 12:33:56 HHC01541I HDL:
dyngui.dll initiated 12:33:56 Error: undefined configuration
I wonder if the "undefined configuration" error above ^^^ isn't the
problem and where it is coming from ...
12:33:56 HHC00809I Processor CP00: disabled wait state
0002000080000000 0000000000004511
If I try to use a system I dnf system-upgrade'd from Fedora 21 to
Fedora 23 I get:-
10:41:39 HHC00809I Processor CP00: disabled wait state
0002000080000000 0000000000004510
Where are the wait state codes documented?
I think they can be decoded by using the z/Arch Principles of
Operation.
Dan
4:27 a.m.
I instruction traced the Fedora IPL, and the "Error: undefined configuration"
comes from the boot loader (zIPL?). Less than 70,000 instructions were executed between
IPL and disabled wait.
The wait codes, i.e. the 4511 or the 4510, are constructs of the operating system being
IPL'ed, they are not hardware-defined, so Principles of Operation won't help. In
this case the wait code is created by the boot loader.
Is zIPL the boot loader for Fedora s390x?
Ian
11:49 a.m.
On Tue, 22 Dec 2015 10:27:37 -0000
"Ian Shorter" <mcisho(a)yahoo.com> wrote:
I instruction traced the Fedora IPL, and the "Error: undefined
configuration" comes from the boot loader (zIPL?). Less than 70,000
instructions were executed between IPL and disabled wait.
hm, maybe the bootloader isn't installed correctly then. Can you
download the logs from /tmp when the installer asks about rebooting?
Or try to run "zipl -V" manually after "chroot /mnt/sysimage" at this
point?
The wait codes, i.e. the 4511 or the 4510, are constructs of the
operating system being IPL'ed, they are not hardware-defined, so
Principles of Operation won't help. In this case the wait code is
created by the boot loader.
Is zIPL the boot loader for Fedora s390x?
yes, it is
Dan
4:03 a.m.
In my initial post I used the word 'apparently', and now I remember why. This is
the end of the log from an install the other day:-
<---snipped--->
16:22:57 [ 3785.662344] anaconda[1666]: Installing rootfiles.noarch (312/312)
16:22:57 [ 3785.666414] anaconda[1666]: Performing post-installation setup tasks
16:22:57 [ 3785.670589] anaconda[1666]: Installing boot loader
16:22:57 [ 3785.674426] anaconda[1666]: .
16:22:57 [ 3785.698240] anaconda[1666]: Performing post-installation setup tasks
16:23:37 [ 3807.560299] anaconda[1666]: .
16:23:37 [ 3807.564972] anaconda[1666]: Configuring installed system
16:23:44 [ 3811.255378] anaconda[1666]: .
16:23:44 [ 3811.260078] anaconda[1666]: Writing network configuration
16:23:48 [ 3813.450645] anaconda[1666]: .
16:23:48 [ 3813.454583] anaconda[1666]: Creating users
16:23:48 [ 3813.472856] anaconda[1666]: .
16:23:48 [ 3813.476688] anaconda[1666]: Configuring addons
16:36:54 [ 4245.643360] anaconda[1666]: .
16:36:54 [ 4245.651541] anaconda[1666]: Generating initramfs
16:38:11 [ 4288.422818] anaconda[1666]: .
16:38:11 [ 4288.430693] anaconda[1666]: Running post-installation scripts
16:38:11 [ 4288.479280] anaconda[1666]: .
22:39:46 HHC01603I quit
22:39:46 HHC01426I Shutdown initiated
The install doesn't complete. I had forgotten about the reboot, so had assumed that
the post-installation scripts must have come to an end. Silly me.
What info can I obtain when the install stalls?
8:35 a.m.
I tried an install earlier, which stalled at the same place. I've extracted various
log files from the /var/log/anaconda directory, namely:-
anaconda.log
dnf.log
dnf.rpm.log
ifcfg.log
journal.log
packaging.log
program.log
storage.log
syslog
Which would be the most useful? Or something else entirely? Can files be attached to this
list? Or do they need to be cut'n'pasted?
6:49 p.m.
I had the same problem and found a solution on a another linux s390x distribution forum.
I removed LOADPARM from my hercules.cnf file and Fedora 23 s390x started up no problem.
I had no problems with the Fedora 23 s390x install(that I saw) and the hercules.cnf file
did contain the LOADPARM. It was only when I tried to start Fedora 23 s390x that the wait
state occurred.
I am using Fedora 23 x86-64 to host Fedora 23 s390x.
Karl
4:51 a.m.
Unfortunately, removing the LOADPARM made no difference for me.
I'm starting to think this is something to do with boot options and/or kickstart.
I've tinkered and now Anaconda doesn't hang, it terminates, though I still get the
4511 wait state when I try to IPL. What boot options and/or kickstart did you use?
3053
days inactive
3096
days old
7 comments
3 participants
participants (3)
-
Dan Horák -
Ian Shorter -
Karl Lasecki