From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] kernel memory allocator got confused?
Date: Fri, 23 Nov 2007 00:09:36 +0100 [thread overview]
Message-ID: <5d375e920711221509t33405b10o48b71f2ff4965b06@mail.gmail.com> (raw)
In-Reply-To: <337456f6a7cc5698b484c52a6f7fe6a1@quintile.net>
I would recommend running memtest first to find out if it is actually
a memory issue. Otherwise you might just mask the issue and think that
moving the memory around
made it go away when it actually is something else but hard to trigger.
If memtest finds errors, then you know with some certainty that there
was no bug.
uriel
On Nov 23, 2007 12:04 AM, Steve Simon <steve@quintile.net> wrote:
> > ...i'm more inclined to suspect memory problems.
>
> Thanks Russ for the very detailed analysis.
>
> I will start by reseating the RAM and if that fails
> I will petition my boss for a new machine (bout time really).
>
> -Steve
>
prev parent reply other threads:[~2007-11-22 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 13:02 Steve Simon
2007-11-21 13:22 ` erik quanstrom
2007-11-22 16:14 ` Russ Cox
2007-11-22 17:20 ` erik quanstrom
2007-11-22 23:04 ` Steve Simon
2007-11-22 23:09 ` Uriel [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=5d375e920711221509t33405b10o48b71f2ff4965b06@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).