From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-kernel@vger.kernel.org
Subject: Machine check exception with a kernel dependency
Date: Wed, 13 Feb 2008 17:25:28 +0100 [thread overview]
Message-ID: <20080213162528.GA32635@janus> (raw)
On at least two Dell optiplex 755 systems with a Core 2 Duo I get
Feb 13 15:14:01 inari CPU 1: Machine Check Exception: 0000000000000004
Feb 13 15:14:01 inari CPU 0: Machine Check Exception: 0000000000000005
Feb 13 15:14:01 inari Bank 0: b200004000000800
Feb 13 15:14:01 inari Bank 5: b200221024080400
2.6.22.10 shows the problem, 2.6.24.2 ditto but I'm unable to reproduce
it with 2.6.24-rc8. BIOS upgrade didn't help. Removing all PCI[e] cards
didn't help either.
Does it make sense to try to pinpoint the problem to a particular
changeset (using git bisect I guess but I've never used it) or is the
hardware just broken?
--
Frank
next reply other threads:[~2008-02-13 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 16:25 Frank van Maarseveen [this message]
2008-02-14 14:54 ` 2.6.24 sysprof induced MCE on Core 2 Duo (was: Machine check exception with a kernel dependency) Frank van Maarseveen
2008-02-15 13:22 ` Machine check exception with a kernel dependency Alan Cox
2008-02-15 14:50 ` Frank van Maarseveen
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=20080213162528.GA32635@janus \
--to=frankvm@frankvm.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