[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
This is a regression introduced by commit 35103d11173b in 4.3-rc1. Commit
bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.
== Fix ==
commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
Author: Ido Schimmel
Date: Tue Nov 21 09:50:12 2017 +0200
ipv6: Do not consider linkdown nexthops during multipath
== Regression Potential ==
This fix is specific to ipv6 and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
I tested the proposed Kernel in Xenial and it is working for me
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
This is a regression introduced by commit 35103d11173b in 4.3-rc1. Commit
bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.
== Fix ==
commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
Author: Ido Schimmel
Date: Tue Nov 21 09:50:12 2017 +0200
ipv6: Do not consider linkdown nexthops during multipath
== Regression Potential ==
This fix is specific to ipv6 and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742630] Re: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
I have the kernel running and I confirm that it resolved the bug Linux s0008 4.13.0-25-generic #29~lp1742630 SMP Thu Jan 11 18:42:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: I cannot boot from 4.13.0-21-generic Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi&m=151523964725984&w=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1742630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742630] Re: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
I have tested this version linux-image-generic-hwe-16.04 4.13.0.26.46 It does not work for me ** Summary changed: - Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] + PTI Kernels: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] ** Summary changed: - PTI Kernels: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] + PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] Status in linux package in Ubuntu: Confirmed Bug description: I cannot boot from 4.13.0-21-generic Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi&m=151523964725984&w=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742630] Re: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
The Kernel does not boot at all, so it is not possible to collect the data with apport-collect ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] Status in linux package in Ubuntu: Confirmed Bug description: I cannot boot from 4.13.0-21-generic Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi&m=151523964725984&w=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742630] [NEW] Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
Public bug reported: I cannot boot from 4.13.0-21-generic Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi&m=151523964725984&w=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: I cannot boot from 4.13.0-21-generic + + Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 + [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi&m=151523964725984&w=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742630 Title: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot from 4.13.0-21-generic Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci] This Kernel bug was already fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414 Relevant discussion: https://marc.info/?l=linux-scsi&m=151523964725984&w=2 Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
I tested the packages on Xenial:
; uname -a
Linux s0006 4.4.0-103-generic #126~lp1738219 SMP Thu Dec 14 16:37:03 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
It LGTM. The bug is fixed when using this kernel.
thank you
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Zesty:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
Fixed in the upstream kernel with patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
I think this patch must be backported to stable kernel in Xenial. I
tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
I tested now with Kernel 4.4.0-103-generic + the patch from commit
bbfcd7 and it works for me
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Xenial:
Triaged
Status in linux-lts-xenial source package in Xenial:
New
Bug description:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
Fixed in the upstream kernel with patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
I think this patch must be backported to stable kernel in Xenial. I
tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
Confirmed
Status in linux-lts-xenial package in Ubuntu:
New
Bug description:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
Fixed in the upstream kernel with patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
I think this patch must be backported to stable kernel in Xenial. I
tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738219] [NEW] the kernel is blackholing IPv6 packets to linkdown nexthops
Public bug reported:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
Fixed in the upstream kernel with patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
I think this patch must be backported to stable kernel in Xenial. I
tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
me.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Tags: xenial
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
Incomplete
Status in linux-lts-xenial package in Ubuntu:
New
Bug description:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
Fixed in the upstream kernel with patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
I think this patch must be backported to stable kernel in Xenial. I
tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation
Hello, I still se this issue on Xenial with Kernel 4.4.0-93-generic #116-Ubuntu The server is bare-metal. It is just a cosmetic problem in the log files or I should upgrade as soon as possible ? I noticed the bad entries in my kern.log with my monitoring tool, but I dont see any side effect so far. Could anyone please clarify what is the operational impact of this bug ? thanks ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705447 Title: misleading kernel warning skb_warn_bad_offload during checksum calculation Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Even when the packet says checksum calculation is unnecessary the kernel will still check the checksum and display a warning that the checksum is bad. This has been fixed upstream in Kernel 4.11 by commit id: b2504a5dbef3305ef41988ad270b0e8ec289331c We have reports of Ubuntu 16.04 virtual machines (with ip forward enabled) displaying these warnings: [10480.074664] [ cut here ] [10480.074667] WARNING: CPU: 1 PID: 0 at /build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 skb_warn_bad_offload+0xd1/0x120 [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1 [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net pata_acpi floppy [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW O 4.8.0-52-generic #55~16.04.1-Ubuntu [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 04/01/2014 [10480.074697] 0286 ec176c2ae03bc036 8beef5643870 b7a2e7b3 [10480.074699] 8beef56438c0 8beef56438b0 b768314b [10480.074702] 098cb84fba80 8bed61f82000 8bee9915c000 0005 [10480.074704] Call Trace: [10480.074704][] dump_stack+0x63/0x90 [10480.074708] [] __warn+0xcb/0xf0 [10480.074710] [] warn_slowpath_fmt+0x5f/0x80 [10480.074713] [] ? ___ratelimit+0xa2/0xf0 [10480.074714] [] skb_warn_bad_offload+0xd1/0x120 [10480.074716] [] __skb_gso_segment+0xd8/0x140 [10480.074717] [] validate_xmit_skb+0x14f/0x2a0 [10480.074719] [] __dev_queue_xmit+0x322/0x6d0 [10480.074720] [] ? nf_nat_ipv4_fn+0x1a6/0x230 [nf_nat_ipv4] [10480.074723] [] dev_queue_xmit+0x10/0x20 [10480.074725] [] ip_finish_output2+0x292/0x380 [10480.074726] [] ? ipv4_confirm+0x7d/0x100 [nf_conntrack_ipv4] [10480.074728] [] ip_finish_output+0x132/0x1d0 [10480.074729] [] ? nf_hook_slow+0x73/0xd0 [10480.074731] [] ip_output+0x6e/0xf0 [10480.074733] [] ? __ip_flush_pending_frames.isra.40+0x90/0x90 [10480.074736] [] ip_forward_finish+0x43/0x70 [10480.074738] [] ip_forward+0x384/0x480 [10480.074739] [] ? ip_frag_mem+0x50/0x50 [10480.074741] [] ip_rcv_finish+0x11b/0x400 [10480.074743] [] ip_rcv+0x28b/0x3c0 [10480.074744] [] ? inet_del_offload+0x40/0x40 [10480.074746] [] __netif_receive_skb_core+0x524/0xab0 [10480.074747] [] ? kmem_cache_alloc+0xd7/0x1b0 [10480.074749] [] ? __build_skb+0x2a/0xe0 [10480.074751] [] __netif_receive_skb+0x18/0x60 [10480.074753] [] netif_receive_skb_internal+0x32/0xa0 [10480.074754] [] napi_gro_receive+0xcd/0x120 [10480.074756] [] virtnet_receive+0x1c3/0x970 [virtio_net] [10480.074758] [] ? update_cfs_rq_load_avg+0x1f9/0x4c0 [10480.074760] [] virtnet_poll+0x1d/0x80 [virtio_net] [10480.074762] [] net_rx_action+0x238/0x380 [10480.074764] [] __do_softirq+0xf6/0x280 [10480.074765] [] irq_exit+0xa3/0xb0 [10480.074766] [] do_IRQ+0x54/0xd0 [10480.074768] [] common_interrupt+0x82/0x82 [10480.074768][] ? native_safe_halt+0x6/0x10 [10480.074772] [] default_idle+0x1e/0xd0 [10480.074774] [] arch_cpu_idle+0xf/0x20 [10480.074775] [] default_idle_call+0x2a/0x40 [10480.074776] [] cpu_startup_entry+0x2ea/0x350 [10480.074778] [] start_secondary+0x151/0x190 [10480.074781] ---[ end trace 3a9bd18de5564b05 ]--- We have recompiled your latest 16.04.2 kernel with this patch and confirmed that this warning does not happen. Could you please consider including this fix in your next 16.0
[Kernel-packages] [Bug 1660634] [NEW] Enable CONFIG_NET_DROP_MONITOR=m in Ubuntu Kernel
Public bug reported: CONFIG_NET_DROP_MONITOR=m is needed for the dropwatch software. At the moment dropwatch is packaged only for Fedora: https://fedorahosted.org/dropwatch/ The kernel compiled with CONFIG_NET_DROP_MONITOR=n makes not possible to use this software. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Fix Committed ** Affects: linux (Ubuntu Trusty) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Yakkety) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Zesty) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1660634 Title: Enable CONFIG_NET_DROP_MONITOR=m in Ubuntu Kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Committed Bug description: CONFIG_NET_DROP_MONITOR=m is needed for the dropwatch software. At the moment dropwatch is packaged only for Fedora: https://fedorahosted.org/dropwatch/ The kernel compiled with CONFIG_NET_DROP_MONITOR=n makes not possible to use this software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
