From: tupeng212 <tupeng212@gmail.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: CPU stucked when xen initializing, why?
Date: Thu, 16 Aug 2012 22:12:26 +0800 [thread overview]
Message-ID: <2012081622122189073014@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1348 bytes --]
Dear all:
I need your help.
--------------------------------------------------------
__start_xen
{
iommu_setup(); /* setup iommu if available */
smp_prepare_cpus(max_cpus);
}
routing patch:
smp_prepare_cpus -> smp_boot_cpus -> do_boot_cpu -> wakeup_secondary_cpu
when BSP "Sending STARTUP #1(num_starts=2)", handling CPU#31, system was stuck, I don't know why.
besides, there are 64 physical CPUs.
wakeup_secondary_cpu
{
for (j = 1; j <= num_starts; j++) {
Dprintk("Sending STARTUP #%d.\n",j); //this printing appeared
apic_read_around(APIC_SPIV);
apic_write(APIC_ESR, 0);
apic_read(APIC_ESR);
Dprintk("After apic_write.\n"); //but this print never come out, and system was stuck
}
}
---------------------------------------------------
1 apic_write/read() contains some lock there? how to check ?
2 BSP CPU 's rip jumped to another place owing to such as an interruption?
the most suspected place I doubt is iommu_setup(), and in this function,
I/O virtualisation enabled
Dom0 mode: Relaxed
but iommu_page_fault never entered after checking log.
3 Can someone teach me a method to analyze Xen's stuck stack, for example
core dump?... this problem happened accidentally, hard to catch its printing.
so if appear, I'd like to analyze it instantly.
Thank you very much!
tupeng212
[-- Attachment #1.2: Type: text/html, Size: 2908 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2012-08-16 14:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2012081622122189073014@gmail.com \
--to=tupeng212@gmail.com \
--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).