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@lists.xensource.com http://lists.xensource.com/xen-devel
i 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@lists.xensource.com http://lists.xensource.com/xen-devel
On 30/5/07 04:35, "Sangmin Lee" <sal008@cs.ucsd.edu> 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?Thanks for the backtrace. I''ll take a look.> And is it okay to adjust STACK_SIZE variable just to pass the test?No! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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@cs.ucsd.edu> 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@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I was enforcing Xen to do assertion check with debug disabled. Now I did with debug enabled but getting same crash. Here is output of ''hg tip'' on my working directory. changeset: 13088:057f7c4dbed1 tag: tip user: Ewan Mellor <ewan@xensource.com> date: Tue Dec 19 12:00:11 2006 +0000 summary: Fix parsing of cpus in the guest configuration file. For me, upgrading is somewhat hard as I''ve working with this revision for a pretty long time and have made much modification on this. Of course I''m testing Xenoprof with the unmodified system. -- Sangmin PS. Here''s new msgs from the crash. (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=y Not tainted ]---- (XEN) CPU: 1 (XEN) EIP: e008:[<ff120f7e>] __bug+0x29/0x47 (XEN) EFLAGS: 00010286 CONTEXT: hypervisor (XEN) eax: 00000000 ebx: 00000028 ecx: 000018ba edx: ff1db3d5 (XEN) esi: ff18476e edi: a7fd01a0 ebp: ff21bf10 esp: ff21bef4 (XEN) cr0: 8005003b cr4: 000026d0 cr3: cb6e6000 cr2: a7f88a70 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff21bef4: (XEN) 00000086 ff186809 ff18476e 00000028 ff1db3ff ff21bfbc ff21bfbc ff21bf30 (XEN) ff16d6fc ff18476e 00000028 00000028 ff18476e ff21bfb4 0000000e ff21bf70 (XEN) ff16e846 ff226100 ff21bfbc ff15142e ff226d84 000000a1 00000000 ff226100 (XEN) ff239704 ff160420 00000000 ff1f6688 ff21bfbc ff21bfbc a7fd01a0 ff21bf90 (XEN) ff16d828 00000001 ff1f6688 ff21bfbc ff226100 00000001 ff21bfbc ff21bfb0 (XEN) ff14034d ff21bfbc 00000001 ff226100 a7f88a88 a7f99ff4 aff571a0 00de402f (XEN) ff16fc25 ff21bfbc a7f99ff4 00000006 00000000 aff571a0 a7fd01a0 aff571c8 (XEN) 00000006 00000006 ff160420 0000e008 00000002 0000007b 0000007b 00000000 (XEN) 00000033 00000001 ff226100 (XEN) Xen call trace: (XEN) [<ff120f7e>] __bug+0x29/0x47 (XEN) [<ff16d6fc>] xenoprofile_get_mode+0x59/0x159 (XEN) [<ff16e846>] ppro_check_ctrs+0x3a/0xc5 (XEN) [<ff16d828>] nmi_callback+0x2c/0x81 (XEN) [<ff14034d>] do_nmi+0x36/0x8b (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 1: (XEN) BUG at xenoprof.c:40 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Keir Fraser wrote:> 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@cs.ucsd.edu> 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@lists.xensource.com >> http://lists.xensource.com/xen-devel >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 30/5/07 22:55, "Sangmin Lee" <sal008@cs.ucsd.edu> wrote:> For me, upgrading is somewhat hard as I''ve working with this revision > for a pretty long time and have made much modification on this. Of > course I''m testing Xenoprof with the unmodified system.That''s too bad. You''re running a 6-month old unstable release. You need to upgrade, or you''ll need to backport bug fixes in the current xenoprofile code back to your tree. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel