Conference ozrock::x25_osf

896.0. "Want X25 Patch Details for the case CFS_41059" by PRCFS1::SOCHUNWAH () Fri May 02 1997 19:02

Hello,

	We had a customer running X2.5 V2.0 at DUNIX V3.2d-2, they 
	encountered X25 panic problem recently, and the panic matched the 
	case of CFS_41059.  They start having panic problem after the system
	was opened to external X25 in-coming connections.

	Customer wants to know what the X.25 patches does in full details, 
	and they want a X.25 test procedure to make sure the patch is 
	working reliability.  (The customer, from a programmer point of
	view, think that a patch kit target for solving some problem, must
	have some way to prove that it had fixed the problem, and there must
	be a way to trigger the happening of the problem such that the
	problem won't happen with the new software).

	After we had applied the CFS_41059 patch on 3-Apr-97, there were no
	X25 related panic being noticed for a month, which was quite reasonable
	to conclude that the patch had resolved the X25 panic problem (because
	the problem used to occur every 3~4 days).  About the X25 patch
	descriptions, we had provided to customer the associate README file,
	but customer want a very detail one.

	There exist no direct impact to customer.  But customer consider 
	providing solution details and testing procedures as part of DEC's
 	duty.  

	How can I be able to get the patch kit details ?  I am OK with the
	readme file associate with the patch kit, but customer didn't feel
	the same.



Rgds
SO




X25 Patch (Ref : CFS_41059) Readme File
---------------------------------------


Copyright (c) Digital Equipment Corporation 1996. All rights reserved.


PRODUCT:

X.25 V2.0


OP/SYS:

Digital UNIX V3.2B


SOURCE:

Digital Equipment Corporation


DATE:

21-MAY-1996
           
PROBLEM:
System crashes with panic string "kernel memory fault"
in asi_ctlinput.

ANALYSIS:
This problem occurs on SMP systems running X.25, running
applications which receive a high rate of incoming X.25 calls.
Using dbx to analyse the crash dump, the stack trace shows the panic
caused by asi_ctlinput(). The pan
ic string is
"kernel memory fault" and the trace footprint is

0 boot
1 panic(s = 0xfffffc000073efc8 = "kernel memory fault")
2 trap()
3 _XentMM
4 sounlock_ext
5 asi_ctlinput
6 AccProcessWaitingServiceQ()
7 netisr_thread()

DIGITAL RESPONSE:
                
There are TWO patched objects

	acc_interface_socket.o
	asi_ctlinput_socket.o

To install patches ..

 1. cd /usr/opt/XXA200/sys/XXAACC200
 2. save the old version of acc_interface_socket.o
    (eg. mv acc_interface_socket.o acc_interface_socket.o.V2)
 
3. copy the new acc_interface_socket.o to /usr/opt/XXA200/sys/XXAACC200
 4. cd /usr/opt/XXA200/sys/XXAACC200
 5. save the old version of asi_ctlinput_socket.o
    (eg. mv asi_ctlinput_socket.o asi_ctlinput_socket.o.V2)
 6. copy the new asi_ctlinput_socket.o to /usr/opt/XXA200/sys/XXAACC200

 7. cd to the /sys/MACHINE directory, 
	where MACHINE is the name of the machine 
    	in uppercase (e.g. for cheez, /sys/CHEEZ).
 8. make a new kernel by issuing a 'make relink' command
 9. save the running kernel (mv /
vmunix /vmunix.sav)
 10. move the new kernel to the root directory (mv vmunix /) 
 11. reboot the machine.

There is no other information.

Matt.