Itanium 1.6.0_11 is a port of JDK 6 update 11 to the Itanium (64 bit) architecture platform.
The full internal version number for this update release is 1.6.0_11-b0305 (where "b" means "build"). The external version number is 6u11. Included in JDK 6u11 for Itanium (64 bit architecture) platform is version 11.0 of the Java HotSpot Server Virtual Machine.
The following JDK, JRE tools are not included in Itanium JDK, JRE 6u11 release:
Please refer to JDK tools and Utilities for JDK tools description.
Only offline installation is available for JDK, JRE 6u11.
Platform | Version | Desktop Managers | Browsers | JRE | JDK |
---|---|---|---|---|---|
Windows 64 bit | |||||
Windows IA64 | Windows Server 2003 SP2 | Windows/Active for Windows |
N/A
|
64-bit Install | 64-bit Install |
Windows Server 2008 for Itanium-Based Systems SP1 | |||||
Linux 64 bit | |||||
Linux IA64 | Linux Suse Enterprise Linux Server 9 SP3, Suse Enterprise Linux Server 10 SP1 | N/A |
N/A
|
64-bit Install | 64-bit Install |
Red Hat Enterprise Linux 4.0 U5, Red Hat Enterprise Linux 5.0 U2 |
Installation procedure installs the JDK or JRE 6u11 but not the Java Plugin or Java Web Start (which are not available for 64-bit Windows) or public Java Runtime Environment (when JDK is installed).
To install, go to Java SE Downloads page, section "JDK 6 Update 11 for Intel ItaniumPH*PH*PH\uFFFDPH*PH*PH" if you need JDK, or "JRE 6 Update 11 for Intel ItaniumPH*PH*PH\uFFFDPH*PH*PH" if you need JRE.
On the Java SE Development Kit for Itanium 6u11 page (if JDK) or Java SE Runtime Environment for Itanium 6u11 page (if JRE), select "Windows" platform.
Download jdk-6u11-windows-ia64.exe or jre-6u11-windows-ia64.exe file and then follow the 32-bit Windows JDK installation or 32-bit Windows JRE installation "Windows Offline Installation" instructions.
Installation procedure installs the JRE or JDK 6u11 but not the Java Plugin or Java Web Start (which are not available for 64-bit Linux) or the public Java Runtime Environment (when JDK is installed).
To install, go to Java SE Downloads page, section "JDK 6 Update 11 for Intel ItaniumPH*PH*PH\uFFFDPH*PH*PH" if you need JDK, or "JRE 6 Update 11 for Intel ItaniumPH*PH*PH\uFFFDPH*PH*PH" if you need JRE.
On the Java SE Development Kit for Itanium 6u11 page (if JDK) or Java SE Runtime Environment for Itanium 6u11 page (if JRE), select "Linux" platform.
The JDK, JRE for Linux 64-bit comes bundled in two install formats - Linux self-extracting files jdk-6u11-linux-ia64.bin, jre-6u11-linux-ia64.bin and Linux RPM in self-extracting files jdk-6u11-linux-ia64-rpm.bin, jre-6u11-linux-ia64-rpm.bin.
Download necessary file and then follow the 32-bit Linux JDK installation or 32-bit Linux JRE installation instructions.
dmidecode(18485): unaligned access to 0x600000000000801a, ip=0x4000000000007390
dmidecode(18485): unaligned access to 0x600000000000801e, ip=0x40000000000073a1
dmidecode(18485): unaligned access to 0x6000000000008065, ip=0x4000000000003151
dmidecode(18485): unaligned access to 0x60000000000080f7, ip=0x4000000000003151
For example, JDK (JRE) 6u7 can not be installed using jdk(jre)-6u7-linux-ia64-rpm.bin file if, on the same machine, JDK (JRE) 6u11 was previously installed using jdk(jre)-6u11-linux-ia64-rpm.bin.
Installation reports:
Preparing... ########################################### [100%] package jdk-1.6.0_11-fcs (which is newer than jdk-1.6.0_07-fcs) is already installed JDK (JRE) 6u7 is not installed.
Workarounds are:
-XX:+AggressiveOpts
-XX:+AggressiveHeap
-XX:+UseParallelGC
-XX:CompileThreshold=10000
-XX:MaxPermSize=256m
-XX:PermSize=256m
-XX:ReservedCodeCacheSize=128m
-XX:+UseLargePages
-XX:LargePageSizeInBytes=16m for Windows
-XX:LargePageSizeInBytes=256m for Linux
PH*PH*PH\uFFFDPH*PH*PHXmx, -Xms, PH*PH*PH\uFFFDPH*PH*PHXmn should have big values.
This is a known bug in kernels of version less than 2.6.22. Processors older than Montecito (e.g. Madison, McKinley) are not affected.
RHEL4 (Nahant Update 5), kernel 2.6.9-55.EL has this bug. In RHEL5.2(Tikanga), kernel 2.6.18-92.el5 the bug is fixed.
Possible workarounds are:
Typically, the crash is caused by SIGILL (si_errno=0, si_code=1 (ILL_ILLOPC)) signal.
Workarounds are: