All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jorge Nerín" <jnerin@juridicas.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux SMP <linux-smp@vger.kernel.org>
Subject: Re: Memory management issues with 2.4.4
Date: Fri, 04 May 2001 08:31:02 +0200	[thread overview]
Message-ID: <3AF24CA6.10807@juridicas.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105021625520.4127-100000@freak.distro.conectiva>

Marcelo Tosatti wrote:

> 
> On Wed, 2 May 2001, Jorge Nerin wrote:
> 
>> Short version:
>> Under very heavy thrashing (about four hours) the system either lockups 
>> or OOM handler kills a task even when there is swap space left.
> 
> 
> First of all, please try to reproduce the problem with 2.4.5-pre1. 
> 
> If it still happens with pre1, please show us the output of "cat
> /proc/slabinfo" when the kernel is about to trigger the OOM killer.
> 
> Thanks.
> 
Well, I have tried with 2.4.5-pre1 compiled form SMP, and the result has been that this morning when I wake up the system has the console black (is there any way to prevent cons.saver from blanking the screen) and the disks where quiet, so I SysRQ-Sync, Umount, powerOff and then, at the last command the console wake up and I have been saluted with:

Kernel BUG in sched.c:709!
Invalid operand: 0000
Dump copied by hand, but not yet filtered by ksymoops (I'm at work now).
kernel panic Aiee, killing interrupt handler!
In interrupt not syncing.

This afternoon when I return home I will feed the stack dump to ksymoops and post the results, I mail this now just to see if someone sees the ligth.

-- 
Jorge Nerin
<comandante@zaralinux.com>


  reply	other threads:[~2001-05-04  8:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 14:57 Memory management issues with 2.4.4 Jorge Nerin
2001-05-02 19:27 ` Marcelo Tosatti
2001-05-04  6:31   ` Jorge Nerín [this message]
2001-05-04 15:29   ` Jorge Nerin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AF24CA6.10807@juridicas.com \
    --to=jnerin@juridicas.com \
    --cc=comandante@zaralinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.