Messages in this thread | | | Date | Sun, 30 May 1999 20:11:23 -0700 (PDT) | From | Ted Rolle <> | Subject | Re: Everyone's a captain on a calm sea... |
| |
Well, it's been a well-known problem since as far back as RH 4.2. It has persisted all this time -- I checked on #linux and others confirmed it.
Is there a 'back door' to get a terminal session? What about Alt-SysRq?
My own systems have all been i486+. The lockup seems to occur at random times when Netscape is up. There is constant disk activity during the problem; response is slow -- 30 seconds for the cursor to move after the mouse has moved -- sometimes.
What information should I gather when the problem recurs? I _may_ have a set of data that can reproduce the problem -- it is a message of my wife's on usa.net that locked it up twice.
I realize that this a "something's wrong, please fix it" request, but it points to a long-standing problem: that of ending a rogue program. Perhaps someone else can provide more information.
On Mon, 31 May 1999, Alan Cox wrote:
> > It seems that the OS should be able to detect a rogue application > > and take some corrective action -- just letting me log in on a different > > terminal to kill the offending process would be sufficient. > > Nod > > However before anyone can even guess what problems you are seeing, you need > to provide some basic info - kernel version, architecture, general machine > info, accurate report of the lockup >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |