On Wed, 22 Jun 2005 19:40:08 +0200, Chris Wedgwood <[email protected]>
wrote:
>> as before) or the kernel is in some way locked up (in particular: is
>> it necessary/better to reboot? Is there some risk of filesystem
>> corruption?).
>
>It's memory allocation failures. This might not work until memory is
>free but it shouldn't kill the kernel of be a huge problem if it's
>just the result of one ore more processes being memory hungry
I'm blaming myself for not having given a closer look before shutting
down the machine.
But, as I said, the shut down happened regularly. Later, to be sure, i
ran an fsck on all partitions and they were ok.
>It could also occur if there is a memory leak, in which case there is
>a bug that needs to be fixed and a reboot would be needed (I would
>only suspect that if it did it often and processes were not using much
>memory though).
It was the first time: this machine had been running on the same
kernel for six month with very long uptimes interrupted only by ups
control daemon (during blackouts).
Ah, no: the kernel had been changed about one month ago, but it was
the same version (2.4.26) and the same .config (except ext3 support
which I moved from modules to kernel itself).
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]