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

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

Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26)

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

Contents

  Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26) Lauri Tirkkonen <lauri@hacktheplanet.fi> - 2021-04-08 09:40 +0200
    Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26) наб <nabijaczleweli@nabijaczleweli.xyz> - 2021-04-10 06:20 +0200
    Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26) Francesc Ferrer <francesc.ferrer@gmail.com> - 2021-04-10 19:40 +0200
    Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26) Salvatore Bonaccorso <carnil@debian.org> - 2021-04-14 16:10 +0200
    Bug#986619: marked as done (linux-image-5.10.0-5-amd64: bonding  broken on 5.10.0-5 (5.10.26)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-04-14 16:10 +0200

#70058 — Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26)

Package: src:linux
Version: 5.10.26-1
Severity: normal

Dear Maintainer,

I have a bonding setup as follows:

	% head -99 /etc/systemd/network/*
	==> /etc/systemd/network/bond0.netdev <==
	[NetDev]
	Name=bond0
	Kind=bond

	[Bond]
	Mode=active-backup
	PrimaryReselectPolicy=always
	MIIMonitorSec=1s

	==> /etc/systemd/network/bond0.network <==
	[Match]
	Name=bond0

	[Network]
	DHCP=yes
	LLMNR=false

	==> /etc/systemd/network/wired.network <==
	[Match]
	Name=enp*

	[Link]
	RequiredForOnline=no

	[Network]
	Bond=bond0
	PrimarySlave=true

	==> /etc/systemd/network/wireless.network <==
	[Match]
	Name=wlan*

	[Link]
	RequiredForOnline=no

	[Network]
	Bond=bond0

on 5.10.0-4, this works fine. On 5.10.0-5, networkd is able to get an
IPv4 address from DHCP on bond0, but not v6, and not even ping responses
arrive from my gateway. The underlying devices work fine on both kernel
versions.

I believe this is fixed in 5.10.27 with commit
36478a9ec5afd4efd031527d0371bf8f61e5aa91; see
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.27

Please update to 5.10.27 or backport the patch in question.

-- Package-specific info:
** Kernel log: boot messages should be attached

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

Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.10.0-5-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod                                    28-1
ii  linux-base                              4.6

Versions of packages linux-image-5.10.0-5-amd64 recommends:
ii  apparmor             2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-5-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  grub-efi-amd64          2.04-17
pn  linux-doc-5.10          <none>

Versions of packages linux-image-5.10.0-5-amd64 is related to:
pn  firmware-amd-graphics     <none>
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>
ii  firmware-iwlwifi          20210315-2
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
ii  firmware-misc-nonfree     20210315-2
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

-- 
Lauri Tirkkonen | lotheac @ IRCnet

[toc] | [next] | [standalone]

#70072

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

Hi!

Just hit this, great time, I'd just like to narrow down this regression,
the previous 5.10.0-5 (5.10.24) works fine, but 5.10.26 is broken.

Best,
наб

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

#70074

I can confirm this behaviour. I also have wired and wireless bonded, and 
it stopped working on 5.10.0-5. Everything looks fine: bond, gateway, 
DNS, ... all have correct if addresses obtained from dhcp; resolvectl 
looks fine; but I cannot even ping my gateway/router.

--
Francesc

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

#70135

Source: linux
Source-Version: 5.10.28-1

On Thu, Apr 08, 2021 at 10:23:55AM +0300, Lauri Tirkkonen wrote:
> Package: src:linux
> Version: 5.10.26-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I have a bonding setup as follows:
> 
> 	% head -99 /etc/systemd/network/*
> 	==> /etc/systemd/network/bond0.netdev <==
> 	[NetDev]
> 	Name=bond0
> 	Kind=bond
> 
> 	[Bond]
> 	Mode=active-backup
> 	PrimaryReselectPolicy=always
> 	MIIMonitorSec=1s
> 
> 	==> /etc/systemd/network/bond0.network <==
> 	[Match]
> 	Name=bond0
> 
> 	[Network]
> 	DHCP=yes
> 	LLMNR=false
> 
> 	==> /etc/systemd/network/wired.network <==
> 	[Match]
> 	Name=enp*
> 
> 	[Link]
> 	RequiredForOnline=no
> 
> 	[Network]
> 	Bond=bond0
> 	PrimarySlave=true
> 
> 	==> /etc/systemd/network/wireless.network <==
> 	[Match]
> 	Name=wlan*
> 
> 	[Link]
> 	RequiredForOnline=no
> 
> 	[Network]
> 	Bond=bond0
> 
> on 5.10.0-4, this works fine. On 5.10.0-5, networkd is able to get an
> IPv4 address from DHCP on bond0, but not v6, and not even ping responses
> arrive from my gateway. The underlying devices work fine on both kernel
> versions.
> 
> I believe this is fixed in 5.10.27 with commit
> 36478a9ec5afd4efd031527d0371bf8f61e5aa91; see
> https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.27
> 
> Please update to 5.10.27 or backport the patch in question.

This is fixed with the 5.10.28-1 upload.

Regards,
Salvatore

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

#70137 — Bug#986619: marked as done (linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26))

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

Your message dated Wed, 14 Apr 2021 16:04:16 +0200
with message-id <YHb2YCEeaI9WqCWN@eldamar.lan>
and subject line Re: Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26)
has caused the Debian Bug report #986619,
regarding linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
986619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986619
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

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

csiph-web