From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>, Keir Fraser <keir@xen.org>
Subject: ERST problems
Date: Thu, 21 Mar 2013 23:22:06 +0000 [thread overview]
Message-ID: <514B961E.8010202@citrix.com> (raw)
Hello,
When debugging ERST boot time hangs, the following debugging proved
interesting
>From a Dell Poweredge 2950 with latest BIOS:
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) erst_init()
(XEN) Found ERST
(XEN) ERST is good
(XEN) About to exec ctx_init()
(XEN) About to exec pre map
(XEN) Starting apei_exec_for_each_entry(). ctx->entries = 15
(XEN) .. i = 0, entry = 0xffff82c3ffd7ab48, ins = 0x3
(XEN) .. i = 1, entry = 0xffff82c3ffd7ab68, ins = 0x3
(XEN) .. i = 2, entry = 0xffff82c3ffd7ab88, ins = 0x3
(XEN) .. i = 3, entry = 0xffff82c3ffd7aba8, ins = 0x3
(XEN) .. i = 4, entry = 0xffff82c3ffd7abc8, ins = 0x2
(XEN) .. i = 5, entry = 0xffff82c3ffd7abe8, ins = 0x3
(XEN) .. i = 6, entry = 0xffff82c3ffd7ac08, ins = 0x3
(XEN) .. i = 7, entry = 0xffff82c3ffd7ac28, ins = 0x3
(XEN) .. i = 8, entry = 0xffff82c3ffd7ac48, ins = 0x1
(XEN) .. i = 9, entry = 0xffff82c3ffd7ac68, ins = 0x0
(XEN) .. i = 10, entry = 0xffff82c3ffd7ac88, ins = 0x0
(XEN) .. i = 11, entry = 0xffff82c3ffd7aca8, ins = 0x2
(XEN) .. i = 12, entry = 0xffff82c3ffd7acc8, ins = 0x0
(XEN) .. i = 13, entry = 0xffff82c3ffd7ace8, ins = 0x3
(XEN) .. i = 14, entry = 0xffff82c3ffd7ad08, ins = 0x3
(XEN) About to get range
(XEN) in erst_get_erange()
(XEN) range->base = 0xffff83007fb4f0a0
(XEN) range->size = 0xffff83007fb4f0a0
(XEN) range->attr = 0x7fb4f0a0
(XEN) About to pre map (0xffff83007fb4f0a0, 0xffff83007fb4f0a0)
(XEN) Error -12, about to unmap gars
(XEN) Starting apei_exec_for_each_entry(). ctx->entries = 15
(XEN) .. i = 0, entry = 0xffff82c3ffd7ab48, ins = 0x3
(XEN) apei_post_unmap_gar(0xffff82c3ffd7ab4c)... . aok
(XEN) .. i = 1, entry = 0xffff82c3ffd7ab68, ins = 0x3
(XEN) apei_post_unmap_gar(0xffff82c3ffd7ab6c)... . aok
(XEN) .. i = 2, entry = 0xffff82c3ffd7ab88, ins = 0x3
(XEN) apei_post_unmap_gar(0xffff82c3ffd7ab8c)... .
The hang at this point turns out to be trivial mis-locking issue, and I
have submitted a patch to fix it.
However, this debugging shows that erst_get_erange() is clearly
returning junk, causing apei_pre_map() to fail.
While in this case it is easy to identify the junk size parameter as it
is far greater than the system RAM (32G), I am not sure this is
necessarily the best approach to try and validate the information. Is
there anything else we could sensibly do?
At the very least, erst_init() should not silently ignore its failures.
~Andrew
next reply other threads:[~2013-03-21 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 23:22 Andrew Cooper [this message]
2013-03-21 23:46 ` ERST problems Andrew Cooper
2013-03-22 9:07 ` Jan Beulich
2013-03-22 9:14 ` [PATCH] ACPI, APEI: Add apei_exec_run_optional Jan Beulich
2013-03-22 11:27 ` Andrew Cooper
2013-03-22 11:45 ` Jan Beulich
2013-03-22 11:54 ` Andrew Cooper
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=514B961E.8010202@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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).