Re: [Xen-devel] E5606 with no HVM; Assertion 'i == 1' failed at p2m-ept.c:524

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 16.08.12 at 10:48, "Mark van Dijk" <lists+xen@xxxxxxxxxxxxxx> wrote:
> On Thu, 16 Aug 2012 09:11:50 +0100
> "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
> 
>> >>> On 15.08.12 at 22:39, Mark van Dijk <lists+xen@xxxxxxxxxxxxxx>
>> >>> wrote:
>> > (XEN) Xen call trace:
>> > (XEN)    [<ffff82c4801e1be9>] ept_get_entry+0x13a/0x28f
>> > (XEN)    [<ffff82c4801da274>] __get_gfn_type_access+0x175/0x256
>> > (XEN)    [<ffff82c4801b5a55>] hvm_hap_nested_page_fault+0x133/0x422
>> > (XEN)    [<ffff82c4801d3c8e>] vmx_vmexit_handler+0x136b/0x1614
>> > 
>> > The entire log from boot to crash can be viewed at the following
>> > link: http://pastebin.com/5wcH7GWR 
>> 
>> Unfortunately quite a few of the registers contain values that
>> could sensibly be "i". Could you either disassemble the
>> instructions around the place yourself to find out which one it
>> is, or make the xen-syms file corresponding to this run available?
> 
> Hi Jan, I'm not capable to disassemble anything because my experience
> with that is zero. So it's probably easier to give you the xen-syms
> file, I posted it to a pastebin with a little detour:
> 
> curl http://sprunge.us/cGeL | openssl enc -a -d | \
>  xz -d > xen-syms-4.2.0-rc3-pre

Thanks. That confirms that "i" (in r12d) is indeed 2. So there are
good chances that the patch I sent earlier will help. Please let us
know.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel