From: Kai Militzer <km@westend.com>
To: linux-kernel@vger.kernel.org
Cc: Kai Militzer <km@westend.com>
Subject: Re: Where do the "Machine Check Exceptions" come from? [update]
Date: 02 Feb 2004 14:51:32 +0100 [thread overview]
Message-ID: <1075729900.777.40.camel@bart> (raw)
In-Reply-To: <1075370497.775.89.camel@bart>
Hello everyone!
I have an update on the reproduction of the strange kernel oopses on an
2.4.24 kernel.
> It all started, that the machine crashed in two-day-intervalls with the
> following message in log:
> Jan 6 22:39:01 CPU 0: Machine Check Exception: 0000000000000004
> Jan 6 22:39:01 Bank 4: b200000000040151
> Jan 6 22:39:01 Kernel panic: CPU context corrupt
That's the message, that always appears.
We then tested around as described in my original mail.
> So there must be something else. Next step was to take the config from
> the 2.4.19 kernel and do a "make oldconfig" with the 2.4.24. The system
> is now running for two days without a crash. So it must be something
> that has changed between the two configs.
The kernel ran for four days without crashing. So I tried to activate
some options, that were activeted in the crashing kernel.
I started with this option, just by a foresought.
> < CONFIG_DEBUG_STACKOVERFLOW=y
> ---
> > # CONFIG_DEBUG_STACKOVERFLOW is not set
It was not set in the kernel running for four days, but in the one,
crashing. After I activated it (means: CONFIG_DEBUG_STACKOVERFLOW=y),
compiled the kernel and let it run under work for the weekend (starting
on friday). This morning (monday) it crashed. So I would say, it was the
CONFIG_DEBUG_STACKOVERFLOW.
Does anyone have an idea, why this options makes the kernel crash?
Shouldn't this option prevent the kernel from crashing?
If more information is needed (i.e. full kernel config, hardware specs,
etc.) please let me know.
Regards
Kai
--
Kai Militzer WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Lütticher Straße 10 Tel 0241/701333-11
km@westend.com D-52064 Aachen Fax 0241/911879
next prev parent reply other threads:[~2004-02-02 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 10:01 Where do the "Machine Check Exceptions" come from? Kai Militzer
2004-02-02 13:51 ` Kai Militzer [this message]
2004-02-08 12:13 ` Re[3]: 2.6.2 Compile Failure - Redhat 7.3 Distro Nick Warne
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=1075729900.777.40.camel@bart \
--to=km@westend.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