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?

Similar Messages

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.

Latest (November) EIS-Patching ISO for Solaris SPARC & X86 systems download.

Hi All,
I hope someone can assist as this has given me a headache for the last few days.
I require the latest (November) EIS-Patching ISO for Solaris SPARC & X86 systems.
I require the ISO and not just the Patch set.
Please advise.
Kind regards,
Paul

The current ISO (october) is available at the usual place : EIS for Partner
And for information, the next planned EIS will be available very soon but not this month.

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.

Problem with kernel patch 127128-11

I am a bit stomped trying to install this patch successfully.
I log into single user mode.
The patch file is currently located in "/var/sadm/spool"
when I run "patchadd 127128-11" i get the following:
"Patch 127128-11 failed to install due to a failure produced by pkgadd."
============================================================
When I try installing the patch using smpatch with: "smpatch add -i 127128-11"
I get the following error:
"Patch 127128-11 failed to install due to a failure produced by pkgadd."
"PaTch_MsG 23 Patch number 127128-11 cannot be applied until all restricted patches are backed out."
"warning: /usr/bin/disable <no longer a symbolic link>
"warning: /usr/bin/enable <no longer a symbolic link>
"warning: /usr/sbin/reject <no longer a symbolic link>
"warning: /usr/lib/print/psm-lpd.so <no longer a regular file>
"warning: /usr/ucb/lpc <no longer a regular file>
"warning: /usr/ucb/lptest <no longer a regular file>
====================================================
I am still troubleshooting but does anyone have any pointers they would like to share?
Thanks and look forward to your replies

Hi,
I have the same problem and was wondering if anyone had a resolution to it?
Thanks
John

Recent changes in patch entitlement for Solaris 10 sparc systems?

Have there been any, especially those which non-contract customers should know about?
I am running Sol 10 u3 sparc on a Sun Blade workstation. Today, I noticed that some patches already installed on my system are now considered private on SunSolve (e.g. 143510-01). Also, kernel patch 142900-04 is private! I've been using SUM to get kernel patches forever (I am at 142900-03). What happened? Hopefully this is just a glitch. I can't believe that kernel patches will be private from now on!
There is a certain Xsun security patch which I have deliberately not installed. For years, it has come up in SUM. Today, for the first time, it is gone.
I am also running Sol 10 u8 on an x86 system. No problem with patches there - all normal. I installed kernel patch 142901-04 on it today. Also without a support contract.
What is going on?

Gary,
That is a great idea. I've been wondering about other ways Oracle could handle this issue, such as charging per patch, etc. This issue applies very much to Sun Studio 12.1 (see other recent thread about SS patches in this forum). There is NO WAY I, or the organization I work for, could justify spending $1,000+ per year just for SS patches. $300+/year for OS patches may be doable, but still probably wouldn't be worth it, unless SEVERE security holes are discovered that must be patched immediately, which I have never found to be the case over the last 8 years.
Your idea sounds like an ideal solution, but I fear that it is highly unlikely that Oracle would consider it. That would make some manager look bad in having to change his/her "great plan." Oracle should find some way to differentiate big "enterprise" Solaris users from 1-2 box shops who can't afford these pricey support contracts, but still depend on Solaris. For the last 7 years, public patches and these forums have done the job for me, and I have NEVER had to initiate a service or support call or request. That is testament to the stability of Solaris and the brilliance of its engineers.

Problem of SIGPOLL(SI_NOINFO) in latest Solaris9 kernel patch

