[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

1627.0. "DEFPA PCI FDDI problem with Digital UNIX V3.2" by 51900::jpt (FIS and Chips) Fri Mar 17 1995 11:22

We have a problem with Sable and DEFPA in Digital UNIX V3.2 (SSB). Could
someone confirm if they have working configuration and what kind that
configuration is with detailed revision information if possible.

Here's an entry from AOSG::ALPHA_OSF conference:

Notefile: AOSG::ALPHA_OSF
Note: 9334.0
Author: NAMIX::jpt "FIS and Chips"
Topic: PCI FDDI problem (crash) with V3.2
Date: 15-MAR-1995 09:42
Lines: 15
Replies: 1

Does anybody have working PCI FDDI configuration, as our customer's system
(same as previous note about presto :-( crashes with Kernel memory fault
soon after FDDI starts.

I have traced few of the dumps, and it seems like it propably crashes to
interrupt handling of FDDI driver. Symptoms are such that it _may_ be hardware
problem, but as DEFPA is bright new card and I have no idea how well it has 
been tested with V3.2. 

If no one can confirm working PCI FDDI configuration and card does not fail
in tests, we'll make an IPMT.

regards,

		-jari
T.RTitleUserPersonal
Name
DateLines
1627.1Works for meMPGS::RIEDLMon Mar 20 1995 07:314
    
     I have the DEFPA working on multiple sables and Mikasa under OSF 3.2,
    no crashes or any other problems. I just can't figure out how to boot
    on it, but the ethernet works good enough for that....
1627.2full installation or installupdate ??51900::jptFIS and ChipsMon Mar 20 1995 11:476
>     I have the DEFPA working on multiple sables and Mikasa under OSF 3.2,
>    no crashes or any other problems. I just can't figure out how to boot
>    on it, but the ethernet works good enough for that....

	Thanks for info! Have you fresh V3.2 installations or have you done
	installupdate from V3.0 to V3.2 on any system?