Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #77076 > unrolled thread

Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup "Kevin P. Fleming" <debian@kevin.km6g.us> - 2022-11-14 12:40 +0100
    Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup Thomas van Gulick <thomas@van.gulick.nl> - 2022-11-19 17:00 +0100
    Processed: Re: Bug#1024070: linux-image-6.0.0-3-amd64: IPv6  ProxyNDP stops responding to ND solicitation some time after startup "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-11-20 14:20 +0100
    Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup Salvatore Bonaccorso <carnil@debian.org> - 2022-11-20 14:20 +0100
      Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup Salvatore Bonaccorso <carnil@debian.org> - 2022-11-20 14:20 +0100
    Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup Salvatore Bonaccorso <carnil@debian.org> - 2022-11-20 14:50 +0100
    Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup Salvatore Bonaccorso <carnil@debian.org> - 2022-11-24 07:50 +0100

#77076 — 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: 00000000

** 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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	IOMMU group: 0
	Expansion ROM at <ignored>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 11
	IOMMU group: 1
	Region 0: Memory at a322e000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	IOMMU group: 2
	Region 0: Memory at a3210000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 123
	IOMMU group: 3
	Region 0: Memory at a3200000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	IOMMU group: 3
	Region 0: Memory at a3220000 (64-bit, non-prefetchable) [size=16K]
	Region 2: Memory at a322d000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 27
	IOMMU group: 4
	Region 0: Memory at 4000000000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	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- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	IOMMU group: 5
	Region 0: Memory at a322b000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel modules: mei_me

00:16.1 Communication controller [0780]: Intel Corporation Device [8086:43e1] (rev 11)
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	IOMMU group: 5
	Region 0: Memory at a322a000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>

00:16.4 Communication controller [0780]: Intel Corporation Device [8086:43e4] (rev 11)
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	IOMMU group: 5
	Region 0: Memory at a3229000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>

00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11) (prog-if 01 [AHCI 1.0])
	DeviceName: Onboard - SATA
	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=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 124
	IOMMU group: 6
	Region 0: Memory at a3224000 (32-bit, non-prefetchable) [size=8K]
	Region 1: Memory at a3228000 (32-bit, non-prefetchable) [size=256]
	Region 2: I/O ports at 4050 [size=8]
	Region 3: I/O ports at 4040 [size=4]
	Region 4: I/O ports at 4020 [size=32]
	Region 5: Memory at a3227000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:43c4] (rev 11) (prog-if 00 [Normal decode])
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 121
	IOMMU group: 7
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: a2400000-a31fffff [size=14M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43b8] (rev 11) (prog-if 00 [Normal decode])
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 122
	IOMMU group: 8
	Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: a0000000-a20fffff [size=33M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA+ VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:438c] (rev 11)
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	IOMMU group: 9

00:1f.4 SMBus [0c05]: Intel Corporation Tiger Lake-H SMBus Controller [8086:43a3] (rev 11)
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H SMBus 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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	IOMMU group: 9
	Region 0: Memory at a3226000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller [8086:43a4] (rev 11)
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Tiger Lake-H SPI 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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	IOMMU group: 9
	Region 0: Memory at a2100000 (32-bit, non-prefetchable) [size=4K]

01:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller X550 [8086:1563] (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd Ethernet Controller X550 [1458:1000]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	IOMMU group: 10
	Region 0: Memory at a2800000 (64-bit, prefetchable) [size=4M]
	Region 4: Memory at a3104000 (64-bit, prefetchable) [size=16K]
	Expansion ROM at a2c80000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: ixgbe
	Kernel modules: ixgbe

01:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller X550 [8086:1563] (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd Ethernet Controller X550 [1458:1000]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	IOMMU group: 11
	Region 0: Memory at a2400000 (64-bit, prefetchable) [size=4M]
	Region 4: Memory at a3100000 (64-bit, prefetchable) [size=16K]
	Expansion ROM at a2c00000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: ixgbe
	Kernel modules: ixgbe

02:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150] (rev 04) (prog-if 00 [Normal decode])
	Subsystem: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	IOMMU group: 12
	Bus: primary=02, secondary=03, subordinate=03, sec-latency=32
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: a0000000-a20fffff [size=33M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA+ VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

03:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller])
	Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	IOMMU group: 12
	Region 0: Memory at a0000000 (32-bit, non-prefetchable) [size=32M]
	Region 1: Memory at a2000000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 3000 [size=128]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: ast
	Kernel modules: ast


** USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.0.0-3-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod                                    30+20220905-1
ii  linux-base                              4.9

Versions of packages linux-image-6.0.0-3-amd64 recommends:
ii  apparmor             3.0.7-1+b2
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.0.0-3-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-efi-amd64          2.06-4
pn  linux-doc-6.0           <none>

Versions of packages linux-image-6.0.0-3-amd64 is related to:
ii  firmware-amd-graphics     20221012-1
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
ii  firmware-linux-nonfree    20221012-1
ii  firmware-misc-nonfree     20221012-1
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#77143

[Multipart message — attachments visible in raw view] — view raw

I am also experiencing this, using the latest linux-image-6.0.0-4-amd64

-- 


*Thomas van Gulick*
thomas@van.gulick.nl

Telegram:  http://t0mm1e.t.me
WhatsApp:  http://wa.me/31651202680
Messenger: http://m.me/t0mm1e

[toc] | [prev] | [next] | [standalone]

#77151 — 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 owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77152

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+JDjqRWbwU@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

[toc] | [prev] | [next] | [standalone]

#77153

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+JDjqRWbwU@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

[toc] | [prev] | [next] | [standalone]

#77154

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+JDjqRWbwU@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

[toc] | [prev] | [next] | [standalone]

#77185

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web