mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Jan Kara <jack@suse.cz>, Dan Carpenter <dan.carpenter@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)
Date: Sun, 14 Oct 2012 13:27:14 +0100	[thread overview]
Message-ID: <20121014132714.7a869932@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <507A8189.7020402@ahsoftware.de>

> The people which are responsible that the chips for "consumer"-HW and 
> laptops got their (already included) ECC functionality disabled should 
> get hit with Googles (now 3y old) study on that topic all the day. 
> Leaving customers in danger by not offering them at least the 
> possibility to use ECC RAM is just stupid.

For the amount of RAM in devices now days then yes probably a good idea.
Adding to the problem is that there is an active market in fake brandname
DIMMs.

Alan

  reply	other threads:[~2012-10-14 12:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 11:34 Alexander Holler
2012-09-25 11:02 ` Dan Carpenter
2012-09-27 11:45   ` Alexander Holler
2012-09-27 15:12     ` Jan Kara
2012-09-27 15:46       ` Alexander Holler
2012-09-27 16:20         ` Alexander Holler
2012-09-27 18:01           ` Alexander Holler
2012-09-27 18:12             ` Alexander Holler
2012-09-27 20:05             ` Jan Kara
2012-09-28  8:09               ` Alexander Holler
2012-09-27 20:03         ` Jan Kara
2012-09-29 19:07           ` Alexander Holler
2012-10-01  9:10             ` Jan Kara
2012-10-01  9:21               ` Alexander Holler
2012-10-02  9:30                 ` Alexander Holler
2012-10-14  9:10                   ` Alexander Holler
2012-10-14 12:27                     ` Alan Cox [this message]
2012-10-15  8:46                       ` Alexander Holler

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=20121014132714.7a869932@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dan.carpenter@oracle.com \
    --cc=holler@ahsoftware.de \
    --cc=jack@suse.cz \
    --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®