From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: 2.6.28.2 kernel bug
Date: Sat, 21 Mar 2009 19:50:51 +0100 [thread overview]
Message-ID: <49C5370B.9010500@xs4all.nl> (raw)
In-Reply-To: <20090321184442.GA4177@x200.localdomain>
Alexey Dobriyan wrote:
>> Also the links I posted might point in the direction of a kernel issue?
>
> Do you have ECC memory?
Nope.
Do you?
On the other hand: if it WERE a RAM glitch that caused this, how long
would I have to test for it to appear? (given many months of relative
problemfree uptime and no seemingly permanent damage to RAM, the amount
and speed of RAM, CPU...)
Also: how do we discern between hardware issues and software problems in
such cases as this? (so at least I can understand)
next prev parent reply other threads:[~2009-03-21 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 17:52 2.6.28.2 kernel bug Udo van den Heuvel
2009-03-21 18:20 ` Udo van den Heuvel
2009-03-21 18:31 ` Alexey Dobriyan
2009-03-21 18:30 ` Udo van den Heuvel
2009-03-21 18:44 ` Alexey Dobriyan
2009-03-21 18:50 ` Udo van den Heuvel [this message]
2009-03-21 21:10 ` Hugh Dickins
2009-03-22 5:52 ` Udo van den Heuvel
2009-03-22 13:55 ` Hugh Dickins
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=49C5370B.9010500@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=adobriyan@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.