From: ZhouPeng <zpengxen@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
stephen.spector@citrix.com, keir.fraser@eu.citrix.com
Cc: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: Re: Panic on cpu0
Date: Thu, 16 Dec 2010 17:30:24 +0800 [thread overview]
Message-ID: <AANLkTi=mLQzJkJ08DxMHDXWrLxyH++BymrTNPP-F9zba@mail.gmail.com> (raw)
In-Reply-To: <20101216075912.GG2754@reaktio.net>
[-- Attachment #1.1: Type: text/plain, Size: 2155 bytes --]
The err msg appears in
void *map_domain_page(unsigned long mfn)
BUG_ON(idx >= MAPCACHE_ENTRIES);
printk idx is 1024 and BUG_ON is called.
I print Xen call trace msg:
[<ffcd3c2>] map_domain_page+0x1a2/0x230
[<ff1cd718>] unmap_domain_page+0x148/0x160
addr_to_dma_page_maddr+0x1f6/0x250
__find_next_zero_bit+0x80/0x90
intel_iommu_map_page+0x14a/0x250
domain_context_mapping+0x14a/0x250
rmrr_identity_mapping+0xb7/0x120
intel_iommu_dom0_init+0x143/0x1eb
construct_dom0+0x138f/0x16b0
__start_xen+0x109a/0x1680
e820nf+0x0/0x4
__high_start+0x58/0x5a
2010/12/16 Pasi Kärkkäinen <pasik@iki.fi>
> On Thu, Dec 16, 2010 at 03:41:17PM +0800, ZhouPeng wrote:
> > (XEN) Panic on CPU 0:
> > (XEN) Xen BUG at domain_page.c:102
> >
> > Any solutions?
> >
>
> You need to post the full boot log, including all output from both Xen and
> dom0 Linux.
> See: http://wiki.xen.org/xenwiki/XenSerialConsole
>
> -- Pasi
>
> > 2010/12/16 ZhouPeng <[1]zpengxen@gmail.com>
> >
> > Hi all,
> >
> > I build xen4.1 from the tarbll (with kernel 2.6.32.26 downloaded by
> > default) on fedora8.
> >
> > After installing, I get the err msg on startup:
> >
> > (XEN) Panic on CPU 0:
> > (XEN) Xen BUG at domain_page.c:102
> >
> > 5 seconds later, the machine reboot.
> >
> > How to deal with this problem.
> >
> > Thanks,
> > --
> > Zhou Peng
> > My daily E-Mail: [2]ailvpeng25@gmail.com
> >
> > --
> > Zhou Peng
> > My daily E-Mail: [3]ailvpeng25@gmail.com
> >
> > References
> >
> > Visible links
> > 1. mailto:zpengxen@gmail.com
> > 2. mailto:ailvpeng25@gmail.com
> > 3. mailto:ailvpeng25@gmail.com
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>
--
Zhou Peng
My daily E-Mail: ailvpeng25@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 3358 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-12-16 9:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 6:40 Panic on cpu0 ZhouPeng
2010-12-16 7:41 ` ZhouPeng
2010-12-16 7:59 ` Pasi Kärkkäinen
2010-12-16 9:30 ` ZhouPeng [this message]
2010-12-16 9:41 ` ZhouPeng
2010-12-16 10:36 ` Keir Fraser
2010-12-16 11:24 ` ZhouPeng
2010-12-16 11:43 ` Pasi Kärkkäinen
2010-12-16 15:25 ` ZhouPeng
2010-12-16 15:34 ` Pasi Kärkkäinen
2010-12-16 15:46 ` Jan Beulich
2011-01-05 13:37 ` Stefano Stabellini
2011-01-05 13:57 ` Ian Campbell
2011-01-07 7:24 ` ZhouPeng
2011-01-07 9:00 ` Ian Campbell
2011-01-07 9:24 ` Pasi Kärkkäinen
2010-12-16 11:47 ` Keir Fraser
2010-12-16 11:52 ` Pasi Kärkkäinen
2010-12-16 15:20 ` ZhouPeng
2010-12-16 11:47 ` Jan Beulich
2010-12-16 15:18 ` ZhouPeng
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='AANLkTi=mLQzJkJ08DxMHDXWrLxyH++BymrTNPP-F9zba@mail.gmail.com' \
--to=zpengxen@gmail.com \
--cc=keir.fraser@eu.citrix.com \
--cc=pasik@iki.fi \
--cc=stephen.spector@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 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).