Srinivas, I'm at a loss. I would say it's time to call in SUSE and IBM to figure out what's going on. Well, perhaps one more thing. What does the I/O definition for this LPAR look like? Are there any devices defined that you don't plan on using? If so, eliminate everything except those things you know for sure the Linux/390 system will need, and try again.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Taraka Srinivas Kumar Sent: Wednesday, May 05, 2004 2:08 AM To: [EMAIL PROTECTED] Subject: Re: Central processor is looping when 64 bit linux is IPLed Hi Jim/Mark, I have tried the same after chrooting into /mnt/newroot. Also issued mkinitrd,zipl. Re-IPled using 1b26, again the same cpu looping problem re-appears. How to check if the kernel on the disk is 64 bit or not ?? Below is the procedure i have followed : inst-sys:~ # insmod dasd_mod dasd=1b26-1b28 Using /lib/modules/2.4.19-3suse-SMP/kernel/drivers/s390/block/dasd_mod.o inst-sys:~ # insmod dasd_eckd_mod Using /lib/modules/2.4.19-3suse-SMP/kernel/drivers/s390/block/dasd_eckd_mod.o inst-sys:~ # mount /dev/dasda1 /mnt/newroot inst-sys:~ # mount /dev/dasdb1 /mnt/newroot/usr inst-sys:~ # chroot /mnt/newroot inst-sys:~ # vi /etc/zipl.conf # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/boot/zipl image=/boot/kernel/image ramdisk=/boot/initrd parameters="dasd=1b26-1b28 root=/dev/dasda1" [dumpdasd] target=/boot/zipl dumpto=/dev/dasd?? [dumptape] target=/boot/zipl dumpto=/dev/rtibm0 ~ ~ linux64:/# mkinitrd using "/dev/dasda1" as root device (mounted on "/" as "ext2") Found ECKD dasd, adding dasd eckd discipline! Note: If you want to add ECKD dasd support for later mkinitrd calls where possibly no ECKD dasd is found, add dasd_eckd_mod to INITRD_MODULES in /etc/sysconfig/kernel creating initrd "/boot/initrd" for kernel "/boot/kernel/image" (version 2.4.19-3suse-SMP) (s390x) - insmod dasd_mod dasd=$dasd (kernel/drivers/s390/block/dasd_mod.o) - insmod dasd_eckd_mod (kernel/drivers/s390/block/dasd_eckd_mod.o) Run zipl now to update the IPL record! linux64:/# zipl -c /etc/zipl.conf building bootmap : /boot/zipl/bootmap adding Kernel Image : /boot/kernel/image located at 0x00010000 adding Ramdisk : /boot/initrd located at 0x00800000 adding Parmline : /boot/zipl/parmfile located at 0x00001000 Bootloader for ECKD type devices with z/OS compatible layout installed. Syncing disks.... ...done linux64:/#exit Regards, Srinivas. Jim Sibley <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 05/04/04 10:03 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 target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters="dasd=1b26-1b28 root=/dev/dasda1" The /mnt mount should not be there. The purpose of the chroot is to make /mnt the "root" device. Also, since /usr is a separate volume, you need a bit more. After IPL'in the cd, mount /dev/dasda1 /mnt/newroot mount /dev/dasdb1 /mnt/newroot/usr mount proc proc /mnt/newroot/proc chroot /mnt/newroot edit /etc/zipl.conf such that the /mnt is removed run mkinitrd zipl exit (to get out of chroot) sync halt Then boot with your new system. ===== Jim Sibley RHCT, Implementor of Linux on zSeries "Computer are useless.They can only give answers." Pablo Picasso __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ---------------------------------------------------------------------- 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:NT000058E2 ---------------------------------------------------------------------- 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
