search for: unmap_single_vma

...nt-warn-patwarn #1 [ 3009.837415] Call Trace: [ 3009.847110] [<ffffffff810674fa>] warn_slowpath_common+0x7a/0xb0 [ 3009.856857] [<ffffffff81067545>] warn_slowpath_null+0x15/0x20 [ 3009.866562] [<ffffffff81042041>] untrack_pfn+0xa1/0xb0 [ 3009.876201] [<ffffffff8111a59b>] unmap_single_vma+0x86b/0x8e0 [ 3009.885895] [<ffffffff81100f16>] ? release_pages+0x196/0x1f0 [ 3009.895488] [<ffffffff8111a65c>] unmap_vmas+0x4c/0xa0 [ 3009.905134] [<ffffffff8111c8fa>] exit_mmap+0x9a/0x180 [ 3009.914706] [<ffffffff81064e72>] mmput+0x52/0xd0 [ 3009.924252] [<ffffffff...

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock

These mappings are in fact special and require special handling in privcmd, which already exists. Failure to mark the PTE as special on arm64 causes all sorts of bad PTE fun. x86 already gets this correct. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Cc: xen-devel@lists.xenproject.org --- arch/arm/xen/enlighten.c |

On 01/06/2018 03:16 AM, Dmitry Melekhov wrote: > The same problem with latest centos 6 kernel,i.e. with meltdown fix. > > I can't see console output, because I have it on "cloud" provider > hosting :-) > > > > 06.01.2018 05:13, Shaun Reitan ?????: >> Broken! >> >> For those of you looking for a PV enabled client Kernel for CentOS Linux

...lt;ffffffff815f3f7e>] xen_do_hypervisor_callback+0x1e/0x30 > [? 587.145018]? <EOI> > [? 587.145018]? [<ffffffff812b8419>] ? free_cpumask_var+0x9/0x10 > [? 587.145018]? [<ffffffff81169618>] ? unmap_page_range+0x5f8/0x860 > [? 587.145018]? [<ffffffff81169901>] ? unmap_single_vma+0x81/0xf0 > [? 587.145018]? [<ffffffff8116a9c9>] ? unmap_vmas+0x49/0x90 > [? 587.145018]? [<ffffffff8117367c>] ? exit_mmap+0xac/0x1a0 > [? 587.145018]? [<ffffffff8105b187>] ? mmput+0x67/0xf0 > [? 587.145018]? [<ffffffff811b6c32>] ? flush_old_exec+0x422/0x880 >...

...[ 587.145018] [<ffffffff815f3f7e>] xen_do_hypervisor_callback+0x1e/0x30 [ 587.145018] <EOI> [ 587.145018] [<ffffffff812b8419>] ? free_cpumask_var+0x9/0x10 [ 587.145018] [<ffffffff81169618>] ? unmap_page_range+0x5f8/0x860 [ 587.145018] [<ffffffff81169901>] ? unmap_single_vma+0x81/0xf0 [ 587.145018] [<ffffffff8116a9c9>] ? unmap_vmas+0x49/0x90 [ 587.145018] [<ffffffff8117367c>] ? exit_mmap+0xac/0x1a0 [ 587.145018] [<ffffffff8105b187>] ? mmput+0x67/0xf0 [ 587.145018] [<ffffffff811b6c32>] ? flush_old_exec+0x422/0x880 [ 587.145018] [<fff...

Hi guys, my computer suddenly failed to boot. It seams that it is unable to mount /home which is btrfs. Here are the messages I get during the boot (the relevant part; hopefully): Feb 02 13:59:58 Edge kernel: kernel BUG at fs/btrfs/extent-tree.c:6185! Feb 02 13:59:58 Edge kernel: invalid opcode: 0000 [#1] PREEMPT SMP Feb 02 13:59:58 Edge kernel: Modules linked in: joydev coretemp kvm_intel kvm

https://bugs.freedesktop.org/show_bug.cgi?id=59069 Priority: medium Bug ID: 59069 Assignee: nouveau at lists.freedesktop.org Summary: nouveau E[ DRM] fail ttm_validate QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter: kees.bakker at xs4all.nl

...ffffffff8135cb5c>] ? __schedule_bug+0x3e/0x46 [ 316.639657] [<ffffffff81361ae9>] ? __schedule+0x90/0x508 [ 316.639664] [<ffffffff8105e21c>] ? __cond_resched+0x10/0x1b [ 316.639669] [<ffffffff813621d4>] ? _cond_resched+0x12/0x1c [ 316.639675] [<ffffffff810d79ab>] ? unmap_single_vma+0x57e/0x620 [ 316.639683] [<ffffffff810c4e47>] ? del_page_from_lru_list+0x73/0x73 [ 316.639688] [<ffffffff810d812f>] ? unmap_vmas+0x58/0x9c [ 316.639694] [<ffffffff810dd0d8>] ? exit_mmap+0x8f/0xd9 [ 316.639700] [<ffffffff8103744a>] ? mmput+0x51/0xf8 [ 316.639706] [...

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others