Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
I think this bug is related to an issue I've seen myself with 2.6.28. The symptoms (point where the boot hangs) are somewhat similar at least. There seems to be a bug in the kernel's timekeeping code which can manifest itself differently depending on the (emulated) hardware clock. My issue was reported upstream in http://lkml.org/lkml/2009/3/7/155. See also http://lkml.org/lkml/2009/3/12/23 and my reply to that. However, it's also possible the above is totally unrelated... Cheers, FJP -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
Actually, a 100 Hz timer seems to work. Then I hang because I didn't load the DASD driver, but I think that's very likely just a problem with my generated RAMDISK. So my recommendation would be to use a 100Hz timer pop for s390 31-bit at least. I wonder if this has anything to do with trying to run on emulated systems whose actual host timer tick is 100Hz? I believe that to be the case for this SLES9 (I think) host for my Flex-box. Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
Fails on released Lenny as well. I'm installing the kernel sources now to see if I can, in fact, build a working 2.6.26 in an otherwise-Lenny environment. If I get something that works on FLEX-ES I'd like for someone to try it on Hercules. Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
Well, my custom kernel (in which, on a hunch, I turned off timer ticks) is still building, but I now have this diagnostic information: If you (under VM) do a CP D P ALL you see that you're generally in scheduler_tick, sometimes in account_user_time_scaled, sometimes tick_switch_to_oneshot. At any rate, it's always some timer routine. So, this may just be telling us that the kernel keeps setting a timer waiting for something to happen, waking up, seeing that whatever hasn't happened, and trying again. But there's another hunch I'm testing: The default ticks Hz value on this kernel was 250. This problem has only appeared on Flex and Hercules. What these have in common is that they're emulated s390 machines, and they're very much slower than the real iron. Might it be that having the jiffy timer popping every 4 ms is interacting badly with what is, effectively, a very very slow variable-clock machine? If that's the case, turning off timer ticks (i.e. CONFIG_NO_HZ=y) may be enough to let me boot, which would be cool. I don't know if that will work on Hercules (or in an LPAR) though. For whatever it's worth, on the etchnhalf system /proc/sys/kernel/hz_timer is 0, which I *think* means the on-demand timer is enabled. Unfortunately, on my system it takes a lot of hours to build a kernel, so I'm not going to be able to test these hypotheses fast. Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
Turning off the timer gets slightly farther, but hangs at 038c18, which is in raise_softirq . So that's not it. Next step: turning the timer back down to 100 Hz. Doubt that's going to help. Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
Also hangs on Hercules. I'm using a D-I daily from about 1/29, though it looks like the kernel was built 1/10. De -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
It fails the same way with Lenny rc2 as previous versions did. Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
reassign 511334 linux-2.6 2.6.26-12 thanks On Friday 09 January 2009, Adam Thornton wrote: S390 boot fails (sometimes just after detecting memory, sometimes after detecting devices) on z/VM 5.2 and a Flex-ES machine. Since there are reports of d-i working on z9 boxes, I suspect the issue is that the kernel is built to exploit later System z functionality. At least for d-i the basic 31-bit-no-frills architecture should be selected as the s390 kernel (and basic 64-bit for s390x, e.g. z900), with options for kernels that exploit later additions to the architecture for installation (ideally based on detected machine type). This sounds like a kernel issue rather than an installer issue. Therefore reassigning to the kernel team. Cheers, FJP -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
Processing commands for cont...@bugs.debian.org: reassign 511334 linux-2.6 2.6.26-12 Bug#511334: debian-installer: S390 boot fails on Flex-ES machine Bug reassigned from package `debian-installer' to `linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511334: debian-installer: S390 boot fails on Flex-ES machine
On Jan 9, 2009, at 1:20 PM, Frans Pop wrote: reassign 511334 linux-2.6 2.6.26-12 thanks On Friday 09 January 2009, Adam Thornton wrote: S390 boot fails (sometimes just after detecting memory, sometimes after detecting devices) on z/VM 5.2 and a Flex-ES machine. Since there are reports of d-i working on z9 boxes, I suspect the issue is that the kernel is built to exploit later System z functionality. At least for d-i the basic 31-bit-no-frills architecture should be selected as the s390 kernel (and basic 64-bit for s390x, e.g. z900), with options for kernels that exploit later additions to the architecture for installation (ideally based on detected machine type). This sounds like a kernel issue rather than an installer issue. Therefore reassigning to the kernel team. OK. I can confirm that 2.6.26-1 as installed via aptitude dist-upgrade from lenny fails in the same way. 2.6.24-etchnhalf was OK. ===begin console log=== Ready; T=0.01/0.01 13:56:33 cp spool cons to adam Ready; T=0.01/0.01 13:56:40 cp spool cons start Ready; T=0.01/0.01 13:56:43 ipl 150 clear zIPL v1.6.2 interactive boot menu 0. default (debian) 1. debian 2. old Note: VM users please use '#cp vi vmsg input' Please choose (default will boot in 10 seconds): Booting default (debian)... Ö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-12) (wa...@debian.org ) (gcc version 4.1.3 20080704 (prerelease) (Debian 4. 1.2-24)) #1 SMP Mon Dec 15 17:10:09 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: root=/dev/disk/by-path/ ccw-0.0.0150-part1 BO OT_IMAGE=0 Ö0.00Ü PID hash table entries: 512 (order: 9, 2048 bytes) Ö17179568.187160Ü console ÖttyS0Ü enabled Ö17179568.189352Ü Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Ö17179568.190397Ü Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Ö17179568.202860Ü Memory: 121428k/131072k available (2272k kernel code, 0k reser ved, 840k data, 148k init) Ö17179569.203017Ü Write protected kernel read-only data: 0x12000 - 0x2edfff Ö17179569.206392Ü Security Framework initialized Ö17179569.206540Ü SELinux: Disabled at boot. Ö17179569.206681Ü Capability LSM initialized Ö17179568.207546Ü Mount-cache hash table entries: 512 Ö17179569.213083Ü Initializing cgroup subsys ns Ö17179569.213277Ü Initializing cgroup subsys cpuacct Ö17179569.213682Ü Initializing cgroup subsys devices [*** HANG occurs here; the CP IPL 150 clear is my interrupt. Then I reboot with the etchnhalf kernel and everything is fine ***] CP IPL 150 CLEAR zIPL v1.6.2 interactive boot menu 0. default (debian) 1. debian 2. old Note: VM users please use '#cp vi vmsg input' Please choose (default will boot in 10 seconds): CP VI VMSG 2 Booting old... Initializing cgroup subsys cpuset Linux version 2.6.24-etchnhalf.1-s390 (Debian 2.6.24-6~etchnhalf.7) (da...@debia n.org) (gcc version 4.1.2 20061115 (prerelease) (Deb ian 4.1.1-21)) #1 SMP Tue Dec 2 16:59:08 UTC 2008 We are running under VM (31 bit mode) This machine has an IEEE fpu Detected 1 CPU's Boot cpu address 0 Zone PFN ranges: Normal 0 -32768 Movable zone start PFN for each node early_node_mapÖ1Ü active PFN ranges 0:0 -32767 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: root=/dev/disk/by-path/ccw-0.0.0150-part1 BOOT_IMAGE=2 PID hash table entries: 512 (order: 9, 2048 bytes) console ÖttyS0Ü enabled Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 122964k/131072k available (2147k kernel code, 0k reserved, 775k data, 14 0k init) Write protected kernel read-only data: 0x12000 - 0x2b8fff Security Framework initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct cpu 0 phys_idx=0 vers=FF ident=030234 machine=1247 unused= Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 debug: Initialization complete Time: tod clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 3, 49152 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 3226k freed audit:
