All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-mm@kvack.org
Subject: Re: VM problem with 2.4.8-ac9 (fwd)
Date: Thu, 23 Aug 2001 20:35:38 +0300	[thread overview]
Message-ID: <3B853EEA.6D445E0E@pp.inet.fi> (raw)
In-Reply-To: 3B84BE0A.C9082E87@pp.inet.fi

Jari Ruusu wrote:
> Marcelo Tosatti wrote:
> > 2) Did you tried with older kernels or 2.4.9?
> 
> Linus' 2.4.9 survived about 7 hours of VM torture, and then I got ext2
> filesystem corruption (just once, dunno if it is repeatable). No "swap
> offset" problems with 2.4.9 so far. Haven't tortured older kernels yet.

Update:

Stock Linus' 2.4.7
~~~~~~~~~~~~~~~~~~
Box didn't die but I stopped VM torture test after this appeared:

Unused swap offset entry in swap_dup 003d6b00
VM: Bad swap entry 003d6b00
Unused swap offset entry in swap_count 003d6b00
VM: Bad swap entry 003d6b00

Stock Linus' 2.4.8
~~~~~~~~~~~~~~~~~~
bzip2 decompress + tar failed (twice, but at different place):
> tar: Skipping to next header
> 
> bzip2: Caught a SIGSEGV or SIGBUS whilst decompressing,
>         which probably indicates that the compressed data
>         is corrupted.
>         Input file = (stdin), output file = (stdout)
> 
> It is possible that the compressed file(s) have become corrupted.
> You can use the -tvv option to test integrity of such files.
> 
> You can use the `bzip2recover' program to *attempt* to recover
> data from undamaged sections of corrupted files.
> 
> tar: 360 garbage bytes ignored at end of archive
> tar: Child returned status 2
> tar: Error exit delayed from previous errors

glibc compile failed:
> make[2]: *** [math/subdir_install] Segmentation fault

Note: previously mentioned ext2 filesystem corruption (with kernel 2.4.9)
was in bzip2 decompress + tar restored directory hierarchy, so above bzip2
decompress + tar failure can explain that too. Maybe something went
similarly wrong and bzip2 outputted garbage to tar instead of terminating
with SIGSEGV.

6 hours of VM torture, 3 incidents where a process died with SIGSEGV. No
"swap offset" problems with 2.4.8 so far.

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-23 17:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 19:25 VM problem with 2.4.8-ac9 (fwd) Rik van Riel
2001-08-22 18:27 ` Marcelo Tosatti
2001-08-23  8:25   ` Jari Ruusu
2001-08-23 17:35     ` Jari Ruusu [this message]
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=3B853EEA.6D445E0E@pp.inet.fi \
    --to=jari.ruusu@pp.inet.fi \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --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 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.