Problem
The kernel variable, lbolt, which counts how many clock ticks
have occurred since boot, is a signed integer whose value exceeds
the range of this data type around the 248th day. Several
instances of code have been found which mishandle this, resulting
in problems, such as these:- X windows freezing or responding slowly to user interaction.
- Console and network logins not proceeding from the "login" to the "Password" prompt.
- System shutdowns hanging while trying to stop NFS.
- Cpd process consuming most of the cpu cycles and exhibiting "streams leak" characteristics.
When lbolt wraps, sco_cpd will continuously broadcast the local
system's license to all of the other sco_cpd's on the local
network. That is why this happens on several systems at once.
It is necessary to reboot all systems with an uptime of 248 days or
more. Solution
Support Level Supplement, (SLS) OSS456B resolves these problems. OSS456B should be installed on 5.0.0 and 5.0.2 systems that have been rebooted _because_ they have experienced the above problems, as well as systems that have not yet experienced the above problems because they have not been up for 248 days. See the attached cover letter that accompanies this SLS for more information, including installation instructions.
NOTE: SLS OSS456B will only install on SCO OpenServer 5.0.0 and 5.0.2.
It will _not_ install on SCO OpenServer 5.0.4. SLS OSS456B will
be included in the first Release Supplement for 5.0.4.Dear SCO Customer,The enclosed Support Level Supplement, (SLS) OSS456B resolves the root cause of certain problems that occur when machines are allowed to remain up for over 247 days. This is known as the "lbolt" problem. Some of the symptoms of this problem are:
- X windows freezing or responding slowly to user interaction.
- Console and network logins not proceeding from the "login" to the "Password" prompt.
- System shutdowns hanging while trying to stop NFS.
- Cpd process consuming most of the cpu cycles and exhibiting "streams leak" characteristics.
The kernel variable, lbolt, which counts how many clock ticks have occurred
since boot, is a signed integer whose value exceeds the range of this data
type around the 248th day. Several instances of code have been found which
mishandle this, resulting in problems, such as the ones listed previously.SLS OSS456B consists of replacement xsys.o and sched.o modules. These are components of the etc/conf/pack.d/kernel/os.a archive.
SLS OSS456B is _only_ for use on these products:
SCO OpenServer Enterprise System Release 5.0.0, 5.0.2 SCO OpenServer Desktop System Release 5.0.0, 5.0.2 SCO OpenServer Host System Release 5.0.0, 5.0.2
INSTALLATION AND REMOVAL INSTRUCTIONSInstalling patches on SCO OpenServer 5.0.0, 5.0.2 usually consists of two
phases: "Loading" and "Applying". The instructions that follow enable you
to both install the patch from distribution media or media image, as well
as configure the patch to be installed from a remote SCO OpenServer 5.0.0,
5.0.2 system over a TCP/IP network.I. LOADING THE PATCH1. Log in as root.2. If you are installing this SLS from floppy disk media, skip this step and proceed to step 3.
If you are installing this SLS from a media image, there is a file
called oss456b.Z. Uncompress this file with this command:# uncompress oss456b.ZCopy the file to the /tmp directory and name it VOL.000.000:
# cp oss456b /tmp/VOL.000.0003. Execute the command:# scoadmin softwareor double click on the Software Manager icon on the desktop.
4. Pull down the "Software" menu and select "Patch Management-->Load Patch".
5. You will see the "Begin Load Patch" menu. Be sure the
local machine name is selected and choose "Continue".6. You will see the "Select Media" menu.
a. If you are loading this SLS from floppy disk media,
select the appropriate floppy disk drive and
choose "Continue". Proceed to step 7.b. If you are loading this SLS from a media image per step 2,
pull down the "Media Device" menu and select "Media Images",
then choose "Continue". You will then see the "Enter Image
Directory" menu. Enter /tmp and choose "OK".7. You will see the "Load Patch Preference" menu. Choose "Full".8. You will see the "Load Patch Progress" window. If the patch loads
successfully, you will see a "Message" window which states "Load
Patch complete". Choose "OK". You are then returned to the main
Software Manager window.9. To apply the patch now, continue with step 2 under section II,
"Applying the Patch". To exit the Software Manager now, select
"Exit" from the "Host" menu.II. APPLYING THE PATCH1. Log in as root. Execute the command:
# scoadmin softwareor double click on the Software Manager icon on the desktop.
2. Pull down the Software menu and select "Patch Management-->Apply Patch".
3. You will see the "Begin Apply Patch" menu. Be sure that the local
machine name is selected and choose "Continue".4. You will see the "Select Media" menu. The "Hard Disk" menu item
should already be selected. Choose "Continue".5. You will be presented with the "Select Patch-product to Apply" menu. Highlight the "lbolt fixes" patch and then choose "Full" to continue.
6. You will see the "Apply Patch Progress" window as the system applies the patch.
7. You will see this message:NOTE: Application or rollback of this patch requires a kernel relink. If you are applying or rolling back several patches at this time, you may choose to defer the relink until the last patch application or rollback. Do you want to relink the kernel now? (y/n)
Enter "y" or "n" based on this message. Note that you will not be able to make use of the patch until you relink the kernel. Therefore, it is suggested that you answer "y" to this question.
8. If you chose "y", the kernel will be relinked. In either case, you will then see:
Press <Enter> to continueAfter pressing <Enter>, you will see the "Apply Patch Progress"
window, after which you will see a "Message" window stating "Apply
Patch Complete". Choose "OK" and you will be returned to the Software
Manager's main menu. Exit the Software Manager by choosing "Exit"
from the "Host" menu.9. Log in as root on tty01, and shut down the system:
# shutdown -g0 -yAfter shutting down and rebooting the machine, application of the patch is complete.
IV. NOTES ON NETWORK INSTALLATIONTo install the patch on other SCO OpenServer 5.0.0, 5.0.2 machines over the
network, first load the patch as in section I above on a designated
installation server. Then create the user "swadmin" on the installation
server.When running the Software Manager on the system where the patch will be
installed, you will be prompted for the source location of the patch in
the "Begin Load Patch" window. Be sure to choose "From Another Host"
during this phase. You will need to provide the name of the installation
server, as well as the password of the "swadmin" user on the installation
server, to initiate the installation process.V. PATCH REMOVALNOTE: Patches must be rolled back in the reverse order in which they
were installed on a per-component basis. Hence, if the "lbolt fixes"
patch is not the most recent patch applied to the UNIX component of the
product, you will have to rollback all patches applied after the "lbolt
fixes" patch prior to rollback of the "lbolt fixes" patch.1. Log in as root.2. Execute the command:# scoadmin softwareor double click on the Software Manager icon in the desktop.
3. Pull down the "Software" menu and select "Patch Management-->Rollback Patch".
4. You will see the "Begin Rollback Patch" menu, and be asked to select patched software to rollback. Select "SCO UNIX System V Operating System" and choose "Continue".
5. You will see the "Patch Selection" window. Make sure that the "lbolt fixes" patch is selected, and choose "Continue".
6. You will see the "Confirm Selected Patches" window. Choose "Rollback" to confirm removal of the "lbolt fixes" patch.
7. You will see the "Rollback Progress" window, as the system performs the rollback of the patch.
8. You will see this message:NOTE: Application or rollback of this patch requires a kernel relink. If you are applying or rolling back several patches at this time, you may choose to defer the relink until the last patch application or rollback. Do you want to relink the kernel now? (y/n)
Enter "y" or "n" based on this message. Note that complete rollback of this patch requires a relink of the kernel to be complete. Therefore, it is suggested that you answer "y" to this question, unless you are installing or removing other patches.
9. If you chose "y", the kernel will be relinked. In either case, you will then see:
Press <Enter> to continueAfter pressing the <Enter> key, you will see the "Rollback Progress" window, after which a "Message" window stating "Rollback Patch Complete". Choose "OK" and you will be returned to the Software Manager's main menu. Exit the Software Manager by choosing "Exit" from the "Host" menu.
10. Log in as root on tty01, and shut down the system:
sh# shutdown -g0 -yAfter shutting down and rebooting the machine, rollback of the patch is complete.
11. To also unload the patch, making it no longer available to be applied,
follow steps 1 through 10 in this section. However, in step 3, choose:"Patch Management-->Unload Patch"instead of:"Patch Management-->Rollback Patch"If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.
We appreciate your business.SCO Support Services