Jump to content
 English      
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
        More options        
HP.com Home
patch database

patch details: PHKL_27092

» 

IT Resource Center

» Login
» Register
» My profile
» Search knowledge base
» Forums
» Patch database
» Download drivers, software and firmware
» Warranty check
» Support Case Manager
» Software Update Manager
» Training and Education
» More maintenance and support options
» Online help
» Site map
Content starts here
» view selected patch list
The recommended patch is :  PHKL_35879
The most recent patch is :  PHKL_35879

   useful links
» Patch Family Tree

You may provide feedback on this document.
» patch name » patch description » creation date » post date » hardware platforms - os releases » products » filesets » automatic reboot? » status » critical » category tags » path name » symptoms » defect description » sr » patch files » what(1) output » cksum(1) output » patch conflicts » patch dependencies » hardware dependencies » other dependencies » supersedes » equivalent patches » patch package size » installation instructions » special installation instructions


Patch Name: PHKL_27092

Patch Description: s700_800 11.11 Thread NOSTOP, Abort; Psets

Creation Date: 02/06/04

Post Date: 02/06/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: 
	Yes
	PHKL_27092: ABORT PANIC MEMORY_LEAK
	PHKL_25728: HANG
	PHKL_24254: OTHER
		Hung, Unkillable Process

Category Tags: 
	defect_repair enhancement general_release critical panic
	halts_system memory_leak manual_dependencies

Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27092

