divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault vanilla 4.4.6
Subsystems (3)
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed (load > 200) 3 times in the last 3 days.
Always with this stack trace: (copy left here: http://pastebin.com/raw/bCWTLKyt)
[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_conntrack nf_conntrack ip_set_hash_net ip_set vhost_net tun vhost macvtap macvlan kvm_intel nfnetlink_log kvm nfnetlink irqbypass netconsole dlm xt_multiport iptable_filter ip_tables x_tables iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss oid_registry bonding coretemp 8021q garp fuse i2c_i801 i7core_edac edac_core i5500_temp button btrfs xor raid6_pq dm_mod raid1 md_mod usb_storage ohci_hcd bcache sg usbhid sd_mod ata_generic uhci_hcd ehci_pci ehci_hcd usbcore ata_piix usb_common igb i2c_algo_bit mpt3sas raid_class ixgbe scsi_transport_sas i2c_core mdio ptp pps_core [69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>] task_h_load+0xcc/0x100 [69068.961763] RSP: 0000:ffff880fda2c7b50 EFLAGS: 00010257 [69069.023910] RAX: 0000000000000000 RBX: ffff880fda2c7c10 RCX: 0000000000000000 [69069.085953] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880fc7f28000 [69069.151731] RBP: ffff880fda2c7bc8 R08: 00000001041955df R09: ffff880fffd153f8 [69069.213757] R10: 0000000000000009 R11: 0000000000000193 R12: ffff881f6832c780 [69069.274271] R13: ffff88203fc35380 R14: 0000000000000007 R15: 00000000000000b6 [69069.334727] FS: 00007f578a3fb700(0000) GS:ffff880fffd00000(0000) knlGS:0000000000000000 [69069.396435] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [69069.458522] CR2: 00007f5784f18468 CR3: 0000001fe9738000 CR4: 00000000000026e0 [69069.520799] Stack: [69069.581430] ffffffff860b6855 ffff880fda2c7b78 0000000000000000 0000000000000005 [69069.642629] ffff880fffd00000 0000000000000015 fffffffffffffe7d 0000000000000015 [69069.702815] 0000000000015380 ffff880fda2c7bc8 ffff880fc7f28000 00000000000001e9 [69069.761881] Call Trace: [69069.819883] [<ffffffff860b6855>] ? task_numa_find_cpu+0x225/0x670 [69069.878368] [<ffffffff860b79f0>] task_numa_migrate+0x550/0x950 [69069.936059] [<ffffffff863d9138>] ? find_next_bit+0x18/0x20 [69069.993262] [<ffffffff860b7e6d>] numa_migrate_preferred+0x7d/0x90 [69070.050528] [<ffffffff860b89a5>] task_numa_fault+0x7c5/0xaa0 [69070.106544] [<ffffffff861a2c0b>] ? mpol_misplaced+0x16b/0x1b0 [69070.163705] [<ffffffff8618104e>] __handle_mm_fault+0x9ae/0x11f0 [69070.220013] [<ffffffff865e4c52>] ? inet_recvmsg+0x72/0x90 [69070.276558] [<ffffffff8655240b>] ? SYSC_recvfrom+0x12b/0x170 [69070.332283] [<ffffffff8618196f>] handle_mm_fault+0xdf/0x180 [69070.388515] [<ffffffff8604f324>] __do_page_fault+0x164/0x380 [69070.443897] [<ffffffff860b25c3>] ? account_user_time+0x73/0x80 [69070.498534] [<ffffffff860b2b3e>] ? vtime_account_user+0x4e/0x70 [69070.552598] [<ffffffff8604f5a7>] do_page_fault+0x37/0x90 [69070.605960] [<ffffffff86002a23>] ? syscall_return_slowpath+0x83/0xf0 [69070.660705] [<ffffffff866b32f8>] page_fault+0x28/0x30 [69070.715707] Code: 86 b8 00 00 00 48 89 86 b0 00 00 00 48 85 c9 75 ca 49 8b 81 b0 00 00 00 49 8b 49 78 31 d2 48 0f af 87 d8 01 00 00 5d 48 83 c1 01 <48> f7 f1 c3 4c 89 ce 48 8b 8e c0 00 00 00 48 8b 46 78 4c 89 86 [69070.835144] RIP [<ffffffff860b372c>] task_h_load+0xcc/0x100 [69070.894095] RSP <ffff880fda2c7b50> [69070.953213] ---[ end trace 8d6f449a03dacfd4 ]---
Would be nice if we can fix this in 4.4?
Greets,
Stefan
Quoted 75 lines · Stefan Priebe
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed (load > 200) 3 times in the last 3 days.
Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_core[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>] task_h_load+0xcc/0x100 [69068.961763] RSP: 0000:ffff880fda2c7b50 EFLAGS: 00010257 [69069.023910] RAX: 0000000000000000 RBX: ffff880fda2c7c10 RCX: 0000000000000000 [69069.085953] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880fc7f28000 [69069.151731] RBP: ffff880fda2c7bc8 R08: 00000001041955df R09: ffff880fffd153f8 [69069.213757] R10: 0000000000000009 R11: 0000000000000193 R12: ffff881f6832c780 [69069.274271] R13: ffff88203fc35380 R14: 0000000000000007 R15: 00000000000000b6 [69069.334727] FS: 00007f578a3fb700(0000) GS:ffff880fffd00000(0000) knlGS:0000000000000000 [69069.396435] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [69069.458522] CR2: 00007f5784f18468 CR3: 0000001fe9738000 CR4: 00000000000026e0 [69069.520799] Stack: [69069.581430] ffffffff860b6855 ffff880fda2c7b78 0000000000000000 0000000000000005 [69069.642629] ffff880fffd00000 0000000000000015 fffffffffffffe7d 0000000000000015 [69069.702815] 0000000000015380 ffff880fda2c7bc8 ffff880fc7f28000 00000000000001e9 [69069.761881] Call Trace: [69069.819883] [<ffffffff860b6855>] ? task_numa_find_cpu+0x225/0x670 [69069.878368] [<ffffffff860b79f0>] task_numa_migrate+0x550/0x950 [69069.936059] [<ffffffff863d9138>] ? find_next_bit+0x18/0x20 [69069.993262] [<ffffffff860b7e6d>] numa_migrate_preferred+0x7d/0x90 [69070.050528] [<ffffffff860b89a5>] task_numa_fault+0x7c5/0xaa0 [69070.106544] [<ffffffff861a2c0b>] ? mpol_misplaced+0x16b/0x1b0 [69070.163705] [<ffffffff8618104e>] __handle_mm_fault+0x9ae/0x11f0 [69070.220013] [<ffffffff865e4c52>] ? inet_recvmsg+0x72/0x90 [69070.276558] [<ffffffff8655240b>] ? SYSC_recvfrom+0x12b/0x170 [69070.332283] [<ffffffff8618196f>] handle_mm_fault+0xdf/0x180 [69070.388515] [<ffffffff8604f324>] __do_page_fault+0x164/0x380 [69070.443897] [<ffffffff860b25c3>] ? account_user_time+0x73/0x80 [69070.498534] [<ffffffff860b2b3e>] ? vtime_account_user+0x4e/0x70 [69070.552598] [<ffffffff8604f5a7>] do_page_fault+0x37/0x90 [69070.605960] [<ffffffff86002a23>] ? syscall_return_slowpath+0x83/0xf0 [69070.660705] [<ffffffff866b32f8>] page_fault+0x28/0x30 [69070.715707] Code: 86 b8 00 00 00 48 89 86 b0 00 00 00 48 85 c9 75 ca 49 8b 81 b0 00 00 00 49 8b 49 78 31 d2 48 0f af 87 d8 01 00 00 5d 48 83 c1 01 <48> f7 f1 c3 4c 89 ce 48 8b 8e c0 00 00 00 48 8b 46 78 4c 89 86 [69070.835144] RIP [<ffffffff860b372c>] task_h_load+0xcc/0x100 [69070.894095] RSP <ffff880fda2c7b50> [69070.953213] ---[ end trace 8d6f449a03dacfd4 ]---
Quoted 1 line
Would be nice if we can fix this in 4.4?
Does this also happen in 4.5? Did this work on 4.4.5? Some previous release? If you can find the offending patch using 'git bisect', that would be great.
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 21 lines · Greg KH
Quoted 20 lines · Stefan Priebe
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed (load > 200) 3 times in the last 3 days.
Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigb
Quoted 8 lines
Quoted 8 lines
i2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_core[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100
decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trapping instruction
This suggests the CONFIG_FAIR_GROUP_SCHED version of task_h_load:
update_cfs_rq_h_load(cfs_rq);
return div64_ul(p->se.avg.load_avg * cfs_rq->h_load,
cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Quoted 55 lines
Quoted 47 lines
[69068.961763] RSP: 0000:ffff880fda2c7b50 EFLAGS: 00010257 [69069.023910] RAX: 0000000000000000 RBX: ffff880fda2c7c10 RCX: 0000000000000000 [69069.085953] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880fc7f28000 [69069.151731] RBP: ffff880fda2c7bc8 R08: 00000001041955df R09: ffff880fffd153f8 [69069.213757] R10: 0000000000000009 R11: 0000000000000193 R12: ffff881f6832c780 [69069.274271] R13: ffff88203fc35380 R14: 0000000000000007 R15: 00000000000000b6 [69069.334727] FS: 00007f578a3fb700(0000) GS:ffff880fffd00000(0000) knlGS:0000000000000000 [69069.396435] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [69069.458522] CR2: 00007f5784f18468 CR3: 0000001fe9738000 CR4: 00000000000026e0 [69069.520799] Stack: [69069.581430] ffffffff860b6855 ffff880fda2c7b78 0000000000000000 0000000000000005 [69069.642629] ffff880fffd00000 0000000000000015 fffffffffffffe7d 0000000000000015 [69069.702815] 0000000000015380 ffff880fda2c7bc8 ffff880fc7f28000 00000000000001e9 [69069.761881] Call Trace: [69069.819883] [<ffffffff860b6855>] ? task_numa_find_cpu+0x225/0x670 [69069.878368] [<ffffffff860b79f0>] task_numa_migrate+0x550/0x950 [69069.936059] [<ffffffff863d9138>] ? find_next_bit+0x18/0x20 [69069.993262] [<ffffffff860b7e6d>] numa_migrate_preferred+0x7d/0x90 [69070.050528] [<ffffffff860b89a5>] task_numa_fault+0x7c5/0xaa0 [69070.106544] [<ffffffff861a2c0b>] ? mpol_misplaced+0x16b/0x1b0 [69070.163705] [<ffffffff8618104e>] __handle_mm_fault+0x9ae/0x11f0 [69070.220013] [<ffffffff865e4c52>] ? inet_recvmsg+0x72/0x90 [69070.276558] [<ffffffff8655240b>] ? SYSC_recvfrom+0x12b/0x170 [69070.332283] [<ffffffff8618196f>] handle_mm_fault+0xdf/0x180 [69070.388515] [<ffffffff8604f324>] __do_page_fault+0x164/0x380 [69070.443897] [<ffffffff860b25c3>] ? account_user_time+0x73/0x80 [69070.498534] [<ffffffff860b2b3e>] ? vtime_account_user+0x4e/0x70 [69070.552598] [<ffffffff8604f5a7>] do_page_fault+0x37/0x90 [69070.605960] [<ffffffff86002a23>] ? syscall_return_slowpath+0x83/0xf0 [69070.660705] [<ffffffff866b32f8>] page_fault+0x28/0x30 [69070.715707] Code: 86 b8 00 00 00 48 89 86 b0 00 00 00 48 85 c9 75 ca 49 8b 81 b0 00 00 00 49 8b 49 78 31 d2 48 0f af 87 d8 01 00 00 5d 48 83 c1 01 <48> f7 f1 c3 4c 89 ce 48 8b 8e c0 00 00 00 48 8b 46 78 4c 89 86 [69070.835144] RIP [<ffffffff860b372c>] task_h_load+0xcc/0x100 [69070.894095] RSP <ffff880fda2c7b50> [69070.953213] ---[ end trace 8d6f449a03dacfd4 ]---Quoted 1 line
Would be nice if we can fix this in 4.4?
Does this also happen in 4.5? Did this work on 4.4.5? Some previous release? If you can find the offending patch using 'git bisect', that would be great.
thanks,
Quoted 8 lines
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 45 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
Quoted 7 lines
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Yes CONFIG_FAIR_GROUP_SCHED is set. I cherry picked now all those commits up to 4.5 for fair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5
It didn't happen again with v4.4.6 + 4.5 patches for fair.c
Greets,
Stefan
Quoted 58 lines
Quoted 58 lines
Quoted 46 lines
[69068.961763] RSP: 0000:ffff880fda2c7b50 EFLAGS: 00010257 [69069.023910] RAX: 0000000000000000 RBX: ffff880fda2c7c10 RCX: 0000000000000000 [69069.085953] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880fc7f28000 [69069.151731] RBP: ffff880fda2c7bc8 R08: 00000001041955df R09: ffff880fffd153f8 [69069.213757] R10: 0000000000000009 R11: 0000000000000193 R12: ffff881f6832c780 [69069.274271] R13: ffff88203fc35380 R14: 0000000000000007 R15: 00000000000000b6 [69069.334727] FS: 00007f578a3fb700(0000) GS:ffff880fffd00000(0000) knlGS:0000000000000000 [69069.396435] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [69069.458522] CR2: 00007f5784f18468 CR3: 0000001fe9738000 CR4: 00000000000026e0 [69069.520799] Stack: [69069.581430] ffffffff860b6855 ffff880fda2c7b78 0000000000000000 0000000000000005 [69069.642629] ffff880fffd00000 0000000000000015 fffffffffffffe7d 0000000000000015 [69069.702815] 0000000000015380 ffff880fda2c7bc8 ffff880fc7f28000 00000000000001e9 [69069.761881] Call Trace: [69069.819883] [<ffffffff860b6855>] ? task_numa_find_cpu+0x225/0x670 [69069.878368] [<ffffffff860b79f0>] task_numa_migrate+0x550/0x950 [69069.936059] [<ffffffff863d9138>] ? find_next_bit+0x18/0x20 [69069.993262] [<ffffffff860b7e6d>] numa_migrate_preferred+0x7d/0x90 [69070.050528] [<ffffffff860b89a5>] task_numa_fault+0x7c5/0xaa0 [69070.106544] [<ffffffff861a2c0b>] ? mpol_misplaced+0x16b/0x1b0 [69070.163705] [<ffffffff8618104e>] __handle_mm_fault+0x9ae/0x11f0 [69070.220013] [<ffffffff865e4c52>] ? inet_recvmsg+0x72/0x90 [69070.276558] [<ffffffff8655240b>] ? SYSC_recvfrom+0x12b/0x170 [69070.332283] [<ffffffff8618196f>] handle_mm_fault+0xdf/0x180 [69070.388515] [<ffffffff8604f324>] __do_page_fault+0x164/0x380 [69070.443897] [<ffffffff860b25c3>] ? account_user_time+0x73/0x80 [69070.498534] [<ffffffff860b2b3e>] ? vtime_account_user+0x4e/0x70 [69070.552598] [<ffffffff8604f5a7>] do_page_fault+0x37/0x90 [69070.605960] [<ffffffff86002a23>] ? syscall_return_slowpath+0x83/0xf0 [69070.660705] [<ffffffff866b32f8>] page_fault+0x28/0x30 [69070.715707] Code: 86 b8 00 00 00 48 89 86 b0 00 00 00 48 85 c9 75ca 49
8b 81 b0 00 00 00 49 8b 49 78 31 d2 48 0f af 87 d8 01 00 00 5d 48 83 c1 01
<48> f7 f1 c3 4c 89 ce 48 8b 8e c0 00 00 00 48 8b 46 78 4c 89 86Quoted 5 lines
[69070.835144] RIP [<ffffffff860b372c>] task_h_load+0xcc/0x100 [69070.894095] RSP <ffff880fda2c7b50> [69070.953213] ---[ end trace 8d6f449a03dacfd4 ]---Would be nice if we can fix this in 4.4?
Does this also happen in 4.5? Did this work on 4.4.5? Some previous release? If you can find the offending patch using 'git bisect', that would be great.
thanks,
Quoted 9 lines
Quoted 8 lines
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 53 lines · Stefan Priebe
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 51 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);
Quoted 7 lines
Quoted 1 line
So the load avg is -1, thus after adding 1 we get division by 0, huh?
Yes
CONFIG_FAIR_GROUP_SCHEDis set. I cherry picked now all those commits up to 4.5 forfair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5It didn't happen again with v4.4.6 + 4.5 patches for
fair.c
Ok, that's a lot of patches, how about figuring out which single patch, or shortest number of patches, makes things work again?
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Am 20.03.2016 um 22:41 schrieb Greg KH:
Quoted 56 lines · Stefan Priebe
Quoted 55 lines
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 52 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Quoted 8 lines
Quoted 5 lines
Yes
CONFIG_FAIR_GROUP_SCHEDis set. I cherry picked now all those commits up to 4.5 forfair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5It didn't happen again with v4.4.6 + 4.5 patches for
fair.cOk, that's a lot of patches, how about figuring out which single patch, or shortest number of patches, makes things work again?
will do so but it seems most out of those 9 patches are based on each other. So it wouldn't be easy.
Stefan
Quoted 5 lines
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 62 lines · Stefan Priebe - Profihost AG
Am 20.03.2016 um 22:41 schrieb Greg KH:
Quoted 60 lines · Stefan Priebe
Quoted 59 lines
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 45 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
Quoted 7 lines
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Yes
CONFIG_FAIR_GROUP_SCHEDis set. I cherry picked now all those commits up to 4.5 forfair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It didn't happen again with v4.4.6 + 4.5 patches for
fair.cOk, that's a lot of patches, how about figuring out which single patch, or shortest number of patches, makes things work again?
will do so but it seems most out of those 9 patches are based on each other. So it wouldn't be easy.
Worst case, we take all 9. Best case, we only need one :)
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Am 21.03.2016 um 14:38 schrieb Greg KH:
Quoted 65 lines · Stefan Priebe - Profihost AG
Quoted 64 lines
Am 20.03.2016 um 22:41 schrieb Greg KH:
Quoted 62 lines · Stefan Priebe
Quoted 60 lines
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 45 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
Quoted 7 lines
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Yes
CONFIG_FAIR_GROUP_SCHEDis set. I cherry picked now all those commits up to 4.5 forfair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5It didn't happen again with v4.4.6 + 4.5 patches for
fair.c
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Ok, that's a lot of patches, how about figuring out which single patch, or shortest number of patches, makes things work again?
will do so but it seems most out of those 9 patches are based on each other. So it wouldn't be easy.
Worst case, we take all 9. Best case, we only need one :)
Today i got another report from: casteven (at) gmail.com having the same issue. I wasn't able to figure out which of those 9 patches helps - i still can just tell that it does not happen with this series on top of 4.4.
Stefan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Thanks Stefan,
I am seeing this on 4.5.0 and 4.5.4 both are compiled from mainline neither include any patches over and above the tree. I ran for well over a month in production on 4.5.0 with no issues at all on a single socket server (E5-2670 v3 @ 2.30GHz) but as soon as we try to run either 4.5.0 or 4.5.4 on a dual socket box we get these traces after 12 or so hours of uptime and the same sky rocketing load. Given you have stopped your issues by applying those patches to 4.4 it's possible I have different issues, but the symptoms are too similar to ignore, our trace is here:
I am using the cfg scheduler, and not the fair scheduler as Stefan reported so that is another difference.
Happy to proceed with any suggestions or further information that may help isolate this, use case on these servers are 12 x CEPH osd's with bcache so they are seeing alot of disk activity via NVMe and SATA buses.
Thanks
Campbell
Quoted 72 lines · Stefan Priebe - Profihost AG
Am 21.03.2016 um 14:38 schrieb Greg KH:
Quoted 71 lines · Stefan Priebe - Profihost AG
Quoted 69 lines
Am 20.03.2016 um 22:41 schrieb Greg KH:
Quoted 56 lines · Stefan Priebe
Quoted 55 lines
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 52 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Quoted 8 lines
Quoted 5 lines
Yes
CONFIG_FAIR_GROUP_SCHEDis set. I cherry picked now all those commits up to 4.5 forfair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5It didn't happen again with v4.4.6 + 4.5 patches for
fair.cOk, that's a lot of patches, how about figuring out which single patch, or shortest number of patches, makes things work again?
will do so but it seems most out of those 9 patches are based on each other. So it wouldn't be easy.
Quoted 7 lines
Quoted 1 line
Worst case, we take all 9. Best case, we only need one :)
Today i got another report from: casteven (at) gmail.com having the same issue. I wasn't able to figure out which of those 9 patches helps - i still can just tell that it does not happen with this series on top of 4.4.
Stefan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 22 lines · Campbell Steven
Thanks Stefan,
I am seeing this on 4.5.0 and 4.5.4 both are compiled from mainline neither include any patches over and above the tree. I ran for well over a month in production on 4.5.0 with no issues at all on a single socket server (E5-2670 v3 @ 2.30GHz) but as soon as we try to run either 4.5.0 or 4.5.4 on a dual socket box we get these traces after 12 or so hours of uptime and the same sky rocketing load. Given you have stopped your issues by applying those patches to 4.4 it's possible I have different issues, but the symptoms are too similar to ignore, our trace is here:
I am using the cfg scheduler, and not the fair scheduler as Stefan reported so that is another difference.
Happy to proceed with any suggestions or further information that may help isolate this, use case on these servers are 12 x CEPH osd's with bcache so they are seeing alot of disk activity via NVMe and SATA buses.
Quoted 85 lines
Thanks
Campbell
Quoted 79 lines · Stefan Priebe - Profihost AG
Am 21.03.2016 um 14:38 schrieb Greg KH:
Quoted 65 lines · Stefan Priebe - Profihost AG
Quoted 64 lines
Am 20.03.2016 um 22:41 schrieb Greg KH:
Quoted 62 lines · Stefan Priebe
Quoted 60 lines
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
Quoted 45 lines · Greg KH
Quoted 29 lines · Stefan Priebe
Quoted 28 lines
Hi,
while running qemu 2.5 on a host running 4.4.6 the host system has crashed
(load > 200) 3 times in the last 3 days.Always with this stack trace: (copy left here:
http://pastebin.com/raw/bCWTLKyt)[69068.874268] divide error: 0000 [#1] SMP [69068.875242] Modules linked in: ebtable_filter ebtables ip6t_REJECT
nf_reject_ipv6nf_conntrack_ipv6nf_defrag_ipv6ip6table_filterip6_tablesipt_REJECTnf_reject_ipv4xt_physdevxt_commentnf_conntrack_ipv4nf_defrag_ipv4xt_tcpudpxt_markxt_setxt_addrtypext_conntracknf_conntrackip_set_hash_netip_setvhost_nettun vhost macvtap macvlankvm_intelnfnetlink_logkvm nfnetlink irqbypass netconsole dlmxt_multiportiptable_filterip_tablesx_tablesiscsi_tcplibiscsi_tcplibiscsiscsi_transport_iscsinfsdauth_rpcgssoid_registrybonding coretemp 8021q
garp fusei2c_i801i7core_edacedac_corei5500_tempbutton btrfs xorraid6_pqdm_modraid1md_modusb_storageohci_hcdbcache sg usbhidsd_modata_genericuhci_hcdehci_pciehci_hcdusbcoreata_piixusb_commonigbi2c_algo_bitmpt3sasraid_classixgbescsi_transport_sasi2c_coremdio ptppps_coreQuoted 8 lines
Quoted 8 lines
[69068.895604] CPU: 14 PID: 6673 Comm: ceph-osd Not tainted 4.4.6+7-ph #1 [69068.897052] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.1 03/17/2012 [69068.898578] task: ffff880fc7f28000 ti: ffff880fda2c4000 task.ti: ffff880fda2c4000 [69068.900377] RIP: 0010:[<ffffffff860b372c>] [<ffffffff860b372c>]
task_h_load+0xcc/0x100decodecode says:
27: 48 83 c1 01 add $0x1,%rcx 2b:* 48 f7 f1 div %rcx <-- trappinginstruction
Quoted 7 lines
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);So the load avg is -1, thus after adding 1 we get division by 0, huh?
Yes
CONFIG_FAIR_GROUP_SCHEDis set. I cherry picked now all those commits up to 4.5 forfair.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/kernel/sched/fair.c?h=v4.5It didn't happen again with v4.4.6 + 4.5 patches for
fair.cQuoted 7 lines
Quoted 5 lines
Quoted 2 lines
Ok, that's a lot of patches, how about figuring out which single patch, or shortest number of patches, makes things work again?
will do so but it seems most out of those 9 patches are based on each other. So it wouldn't be easy.
Worst case, we take all 9. Best case, we only need one :)
Today i got another report from: casteven (at) gmail.com having the same issue. I wasn't able to figure out which of those 9 patches helps - i still can just tell that it does not happen with this series on top of 4.4.
Stefan
Just reinvigorating this thread based off yesterdays post by Yannis
here: https://lkml.org/lkml/headers/2016/6/21/491 of which the trace is more or less is identical to what we see.
In addition to this we have since tested the 4.6.x releases and have seen the same issues as we have in all the 4.4 and 4.5 releases we tried. I have noticed a few commits in this area of the kernel into the 4.7 series, curious if this may be solved already in 4.7 and if there is a patch to 4.6 we could possibly test, our constraint is that we are only able to reproduce this in our production environment it seems, we never see it in our test/dev systems.
We have also found we can work around the issue by disabling all cores on the second CPU socket (e.g. echo 1 > /sys/devices/system/cpu/cpuX/online), doing this "fixes" this problem for us but is obviously not ideal or long term but gives stability if like us you need to run kernels in these series for various other unrelated reasons and can do without your second socket.
Campbell
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Peter Zijlstra
maintainerQuoted 6 lines · Campbell Steven
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);
---
commit 8974189222159154c55f24ddad33e3613960521a
Author: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200
sched/fair: Fix cfs_rq avg tracking underflow
As per commit:
b7fa30c9cc48 ("sched/fair: Fix post_init_entity_util_avg() serialization")
> the code generated from update_cfs_rq_load_avg():
>
> if (atomic_long_read(&cfs_rq->removed_load_avg)) {
> s64 r = atomic_long_xchg(&cfs_rq->removed_load_avg, 0);
> sa->load_avg = max_t(long, sa->load_avg - r, 0);
> sa->load_sum = max_t(s64, sa->load_sum - r * LOAD_AVG_MAX, 0);
> removed_load = 1;
> }
>
> turns into:
>
> ffffffff81087064: 49 8b 85 98 00 00 00 mov 0x98(%r13),%rax
> ffffffff8108706b: 48 85 c0 test %rax,%rax
> ffffffff8108706e: 74 40 je ffffffff810870b0 <update_blocked_averages+0xc0>
> ffffffff81087070: 4c 89 f8 mov %r15,%rax
> ffffffff81087073: 49 87 85 98 00 00 00 xchg %rax,0x98(%r13)
> ffffffff8108707a: 49 29 45 70 sub %rax,0x70(%r13)
> ffffffff8108707e: 4c 89 f9 mov %r15,%rcx
> ffffffff81087081: bb 01 00 00 00 mov $0x1,%ebx
> ffffffff81087086: 49 83 7d 70 00 cmpq $0x0,0x70(%r13)
> ffffffff8108708b: 49 0f 49 4d 70 cmovns 0x70(%r13),%rcx
>
> Which you'll note ends up with sa->load_avg -= r in memory at > ffffffff8108707a.
So I _should_ have looked at other unserialized users of ->load_avg, but alas. Luckily nikbor reported a similar /0 from task_h_load() which instantly triggered recollection of this here problem.
Aside from the intermediate value hitting memory and causing problems, there's another problem: the underflow detection relies on the signed bit. This reduces the effective width of the variables, IOW its effectively the same as having these variables be of signed type.
This patch changes to a different means of unsigned underflow detection to not rely on the signed bit. This allows the variables to use the 'full' unsigned range. And it does so with explicit LOAD - STORE to ensure any intermediate value will never be visible in memory, allowing these unserialized loads.
Note: GCC generates crap code for this, might warrant a look later.
Note2: I say 'full' above, if we end up at U*_MAX we'll still explode;
maybe we should do clamping on add too.
kernel/sched/fair.c +25 -8
@@ -2904,6 +2904,23 @@ static inline void cfs_rq_util_change(struct cfs_rq *cfs_rq) } } +/* +* Unsigned subtract and clamp on underflow. +* +* Explicitly do a load-store to ensure the intermediate value never hits +* memory. This allows lockless observations without ever seeing the negative +* values. +*/ +#define sub_positive (_ptr, _val) do { \ + typeof(_ptr) ptr = (_ptr); \ + typeof(*ptr) val = (_val); \ + typeof(*ptr) res, var = READ_ONCE(*ptr); \ + res = var - val; \ + if (res > var) \ + res = 0; \ + WRITE_ONCE(*ptr, res); \ +} while (0) +/* Group cfs_rq's load_avg is used for task_h_load and update_cfs_share */ static inline int update_cfs_rq_load_avg (u64 now,struct cfs_rq *cfs_rq,bool update_freq)
@@ -2913,15 +2930,15 @@ update_cfs_rq_load_avg(u64 now, struct cfs_rq *cfs_rq, bool update_freq)if (atomic_long_read (&cfs_rq->removed_load_avg)) {s64 r =atomic_long_xchg (&cfs_rq->removed_load_avg,0 ); - sa->load_avg =max_t (long, sa->load_avg - r,0 ); - sa->load_sum =max_t (s64, sa->load_sum - r *LOAD_AVG_MAX ,0 ); +sub_positive (&sa->load_avg, r); +sub_positive (&sa->load_sum, r *LOAD_AVG_MAX ); removed_load =1 ; }if (atomic_long_read (&cfs_rq->removed_util_avg)) {long r =atomic_long_xchg (&cfs_rq->removed_util_avg,0 ); - sa->util_avg =max_t (long, sa->util_avg - r,0 ); - sa->util_sum =max_t (s32, sa->util_sum - r *LOAD_AVG_MAX ,0 ); +sub_positive (&sa->util_avg, r); +sub_positive (&sa->util_sum, r *LOAD_AVG_MAX ); removed_util =1 ; }
@@ -2994,10 +3011,10 @@ static void detach_entity_load_avg(struct cfs_rq *cfs_rq, struct sched_entity *s &se->avg, se->on_rq *scale_load_down (se->load.weight), cfs_rq->curr == se, NULL); - cfs_rq->avg.load_avg =max_t (long, cfs_rq->avg.load_avg - se->avg.load_avg,0 ); - cfs_rq->avg.load_sum =max_t (s64, cfs_rq->avg.load_sum - se->avg.load_sum,0 ); - cfs_rq->avg.util_avg =max_t (long, cfs_rq->avg.util_avg - se->avg.util_avg,0 ); - cfs_rq->avg.util_sum =max_t (s32, cfs_rq->avg.util_sum - se->avg.util_sum,0 ); +sub_positive (&cfs_rq->avg.load_avg, se->avg.load_avg); +sub_positive (&cfs_rq->avg.load_sum, se->avg.load_sum); +sub_positive (&cfs_rq->avg.util_avg, se->avg.util_avg); +sub_positive (&cfs_rq->avg.util_sum, se->avg.util_sum);cfs_rq_util_change (cfs_rq); }
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 14 lines · Peter Zijlstra
Quoted 6 lines · Campbell Steven
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
This suggests the
CONFIG_FAIR_GROUP_SCHEDversion oftask_h_load:update_cfs_rq_h_load(cfs_rq); return div64_ul(p->se.avg.load_avg * cfs_rq->h_load, cfs_rq_load_avg(cfs_rq) + 1);---
commit8974189222159154c55f24ddad33e3613960521aAuthor: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200
Quoted 14 lines
sched/fair: Fix cfs_rq avg tracking underflow
As per commit:
b7fa30c9cc48 ("sched/fair: Fix post_init_entity_util_avg() serialization")
> the code generated from update_cfs_rq_load_avg():
>
> if (atomic_long_read(&cfs_rq->removed_load_avg)) {
> s64 r = atomic_long_xchg(&cfs_rq->removed_load_avg, 0);
> sa->load_avg = max_t(long, sa->load_avg - r, 0);
> sa->load_sum = max_t(s64, sa->load_sum - r * LOAD_AVG_MAX, 0);
> removed_load = 1;
> }Hi Peter,
I just wanted to report back to say thanks for this, and we have (and others) have tested this out in 4.7 rc6 and have not been able to repeat the issue. It seems that anyone running busy ceph osd's or high load KVM instances is able to trigger this on a dual socket box pretty easily.
Since these early reports from Stefan and I it looks like it's been hit but alot more folks now so I'd like to ask what the process is for getting this backported into 4.6, 4.5 and 4.4 as in our testing all those versions for their latest point release seem to have the same problem.
Thanks
Campbell
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Peter Zijlstra
maintainerQuoted 9 lines · Campbell Steven
Quoted 3 lines
commit
8974189222159154c55f24ddad33e3613960521aAuthor: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200Since these early reports from Stefan and I it looks like it's been hit but alot more folks now so I'd like to ask what the process is for getting this backported into 4.6, 4.5 and 4.4 as in our testing all those versions for their latest point release seem to have the same problem.
I think this should do; Greg is on Cc and will mark the commit somewhere. It is already in Linus' tree and should indeed be sufficient.
It has a Fixes tag referring the commit that introduced it, which IIRC is somewhere around v4.2.
Greg, anything else required?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 12 lines · Peter Zijlstra
Quoted 9 lines · Campbell Steven
Quoted 3 lines
commit
8974189222159154c55f24ddad33e3613960521aAuthor: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200Since these early reports from Stefan and I it looks like it's been hit but alot more folks now so I'd like to ask what the process is for getting this backported into 4.6, 4.5 and 4.4 as in our testing all those versions for their latest point release seem to have the same problem.
Quoted 7 lines
I think this should do; Greg is on Cc and will mark the commit somewhere. It is already in Linus' tree and should indeed be sufficient.
It has a Fixes tag referring the commit that introduced it, which IIRC is somewhere around v4.2.
Greg, anything else required?
Nope, that should be fine.
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 12 lines · Peter Zijlstra
Quoted 9 lines · Campbell Steven
Quoted 3 lines
commit
8974189222159154c55f24ddad33e3613960521aAuthor: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200Since these early reports from Stefan and I it looks like it's been hit but alot more folks now so I'd like to ask what the process is for getting this backported into 4.6, 4.5 and 4.4 as in our testing all those versions for their latest point release seem to have the same problem.
Quoted 7 lines
I think this should do; Greg is on Cc and will mark the commit somewhere. It is already in Linus' tree and should indeed be sufficient.
It has a Fixes tag referring the commit that introduced it, which IIRC is somewhere around v4.2.
Greg, anything else required?
Oops, this commit does not apply cleanly to 4.6 or 4.4-stable trees. Can someone send me the backported verision that they have tested to work properly so I can queue it up?
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Peter Zijlstra
maintainerQuoted 3 lines · Greg KH
Oops, this commit does not apply cleanly to 4.6 or 4.4-stable trees. Can someone send me the backported verision that they have tested to work properly so I can queue it up?
I've never actually been able to reproduce, but the attached patches apply, the reject was trivial.
They seem to compile and boot on my main test rig, but nothing else was done but build the next kernel with it.
commit 8974189222159154c55f24ddad33e3613960521a
Author: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200
sched/fair: Fix cfs_rq avg tracking underflow
As per commit:
b7fa30c9cc48 ("sched/fair: Fix post_init_entity_util_avg() serialization")
> the code generated from update_cfs_rq_load_avg():
>
> if (atomic_long_read(&cfs_rq->removed_load_avg)) {
> s64 r = atomic_long_xchg(&cfs_rq->removed_load_avg, 0);
> sa->load_avg = max_t(long, sa->load_avg - r, 0);
> sa->load_sum = max_t(s64, sa->load_sum - r * LOAD_AVG_MAX, 0);
> removed_load = 1;
> }
>
> turns into:
>
> ffffffff81087064: 49 8b 85 98 00 00 00 mov 0x98(%r13),%rax
> ffffffff8108706b: 48 85 c0 test %rax,%rax
> ffffffff8108706e: 74 40 je ffffffff810870b0 <update_blocked_averages+0xc0>
> ffffffff81087070: 4c 89 f8 mov %r15,%rax
> ffffffff81087073: 49 87 85 98 00 00 00 xchg %rax,0x98(%r13)
> ffffffff8108707a: 49 29 45 70 sub %rax,0x70(%r13)
> ffffffff8108707e: 4c 89 f9 mov %r15,%rcx
> ffffffff81087081: bb 01 00 00 00 mov $0x1,%ebx
> ffffffff81087086: 49 83 7d 70 00 cmpq $0x0,0x70(%r13)
> ffffffff8108708b: 49 0f 49 4d 70 cmovns 0x70(%r13),%rcx
>
> Which you'll note ends up with sa->load_avg -= r in memory at > ffffffff8108707a.
So I _should_ have looked at other unserialized users of ->load_avg, but alas. Luckily nikbor reported a similar /0 from task_h_load() which instantly triggered recollection of this here problem.
Aside from the intermediate value hitting memory and causing problems, there's another problem: the underflow detection relies on the signed bit. This reduces the effective width of the variables, IOW its effectively the same as having these variables be of signed type.
This patch changes to a different means of unsigned underflow detection to not rely on the signed bit. This allows the variables to use the 'full' unsigned range. And it does so with explicit LOAD - STORE to ensure any intermediate value will never be visible in memory, allowing these unserialized loads.
Note: GCC generates crap code for this, might warrant a look later.
Note2: I say 'full' above, if we end up at U*_MAX we'll still explode;
maybe we should do clamping on add too.
--- kernel/sched/fair.c | 33 +++++++++++++++++++++++++-------- 1 file changed, 25 insertions(+), 8 deletions(-)
kernel/sched/fair.c +25 -8
@@ -2682,6 +2682,23 @@ static inline void update_tg_load_avg(ststatic inline u64 cfs_rq_clock_task (struct cfs_rq *cfs_rq); +/* +* Unsigned subtract and clamp on underflow. +* +* Explicitly do a load-store to ensure the intermediate value never hits +* memory. This allows lockless observations without ever seeing the negative +* values. +*/ +#define sub_positive (_ptr, _val) do { \ + typeof(_ptr) ptr = (_ptr); \ + typeof(*ptr) val = (_val); \ + typeof(*ptr) res, var = READ_ONCE(*ptr); \ + res = var - val; \ + if (res > var) \ + res = 0; \ + WRITE_ONCE(*ptr, res); \ +} while (0) +/* Group cfs_rq's load_avg is used for task_h_load and update_cfs_share */ static inline int update_cfs_rq_load_avg (u64 now,struct cfs_rq *cfs_rq) {
@@ -2690,15 +2707,15 @@ static inline int update_cfs_rq_load_avgif (atomic_long_read (&cfs_rq->removed_load_avg)) {s64 r =atomic_long_xchg (&cfs_rq->removed_load_avg,0 ); - sa->load_avg =max_t (long, sa->load_avg - r,0 ); - sa->load_sum =max_t (s64, sa->load_sum - r *LOAD_AVG_MAX ,0 ); +sub_positive (&sa->load_avg, r); +sub_positive (&sa->load_sum, r *LOAD_AVG_MAX ); removed =1 ; }if (atomic_long_read (&cfs_rq->removed_util_avg)) {long r =atomic_long_xchg (&cfs_rq->removed_util_avg,0 ); - sa->util_avg =max_t (long, sa->util_avg - r,0 ); - sa->util_sum =max_t (s32, sa->util_sum - r *LOAD_AVG_MAX ,0 ); +sub_positive (&sa->util_avg, r); +sub_positive (&sa->util_sum, r *LOAD_AVG_MAX ); } decayed = __update_load_avg(now, cpu_of(rq_of(cfs_rq)), sa,
@@ -2764,10 +2781,10 @@ static void detach_entity_load_avg(struc &se->avg, se->on_rq *scale_load_down (se->load.weight), cfs_rq->curr == se, NULL); - cfs_rq->avg.load_avg =max_t (long, cfs_rq->avg.load_avg - se->avg.load_avg,0 ); - cfs_rq->avg.load_sum =max_t (s64, cfs_rq->avg.load_sum - se->avg.load_sum,0 ); - cfs_rq->avg.util_avg =max_t (long, cfs_rq->avg.util_avg - se->avg.util_avg,0 ); - cfs_rq->avg.util_sum =max_t (s32, cfs_rq->avg.util_sum - se->avg.util_sum,0 ); +sub_positive (&cfs_rq->avg.load_avg, se->avg.load_avg); +sub_positive (&cfs_rq->avg.load_sum, se->avg.load_sum); +sub_positive (&cfs_rq->avg.util_avg, se->avg.util_avg); +sub_positive (&cfs_rq->avg.util_sum, se->avg.util_sum); }/* Add the load generated by se into cfs_rq's load average */
commit 8974189222159154c55f24ddad33e3613960521a
Author: Peter Zijlstra <[email protected]> Date: Thu Jun 16 10:50:40 2016 +0200
sched/fair: Fix cfs_rq avg tracking underflow
As per commit:
b7fa30c9cc48 ("sched/fair: Fix post_init_entity_util_avg() serialization")
> the code generated from update_cfs_rq_load_avg():
>
> if (atomic_long_read(&cfs_rq->removed_load_avg)) {
> s64 r = atomic_long_xchg(&cfs_rq->removed_load_avg, 0);
> sa->load_avg = max_t(long, sa->load_avg - r, 0);
> sa->load_sum = max_t(s64, sa->load_sum - r * LOAD_AVG_MAX, 0);
> removed_load = 1;
> }
>
> turns into:
>
> ffffffff81087064: 49 8b 85 98 00 00 00 mov 0x98(%r13),%rax
> ffffffff8108706b: 48 85 c0 test %rax,%rax
> ffffffff8108706e: 74 40 je ffffffff810870b0 <update_blocked_averages+0xc0>
> ffffffff81087070: 4c 89 f8 mov %r15,%rax
> ffffffff81087073: 49 87 85 98 00 00 00 xchg %rax,0x98(%r13)
> ffffffff8108707a: 49 29 45 70 sub %rax,0x70(%r13)
> ffffffff8108707e: 4c 89 f9 mov %r15,%rcx
> ffffffff81087081: bb 01 00 00 00 mov $0x1,%ebx
> ffffffff81087086: 49 83 7d 70 00 cmpq $0x0,0x70(%r13)
> ffffffff8108708b: 49 0f 49 4d 70 cmovns 0x70(%r13),%rcx
>
> Which you'll note ends up with sa->load_avg -= r in memory at > ffffffff8108707a.
So I _should_ have looked at other unserialized users of ->load_avg, but alas. Luckily nikbor reported a similar /0 from task_h_load() which instantly triggered recollection of this here problem.
Aside from the intermediate value hitting memory and causing problems, there's another problem: the underflow detection relies on the signed bit. This reduces the effective width of the variables, IOW its effectively the same as having these variables be of signed type.
This patch changes to a different means of unsigned underflow detection to not rely on the signed bit. This allows the variables to use the 'full' unsigned range. And it does so with explicit LOAD - STORE to ensure any intermediate value will never be visible in memory, allowing these unserialized loads.
Note: GCC generates crap code for this, might warrant a look later.
Note2: I say 'full' above, if we end up at U*_MAX we'll still explode;
maybe we should do clamping on add too.
kernel/sched/fair.c +25 -8
@@ -2821,6 +2821,23 @@ static inline void update_tg_load_avg(ststatic inline u64 cfs_rq_clock_task (struct cfs_rq *cfs_rq); +/* +* Unsigned subtract and clamp on underflow. +* +* Explicitly do a load-store to ensure the intermediate value never hits +* memory. This allows lockless observations without ever seeing the negative +* values. +*/ +#define sub_positive (_ptr, _val) do { \ + typeof(_ptr) ptr = (_ptr); \ + typeof(*ptr) val = (_val); \ + typeof(*ptr) res, var = READ_ONCE(*ptr); \ + res = var - val; \ + if (res > var) \ + res = 0; \ + WRITE_ONCE(*ptr, res); \ +} while (0) +/* Group cfs_rq's load_avg is used for task_h_load and update_cfs_share */ static inline int update_cfs_rq_load_avg (u64 now,struct cfs_rq *cfs_rq) {
@@ -2829,15 +2846,15 @@ static inline int update_cfs_rq_load_avgif (atomic_long_read (&cfs_rq->removed_load_avg)) {s64 r =atomic_long_xchg (&cfs_rq->removed_load_avg,0 ); - sa->load_avg =max_t (long, sa->load_avg - r,0 ); - sa->load_sum =max_t (s64, sa->load_sum - r *LOAD_AVG_MAX ,0 ); +sub_positive (&sa->load_avg, r); +sub_positive (&sa->load_sum, r *LOAD_AVG_MAX ); removed =1 ; }if (atomic_long_read (&cfs_rq->removed_util_avg)) {long r =atomic_long_xchg (&cfs_rq->removed_util_avg,0 ); - sa->util_avg =max_t (long, sa->util_avg - r,0 ); - sa->util_sum =max_t (s32, sa->util_sum - r *LOAD_AVG_MAX ,0 ); +sub_positive (&sa->util_avg, r); +sub_positive (&sa->util_sum, r *LOAD_AVG_MAX ); } decayed = __update_load_avg(now, cpu_of(rq_of(cfs_rq)), sa,
@@ -2927,10 +2944,10 @@ static void detach_entity_load_avg(struc &se->avg, se->on_rq *scale_load_down (se->load.weight), cfs_rq->curr == se, NULL); - cfs_rq->avg.load_avg =max_t (long, cfs_rq->avg.load_avg - se->avg.load_avg,0 ); - cfs_rq->avg.load_sum =max_t (s64, cfs_rq->avg.load_sum - se->avg.load_sum,0 ); - cfs_rq->avg.util_avg =max_t (long, cfs_rq->avg.util_avg - se->avg.util_avg,0 ); - cfs_rq->avg.util_sum =max_t (s32, cfs_rq->avg.util_sum - se->avg.util_sum,0 ); +sub_positive (&cfs_rq->avg.load_avg, se->avg.load_avg); +sub_positive (&cfs_rq->avg.load_sum, se->avg.load_sum); +sub_positive (&cfs_rq->avg.util_avg, se->avg.util_avg); +sub_positive (&cfs_rq->avg.util_sum, se->avg.util_sum); }/* Add the load generated by se into cfs_rq's load average */
Quoted 11 lines · Peter Zijlstra
Quoted 3 lines · Greg KH
Oops, this commit does not apply cleanly to 4.6 or 4.4-stable trees. Can someone send me the backported verision that they have tested to work properly so I can queue it up?
I've never actually been able to reproduce, but the attached patches apply, the reject was trivial.
They seem to compile and boot on my main test rig, but nothing else was done but build the next kernel with it.
Thanks for these, now applied.
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>