similar to: BUG: soft lockup - CPU#0 stuck for 61s!

Config.mk | 1 + tools/Makefile | 1 + tools/tests/Makefile | 20 ++++++++++++++++++++ 3 files changed, 22 insertions(+), 0 deletions(-) Build tests as part of the tools build. It is enabled with CONFIG_TESTS in Config.mk Currently disabled build of tests/regressions and tests/xen-access (in 32 bit mode) as they fail. Signed-off-by: Andres Lagar-Cavilla

reassign 646917 xen thanks -- .''`. Sell Crazy Someplace Else. We're all stocked up here : :' : `. `' `- Proudly running Debian GNU/Linux

There has been some progress, but still no joy. Definitely not intended for inclusion at this point. Tim, Wei, I added a Xen command line toggle to disable IOMMU and P2M table sharing. Tim, I verified that changes to p2m-pt.c don''t break shadow mode (64bit hypervisor and Win 7 guest). Hongkaixing, I incorporated your suggestion in patch 2, so I should add your Signed-off-by eventually.

ging_prep ensures that an mfn is backing the paged-out gfn, and transitions to the next state in the paging state machine for this page. Foreign mappings of the gfn will now succeed. This is the key idea, as it allows the pager to now map the gfn and fill in its contents. Unfortunately, it also allows any other foreign mapper to map the gfn and read its contents. This is particularly dangerous

I ran a bisect to find out when Windows XP 32 bit becomes unusably slow. And I found the changeset that caused it. ========== The problem: ========== Windows 8 64 bit and 32 bit run fast and fine in the newest xen versions. Windows XP 32 bit runs unusably slow in anything new that I built from xen-unstable, but runs fast in 4.1.2 and 4.1.3 stable. While it is running slow, "xm top" or

This is a cherry pick of two patches that add support for guest paged out frames in the XCP 2.6.32 dom0 patch queue. First patch propagates the ENOENT returned by the hypervisor in the case of a paged out page, all the way up the call chain to the MMAPBATCH_V2 ioctl. The ioctl is mainly used to harvest those return values and retry. The second patch adds retry loops to all backend grant

what does it mean? i never seen that before xen4 on debian squeeze 2.6.32-5-xen-amd64 [22077.208077] BUG: soft lockup - CPU#7 stuck for 61s! [udisks-dm-expor:11772] [22077.208139] Modules linked in: ext4 jbd2 crc16 xfs exportfs xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev bridge stp ip6table_filter ip6_tables iptable_filter ip_tables x_tables xen_evtchn xenfs fuse

This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, calls to hvm_memory_event_cr3 and hvm_memory_event_cr4 were lost. These functions were originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in

The patch ''mem_event: use wait queue when ring is full'' I just sent out makes use of the waitqueue feature. There are two issues I get with the change applied: I think I got the logic right, and in my testing vcpu->pause_count drops to zero in p2m_mem_paging_resume(). But for some reason the vcpu does not make progress after the first wakeup. In my debugging there is one

flight 13383 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13383/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 16 guest-start fail REGR. vs. 13379 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 12

Hi everybody, i hope that i'm on the right mailing list. I'm having some trouble with xfs and xen. We are running the newest xenserver version with ha on dell servers and a dell equalogic. I set up a fileserver (debian lenny 2.6.29-xs5.5.0.17) with one ext3 partiton for the os and one xfs partition for the data. Two webserver are using this fileserver with nfs. Now i run the second

Dear All, I selected CentOS5 in my works and installed them in two DELL PowerEdge1950. However, a trouble blocked me during the machines run after two days. The machines crashed and the syslog said it got the following messages: ------------------ part dump of /var/log/messages ---------------------- ..... Jul 25 02:15:02 vega2008 kernel: [<c045bc58>] ? exit_mmap+0x93/0xc9 Jul 25

Ian, this one is special just for you. I''m sending it as an attachment because my email client will mangle it. This patch will remove the cmake dependency from xen prior to autoconf stubdom This patch applies ontop of [VTPM v7 3/8] vtpm/vtpmmgr and required libs to stubdom/Makefile You can apply it to your tree by doing the following: git rebase -i <VTPM v7 3/8 revision>

about VIRQ &amp; PIRQ what is VIRQ  ?How VIRQ is different from PIRQ ?How VIRQ &amp; PIRQ are related each other ? DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any

> I''m not mad keen on propagating these sorts of asm atomic operations throughout > our code base. Other options would be: gcc has atomic builtins to do this kind of work. I don''t know about arm, but they do the job in x86 http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Atomic-Builtins.html so atomic_inc(val) -> __sync_fetch_and_add(val, 1) and likewise for dec/sub Andres

flight 13439 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13439/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl-qemuu-winxpsp3 9 guest-localmigrate fail REGR. vs. 13379 test-amd64-amd64-xl-qemuu-win7-amd64 9 guest-localmigrate fail REGR. vs. 13376 Regressions which are regarded as

> # HG changeset patch > # User Olaf Hering <olaf@aepfle.de> > # Date 1332942876 -7200 > # Node ID d0fe664fca8a7e7db8b46b2f6c267acc88fa9c78 > # Parent 4bd752a4cdf323c41c50f8cd6286f566d67adeae > tools/memshr: fix build errors caused by Werror > > -O2 -Wall -Werror triggers these warnings: > > cc1: warnings being treated as errors > interface.c: In function

If m.num is too large then the "m.num * sizeof(*m.arr)" multiplication could overflow and the access_ok() check wouldn't test the right size. Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com> --- Only needed in linux-next. diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c index 215a3c0..fdff8f9 100644 --- a/drivers/xen/privcmd.c +++ b/drivers/xen/privcmd.c

If m.num is too large then the "m.num * sizeof(*m.arr)" multiplication could overflow and the access_ok() check wouldn't test the right size. Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com> --- Only needed in linux-next. diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c index 215a3c0..fdff8f9 100644 --- a/drivers/xen/privcmd.c +++ b/drivers/xen/privcmd.c

I just updated my quad-processor X64 machine (AMD Phenom(tm) II X4 945 Processor) to the latest CentOS 5 xen kernel (2.6.18-371.4.1.el5xen) and I am getting occasional "BUG: soft lockup - CPU#n stuck for X s! [swapper:0]" messages. I did some net searching, and found some bugzilla reports (https://bugzilla.redhat.com/show_bug.cgi?id=649519 and http://bugs.centos.org/view.php?id=4488),