From: Forest Bond <forest@alittletooquiet.net>
To: kexec@lists.infradead.org
Cc: Chris Hovious <chris.hovious@logicsupply.com>
Subject: kexec & memtest86+: inconsistent memory errors
Date: Tue, 7 Oct 2008 14:23:50 -0400 [thread overview]
Message-ID: <20081007182350.GD13130@storm.local.network> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1010 bytes --]
Hi,
We've been using kexec to drop into memtest86+ for a few years now. We run
memtest86+ from within our Linux-based hardware test suite. This has always
worked quite well. It was painful to get running at first (kexec was still
young then and wasn't included with our distribution's kernel), but is very easy
to use now.
Unfortunately, though, we've hit a new snag with our latest platform version.
This is based on Ubuntu 8.04.
Specific software version info:
kernel version 2.6.24-19-generic
kexec-tools-testing 20070330 released 30th March 2007
memtest86+ version 2.01
The problem is that memtest86+ reports numerous memory errors when booted via
kexec, booting directly into memtest86+ does not turn up these errors.
I suspect a device is getting mapped into memory and not deallocated prior to
kexec execution (but I may be putting my ignorance on display).
Any ideas?
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2008-10-07 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 18:23 Forest Bond [this message]
2008-10-28 17:31 ` kexec & memtest86+: inconsistent memory errors Forest Bond
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=20081007182350.GD13130@storm.local.network \
--to=forest@alittletooquiet.net \
--cc=chris.hovious@logicsupply.com \
--cc=kexec@lists.infradead.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