README VERSION		: 1.0
README Creation Date	: 2011-09-14
Patch-ID 		: 5.1.132.000 
Patch Name		: VRTSamf-5.1SP1RP2-SLES11
BASE PACKAGE NAME	: Veritas Asynchronous Monitoring Framework Module
BASE PACKAGE VERSION	: VRTSamf 5.1SP1
Obsolete Patches	: NONE
Superseded Patches	: NONE
Required Patches	: NONE
Incompatible Patches	: NONE
Supported PADV		: sles11_x86_64
(P-Platform , A-Architecture , D-Distribution , V-Version)
Patch Category		:  HANG ,  PANIC
Reboot Required		: YES


KNOWN ISSUES : 


FIXED INCIDENTS: 
----------------


 Patch Id::5.1.132.000

* Incident no::2287061	 Tracking ID ::2348721

 Symptom::The basic event registration with AMF fails. Subsequently basic
commands on the system hang.

 Description::This issue is observed only on SLES10 SP4. The AMF implementation
running on SLES10 SP3 needed some changes to work on SLES10 SP4.

 Resolution::Symantec has enhanced the AMF driver so that it now supports SLES10 SP4.

* Incident no::2301731	 Tracking ID ::2301709

  Symptom::Kernel panics when you unconfigure the AMF driver.

  Description::There was a race condition between a system call and the AMF driver
unconfiguration which caused this issue.

  Resolution::Symantec modified the code to address this race condition.

* Incident no::2403851	 Tracking ID ::2403846

  Symptom::System cannot unload the AMF driver.

  Description::An error in the code prevented the AMF module from being unloaded 
though the module was not being used.

  Resolution::Symantec has modified the code. AMF module can be unloaded when it 
is not in use.


* Incident no::2406748	 Tracking ID ::2406746

  Symptom::Offline registration for a process with AMF succeeds even when the  
process is running.

  Description::When AMF processes the offline registration request, stale data 
from earlier cycles causes an online process to be reported as offline.

  Resolution::Symantec had modified the code to remove the stale data. The 
correct status is passed on to registration requests.


* Incident no::2407653	 Tracking ID ::2407652

  Symptom::The module reference count on the filesystem registered with AMF for
mount offline monitoring or mount online monitoring is not released when you
forcefully unconfigure AMF using the "amfconfig -Uof" command.

  Description::When forcefully unconfiguring AMF, it was not releasing its
reference from the filesystem modules. This caused extra reference counts on
these modules to remain even after AMF driver was unloaded.

  Resolution::Symantec modified the code for proper reference counting on these
filesystem modules during forceful unconfiguration of AMF.


* Incident no::2439310	 Tracking ID ::2483712

  Symptom::Kernel panics when you mount a file system that is registered for mount
offline monitoring.

  Description::The driver was sleeping on a semaphore in an atomic context and
thus panicked by giving the error message "BUG: Scheduling while atomic".

  Resolution::Symantec modified the code to hold the semaphore in a non-atomic
context. 



Incidents from old Patches:
---------------------------
NONE