Thanks for the suggestion Mark, here is what I've found out.
When I run the trace after the IPL gets stuck I see the same four
instructions
repeated over and over again.
00013960' SLR 1F00 CC 2
00013962' CS BA01C000 0020F060 CC 1
00013966' BRM A744FFFB -> 0001395C' CC 1
-> 0001395C' DIAG 83000044 00000044 CC 1
When I look at the System.map created with the 2.4.18 kernel I can see the
addresses
fall within the range for '00013904 T die'
I have compared the System.map files for the new and old kernel around the
die address
and I've noticed that there are some new instructions that were added. Not
sure if it's
important, but I wanted to point it out.
On the old System.map I have:
00013240 T _zb_findmap
00013340 T die
But on the new I have:
000132a0 T _zb_findmap
000133a0 T show_trace
000134dc T show_trace_task
00013514 T show_stack
000135d0 T show_registers
000137c0 T task_show_regs
00013904 T die
Any ideas ??
Thanks again!
Josh Konkol, CNE MCSE
Senior Network Analyst
GuideOne Insurance
Mail Stop AB-1
515-267-2427
[EMAIL PROTECTED]
.~.
/V\
/( )\
^^-^^
-----Original Message-----
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 4:00 PM
To: [EMAIL PROTECTED]
Subject: Re: HELP-2.4.18 Kernel upgrade
Josh,
What you could do is, once the system appears to be "stuck", use CP to turn
on instruction tracing. Let that run for a bit to gather some information,
and then stop it. Re-boot to your previous kernel, and compare the
addresses in your trace to the System.map file that was generated by your
kernel compile. That'll give you some hint as to where you are in the code.
Then, you can re-post here with the information, possibly send it to
[EMAIL PROTECTED] for some help.
Mark Post
-----Original Message-----
From: Konkol, Josh [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 29, 2002 2:01 PM
To: [EMAIL PROTECTED]
Subject: HELP-2.4.18 Kernel upgrade
Sorry if I'm sending this to the wrong list, if there's anyone who can point
me in the right direction I'd appreciate it!
We are running Suse 2.4.7 kernel on s/390 under z/VM. I need to update the
kernel to level 2.4.18 to enable me to apply a patch to add ACL/EA support.
For the meantime I'm just trying to upgrade to 2.4.18.
I was able to successfully build the kernel. I then copied the image,
System.map, ipleckd.boot files to a directory under /boot. To update the
module dependancies I ran: 'depmod -a -F /boot/kernel-2.4.18/System.map
2.4.18'. I then ran 'zipl --image /boot/kernel-2.4.18/image' Both ran fine
with no errors.
After IPL'ing the instance it just gets stuck at 'POSIX conformance testing
by UNIFIX'. Here is the output I get when connected to VM:
hwc low level driver: can write messages
hwc low level driver: can not read state change notifications
hwc low level driver: can read commands
hwc low level driver: can read priority commands
Linux version 2.4.18 (root@files01d) (gcc version 2.95.3 20010315 (SuSE)) #1
SMP Mon Apr 29 08:43:42 CDT 2002
We are running under VM
This machine has an IEEE fpu
On node 0 totalpages: 32768
zone(0): 32768 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: dasd=0200,0201 root=/dev/dasdb1 noinitrd
Highest subchannel number detected (hex) : 000F
Calibrating delay loop... 240.02 BogoMIPS
Memory: 125420k/131072k available (2005k kernel code, 0k reserved, 658k
data, 52k init)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
debug: Initialization complete
POSIX conformance testing by UNIFIX
Any help is appreciated !!
Josh Konkol, CNE MCSE
Senior Network Analyst
GuideOne Insurance
Mail Stop AB-1
515-267-2427
[EMAIL PROTECTED]
.~.
/V\
/( )\
^^-^^
