Kernel Patch 108528-26 bad?

On machine: SunOS boedev 5.8 Generic_108528-14 sun4u sparc SUNW,UltraAX-MP
As part of the J2SE recommended patches, I attempted install of the downloaded 108528-26 kernel patch and received:
<snip>
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: source path </export/home/src/J2SE_Solaris_8_Recommended/108528-2
6/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is c
orrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/J2SE_Solaris_8_Recommended/108528-2
6/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is
corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
------------------------------>
Then, without rebooting, I downloaded the separate patch 108528-26 and attempted to load with patchadd...basically the same result:
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/
platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/
platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
I think this patch is "bad" as it has been released... but I have as yet seen no acknowledgement of that. Anyone else tried this patch?!
The machine reboots and runs, but in what state is it left with the new patches running on the old kernel?
I have posted this to other related groups. Thanks. jj.

JJ,
I downloaded and tried to install this patch this weekend. I am having the same problems. Anyone know where I can get patch 108528-21? I need this for a piece of software I am installing.
Thanks,
Sherryl

Similar Messages

J2EE Recommended Patch Cluster fails with Kernel patch 108528-26

As part of the J2EE recommended cluster, I attempted installing patch 108528-26 to my Solaris 8 box (all of which was downloaded from sun.com):
SunOS boedev 5.8 Generic_108528-14 sun4u sparc SUNW,UltraAX-MP
It failed and rolled back as part of the cluster with the following error log:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Without rebooting, I then downloaded the patch from sunsolve as a separate patch and attempted to load it with patchadd, to no avail but with additional errors (WARNING:) along with the original ones:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Now I have a box with many J2EE patches but without the proper kernel!!! Halp! jj.

did you try and removed the IDR? I.e: patchrm IDR138540-01 ?
.7/M.

Kernel Patch upgrade results into error

Recently, we upgraded our R/3 640 kernel from patch number 196 to 327. It went successful.
But now, the Sales and order team is having problem in saving the orders(VA02, VA01).
While saving Sales order, error pops up saying "dialog step number missing".
Kindly suggest.

Hi ppl,
The problem has been resolved.
As i said, problem wasnt with the upgrade, but came thereafter, functional team faced issues while switching between the windows.
Problem was with the Gui level, it needed to be upgraded too after the kernel patch upgrade.
Thanks a lot for putting your thoughts.
Thanks

ABAP and Kernel Patches for Upgrade and Conversion in 4.6C

Hi,
We are in a process of upgrade and unicode conversion for the source release 4.6C (Kernel 46D_EXT Patch 2225).
"Combined Upgrade&Unicode Conversion Guide" for "SAP Basis 4.6C u2192 SAP NetWeaver 7.0 application Server ABAP Unicode Including Enhancement Package 1 Support Package 01 - 06" , In Software Requirements step, it says
"3. Import 4.6D Kernel patch 2326 from SAP Service Marketplace according to SAP Note 19466"
We wanted to know whether "IT IS ABSOLUTELY NECCESSARY TO GO FOR THE KERNEL PATCH 2326". We dont have "EBCIDIC code pages" in our MDMP system.
We need to know becauase we are also doing OS migration from AIX to Sun and this step will add to our production downtime.
Please advice what are the other causes we should go for the kernel 2326.
Regards

