On Wed, 1 Mar 2000, Mark Sawle wrote:
> This is no good because it is a complete lockup. The machine
> won't respond to pings or any other network activity, or allow
> me to bring up the X display if the screen blanker has kicked
> in, respond to caps lock key presses, etc.
Before you say kernel bug, consider whether some user-level app is
eating up all the free memory. An infinite loop which allocates
memory can look like kernel lockup -- it's happened at least twice
to me, and I thought they were kernel bugs too at first, but in
both cases they were processes eating up all the free memory.
Try waiting it out. The wait will vary according to how much free
memory you have. You can limit process memory consumption with
ulimit, which may cut down the wait and help identify the source
of the problem.
If it is a memory hog problem, it may be in a script that you have
written (look for infinite recursion or an infinite loop which
allocates but doesn't free resources) or it may be a bug in any
application running on your computer, maybe even syslogd. Try to
make it reproducible with a minimal configuration so we have at
least some idea which app it may be. If the bug isn't immediately
obvious, tracking it down will likely require a debugger like gdb.
Ed
--
Ed Doolittle <mailto:[EMAIL PROTECTED]>
"Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
