linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-mm@kvack.org, Jari Ruusu <jari.ruusu@pp.inet.fi>
Subject: Re: VM problem with 2.4.8-ac9 (fwd)
Date: Wed, 22 Aug 2001 15:27:45 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0108221526170.2651-100000@freak.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108221622160.31410-100000@duckman.distro.conectiva>


On Wed, 22 Aug 2001, Rik van Riel wrote:

> Hi Alan,
> 
> Another report of tasks dying on recent 2.4 kernels.
> Suspect code would be:
> - tlb optimisations in recent -ac    (tasks dying with segfault)
> - swapfile.c, especially sys_swapoff (known race condition, marcelo?)

There are known races on swapoff, but Jari is not running swapoff...

> 
> What would cause the swap map badness below I wouldn't know,
> maybe marcelo is more familiar with the swapfile.c code...

Jari, 

1) Are you using an SMP kernel? 
2) Did you tried with older kernels or 2.4.9?


> 
> Rik
> --
> IA64: a worthy successor to the i860.
> ---------- Forwarded message ----------
> Date: Wed, 22 Aug 2001 20:37:01 +0300
> From: Jari Ruusu <jari.ruusu@pp.inet.fi>
> To: Rik van Riel <riel@conectiva.com.br>
> Subject: VM problem with 2.4.8-ac9
> 
> Unused swap offset entry in swap_dup 00519e00
> VM: Bad swap entry 00519e00
> Unused swap offset entry in swap_count 00519e00
> Unused swap offset entry in swap_count 00519e00
> VM: Bad swap entry 00519e00
> Unused swap offset entry in swap_dup 006b8a00
> VM: Bad swap entry 006b8a00
> Unused swap offset entry in swap_dup 006b8a00
> VM: killing process nscd
> Unused swap offset entry in swap_dup 006b8a00
> VM: killing process nscd
> VM: Bad swap entry 006b8a00
> Unused swap offset entry in swap_dup 005e6900
> VM: Bad swap entry 005e6900
> Unused swap offset entry in swap_dup 005e6900
> VM: killing process init
> Unused swap offset entry in swap_dup 005e6900
> VM: killing process init
> Unused swap offset entry in swap_dup 005e6900
> VM: killing process init
> Unused swap offset entry in swap_dup 005e6900
> VM: killing process init
> Kernel panic: Attempted to kill init!
> 
> Linux debian 2.4.8-ac9 #1 Wed Aug 22 16:04:25 EEST 2001 i686 unknown
> Gnu C                  2.95.3
> Gnu make               3.79.1
> binutils               2.9.5.0.37
> mount                  2.11g
> modutils               2.4.6
> e2fsprogs              1.18
> PPP                    2.3.11
> Linux C Library        2.1.3
> ldd: version 1.9.11
> Procps                 2.0.6
> Net-tools              1.54
> Console-tools          0.2.3
> Sh-utils               2.0
> 
> I get a repeatable VM failure with recent 2.4 kernels, tested with
> 2.4.8-ac[789] on x86 architecture. My VM torture test consists of following:
> boot the kernel with "mem=16M" parameter, start X11 and a couple xterms
> running kernel compile, glibc compile, bzip2 decompressor + tar, and top.
> Also xosview was running. Working memory need of such setup is way over
> available RAM, and swap use was about 20-35 MB (of 190 MB available swap),
> and swapping activity was _continuous_. Kernel 2.2.19aa2 survives the
> torture (everything else being same), and memtest-86 does not find any
> errors, so it is unlikely to be hardware failure.
> 
> Anyway, the box dies after about 1-3 hours of torture. Sometimes it just
> kills some random process. I captured above info using serial console. If
> you need more info (.config, System.map, whatever) just ask for it. I am
> willing to do more testing, just tell me what you need done.
> 
> Regards,
> Jari Ruusu <jari.ruusu@pp.inet.fi>
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2001-08-22 18:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 19:25 Rik van Riel
2001-08-22 18:27 ` Marcelo Tosatti [this message]
2001-08-23  8:25   ` Jari Ruusu
2001-08-23 17:35     ` Jari Ruusu
2001-08-23 20:24       ` Hugh Dickins
2001-08-23 20:29         ` Alan Cox
2001-08-23 20:37           ` Rik van Riel
2001-08-24 17:23         ` Jari Ruusu
2001-08-24 17:41           ` Alan Cox
2001-08-24 18:40             ` Marcelo Tosatti
2001-08-24 20:11               ` Rik van Riel
2001-08-25 13:10                 ` Jari Ruusu
2001-08-28 15:49                   ` Jari Ruusu
2001-08-22 21:14 ` Alan Cox
2001-08-22 21:28   ` Rik van Riel
2001-08-22 21:33     ` Alan Cox
2001-08-22 20:03       ` Marcelo Tosatti
2001-08-22 21:34       ` Rik van Riel
2001-08-23  6:19   ` Eric W. Biederman
2001-08-23 12:53     ` Alan Cox
2001-08-23 13:18     ` Rik van Riel

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=Pine.LNX.4.21.0108221526170.2651-100000@freak.distro.conectiva \
    --to=marcelo@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jari.ruusu@pp.inet.fi \
    --cc=linux-mm@kvack.org \
    --cc=riel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox