Kernel Patching with zones

I have a T2000 installed with the Solaris 10 1/06 release with several zones created on it. 4 zones are "sparse" root, and one (zone-5) is a "whole root" zone.
In order to apply and certify (internally) the latest sendmail patch, Solaris 10 needs a later kernel patch than I had installed (this is a subject for another discussion...). So I downloaded the latest patch cluster (4/6 Recommended cluster) to apply it.
I shut down the non-global zones, and took the machine to single user mode, and installed the cluster. It seemed to go in fine, except for the following error:
Zone zone-5
Rejected patches:
122856-01
Patches that passed the dependency check:
None.
Fatal failure occurred - impossible to install any patches.
zone-5: For patch 122856-01, required patch 118822-30 does not exist.
Fatal failure occurred - impossible to install any patches.Now, 118822-30 is a kernel patch series that is prerequisite for the latest kernel patch (118833-03). Zone-5 is my only whole-root zone. I then looked at the patch cluster log, and discovered that a handful of patches (including 118822-30) had also failed:
titan15n> grep failed /var/sadm/install_data/Solaris_10_Recommended_Patch_Cluster_log
Pkgadd failed. See /var/tmp/119254-19.log.6615 for details
Pkgadd failed. See /var/tmp/118712-09.log.9307 for details
Pkgadd failed. See /var/tmp/119578-18.log.15160 for details
Pkgadd failed. See /var/tmp/121308-03.log.18339 for details
Pkgadd failed. See /var/tmp/119689-07.log.22068 for details
Pkgadd failed. See /var/tmp/118822-30.log.9404 for details
Pkgadd failed. See /var/tmp/119059-11.log.29911 for details
Pkgadd failed. See /var/tmp/119596-03.log.4724 for details
Pkgadd failed. See /var/tmp/119985-02.log.8349 for details
Pkgadd failed. See /var/tmp/122032-02.log.13334 for details
Pkgadd failed. See /var/tmp/118918-14.log.27743 for detailsLooking at any of these logs (in the non-global zone-5's /var/tmp directory shows failures like the following snippet:
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/cheetahregs.h6HaG8w>: (30) Read-only file sy
stem
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/clock.h7HaG8w>: (30) Read-only file system
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/dvma.h8HaG8w>: (30) Read-only file systemQuestion(s):
Why would there be read-only file systems where tmp files are getting written? Possibly a timing issue?
Is there a "best practice" on applying patch clusters, and specifically, the kernel patch? Did I make a mistake in taking the zones down first? It seems like the zones were being booted up as the patches were getting applied, but I may be misinterpreting the output.
Even though the patches failed to apply to zone-5, the uname -a output in the zone show the latest kernel patch, but does NOT show 118822-30 (118822-25 is what showrev -p in the non-global zone-5 shows -- which is the level I was at before attempting to patch).
Any solutions?
Thanks.

The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
I notice in the build I get this message -
==> Building the kernel
fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
CHK include/linux/version.h

Similar Messages

Kernel patching with ABS

I have a problem with the newest kernel (kacpid takes 90% of cpu), so I found a patch on kernel.org bugzilla, located at http://bugzilla.kernel.org/show_bug.cgi?id=10224#c25
I really have no clue what I am doing, but I carried on regardless.
I copied /var/abs/core/kernel26 into ~/builds/, put the patch into kernel26/src called acpi.patch and edited the PKGBUILD like so:
I added patch -Np1 -i $startdir/src/acpi.patch || return 1
# $Id: PKGBUILD 1759 2008-05-16 13:58:54Z thomas $
# Maintainer: Tobias Powalowski <[email protected]>
# Maintainer: Thomas Baechler <[email protected]>
pkgname=kernel26
_basekernel=2.6.25
pkgver=2.6.25.4
pkgrel=1
_patchname="patch-${pkgver}-${pkgrel}-ARCH"
pkgdesc="The Linux Kernel and modules"
arch=(i686 x86_64)
license=('GPL2')
groups=('base')
url="http://www.kernel.org"
backup=(etc/mkinitcpio.d/${pkgname}.preset)
depends=('coreutils' 'module-init-tools' 'mkinitcpio>=0.5.18')
# pwc, ieee80211 and hostap-driver26 modules are included in kernel26 now
# nforce package support was abandoned by nvidia, kernel modules should cover everything now.
# kernel24 support is dropped since glibc24
replaces=('kernel24' 'kernel24-scsi' 'kernel26-scsi'
'alsa-driver' 'ieee80211' 'hostap-driver26'
'pwc' 'nforce' 'squashfs' 'unionfs' 'ivtv'
'zd1211' 'kvm-modules' 'iwlwifi' 'rt2x00-cvs')
install=kernel26.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
ftp://ftp.archlinux.org/other/kernel26/${_patchname}.bz2
# the main kernel config files
config config.x86_64
# standard config files for mkinitcpio ramdisk
kernel26.preset)
md5sums=('db95a49a656a3247d4995a797d333153'
'bf582e97c84be9abce998a8d640f4ae7'
'777d94911faa1cb480832b1c47bee307'
'2b19c2ff9abd0e6d0ad1e29f124021c3'
'25584700a0a679542929c4bed31433b6')
build() {
KARCH=x86
cd $startdir/src/linux-$_basekernel
# Add -ARCH patches
# See http://projects.archlinux.org/git/?p=linux-2.6-ARCH.git;a=summary
patch -Np1 -i $startdir/src/${_patchname} || return 1
patch -Np1 -i $startdir/src/acpi.patch || return 1
if [ "$CARCH" = "x86_64" ]; then
cat ../config.x86_64 >./.config
else
cat ../config >./.config
fi
# build the full kernel version to use in pathnames
. ./.config
### next line is only needed for rc kernels
_kernver="2.6.25${CONFIG_LOCALVERSION}"
#_kernver="${_basekernel}${CONFIG_LOCALVERSION}"
# load configuration
yes "" | make config
# build!
# stop here
# this is useful to configure the kernel
#msg "Stopping build"
#return 1
make bzImage modules || return 1
mkdir -p $startdir/pkg/{lib/modules,boot}
make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1
cp System.map $startdir/pkg/boot/System.map26
cp arch/$KARCH/boot/bzImage $startdir/pkg/boot/vmlinuz26
install -D -m644 Makefile \
$startdir/pkg/usr/src/linux-${_kernver}/Makefile
install -D -m644 kernel/Makefile \
$startdir/pkg/usr/src/linux-${_kernver}/kernel/Makefile
install -D -m644 .config \
$startdir/pkg/usr/src/linux-${_kernver}/.config
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include
for i in acpi asm-{generic,x86} config linux math-emu media net pcmcia scsi sound video; do
cp -a include/$i $startdir/pkg/usr/src/linux-${_kernver}/include/
done
# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers $startdir/pkg/usr/src/linux-${_kernver}
cp -a scripts $startdir/pkg/usr/src/linux-${_kernver}
# fix permissions on scripts dir
chmod og-w -R $startdir/pkg/usr/src/linux-${_kernver}/scripts
#mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/.tmp_versions
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel
cp arch/$KARCH/Makefile $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
if [ "$CARCH" = "i686" ]; then
cp arch/$KARCH/Makefile_32.cpu $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
fi
cp arch/$KARCH/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel/
# add headers for lirc package
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video
cp drivers/media/video/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/
for i in bt8xx cpia2 cx25840 cx88 em28xx et61x251 pwc saa7134 sn9c102 usbvideo zc0301; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
cp -a drivers/media/video/$i/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
done
# add dm headers
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
cp drivers/md/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
# add inotify.h
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include/linux
cp include/linux/inotify.h $startdir/pkg/usr/src/linux-${_kernver}/include/linux/
# add CLUSTERIP file for iptables
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/ipv4/netfilter/
# add wireless headers
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
cp net/mac80211/*.h $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
# add dvb headers for external modules
# in reference to:
# http://bugs.archlinux.org/task/9912
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core
cp drivers/media/dvb/dvb-core/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core/
# add xfs and shmem for aufs building
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/fs/xfs
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/mm
cp fs/xfs/xfs_sb.h $startdir/pkg/usr/src/linux-${_kernver}/fs/xfs/xfs_sb.h
# add vmlinux
cp vmlinux $startdir/pkg/usr/src/linux-${_kernver}
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-${_kernver}/$i
done
cd $startdir/pkg/usr/src/linux-${_kernver}/include && ln -s asm-$KARCH asm
chown -R root.root $startdir/pkg/usr/src/linux-${_kernver}
find $startdir/pkg/usr/src/linux-${_kernver} -type d -exec chmod 755 {} \;
cd $startdir/pkg/lib/modules/${_kernver} && \
(rm -f source build; ln -sf ../../../usr/src/linux-${_kernver} build)
# install fallback mkinitcpio.conf file and preset file for kernel
install -m644 -D $startdir/src/${pkgname}.preset $startdir/pkg/etc/mkinitcpio.d/${pkgname}.preset || return 1
# set correct depmod command for install
sed -i -e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/g" $startdir/kernel26.install
echo -e "# DO NOT EDIT THIS FILE\nALL_kver='${_kernver}'" > ${startdir}/pkg/etc/mkinitcpio.d/${pkgname}.kver
# remove unneeded architectures
rm -rf $startdir/pkg/usr/src/linux-${_kernver}/arch/{alpha,arm,arm26,avr32,blackfin,cris,frv,h8300,ia64,m32r,m68k,m68knommu,mips,parisc,powerpc,ppc,s390,sh,sh64,sparc,sparc64,um,v850,xtensa}
It compiled fine and so I though all was well, but when installing, I get the following errors.
(1/1) upgrading kernel26 [####################################################################################################] 100%
>>>
>>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
>>>
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]generic' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ahci' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]piix' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
find: /lib/modules/2.6.25-ARCH: No such file or directory
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]generic' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ahci' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]piix' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
Is that kernel safe to boot from or not - the No such file or directory errors are worrying.

The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
I notice in the build I get this message -
==> Building the kernel
fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
CHK include/linux/version.h

Kernel Patch Update

Hi
I have a question about updating the kernel patch to the latest version Can a kernel patch be directly updated from any lower version to the latest version by applying the latest patch even if the kernel patch number itself has changed like the below scenarios
1. Can I directly update the kernel pacth 122300-51 to 122300-57
2.Can I directly update the kernel patch 142909-17 to 144488-17
Thanks in advance

Basically, yes, but you need to take care of the patch dependencies. Usually a kernel patch with a new patch ID will require the last revision of each former kernel patch to be installed first.
Either you use patchadd on the most recent kernel patch you want to apply and then work yourself back through the patch dependencies, or you use PCA (http://www.par.univie.ac.at/solaris/pca/) which will do this job for you. Use e.g. "pca -l 144488" to get a list of all the patches which have to be installed first to get the system up to the wanted kernel patch level.

Deferred patching broken for machines with zones

For a while I've noticed that Ive had trouble patching a couple of machines.
I've managed to determine the significant characteristic identifying them.
All the machines with a non global zone have the problem.
To confirm, I added a test zone to a machine that was fine. And it immediately it developed the problem.
Anyway, the symptom is that no deferred patches will install.
So patches delayed by a "smpatch update" till the reboot fail to install.
The sunucLog displays the following error
Sep 17 10:30:05 webdb1 123186-03 [notice] Status Install Begin 123186-03
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Validating patches...
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Loading patches installed on the system...
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Loading patches requested to install.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Checking patches that you specified for installation.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] svcadm: Instance "svc:/system/filesystem/local:default" has been disabled by another entity.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] ERROR: Enabling filesystem/local service failed.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Status Install End 123186-03 Install Update installation failed
Anyone got any workarounds for this problem.
Is it a known issue.
Or should I log a support request.

Any progress on this? Its been 2 months. And sun has managed to put out an entire new update to Solaris.
And a 119254-59 has been released. But neither includes a fix for this issue as far as I can tell...
Its now basically impossible to patch machines with zones up to the latest kernel 137137-09 since that has a dependency on 119254-58.
And machines with zones can't be patched if a version higher than 119254-53 is installed....

Is patching Sol 10 machines with zones safe?

Now that Sun update has been released, "smpatch update" explicitly checks for the presence of non global zones and refused to run.
Now, its fairly trival to reproduce the "smpatch update" functionality from "smpatch download" which still works and a bit of scripting.
Ive done this on a test machine with zones with no obvious ill effects.
However since Sun went to the trouble of disabling "smpatch update", you have to presume there was a good reason.
So is patching machines with zones safe. Or is there some known problem with doing this.

The problem was that the underlying tool patchadd was not zones aware and then changes (I believe for bug: 6200143 ) changed the exit codes that smpatch relies on.
Now in Solaris 10 patchadd/patchrm now returns only an exit code of 1 or 0 when using zones which is insufficient both for smpatch and for the Update Manager.
So there are two options:
If the system does not have any local zones configured then you can run "patchadd -t" in transitional mode which reverts back to the old pre Solaris 10 rich return codes that smpatch needs.
If there are zones on the system, using smpatch download + patchadd will work, but you cannot get rich status from patchadd:
Running "patchadd -t" on a system with local zones gives:
# patchadd -t
Transition patching (-t option) is not supported in a zones environment.
HTH
ethan

[Solved] Error compiling kernel 2.6.36.2 patched with MOSIX

Hi, I'm a new user in this forum!
I'm trying to compile manually the kernel version with MOSIX-2.29.0.1 for computer clustering. But When I try to compile it with make command there is an error:
In file included from arch/x86/kernel/signal.c:17:0:
include/linux/tracehook.h: In function ‘tracehook_unsafe_exec’:
include/linux/tracehook.h:164:40: error: ‘struct task_struct’ has no member named ‘mflags’
arch/x86/kernel/signal.c: In function ‘do_notify_resume’:
arch/x86/kernel/signal.c:884:44: error: ‘struct task_struct’ has no member named ‘parent_waiting’
make[2]: *** [arch/x86/kernel/signal.o] Error 1
make[1]: *** [arch/x86/kernel] Error 2
make: *** [arch/x86] Error 2
I have launched make menuconfig and I have configured the kernel in this way:
Configure the following option:
CONFIG_FUSE_FS
File systems ---> FUSE (Filesystem in Userspace) support
CONFIG_SYSVIPC
General setup ---> System V IPC
But make sure that the following is NOT CONFIGURED:
CONFIG_HEADERS_CHECK"
'Kernel hacking' ---> 'Run 'make headers_check' when building vmlinux'
What is the problem?
Last edited by andychaser (2011-02-17 12:37:50)

I've solved the issue, infact there was a problem with the patch. Now I am able to compile the kernel.
Thanks anyway!

ROSS CPU didn't work with kernel patch 112233-07

Just noticed my HyperSPARC (ROSS CPU for S10/S20) had problem with kernel patch.
Got 2 X 180Mhz ROSS CPUs running fine with Solaris 9 (kernel level 112233-07) on S20 until applied the Recommended patches set (kernel level 112233-12), once the patches set installed and reboot, the S20 won't boot up anymore and showed some error on the kernel...
Reinstall again the Solaris 9 (kernel level 112233-07), and applied the Recommended patches set without kernel patch 112233-12, system boot up fine without issue.
Was looking around but didn't find anyone else got same issue (even on Sunsolve site) like me, maybe the box is too old to play with...
Cheers,

Oops, put wrong patch ID in subject...

Steps for Kernel Patch Updation on Solaris 10 X4100 with 2disks mirrored

Hi all,
I have Solaris 10 10/06 (118855-19) installed on one of the X4100 server. This is the time for me to update the latest kernel patch (118855-36). We have two disks mirrored. My questions are,
1) Do i need to detach any of the disk from the mirror before doing any patching.
2) Is it possible to install the patches without detaching any disks from the mirror. (i.e. installeing patch on mirrored root filesystem)
3) how to boot from the second disk in case the patch installation creates problem while booting up.
Any suggestions or steps which you have already implemented for the above scenario.

This isn't really a question for this forum, you may be better to look at some of the sys-admin forums for a complete answer.
You should not need to break the mirror in order to apply the kernel patch, however doing so would allow for quicker recovery of the system should something go wrong during patching.
I would strongly advise that you read the special install instructions for the kernel patch prior to installing it.
http://sunsolve.sun.com/search/document.do?assetkey=1-21-118855-36-1
You may also wish to use a patch cluster rather than smpatch/updatemanager, these can be downloaded from SunSolve:
http://sunsolve.sun.com/private-cgi/show.pl?target=patchpage

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

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

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

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?

Kernel Patching with zones

Similar Messages

Maybe you are looking for