From: Andrea Arcangeli <andrea@suse.de>
To: Jure Pecar <pegasus@telemach.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre5aa1 oops via kt266a
Date: Mon, 1 Apr 2002 20:03:09 +0200 [thread overview]
Message-ID: <20020401200309.R1331@dualathlon.random> (raw)
In-Reply-To: <20020401142557.171cb72e.pegasus@telemach.net> <20020401164813.138ad1ae.pegasus@telemach.net>
On Mon, Apr 01, 2002 at 04:48:13PM +0200, Jure Pecar wrote:
>
> Looks like i panicked too early; it looks like the dimm in my board is
> misbehaving. I got another strange oops and sudnely bios deceided to
> recognize only half of it. gotta replace it asap ...
never mind, I just wanted to ask you about the ram, 90% of those
prune_dcache oopses are due bad ram. Thanks,
Andrea
prev parent reply other threads:[~2002-04-01 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 12:25 Jure Pecar
2002-04-01 14:48 ` Jure Pecar
2002-04-01 18:03 ` Andrea Arcangeli [this message]
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=20020401200309.R1331@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pegasus@telemach.net \
/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
all inboxes | Powered by JetHome®