|
Hello Kenji,
The Bit3 adapter you have is old. There have been a number of
revision changes since then.
A few months ago, we found certain high performance PCI cards can
cause different "bad" things to happen when running with the older
Bit3 PCI cards. Bit3 Corp. did some investigating and identified
a problem with their boards. They have since come up with a hardware
fix for this problem. This "fix" is in revision "P" or "Q" of their
PCI board.
I recommend you get your hardware updated to the latest. The Bit3
manual explains how to do this. If you have any questions, send
me mail at ADISSW::TENHAVE. Bit3 will do the update for any hardware
less than 1 year old. Their tech support people can find out the
age of your hardware. After 1 year old, Bit3 will charge for the work.
I would like to see any "crash" files or "messages" files you may have.
Please also include a copy of "dwpvc_data.c" file for UNIX 3.2X or
"sysconfigtab" file for UNIX 4.0, versions of the DWPVC kit.
Let me know or post here what you decide to do...
Thanks, Tim Tenhave
|
|
Thanks Tenhave-san,
I understood I will must change Bit3 hardware. However, I have some
OEM customer who configured old Bit3 hardware to their system. If possible,
please tell me the reason why must change later Bit3 PCI card.
Because I have never heard the problem about old Bit3 card from my
customer. Should every customer update to later Bit3 PCI card ?
I hsten to inform you the following facts about this problem.
- Configuration parameter
I used default dwpvc_data.c, default sysconfigtab, excluding VME
probe address.
- No error message
I could not find any error log from UNIX.
- Irregurar appearance
Bad state was not irrelevant to size of DMA transfer, number of DMA
transfer.
- Reappear bad state
- Lock timing
When VGA console was displaied on screen for abort, if I quickly
stopped process of continuously DMA transfer invoking CTRL/C,
UNIX understood some command, for examples "/usr/sbin/xdm stop",
but Xserver could not restart.
If I invoked CTRL/C late, UNIX did not reply. Sorry then I did not
tried to login via network or login via serial port.
Sorry it was not importance now that I settle this question, sales
person decided to propose other way to him customer. Rather I concern
about replacement of Bit3 hardware.
regards,
Kenji
|
|
Hello Matsumoto-san,
>> Should every customer update to later Bit3 PCI card ?
This is difficult to answer. If it is not broken, do not fix it. But,
if the same Bit3 adapter may be used on newer Alpha systems in the
future, you may want to fix it. This problem brings up a larger
problem. Since DIGITAL does not manufacture and control the Bit3
hardware, it is very difficult for us to control all the various ways
that these adapters are used and the various systems they end up in.
I also understand that if you are not in the United States, it is even
more difficult to get boards updated.
The best thing to keep in mind, is that if everything is OK in one
system, it may not be OK in a newer system. This may not be acceptable
to everyone, but DIGITAL does NOT control the hardware design of the
Bit3.
I am also not saying Bit3 Corp is doing a bad job. Their product is
used on PC's, Workstations, and Servers from many different venders.
It is not just for DIGITAL Alpha systems. They cannot possibly test
and design for every venders hardware using every possible PCI add-on
card.
This is one reason why we take so long to make a system official.
--------------------
Now back to your problem:
Make sure that the DWPVC kit is the first thing in the HOSTNAME.list
file.
Without seeing and having the equipment to see you exact problem, I
can not do much more than this.
------------------
Please feel free to ask about any concerns,
Tim Tenhave
|