similar to: xen-unstable dom0/1 smp schedule while atomic

Hi, I have one KVM instance (centos 5) that keeps crashing and i see the message log with the following: Oct 14 16:24:48 localhost kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Oct 14 16:24:49 localhost kernel: BUG: soft lockup - CPU#0 stuck for 12s! [ntpd:2363] Oct 14 16:24:49 localhost kernel: CPU 0: Oct 14 16:24:49 localhost kernel:

i386 Transparent paravirtualization patch #1. Add support for interrupt holdoff to the entry.S fault and syscall paths. This is a straightforward macro-ization for the default sub-architecture. Note that CLI, STI and IRET may be called with non-flat segments because guest %ds and %es segments are live at the time. Any alternative implementation (such as a virtual interrupt mask) is required to

i386 Transparent paravirtualization patch #1. Add support for interrupt holdoff to the entry.S fault and syscall paths. This is a straightforward macro-ization for the default sub-architecture. Note that CLI, STI and IRET may be called with non-flat segments because guest %ds and %es segments are live at the time. Any alternative implementation (such as a virtual interrupt mask) is required to

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=395 The guest domain crashed during the routine daily tests that I ran. Machine: IBM ThinkCentre, 1GB of RAM with FC3 based setup. Xen build, PAE enabled using changeset: 7701:abbe3df33774 [root@thinkcentre-dom0 xen-unstable.hg]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 3

Hello, I''ve got a big problem when I try to install Zimbra on a xen debian etch vm. Eeek! page_mapcount(page) went negative! (-1) page pfn = 7141 page->flags = 4000083c page->count = 2 page->mapping = cd946510 vma->vm_ops = 0x0 ------------[ cut here ]------------ kernel BUG at mm/rmap.c:669! invalid opcode: 0000 [#1] SMP Pid: 7717, comm: java Not tainted

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

I'm experimenting with a 2.0 setup, using the sieve plugin for 2.0 from mercurial. Without sieve, everything seems to work fine. Once I put in a .dovecot.sieve file, though, nothing gets delivered, with the only hint of what's going wrong being this mess in syslog: Jul 7 13:18:00 bellman dovecot: lda(perry): Panic: file index-transaction.c: line 70 (index_transaction_init): assertion

On 05/23, Eric W. Biederman wrote: > > I want to point out that we need to consider not just SIGKILL, but > SIGABRT that causes a coredump, as well as the process peforming > an ordinary exit(2). All of which will cause get_signal to return > SIGKILL in this context. Yes, but probably SIGABRT/exit doesn't really differ from SIGKILL wrt vhost_worker(). > It is probably not

When xfstests 224 was running, the box was panic, and i got this message: [ 1998.327235] ============================================= [ 1998.329940] [ INFO: possible recursive locking detected ] [ 1998.329940] 2.6.39+ #3 [ 1998.329940] --------------------------------------------- [ 1998.329940] dd/25718 is trying to acquire lock: [ 1998.329940] (&(&eb->lock)->rlock){+.+...}, at:

Hi there, I just found a segfaulting tapdisk2 process which led into a kernel oops. [1527071.169682] tapdisk2[26548]: segfault at 7fffd324cfe8 ip 000000000040837f sp 00007fffd324cff0 error 6 in tapdisk2[400000+38000] [1527071.220104] BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 [1527071.220170] IP: [<ffffffff810ce73c>] apply_to_page_range+0x47/0x2f3

On 2020/2/13 ??1:38, Anton Ivanov wrote: > > > On 11/02/2020 10:37, Michael S. Tsirkin wrote: >> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote: >>> On 11/02/2020 02:51, Jason Wang wrote: >>>> >>>> On 2020/2/11 ??12:55, Anton Ivanov wrote: >>>>> >>>>> >>>>> On 09/12/2019 10:48, anton.ivanov

Hey all, I upgraded some servers today from Debian Lenny to Debian Squeeze, and after the upgrade I started getting dovecot crashes. I was on 2.0.13 but got these there as well, and hoped upgrading to 2.0.16 would help. It didn't. Anyone have an idea? Cor Dec 18 23:32:21 userimap1 kernel: [263492.245530] __ratelimit: 122 callbacks suppressed Dec 18 23:32:21 userimap1 kernel:

On 3.8-rc2 with lockdep enabled and dual-GPU setup (Macbook Pro Retina), I see two releated lock inversion issues with the EFI framebuffer, leading to possible deadlock: when X takes over from the EFI framebuffer [1] and when nouveau releases the framebuffer when being vgaswitcherood [2]. Let me know if you'd like any testing or analysis when I can get the time. Many thanks, Daniel ---

Under both XEN 3.0.4 (2.6.16.33) and XEN 3.1 (2.6.18), I can make the OOM killer appear in dom0 of my server by doing heavy I/O from within a VM. If I start 5 VMs on the same server, each VM doing constant I/O over its boot disk (read/write a 2GB file), after about 30 minutes the OOM killer appears in dom0 and starts killing processes. This was observed using 256MB in dom0. If I bump the memory in

I''m looking into getting Xenoprof to tun in an HVM domain, since we will eventually need a profiler for HVM domains to track down areas of poor performance. (HVMs have poor performance? :) ) Being relatively new to OProfile, Xenoprof, and Xen internals, I would appreciate any pointers, tips, and comments on how to work the implementation. I see three basic areas of work. 1. Implement

Hi Patch "drm/nouveau: use drm_mm in preference to custom code doing the same thing" in nouveau tree introduced new deadlock possibility, for which lockdep complains loudly: [ 1541.070202] [drm] nouveau 0000:02:00.0: Allocating FIFO number 3 [ 1541.084772] [drm] nouveau 0000:02:00.0: nouveau_channel_alloc: initialised FIFO 3 [ 2417.733440] [drm] nouveau 0000:02:00.0:

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 6 Jan 2011 20:59:08 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=26242 > > Summary: BUG: unable to handle kernel NULL pointer dereference > at (null) > Product: Memory Management >

Hi Andrew, This series of patches lays the basic ground work for the paravirtualized kernel patches coming later on. I think this lot is ready for the rough-and-tumble world of the -mm tree. The main change from the last posting is that all the page-table related patches have been moved out, and will be posted separately. Also, the off-by-one in reserving the top of address space has been