Re: Lenny installer hanging?
I have also come across the same problem as Adam on a FLEX-ES system running z/VM 5.2 where it hangs in exactly the same place. A quick test of just IPL'ing under Hercules from tape though works just fine so I just need to test using tape on FLEX-ES under z/VM. One thing that might be a problem is that FLEX-ES does not support QDIO and this version of Debian only supports CTC, QETH and IUCV so instead of defining OSA in the FLEX-ES configuration file you might want to try CTC instead (which is what I did under Hercules.) -- MfG / Best Regards Sebastian -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny installer hanging?
On Thu, Jan 08, 2009 at 03:06:04PM -0600, Adam Thornton wrote: So, is there something I'm doing wrong? Not that I spot anything. This is a perfectly normal (if slow) z/VM development system (yes, it's actually emulated, but for all that, IBM still recognizes Flex boxes as being legitimate s390x machines until the last dongle has expired!). It runs Etch, SLES10, and CentOS 4.4 just fine, and it runs z/VM 5.2 and z/OS 1.9 fine too. Etch, SLES10 and CentOS 4.4 are much older. Is there something in newer Linux kernels that requires z9 or later functionality? No. They work fine on z900. Can you try if a new kernel will work at all on this system? Bastian -- Killing is stupid; useless! -- McCoy, A Private Little War, stardate 4211.8 -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny installer hanging?
It seems that 2.6.26-2.6.27 have a regression that hangs my machine during startup of the kernel, that has something to do with HPET. I can stop it by using hpet=disable. It seems other people have trouble with other chipsets, too. 2.6.28 seems to be fine. Maybe it's the same bug? Though my machine is x86_64, it might be a valid speculation. Cheers Dan -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny installer hanging?
Dan Dart wrote: It seems that 2.6.26-2.6.27 have a regression that hangs my machine during startup of the kernel, that has something to do with HPET. I can stop it by using hpet=disable. It seems other people have trouble with other chipsets, too. 2.6.28 seems to be fine. Maybe it's the same bug? Though my machine is x86_64, it might be a valid speculation. Cheers Dan Err.. We're talking about a s390/s390x issue here.. (namely a problem with booting/IPLing the s390 Lenny debian install from within IBM's z/VM) I don't think HPET applies here.. (correction.. I am *certain* HPET doesn't apply here).. But thanks for the suggestion Dan ! Bastian.. I did encounter that problem too.. In a totally different environment.. (still under z/VM).. Especially the di that can be found at http://ftp.nl.debian.org/debian/dists/unstable/main/installer-s390/20081029/images/ is broken. - or at least, in my case, hanging at the place/same circumstances as indicated by Adam.. And using the etch one (http://ftp.nl.debian.org/debian/dists/etch/main/installer-s390/current/images/tape/) is a pain in the neck because there is a (known) mismatch between the kernel and /lib/modules (it can be overcome.. mv modprobe do wonders.. but it's not seamless !).. Once the installer is done (after having jumped through all the hoops), there is no problem upgrading to a newer kernel. (which seem to indicate a recent kernel doesn't have a problem in that environment). The question is : would it be possible to have a more recent DI build for s390 (more recent than October 27th 2008) - and especially with a newer kernel ? (note that 2.6.25 might be an issue. (there is a PSF/PRSSD issue that's of some concern to me) 2.6.26 version updated by Frans Pop should be fine.. and 2.6.27 shouldn't have any problem).. a current unstable (and possibly testing) linux-2.6-s390(x) unstable should do anyway. -Ivan (PS : Sorry dan .. you're going to get this one in duplicate.. I'm so used to hitting 'reply' to reply to a mailing list I didn't realize I was sending my response to you only instead of the ML). smime.p7s Description: S/MIME Cryptographic Signature
Re: Lenny installer hanging?
On Jan 9, 2009, at 12:24 PM, Dan Dart wrote: It seems that 2.6.26-2.6.27 have a regression that hangs my machine during startup of the kernel, that has something to do with HPET. I can stop it by using hpet=disable. It seems other people have trouble with other chipsets, too. 2.6.28 seems to be fine. Maybe it's the same bug? Though my machine is x86_64, it might be a valid speculation. Tried with parmline ro locale=C hpet=disable But same symptoms. Hangs after initializing cgroup subsys devices Adam -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny installer hanging, replace SUSE with Lenny
booting/IPLing the s390 Lenny debian install from within IBM's z/VM) Whoops. Got the wrong end of the stick. I was thinking boot problems with the kernel... since we're using the same (ish) kernel and both having problems with freezing, I thought it might have some similarity. Never mind. Plus. does anyone have a safe way to replace SUSE with Debian while running SUSE? (This IS on s/390 now, haha) I have experimented with debootstrap and have found it to be a great tool. But how would I go about making it permanent? Do I make sure openssh-server is installed, install debian from inside a chroot, to outside it, or is there a better way? Cheers Dan -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny installer hanging?
Ivan Warren wrote: The question is : would it be possible to have a more recent DI build for s390 (more recent than October 27th 2008) - and especially with a newer kernel ? You could try a daily built image from [1], which uses 2.6.26-12 (current unstable/testing kernel based on upstream 2.6.26.8). note that 2.6.25 might be an issue. Hmmm? The Lenny RC1 image also uses 2.6.26, though based on a somewhat older upstream stable update. So .25 cannot be an issue here. PSF/PRSSD issue that's of some concern to me) 2.6.26 version updated by Frans Pop should be fine.. and 2.6.27 shouldn't have any problem) 2.6.27 is likely to get skipped for Debian as the kernel will not be updated until after Lenny is released and that will certainly be with 2.6.26. Cheers, FJP [1] http://www.debian.org/devel/debian-installer/ signature.asc Description: This is a digitally signed message part.
Re: Lenny installer hanging
Lenny 2.6.26-1 fails identically to Lenny d-i. (after aptitude dist- upgrade). Frans Pop reassigned bug 511334 to the kernel, which seems right. Etchnhalf kernel is fine. Adam -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny installer hanging, replace SUSE with Lenny
Here's how I'd do it: Set up a new disk (this does require that you can get a new chunk of DASD; under z/VM, of course, this is usually really easy. LPAR, not so much.) Mount it from the SuSE system. Bind-mount /sys, /proc, /dev debootstrap into the new disk run mkinitrd/zipl on the new disk Then shutdown the SuSE system and IPL from the new device. Adam I can't really do this.. I only have one disk (DASD), and I have to do it INSIDE the VM environment... I'm not the admin, I have root on one of the VMs, that's it. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Lenny installer hanging?
I don't seem to be able to boot (under z/VM 5.2 on a Flex-ES machine) the Lenny RC1 installer. Sometimes the session hangs just after memory detection. Sometimes I get to device detection. Here's the spooled console: Ready; T=0.01/0.01 15:21:14 access 19f d Ready; T=0.01/0.01 15:21:23 listf * * d DEBIAN EXEC D1 INITRD DEBIAN D1 KERNEL DEBIAN D1 PARMFILE DEBIAN D1 Ready; T=0.01/0.01 15:21:32 debian 003 FILES PURGED RDR FILE 0009 SENT FROM LENNYPUN WAS 0009 RECS 042K CPY 001 A NOHOLD NOKEEP RDR FILE 0010 SENT FROM LENNYPUN WAS 0010 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0011 SENT FROM LENNYPUN WAS 0011 RECS 035K CPY 001 A NOHOLD NOKEEP 003 FILES CHANGED 003 FILES CHANGED Ö0.00Ü Initializing cgroup subsys cpuset Ö0.00Ü Initializing cgroup subsys cpu Ö0.00Ü Linux version 2.6.26-1-s390 (Debian 2.6.26-8) (wa...@debian.org ) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1 .2-23)) #1 SMP Thu Oct 9 14:15:49 UTC 2008 Ö0.00Ü We are running under VM (31 bit mode) Ö0.00Ü This machine has an IEEE fpu Ö0.00Ü Zone PFN ranges: Ö0.00Ü Normal 0 -32768 Ö0.00Ü Movable zone start PFN for each node Ö0.00Ü early_node_mapÖ1Ü active PFN ranges Ö0.00Ü 0:0 -32767 Ö0.00Ü Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 32511 Ö0.00Ü Kernel command line: ro locale=C Ö0.00Ü Ö0.00Ü PID hash table entries: 512 (order: 9, 2048 bytes) Ö17179569.187036Ü console ÖttyS0Ü enabled Ö17179569.188091Ü Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Ö17179568.189257Ü Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Ö17179568.198595Ü Memory: 122536k/131072k available (2270k kernel code, 0k reser ved, 842k data, 148k init) ===NOTE FROM ADAM: this hung for a long time, so I restarted it and upped the storage from 128 to 512M=== CP IPL CMS z/VM V5.2.02008-02-12 13:23 DMSACR1240E You are not authorized to connect to file pool USER01 Ready; T=0.03/0.05 15:24:15 def stor 512M STORAGE = 512M Storage cleared - system reset. IPL CMS z/VM V5.2.02008-02-12 13:23 DMSACR1240E You are not authorized to connect to file pool USER01 Ready; T=0.03/0.04 15:24:26 acc 19f D Ready; T=0.01/0.01 15:24:37 Ready; T=0.01/0.01 15:26:34 debian 003 FILES PURGED RDR FILE 0012 SENT FROM LENNYPUN WAS 0012 RECS 042K CPY 001 A NOHOLD NOKEEP RDR FILE 0013 SENT FROM LENNYPUN WAS 0013 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0014 SENT FROM LENNYPUN WAS 0014 RECS 035K CPY 001 A NOHOLD NOKEEP 003 FILES CHANGED 003 FILES CHANGED Ö0.00Ü Initializing cgroup subsys cpuset Ö0.00Ü Initializing cgroup subsys cpu Ö0.00Ü Linux version 2.6.26-1-s390 (Debian 2.6.26-8) (wa...@debian.org ) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1 .2-23)) #1 SMP Thu Oct 9 14:15:49 UTC 2008 Ö0.00Ü We are running under VM (31 bit mode) Ö0.00Ü This machine has an IEEE fpu Ö0.00Ü Zone PFN ranges: Ö0.00Ü Normal 0 - 131072 Ö0.00Ü Movable zone start PFN for each node Ö0.00Ü early_node_mapÖ1Ü active PFN ranges Ö0.00Ü 0:0 - 131071 Ö0.00Ü Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 130047 Ö0.00Ü Kernel command line: ro locale=C Ö0.00Ü Ö0.00Ü PID hash table entries: 2048 (order: 11, 8192 bytes) Ö17179568.189070Ü console ÖttyS0Ü enabled Ö17179568.197213Ü Dentry cache hash table entries: 65536 (order: 6, 262144 bytes ) Ö17179569.214577Ü Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Ö17179569.247170Ü Memory: 511872k/524288k available (2270k kernel code, 0k reser ved, 842k data, 148k init) Ö17179568.251718Ü Write protected kernel read-only data: 0x12000 - 0x2edfff Ö17179568.254542Ü Security Framework initialized Ö17179568.254634Ü SELinux: Disabled at boot. Ö17179569.254734Ü Capability LSM initialized Ö17179569.256117Ü Mount-cache hash table entries: 512 Ö17179568.262898Ü Initializing cgroup subsys ns Ö17179569.263033Ü Initializing cgroup subsys cpuacct Ö17179568.263242Ü Initializing cgroup subsys devices CP SPOOL CONS CLOSE (that's where I gave up waiting and sent the console back to my CMS useridthe guest is still there but I have little hope that it will continue) In addition to the hang, the control characters, which doubtless look fine on a VT220 or ANSI terminal, are nasty on a 3270. This would seem to be a kernel decision, though, so doubt we can change it. So, is there something I'm doing wrong? This is a perfectly normal (if slow) z/VM development system (yes, it's actually emulated, but for all that, IBM still recognizes Flex boxes as being legitimate s390x machines until the last dongle has expired!). It runs Etch, SLES10, and CentOS 4.4 just fine, and it
