What you did looks OK for the purposes of getting this figured out. Did you try to reboot your system from 1B26 after doing this? Did you get the same results?
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Taraka Srinivas Kumar Sent: Tuesday, May 04, 2004 4:31 AM To: [EMAIL PROTECTED] Subject: Re: Central processor is looping when 64 bit linux is IPLed Hi all, Thanks for the responses. I have tried what Mark suggested. Below is the procedure I have followed as per your instructions. Please correct me if I am wrong. 1. IPLed the LPAR from CD-ROM 2. Issued the following commands after logging in. 1b26 - root, 1b27 - /usr, 1b28 - swap devices. * * * * *insmod dasd_mod=1b26-1b28 * * * * *insmod dasd_eckd_mod * * * * *cat /proc/dasd/devices * * * * *mount /dev/dasda1 /mnt * * * * *mount /dev/dasdb1 /mnt/usr Note : "dd" command worked without chrooting to /mnt * * * * *dd if=/dev/dasda bs=512 count=20 | od -x 0000000 0000 0000 0008 0000 8000 2008 0600 0218 0000020 6000 0090 0800 0228 0000 0000 e5e5 e5e5 0000040 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0010000 0200 0000 0950 000b 0810 0000 0000 0000 0010020 0000 0000 0700 02a0 6000 0006 3100 02a2 0010040 6000 0005 0800 0230 0000 0000 0600 2000 0010060 2000 1000 0600 0000 6000 0000 0600 0000 0010100 6000 0000 0600 0000 6000 0000 0600 0000 * 0010200 6000 0000 0600 0000 2000 0000 0000 0000 0010220 0000 0400 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0010240 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0020000 ffff ffff ffff ffff ffff ffff ffff ffff 20+0 records in * 0020060 ffff ffff ffff ffff ffff ffff ffff ff00 20+0 records out 0020100 0000 0000 0000 0000 0000 0000 0000 0000 0020120 0000 0000 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0020140 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0024000 * * * * *dd if=/dev/dasdb bs=512 count=20 | od -x 0000000 0000 0000 0000 0000 0000 0000 0000 0000 0000020 0000 0000 0000 0000 0000 0000 e5e5 e5e5 0000040 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0010000 0200 0000 0300 0000 0400 0000 087e d53d 0010020 0200 0000 0000 0000 0000 0000 0000 0000 0010040 0280 0000 0380 0000 0480 0000 0d7e e03d 0010060 0000 0000 0000 0000 0000 0000 0000 0000 0010100 0000 0100 0100 0100 0400 0100 0f7e e03d 0010120 0000 0000 0000 0000 0000 0000 0000 0000 0010140 0280 0100 0380 0100 0480 0100 0d7e e03d 0010160 0000 0000 0000 0000 0000 0000 0000 0000 0010200 0000 0200 0100 0200 0400 0200 0f7e e03d 0010220 0000 0000 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0010240 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 20+0 records in 0020000 ffff ffff ffff ffff ffff ffff ffff ffff 20+0 records out * 0020060 ffff ffff ffff ffff ffff ffff ffff ff00 0020100 0000 0000 0000 0000 0000 0000 0000 0000 0020120 0000 0000 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0020140 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0024000 * * * * *Edited the zipl.conf as follows: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters="dasd=1b26-1b28 root=/dev/dasda1" [dumpdasd] target=/mnt/boot/zipl dumpto=/mnt/dev/dasd?? [dumptape] target=/mnt/boot/zipl dumpto=/mnt/dev/rtibm0 * * * * *zipl -c /etc/zipl.conf building bootmap : /mnt/boot/zipl/bootmap adding Kernel Image : /mnt/boot/kernel/image located at 0x00010000 adding Ramdisk : /mnt/boot/initrd located at 0x00800000 adding Parmline : /mnt/boot/zipl/parmfile located at 0x00001000 Bootloader for ECKD type devices with z/OS compatible layout installed. Syncing disks.... ...done * * * * *dd if=/dev/dasda bs=512 count=20 | od -x 0000000 0000 0000 0008 0000 8000 2008 0600 0218 0000020 6000 0090 0800 0228 0000 0000 e5e5 e5e5 0000040 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0010000 0200 0000 0019 0004 0210 0000 0000 0000 0010020 0000 0000 0700 02a0 6000 0006 3100 02a2 0010040 6000 0005 0800 0230 0000 0000 0600 2000 0010060 2000 1000 0600 0000 6000 0000 0600 0000 0010100 6000 0000 0600 0000 6000 0000 0600 0000 * 0010200 6000 0000 0600 0000 2000 0000 0000 0000 0010220 0000 0400 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0010240 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 20+0 records in 20+0 records out 0020000 ffff ffff ffff ffff ffff ffff ffff ffff * 0020060 ffff ffff ffff ffff ffff ffff ffff ff00 0020100 0000 0000 0000 0000 0000 0000 0000 0000 0020120 0000 0000 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0020140 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0024000 * * * * *dd if=/dev/dasdb bs=512 count=20 | od -x 0000000 0000 0000 0000 0000 0000 0000 0000 0000 0000020 0000 0000 0000 0000 0000 0000 e5e5 e5e5 0000040 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0010000 0200 0000 0300 0000 0400 0000 087e d53d 0010020 0200 0000 0000 0000 0000 0000 0000 0000 0010040 0280 0000 0380 0000 0480 0000 0d7e e03d 0010060 0000 0000 0000 0000 0000 0000 0000 0000 0010100 0000 0100 0100 0100 0400 0100 0f7e e03d 0010120 0000 0000 0000 0000 0000 0000 0000 0000 0010140 0280 0100 0380 0100 0480 0100 0d7e e03d 0010160 0000 0000 0000 0000 0000 0000 0000 0000 0010200 0000 0200 0100 0200 0400 0200 0f7e e03d 0010220 0000 0000 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0010240 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 20+0 records in 20+0 records out 0020000 ffff ffff ffff ffff ffff ffff ffff ffff * 0020060 ffff ffff ffff ffff ffff ffff ffff ff00 0020100 0000 0000 0000 0000 0000 0000 0000 0000 0020120 0000 0000 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 0020140 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 e5e5 * 0024000 It seems that /dev/dasda is getting modified which is my root device. Anything that can be concluded from the above results ? Hi Jim, We are having an evaluation copy of SuSE Linux 8.0 64 bit for zSeries. Thanks and Regards, Srinivas. "Post, Mark K" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 05/01/04 09:55 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: Central processor is looping when 64 bit linux is IPLed Just a wild guess, but it sounds as though the IPL text wasn't written to the IPL volume, or perhaps it was, but to a different volume. Try IPLing from tape, and using the "dd" command to dump the beginning of the volume you believe to contain the IPL text: dd if=/dev/dasda bs=512 count=20 | od -x You may need to mount your DASD volumes and chroot to them to get access to all those commands. Also, check your other DASD volumes in the same way. Finally, do a chroot to the root file system, and re-run zipl, and see if it complains about anything. If not, then dump the beginning of the DASD volume again to see if it looks any different. Note that you will be specifying the "whole volume" device node, not any of the partition nodes. So, use dasda and not dasda1, dasdb and not dasdb1, etc. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Taraka Srinivas Kumar Sent: Saturday, May 01, 2004 7:53 AM To: [EMAIL PROTECTED] Subject: Fw: Central processor is looping when 64 bit linux is IPLed Guys, Resending the same query again. I am installing 64 bit linux SuSE 8.0 in LPAR mode on zSeries. Completed all the Yast partitioning and package selection. Even installation using Yast went thru fine without any problems. When i IPL the Linux LPAR with the root dasd address, it throws the following hardware error message. An error was detected in partition LINXLPAR. Central processor (CP) 00 is looping due to switching between program status words (PSWs) that are not valid. The program status word(PSW) is 00000000000000000000000000000000 - ( 32 zeroes). Any inputs ? Regards, Srinivas. ----- Forwarded by Taraka Srinivas/CHN/TCS on 05/01/04 05:21 PM ----- Taraka Srinivas/CHN/TCS 04/30/04 07:34 PM To Linux on 390 Port <[EMAIL PROTECTED]> cc Subject Central processor is looping when 64 bit linux is IPLedLink <Notes:///65256DF50026ABCF/DABA975B9FB113EB852564B5001283EA/B5B13346040B1B3B 65256E85007CA1E0> Hi all, I am installing 64 bit linux SuSE 8.0 in LPAR mode on zSeries. Completed all the Yast partitioning and package selection. Even installation using Yast went thru fine without any problems. When i IPL the Linux LPAR with the root dasd address, it throws the following hardware error message. An error was detected in partition LINXLPAR. Central processor (CP) 00 is looping due to switching between program status words (PSWs) that are not valid. The program status word(PSW) is 00000000000000000000000000000000 - ( 32 zeroes). Anybody aware of this bug ? Is it a problem with the way LPAR profile is customized ? We are having 2 CPUs for this LPAR. Regards, Srinivas. ForwardSourceID:NT000056BE ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ForwardSourceID:NT00005712 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
