| >>prioris XL system problem is described as a "memory leak". System slow
>>and lots of paging. we're currently investigating BLITZ 2055 but that
>>only lists the Celebris as having the problem.
What are the details for BLITZ 2055?
>>Can someone verify that these configurations are valid and
>>should work? (and that v2.7 didn't introduce a problem...)
Both configurations are supported as far as the DEFPA team is
concerned. The DEFPA is qual'd on the Sable (AlphaServer 2100), but
the PCBU is only now beginning a DEFPA qual on their high end servers.
There are no memory leaks that I'm aware of in the DEFPA drivers and
there haven't been any since I first released the driver a year and a
half ago. There *was* a potential stack overflow problem in the transmit
path that was quashed late last year.
I use the Prioris XL Server for development with two DEFPA's and a
DEFEA. If there was a systemic problem, I would probably have found
it. You may wish to file an IPMT case. I'm sure there are working
XL server configurations with DEFPA that could be compared with yours
to see what the differences are.
- Larry
|
| >>What are the details for BLITZ 2055?
I read your note. BLITZ 2055 refers to the Triton chipset issue with
original revision DEFPA's. Since the Celebris GL is the only Digital
PC that I'm aware of that uses Triton, this report isn't applicable to
your customer's Prioris XL Server platform.
If the customer is still willing to work with us, have them replace the
DEFPA in the system, then escalate the problem. You should provide, at
a minimum, a WINMSD dump of the system and a complete listing of
installed options and their resource configurations (IRQ, I/O, memory,
DMA, etc). It can then be matched with known working setups (like the
one in my office) and perhaps we can come to a resolution.
With regards to the 2100, the DEFPA does work in that system and since
it is THE FDDI PCI adapter for the Alpha systems, there's an installed
base of hundreds if not thousands.
- Larry
|