search for: vmap_page_range_noflush

...; me start with a page allocation failure. It eventually reaches dracut > failures due to systemd/udev not setting up properly, but I think the > root is this: > > [ 1.970630] ------------[ cut here ]------------ > [ 1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131 > vmap_page_range_noflush+0x2c1/0x350 > [ 1.970660] Modules linked in: > [ 1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted > 3.10.0-693.1.1.el7.x86_64 #1 > [ 1.970677] 0000000000000000 000000008cddc75d ffff8803e8587bd8 > ffffffff816a3d91 > [ 1.970688] ffff8803e8587c18 ffffffff810879...

...eventually reaches dracut >>> failures due to systemd/udev not setting up properly, but I think the >>> root is this: >>> >>> [ 1.970630] ------------[ cut here ]------------ >>> [ 1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131 >>> vmap_page_range_noflush+0x2c1/0x350 >>> [ 1.970660] Modules linked in: >>> [ 1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted >>> 3.10.0-693.1.1.el7.x86_64 #1 >>> [ 1.970677] 0000000000000000 000000008cddc75d ffff8803e8587bd8 >>> ffffffff816a3d91 >>>...

A recently created and fully functional CentOS 7.3 VM fails to boot after applying CR updates: ... ;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f

...xt_replace_table->xt_jumpstack_alloc() (in my case I suspect there were no free memory when it's happened): ... oldinfo = xt_replace_table(t, num_counters, newinfo, &ret); if (!oldinfo) goto put_module; The full bactrace is WARNING: at /kernel/mm/vmalloc.c:107 vmap_page_range_noflush+0x120/0x1b4() <4>[18835.587677] [<c00409dc>] (unwind_backtrace+0x0/0x164) from [<c0082a34>] (warn_slowpath_common+0x4c/0x64) <4>[18835.587707] [<c0082a34>] (warn_slowpath_common+0x4c/0x64) from [<c0082a64>] (warn_slowpath_null+0x18/0x1c) <4>[18835.587738] [...

...ear to kick off the failure for me start with a page allocation failure. It eventually reaches dracut failures due to systemd/udev not setting up properly, but I think the root is this: [ 1.970630] ------------[ cut here ]------------ [ 1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131 vmap_page_range_noflush+0x2c1/0x350 [ 1.970660] Modules linked in: [ 1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted 3.10.0-693.1.1.el7.x86_64 #1 [ 1.970677] 0000000000000000 000000008cddc75d ffff8803e8587bd8 ffffffff816a3d91 [ 1.970688] ffff8803e8587c18 ffffffff810879c8 00000083811c14e8 ffff880006...

...allocation failure. It eventually reaches dracut >> failures due to systemd/udev not setting up properly, but I think the >> root is this: >> >> [ 1.970630] ------------[ cut here ]------------ >> [ 1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131 >> vmap_page_range_noflush+0x2c1/0x350 >> [ 1.970660] Modules linked in: >> [ 1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted >> 3.10.0-693.1.1.el7.x86_64 #1 >> [ 1.970677] 0000000000000000 000000008cddc75d ffff8803e8587bd8 >> ffffffff816a3d91 >> [ 1.970688] ffff880...

...t >>>> failures due to systemd/udev not setting up properly, but I think the >>>> root is this: >>>> >>>> [ 1.970630] ------------[ cut here ]------------ >>>> [ 1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131 >>>> vmap_page_range_noflush+0x2c1/0x350 >>>> [ 1.970660] Modules linked in: >>>> [ 1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted >>>> 3.10.0-693.1.1.el7.x86_64 #1 >>>> [ 1.970677] 0000000000000000 000000008cddc75d ffff8803e8587bd8 >>>> ffffffff8...

...ailures due to systemd/udev not setting up properly, but I think the >>>>> root is this: >>>>> >>>>> [ 1.970630] ------------[ cut here ]------------ >>>>> [ 1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131 >>>>> vmap_page_range_noflush+0x2c1/0x350 >>>>> [ 1.970660] Modules linked in: >>>>> [ 1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted >>>>> 3.10.0-693.1.1.el7.x86_64 #1 >>>>> [ 1.970677] 0000000000000000 000000008cddc75d ffff8803e8587bd8 >>&g...

Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong''s ''rc7.git4''  kernel for F12. Boris. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris