mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: linux-kernel@vger.kernel.org
Subject: /dev/mem and highmem
Date: Mon, 3 Mar 2003 17:00:50 +0100	[thread overview]
Message-ID: <20030303160050.GA17182@clipper.ens.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Is there any hope to have access to the highmem through /dev/mem, or a
similar device? Or did I miss an already existing method?

Rationale:

These days, bad RAM seems to become dramatically frequent. We have here
a PC with a few bad bits (switching to ECC is in project), but memtest86
did not find them. Recently, sshd started to segfault. Using cmp -lb
with an uncorrupted version we found the bad bit in the file, and then
looked for it in the phyical memory with `xxd /dev/mem | grep'. We found
it, disabled the area using mem= boot parameter.

Now this PC has a crontab that will write pseudo-random data in the
disabled area, and later read it back and compare it with the original
to find all bad bits.

Then I have another PC with bad RAM, I also discovered a file affected,
and tried the same method. Unfortunately the grep failed. The reason is
likely to be that the file was in highmem.

PS: please Cc me the answers.

Regards,

-- 
  Nicolas George

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

             reply	other threads:[~2003-03-03 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 16:00 Nicolas George [this message]
2003-03-06 16:22 ` Nicolas George

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=20030303160050.GA17182@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --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

all inboxes | Powered by JetHome®