Hello Mr. Nils Buerckel,
Thanks for the reply.
We wanted to be very sure whether we should used Kernel 46D Kernel patch 2326 (As it is specifically mentioned in the SAP CU&UC guide and in SAP Note 867193, It is mentioned that "This patch contains enhancements that are required to execute the "INDX Analysis" scan)
OR
Can we go for the latest kernel patch avaialable at market place? And Will the latest kernel patch also contains the "enhancements that are required to execute the "INDX Analysis" ?
Please reply
Thanks

Static library not accessed properly after Solaris Kernel patch update !

Hi,
We are facing a sever issue in our application after our customer updated the Solaris 10 kernel patch u9 to u10.
We have two static libraries libdlib.a and libDLIB.a, with exactly same code base, but these two libraries are scattered across the code base and linked by many shared objects in our application.
However, one of the shared objects that links to "libdlib.a" library tries to access a function from "libDLIB.a". This behavior is causing a crash at a later point, since that shared object is supposed to access the function from "libdlib.a". Moreover, we found this is happening through the use of dbx.
I'm unable to understand why this problem surfaced after kernel patch update, though still the shared object works fine on Solaris 10 u9 patch.
Flow is something like this :
1. syslogrecorder.so gets loaded by one of the processes.
2. syslogrecorder.so is linked to "libdlib.a" at compile time, so it uses "libdlib.a" function DLIB_LoadLibrary and gets a handle to all the function pointers of the loaded library ( The purpose of DLIB_LoadLibrary is to load a shared library dynamically using dlopen )
3. syslogrecorder.so tries to do a "dlsym" and to do that it needs access to the library handle which we got in previous call DLIB_LoadLibrary. So syslogrecorder.so calls another function from DLIB_ProcAddress, which actually gives back the access to the loaded shared library.
Here is a catch in step 3, it is supposed to call DLIB_ProcAddress from the libdlib.a but as we observed from dbx output it does so by calling DLIB_ProcAddress from libDLIB.a and hence fails to give back the access to loaded shared library, causing crash at a later point in code.
Can someone put some light here that why this could happen ??
Thanks
Kuldeep

To clarify: You did not modify or rebuild any of your binaries, but after installing a kernel patch, the application stopped working. Most likely, something about your application depended on a accidental behavior of the runtime loader. That accidental behavior changed due to the patch, and your application failed.
For example, if there is a circular dependency among shared libraries, the loader will break the cycle at an arbitrary point to establish an initialization order. By accident, that order might work, in the sense of not causing a problem. A change to the loader could cause the cycle to be broken at a different point, and the resulting initialization order could cause a now-uninitialized object to be accessed. I'm not saying this is what is wrong, but this is an example of a dependency on accidental loader behavior.
Finding your actual problem will require tracing the sequence of operations leading up to the failure. You are more likely to find help in a Solaris linker forum. AFAIK, there are currently no Oracle forums for Solaris, and the old OpenSolaris forums have been converted to mailing lists. You can try the "tools-linking" list found on this page:
http://mail.opensolaris.org/mailman/listinfo
I also suggest you review the paper on best practices for using shared libraries written by Darryl Gove and myself:
http://www.oracle.com/technetwork/articles/servers-storage-admin/linkinglibraries-396782.html
If you have a service contract with Oracle, you can use your support channel to get more help.
Edited by: Steve_Clamage on May 18, 2012 3:21 PM

Can I take my OS on kernel patch backwards?

Hi All,
I know that this is a weird question.
Can I take my OS one (or two) kernel patch backwards?
Lets say from "Generic_120011-14" to "Generic_118833-36". ? is it possiblle?
All this mass is beacuse of a testing team at my work.
Thanks!!!!

It depends on how you got to 120011-14.
If your initial install was 118833-36 or earlier and you patched up to 120011-14, then in theory you can back out the patches.
But the initial install was higher than 118833-36. Or you live upgraded past it then you can't go back.
Even if you patched past it, it would be a difficult excercise because there are a lot of related patches that rely on the higher kernel. So you would need to backout any patches that rely on it first.

Kernel patch level

hello,
We have 3 system landscape DEV, QAS & PRD on HP-UX, oracle 9.2, ECC 5.0.
kerne patch level of DEV system is 196 and QAS system is 347 and PRD system's kernel patch level is 196
can this is affect on request transporting DEV to QAS and PRD or any issues plz. guide me
thanks

Hi,
No problems for tranports but you're not qualifying what will be running on production....
The whole point of a quality system is to use exactly the same release, kernel patch levels and SP levels as the prodcution system.
Regards,
Olivier

Pchdtv hd-3000 kernel patches

I just purchased an HD-3000 HDTV card from http://www.pchdtv.com. Their instructions are for Fedora Core 2. Since I can't stand Fedora, and I have Arch installed, I was wondering if anyone knew how to install the kernel driver for this card in Arch. On their downloads page, there are kernel patches, but I've never installed a kernel patch before. The patches appear to be for kernel 2.6.3 and 2.6.6. I know that my kernel is 2.6.9. Would I have to go back some kernels in order to use the patch? How does one go about using a kernel patch?
Thanks for any assistance on this topic.

http://www.thegeorges.us/mythtv/
there's a patch on there.

How do I see the Kernel patch level in Java ONLY instance?

Could someone please tell me How do I see the Kernel patch level in a Java ONLY instance?
In Abap, it is simple!
In Java I see in the System Info: Kernel Version: 7.00 PatchLevel 108458.44
BUT that doesn't correspond to the real patch level which I can see when I do disp+work which gave me 111

Hello Yechezkel,
I am not sure whether the patch number you are looking for is available.
Typically you can use "-v" to display the patch level of SAP kernel programs. When I run "jcontrol -v" or "jlaunch -v", the patch number is blank (at least on the 6.40 release I checked)
The SP level should be able to tell how current the Java instance is updated, especially for NetWeaver 7 systems always patched with JSPM stack.
Best regards,
Victor

Applied Kernel Patch to Solaris 10 on v40z, no longer auto boots

I recently updated the patches on a v40z machine including a kernel patch. After rebooting, the machine would no longer automatically boot to Solaris. Instead it would just wait for user input at the Grub bootloader screen. Anyone experienced this or have a solution?
I believe the patch in question is 118855-19
# bootadm list-menu
The location for the active GRUB menu is: /boot/grub/menu.lst
default 0
timeout 10
0 Solaris 10 6/06 s10x_u2wos_09a X86
1 Solaris failsafe

SOLVED:
Disabled ECC in the bios (though Windows and Gentoo Linux show now trouble whatsoever with my ECC memory, solaris doesn't like it)

Kernel patch for more CPU families offers measurable speed increases

I wanted to show folks a pretty nice patch that allows one more options when compiling a kernel for CPU families. Complete list included at the bottom of this post. I tested it using three different x86_64 machines running a generic x86-64 kernel and an otherwise identical kernel running with the optimized gcc options.
Conclusion: There are small but real speed increases using a make endpoint to building with this patch.
Details:
1) Three test machines: Intel Xeon X3360, Intel i7-2620M, Intel Core i7-3660K.
2) All ran the make benchmark (linked below) 35 times while booted into a 'generic' kernel. Then all ran the same make benchmark 35 times after booting into an optimized kernel. Below are the optimizations chosen for each machine.
2a) X3360 = core2
2b) i7-2620M = corei7-avx
2c) i7-3660K = core-avx-i
3) Analyzed resulting distributions for statistical significance via ANOVA plots that clearly show statistically significant albeit small differences.
Discussion
1) All the assumptions for ANOVA are met:
*Data are normally distributed as show in the normal quantile plots.
*The population variances are fairly equal (Levene and Barlett tests).
2) The ANOVA plots clearly show significance.
*Pair-wise analysis by Tukey-Kramer shows significance at the 0.05 level for all CPUs compared.
Below are the differences in median values:
core2 +87.5 ms
corei7-avx +79.7 ms
core-avx-i +257.2 ms
References:
Kernel patch: https://github.com/graysky2/kernel_gcc_patch
Bash script that controls the benchmark: https://github.com/graysky2/bin/blob/master/bench
Log file generated by script: http://repo-ck.com/bench/compile_time_o … ion.txt.gz
Links to ANOVA plots:
Complete list of x86_64 CPU Families:
1. AMD Opteron/Athlon64/Hammer/K8 (MK8)
2. AMD 61xx/7x50/PhenomX3/X4/II/K10 (MAMDFAM10) (NEW)
3. AMD Barcelona (MBARCELONA) (NEW)
4. AMD Bobcat (MBOBCAT) (NEW)
5. AMD Bulldozer (MBULLDOZER) (NEW)
6. AMD Piledriver (MPILEDRIVER) (NEW)
7. Intel P4 / older Netburst based Xeon (MPSC)
8. Intel Core 2 (MCORE2)
9. Intel Core i7 (MCOREI7) (NEW)
11. Intel Core 2nd Gen AVX (MCOREI7AVX) (NEW)
12. Intel Core 3rd Gen AVX (MCOREAVXI) (NEW)
13. Intel Core AVX-2 (MCOREAVX2) (NEW)
14. Intel Atom (MATOM)
15. Generic-x86-64 (GENERIC_CPU)
Complete list of i686 CPU Families:
1. 386 (M386)
2. 486 (M486)
3. 586/K5/5x86/6x86/6x86MX (M586)
4. Pentium-Classic (M586TSC)
5. Pentium-MMX (M586MMX)
6. Pentium-Pro (M686)
7. Pentium-II/Celeron(pre-Coppermine) (MPENTIUMII)
8. Pentium-III/Celeron(Coppermine)/Pentium-III Xeon (MPENTIUMIII)
9. Pentium M (MPENTIUMM)
10. Pentium-4/Celeron(P4-based)/Pentium-4 M/older Xeon (MPENTIUM4)
11. AMD K6/K6-II/K6-III (MK6)
12. AMD Athlon/Duron/K7 (MK7)
13. AMD Opteron/Athlon64/Hammer/K8 (MK8)
14. AMD 61xx/7x50/PhenomX3/X4/II/K10 (MAMDFAM10) (NEW)
15. AMD Barcelona (MBARCELONA) (NEW)
16. AMD Bobcat (MBOBCAT) (NEW)
17. AMD Bulldozer (MBULLDOZER) (NEW)
18. AMD Piledriver (MPILEDRIVER) (NEW)
19. Crusoe (MCRUSOE)
20. Efficeon (MEFFICEON)
21. Winchip-C6 (MWINCHIPC6)
22. Winchip-2/Winchip-2A/Winchip-3 (MWINCHIP3D)
23. AMD Elan (MELAN)
24. GeodeGX1 (MGEODEGX1)
25. Geode GX/LX (MGEODE_LX)
26. CyrixIII/VIA-C3 (MCYRIXIII)
27. VIA C3-2 (Nehemiah) (MVIAC3_2)
28. VIA C7 (MVIAC7)
29. Intel Core 2 (MCORE2)
30. Intel Core i7 (MCOREI7) (NEW)
31. Intel Core 2nd Gen AVX (MCOREI7AVX) (NEW)
32. Intel Core 3rd Gen AVX (MCOREAVXI) (NEW)
33. Intel Core AVX-2 (MCOREAVX2) (NEW)
34. Intel Atom (MATOM)
Last edited by graysky (2013-01-16 19:14:09)