Symptoms: 
	PHKL_27092:
	( SR:8606241506 CR:JAGae08764 )
	Increasing kernel memory consumption with heavy debugger
	use leaves less memory available for the application. This
	may result in increased paging.

	( SR:8606233458 CR:JAGae02681 )
	The system panics due to a data page fault in the signal
	routines for multi-threaded processes. This panic is quite
	rare, occuring only under extreme loading conditions, such
	as those existing during HP internal kernel stress
	testing. To date, this problem has not been reported by any
	customer. The stack trace of the faulting thread will be
	similar to the following:

	        crash event was a panic
	        panic+0x14
	        report_trap_or_int_and_panic+0x80
	        trap+0xdb8
	        nokgdb+0x8
	        pm_signalx+0x25c
	        pm_psignalx+0x54
	        psignalx+0x74
	        kill1+0x228
	        kill+0x58
	        syscall+0x8f0

	( SR:8606248132 CR:JAGae14532 )
	The 64bit Java Virtual Machine (JVM) aborts due to
	"unexpected signal" or "illegal instruction" or
	"segmentation violation" or due to other non-deterministic
	error.

	PHKL_25840:
	( SR:8606229034 CR:JAGad98088 )
	Enhancement to provide support for the interruption of a
	specic thread blocked interruptibly in a system call.

	PHKL_25728:
	( SR:8606216254 CR:JAGad85424 )
	High comsumption of CPU resources can result in an apparent
	system hang.  This occurs with applications that use a large
	number of threads per process.

	PHKL_24568:
	( 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.

	PHKL_24254:
	( 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 mutiple threads in different processes competing for
	the same resource when one thread is stopped.

	PHKL_24844:
	( SR:8606200984 CR:JAGad70160 )
	An MP system may show as being 100% busy with a load that
	should have only kept it 60-70% busy.

	These symptoms were observed on N class and V class systems
	running a load consisting of many short transactions with
	many threads.  The observed behavior is not limited,
	however, to these type of systems alone and can occur on MP
	systems with a similar type of load.

	PHKL_24574:
	( 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_27092:
	( SR:8606241506 CR:JAGae08764 )
	For each thread of a process which had ever been under
	debugger control, a small data structure is not properly
	returned to the free kernel memory pool.  This results in
	increasing memory consumption on systems where the
	debugger is used on many different threads.  The problem
	is caused by a minor coding error which prematurely sets
	the structure pointer to null during thread exit.

	Resolution:
	Removed the extra line of code which prematurely sets the
	pointer to null. This allows the structure to be freed
	correctly.

	( SR:8606233458 CR:JAGae02681 )
	Debug threads were incorrectly left on the signalable
	threads list for a process.  This defect was found at HP
	during product improvement testing.  To our knowledge, no
	customer system has experienced this defect.

	Resolution:
	Ensure the debug thread is not on the signalable threads
	list at the time of its creation.

	( SR:8606248132 CR:JAGae14532 )
	A kernel interface used to initialize register values
	takes either a direct or indirect pointer address
	parameter. For 64-bit programs, the address is always
	interpreted as an indirect pointer address, which is
	incorrect for the 64-bit Java Virtual Machine (JVM).
	This defect only occurs on 64-bit systems.

	Resolution:
	Extended the interface so that the 64-bit JVM can specify
	whether the pointer address parameter is to be interpreted
	as direct or indirect.

	PHKL_25840:
	( SR:8606229034 CR:JAGad98088 )
	The Operating System currently has no way to abort a
	specific thread blocked interruptibly in a system call.

	Resolution:
	A new kernel internal interface (function) is introduced to
	provide kernel subsystems the ability to abort a thread that
	is currently blocked interruptibly in a system call.

	PHKL_25728:
	( SR:8606216254 CR:JAGad85424 )
	All non-running threads are searched to see if they can
	handle a process directed signal.  However, if the signal is
	blocked by all the threads of a process, the signal cannot
	be delivered to a thread and must be left pending at the
	process level.
	This causes repeated attempts to deliver the signal since
	it is possible that a thread will eventually accept the
	signal.  The POSIX standards require the signal to be
	delivered.

	Resolution:
	The solution is to reduce the number of times the entire
	list of threads is searched by keeping a hint that a
	previous search has found all threads having that signal
	masked, and not repeating the search.  This avoids
	unnecessary and time sonsuming searches for a thread to
	handle a signal when a candidate is not available.

	PHKL_24568:
	( SR:8606200799 CR:JAGad69975 )
	This patch contains minor enhancements required to support
	the HP-UX Processor Sets product.

	Resolution:
	Enhancements added to handle pset inheritance and to manage
	threads/processes within their processor set domain when
	Processor Sets product is enabled.

	PHKL_24254:
	( 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_24844:
	( SR:8606200984 CR:JAGad70160 )
	The problem happens because threads are moved too often from
	one processor to another.  When this happens, all the cache
	state of the thread must be moved to the new processor also.
	All this cache movement is the source of the extra cpu time
	being used.  That is, when a thread moves to a new cpu, the
	new cpu takes a lot more cache misses than it would if the
	thread were not moved.

	The main mechanism moving threads in this case is the "idle
	stealing" algorithm; when a cpu is idle, it looks around at
	the other cpus and takes threads that are waiting to run on
	another cpu.  This mechanism can be the source of thread
	cache thrashing.

	Resolution:
	The idle stealing mechanism cannot be removed as it is
	needed for balancing the load on the system.  However, the
	delay between when a processor goes idle and when it starts
	looking at other cpus run queues was increased.  This
	decreased thread cache thrashing significantly at some cost
	to thread start latency; additionally some loads will
	slightly degrade their maximum throughput.

	PHKL_24574:
	( SR:8606200799 CR:JAGad69975 )
	This patch contains minor enhancements required to support
	the HP-UX Processor Sets product.

	Resolution:
	Enhacements added in fair share scheduler to work within
	processor set domain when Processor Sets product is enabled.

SR: 
	8606103740 8606159451 8606200799 8606200984 8606216254
	8606229034 8606233458 8606241506 8606248132

Patch Files: 
	
	OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
	/usr/conf/lib/libpm.a(pm_init.o)
	/usr/conf/lib/libpm.a(pm_proc.o)
	/usr/conf/lib/libpm.a(pm_threads.o)
	/usr/conf/lib/libpm.a(subr_threads.o)
	/usr/conf/lib/libprm.a(kern_fss.o)

	OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
	/usr/conf/lib/libpm.a(pm_init.o)
	/usr/conf/lib/libpm.a(pm_proc.o)
	/usr/conf/lib/libpm.a(pm_threads.o)
	/usr/conf/lib/libpm.a(subr_threads.o)
	/usr/conf/lib/libprm.a(kern_fss.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(pm_init.o):
		pm_init.c $Date: 2001/11/28 17:03:18 $Revision: r11.
			11/4 PATCH_11.11 (PHKL_25728)
	/usr/conf/lib/libpm.a(pm_proc.o):
		pm_proc.c $Date: 2002/05/16 11:06:48 $Revision: r11.
			11/7 PATCH_11.11 (PHKL_27092)
	/usr/conf/lib/libpm.a(pm_threads.o):
		pm_threads.c $Date: 2002/05/16 11:07:02 $Revision: r
			11.11/5 PATCH_11.11 (PHKL_27092)
	/usr/conf/lib/libpm.a(subr_threads.o):
		subr_threads.c $Date: 2001/07/05 22:08:29 $Revision:
			 r11.11/2 PATCH_11.11 (PHKL_24568)
	/usr/conf/lib/libprm.a(kern_fss.o):
		kern_fss.c $Date: 2001/07/05 22:51:01 $Revision: r11
			.11/1 PATCH_11.11 (PHKL_24574)

	OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
	/usr/conf/lib/libpm.a(pm_init.o):
		pm_init.c $Date: 2001/11/28 17:03:18 $Revision: r11.
			11/4 PATCH_11.11 (PHKL_25728)
	/usr/conf/lib/libpm.a(pm_proc.o):
		pm_proc.c $Date: 2002/05/16 11:06:48 $Revision: r11.
			11/7 PATCH_11.11 (PHKL_27092)
	/usr/conf/lib/libpm.a(pm_threads.o):
		pm_threads.c $Date: 2002/05/16 11:07:02 $Revision: r
			11.11/5 PATCH_11.11 (PHKL_27092)
	/usr/conf/lib/libpm.a(subr_threads.o):
		subr_threads.c $Date: 2001/07/05 22:08:29 $Revision:
			 r11.11/2 PATCH_11.11 (PHKL_24568)
	/usr/conf/lib/libprm.a(kern_fss.o):
		kern_fss.c $Date: 2001/07/05 22:51:01 $Revision: r11
			.11/1 PATCH_11.11 (PHKL_24574)

cksum(1) Output: 
	
	OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
	1127628367 5496 /usr/conf/lib/libpm.a(pm_init.o)
	1023541154 24524 /usr/conf/lib/libpm.a(pm_proc.o)
	3505038683 24168 /usr/conf/lib/libpm.a(pm_threads.o)
	675181813 21212 /usr/conf/lib/libpm.a(subr_threads.o)
	812943801 21312 /usr/conf/lib/libprm.a(kern_fss.o)

	OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
	3889763419 16768 /usr/conf/lib/libpm.a(pm_init.o)
	249587232 64208 /usr/conf/lib/libpm.a(pm_proc.o)
	1842780222 62680 /usr/conf/lib/libpm.a(pm_threads.o)
	1568250774 52504 /usr/conf/lib/libpm.a(subr_threads.o)
	1004836206 48848 /usr/conf/lib/libprm.a(kern_fss.o)

Patch Conflicts: None

Patch Dependencies: 
	s700: 11.11: PHKL_25729
	s800: 11.11: PHKL_25729

Hardware Dependencies: None

Other Dependencies: 
	PHKL_25840:  For enablement of this feature, PHKL_25842 also
	needs to be installed in the system.  Installation of either
	patch by itself has no effect on the system.

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

Supersedes: 
	PHKL_25840 PHKL_25728 PHKL_24844 PHKL_24574 PHKL_24568 PHKL_24254

Equivalent Patches: None

Patch Package Size: 380 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_27092

	5. Run swinstall to install the patch:

		swinstall -x autoreboot=true -x patch_match_target=true \
			  -s /tmp/PHKL_27092.depot

	By default swinstall will archive the original software in 
	/var/adm/sw/save/PHKL_27092.  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_27092.text file is 
	available in the product readme:

		swlist -l product -a readme -d @ /tmp/PHKL_27092.depot

	To put this patch on a magnetic tape and install from the
	tape drive, use the command:

		dd if=/tmp/PHKL_27092.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions: None




» top of page
Printable version
Privacy statement Using this site means you accept its terms
© 2009 Hewlett-Packard Development Company, L.P.