From: garrett@garnet.berkeley.edu (Garrett D'Amore) Subject: [BUG] Network eth0 device fault Date: 24 Apr 1993 09:09:52 GMT
I have very recently started getting errors:
"eth0:DMAing conflict in ne_block_output". I've gotten
three of these within a short span (two hours) that I know about. Two of
them locked the system -- had to reboot. Not nice!
What am I doing:
1) Using nnmaster to thread news off of a remote site, and trn to read
news simultaneously.
2) Allowing users to telnet in. I don't know everything that they might
be doing, but I don't think its network intensive stuff.
3) Running vi. The two lockups occured while I was in vi (running from
trn).
Yesterday I was running trn just fine... no problems (except for a bug
in mini-inews having to do with gethostname not returning, I posted about
that and the fix earlier).
Only today have I had problems, and only since I tried to run nnmaster in the
background to build the local thread database.
Is this is a problem with multiple processing trying to use the same port?
(Port 119 in this case...)
Is there a fix to this? Has anyone else tried to use processing which use
the same port simultaneously? Is it hopeless for me to try?
I will try testing different telnet/ftp/nn/trn/etc combinations to see if
I can reproduce the behaviour on different ports, or even just this port.
It is possible I suppose that the problem could be nnmaster, but it would be
nice if nnmaster didn't have the power to shut down the system like that.
====================================================================
Garrett D'Amore | garrett@haas.berkeley.edu
Software Co-Ordinator | 68 Barrows Hall, UC Berkeley
Haas Computing Services | Ph: 510-643-5923 Fax: 642-4769
====================================================================