Very First IPL
Ready; T=0.01/0.01 07:00:52
TRACE I R 10000
Ready; T=0.01/0.01 07:01:18
TRACE ST INTO 10480.32
Ready; T=0.01/0.01 07:01:32
ipl 62c clear
00: Tracing active at IPL
00: -> 000020D0 MVC D2FF20001000 >> 00010480 00001000 CC 0
00: B
00: -> 00010000 BASR 0DD0 CC 0
00: D TX10480.16
00: R00010480 64617364 3D363230 2D363266 20726F6F 06 *dasd=620-62f roo*
00: R00010490 743D2F64 65762F64 6173646D 310A0000 *t=/dev/dasdm1...*
00: B
Failed restart . 3 worked this is the 4th.
Tracing active at IPL
00: -> 000020D0 MVC D2FF20001000 >> 00010480 00001000 CC 0
00: B
00: -> 00010000 BASR 0DD0 CC 0
00: D TX10480.16
00: R00010480 5B47656E 6572616C 5D0A556E 69717565 06 *�General�.Unique*
00: R00010490 49443D31 6851342E 48624B43 68665276 *ID=1hQ4.HbKChfRv*
00: B
00: hwc low level driver: can write messages
00: hwc low level driver: can not read state change notifications
00: hwc low level driver: can receive signal quiesce
00: hwc low level driver: can read commands
00: hwc low level driver: can read priority commands
Linux version 2.4.19-3suse-SMP ([EMAIL PROTECTED]) (gcc version 3.2) #1 SMP Wed Nov 6
22:34:43 UTC 2002
We are running under VM (31 bit mode)
This machine has an IEEE fpu
On node 0 totalpages: 262144
zone(0): 262144 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Building zonelist for node : 0
Kernel command line: �General�
UniqueID=1hQ4.HbKChfRvG13
HWClass=disk
Model=S390 Disk
�Status�
Configured=yes
Available=yes
Needed=no
�Hardware�
Bus=0x8b
Slot=0x6
Function=0x2d
BaseClass=0x106
DeviceName=S390 Disk
UnixDevice=/dev/dasdn
ROMID=062D
Res.Size=3,601020,4096
Res.DiskGeometry=3339,15,12,1
Highest subchannel number detected (hex) : 000F
Calibrating delay loop...
627.50 BogoMIPS
Memory: 1032100k/1048576k available (1706k kernel code, 0k reserved, 396k data, 56k
init)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
debug: Initialization complete
POSIX conformance testing by UNIFIX
Detected 2 CPU's
Boot cpu address 0
cpu 0 phys_idx=0 vers=FF ident=02A07A machine=2066 unused=0000
cpu 1 phys_idx=1 vers=FF ident=02A07A machine=2066 unused=0000
migration_task 0 on cpu=0
migration_task 1 on cpu=1
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
kinoded started
VFS: Diskquotas version dquot_6.5.0 initialized
aio_setup: num_physpages = 65536
aio_setup: sizeof(struct page) = 44
pty: 256 Unix98 ptys configured
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 16 devices)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
debug: cio_msg: new level 6
debug: cio_trace: new level 6
debug: cio_crw: new level 6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 64Kbytes
TCP: Hash tables configured (established 131072 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 636k freed
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 14k freed
�General�: Can't open �General�
Kernel panic: Attempted to kill init!
00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU
01.
01: HCPGIR450W CP entered; disabled wait PSW 000A0000 80028872
00: D TX10480.16
00: V00010480 5B47656E 6572616C 5D0A556E 69717565 06 *�General�.Unique* L00010480
00: V00010490 49443D31 6851342E 48624B43 68665276 *ID=1hQ4.HbKChfRv*
00: I CMS
00: Tracing active at IPL
z/VM V4.3.0 2002-10-15 17:04
DMSACP723I D (192) R/O
Ready; T=0.01/0.02 07:08:57
close console
----- Original Message -----
From: "Lucius, Leland" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 25, 2003 8:34 PM
Subject: Re: Corrupted Kernel?
> First off, do you have my "multiboot" patch on? :-)
>
> As you can see, the command line area of storage (0x10480) is getting
> corrupted. But, what's strange about it is that the bootloader reloads it
> from disk even when you do a "shutdown -r" so it's kind of an interesting
> problem.
>
> Does it always show the same garbage for the command line when it fails?
> The stuff in the log you sent was from the hwinfo package and a hwscan runs
> at boot time, but that doesn't mean it's the problem. The information is
> stored in /var/lib/hardware or you can see it by using the "hwinfo" command.
>
> If you're willing to play a bit, it might be kind of interesting to see what
> the following produces. It isn't gonna fix your problem, but it "might"
> help track it down.
>
> Get into CMS and set a breakpoint:
>
> TRACE I R 10000
>
> And just for fun to try and catch the culprit:
>
> TRACE ST INTO 10480.32
>
> Start your IPL: (use correct address)
>
> I 62C
>
> You should break when the bootloader moves the command line to 0x10480:
>
> 00: -> 000020E6 MVC D2FF20001000 >> 00010480 00001000 CC 0
>
> Continue with the IPL:
>
> B
>
> When you hit the breakpoint you should receive something like:
>
> 00: Tracing active at IPL
> 00: -> 00010000 LM 980F0180 00000180 CC 0
>
> Now, issue this command to display the contents of your command line:
>
> D TX10480.16
>
> It should produce something like this:
>
> 00: R00010480 8481A284 7EF6F2F0 60F6F286 40999696 06 *dasd=620-62f roo*
> 00: R00010490 A37E6184 85A56184 81A28494 F10A0000 *t=/dev/dasdm1...*
>
> Continue with the IPL:
>
> B
>
> After the IPL is done, display the command line contents again:
>
> D TX10480.16
>
> We should see the same contents:
>
> 00: V00010480 8481A284 7EF6F2F0 60F6F286 40999696 06 *dasd=620-62f roo*
> 00: V00010490 A37E6184 85A56184 81A28494 F10A0000 *t=/dev/dasdm1...*
>
> Now, do the reboot:
>
> shutdown -r now
>
> And try the above steps again until it fails. Then display the storage
> again:
>
> D TX10480.16
>
> Like I said, it taint gonna fix your problem, but it "might" be worth the
> exercise.
>
> Leland
