Go to www.vm.ibm.com/pubs.
Under z/VM 4.2 click on general publications
Pick the pub CP Programming Services
Look at Chapter 2 which has the IBM supplied DIAGS
To: [EMAIL PROTECTED]
"Post, Mark K" cc: (bcc: Michael Short/Towers
Perrin)
<[EMAIL PROTECTED] Subject: Re: HELP-2.4.18 Kernel upgrade
m>
Sent by: Linux on
390 Port
<[EMAIL PROTECTED]
IST.EDU>
05/02/2002 04:11
PM
Please respond to
Linux on 390 Port
Michael,
Are you aware of a web resource anywhere that has a table of what all the
DIAG codes are? That would be a good addition to my links page.
Mark Post
-----Original Message-----
From: Michael Short/Towers Perrin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 3:54 PM
To: [EMAIL PROTECTED]
Subject: Re: HELP-2.4.18 Kernel upgrade
The diag 68, or x'44', is a "voluntary time-slice end"
To:
[EMAIL PROTECTED]
"Post, Mark K" cc: (bcc: Michael
Short/Towers Perrin)
<[EMAIL PROTECTED] Subject: Re: HELP-2.4.18
Kernel upgrade
m>
Sent by: Linux on
390 Port
<[EMAIL PROTECTED]
IST.EDU>
05/02/2002 03:43
PM
Please respond to
Linux on 390 Port
Well, this seems to correlate to this piece of code in
arch/s390/kernel/traps.c
void die(const char * str, struct pt_regs * regs, long err)
{
console_verbose();
spin_lock_irq(&die_lock);
bust_spinlocks(1);
printk("%s: %04lx\n", str, err & 0xffff);
show_regs(regs);
bust_spinlocks(0);
spin_unlock_irq(&die_lock);
do_exit(SIGSEGV);
}
Which seems to correlate to this bit of assembler (even though the register
numbers don't seem to match completely).
.long do_exit
.LTN5_0:
LR 1,15
AHI 15,-104
ST 1,0(15)
L 5,.LC313-.LT5_0(13)
L 1,0(5)
LR 8,2
LR 7,3
LR 11,4
LTR 1,1
JE .L955
LHI 1,15
ST 1,0(5)
.L955:
#APP
stnsm 96(15),0xFC
#NO_APP
L 10,.LC314-.LT5_0(13)
#APP
bras 1,1f
0: diag 0,0,68
1: slr 0,0
cs 0,1,0(10)
jl 0b
I don't know what a DIAG 68 is, but apparently the cs instruction never
sets
a "low" return code, so you never get on with life. Can anyone else add to
the discussion? I'm pretty much in over my head already.
Mark Post
-----Original Message-----
From: Konkol, Josh [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 11:14 AM
To: [EMAIL PROTECTED]
Subject: Re: HELP-2.4.18 Kernel upgrade
I am using the "vanilla" 2.4.18 kernel. I wanted to get it working without
the ACL. We've done a little more work and we did a trace from the start
of
the 'die' module up until the loop started. Here's the Instruction trace:
Kernel command line: dasd=0200,0201,0204 root=/dev/dasdb1 noinitrd
Highest subchannel number detected (hex) : 000F
Calibrating delay loop... -> 00013904' STM 908FF020 >> 0011AB20 CC 0
00013908' BRAS A7D50012 -> 0001392C' CC 0
-> 0001392C' LR 181F CC 0
0001392E' AHI A7FAFF98 CC 1
00013932' ST 5010F000 >> 0011AA98 CC 1
00013936' L 5810D000 0001390C CC 1
0001393A' LR 1892 CC 1
0001393C' LR 1883 CC 1
0001393E' LR 18B4 CC 1
00013940' ICM BF2F1000 002131F8 CC 2
00013944' BRZ A7840006 00013950 CC 2
00013948' LHI A728000F CC 2
0001394C' ST 50201000 >> 002131F8 CC 2
00013950' STNSM ACFCF060 >> 0011AAF8 CC 2
00013954' L 58C0D004 00013910 CC 2
00013958' BRAS A7150004 -> 00013960' CC 2
00013960' SLR 1F00 CC 2
00013962' CS BA01C000 >> 0020F060 CC 0
00013966' BRM A744FFFB 0001395C CC 0
0001396A' LHI A7280001 CC 0
0001396E' L 58A0D008 00013914 CC 0
00013972' BASR 0DEA -> 000119C4' CC 0
00013974' L 5810D014 00013920 CC 2
00013978' LR 184B CC 2
0001397A' N 5440D00C 00013918 CC 1
0001397E' LR 1839 CC 1
00013980' L 5820D010 0001391C CC 1
00013984' BASR 0DE1 -> 0001FBCC' CC 1
00013986' L 5830D018 00013924 CC 2
0001398A' LR 1828 CC 2
0001398C' BASR 0DE3 -> 000152FC' CC 2
0001398E' LHI A7280000 CC 2
00013992' BASR 0DEA -> 000119C4' CC 2
00013904' STM 908FF020 >> 0011A6F8 CC 0
00013908' BRAS A7D50012 -> 0001392C' CC 0
0001392C' LR 181F CC 0
0001392E' AHI A7FAFF98 CC 1
00013932' ST 5010F000 >> 0011A670 CC 1
00013936' L 5810D000 0001390C CC 1
0001393A' LR 1892 CC 1
0001393C' LR 1883 CC 1
0001393E' LR 18B4 CC 1
00013940' ICM BF2F1000 002131F8 CC 2
00013944' BRZ A7840006 00013950 CC 2
00013948' LHI A728000F CC 2
0001394C' ST 50201000 >> 002131F8 CC 2
00013950' STNSM ACFCF060 >> 0011A6D0 CC 2
00013954' L 58C0D004 00013910 CC 2
00013958' BRAS A7150004 -> 00013960' CC 2
00013960' SLR 1F00 CC 2
00013962' CS BA01C000 0020F060 CC 1
00013966' BRM A744FFFB -> 0001395C' CC 1
0001395C' DIAG 83000044 00000044 CC 1
00013960' SLR 1F00 CC 2
00013962' CS BA01C000 0020F060 CC 1
00013966' BRM A744FFFB -> 0001395C' CC 1
0001395C' DIAG 83000044 00000044 CC 1
00013960' SLR 1F00 CC 2
00013962' CS BA01C000 0020F060 CC 1
00013966' BRM A744FFFB -> 0001395C' CC 1
0001395C' DIAG 83000044 00000044 CC 1
00013960' SLR 1F00 CC 2
00013962' CS BA01C000 0020F060 CC 1
00013966' BRM A744FFFB -> 0001395C' CC 1
Thanks !!!
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: Thursday, May 02, 2002 10:01 AM
To: [EMAIL PROTECTED]
Subject: Re: HELP-2.4.18 Kernel upgrade
Josh,
Just a quick question. Are you just trying to IPL a "vanilla" 2.4.18
kernel
before putting on the ACL patches, or are you trying to IPL a kernel with
them already applied?
Mark Post
-----Original Message-----
From: Konkol, Josh [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 10:08 AM
To: [EMAIL PROTECTED]
Subject: Re: HELP-2.4.18 Kernel upgrade
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\
/( )\
^^-^^
