| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1761.1 | | NETCAD::STEFANI | Machines to humanize | Thu Jul 27 1995 22:09 | 7 |
| >>A customer of ours running Novell 3.12 is abending several times daily.
>>He uses the XL590 with a DEFPA and a RAID system on the EISA bus.
What's the message when it ABENDs? I don't know of any DEFPA-related
issues on NetWare 3.12.
- Larry
|
| 1761.2 | The error messages are ... | SNOFS1::KHOOJEANNIE | | Sun Jul 30 1995 23:32 | 31 |
| Dear Larry
The abend messages are as follows:
1 General protection processor exception (error code 00000000)
2 Operating system version ...
3 Running process interrupt service routine (nested count 2)
followed by either of
4 interrupted process media manager (this occurs about half the time)
4 interrupted process server 12 process
4 interrupted process intel prescan 0 process
4 interrupted process PAC transport process
Apparently the DEFPA is not on the supported options list for the
XL590, and in consequence the customer has had a lot of difficulty
getting Digital to support him.
He installed a DEFEA instead two days ago, and has had no further
abends. However his performance is 50% slower (what used to take 46s
with the PCI now takes 66s with the EISA), so he would prefer to return
to the PCI NIC, if and when he can get it to work, and Digital agrees
to support him!
Any suggestions would be much appreciated,
Jeannie
|
| 1761.3 | | NETCAD::STEFANI | Machines to humanize | Mon Jul 31 1995 09:55 | 26 |
| >>He installed a DEFEA instead two days ago, and has had no further
>>abends. However his performance is 50% slower (what used to take 46s
>>with the PCI now takes 66s with the EISA), so he would prefer to return
>>to the PCI NIC, if and when he can get it to work, and Digital agrees
>>to support him!
Digital (as in the Adapter Product Group) does support your customer.
Whether other business units do is out of our control.
The DEFEA and DEFPA drivers are essentially the same except for some
small differences in the bus interface. The DECpc XL family is not
"plug and play" so you must assign resources to the peripherals via the
PCI configuration setup. This includes enabling the slot, enabling bus
mastering, assigning and IRQ and latency timer value, and ensuring that
the DEFPA is installed in a bus mastering slot. I believe at least 1
of the slots in the XL is non-bus mastering.
Is it possible that the customer had a resource conflict (eg. IRQ
conflict) with the DEFPA installed? Are they using the MSM31X.NLM,
FDDITSM.NLM, and DEFPA.LAN files off the
KALI::PCDRIVERS:[DEFPA.INTERIM]FPKIT242.ZIP kit?
Also, make sure they are running the latest and greatest BIOS for the
XL and the most current disk driver.
- Larry
|
| 1761.4 | A couple more questions ... | SNOFS1::KHOOJEANNIE | | Tue Aug 01 1995 23:28 | 31 |
| >>> I believe at least 1 of the slots in the XL is non-bus mastering.
He is using a XL590 server as opposed to the XL590 workstation so
all slots are bus mastering.
>>> Also make sure they are running the latest and greatest BIOS
for the XL and the most current disk driver.
Yep, sure is.
>>> Is it possible that the customer had a resource conflict
(eg. IRQ conflict) with the DEFPA installed? Are they using the
MSM31X.NLM, FDDITSM.NLM, and DEFPA.LAN files off the
KALI::PCDRIVERS:[DEFPA.INTERIM]FPKIT242.ZIP kit?
He believes that there are no resource conflicts (he had an IRQ
conflict with his RAID controller early on but he fixed this).
I have given him copies of fpkit242.zip and fpkit241.zip (he was
using 2.40) for him to try.
With his replacement DEFEA, he has noticed that it does not run
FDDITSM.NLM, whereas the DEFPA did. What does the FDDI TSM.NLM
actually do?
I also found out that he is concurrently using an NE3200 Ethernet
EISA NIC (Ethernet TSM NLM). Could it be conflict between this NLM
and the FDDITSM.NLM?
Thank you very much for all your help so far - it has proved invaluable.
Jeannie
|
| 1761.5 | Latest DEFEA.LAN MUST use FDDITSM.NLM | MAVRIC::POST | Network backed up? Give it more fiber. | Thu Aug 03 1995 00:28 | 32 |
| Hi,
Larry is out for the week... Both the DEFEA and the DEFPA use
FDDITSM.NLM. The Novell architecture is each LAN driver is comprised of
three modules loaded at runtime:
MSM.NLM - Novell Supplied
OS Interface Module
xxxTSM.NLM - NOvell Supplied
ETHERTSM.NLM is used for Ethernet drivers
FDDITSM.NLM is used for FDDI drivers
TOKENTSM.NLM is used for Token Ring drivers...
xxx.LAN - Vendor supplied driver for adapter
EWRK3.LAN -
3C503.LAN -
DEFEA.LAN
DEFPA.LAN
For 3.11 servers there was a "monolithic" driver that was all three
modules in one .lan file. the newer architecture has been in place
since NetWare 3.12. The readme's on the floppy show how to make the
"new" architecture driver run on 3.11.
If he is using both the latest DEFEA and DEFPA drivers, then
FDDITSM.NLM MUST be loaded.....
Again, is sounds like a resource conflict...
-Don
|
| 1761.6 | | NETCAD::STEFANI | Machines to humanize | Mon Aug 07 1995 19:29 | 11 |
| To add to Don's note, if the customer has multiple NICs installed, they
should *ALL* be of the MSM-TSM-.LAN variety. The ETHERTSM.NLM and
FDDITSM.NLM files won't interfere with eachother, but they ARE tied
closely with two files: MSM.NLM (for NetWare 4.X) and MSM31X.NLM (for
NetWare 3.1X).
The current certified versions of MSM.NLM, MSM31X.NLM, ETHERTSM.NLM,
and FDDITSM.NLM are v2.50. The customer should check that these files
are up to rev.
/l
|
| 1761.7 | How to load FDDITSM? | SNOFS1::KHOOJEANNIE | | Wed Aug 09 1995 23:14 | 9 |
| Thanks Larry and Don
The customer is *sure* that the DEFEA's autoload does not load
FDDITSM.NLM and that it is not running.
Could this be possible? What can he do to fix this?
Jeannie
|
| 1761.8 | Double-check his autoexec.ncf | TOOK::THOMPSON | | Thu Aug 10 1995 12:26 | 16 |
|
Jeannie,
Tell the customer to load the install utility and under system
options to edit his autoexec.ncf. It should load all files that
he needs to run the driver including:
load msm
load fdditsm
load defpa.lan frame = ...
bind ipx to defpa net = ...
Make sure all these paramaters are loaded and try again.
-Brenda
|
| 1761.9 | DEFEA.LAN may be very very old | MAVRIC::POST | Network backed up? Give it more fiber. | Thu Aug 10 1995 18:17 | 15 |
| Hi Jeannie,
After rereading the previous notes again, I noticed that the version of
the DEFEA.LAN driver is never mentioned. If the customer is loading the
1st DEFEA.LAN driver we ever shipped (1993 date) the yes FDDITSM.NLM
will not be loaded. It is of the old style which had the MSM,TSM, and
HSM built into one driver. Using this driver his performance would be
as worse than the new driver. Make sure he is running the driver from
the 2.40 disk KALI::PCDRIVERS:[DEFEA.RELEASE]FEKIT240.ZIP or ftp
from
ftp.dec.com \pub\DEC\adapters\defea\interim\fekit240.zip
This driver will load with a FDDITSM.NLM and have better performance...
-Don
|