From: David King <dave@daveking.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pls help me understand this MCE
Date: Thu, 11 Aug 2005 14:02:20 -0400 [thread overview]
Message-ID: <42FB92AC.9080009@daveking.com> (raw)
In-Reply-To: <42FB5C4B.2010205@vc.cvut.cz>
Petr Vandrovec wrote:
> Try dumping *all* MCE values, as well as a call stack. Even although
> MCE is tagged as processor context corrupt, there is rather big chance
> that stack trace will point back to the instruction which caused MCE
> (it always did in my case), especially if it is single processor system.
> Then you'll at least know which subsystem/driver did that.
Ok, here's everything I got from the serial console when the error
occurred. I don't have a clue how to interpret this stuff so I'd be
eternally grateful if someone out there can help. Or, if I
misunderstood what you were telling me I ought to do, then explaining
the process a bit more would be appreciated too.
CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f
TSC 7cba18189a
Kernel panic - not syncing: Machine check
Call Trace: <#MC> <ffffffff8013a4b5>{panic+133}
<ffffffff80116d48>{print_mce+136}
<ffffffff80116e19>{mce_panic+137} <ffffffff801173f2>{do_machine_check+754}
<ffffffff80110147>{machine_check+127}
<ffffffff80113dec>{timer_interrupt+444}
<EOE> <IRQ> <ffffffff80146b50>{process_timeout+0}
<ffffffff801704dc>{handle_IRQ_event+44} <ffffffff801706ed>{__do_IRQ+477}
<ffffffff801120b8>{do_IRQ+72} <ffffffff8010f6c3>{ret_from_intr+0}
<EOI> <ffffffff8010d230>{default_idle+0} <ffffffff8010d252>{default_idle+34}
<ffffffff8010d291>{cpu_idle+49} <ffffffff8057e7e5>{start_kernel+469}
<ffffffff8057e1f4>{_sinittext+500}
Thanks
--
David King
dave@daveking.com
prev parent reply other threads:[~2005-08-11 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 13:49 Pls help me understand this MCE David King
2005-08-11 14:10 ` Petr Vandrovec
2005-08-11 18:02 ` David King [this message]
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=42FB92AC.9080009@daveking.com \
--to=dave@daveking.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.