Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Wed, 15 Apr 2009 09:55:08 -0400
David Boyes dbo...@sinenomine.net wrote:
Rather than testing for specific model numbers, why don't you test for
specific capabilities that you need/want? That way you get a exception that
you can handle and actually issue a useful message or load a specific PSW
(similar to the way things work on other OSes), rather than just dying in a
cryptic way.
How about this:
Subject: [PATCH] use facility list for cpu type safety check
From: Martin Schwidefsky schwidef...@de.ibm.com
Signed-off-by: Martin Schwidefsky schwidef...@de.ibm.com
---
arch/s390/include/asm/lowcore.h |1
arch/s390/kernel/head.S | 49 +++-
2 files changed, 35 insertions(+), 15 deletions(-)
diff -urpN linux-2.6/arch/s390/include/asm/lowcore.h
linux-2.6-patched/arch/s390/include/asm/lowcore.h
--- linux-2.6/arch/s390/include/asm/lowcore.h 2009-04-17 09:37:40.0
+0200
+++ linux-2.6-patched/arch/s390/include/asm/lowcore.h 2009-04-17
12:14:06.0 +0200
@@ -30,6 +30,7 @@
#define __LC_SUBCHANNEL_NR 0x00ba
#define __LC_IO_INT_PARM 0x00bc
#define __LC_IO_INT_WORD 0x00c0
+#define __LC_STFL_FAC_LIST 0x00c8
#define __LC_MCCK_CODE 0x00e8
#define __LC_DUMP_REIPL0x0e00
diff -urpN linux-2.6/arch/s390/kernel/head.S
linux-2.6-patched/arch/s390/kernel/head.S
--- linux-2.6/arch/s390/kernel/head.S 2009-04-17 09:37:40.0 +0200
+++ linux-2.6-patched/arch/s390/kernel/head.S 2009-04-17 12:14:06.0
+0200
@@ -478,27 +478,46 @@ startup:basr %r13,0 # get base
mvc __LC_LAST_UPDATE_TIMER(8),6f-.LPG0(%r13)
mvc __LC_EXIT_TIMER(8),5f-.LPG0(%r13)
#ifndef CONFIG_MARCH_G5
- # check processor version against MARCH_{G5,Z900,Z990,Z9_109,Z10}
- stidp __LC_CPUID # store cpuid
- lhi %r0,(3f-2f) / 2
- la %r1,2f-.LPG0(%r13)
-0: clc __LC_CPUID+4(2),0(%r1)
- jne 3f
- lpsw1f-.LPG0(13)# machine type not good enough, crash
+ # check capabilities against MARCH_{G5,Z900,Z990,Z9_109,Z10}
+ xc __LC_STFL_FAC_LIST(8),__LC_STFL_FAC_LIST
+ stfl__LC_STFL_FAC_LIST # store facility list
+ tm __LC_STFL_FAC_LIST,0x01 # stfle available ?
+ jz 0f
+ la %r0,0
+ stfle __LC_STFL_FAC_LIST # store facility list extended
+0: l %r0,__LC_STFL_FAC_LIST
+ n %r0,2f+8-.LPG0(%r13)
+ cl %r0,2f+8-.LPG0(%r13)
+ jne 1f
+ l %r0,__LC_STFL_FAC_LIST
+ n %r0,2f+12-.LPG0(%r13)
+ cl %r0,2f+12-.LPG0(%r13)
+ je 3f
+1: lpsw2f-.LPG0(13)# machine type not good enough, crash
.align 16
-1: .long 0x000a,0x
-2:
+2: .long 0x000a,0x8bad
+#if defined(CONFIG_64BIT)
#if defined(CONFIG_MARCH_Z10)
- .short 0x9672, 0x2064, 0x2066, 0x2084, 0x2086, 0x2094, 0x2096
+ .long 0xc100efe3, 0xf068
#elif defined(CONFIG_MARCH_Z9_109)
- .short 0x9672, 0x2064, 0x2066, 0x2084, 0x2086
+ .long 0xc100efc3, 0x
#elif defined(CONFIG_MARCH_Z990)
- .short 0x9672, 0x2064, 0x2066
+ .long 0xc0002000, 0x
#elif defined(CONFIG_MARCH_Z900)
- .short 0x9672
+ .long 0xc000, 0x
#endif
-3: la %r1,2(%r1)
- brct%r0,0b
+#else
+#if defined(CONFIG_MARCH_Z10)
+ .long 0x8100c880, 0x
+#elif defined(CONFIG_MARCH_Z9_109)
+ .long 0x8100c880, 0x
+#elif defined(CONFIG_MARCH_Z990)
+ .long 0x80002000, 0x
+#elif defined(CONFIG_MARCH_Z900)
+ .long 0x8000, 0x
+#endif
+#endif
+3:
#endif
l %r13,4f-.LPG0(%r13)
--
blue skies,
Martin.
Reality continues to ruin my life. - Calvin.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Looks OK to me, other than it doesn¹t have docs to describe the error codes. Fix that and I¹ll gladly sign off on it. 8-) On 4/17/09 6:22 AM, Martin Schwidefsky schwidef...@de.ibm.com wrote: Subject: [PATCH] use facility list for cpu type safety check From: Martin Schwidefsky schwidef...@de.ibm.com Signed-off-by: Martin Schwidefsky schwidef...@de.ibm.com [snip] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Martin Schwidefsky wrote: #if defined(CONFIG_MARCH_Z10) - .short 0x9672, 0x2064, 0x2066, 0x2084, 0x2086, 0x2094, 0x2096 + .long 0xc100efe3, 0xf068 Does the linux kernel (with CONFIG_MARCH_Z10) really need all the z10 facilities ? (especially some of those are simply hints - like bit 19) --Ivan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME Cryptographic Signature
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Fri, 17 Apr 2009 15:41:49 +0200 Ivan Warren i...@vmfacility.fr wrote: Martin Schwidefsky wrote: #if defined(CONFIG_MARCH_Z10) - .short 0x9672, 0x2064, 0x2066, 0x2084, 0x2086, 0x2094, 0x2096 + .long 0xc100efe3, 0xf068 Does the linux kernel (with CONFIG_MARCH_Z10) really need all the z10 facilities ? (especially some of those are simply hints - like bit 19) Bit 19 is 0x1000 in the first stfl word and is not set, no? The logic I've used for the capability bits: 1) the bits the kernel really needs, e.g. the z/Architecture bit for a 64 bit kernel 2) the bits for facilities that can be used in user space and therefore in theory could be generated by the compiler, e.g. by __builtin_xyz I did not include: 1) bits for facilities that can only be used by the kernel and are currently unused, e.g. the ASN-and-LX reused facility. 2) hint bits, e.g. about the performance of long-displacement or DFP -- blue skies, Martin. Reality continues to ruin my life. - Calvin. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
John Summerfield wrote: Andrew Avramenko wrote: Daniel, SLES 11 doesn't support old hardware, just only z9 and z10. I'm not familiar with Hercules, but may be that is the problem. I have experience with installation SLES 11 on z9 under VM 5.3 and everything was fine. I the Hercules folk pride themselves on supporting the latest incantations of S/360, right up to current. Actually, Hercules does not support System/360 architecture. It does support System/370 Basic Control mode which is very close to System/360, but not identical. And yes, the very latest capabilities of System/370 is supported as defined by the IBM System/370 Principles of Operation, manual GA22-7000-10 published in September 1987 and still available from IBM publications. I ordered my copy last year. And, yes, the intervening architectual enhancements are also supported to the z/Architecture PoO published last fall. And we are looking at the implications of the one published in February of this year. Of course, Hercules has actual users of all of these architectures, so it does make sense that all of them are supported. So, I guess this post proves your point, John, we are proud of that. The Linux kernel developers are not in anyway attempting to restrict where Linux can run. It is making the boot code sensitive to the compiler and options used to create the kernel. Those settings influence instructions selected for the generated code. Rather than an obscure abend occurring someplace because of a hardware capabilities/compiler option conflict, the boot logic is trying to detect that up front. This is standard defensive programming. While historically there has been slightly less adherence to backward compatibility for control programs than application programs on IBM mainframes. For example, backward compatibility was lost for control programs when the subchannel subsystem was introduced in the 370-XA architecture. The domain of gcc is application programs, meaning, non-privileged instructions in mainframe architectural terms. And, on an IBM mainframe, application program backward compatibility has been absolute. The Linux kernel's use of privileged instructions in in-line assembly raises the question of backward compatibility for the a control program. A separate question from the gcc compiler and options settings addressed by this boot logic. The gcc compiler and option detection is also separate from the decisions of a distributor such as Novell or RedHat or Debian. For the user, there are both positive and negative implications of those decisions. The beauty of open source, is, if you don't like those decisions or absolutely can't live with them, you have options. And, while these changes don't actually enable such decisions by a distributor, a distributor could change compiler and option settings at will, they do attempt to aid a Linux user early detection. And of course, this becomes a potential differentiator of distributors. Just as the Hercules developers are sensitive to the users of Hercules, kernel developers also have to be sensitive to their users. For a kernel developer, this is not just the users of Linux but also the distributors of Linux. Harold Grovesteen -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Andrew Avramenko wrote: Daniel, SLES 11 doesn't support old hardware, just only z9 and z10. I'm not familiar with Hercules, but may be that is the problem. I have experience with installation SLES 11 on z9 under VM 5.3 and everything was fine. I the Hercules folk pride themselves on supporting the latest incantations of S/360, right up to current. -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Tue, 14 Apr 2009 23:52:18 +0200 Ivan Warren i...@vmfacility.fr wrote: Daniel Jarboe wrote: On Tue, Apr 14, 2009 at 3:34 PM, Neale Ferguson wrote: SLES11 was checking the CPU Model, not liking 9672, and aborting. I changed CPUMODEL to something more current (2096) and the SLES11 installer IPLed without incident. It's not actually a SLES 11 thing.. The test exists in the upstream kernel. Go fetch me the cane so I can flog the guy who put that weird test in arch/s390/kernel/head.S ! Martin! ;) I mean.. come on.. ok.. Specifying 9672 breaks but specifying 2096 works... but guess what.. having a 4341 CPU model also works ;) (not that it would go very far anyway on a *REAL* 4341 !) At least, there should be a significantly unique magic in the disabled wait PSW IA to allow someone to easily find it by googling ! Someone attempting to boot a modern kernel on an old machine (like a z9 only kernel on a z990) may be happy to find a quick answer ! Like 00A 8EADBADC (read : head.S Bad CPU) (I might actually want to submit a patch on that one to the IBM linux folks in Germany !) How about the patch below? Since I would expect that this is going to happen a lot of times as soon as some distro starts to compile the kernel with e.g. only z9-109 and higher support we indeed need a magic number here. Otherwise we can't tell immediately what's going wrong. --- arch/s390/kernel/head.S |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: linux-2.5/arch/s390/kernel/head.S === --- linux-2.5.orig/arch/s390/kernel/head.S +++ linux-2.5/arch/s390/kernel/head.S @@ -486,7 +486,7 @@ startup:basr%r13,0 # get base jne 3f lpsw1f-.LPG0(13)# machine type not good enough, crash .align 16 -1: .long 0x000a,0x +1: .long 0x000a,0x8bad 2: #if defined(CONFIG_MARCH_Z10) .short 0x9672, 0x2064, 0x2066, 0x2084, 0x2086, 0x2094, 0x2096 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Heiko Carstens wrote: How about the patch below? Since I would expect that this is going to happen a lot of times as soon as some distro starts to compile the kernel with e.g. only z9-109 and higher support we indeed need a magic number here. Otherwise we can't tell immediately what's going wrong. --- arch/s390/kernel/head.S |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: linux-2.5/arch/s390/kernel/head.S === --- linux-2.5.orig/arch/s390/kernel/head.S +++ linux-2.5/arch/s390/kernel/head.S @@ -486,7 +486,7 @@ startup:basr%r13,0 # get base jne 3f lpsw1f-.LPG0(13)# machine type not good enough, crash .align 16 -1: .long 0x000a,0x +1: .long 0x000a,0x8bad 2: #if defined(CONFIG_MARCH_Z10) .short 0x9672, 0x2064, 0x2066, 0x2084, 0x2086, 0x2094, 0x2096 I was looking into it and came around with the exact same patch - only with a different magic - but I'll let you all decide on that ! So yes, that looks great ! Thanks, --Ivan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME Cryptographic Signature
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/15/09 5:49 AM, Heiko Carstens heiko.carst...@de.ibm.com wrote: How about the patch below? Since I would expect that this is going to happen a lot of times as soon as some distro starts to compile the kernel with e.g. only z9-109 and higher support we indeed need a magic number here. Otherwise we can't tell immediately what's going wrong. Rather than testing for specific model numbers, why don't you test for specific capabilities that you need/want? That way you get a exception that you can handle and actually issue a useful message or load a specific PSW (similar to the way things work on other OSes), rather than just dying in a cryptic way. If I remember, the response from STSI should give you whether a specific set of capabilities is present, and then you don't care what weird-ass things the marketing people do. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Not STSI but STFL (to see if STFLE is available) and then STFLE to find what facilities the processor has. On 4/15/09 9:55 AM, David Boyes dbo...@sinenomine.net wrote: If I remember, the response from STSI should give you whether a specific set of capabilities is present, and then you don't care what weird-ass things the marketing people do. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/15/09 10:01 AM, Neale Ferguson ne...@sinenomine.net wrote: Not STSI but STFL (to see if STFLE is available) and then STFLE to find what facilities the processor has. Good catch. I have a older copy of the POP on my desk; time to upgrade...8-) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Wed, 15 Apr 2009 09:55:08 -0400 David Boyes dbo...@sinenomine.net wrote: On 4/15/09 5:49 AM, Heiko Carstens heiko.carst...@de.ibm.com wrote: How about the patch below? Since I would expect that this is going to happen a lot of times as soon as some distro starts to compile the kernel with e.g. only z9-109 and higher support we indeed need a magic number here. Otherwise we can't tell immediately what's going wrong. Rather than testing for specific model numbers, why don't you test for specific capabilities that you need/want? That way you get a exception that you can handle and actually issue a useful message or load a specific PSW (similar to the way things work on other OSes), rather than just dying in a cryptic way. If I remember, the response from STSI should give you whether a specific set of capabilities is present, and then you don't care what weird-ass things the marketing people do. If you look at arch/s390/Makefile you will find this: cflags-$(CONFIG_MARCH_G5) += $(call cc-option,-march=g5) cflags-$(CONFIG_MARCH_Z900) += $(call cc-option,-march=z900) cflags-$(CONFIG_MARCH_Z990) += $(call cc-option,-march=z990) cflags-$(CONFIG_MARCH_Z9_109) += $(call cc-option,-march=z9-109) cflags-$(CONFIG_MARCH_Z10) += $(call cc-option,-march=z10) We could translate the compile option for a particular model to the set of capabilities of the machine. That would help with future models where we don't know the model number yet. Printing a message is harder to do. We cannot use the device drivers because they are compiled with options that will generate instruction that will trap on older machines. The only option would be to use assembler written function to print a message via sclp. -- blue skies, Martin. Reality continues to ruin my life. - Calvin. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Wed, 15 Apr 2009 09:55:08 -0400 David Boyes dbo...@sinenomine.net wrote: On 4/15/09 5:49 AM, Heiko Carstens heiko.carst...@de.ibm.com wrote: How about the patch below? Since I would expect that this is going to happen a lot of times as soon as some distro starts to compile the kernel with e.g. only z9-109 and higher support we indeed need a magic number here. Otherwise we can't tell immediately what's going wrong. Rather than testing for specific model numbers, why don't you test for specific capabilities that you need/want? That way you get a exception that you can handle and actually issue a useful message or load a specific PSW (similar to the way things work on other OSes), rather than just dying in a cryptic way. I agree that it would be better to emit a message to the console. But the code that emits the message must be written completely in assembler to prevent the compiler from generating instructions that wouldn't work on older machines. So currently we have this piece of code which is simple and with a magic PSW it should be sufficient. We might change it, but no promises. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Wednesday, 04/15/2009 at 11:00 EDT, Heiko Carstens heiko.carst...@de.ibm.com wrote: I agree that it would be better to emit a message to the console. But the code that emits the message must be written completely in assembler to prevent the compiler from generating instructions that wouldn't work on older machines. So currently we have this piece of code which is simple and with a magic PSW it should be sufficient. We might change it, but no promises. It is standard for any mainframe operating system that cannot IPL to load a disabled wait state with a PSW that acts as code number in it so that you can look in a book to find out what it means. VM, MVS, VSE, and TPF all do it. Come on in! The water's fine! :-) There is no need for heroic measures to write a nice message to the console. Just make sure that the addresses in the PSW are unique for each condition. If you can be clever in your use of letters A-F and numbers (and l33t5peak), you can give informative wait state codes. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Alan Altmark wrote: There is no need for heroic measures to write a nice message to the console. Just make sure that the addresses in the PSW are unique for each condition. If you can be clever in your use of letters A-F and numbers (and l33t5peak), you can give informative wait state codes. I'll second that.. That's why I was proposing : 8EADBADC (HEAD detected BAD Cpu) I also noticed there is a flurry of conditions in head.S that also load a disabled wait PSW, incurring from an IPL I/O error.. So I guess 8EAD1030 (For Head I/O ErrOr) The problem of course is that with 8 characters of 1337 (And.. Alan.. it's 13375|*34| - but I digress) expressing something is - shall we say - bound to be esoteric. My idea would be to put some random magic in there.. and *document* it (possibly in a new ./Documentation/s390/ipl.txt file) so as to allow it to appear prominently in search engines. So if someone gets a 000A 8EADBADC disabled wait PSW, chances are good that searching for that will yield useful results quite easily for the unsuspecting victim. We probably have to go through something like this because - contrary to IBM program products (not limited to strictly mainframe OSes.. AIX is the same, as well as about any IBM issued software), which have a centralized managed catalog for message numbers and the documentation that goes with it - linux doesn't have that - so we have to rely on some external source to achieve the same result - that is - finding resolution about a failure with whatever information -is- or -can be- provided at the time of failure. Now, I'm still not 100% convinced that checking the CPUID is the right thing to do.. STFL/STFLE - as proposed earlier- is probably a better approach (but that complicates the code quite a bit). Now, if you generate a say.. z9+ only kernel and run it on a z800.. And gcc generates some z9 only code, we're going to get a program check quite quickly (it won't break anything.. it'll just panic big time).. And if for some reason, IBM decides to port some of the newer functions to older machines (through a driver update - driver in the sense of functional LIC) - then it will run because.. it can ! Finally, maybe this should be moved to the s390 kernel list.. not sure this is the appropriate list to go into such gory details ! --Ivan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME Cryptographic Signature
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Posting on Linux-390 list too... --- In hercules-...@yahoogroups.com, Harold Grovesteen h.grovst...@... wrote: The assumption that has been made is that the files listed in your .ins file were in fact loaded. That assumption needs to be validated. Please display real storage for each of the starting addresses in your .ins file. This should validate that what you think got loaded did get loaded. The command format is: r hexaddr.len So: r .1F will display the first 32 bytes of storage. If what is displayed is other than 0x00 then something did in fact get loaded. r 0001040C.4 etc. Thanks for thinking of that suggestion. Based on the response on the Linux-390 Marist list, I pulled from SVN last night: 5323. Incidentally, the make blew up in po; I had to ./configure --disable-nls. Now, doing the displays like you mentioned in that build... # Start up Hercules (storage is empty): HHCAO001I Hercules Automatic Operator thread started; tid=76FA7B90, pri=0, pid=11594 r 0.1f R::K:00= R:0010:K:00= # IPL the SLES11 .ins and get the disabled wait state; storage is no longer empty: ipl ./rdr/sles11/suse.ins HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A r 0.1f R::K:06=0008 8298 0218 6050 ...q-.. R:0010:K:06=0268 6050 40404040 40404040 -.. r 1040c.f R:0001040C:K:06=0080 00C4CC37 .D.. r 10414.f R:00010414:K:06=00C4CC37 .D.. r 80.1f R:0080:K:06=1F8B0808 5C47B449 0203696E 69747264 *.. R:00800010:K:06=00AC590B 7C935596 BF5F9A36 01298452 @l.o.^d. r 10480.1f R:00010480:K:06=72616D64 69736B5F 73697A65 3D363535 ./_...,^..:. R:00010490:K:06=33362072 6F6F743D 2F646576 2F72616D ??/_ # The files specified in the .ins files do appear to be loaded. For comparisons sake I loaded the SLES10SP2 vmrdr.ikr to see if it looked the same... loadcore ./rdr/sles10SP2/vmrdr.ikr HHCPN112I Loading ./rdr/sles10SP2/vmrdr.ikr to location 0 HHCPN113I 7161160 bytes read from ./rdr/sles10SP2/vmrdr.ikr r 0.1f R::K:06=0008 8298 0218 6050 ...q-.. R:0010:K:06=0268 6050 40404040 40404040 -.. # Both start off the same. I checked outside of Hercules and the first 671 bytes of the files are identical. For grins restart with the SLES10SP2 vmrdr.ikr and SLES11 initrd/parmfile/etc. restart HHCPN038I Restart key depressed CPU: SIGP Set architecture mode (12) CPU, PARM 0001: CC 0 HHCCP007I CPU architecture mode set to z/Arch HHCCP014I CPU: Addressing exception CODE=0005 ILC=6 PSW=1001 8000 00011176 INST=E5015000 TPROT 0(5),0(0) test_protection R:4000: Translation exception 0005 R::K:06=0008 8298 000A ...q R0=00728F04 R1=0002 R2= R3=006DC610 R4= R5=4000 R6= R7= R8= R9=4000 RA=0010 RB= RC=00010400 RD=00011002 RE=00011058 RF=0069FF60 HHCCP014I CPU: Special-operation exception CODE=0013 ILC=6 PSW=1001 8000 00011290 INST=C800 MVCOS 0(0),0(0),0move_with_optional_specifications R::K:06=0008 8298 000A ...q R::K:06=0008 8298 000A ...q R0= R1=00011290 R2= R3=006DC628 R4=4002 R5=4002 R6= R7= R8=0001 R9=4000 RA=000F RB= RC=006DC5F8 RD=00011002 RE=00011058 RF=0069FF60 HHCCP014I CPU: Operation exception CODE=0001 ILC=4 PSW=1001 8000 000112AE INST=B9AF0011 PFMF 1,1perform_frame_management_function R:: Translation exception 0005 R:: Translation exception 0005 R0= R1= R2= R3=006DC628 R4=4002 R5=4002 R6= R7= R8=0001 R9=4000 RA=000F RB= RC=006DC5F8 RD=00011002 RE=00011058 RF=0069FF60 HHCCP014I CPU: Operation exception CODE=0001 ILC=4 PSW=0001 8000 000112CC INST=B9AB0001 ? , ? R::K:06=0008 8298 000A ...q R::K:06=0008 8298 000A ...q R0= R1=
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Tuesday, 04/14/2009 at 09:36 EDT, Daniel Jarboe daniel.jar...@gmail.com wrote: ipl ./rdr/sles11/suse.ins HHCCP007I CPU architecture mode set to ESA/390 restart HHCPN038I Restart key depressed CPU: SIGP Set architecture mode (12) CPU, PARM 0001: CC 0 HHCCP007I CPU architecture mode set to z/Arch My guess is that something's wrong with the SIGP SARCH (Set Architecture) that Linux issues to get into z/Architecture mode. IPL resets to the CPUs to ESA/390 architecture. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/14/2009 at 10:54 AM, Alan Altmark alan_altm...@us.ibm.com wrote: -snip- My guess is that something's wrong with the SIGP SARCH (Set Architecture) that Linux issues to get into z/Architecture mode. IPL resets to the CPUs to ESA/390 architecture. I'm pretty sure that's by design, and not a problem. The kernel starts out in 31-bit mode, and then switches to 64-bit mode. I've been seeing the same thing for years now, and I still do on my own Hercules setup that can successfully boot up SLES11. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
I'm pretty sure that's by design, and not a problem. The kernel starts out in 31-bit mode, and then switches to 64-bit mode. I've been seeing the same thing for years now, and I still do on my own Hercules setup that can successfully boot up SLES11. Hi Mark, can you confirm? $ md5sum vmrdr.ikr 98573dfb90ece6c6deaaf936e7d7e725 vmrdr.ikr Also, what release of hercules? I might as well try that too for completeness sake. Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/14/2009 at 12:35 PM, Daniel Jarboe daniel.jar...@gmail.com wrote: -snip- Hi Mark, can you confirm? $ md5sum vmrdr.ikr 98573dfb90ece6c6deaaf936e7d7e725 vmrdr.ikr That matches what I have. Also, what release of hercules? I might as well try that too for completeness sake. The package I built shows 3.04.1. The date and time on the newest file in the top-level directory was 2006-03-25 08:13 configure.ac Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Alan Altmark wrote: My guess is that something's wrong with the SIGP SARCH (Set Architecture) that Linux issues to get into z/Architecture mode. IPL resets to the CPUs to ESA/390 architecture. With only 2 instructions executed, I doubt we're going this far ! Note that SIGP 12 works as designed on hercules ! (as far as I know anyway) ! (I really need to load that SLES 11 eval try it myself.. I guess I'll have yet another 'expired trial' in my NCC again ;) ) --Ivan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME Cryptographic Signature
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/14/2009 at 9:34 AM, Daniel Jarboe daniel.jar...@gmail.com wrote: -snip- No matter which SLES11 .ikr file is specified in the .ins (cd.ikr, tapeipl.ikr, vmrdr.ikr), I go into immediate disabled wait state. Yet specify ../sles10SP2/vmrdr.ikr in suse.ins and off it goes. What kind of hardware and operating system are you running this on? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
What kind of hardware and operating system are you running this on? A Ubuntu 8.10 installation. P4 Intel chip, 1GB RAM. I still end up at disabled wait state with 3.04.1 (though with the older release of hercules it reports instcount of 18 rather than 2). I'll have to try this on some other boxes. herc 3.04.1 SLES11 IPL from suse.ins: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A M.W. instcount=18 herc 3.04.1 SLES10SP2 IPL from suse.ins: IPLs, but ultimately blows up with an instruction count of about 1.7 million (before installer asks for anything) herc 3.04.1 Debian Lenny IPL from reader: IPLs, installer runs but is unable to activate dasd herc 3.06 SLES11 IPL from suse.ins: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A 24M.W. instcount=2 herc 3.06 SLES10SP2 IPL from suse.ins: IPLs, full installation complete without apparent problem herc 3.06 Debian Lenny IPL from reader: IPLs, full installation complete without apparent problem -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Can you display the program old PSW and the instruction that the address portion of the PSW points to? (Actually, the address less the ILC.) On 4/14/09 2:17 PM, Daniel Jarboe daniel.jar...@gmail.com wrote: What kind of hardware and operating system are you running this on? A Ubuntu 8.10 installation. P4 Intel chip, 1GB RAM. I still end up at disabled wait state with 3.04.1 (though with the older release of hercules it reports instcount of 18 rather than 2). I'll have to try this on some other boxes. herc 3.04.1 SLES11 IPL from suse.ins: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A M.W. instcount=18 herc 3.04.1 SLES10SP2 IPL from suse.ins: IPLs, but ultimately blows up with an instruction count of about 1.7 million (before installer asks for anything) herc 3.04.1 Debian Lenny IPL from reader: IPLs, installer runs but is unable to activate dasd herc 3.06 SLES11 IPL from suse.ins: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A 24M.W. instcount=2 herc 3.06 SLES10SP2 IPL from suse.ins: IPLs, full installation complete without apparent problem herc 3.06 Debian Lenny IPL from reader: IPLs, full installation complete without apparent problem -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Tue, Apr 14, 2009 at 3:34 PM, Neale Ferguson wrote: Can you display the program old PSW and the instruction that the address portion of the PSW points to? (Actually, the address less the ILC.) That fished it out. Enabling instruction stepping increased the instruction count, but not by much. s+ HHCPN040I Instruction stepping on ipl ./rdr/sles11/suse.ins HHCCP007I CPU architecture mode set to ESA/390 PSW=0008 8298 INST=481000B8 LH1,184(0,0) load_halfword R:00B8:K:06=02000500 6050 02000550 6050 -.-.. GR00= GR01= GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 829C INST=461003F0 BCT 1,1008(0,0) branch_on_count R:03F0:K:06=581003FE 07F100B1 E7B80001 0401 .1..X... GR00= GR01=0200 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 83F0 INST=581003FE L 1,1022(0,0)load R:03FE:K:06=0001 0060 3F90C3C8 C1D5C7C5 40D9 .-..CHANGE R GR00= GR01=01FF GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 83F4 INST=07F1 BCR 15,1 branch_on_condition_register GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 8001 INST=0DD0 BASR 13,0 branch_and_save_register GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 80010002 INST=B2020D80 STIDP 3456(0) store_cpu_id R:0D80:K:04= GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= CR00=00E0 CR01= CR02= CR03= CR04= CR05= CR06= CR07= CR08= CR09= CR10= CR11= CR12= CR13= CR14=C200 CR15= PSW=0008 80010006 INST=A7080001 LHI 0,1 load_halfword_immediate GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 8001000A INST=4110D026 LA1,38(0,13) load_address R:00010028:K:06=96724110 1002A706 FFF058D0 D03847F0 o.x..0.}}..0 GR00=0001 GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 8001000E INST=D5010D841000 CLC 3460(2,0),0(1) compare_logical_character R:0D84:K:06=9672 o... R:00010028:K:06=96724110 1002A706 FFF058D0 D03847F0 o.x..0.}}..0 GR00=0001 GR01=00010028 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 80010014 INST=A774000B BRC 7,*+22 branch_relative_on_condition GR00=0001 GR01=00010028 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 80010018 INST=8200D01E LPSW 30(13) load_program_status_word R:00010020:K:06=000A 96724110 1002A706 o.x. GR00=0001 GR01=00010028 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= HHCCP043I Wait state PSW loaded: PSW=000A HHCCP011I CPU: Disabled wait state PSW=000A SLES11 was checking the CPU Model, not liking 9672, and aborting. I changed CPUMODEL to something more current (2096) and the SLES11 installer IPLed without incident. Thank you everybody for the eyes and the
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Daniel Jarboe wrote: On Tue, Apr 14, 2009 at 3:34 PM, Neale Ferguson wrote: SLES11 was checking the CPU Model, not liking 9672, and aborting. I changed CPUMODEL to something more current (2096) and the SLES11 installer IPLed without incident. It's not actually a SLES 11 thing.. The test exists in the upstream kernel. Go fetch me the cane so I can flog the guy who put that weird test in arch/s390/kernel/head.S ! I mean.. come on.. ok.. Specifying 9672 breaks but specifying 2096 works... but guess what.. having a 4341 CPU model also works ;) (not that it would go very far anyway on a *REAL* 4341 !) At least, there should be a significantly unique magic in the disabled wait PSW IA to allow someone to easily find it by googling ! Someone attempting to boot a modern kernel on an old machine (like a z9 only kernel on a z990) may be happy to find a quick answer ! Like 00A 8EADBADC (read : head.S Bad CPU) (I might actually want to submit a patch on that one to the IBM linux folks in Germany !) --Ivan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME Cryptographic Signature
IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
I'm having trouble IPLing the starter SLES11 system using Hercules 3.06. The IPL method should be equivalent to a LPAR load from CD-ROM. The deployment.pdf included within SuSE's docu directory didn't reveal any obvious differences why what works for SLES10 SP2 installation under Hercules doesn't work for me now with SLES11 media. ipl /path/to/suse.ins now results in: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A 24M.W. instcount=2 The new SLES11 suse.ins is: * SuSE Linux for zSeries Installation/Rescue System vmrdr.ikr 0x initrd.off 0x0001040c initrd.siz 0x00010414 initrd 0x0080 parmfile 0x00010480 All files are present. For reference, the SLES10SP2 suse.ins was fairly similar and works without problems for SLES10: * SuSE Linux for zSeries Installation/Rescue System vmrdr.ikr 0x initrd.siz 0x00010414 initrd 0x0080 parmfile 0x00010480 There's no z/VM in the mix. I also replaced vmrdr.ikr with cd.ikr in the .ins file, but the result was the same. Has anyone already been through a SLES11 LPAR IPL from CD, or can get me started in the right direction on this? Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Daniel, SLES 11 doesn't support old hardware, just only z9 and z10. I'm not familiar with Hercules, but may be that is the problem. I have experience with installation SLES 11 on z9 under VM 5.3 and everything was fine. 2009/4/13 Daniel Jarboe daniel.jarboe [at] gmail.com: I'm having trouble IPLing the starter SLES11 system using Hercules 3.06. The IPL method should be equivalent to a LPAR load from CD-ROM. The deployment.pdf included within SuSE's docu directory didn't reveal any obvious differences why what works for SLES10 SP2 installation under Hercules doesn't work for me now with SLES11 media. -- With best regards, Andrew -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Just like information , I'm running SLES11 over an older IBM 2064 hardware (a generation before z9 z10) , proc , dasd and osa cards were recognized without problems .. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/13/2009 at 8:09 AM, Daniel Jarboe daniel.jar...@gmail.com wrote: I'm having trouble IPLing the starter SLES11 system using Hercules 3.06. The IPL method should be equivalent to a LPAR load from CD-ROM. The deployment.pdf included within SuSE's docu directory didn't reveal any obvious differences why what works for SLES10 SP2 installation under Hercules doesn't work for me now with SLES11 media. I suspect you've run into the same problem that (at least) Rick Troth and I did. Hercules implemented one of the instructions incorrectly that are used by newer kernels. If you take a copy of the current CVS and compile it from source, everything should be fine. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/13/2009 at 9:20 AM, Andrew Avramenko l...@volgograd.ru wrote: Daniel, SLES 11 doesn't support old hardware, just only z9 and z10. I'm not familiar with Hercules, but may be that is the problem. I have experience with installation SLES 11 on z9 under VM 5.3 and everything was fine. SLES11 GA will _run_ on all zSeries and System z hardware. It will only be _supported_ on z9 and later. Beginning with SP1 or SP2, it will only run on z9 or later. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Mark Post wrote: On 4/13/2009 at 8:09 AM, Daniel Jarboe daniel.jar...@gmail.com wrote: I'm having trouble IPLing the starter SLES11 system using Hercules 3.06. The IPL method should be equivalent to a LPAR load from CD-ROM. The deployment.pdf included within SuSE's docu directory didn't reveal any obvious differences why what works for SLES10 SP2 installation under Hercules doesn't work for me now with SLES11 media. I suspect you've run into the same problem that (at least) Rick Troth and I did. Hercules implemented one of the instructions incorrectly that are used by newer kernels. If you take a copy of the current CVS and compile it from source, everything should be fine. I would not deny that this might be a problem, but with an instruction count of 2, it did not get very far, unless of course it is the very first instruction. This question came up on the Hercules list, and I recommended this list. Can anyone validate for the poster, the correct .ins file content? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
I would not deny that this might be a problem, but with an instruction count of 2, it did not get very far, unless of course it is the very first instruction. This question came up on the Hercules list, and I recommended this list. Can anyone validate for the poster, the correct .ins file content? I ran into a bug earlier when using the 3.0.5 .deb package that made dasd activation fail. I had already gotten past that one by downloading the hercules 3.0.6 release and building that. I figured it wouldn't hurt to pull the latest from SVN for grins when I get home and give it a whirl *just in case*. The initrd looks perfectly valid: a gzipped cpio archive. I'm not sure how to validate the different .ikr files at this point. According to file the headers indicate both SLES10SP2 and SLES11 are Applesoft BASIC program data. I have some reading to do here. The instruction count of two gave me hope that it was something silly with a quick solution, but I will dig more. I IPLed the debian Lenny installer from the reader so it's not really an apples to apples, but SLES 10 SP2 was an ipl suse.ins which is the same method I'm trying to use with SLES 11. Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On 4/13/2009 at 2:31 PM, Harold Grovesteen h.grovst...@tx.rr.com wrote: -snip- I would not deny that this might be a problem, but with an instruction count of 2, it did not get very far, unless of course it is the very first instruction. This question came up on the Hercules list, and I recommended this list. Can anyone validate for the poster, the correct .ins file content? I just fired up my 2 year old version of Hercules with this suse.ins file: # cat suse.ins * SuSE Linux for zSeries Installation/Rescue System tapeipl.ikr 0x initrd.off 0x0001040c initrd.siz 0x00010414 initrd 0x0080 parmfile 0x00010480 Within a couple of seconds I got these messages on the console: Linux version 2.6.27.19 (ge...@buildhost) (gcc version 4.3.2 gcc-4_3-branch revision 141291! (SUSE Linux) ) #1 SMP PREEMPT Sat Feb 28 07:36:00 UTC 2009 setup.6bac7a: Linux is running natively in 64-bit mode Zone PFN ranges: DMA 0x - 0x0008 Normal 0x0008 - 0x0008 Movable zone start PFN for each node early_node_map1! active PFN ranges Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
