Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
Hi Kevin, On Mon, Nov 21, 2022 at 04:49:16PM -0500, Kevin P. Fleming wrote: > On Sun, Nov 20, 2022, at 12:56, Kevin P. Fleming wrote: > > On Sun, Nov 20, 2022, at 08:38, Salvatore Bonaccorso wrote: > > > >> If that would be helpful, we have some instructions on "simple > >> patching and building" the kernel with a additional patches on top > >> here: > >> > >> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 > > > > I found those via another path, and used them :-) Had a few little > > issues along the way: failing to set DEBFULLNAME produces a broken > > changelog entry so then the build won't run (and leaves the tree in a > > broken state as well). Once I solved that problem I was able to make > > packages, but the linux-headers-common package didn't get produced, so > > I had to use --force-depends-version when installing the packages > > (which I knew was safe since the headers had not changed). > > > > I now have the patched kernel in operation and should know whether the > > problem is solved in 24-48 hours. > > It's been more than 24 hours and connectivity is still in place, and > it never lasted this long without the patch. I'm comfortable saying > that this patch resolved the problem. Thanks for testing. I will try to make it included in the next unstable upload (waiting for 6.0.10 which should come around friday). Regards, Salvatore
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
On Sun, Nov 20, 2022, at 12:56, Kevin P. Fleming wrote: > On Sun, Nov 20, 2022, at 08:38, Salvatore Bonaccorso wrote: > >> If that would be helpful, we have some instructions on "simple >> patching and building" the kernel with a additional patches on top >> here: >> >> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 > > I found those via another path, and used them :-) Had a few little > issues along the way: failing to set DEBFULLNAME produces a broken > changelog entry so then the build won't run (and leaves the tree in a > broken state as well). Once I solved that problem I was able to make > packages, but the linux-headers-common package didn't get produced, so > I had to use --force-depends-version when installing the packages > (which I knew was safe since the headers had not changed). > > I now have the patched kernel in operation and should know whether the > problem is solved in 24-48 hours. It's been more than 24 hours and connectivity is still in place, and it never lasted this long without the patch. I'm comfortable saying that this patch resolved the problem.
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
On Sun, Nov 20, 2022, at 08:38, Salvatore Bonaccorso wrote: > If that would be helpful, we have some instructions on "simple > patching and building" the kernel with a additional patches on top > here: > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 I found those via another path, and used them :-) Had a few little issues along the way: failing to set DEBFULLNAME produces a broken changelog entry so then the build won't run (and leaves the tree in a broken state as well). Once I solved that problem I was able to make packages, but the linux-headers-common package didn't get produced, so I had to use --force-depends-version when installing the packages (which I knew was safe since the headers had not changed). I now have the patched kernel in operation and should know whether the problem is solved in 24-48 hours.
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
Hi Kevin,
On Sun, Nov 20, 2022 at 08:23:04AM -0500, Kevin P. Fleming wrote:
> On Sun, Nov 20, 2022, at 08:15, Salvatore Bonaccorso wrote:
> > Hi,
> >
> > On Sun, Nov 20, 2022 at 02:13:11PM +0100, Salvatore Bonaccorso wrote:
> >> Control: tags -1 + moreinfo
> >>
> >> Hi,
> >>
> >> On Mon, Nov 14, 2022 at 06:34:43AM -0500, Kevin P. Fleming wrote:
> >> > Package: src:linux
> >> > Version: 6.0.7-1
> >> > Severity: normal
> >> > Tags: ipv6
> >> >
> >> > Dear Maintainer,
> >> >
> >> > This system has been operating for most of the last 12 months, using
> >> > ProxyNDP on its external interface for eight addresses. After
> >> > upgrading to the 6.0 kernel series, the kernel stops responding to ND
> >> > solicitations for those addresses after startup... it does not happen
> >> > immediately, but reliably occurs. When the system is in this state
> >> > (not responding to ND solicitations for the proxy addresses), the
> >> > proxy addresses are still shown in 'ip neigh show proxy', and the
> >> > single non-proxy address on the same interface continues operating
> >> > normally.
> >> >
> >> > Booting the system with the 5.19.0-2 kernel package cures the problem,
> >> > with no other changes.
> >> >
> >> > Example output:
> >> >
> >> > root@net22:~# ip neigh show proxy
> >> > 2607:5300:203:9743::1 dev ve-diw20 proxy
> >> > 2607:5300:203:9743::1 dev ve-matrix20 proxy
> >> > 2607:5300:203:9743::1 dev ve-ns3 proxy
> >> > 2607:5300:203:9743::1 dev ve-ldl20 proxy
> >> > 2607:5300:203:9743::1 dev ve-quassel21 proxy
> >> > 2607:5300:203:9743::1 dev ve-mastodon22 proxy
> >> > 2607:5300:203:9743::1 dev ve-monica21 proxy
> >> > 2607:5300:203:9743::1 dev ve-mail20 proxy
> >> > 2607:5300:203:9743:4::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:1::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:8::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:5::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:3::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:2::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:6::1 dev enp1s0f0 proxy
> >> > 2607:5300:203:9743:7::1 dev enp1s0f0 proxy
> >> >
> >> > The addresses on enp1s0f0 are the ones which stop responding.
> >>
> >> Does the following matches your problem?
> >>
> >> https://lore.kernel.org/netdev/y295+9+jdjqrw...@x1.ze-it.at/
> >>
> >> Would you be able to test the mentioned patch to verify a fix for your
> >> issue? The above changes fixes 0ff4eb3d5ebb ("neighbour: make
> >> proxy_queue.qlen limit per-device") introduced in 6.0-rc2.
> >
> > For reference, the commit would be v2 as applied in netdev as
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8207f253a097fe15c93d85ac15ebb73c5e39e1e1
>
> While that description does not exactly match my problem, it is so
> similar as to almost certainly be the cause. I would be happy to try
> applying that patch, but it's been a while since I built a patched
> Debian kernel so it may take a couple of days :-)
If that would be helpful, we have some instructions on "simple
patching and building" the kernel with a additional patches on top
here:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
Hope this helps for it.
Regards,
Salvatore
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
On Sun, Nov 20, 2022, at 08:15, Salvatore Bonaccorso wrote:
> Hi,
>
> On Sun, Nov 20, 2022 at 02:13:11PM +0100, Salvatore Bonaccorso wrote:
>> Control: tags -1 + moreinfo
>>
>> Hi,
>>
>> On Mon, Nov 14, 2022 at 06:34:43AM -0500, Kevin P. Fleming wrote:
>> > Package: src:linux
>> > Version: 6.0.7-1
>> > Severity: normal
>> > Tags: ipv6
>> >
>> > Dear Maintainer,
>> >
>> > This system has been operating for most of the last 12 months, using
>> > ProxyNDP on its external interface for eight addresses. After
>> > upgrading to the 6.0 kernel series, the kernel stops responding to ND
>> > solicitations for those addresses after startup... it does not happen
>> > immediately, but reliably occurs. When the system is in this state
>> > (not responding to ND solicitations for the proxy addresses), the
>> > proxy addresses are still shown in 'ip neigh show proxy', and the
>> > single non-proxy address on the same interface continues operating
>> > normally.
>> >
>> > Booting the system with the 5.19.0-2 kernel package cures the problem,
>> > with no other changes.
>> >
>> > Example output:
>> >
>> > root@net22:~# ip neigh show proxy
>> > 2607:5300:203:9743::1 dev ve-diw20 proxy
>> > 2607:5300:203:9743::1 dev ve-matrix20 proxy
>> > 2607:5300:203:9743::1 dev ve-ns3 proxy
>> > 2607:5300:203:9743::1 dev ve-ldl20 proxy
>> > 2607:5300:203:9743::1 dev ve-quassel21 proxy
>> > 2607:5300:203:9743::1 dev ve-mastodon22 proxy
>> > 2607:5300:203:9743::1 dev ve-monica21 proxy
>> > 2607:5300:203:9743::1 dev ve-mail20 proxy
>> > 2607:5300:203:9743:4::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:1::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:8::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:5::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:3::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:2::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:6::1 dev enp1s0f0 proxy
>> > 2607:5300:203:9743:7::1 dev enp1s0f0 proxy
>> >
>> > The addresses on enp1s0f0 are the ones which stop responding.
>>
>> Does the following matches your problem?
>>
>> https://lore.kernel.org/netdev/y295+9+jdjqrw...@x1.ze-it.at/
>>
>> Would you be able to test the mentioned patch to verify a fix for your
>> issue? The above changes fixes 0ff4eb3d5ebb ("neighbour: make
>> proxy_queue.qlen limit per-device") introduced in 6.0-rc2.
>
> For reference, the commit would be v2 as applied in netdev as
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8207f253a097fe15c93d85ac15ebb73c5e39e1e1
While that description does not exactly match my problem, it is so similar as
to almost certainly be the cause. I would be happy to try applying that patch,
but it's been a while since I built a patched Debian kernel so it may take a
couple of days :-)
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
Hi,
On Sun, Nov 20, 2022 at 02:13:11PM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Mon, Nov 14, 2022 at 06:34:43AM -0500, Kevin P. Fleming wrote:
> > Package: src:linux
> > Version: 6.0.7-1
> > Severity: normal
> > Tags: ipv6
> >
> > Dear Maintainer,
> >
> > This system has been operating for most of the last 12 months, using
> > ProxyNDP on its external interface for eight addresses. After
> > upgrading to the 6.0 kernel series, the kernel stops responding to ND
> > solicitations for those addresses after startup... it does not happen
> > immediately, but reliably occurs. When the system is in this state
> > (not responding to ND solicitations for the proxy addresses), the
> > proxy addresses are still shown in 'ip neigh show proxy', and the
> > single non-proxy address on the same interface continues operating
> > normally.
> >
> > Booting the system with the 5.19.0-2 kernel package cures the problem,
> > with no other changes.
> >
> > Example output:
> >
> > root@net22:~# ip neigh show proxy
> > 2607:5300:203:9743::1 dev ve-diw20 proxy
> > 2607:5300:203:9743::1 dev ve-matrix20 proxy
> > 2607:5300:203:9743::1 dev ve-ns3 proxy
> > 2607:5300:203:9743::1 dev ve-ldl20 proxy
> > 2607:5300:203:9743::1 dev ve-quassel21 proxy
> > 2607:5300:203:9743::1 dev ve-mastodon22 proxy
> > 2607:5300:203:9743::1 dev ve-monica21 proxy
> > 2607:5300:203:9743::1 dev ve-mail20 proxy
> > 2607:5300:203:9743:4::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:1::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:8::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:5::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:3::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:2::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:6::1 dev enp1s0f0 proxy
> > 2607:5300:203:9743:7::1 dev enp1s0f0 proxy
> >
> > The addresses on enp1s0f0 are the ones which stop responding.
>
> Does the following matches your problem?
>
> https://lore.kernel.org/netdev/y295+9+jdjqrw...@x1.ze-it.at/
>
> Would you be able to test the mentioned patch to verify a fix for your
> issue? The above changes fixes 0ff4eb3d5ebb ("neighbour: make
> proxy_queue.qlen limit per-device") introduced in 6.0-rc2.
For reference, the commit would be v2 as applied in netdev as
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8207f253a097fe15c93d85ac15ebb73c5e39e1e1
.
Regards,
Salvatore
Processed: Re: Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
Processing control commands: > tags -1 + moreinfo Bug #1024070 [src:linux] linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup Added tag(s) moreinfo. -- 1024070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
Control: tags -1 + moreinfo
Hi,
On Mon, Nov 14, 2022 at 06:34:43AM -0500, Kevin P. Fleming wrote:
> Package: src:linux
> Version: 6.0.7-1
> Severity: normal
> Tags: ipv6
>
> Dear Maintainer,
>
> This system has been operating for most of the last 12 months, using
> ProxyNDP on its external interface for eight addresses. After
> upgrading to the 6.0 kernel series, the kernel stops responding to ND
> solicitations for those addresses after startup... it does not happen
> immediately, but reliably occurs. When the system is in this state
> (not responding to ND solicitations for the proxy addresses), the
> proxy addresses are still shown in 'ip neigh show proxy', and the
> single non-proxy address on the same interface continues operating
> normally.
>
> Booting the system with the 5.19.0-2 kernel package cures the problem,
> with no other changes.
>
> Example output:
>
> root@net22:~# ip neigh show proxy
> 2607:5300:203:9743::1 dev ve-diw20 proxy
> 2607:5300:203:9743::1 dev ve-matrix20 proxy
> 2607:5300:203:9743::1 dev ve-ns3 proxy
> 2607:5300:203:9743::1 dev ve-ldl20 proxy
> 2607:5300:203:9743::1 dev ve-quassel21 proxy
> 2607:5300:203:9743::1 dev ve-mastodon22 proxy
> 2607:5300:203:9743::1 dev ve-monica21 proxy
> 2607:5300:203:9743::1 dev ve-mail20 proxy
> 2607:5300:203:9743:4::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:1::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:8::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:5::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:3::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:2::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:6::1 dev enp1s0f0 proxy
> 2607:5300:203:9743:7::1 dev enp1s0f0 proxy
>
> The addresses on enp1s0f0 are the ones which stop responding.
Does the following matches your problem?
https://lore.kernel.org/netdev/y295+9+jdjqrw...@x1.ze-it.at/
Would you be able to test the mentioned patch to verify a fix for your
issue? The above changes fixes 0ff4eb3d5ebb ("neighbour: make
proxy_queue.qlen limit per-device") introduced in 6.0-rc2.
Regards,
Salvatore
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
I am also experiencing this, using the latest linux-image-6.0.0-4-amd64 -- *Thomas van Gulick* tho...@van.gulick.nl Telegram: http://t0mm1e.t.me WhatsApp: http://wa.me/31651202680 Messenger: http://m.me/t0mm1e
Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup
Package: src:linux Version: 6.0.7-1 Severity: normal Tags: ipv6 Dear Maintainer, This system has been operating for most of the last 12 months, using ProxyNDP on its external interface for eight addresses. After upgrading to the 6.0 kernel series, the kernel stops responding to ND solicitations for those addresses after startup... it does not happen immediately, but reliably occurs. When the system is in this state (not responding to ND solicitations for the proxy addresses), the proxy addresses are still shown in 'ip neigh show proxy', and the single non-proxy address on the same interface continues operating normally. Booting the system with the 5.19.0-2 kernel package cures the problem, with no other changes. Example output: root@net22:~# ip neigh show proxy 2607:5300:203:9743::1 dev ve-diw20 proxy 2607:5300:203:9743::1 dev ve-matrix20 proxy 2607:5300:203:9743::1 dev ve-ns3 proxy 2607:5300:203:9743::1 dev ve-ldl20 proxy 2607:5300:203:9743::1 dev ve-quassel21 proxy 2607:5300:203:9743::1 dev ve-mastodon22 proxy 2607:5300:203:9743::1 dev ve-monica21 proxy 2607:5300:203:9743::1 dev ve-mail20 proxy 2607:5300:203:9743:4::1 dev enp1s0f0 proxy 2607:5300:203:9743:1::1 dev enp1s0f0 proxy 2607:5300:203:9743:8::1 dev enp1s0f0 proxy 2607:5300:203:9743:5::1 dev enp1s0f0 proxy 2607:5300:203:9743:3::1 dev enp1s0f0 proxy 2607:5300:203:9743:2::1 dev enp1s0f0 proxy 2607:5300:203:9743:6::1 dev enp1s0f0 proxy 2607:5300:203:9743:7::1 dev enp1s0f0 proxy The addresses on enp1s0f0 are the ones which stop responding. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: GIGABYTE product_name: MX33-BS1-V1 product_version: 0100 chassis_vendor: GIGABYTE chassis_version: To be filled by O.E.M. bios_vendor: GIGABYTE bios_version: F04a board_vendor: GIGABYTE board_name: MX33-BS1-V1 board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4c53] (rev 01) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Device [1458:1000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: icl_uncore 00:08.0 System peripheral [0880]: Intel Corporation Device [8086:4c11] (rev 01) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Device [1458:1000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:12.0 Serial controller [0700]: Intel Corporation Tiger Lake-H Integrated Sensor Hub [8086:43fc] (rev 11) (prog-if 00 [8250]) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H Integrated Sensor Hub [1458:1000] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: intel_ish_ipc 00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller [8086:43ed] (rev 11) (prog-if 30 [XHCI]) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller [1458:1000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-H Shared SRAM [8086:43ef] (rev 11) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H Shared SRAM [1458:1000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 [8086:43e8] (rev 11) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H Serial IO I2C Controller [1458:1000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Tiger Lake-H Management Engine Interface [8086:43e0] (rev 11) DeviceName: Onboard - Other Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H Management Engine Interface [1458:1000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
