Morning/Afternoon/Evening, Possibly ATTN: Bastian, but eventually to anyone with pointers to solutions...
I have been hapilly using 2.4.26, both s390 & s390x, under hercules... Problem 1 : I tried using 2.4.27 and I am currently getting this : <LOG> ipl 108 HHCCP007I CPU0000 architecture mode set to ESA/390 HHCCP041I SYSCONS interface active zIPL v1.3.1 interactive boot menu 0. default (deb2426x) 1. deb268x 2. deb268 3. deb2427x 4. deb2427 5. deb2426x 6. deb2426 7. deb2427isw Please choose (default will boot in 30 seconds): .3 Booting deb2427x... HHCCP042I SYSCONS interface inactive CPU0000: SIGP CPU0000 Set Architecture Mode PARM 00000001 HHCCP007I CPU0000 architecture mode set to ESAME HHCCP041I SYSCONS interface active HHCCP041I SYSCONS interface active Linux version 2.4.27-1-s390x ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian 1:3.3.4-7 )) #1 SMP Tue Aug 17 12:27:26 CEST 2004 We are running native (64 bit mode) On node 0 totalpages: 196608 zone(0): 196608 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/dasd/0108/part1 ro noinitrd dasd=0108,0109 vmpoff ="LOGOFF" BOOT_IMAGE=3 Highest subchannel number detected (hex) : 000B Calibrating delay loop... 164.24 BogoMIPS Memory: 763676k/786432k available (2447k kernel code, 0k reserved, 693k data, 64 k init) Dentry cache hash table entries: 131072 (order: 9, 2097152 bytes) Inode cache hash table entries: 65536 (order: 8, 1048576 bytes) Mount cache hash table entries: 256 (order: 0, 4096 bytes) Buffer cache hash table entries: 65536 (order: 7, 524288 bytes) Page-cache hash table entries: 262144 (order: 9, 2097152 bytes) debug: Initialization complete CPU0000: SIGP CPU0001 Sense PARM 0000000000000000 POSIX conformance testing by UNIFIX Detected 1 CPU's Boot cpu address 0 cpu 0 phys_idx=0 vers=00 ident=000777 machine=2084 unused=0000 Waiting on wait_init_idle (map = 0x0) All processors have done init_idle init_mach : starting machine check handler Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket mach_handler : ready mach_handler : waiting for wakeup Starting kswapd VFS: Disk quotas vdquot_6.5.1 Journalled Block Device driver loaded devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 HHCCP041I SYSCONS interface active pty: 256 Unix98 ptys configured 3270: 001f on sch 0, minor 1 devfs_register(ttyS): could not append to parent, err: -17 dasd: initializing... dasd: Registered successfully to major no 94 dasd(eckd): ECKD discipline initializing dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: 3390/0A(CU:3990/02) Cyl:3339 Head:15 Sec:224 dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: 3390/0A(CU:3990/02): Configuration da ta read dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: (4kB blks): 2404080kB at 48kB/trk com patible disk layout dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 3390/0A(CU:3990/02) Cyl:3339 Head:15 Sec:224 dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 3390/0A(CU:3990/02): Configuration da ta read dasd: waiting for responses... dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: (4kB blks): 2404080kB at 48kB/trk com patible disk layout Partition check: /dev/dasd/0108:VOL1/ LX0108: p1 /dev/dasd/0109:VOL1/ LX0109: p1 dasd(eckd): We are interested in: CU 3880/00 dasd(eckd): We are interested in: CU 3990/00 dasd(eckd): We are interested in: CU 2105/00 dasd(eckd): We are interested in: CU 9343/00 dasd: Registered ECKD discipline successfully dasd(fba): FBA discipline initializing dasd(fba): We are interested in: Dev 9336/00 @ CU 6310/00 dasd(fba): We are interested in: Dev 3370/00 @ CU 3880/00 dasd: Registered FBA discipline successfully dasd: initialization finished RAMDISK driver initialized: 16 RAM disks of 24576K size 1024 blocksize Initializing Cryptographic API chsc: Invalid command chsc_get_sch_descriptions: Error -22 while doing chsc; processing some machine c hecks may not work qdio: loading QDIO base support version 2 ($Revision: 1.145.4.9 $/$Revision: 1.5 7.4.4 $) qdio : Was not able to determine general characteristics of all QDIO devices abo ard. IPv6 v0.8 for NET4.0 IPv6 over IPv4 tunneling driver NET4: Linux TCP/IP 1.0 for NET4.0 IP: routing cache hash table of 2048 buckets, 48Kbytes HHCCD001I Readahead thread 1 started: tid=71CD7BB0, pid=22209 HHCCD001I Readahead thread 2 started: tid=724D7BB0, pid=22209 HHCCD002I Writer thread 1 started: tid=72CD7BB0, pid=22209 HHCCD003I Garbage collector thread started: tid=734D7BB0, pid=22209 TCP: Hash tables configured (established 65536 bind 65536) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 8k freed Warning: unable to open an initial console. </LOG> (Ignore the HHCXXNNNT Messages, these are hercules hardware panel messages).. Beyond that, there is *some* activity, followed by a enabled wait state... Init doesn't even respond to the SCP Shutdown signal - so possibly we didn't actually switch to the *real* init (and still are in initrd init version) - or maybe we haven't finished processing the inittab.. I suspect something has changed in devfs preventing init et al from accessing the SCP System Console... But not much else I have been able to gather.. Problem #2 : When attempting to IPL 2.6.8 : First, I was just getting 'Kernel panic, attempting to kill init'... Ok.. So I suspected that dasd_eckd_mod just wasn't properly detecting my DASDs (possibly because of an hercules glitch in dynamic I/O processing [1]) - So I simply added a 'dasd_mod dasd=0108-010A' to /etc/mkinitrd/modules (my range of dasds I use) - and at least I am seeing the modules registering and detecting the EXT2/3 and swap partitions.. However, it doesn't get much further, still crashing after pivot_root... Of course, I strongly suspect it just isn't getting to mount my root fs.. I tried changing my root from /dev/dasd/0108/part1 to /dev/dasd/0.0.0108/part1 - to no avail.. I also changed the timeout period in /etc/mkinitrd/mkinitrd.conf so at least I get a chance to see what the status of the system is after the modules are loaded... I do have a /dev2/dasd/0.0.0108/part1 (and it is my root fs alright).. Based on that... How should I specify my root device ? Of course, I am ready and willing to provide ANY additional information ! Thanks, --Ivan [1] I am saying this because of : chsc: Invalid command chsc_get_sch_descriptions: Error -22 while doing chsc; processing some machine c hecks may not work But my belief is that this should only affect device to CHPID relationship - which is pretty much meaningless under hercules..
