PROBLEM: (749B23467/QAR 52293) (Patch ID: OSF405-400225) ******** This patch is an upgrade/replacement for the "FTA" FDDI driver and fixes a DMA Error which can occur with the older driver. If it became necessary to back out a partially constructed frame from the transmit queue, the older driver was unable to properly backed out the frame before restarting. This resulted in the following errors being logged to the /var/adm/messages file: vmunix: fta0: Halted. vmunix: fta0: Halt Reason: DMA Error vmunix: fta0: Link Unavailable. vmunix: fta0: Link Available. PROBLEM: (CLD MCPM40MKM, QAR 52790) (Patch ID: OSF405-400409 ) ******** This patch resolves a problem in the FDDI driver during device reset and and initialization. PROBLEM: (MGO103292) (Patch ID: OSF405-400467) ******** This patch fixes a kernel memory fault caused by the fta FDDI driver. The stack trace looks like this: panic trap _XentMM prf printf fta_poll_cmd_req ftaioctl ifioctl soo_ioctl ioctl_base ioctl syscall _Xsyscall PROBLEM: (MXOB30447) (Patch ID: OSF405-208) ******** This patch corrects a problem with the FDDI fta driver. In systems that have heavy FDDI traffic, it is possible for the FDDI fta driver to think it received a bad packet. A message will appear in the /var/adm/messages file similar to the following: vmunix: fta0: Invalid length: DA: ef-be-ad-de-ef-be => SA: ad-de-ef-be-ad-de In this example, kmem_debug was turned on with kmem checksum. The kmembucket that was being read by the driver was corrupted BEFORE the read was posted. You may see different values on your system.