All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: machine check report on HVM startup
Date: Wed, 13 Aug 2008 13:48:05 +0200	[thread overview]
Message-ID: <200808131348.05596.Christoph.Egger@amd.com> (raw)


Hi,

When I launch  memtest as HVM guest, then Xen sends tons of VIRQ_MCA events
to the Dom0, although there occured NO correctable machine check errors.
When the Dom0 tries to fetch the error telemetry, then the

BUG_ON(mc_data.fetch_idx > mc_data.error_idx); in x86_mcinfo_getfetchptr()
in xen/arch/x86/cpu/mcheck/mce.c is hit. (x86_mcinfo_getfetchptr() only works
if actually real error occured which is not the case.)

This looks to me, there's a non-public event channel using the same number
as VIRQ_MCA which fires when  launching memtest as HVM guest.

Christoph


-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

             reply	other threads:[~2008-08-13 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 11:48 Christoph Egger [this message]
2008-08-13 12:27 ` machine check report on HVM startup Keir Fraser
2008-08-13 12:36   ` Keir Fraser
2008-08-13 12:40     ` Christoph Egger
2008-08-13 12:48       ` Keir Fraser
2008-08-13 13:17         ` Christoph Egger
2008-08-13 13:22           ` Keir Fraser
2008-08-13 13:17         ` Keir Fraser

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=200808131348.05596.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.