Date: Wed, 1 Sep 1999 11:25:10 +0200 (CEST) From: serces@mud.dk To: FreeBSD Tokenring Mailinglist <freebsd-tokenring@freebsd.org> Subject: Strange Lockup Occurring Message-ID: <Pine.LNX.4.10.9909011053130.24445-100000@eowyn.zahle.dk>
next in thread | raw e-mail | index | archive | help
Hi all Sorry if this has been asked before or answered somewhere else, but I seemed unable to find anything about it in the Archives :). System is running 3.2-STABLE on a NetFinity 5000, with an Olicom 3117 ISA card. I have had the same NIC running in another machine, though only at 4Mbit, whereas in production it has to run 16Mbit not that I could see that being any problem. Though something goes haywire somewhere, and to me it's veryveryvery strange.. :) Here's what's going down: Machine boots, I login on the console no problem, then I start a connection to another machine, woohoo, no problem, happy I am :), then I try to connect from a remote station to the server, still no problem, everything should be happy in tokenland (or so I thought). I then decide to start configuring the machine, installing the things I need, so I switch to the apachedir in the ports-collection, and exclaim make install on command line, it fires up, and then stops responding, nothing happens, no transfer, nothing, and at the same time I start losing my connection to the machine (Connection closed by remote host). First time around, I go to the machine, login on the console, and reboot the machine. Everything starts working again, so I think, ah, I must have made a blunder somewhere. While still at the console I do the exact same manouver as before to install apache (or anything really :), same thing happens, NIC stops responding, and nothing happens. For some obscure reason I try to do an "ifconfig oltr0 down", that one gives: Aug 31 13:39:30 urd /kernel: oltr0: otlr_stop Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 12 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 13 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 14 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 15 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 0 status 1) ... etc .. a ton of these followed by Aug 31 13:39:36 urd /kernel: oltr0: DriverCloseCompleted And then an "ifconfig oltr0 up", everything works perfectly again. Someone suggested setting the MAX_USERS to 256, which was tried, and even though I couldn't see any immediate result, it might have helped since I think it performed a bit better (But that again might simply be because of the increased buffer sizes :). Currently the machine is not in production, so every 15 minutes I reset the NIC by a small shellscript that takes it down and then up again, it works, At least if I then try to do something that will lockup the NIC I only have to wait max 15 mins to get it running again, and is thereby saved the trouble of running back and forth.. :) Any ideas of what might be wrong? I mean, connectivity to/from the machine seems to be no problem using ssh or telnet, but scp/rcp/ftp/http anything really that fetches more data, will stop the NIC from responding. hope someone can help.. :) S. P. Skou "The Law of Self Sacrifice" When you starve with a tiger, the tiger starves last. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.9909011053130.24445-100000>