Re: [Xen-devel] Xenoprof Assertion fails

[Keir Fraser <keir@xxxxxxxxxxxxx>]

How old is your xen-unstable? And how did you build it?

 1. It appears to have assertions compiled in, yet it's not a debug build
(debug=n). This is weird.
 2. You have the function __bug() on your backtrace. Current xen-unstable
does not use the __bug() function.

You probably need to upgrade and do a clean build.

 -- Keir

On 30/5/07 04:35, "Sangmin Lee" <sal008@xxxxxxxxxxx> wrote:

> Hi all,
> I'm trying to run Xenoprofile but I get crashes when I start profiling.
> 
> I'm using revision 13088 and running one HVM guest.
> Does anyone know about this?
> And is it okay to adjust STACK_SIZE variable just to pass the test?
> 
> Thanks,
> Sangmin
> 
> The following is the msgs from console.
> 
> (XEN) Assertion 'diff < STACK_SIZE' failed, line 40, file xenoprof.c
> (XEN) BUG at xenoprof.c:40
> (XEN) ----[ Xen-3.0-unstable  x86_32  debug=n  Not tainted ]----
> (XEN) CPU:    1
> (XEN) EIP:    e008:[<ff12bfd8>] __bug+0x28/0x50
> (XEN) EFLAGS: 00010282   CONTEXT: hypervisor
> (XEN) eax: 00000000   ebx: 00000028   ecx: 0000000a   edx: 00000000
> (XEN) esi: ff19034c   edi: 00000000   ebp: ffbe7fb4   esp: ffbe7ef4
> (XEN) cr0: 8005003b   cr4: 000026d0   cr3: 71d4a000   cr2: 08061a5c
> (XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
> (XEN) Xen stack trace from esp=ffbe7ef4:
> (XEN)    00000082 ff192e2f ff19034c 00000028 ffbe7f28 ff301eff ff19db05
> 00000028
> (XEN)    ff1783be ff19034c 00000028 00000028 ff19034c 00000001 00000000
> ffbe7fbc
> (XEN)    ff1796ae ff379180 ffbe7fbc ff15b82d ff379e04 ff1cb6e4 ffffffb5
> 00000001
> (XEN)    ff379180 ff169850 00000000 ff31d5a8 ffbe7fbc ffbe7fbc 00000000
> 00000000
> (XEN)    ff17846d 00000001 ff31d5a8 ffbe7fbc ff379180 00000031 00000001
> ffbe7fbc
> (XEN)    ff147696 ffbe7fbc 00000001 ff379180 00eaf208 05eb29ef b02fdfa0
> 00000000
> (XEN)    ff17aaf1 ffbe7fbc b02fdfa0 00000000 00000f9e 00000000 00000000
> 00000000
> (XEN)    b02b4d0c b02b4d0c ff169850 0000e008 00000002 0000007b 0000007b
> 00000000
> (XEN)    00000033 00000001 ff379180
> (XEN) Xen call trace:
> (XEN)    [<ff12bfd8>] __bug+0x28/0x50
> (XEN)    [<ff1783be>] xenoprofile_get_mode+0xce/0x150
> (XEN)    [<ff1796ae>] ppro_check_ctrs+0x4e/0xe0
> (XEN)    [<ff15b82d>] cpu_get_apic_interrupt+0x2d/0x80
> (XEN)    [<ff169850>] vmx_asm_vmexit_handler+0x0/0x30
> (XEN)    [<ff17846d>] nmi_callback+0x2d/0x90
> (XEN)    [<ff147696>] do_nmi+0x36/0x110
> (XEN)    [<ff17aaf1>] continue_nmi+0x11/0x19
> (XEN)    [<ff169850>] vmx_asm_vmexit_handler+0x0/0x30
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 1:
> (XEN) BUG at xenoprof.c:40
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel