| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1136.1 | more infos please | PADNOM::PEYRACHE | Sarip Torppus Lanoiger | Wed Nov 03 1993 10:30 | 6 | 
|  | 
 hi Danny,
 what kind of problem have you with TSM ??
 Jean-Yves
 | 
| 1136.2 | FXDRIVER X-24 | CSC32::DEUMBERTO |  | Wed Nov 03 1993 11:47 | 16 | 
|  | 	I have a copy of this driver which was given to me specificaly for a CLD
	at Mc Donald Dougles. We had a problem where NETACP would hang in LEF
	waiting for a USTART command to complete. The I/O could been found 
	sitting on the Control Pending Queue of the LSB. This driver was a 
	work around and the actual cause to the problem was located in the 	
	firmware. It is unclear if the fix has made it to release 2.0.
	I had a problem with TSM related to this firmware bug. When issuing 
	commands from TSM a %SYSTEM-F-DEVREQERR error was returned. Commands 
	issued to the DEMFA were failing. As mention in .3 I need to understand 
			
	the problem you are having with TSM before we can determine if this will
	help.
	
	 
 | 
| 1136.3 | See note 598 in TSM-notes | BACHUS::GOOVAERTS |  | Thu Nov 04 1993 02:17 | 10 | 
|  |     Hello,
    	my problem is the problem as described in notes entry 598 of TSM.
    In 598.3,there is  reply which states that fxdriver x-24 solves
    the problem.
    	Why so anxious about that fxdriver?Does it contain also 
    	the formula against hair-loss,the recipe for eternal youth,
        and the remedy against the world-wide economic crisis?
    
    Danny
    
 | 
| 1136.4 | not really fixed.... | PADNOM::PEYRACHE | Sarip Torppus Lanoiger | Fri Nov 05 1993 04:56 | 18 | 
|  | 
   response .2
 
  >>> It is unclear if the fix has made it to release 2.0.
    
   For me, it's clear now ....
 i have tried this version on customer site (v2.0 of DEMFA)
  and the problem still occurs.
 Now i wait a full dump during the problem for Raise a IPMT process.
  if you have more infos ,thanks to posted some replies
  Regards
  Jean-Yves
  Country Support France
 | 
| 1136.5 | FIX for TSM and NETACP | STU03::RUEGGEN |  | Mon Nov 08 1993 03:38 | 13 | 
|  |     Hello,
    
    
    I had all these problems aswell and for me the fix was as follows:
    
    1. NETACP problem was fixed by FXDRIVER X-24
    
    2. TSM problems were fixed by TSM 2.0-003
    
    
    	regards
    
    		Ulrich Rueggen
 | 
| 1136.6 | Do you have it stored somewhere? | BACHUS::GOOVAERTS |  | Mon Nov 08 1993 04:33 | 8 | 
|  |     Hello,
    
    	do you have still a copy of that FXDRIVER ?
    
    	I would be luchy with it.
    
    Danny
     
 | 
| 1136.7 | Thanks | BACHUS::GOOVAERTS |  | Mon Nov 08 1993 14:38 | 4 | 
|  |     Thanks for the copy
    
    Danny
    
 | 
| 1136.8 | A couple of questions | 42033::HARBOUR | Stuart | Tue Feb 15 1994 09:13 | 30 | 
|  |     We have a customer who has been suffering from both intermittent system
    hangs and CPUSPINWAIT bug checks. They are running TSM V2.0-0 across FDDI
    and are using VMS V5.5-2 with the X-22 FXDRIVER. 
    The crash dumps that I've looked at show that the hung CPU is looping in 
    FXDRIVER in modules FX$START_CMD and FX$DO_STAT with FX$C_RUN = 5 and
    LSB$L_MFA_FLAGS = 50. R5 always points to the UCB for the DECNET client 
    device.
    As a temporary workaround we have moved TSM away from the node with FDDI
    and I also appreciate that I can fix the TSM problem by applying patches
    to bring it to V2.0-5, but I have a couple of questions.
    Which version of the FXDRIVER should I be using, X-22 or X-24? Image
    identification information is as follows:
    		image file identification: "X-24"
    		link date/time: 26-MAR-1993 13:56:54.82
    		linker identification: "05-13"
    
    		image file identification: "X-22"
    		link date/time: 5-OCT-1993 12:57:39.81
    		linker identification: "05-13"
    Is TSM the only cause of this loop in the driver or is it possible that
    something else may trigger the problem?  
      
    Thanks in advance,
    Stuart.
 |