Hi,
We are facing a rather strange problem with the latest kernel patch on Solaris 9. (Generic_112233-08). We had not faced this problem with any of the other kernel patches of Solaris 9.
Our application has a main thread and a single child thread (pthread). The main thread schedules aio_writes() on the raw disk interface and lets the child thread block on sigwaitinfo() to listen to the signal completion notification. This is communicated to it via the SI_ASYNCIO code of SIGPOLL. The child thread then informs the main thread by writing to a bi-directional pipe. Since the main thread has registered for read interest on the bi-directional pipe (via /dev/poll) it is informed of the completion of the aio_write() without having to block itself. Under normal circumstances, the child thread receives SIGPOLL with SI_ASYNCIO code.
This application has been running fine on all the previous builds of Solaris (Generic, Generic_112233-04, Generic_112233-06) on sparc platform expect with the latest kernel patch. The child thread now keeps receiving SIGPOLL with SI_NOINFO code. There has been no change in our application and we are perplexed to the reason of this behaviour. Since it is SI_NOINFO there is not much debugging information we can get.
We have been able to replicate this behaviour using a small stand-alone program. We are attaching it at the end of the email. We tried this program on a couple of different Sparc systems and were able to reproduce this behaviour on one of them but not on the other.
Has anybody faced problems with regard to SIGPOLL in the latest kernel patch of Solaris 9 for sparc systems ?
Thanks
Regards
Raj Pagaku
proxy-24:~ >uname -a
SunOS proxy-24 5.9 Generic_112233-08 sun4u sparc SUNW,Ultra-5_10
proxy-24:~ >gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.2/specs
Configured with: ../configure with-as=/usr/ccs/bin/as with-ld=/usr/ccs/bin/ld --disable-nls
Thread model: posix
gcc version 3.2
Compiled this program using the following command : gcc -g kernel_bug.c -lrt -lpthread
#include <stdio.h>
#include <aio.h>
#include <errno.h>
#include <fcntl.h>
#include <pthread.h>
#include <signal.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/resource.h>
#include <sys/stat.h>
#include <sys/types.h>
#define min(x,y) (((x)<=(y))?(x):(y))
#define DISPLAY_COUNT 10000
typedef struct DiskInfoCallOut {
void (*func_ptr)(void *);
void *data_ptr;
} DiskInfoCallOut;
typedef struct DiskInfo {
struct aiocb di_aiocb;
DiskInfoCallOut di_callout;
off_t di_currOffset;
int di_scheduled;
} DiskInfo;
typedef struct Disk {
int fd;
char *buffer;
int bufferLen;
} Disk;
static sigset_t aioSignalSet;
int aioSigFD[2];
int glob_scheduled = 1;
int glob_respond = 1;
Disk disk;
static void LaunchDiskOperation(DiskInfo *di);
char BUFDATA[4096] = {'a'};
char rawDeviceName[256] = "/dev/rdsk/";
static void
InitializeDisk()
int fd;
if ((fd = open(rawDeviceName, O_RDWR, 0)) == -1) {
fprintf(stderr, "Unable to open raw device \n");
exit(-1);
disk.fd = fd;
disk.buffer = BUFDATA;
disk.bufferLen = sizeof(BUFDATA);
static void
AIOSignalHandler(int sigNum, siginfo_t* si, void* context)
fprintf(stderr, "WARN: got signal %d in AIOSignalHandler!\n", sigNum);
/* Function implementing the slave thread */
static void*
AIOSignalThread(void *arg)
struct sigaction sa;
siginfo_t info;
sigset_t ss;
int sig_num;
int retVal;
/* Initialize the signal set*/
sigemptyset(&ss);
sigaddset(&ss, SIGPOLL);
if ((retVal = pthread_sigmask(SIG_SETMASK, &ss, NULL))) {
fprintf(stderr, "pthread_sigmask failed in AIOSignalThread \n");
exit(-1);
sa.sa_handler = NULL;
sa.sa_sigaction = AIOSignalHandler;
sa.sa_mask = aioSignalSet;
sa.sa_flags = SA_SIGINFO;
if (sigaction(SIGPOLL, &sa, NULL)) {
fprintf(stderr, "sigaction in AIOSignalThread \n");
exit(-1);
/* Wait infinitely for the signals and respond to the main thread */
while (1) {
sig_num = sigwaitinfo(&aioSignalSet, &info);
if (sig_num != SIGPOLL) {
fprintf(stderr, "caught unexpected signal %d in AIOSignalThread \n",
sig_num);
exit(-1);
if (info.si_code != SI_ASYNCIO){
fprintf(stderr, "ERROR: siginfo_t had si_code != SI_ASYNCIO, si_code = %d \n", info.si_code);
continue;
/* Write the stored pointer value in the pipe so that the main thread can process it */
if (write(aioSigFD[1], &(info.si_value.sival_ptr), sizeof(info.si_value.sival_ptr)) !=
sizeof(info.si_value.sival_ptr)) {
perror("Couldn't write the whole pointer");
exit(-1);
return (NULL);
static void
Init()
pthread_attr_t aioAttr;
pthread_t aioThread;
int retVal = 0;
/* Create a bidirectional pipe */
if (pipe(aioSigFD)) {
perror("pipe failed");
exit(-1);
/* Initialize to prevent other threads from being interrupted by
SIGPOLL */
sigemptyset(&aioSignalSet);
sigaddset(&aioSignalSet, SIGPOLL);
if ((retVal = pthread_sigmask(SIG_BLOCK, &aioSignalSet, NULL))) {
fprintf(stderr, "pthread_sigmask failed in Init\n");
exit(-1);
InitializeDisk();
if ((retVal = pthread_attr_init(&aioAttr)))
fprintf(stderr, "pthread_attr_init failed \n");
if ((retVal = pthread_attr_setdetachstate(&aioAttr, PTHREAD_CREATE_DETACHED)))
fprintf(stderr, "pthread_attr_setdetachstate failed \n");
if ((retVal = pthread_attr_setscope(&aioAttr, PTHREAD_SCOPE_SYSTEM)))
fprintf(stderr, "pthread_attr_setscope failed in \n");
if ((retVal = pthread_attr_setstacksize(&aioAttr, 2*1024*1024)))
fprintf(stderr, "pthread_attr_setstacksize failed \n");
if ((retVal = pthread_create(&aioThread, &aioAttr,
AIOSignalThread, NULL)))
fprintf(stderr, "pthread_create failed \n");
static void
UpdateDiskWriteInformation(DiskInfo *di)
di->di_currOffset += disk.bufferLen;
di->di_scheduled = 0;
static void
DiskOpCompleted(void *ptr)
DiskInfo di = (DiskInfo )ptr;
if (aio_error(&di->di_aiocb))
perror("aio_error");
if (aio_return(&di->di_aiocb) < 0)
perror("aio_return ");
UpdateDiskWriteInformation(di);
glob_respond++;
static void
LaunchDiskOperation(DiskInfo *di)
int res;
di->di_callout.func_ptr = DiskOpCompleted;
di->di_callout.data_ptr = di;
memset(&di->di_aiocb, 0, sizeof(di->di_aiocb));
di->di_aiocb.aio_fildes = disk.fd;
di->di_aiocb.aio_buf = disk.buffer;
di->di_aiocb.aio_nbytes = disk.bufferLen;
di->di_aiocb.aio_offset = di->di_currOffset;
di->di_scheduled = 1;
di->di_aiocb.aio_sigevent.sigev_notify = SIGEV_SIGNAL;
di->di_aiocb.aio_sigevent.sigev_signo = SIGPOLL;
di->di_aiocb.aio_sigevent.sigev_value.sival_ptr = &di->di_callout;
res = aio_write(&di->di_aiocb);
if (res == -1) {
perror("aio op error");
static void
HandleSignalResponses()
int fd;
#define DISKINFO_CALLOUT_MAX 64
DiskInfoCallOut* callout[DISKINFO_CALLOUT_MAX];
struct stat pipeStat;
int numCompleted;
int bytesToRead;
int sz;
int i;
fd = aioSigFD[0];
while (1) {
/* Find whether there is any data in the pipe */
if(-1 == fstat(fd, &pipeStat)) {
perror("fstat");
exit(-1);
if (pipeStat.st_size < sizeof(DiskInfoCallOut *))
break;
numCompleted = min((pipeStat.st_size/sizeof(DiskInfoCallOut *)),DISKINFO_CALLOUT_MAX);
bytesToRead = numCompleted * sizeof(DiskInfoCallOut *);
if ((sz = read(fd, callout, bytesToRead)) != bytesToRead) {
perror("Error reading from pipe");
exit(-1);
for (i = 0; i < numCompleted; i++)
(*callout[i]->func_ptr)(callout[i]->data_ptr);
int main(int argc, char *argv[])
DiskInfo *di;
FILE *logPtr1 = NULL;
FILE *logPtr2 = NULL;
FILE *logPtr3 = NULL;
struct rusage ru;
struct timeval t1, t2;
long timeTaken = 0;
int writeCount = 0;
int i;
char logFileName1[1024];
char logFileName2[1024];
char logFileName3[1024];
if (argc < 2) {
fprintf(stderr, "Usage : %s <partition_name> \n", argv[0]);
exit(-1);
strcat(rawDeviceName, argv[1]);
writeCount = 1;
printf("Partition selected = %s \n", rawDeviceName);
di = calloc(writeCount, sizeof(DiskInfo));
sprintf(logFileName1, "%s.log1", argv[0]);
if ((logPtr1 = fopen(logFileName1, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
sprintf(logFileName2, "%s.log2", argv[0]);
if ((logPtr2 = fopen(logFileName2, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
sprintf(logFileName3, "%s.log3", argv[0]);
if ((logPtr3 = fopen(logFileName3, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
Init();
for (i = 0; i < writeCount; i++) {
di.di_currOffset = (1 << 18) * (i + 1);
di[i].di_scheduled = 0;
gettimeofday(&t1, NULL);
while (1) {
int curScheduled = 0;
/* Schedule the disk operations */
for (i = 0; i < writeCount; i++) {
if (di[i].di_scheduled == 0) {
LaunchDiskOperation(&di[i]);
glob_scheduled++;
curScheduled++;
/* Handle the responses */
HandleSignalResponses();
if ((curScheduled) && (glob_respond % DISPLAY_COUNT == 0)) {
gettimeofday(&t2, NULL);
timeTaken = ((t2.tv_sec * 1000000 + t2.tv_usec) -
(t1.tv_sec * 1000000 + t1.tv_usec))/1000;
printf("Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(logPtr1, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr1 ..\n");
fprintf(logPtr2, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr2 ..\n");
fprintf(logPtr3, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr3 ..\n");
t1 = t2;

Hi @cooldog ,
I hit this same LVM2 snapshot kernel oops on several Oracle Linux 6.5 servers running UEK R3 kernel version 3.8.13-16.3.1. I have Linux Premier Support so I opened a Service Request. Oracle Support got back to me with the following notes.
Hello Matt,
Bug 17487738 : EXT4: STRESS TESTING WITH SUSPEND/RESUME FS ACCESS CAUSES FS ERRORS This bug is fixed in kernel version: 3.8.13-18. This kernel will be available quite soon for download.
You may upgrade the kernel once its available. ~Siju
Update
Dear Matt, Latest available UEK3 kernel version 'kernel-uek-3.8.13-26.el6uek.x86_64' incorporates the required bugfix. [root@server1 tmp]# rpm -q --changelog -p kernel-uek-3.8.13-26.el6uek.x86_64.rpm | grep -i 17487738
warning: kernel-uek-3.8.13-26.el6uek.x86_64.rpm: Header V3 RSA/SHA256 signature: NOKEY, key ID ec551f03
- fs: protect write with sb_start/end_write in generic_file_write_iter (Guangyu Sun) [Orabug: 17487738] <<<<<<======================================== You can download the UEK3 kernel from ULN or from public-yum repo.
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-firmware-3.8.13-26.el6uek.noarch.rpm
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-3.8.13-26.el6uek.x86_64.rpm Hope this helps! ~Siju
Subscribe to the Oracle Linux el-errata mailing list .
The latest kernel-uek-3.8.13-26.el6uek.x86_64 version fixed the problem.
- Matt

Affect of Kernel Patch on 4.6B

Hi Experts,
We are on 4.6B and latest kernel patches 2364 were applied on our system.
We see some screen changes in XD02/ME23N.
In Purchase order for third party items we do not see reference sales order no in Account assignmnet tab in ME23N. In XD02, there are some weird spacing between the blocks in the address screen.
Kindly help.
Thank You

I doubt if the forum can help you on this - try OSS.
Rob

Unicode Kernel Patch Update

Hi,
I want to Update the Unicode kernel patch of my ECC 6.0 system.
Since ,there is no run folder in a Unicode system,how do we go about it.
Since downtime on a Production system is a huge constraint,I dont want to mess up things.
Please help.
Thanks,
saba.

Hi,
Check this links
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/go/km/docs/library/webas/s-u/sp8%20downloading%20the%20patches/index.htm">Click here</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/go/km/docs/library/webas/s-u/sp8%20kernel%20copy/index.htm">Click here</a>
Kind Regards
Umesh K

Kernel Patch questions

Sorry but it has been a while. After reading all the kernel threads, I still have a few kernel patch questions.
1) Sequencing - Does it matter what sequence I apply all the patches? Alphabetic order? Date sequence? Always finish with DW?
2) Versioning info - some commands have a -v parameter to tell what version you currently have. Some don't. Is there some way to find out versioning info for all potential patches?
3) Marketplace - I see there is a "complete" kernel on the marketplace now (albeit in two parts). However it's never current. It looks like the hot setup to download that and patch that and then slip that in. Does everyone agree with that assessment?
4) Yes, I know the truly hot setup would be to contract with Volker to get s fully patched CD but since we were stuck on 4.0B for so long, I haven't had a chance to keep my skills up to date. This looks like a good opportunity.
Thanks,
Rick

Hi my friend
I assume you're referring to how to load new 700 kernel since you didn't mention. Here's the steps listed below, for details you could find in Note 912575 - iSeries: Using LODSAPKRN to load a 7.00 kernel
1. Download the latest SAPEXE.SAR, SAPEXEDB.SAR and IGSEXE.SAR from SWDC.
2. Create a directory in IFS and put 3 SAR files there, create a stream file called "parts" with content below:
SAPEXE.SAR,
SAPEXEDB.SAR,
IGSEXE.SAR,
P.S: I opt this way to patch IGS myself because it's more convenient, the formal IGS patching is introduced in
Note 937000 - iSeries: Installing and patching the IGS
3. Log on as QSECOFR or equivalent user (in 912575 it says SIDADM, which could lead to lack of authorization sometimes), and run command:
LODSAPKRN DEV(STMF) MNTPNT('<dir>') KRNLIB(<kernel library>) USERDEF(YES) LIST('<dir>/parts')
4. Stop SAP system and then remove old kernel:
RMVSAP SID(<SID>) DLTKRNLIB(*NO)
5. Change the library list (EDTLIBL) and replace the old kernel library with the new 7.00 kernel library.
6. Activate the new 7.00 kernel:
APYSAP TYPE(*KERNEL) SID(<SID>) DSTLIB(<new kernel library>)
7. Delete all SQL packages: DLTR3PKG SID(<SID>)
then start SAP system
Regards,

Latest kernel patch

What is the latest kernel patch for 720_ext_rel for a SAP system on ERP 6.0 EHP3(SPS2) on a SAP NETWEAVER 7.0

Hi, Isaias is right, 720 is not supported, 721 is the official replacement of 720 kernel.
1716826 - Usage of the downward compatible kernel 721 (EXT)
Where can the 721 kernel be used?
There are two use cases for the 721 (EXT) downward compatible kernel:
For all systems with NetWeaver Releases 7.00, 7.01 (7.0 Enhancement Package 1), 7.10 and 7.11 (7.1 Enhancement Package 1) that still run with a kernel 700, 701, 710 or 711 which was delivered originally. These kernel versions are out of maintenance maintenance since August 31st, 2012. You may install the kernel 721 (EXT) on these systems as an alternative to the 720 (EXT) downward compatible kernel.
For all systems running the kernel 720 (EXT) which are:
Systems originally delivered with the 720 (EXT) kernel such as:
SAP EhP2 for SAP NetWeaver 7.0 ("7.02"
SAP EhP3 for SAP NetWeaver 7.0 ("7.03"
SAP NetWeaver 7.2 ("7.20"
SAP NetWeaver 7.3 ("7.30"
SAP EhP1 forNetWeaver 7.3 ("7.31"
Systems where the original kernel 700/701/710/711 was already upgraded to the 720 (EXT) version. In these systems you can upgrade the kernel from 720 (EXT) to 721 (EXT) version.
What are the benefits of the kernel 721 (EXT)?
The SAP kernel 721 (EXT) offers several enhancements as compared to the SAP kernel 720. These enhancements may be used in different application scenarios. Please refer to the note 1728283 for more details. The SAP kernel 720 will be replaced by kernel 721 as the standard kernel for NW 7.00-7.31 based SAP systems by end of Q1 2015. A new innovation kernel will be introduced at that time.

Install Kernel Patch and Support Package

Hi Gurus.
How can I update the kernel patch and support package in solution manager?
What patchs i have to download In the service.sap.com ?
best Regards
luis

Hi Luis,
Yopu must already have checked this info at Inst Guides..
else...The Post installation steps in the installation guide contain the procedure for application of latest support packs procedure.
https://websmp204.sap-ag.de/instguides
The following SAP notes can also be referred : 212876
Information of how to download a kernel can be obtained from 19466.
Details of Patches and their release schedules can be obtained as always at
https://websmp104.sap-ag.de/ocs-schedules
Hopefully it Helps in your quest.
Br,
Sri

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 ...

Solaris 8 x86 system refuses to upgrade to Solaris 9

My x86 system successfully runs Solaris 8 (Feb. 2000 revision A) but refuses to upgrade to Solaris 9. When trying to boot one of the installation cds in anyone of the installation modes, the boot process proceeds till the message "booting kernel/unix, ... use is subject to license terms". Next I would expect setup messages for the network interface, but instead I get a blank screen with a cursor blinking top left, and that's the end of it.
Well, to be true, it's not really a problem of Solaris 9. The same thing happened when I tried to install a patch set on Solaris 8.
What ways of diagnosis do I have?
Is anything in Solaris 8 not upward compatible?
Thanks in advance for every hint!
Bernd.

OK after the DCA scans, it goes to a screen labeled "Boot Solaris" which indicates the boot drive. On that screen f4 is labeled Boot Tasks. Press f4 and go thru the settings to select the boot device and any of the other settings you might want to change. then f3 back to the boot screen and f2 continue. When the boot options screen appears, type in b -r. The DCA should not start up each time after that. To be honest, I had to do this a couple of times before something unknown to me made it finally work. Go figure!
Lee

Patch 127128-11 broken

On Solaris 10 U5, after patch 127128-11 there are now error/warning messages that did not
occur before the patch installation. The load continues, however.
WARNING: /pci@0,0/pci-ide... (ata1):
     timeout: reset bus, target=0 lun=0
WARNING: /pci@0,0/pci-ide..../cmdk@0,0 (Disk1)
     Error for command 'read sector
     Error Level: Informational
     Sense Key: aborted command
     Vendor 'Gen-ATA' error code: 0x3
The above error messages repeat for one screen and the booting continues successfully. No
damage done but it is annoying, especially when showing off Solaris to newcomers. I have not been
able to figure out how to file a bug report, short of going to the phone. Perhaps someone at Sun
could pass this along to the appropriate party.

Every Solaris patch comes with a Readme file. It is always a good idea to read the Readme file before installing the patch. This particular patch is a kernel patch. All Solaris kernel patches require that system is in single-user mode before install or you will wind up with a system that behaves unpredictably or may not boot at all. Every Solaris user should be familiar with this site: [Sunsolve Patch Access|http://sunsolve.sun.com/show.do?target=patches/patch-access]

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

Similar Messages

Maybe you are looking for