 |
» |
|
|
|
|
|
|
|
|
|
Patch Name: PHKL_33336
Patch Description: s700_800 11.11 Core PM, vPar, Psets, slpq1, FSS, rtprio
Creation Date: 05/07/19
Post Date: 05/09/13
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Superseded
Critical:
No (superseded patches were critical)
PHKL_31993: HANG
PHKL_29706: PANIC
PHKL_27091: PANIC HANG
PHKL_24257: OTHER
Hung, Unkillable Process
Category Tags:
defect_repair enhancement general_release critical panic
halts_system manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_33336
Symptoms:
PHKL_33336:
( SR:8606359621 CR:JAGaf20317 )
The commands top(1) and uptime(1) may show high load
averages on a 100% idle UP system.
PHKL_33328:
( SR:8606394370 CR:JAGaf54393 )
Applications that are running with POSIX real-time
scheduling policy and have a high rate of context switching
may experience performance degradation when many such
application threads are concurrently executing.
PHKL_31993:
( SR:8606323066 CR:JAGae85531 )
A system hang due to starvation of RTPRIO processes.
PHKL_30036:
( SR:8606314571 CR:JAGae77335 )
Certain workloads cannot achieve their entitlements
with the Fair Share Scheduler (FSS) when capping is enabled.
This results in a performance degradation for some
workloads.
PHKL_29708:
( SR:8606247911 CR:JAGae14311 )
A Process Resource Manager (PRM) and Fair Share Scheduler
(FSS) group with a large entitlement and just enough jobs
to get that share could be outperformed by a smaller
entitlement group with more jobs.
( SR:8606274083 CR:JAGae38161 )
When running the IO based jobs with the Fair Share
Scheduler (FSS) enabled via Process Resource Manager (PRM)
or Workload Manager (WLM), the observation of performance
degradation is 10-20%.
PHKL_30587:
( SR:8606341661 CR:JAGaf02569 )
This product update is a member of a set needed to enable
the optional HP-UX Detect and Strobe feature. Upon
installation, the HP-UX Detect and Strobe bundle
(InterruptStrobe) will install the full set of product
updates (including this one) to enable the Detect and Strobe
feature.
If the HP-UX Detect and Strobe product is not installed,
this product update will have no impact on your system.
PHKL_30033:
( SR:8606314571 CR:JAGae77335 )
Certain workloads cannot achieve their entitlements
with the Fair Share Scheduler (FSS) when capping is enabled.
This results in a performance degradation for some
workloads.
PHKL_29706:
( SR:8606236276 CR:JAGae05337 )
System panics with "data page fault". There are two stack
traces that represent the same failure:
panic string : Data page fault
panic+0x6c
report_trap_or_int_and_panic+0x94
trap+0xed4
thandler+0xd20
-------- TRAP -----------
find_thread_other_spu+0x60
idle_nonpset_loop+0x4e4
idle+0x4e0
swidle+0x28
panic: Zombie thread walks !
stack trace for event 0
crash event was a panic
panic+0x6c
thread_exit+0x200
thread_process_suspend+0x1ec
issig+0x2a4
syscall+0x9e4
$syscallrtn+0x0
( SR:8606236816 CR:JAGae05866 )
The Processor Sets based systems show performance
degradation when relatively idle. This problem is
observed only when the optional Process Sets (PROCSETS)
product is installed.
( SR:8606274083 CR:JAGae38161 )
When running the IO based jobs with the Fair Share
Scheduler (FSS) enabled via Process Resource Manager (PRM)
or Workload Manager (WLM), the observation of performance
degradation is 10-20%.
( SR:8606316028 CR:JAGae78747 )
When Process Resource Manager (PRM) is enabled, certain
workloads -- especially memory intensive workloads -- may
show significant performance degradation on relatively
idle systems.
PHKL_27091:
( SR: 8606236276 CR:JAGae05337 )
Panics due to run queue corruption may occur on systems
with patches PHKL_24551 or PHKL_25389. The panics occur
on systems in which at least one processor is idle, and
symptoms may take the form of a data page fault panic
in find_thread_other_spu() or gs_rendezvous_thread(),
or a spinlock deadlock panic on the 'Per SPU RUNQ Lock'.
( SR:8606249635 CR:JAGae16022 )
Applications may hang with threads in the accept(2) system
call. The problem occurs only when multiple threads are
issuing accept(2) on the same socket, and when no thread
calls accept(2) again after a thread is interrupted by a
signal.
( SR:8606259436 CR:JAGae23754 )
System may panic with data page fault in clock interrupt
path. The stack trace is as follows:
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
determine_processor_state+0xbc
per_spu_hardclock+0xc8
clock_int+0x58
mp_ext_interrupt+0x150
ivti_patch_to_nop3+0x0
idle+0x108
swidle_exit+0x0
( SR:8606234249 CR:JAGae03469 )
Enhancement: This product update is a member of a set
needed to support the kernel sleep/wakeup queuing
performance enhancement. The full list of product updates
required for this feature are: PHKL_27091, PHKL_27294,
PHKL_27093 and PHKL_27094.
Performance degradation may be seen on systems in
which a large number (500 or more) of TIMESHARE threads
call the accept(2) function on a single socket.
( SR:8606245859 CR:JAGae12318 )
Processes which call vfork(2) can sometimes hang and
become unkillable. Further, executing a setpriority(2)
operation (e.g. via renice(1M)) on such a process may
cause a kernel panic due to a Data Page Fault, with the
stack trace:
is_realtime+0x0
get_pregionnice+0x34
update_preg_nice+0x44
donice+0xc8
setpriority+0x6c
syscall+0x750
syscallinit+0x5b0
PHKL_25389:
( SR:8606215976 CR:JAGad85148 )
When thousands of threads are waiting on a select(2) call,
application performance slows down considerably. This is
an enhancement to sleep queues to boost performance.
( SR:8606226427 CR:JAGad95496 )
Possible races from kernel subsystems that assume the
entry to kernel sleep is atomic. This can result in
missed wakeup events.
PHKL_24551:
( SR:8606200799 CR:JAGad69975 )
This patch is a member of a set of patches needed to enable
the HP-UX Processor Sets product (PROCSETS). When PROCSETS
product is installed, it will install the full set of
required patches for that product, including this patch.
If the HP-UX Processor Sets product is not installed, this
change will have no Processor Sets impact on your system.
( SR:8606199577 CR:JAGad68764 )
This patch is a member of a set of patches needed to enable
the HP-UX Virtual Partitions product Sets. When the HP-UX
Virtual Partitions product (VPARSBASE or T1335AA) is
installed, it will install the full set of required patches
for that product, including this patch.
If the HP-UX Virtual Partitions product is not installed,
this change will have no Virtual Partitions impact on your
system.
( SR:8606194817 CR:JAGad64023 )
Load averages reported by such utilities as top and uptime
are overall higher in 11.11 than they were in earlier
releases.
PHKL_23665:
( SR:8606128017 CR:JAGac78818 )
vhand priority does not match scheduling policy for brief
durations.
PHKL_24257:
( SR:8606159451 CR:JAGad28779 ) Duplicate
( SR:8606103740 CR:JAGab70789 )
A multi-threaded process being executed over NFS can become
hung and unkillable while performing either a fork, core,
setrlimit, SIGSTOP, or debugger operations. This can happen
with multiple threads in different processes competing for
the same resource when one thread is stopped.
PHKL_32094:
( SR:8606379188 CR:JAGaf39437 )
Customer applications using the SCHED_NOAGE scheduling
policy on the 11.11 release may experience performance
degradation in presence of high-priority SCHED_TIMESHARE
processes.
PHKL_30035:
( SR:8606314571 CR:JAGae77335 )
Certain workloads cannot achieve their entitlements
with the Fair Share Scheduler (FSS) when capping is enabled.
This results in a performance degradation for some
workloads.
PHKL_29705:
( SR:8606274083 CR:JAGae38161 )
When running the IO based jobs with the Fair Share
Scheduler (FSS) enabled via Process Resource Manager (PRM)
or Workload Manager (WLM), the observation of performance
degradation is 10-20%.
PHKL_27531:
( SR:8606277297 CR:JAGae41368 )
The design for callbacks on clock interrupts only allows for
a single client to register a callback at a time.
Registering multiple callbacks simultaneously will cause the
callbacks to interfere with each other.
PHKL_26232:
( SR:8606235626 CR:JAGae04770 )
When running Process Resource Manager(PRM) on Instant
Capacity On Demand (iCOD) enabled system, PRM groups may
exceed their CPU entitlement when the PRM capping feature
is on.
PHKL_24573:
( SR:8606200799 CR:JAGad69975 )
This patch is a member of a set of patches needed to enable
the HP-UX Processor Sets product (PROCSETS). When PROCSETS
product is installed, it will install the full set of
required patches for that product, including this patch.
If the HP-UX Processor Sets product is not installed, this
change will have no impact on your system.
Defect Description:
PHKL_33336:
( SR:8606359621 CR:JAGaf20317 )
The system and per-processor load average computations use
the absolute load on run queues at the time of computation.
This makes the computed load averages susceptible to daemon
threads becoming "ready to run" at regular intervals that
coincide with computation times. The kernel daemon threads
are also not included in load calculations.
Resolution:
Maintain and use the smoothed run queues' load to compute
the system and per-processor load averages. The kernel
daemon threads are also included in the load calculations.
PHKL_33328:
( SR:8606394370 CR:JAGaf54393 )
When many POSIX real-time threads are executing with high
rate of context switching, they cause most processors in
the system to contend for these threads even though not
all processors will eventually get one of these threads
to execute. This contention causes scheduling delays for
the workload in the system.
Resolution:
Optimize how many processors contend for the POSIX
real-time run queue based on how many POSIX real-time
threads are waiting to execute.
PHKL_31993:
( SR:8606323066 CR:JAGae85531 )
The load balancer starvation detection algorithm excludes
RTPRIO threads from consideration. This may cause weaker
priority RTPRIO threads to starve in presence of higher
priority real-time threads.
Resolution:
Extend the load balancer to include RTPRIO threads in its
starvation detection algorithm.
PHKL_30036:
( SR:8606314571 CR:JAGae77335 )
Existing algorithms of the fair-share scheduler (FSS)
make some decisions which are inappropriate for some
workloads when the capping feature of FSS is enabled.
This causes processors to remain idle even when some
FSS groups have not attained their entitlements.
Resolution:
The FSS balancer and thread selection algorithms
have been modified where capping is enabled so that
the processors do not inappropriately idle. This
improves the ability of FSS groups to attain their
entitlements.
Removes the FSS load balancer with the updated
FSS balancer in PHKL_30032.
PHKL_29708:
( SR:8606247911 CR:JAGae14311 )
Due to the way HP-UX round-robin jobs separately among the
processors for each CPU, all groups start on the same CPU.
That means on a 4 processor box, if a system has four
groups each with 24% and one job, they all ended up
sharing the same CPU. A fifth group with only 4% but lots
of jobs would end up spread over all the CPUs, and take
about 76% of the over all system cycles.
Resolution:
When distributing jobs on round-robin policy, the start
position is different for each group, biggest first.
( SR:8606274083 CR:JAGae38161 )
On a large PRM group count systems, HP-UX walks the run
queue once per group. Also, per-group tick accounting is
not very precise.
Resolution:
When a group has fewer jobs than there are cpus, and it is
grossly underachieving, systems allow the temporary
dedication of sufficient cpus to that group to make
reaching the entitlement possible.
PHKL_30587:
( SR:8606341661 CR:JAGaf02569 )
This product update contains minor enhancements required to
enable the HP-UX Detect and Strobe feature.
Resolution:
Enable idle() path to interact with the Detect and Strobe
feature when enabled.
PHKL_30033:
( SR:8606314571 CR:JAGae77335 )
Existing algorithms of the fair-share scheduler (FSS)
make some decisions which are inappropriate for some
workloads when the capping feature of FSS is enabled.
This causes processors to remain idle even when some
FSS groups have not attained their entitlements.
Resolution:
The FSS balancer and thread selection algorithms
have been modified where capping is enabled so that
the processors do not inappropriately idle. This
improves the ability of FSS groups to attain their
entitlements.
The run queue management support has been updated
to support the improved FSS capping mechanism.
PHKL_29706:
( SR:8606236276 CR:JAGae05337 )
The first symptom is caused by looping forever on a
thread's run queue links, which points back the thread
itself. The second is caused by dereferencing a thread's
null run queue links. Both are separate stages of the
same problem.
In idle() path, two of the synchronized flags in sequence
are reversed in store order by the compiler optimization
which causes an inconsistent thread state that leads to
run queue corruption.
PHKL_24551 and PHKL_25389 were impacted by the flipped
store order. However, PHKL_27091 which supersedes the
above two patches has the correct order even without the
code fix.
Resolution:
Explicitly set the two flags to be volatile in idle code
path to ignore compiler optimization.
( SR:8606236816 CR:JAGae05866 )
The Processor Sets functionality is consuming huge amounts
of CPU cycles in the "idle" loop due to one heavy lock
contention and cache misses.
Resolution:
Changes to reduce lock contention in a Processor Sets
kernel.
( SR:8606274083 CR:JAGae38161 )
On a large PRM group count systems, HP-UX walks the run
queue once per group. Also, per-group tick accounting is
not very precise.
Resolution:
Remember what groups a system has on the first pass
through the run queue and only walk it a second time if
the system is guaranteed of a success.
( SR:8606316028 CR:JAGae78747 )
When PRM is enabled, an extreme case of cache thrashing is
observed due to the unnecessary constant update of a
global volatile variable in the idle() path. This
scenario causes heavy traffic on the system bus, greatly
impacting overall system performance on relatively idle
systems.
The idle() path is seen in two different places, one is
based kernel, and the other one is Processor Sets kernel.
These two paths are independent to each other.
Resolution:
Remove the update of the global volatile variable in the
based kernel idle() path when PRM is enabled.
PHKL_27091:
( SR: 8606236276 CR:JAGae05337 )
Patches PHKL_24551 and PHKL_25389 introduced a race
condition in the interaction between the idle and suspend
paths, leading to a thread being in an inconsistent state
while either actively running or on the run queue.
Resolution:
In PHKL_27091 the race condition no longer exists.
( SR:8606249635 CR:JAGae16022 )
A thread receiving an event wakeup and a signal
simultaneously will handle the signal. The event will not
be handled even though there may be other threads
waiting for that event. They will wait forever, unless
another duplicate event occurs.
Resolution:
A signaled thread will now determine if it also received
an event wakeup. If so, it will wake up the next waiting
thread to handle the event.
( SR:8606259436 CR:JAGae23754 )
A clock interrupt occurring as soon as the idle loop
enables interrupts may attempt to dereference a null
thread pointer if the cpu state is stale, causing the
panic.
Resolution:
Set the processor state information earlier in the idle
loop, before interrupts are enabled.
( SR:8606234249 CR:JAGae03469 )
This product update contains a performance enhancement to
the kernel sleep/wakeup queuing mechanism.
Resolution:
Implement a new sleep/wakeup queuing mechanism that
addresses the performance issue.
( SR:8606245859 CR:JAGae12318 )
A race condition in vfork(2) causes a wakeup to be missed.
As the parent is left in an incoherent state, a subsequent
priority setting operation encounters a stale pointer,
causing the Data Page Fault.
Resolution:
Fixed operation sequence to close the race, so that the
wakeup is not missed.
PHKL_25389:
( SR:8606215976 CR:JAGad85148 )
This is an enhancement for a performance problem seen while
trying to remove a single thread from a long sleep queue.
This would be useful to customers who are making numerous
system calls that would cause threads to sleep on the same
sleep queue, such as select(2).
Resolution:
The sleep queues were changed from a single-linked list to
a double-linked list.
( SR:8606226427 CR:JAGad95496 )
This is an enhancement that allows kernel subsystems to
enter kernel sleep with alternative locking rules. By
permitting these new locking rules, other subsystems are
able to close race windows around entering and leaving
kernel sleep. If there is no other patch that requires
this change, it will do nothing.
Resolution:
Permit kernel subsystems entering kernel sleep to hold
an additional resource to prevent race conditions .
PHKL_24551:
( SR:8606200799 CR:JAGad69975 )
This patch contains minor enhancements required to support
the HP-UX Processor Sets product.
Resolution:
Enhancements added to enable scheduler to recognize and
work with processor sets when the Processor Sets product
is enabled.
( SR:8606199577 CR:JAGad68764 )
This patch contains minor enhancements required to support
the HP-UX Virtual Partitions product.
Resolution:
Enhancements added to support CPU migration.
( SR:8606194817 CR:JAGad64023 )
System daemon threads are factored into the load average
calculations in 11.11 where they were not in earlier
releases. This makes the reported load averages higher
than they were in earlier releases.
Resolution:
This patch changes the load average calculations to once
more disregard system daemon threads, resulting in load
averages much more closely aligned to those in earlier
releases.
PHKL_23665:
( SR:8606128017 CR:JAGac78818 )
When vhand's priority is increased due to it being
preempted, there is a race with other threads which are
also raising vhand's priority at the same time. Thus,
when vhand switches back to run again, its policy and
priority number do not match. The priority and policy
will be back in sync once the thread which elevated the
priority of vhand is restored to run again.
Resolution:
Preemption_point no longer elevates the priority of the
preempted thread.
PHKL_24257:
( SR:8606159451 CR:JAGad28779 ) Duplicate
( SR:8606103740 CR:JAGab70789 )
A thread acquires a lock and then sleeps interruptibly. The
interruptible sleep permits the thread to be stopped. Any
other thread attempting to acquire this lock will sleep
uninterruptibly until the lock is available. This
uninterruptible thread is also unkillable. This introduces
a deadlock potential in multi-threaded processes: when a
thread holding the lock, a thread desiring the lock, and a
third thread doing one of fork, setrlimit, core, SIGSTOP, or
debugger operations, all occur at the same time in the
same process, the deadlock is reached. The only way to
resolve the deadlock is to reboot the system. A similar
situation can occur when threads in different processes
are competing for the same NFS resource and the thread that
owns that resource is stopped via a signal, a debugger,
or a ctrl-Z.
This patch is part of a set of five patches (PHKL_24253,
PHKL_24254,PHKL_24255,PHKL_24256,PHKL_24257) that enable
P_NOSTOP, a new feature that prevents a process from being
unkillable. Each patch is independently installable.
Without all five installed, P_NOSTOP will be unavailable.
In order to prevent the process executed over NFS from
becoming unkillable, NFS must use the P_NOSTOP feature.
Usage of this feature was added to PHNE_23502.
Resolution:
If a thread acquires a lock and then sleeps interruptibly,
it is not permitted to be stopped if P_NOSTOP is set. This
prevents this thread from becoming unkillable and prevents
the deadlock.
PHKL_32094:
( SR:8606379188 CR:JAGaf39437 )
The SCHED_NOAGE policy introduced in 11.00 allowed for
priorities in the range of 153-255. The SCHED_NOAGE policy
in HP_UX 11.11 supports priorities in the range of 178-255.
Some applications may need to use priorities below 178,
as was possible in HP-UX 11.00.
Resolution:
The SCHED_NOAGE policy in HP-UX 11.11 has been extended to
include priorities 153-255. Priorities from 153-177 are
accessible only when the new system global
sched_noage_extend is set to 1 using adb(1).
An inappropriate use of this variable can result in
application performance degradation or system hang.
If this variable is reset to zero dynamically after
setting it to one, the system behavior is undefined.
If the sched_noage_extend variable is not enabled,
this change (support for the extended SCHED_NOAGE
priority range) will have no impact on the system.
PHKL_30035:
( SR:8606314571 CR:JAGae77335 )
Existing algorithms of the fair-share scheduler (FSS)
make some decisions which are inappropriate for some
workloads when the capping feature of FSS is enabled.
This causes processors to remain idle even when some
FSS groups have not attained their entitlements.
Resolution:
Invokes the updated version of FSS per clock
interrupt function.
The FSS balancer and thread selection algorithms
have been modified where capping is enabled so that
the processors do not inappropriately idle. This
improves the ability of FSS groups to attain their
entitlements.
PHKL_29705:
( SR:8606274083 CR:JAGae38161 )
On a large PRM group count systems, HP-UX walks the run
queue once per group. Also, per-group tick accounting is
not very precise.
Resolution:
In clock interrupt path, update per-group tick accounting
to be more accurate for IO.
PHKL_27531:
( SR:8606277297 CR:JAGae41368 )
The system doesn't support simultaneous multiple callbacks.
Resolution:
This patch implements a new function which can be used to
schedule a callback per processor on each clock tick. This
new function can be called by multiple system components
thereby eliminating the potential for interference.
PHKL_26232:
( SR:8606235626 CR:JAGae04770 )
The scheduler used by PRM charges CPU usage based on shares
allocated to each processor, to appropriate PRM groups.
However, on iCOD systems, where one or more processors are
deallocated, CPU time on deallocated processors was charged
erroneously to PRM groups. This erroneous charge gave the
appearance of PRM groups achieving usage beyond entitlement,
when PRM capping feature is on.
Resolution:
CPU time on deallocated processors will not be charged to
PRM groups.
PHKL_24573:
( SR:8606200799 CR:JAGad69975 )
This patch contains minor enhancements required to support
the HP-UX Processor Sets product.
Resolution:
Enhancements added to enable the clock interrupt path to
handle processor sets impact when Processor Sets is enabled.
Enhancement:
No (superseded patches contained enhancements)
PHKL_33328:
This patch enhances the performance of the
applications which use threads with POSIX
real-time scheduling.
PHKL_30587:
Support added for HP-UX Detect and Strobe feature.
PHKL_29706:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
No (superseded patches contained enhancements)
PHKL_27531:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
8606359621 8606103740 8606128017 8606159451 8606194817
8606199577 8606200799 8606215976 8606226427 8606234249
8606236276 8606236816 8606245859 8606247911 8606249635
8606259436 8606274083 8606314571 8606316028 8606323066
8606341661 8606379188 8606394370 8606200799 8606235626
8606274083 8606277297 8606314571
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libpm.a(balance.o)
/usr/conf/lib/libpm.a(find_thread.o)
/usr/conf/lib/libpm.a(pm_clockint.o)
/usr/conf/lib/libpm.a(pm_rtsched.o)
/usr/conf/lib/libpm.a(pm_swtch.o)
/usr/conf/lib/libvm.a(vm_stats.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpm.a(balance.o)
/usr/conf/lib/libpm.a(find_thread.o)
/usr/conf/lib/libpm.a(pm_clockint.o)
/usr/conf/lib/libpm.a(pm_rtsched.o)
/usr/conf/lib/libpm.a(pm_swtch.o)
/usr/conf/lib/libvm.a(vm_stats.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libpm.a(balance.o):
balance.c $Date: 2004/09/10 12:02:15 $Revision: r11.
11/4 PATCH_11.11 (PHKL_31993)
/usr/conf/lib/libpm.a(find_thread.o):
find_thread.c $Date: 2005/06/20 02:08:21 $Revision:
r11.11/1 PATCH_11.11 (PHKL_33328)
/usr/conf/lib/libpm.a(pm_clockint.o):
pm_clockint.c $Date: 2005/07/12 10:48:27 $Revision:
r11.11/7 PATCH_11.11 (PHKL_33336)
/usr/conf/lib/libpm.a(pm_rtsched.o):
pm_rtsched.c $Date: 2005/06/20 02:08:21 $Revision: r
11.11/2 PATCH_11.11 (PHKL_33328)
/usr/conf/lib/libpm.a(pm_swtch.o):
pm_swtch.c $Date: 2005/06/20 02:08:21 $Revision: r11
.11/15 PATCH_11.11 (PHKL_33328)
/usr/conf/lib/libvm.a(vm_stats.o):
vm_stats.c $Date: 2005/07/12 10:51:02 $Revision: r11
.11/2 PATCH_11.11 (PHKL_33336)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpm.a(balance.o):
balance.c $Date: 2004/09/10 12:02:15 $Revision: r11.
11/4 PATCH_11.11 (PHKL_31993)
/usr/conf/lib/libpm.a(find_thread.o):
find_thread.c $Date: 2005/06/20 02:08:21 $Revision:
r11.11/1 PATCH_11.11 (PHKL_33328)
/usr/conf/lib/libpm.a(pm_clockint.o):
pm_clockint.c $Date: 2005/07/12 10:48:27 $Revision:
r11.11/7 PATCH_11.11 (PHKL_33336)
/usr/conf/lib/libpm.a(pm_rtsched.o):
pm_rtsched.c $Date: 2005/06/20 02:08:21 $Revision: r
11.11/2 PATCH_11.11 (PHKL_33328)
/usr/conf/lib/libpm.a(pm_swtch.o):
pm_swtch.c $Date: 2005/06/20 02:08:21 $Revision: r11
.11/15 PATCH_11.11 (PHKL_33328)
/usr/conf/lib/libvm.a(vm_stats.o):
vm_stats.c $Date: 2005/07/12 10:51:02 $Revision: r11
.11/2 PATCH_11.11 (PHKL_33336)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
124346899 7216 /usr/conf/lib/libpm.a(balance.o)
623037943 4116 /usr/conf/lib/libpm.a(find_thread.o)
2825144228 6304 /usr/conf/lib/libpm.a(pm_clockint.o)
2590433389 10996 /usr/conf/lib/libpm.a(pm_rtsched.o)
3397001749 45752 /usr/conf/lib/libpm.a(pm_swtch.o)
750154070 10088 /usr/conf/lib/libvm.a(vm_stats.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
1586893650 16088 /usr/conf/lib/libpm.a(balance.o)
1556291407 9592 /usr/conf/lib/libpm.a(find_thread.o)
1742839963 14576 /usr/conf/lib/libpm.a(pm_clockint.o)
3339921679 29760 /usr/conf/lib/libpm.a(pm_rtsched.o)
3906056679 106272 /usr/conf/lib/libpm.a(pm_swtch.o)
2717049432 24584 /usr/conf/lib/libvm.a(vm_stats.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHKL_27093 PHKL_29704 PHKL_30032 PHKL_30034
PHKL_33408
s800: 11.11: PHKL_27093 PHKL_29704 PHKL_30032 PHKL_30034
PHKL_33408
Hardware Dependencies: None
Other Dependencies:
PHKL_33336: If the PSET product is installed, the PSET
product patch PHKL_33337 must be installed with this one to
resolve this defect. If PHKL_33337 is not installed and the
PSET product installed, this change will have no impact on
your system.
PHKL_30033 and PHKL_30036: On systems with the HP-UX
Processor Sets product (PROCSETS) version A.01.00.00.06
installed, PHKL_30037 must be installed with this patch to
avoid a system panic.
PHKL_29708: To solve the PRM(FSS) entitlement problem
related to JAGae14311 in Processor Sets path, PHKL_29709
must be installed.
PHKL_29706: To solve the Processor Sets performance
degradation problem JAGae05866 and PRM performance
degradation problem JAGae78747, PHKL_29709 must be
installed.
PHKL_24257: If NFS is installed on the system, all five
patches (PHNE_23502, PHKL_24253, PHKL_24254,PHKL_24255,
PHKL_24256, PHKL_24257) are required to resolve the process
hang/deadlock due to unkillable processes executed over NFS.
However, if NFS is not in use, none of these patches are
required.
PHKL_30035: On systems with the HP-UX Processor Sets product
(PROCSETS) version A.01.00.00.06 installed, PHKL_30037 must
be installed with this patch to avoid a system panic.
Supersedes:
PHKL_33328 PHKL_32094 PHKL_31993 PHKL_30587 PHKL_30036 PHKL_30035
PHKL_30033 PHKL_29708 PHKL_29706 PHKL_29705 PHKL_27531 PHKL_27091
PHKL_26232 PHKL_25389 PHKL_24573 PHKL_24551 PHKL_24257 PHKL_23665
Equivalent Patches: None
Patch Package Size: 180 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_33336
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_33336.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_33336. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_33336.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHKL_33336.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_33336.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHKL_32094
To set the sched_noage_extend variable to one to extend
the SCHED_NOAGE priority range, use the adb(1) command.
Refer to the adb(1) man page for correct syntax.
Note: inappropriate use of this variable can result
in application performance degradation or system hang.
|
Printable version