graysky wrote:Practically, why do you need more than a few frequencies? For example, you're idle. I would want the lowest freq. You're under load. I would want the highest frequency. For situations in between, say launching a program, or moving data, whatever, an intermediate frequency would be fine. What do you hope to achieve with a more refined list of available frequencies?
I agree, your CPU, in practice, is really either idle or loaded.
In my case (AMD 965, 4 freq steps) the processor is at lowest freq for about 90 - 95% of a time, and at highest for 5 - 10%. The 2 intermediate are used for about 0.1% of a time.
My guess would be that intermediate ones are only used for smooth transition from lowest to highest. So they really are hardware dependent...

Kernel patch 127128-11 renders my x86 system unbootable - what to do?

Just installed some patches with smpatch as usual, kernel patch 127128-11 among them. I then dropped to single user mode to finish the installation, rebooted and... nothing. I get the SunOS copyright notice, and then nothing but a flashing cursor... I waited for half an hour, but nothing happened, no disk activity, keyboard not responding, nothing.
I had to reset the stupid machine...
This happened on old(ish) HP Vectra SFF.
What I can do now? What are my options? (And please DON'T say: "reinstall everything"!!!)
I have used Linux for 7-8 years, but Solaris is pretty new for me, this installation is some 2 months old (Sun Solaris 10 - 8/07 - x86)

I remember I ever tried a tool that you need to run in order to put your computer on the list.
Well it suddenly crashed and I didn't try it again.The certification tool: http://www.sun.com/bigadmin/hcl/hcts/
At Sun they know very well which systems I'm running Solaris on.
This data is sent when you register to apply for updates.They don't use your registration info to list a system as certified to run Solaris10. See link above.
I have to admit I never added any patches by going into single user mode.I install in single user per instructions in patch README. I have rarely had issues installing patches this way.
Reading back this thread I see that this patch was part of the Solaris 10 5/08 version
and since I recently upgraded to this version and everything is working fine,
I don't think there is an issue. Neither do I think that there is an issue with 127128-11 patch, which is why I mentioned that OPs machine was not on HCL. It's an issue with OPs hardware, not the new kernel. So, what is that 'fix' disabling so that Solaris will run on unsupported hardware?
I haven't tried OpenSolaris yet. What do you think of it so far?

Last kernel patch for Solaris 10 x86 screwed up my kernel

Hi,
The last kernel patch for Solaris 10 x86 (sorry I can�t remember the patch id, but the revision is 30), available from Sun Update Manager screwed up my system.
The system is still booting but in maintenance mode: smf can't start because of repository corrupted. Given instructions to restore the repository does not work because / filesystem is mounted read-only...
As I am not a solaris expert, I will reinstall it from CD. I hope I won't loose the filesystem.
I was used to blindly trust Sun solaris patches, that was a mistake.
Laurent.

i dont know why but still i do get default log in into the single mode
after startup
Requesting maintenance mode
(See /lib/svc/share/README for aditional information. )
Root password for system maintenance (control-d to bypass):i did removed the patch installed before so now
SunOS jorgito 5.10 Generic_118844-26 i86pc i386 i86pcand finaly i do have milestone like this
bash-3.00$ svcprop restarter | grep mile
options/milestone astring svc:/milestone/multi-user:default
dont know what to do else, also tried to synchronize boot-archive from solaris failsafe ...

Kernel patch updation for solaris 10 x86

I have Solaris 10 06/06 installed on x86 machine which is using svm and clustered with another node. The kernel revision is 118855-19 from the uname -a output. I am looking for the kernel patch updation and I heard 118855-36 is the latest one. Shall I go ahead with this patch and what r the dependency patches for this.
If anyone done this please guide me..

Patch 118855-36 is the latest kernel patch for Solaris 10 on x86 and its dependencies are:
113000-01 117435-02 118344-14 119043-09 119255-14 121264-01 122035-01 123840-01 (or greater)
Whether you should go ahead and install the patch is up to you, if possible try it out on a test box first. For better advice on this matter, I would suggest posting in the Solaris 10 forum as this forum is for the Sun Update Connection, Patch Manager & PatchPro toolsets.

Kernel patch update for solaris 10 x86

I have Solaris 10 06/06 installed on x86 machine which is using svm and clustered with another node. The kernel revision is 118855-19 from the uname -a output. I am looking for the kernel patch updation and I heard 118855-36 is the latest one. Shall I go ahead with this patch and what r the dependency patches for this.
If anyone done this please suggest and guide me..

For Solaris 10 x86 the latest offered with smpatch is 125101-07 and yes it may be recommended to patch. Then again you said clustered with sun cluster? You may want to check the documentation and if your machines aren't facing the internet you may wait for 7/07 to hit the street and do an upgrade.

Kernel Patch 108528-26 bad?

Similar Messages

Maybe you are looking for