From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Luke S Crawford <lsc@prgmr.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board
Date: Fri, 7 May 2010 08:14:11 +0100 [thread overview]
Message-ID: <C8097C53.13746%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <m34oiko570.fsf@luke.xen.prgmr.com>
Try 'no-mce' on xen-4.0 or xen-unstable command line, or 'nomce' on xen-3.4
command line. Looks like MCE support playing up. You probably didn't want
the MCE goop enabled anyway. :-)
-- Keir
On 07/05/2010 02:45, "Luke S Crawford" <lsc@prgmr.com> wrote:
>
> so I get this on bootup right after detecting USB. this is using the
> 2.6.18.8-xen dom0 kernel. I got the same results with the 3.4.3-rc6 xen
> hypervisor.
>
> Ideas on what the problem might be? looking at amd_nonfatal it seems that
> the MCE code is in an impossible state?
>
> (XEN) Xen BUG at amd_nonfatal.c:165
> (XEN) ----[ Xen-3.4.2 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 0
> (XEN) RIP: e008:[<ffff828c801778f9>] mce_amd_work_fn+0x1d9/0x1f0
> (XEN) RFLAGS: 0000000000010246 CONTEXT: hypervisor
> (XEN) rax: 0000000000000ffe rbx: ffff828c8024ff28 rcx: 0000000000000000
> (XEN) rdx: c0080ffe01000000 rsi: 0000000000000413 rdi: 0000000000000000
> (XEN) rbp: 000000025f13f8e0 rsp: ffff828c8024fe60 r8: ffff828c8028f800
> (XEN) r9: 0000000000000000 r10: 0000000000000005 r11: 0000000000000000
> (XEN) r12: 0000000000000000 r13: ffff828c80177720 r14: ffff83081fd7b190
> (XEN) r15: ffff83081fd7b190 cr0: 000000008005003b cr4: 00000000000006f0
> (XEN) cr3: 00000004ca4a6000 cr2: 000000000083c770
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
> (XEN) Xen stack trace from rsp=ffff828c8024fe60:
> (XEN) 0000000000000000 c0080ffe01000000 ffff828c80221180 ffff828c8011a12c
> (XEN) ffff8300dfc2c060 ffff828c80221180 ffff83081fd7b198 ffff828c8011a20d
> (XEN) 000000024ab06880 0000000000000000 ffff828c8024ff28 ffff828c80267900
> (XEN) ffff828c80266900 0000000000000000 ffff828c80221100 ffff828c801185b8
> (XEN) 000000000000e008 ffff828c8024ff28 ffff828c80266900 ffff828c802215b0
> (XEN) 000000025e3b7f20 ffff828c80138fcc 0000000000000000 ffff8300dfafc000
> (XEN) ffff8300dfc2c000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000246
> (XEN) 0000000000000008 00000000ffff8e54 0000000000000054 0000000000000000
> (XEN) ffffffff802053aa 0000000000000001 0000000000000000 0000000000000001
> (XEN) 0000010000000000 ffffffff802053aa 000000000000e033 0000000000000246
> (XEN) ffffffff80511f50 000000000000e02b 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 ffff8300dfafc000
> (XEN) Xen call trace:
> (XEN) [<ffff828c801778f9>] mce_amd_work_fn+0x1d9/0x1f0
> (XEN) [<ffff828c8011a12c>] execute_timer+0x2c/0x50
> (XEN) [<ffff828c8011a20d>] timer_softirq_action+0xbd/0x2e0
> (XEN) [<ffff828c801185b8>] do_softirq+0x58/0x80
> (XEN) [<ffff828c80138fcc>] idle_loop+0x4c/0xa0
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at amd_nonfatal.c:165
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-07 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 1:45 (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board Luke S Crawford
2010-05-07 7:14 ` Keir Fraser [this message]
2010-05-07 21:10 ` Luke S Crawford
2010-05-07 21:45 ` Keir Fraser
2010-05-12 8:10 ` Keir Fraser
2010-05-20 9:13 ` Luke S Crawford
2010-05-20 12:54 ` Keir Fraser
2010-05-20 14:01 ` Christoph Egger
2010-07-15 5:40 ` Luke S Crawford
2010-07-15 7:04 ` Keir Fraser
2010-07-15 8:34 ` Luke S Crawford
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=C8097C53.13746%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=lsc@prgmr.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 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).