public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Ventura <yoda@isr.ist.utl.pt>
To: linux-kernel@vger.kernel.org
Subject: random errors with bzip2
Date: 19 Jun 2001 16:25:28 +0100	[thread overview]
Message-ID: <lxiths7aqf.fsf@pixie.isr.ist.utl.pt> (raw)


        Hi. Let me first apologize if this message is at the wrong
mailing list, but in fact I haven't the faintest idea to where shall I
send this.

        Randomly bzip2 gives an crc error when checking a big bz2
file, e.g. linux-2.4.5.tar.bz2 (20M), in a particular machine (asus
a7v, athlon@1.2G, 256M). The same file (with the same md5sum, NFS file
system) gives no problem whatsoever on other machines. On the asus
machine, sometimes the file is checked ok, other times it fails (crc
error). When several bzip2 processes are launched at the same time for
the same file, some of them fail, others return ok. These have been my
latest observations:

        - avoiding shared IRQs (by moving PCI cards in different
slots) seems to reduce probability of error;

        - fresh reboot seems to solve the problem, but after some
hours of uptime, it comes again;

        - all machines are using 2.4.6-pre3, the file is local to the
asus machine but NFS for the others. The local filesystem is
*ReiserFS*;

        - bzip2 executable is ok (as far as md5sum);

        - it could be a memory problem, but if it were, lots of kernel
oops were expected, right?

        - could it be a process pre-emption problem? (FPU?) the kernel
is compiled for generic i586 (to be shared by several machines);

        - could it be a shared IRQ problem? I've been experiencing
several problems (freeze) related with IRQ sharing on asus boards, but
I'm not totally sure about this;

        - I've read some posts about file shifting, can it cause these
kinds of bzip problems?

        Cheers,

-- 

*** Rodrigo Martins de Matos Ventura <yoda@isr.ist.utl.pt>
***  Web page: http://www.isr.ist.utl.pt/~yoda
***   Teaching Assistant and PhD Student at ISR:
***    Instituto de Sistemas e Robotica, Polo de Lisboa
***     Instituto Superior Tecnico, Lisboa, PORTUGAL
*** PGP fingerprint = 0119 AD13 9EEE 264A 3F10  31D3 89B3 C6C4 60C6 4585

             reply	other threads:[~2001-06-19 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19 15:25 Rodrigo Ventura [this message]
2001-06-19 16:11 ` random errors with bzip2 André Dahlqvist
2001-06-20  7:27   ` Ville Herva

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=lxiths7aqf.fsf@pixie.isr.ist.utl.pt \
    --to=yoda@isr.ist.utl.pt \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox