Re: 2.1.128 Lock - can be unlocked

Helge Hafting (helge.hafting@daldata.no)
Mon, 16 Nov 1998 09:23:57 +0100


2.1.128 tend to lock up for me now and then. I am typically using X
when this happens, logged in as a normal user running X by using "startx"

My load meter in x display high load. I can switch
to another virtual console and try to log in as root,
it gets to "no mail" and nothing more happens.
No command prompt no matter how much I wait.

But I can "unlock" by switching to another virtual console
and back. Now I have a command promtpt for root, and can give
some command, like "ps". This tend to lock again with no output,
but ALT-F1 ALT-F2 and I have the process list on my screen.
This is repeatable once the lock occur, most commands will just stop
but output get there if I change between virutal consoles one or two times.

Killing some user processes or the entire X server with all clients
will sometimes restore the machine to a normal state so I can
continue using it. Other times require a reboot, this is
usually possible by using a normal "shutdown -r now" and some
console switching for unlocking.

I am using a uniprocessor kernel 2.1.128 with no patches. It looks like
any process can make the problem occur, but it looks like the console
may have something to do with it as the console switching help a bit.

Please tell if there is more I can do to help track this down.

Helge Hafting

-
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/