From: Dmitri Nikulin <dnikulin@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel bug in file-item.c
Date: Thu, 30 Apr 2009 17:23:14 +1000 [thread overview]
Message-ID: <3a7f57190904300023k411bf55crf527003096884a2c@mail.gmail.com> (raw)
In-Reply-To: <49F8A4AF.3020907@oel.state.nj.us>
On Thu, Apr 30, 2009 at 5:04 AM, Marc R. O'Connor
<mroconnor@oel.state.nj.us> wrote:
>> If you can stomach it, you can get a second opinion from the bootabl=
e
>> windows memory testing iso:
>>
>> =C2=A0 http://oca.microsoft.com/en/windiag.asp
>
>
> It will be hard but I might just try it. Two versions of memtest86+ d=
ie
> in the middle of the scan. Ugh.
Also try memtester in Linux. Boot up as you normally do and give it a
fair chunk of your RAM to run on. Unlike memtest it leaves all the
actual low level stuff to the kernel. Doesn't even need root, let
alone boot. At least then you can thoroughly rule out a memtest86 bug.
--=20
Dmitri Nikulin
Centre for Synchrotron Science
Monash University
Victoria 3800, Australia
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-30 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:39 kernel bug in file-item.c Marc R. O'Connor
2009-04-28 19:23 ` Chris Mason
2009-04-28 19:30 ` Marc R. O'Connor
2009-04-29 16:04 ` Marc R. O'Connor
2009-04-29 17:53 ` Chris Mason
2009-04-29 18:21 ` Marc R. O'Connor
2009-04-29 18:30 ` Chris Mason
2009-04-29 18:38 ` Marc R. O'Connor
2009-04-29 18:40 ` Chris Mason
2009-04-29 18:46 ` Marc R. O'Connor
2009-04-29 18:50 ` Zach Brown
2009-04-29 19:04 ` Marc R. O'Connor
2009-04-30 7:23 ` Dmitri Nikulin [this message]
2009-04-29 19:32 ` Tracy Reed
2009-04-30 9:08 ` Paul Komkoff
2009-04-30 16:54 ` Tracy Reed
2009-05-01 2:13 ` Dmitri Nikulin
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=3a7f57190904300023k411bf55crf527003096884a2c@mail.gmail.com \
--to=dnikulin@gmail.com \
--cc=linux-btrfs@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