From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Re: Massive repository corruptions
Date: Thu, 5 Aug 2010 22:10:27 +0200 [thread overview]
Message-ID: <20100805201026.GC2630@nibiru.local> (raw)
In-Reply-To: <AANLkTikFypx3e-=+8J2925A++_jY-aJCDYHHw6dry5s6@mail.gmail.com>
* Jussi Sirpoma <jussi.sirpoma@gmail.com> wrote:
> I once had a difficult to trace memory problem on a box when one of the last
> memory banks
> was bad. It was only used during high load situations while compiling the
> kernel or something
> similar. The problem was finally pinpointed by memtest86 which stresses all
> memory.
hmm, you know some way to do a memory-stresstest w/o rebooting ?
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2010-08-05 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 1:56 Massive repository corruptions Enrico Weigelt
2010-07-13 3:23 ` Avery Pennarun
2010-07-13 5:03 ` Enrico Weigelt
2010-07-13 5:31 ` Enrico Weigelt
2010-07-13 6:46 ` Enrico Weigelt
2010-07-13 10:17 ` Valeo de Vries
2010-07-13 9:40 ` Avery Pennarun
2010-07-13 10:22 ` Enrico Weigelt
2010-07-13 17:59 ` Avery Pennarun
2010-07-14 13:22 ` Enrico Weigelt
2010-08-05 17:31 ` Enrico Weigelt
[not found] ` <AANLkTikFypx3e-=+8J2925A++_jY-aJCDYHHw6dry5s6@mail.gmail.com>
2010-08-05 20:10 ` Enrico Weigelt [this message]
[not found] ` <AANLkTi=5HVQ2kSEt7O+OXdMRtvy8amufpFKgRpj2VLEy@mail.gmail.com>
2010-08-05 20:42 ` Enrico Weigelt
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=20100805201026.GC2630@nibiru.local \
--to=weigelt@metux.de \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).