Re: 2.1.38/39 unstable, No, REALLY, I mean it.

Jeffrey Wiegley (wiegley@usc.edu)
Mon, 19 May 1997 11:46:53 -0700


Open mouth, insert foot, chew...

Of course after sending my lengthy reply about undefining SMP=1 and
having the machine up and running for two days...

V2.1.39 REALLY DOES LOCK UP!! (so does probably v2.1.38)

Things I had running:
v2.1.39 kernel with 2940 support.
PPP v2.3
X-Windows v3.2A
Netscape Communicator 4.0b3

I know exactly what I did to cause the lockup but I don't know if I can
repeat it and I don't know what underlying network stuff went on that
locked up.

Basically:

I had some Netscape windows open. I clicked to open a new browser. The
browser window came up. The browsers load, as a default URL, a cgi-bin
program on my local machine. So the first thing Netscape browsers do
is: "Contacting host: 127.0.0.1..." and at that point *everything* about
my computer locked up solid. I could hear a disk chirp every couple of
seconds but nothing else did anything at all.

There is *nothing* about anything unusual in the log files either.

So. In summary there does appear to be a serious network bug in at least
v2.1.39 and v2.1.38 that can cause complete locks.

I apologize for not being more help in providing a fix but hope that
this info can help a guru trace down the problem.

- Jeff Wiegley