From: "André Dahlqvist" <andre.dahlqvist@telia.com>
To: linux-kernel@vger.kernel.org
Subject: Re: random errors with bzip2
Date: Tue, 19 Jun 2001 18:11:48 +0200 [thread overview]
Message-ID: <20010619181148.A24734@telia.com> (raw)
In-Reply-To: <lxiths7aqf.fsf@pixie.isr.ist.utl.pt>
In-Reply-To: <lxiths7aqf.fsf@pixie.isr.ist.utl.pt>
Rodrigo Ventura <yoda@isr.ist.utl.pt> wrote:
> - it could be a memory problem, but if it were, lots of kernel
> oops were expected, right?
This certainly sounds like a memory problem. I experienced almost the same
behaviour with a box some years ago, and it turned out to be memory. The
kernel didn't oops, and I actually had to run several kernel compiles at
the same time to have gcc die.
Try memtest86 on the suspect box.
--
André Dahlqvist <andre.dahlqvist@telia.com>
next prev parent reply other threads:[~2001-06-19 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 15:25 random errors with bzip2 Rodrigo Ventura
2001-06-19 16:11 ` André Dahlqvist [this message]
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=20010619181148.A24734@telia.com \
--to=andre.dahlqvist@telia.com \
--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