[PLUG] computer lockups

[Charles Allen]

Woah, dude! the same thing happened to me today!  I came back to find my GUI
locked up... I just cold booted though.....probably shouldn't have though
:-)
-chuck

----- Original Message -----
From: Scott Minster <sminster@purdue.edu>
To: Plug <plug@csociety.purdue.edu>
Sent: Thursday, April 05, 2001 7:34 PM
Subject: [PLUG] computer lockups


> I came home from class today to find my Linux computer somewhat frozen.  I
> say somewhat because the GUI did not respond at all (so it looked like it
> was locked up), but it still responded to pings and it routed packets.
> However, I couldn't create a new ssh session (and I didn't already have
one
> up).  I suspect that the problem was that it couldn't (for some reason)
> create a new process (since sshd forks to handle each session).  After I
> cold rebooted, there were no messages in any log files.  The logging just
> stopped after a certain point, then started up again with the boot logs.
So
> either the logging daemon stopped working, or nothing made any logs after
> the point that it froze.
>
> Oddly enough, I can make my Windows 2000 computer do the same thing under
> certain circumstances.  One game I have has an odd bug that sometimes
causes
> the same result.  As near as I can tell, the computer is still there, but
> must be heavily loaded since typing on a telnet login is incredibly slow.
> It also displays the same problem of not being able to create any new
> processes.  As a result, I can't even kill the program that creates this
> problem (so I don't know if it's the program or the system).
>
> These two computers are both x86, but that's about their only similarity.
> Is it possible that both Win2k and Linux have a similar bug, or is it not
OS
> dependent but some flaw somewhere else?  Or is it just coincidence?  I'd
> consider bad hardware, but to see the same type of thing on two different
> systems raises some questions.  In any case, it's an extremely rare thing,
> since I have to really work to make it happen on my Win2k computer, and
have
> no idea what causes it on my Linux computer (it was screensaving when it
did
> it).
>
> Does anyone have any ideas about what this could be?  It's not a huge deal
> since it doesn't happen very often, but it would be nice to not have it
> happen at all.
>
> ----
> Scott Minster
> sminster@purdue.edu
> http://mland.dhs.org/
> icq://18777468/
>
> ____________________________________________________
> The Purdue Linux Users' Group (PLUG) mailing list.
> For account maintenance, go to:
> plug mailing list  -  plug@csociety.purdue.edu
> http://csociety.ecn.purdue.edu/mailman/listinfo/plug
>