From: Ben Twijnstra <bentw@chello.nl>
To: linux-kernel@vger.kernel.org
Subject: Machine Check Exception in 2.6.0-test2
Date: Mon, 28 Jul 2003 23:52:15 +0200 [thread overview]
Message-ID: <200307282352.15775.bentw@chello.nl> (raw)
Hi all,
When running a fairly CPU and thread-hungry application under 2.5.75,
2.6.0-test1 and 2.6.0-test2 I'm getting the following error messages on the
console:
Jul 25 00:16:31 durak kernel: CPU 0: Machine Check Exception: 0000000000000004
Jul 25 00:16:31 durak kernel: Bank 0: b600000000000175 at 0000000025a0cff8
Jul 25 00:16:31 durak kernel: Kernel panic: CPU context corrupt
Once I get this message, one of the threads becomes unkillable yet remains
soaking up CPU cycles.
This does not happen in the 2.4 kernels. How do I go about finding the source
of the problem? The address indicated in the second line indicates that this
happened somewhere in userspace (0x25a0cff8), but since this is a commercial
package I don't have any symbolic info. This last address changes between
runs, so I assume it's a virtual address.
Any ideas welcome.
Best regards,
Ben
reply other threads:[~2003-07-28 21:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200307282352.15775.bentw@chello.nl \
--to=bentw@chello.nl \
--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;
as well as URLs for NNTP newsgroup(s).