From: Bill Davidsen <davidsen@tmr.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: single bit flip detector.
Date: Tue, 01 Aug 2006 16:15:42 -0400 [thread overview]
Message-ID: <44CFB66E.1080500@tmr.com> (raw)
In-Reply-To: <20060801184451.GP22240@redhat.com>
eventuallyDave Jones wrote:
> In case where we detect a single bit has been flipped, we spew
> the usual slab corruption message, which users instantly think
> is a kernel bug. In a lot of cases, single bit errors are
> down to bad memory, or other hardware failure.
>
> This patch adds an extra line to the slab debug messages
> in those cases, in the hope that users will try memtest before
> they report a bug.
>
> 000: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> Single bit error detected. Possibly bad RAM. Run memtest86.
Given the probability of hardware vs. kernel, you could replace
"possible" with "probable" and not get any argument from me.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-08-01 20:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 18:44 single bit flip detector Dave Jones
2006-08-01 20:15 ` Bill Davidsen [this message]
2006-08-01 22:14 ` Alan Cox
2006-08-01 22:30 ` Dave Jones
2006-08-01 22:36 ` Dave Jones
2006-08-01 23:00 ` Alexey Dobriyan
2006-08-01 23:16 ` Dave Jones
2006-08-01 23:27 ` Dave Jones
2006-08-01 23:28 ` Andreas Schwab
2006-08-01 23:51 ` Dave Jones
2006-08-02 0:16 ` Dave Jones
2006-08-02 6:20 ` Rolf Eike Beer
2006-08-02 7:08 ` Jan Engelhardt
2006-08-06 11:05 ` Geert Uytterhoeven
2006-08-02 15:24 ` Patrick McLean
2006-08-02 16:12 ` Randy.Dunlap
2006-08-04 21:19 ` Andrew Morton
2006-08-04 22:06 ` Dave Jones
2006-08-04 22:25 ` Andrew Morton
2006-08-04 22:28 ` Dave Jones
2006-08-02 7:08 ` Jan Engelhardt
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=44CFB66E.1080500@tmr.com \
--to=davidsen@tmr.com \
--cc=davej@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox