All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kim Bisgaard <kib@dmi.dk>
To: linux-kernel@vger.kernel.org
Cc: lastec@dmi.dk, kib@dmi.dk
Subject: Random core dumps, and misreading files
Date: Thu, 9 Aug 2001 14:07:20 +0200 (MET DST)	[thread overview]
Message-ID: <200108091207.OAA10720@berta> (raw)


I gets random core dumps and and misreading of files. The chances for provoking
there errors, increases with the amount of memory used.

With misreadings of files I mean eg. copy a large file then compare several
times and get different answers each time.

I have seen this in kernels 2.4.4-7, in both 1GB and 4GB settings, and using
kgcc and gcc-2.96-69. 

The HW is AMD Athlon 1100, 1.5GB memory, VIA Apollo KT133 chipset.

I have used a memory test program, which ran without any problems!
- memtest: http://www.qcc.sk.ca/~charlesc/software/memtester/
     version is v.2.93.1 by Charles Cazabon <memtest@discworld.dyndns.org>
     dynamic version (libc.so.6 and ld-linux.so.2) (28/12/2000)


Good ways to provoke the error is to create a couple of ~2GB files, the files
have to get in and out of the file system cache, in order to go different.

Error scenario:
% cmp clout010629part001.dump.gz clout010629part001.dump.2.gz
clout010629part001.dump.gz clout010629part001.dump.2.gz differ: char 2351101, line 7984
% gunzip -vt clout010629part001.dump.2.gz &
% gunzip -vt clout010629part001.dump.gz&
gunzip: clout010629part001.dump.2.gz: invalid compressed data--crc error
[3]    Done                          gunzip -vt clout010629part001.dump.gz
[2]  - Exit 1                        gunzip -vt clout010629part001.dump.2.gz
% cmp clout010629part001.dump.gz clout010629part001.dump.2.gz
clout010629part001.dump.gz clout010629part001.dump.2.gz differ: char 1253855229, line 4124979
% cmp clout010629part001.dump.gz clout010629part001.dump.2.gz
cmp: clout010629part001.dump.gz: Input/output error
% gunzip -vt clout010629part001.dump.2.gz
clout010629part001.dump.2.gz:        OK
% gunzip -vt clout010629part001.dump.gz
clout010629part001.dump.gz:   OK
% cmp clout010629part001.dump.gz clout010629part001.dump.2.gz
% gunzip -tv clout010629part001.dump.2.gz &
% gunzip -tv clout010629part001.dump.gz &
gunzip: clout010629part001.dump.2.gz: invalid compressed data--crc error
gunzip: clout010629part001.dump.gz: invalid compressed data--crc error
gunzip: clout010629part001.dump.gz: invalid compressed data--length error
% 


A zap from top during these tests:

% top
    1:44pm  up 2 days, 22:04,  6 users,  load average: 2.03, 1.22, 0.81
205 processes: 202 sleeping, 3 running, 0 zombie, 0 stopped
CPU states: 13.3% user, 37.3% system,  0.0% nice, 49.3% idle
Mem:   899996K av,  896940K used,    3056K free,       0K shrd,    3556K buff
Swap: 5210256K av,  224132K used, 4986124K free                  851892K cached

  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 9290 kib       18   0   352  352   288 R    25.2  0.0   0:20 cmp
 9289 kib       19   0   384  384   316 D    21.6  0.0   0:17 diff

I am available for further tests, and requests for more info.

Best Regards,
Kim Bisgaard


                 reply	other threads:[~2001-08-09 12:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200108091207.OAA10720@berta \
    --to=kib@dmi.dk \
    --cc=lastec@dmi.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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.