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

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

Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN"

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN" Ben Hutchings <ben@decadent.org.uk> - 2025-10-21 22:30 +0200
    Processed: Re: Bug#1118465: Regression: linux-image-5.10.0-36-arm64  fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN" "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-10-21 22:30 +0200
    Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN" Salvatore Bonaccorso <carnil@debian.org> - 2025-10-22 14:50 +0200
    Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN" Axel Beckert <abe@debian.org> - 2025-10-23 16:50 +0200
      Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN" Axel Beckert <abe@debian.org> - 2025-11-08 18:40 +0100
        Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN" Salvatore Bonaccorso <carnil@debian.org> - 2025-11-08 22:00 +0100

#89706 — Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN"

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

Control: tag -1 upstream patch moreinfo

Does this patch fix it?

Ben.

-- 
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump of a severed limb. - me, 29 June 1999

[toc] | [next] | [standalone]

#89707 — Processed: Re: Bug#1118465: Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN"

Processing control commands:

> tag -1 upstream patch moreinfo
Bug #1118465 [src:linux] Regression: linux-image-5.10.0-36-arm64 fails to bring up LAN7800 USB NIC: "NO-CARRIER" and "state DOWN"
Added tag(s) moreinfo, upstream, and patch.

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

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

#89719

Hi Ben,

In case Axel can confirm, there is a "off-by-one" in one of the Fixes:

On Tue, Oct 21, 2025 at 10:27:37PM +0200, Ben Hutchings wrote:
> Control: tag -1 upstream patch moreinfo
> 
> Does this patch fix it?
> 
> Ben.
> 
> -- 
> Ben Hutchings
> Editing code like this is akin to sticking plasters on the bleeding
> stump of a severed limb. - me, 29 June 1999

> From 4f97e494a3e2500166be4e8b53b4c412d6a44a9f Mon Sep 17 00:00:00 2001
> From: Ben Hutchings <benh@debian.org>
> Date: Tue, 21 Oct 2025 22:18:49 +0200
> Subject: [PATCH] usbnet: Report link up even when the interface is not yet up
> 
> Even after commit 466d393700f9 ("net: usbnet: Fix the wrong
> netif_carrier_on() call"), usbnet isn't calling netif_carrier_on() in
> all the same cases it would before.  Specifically, if the link is
> reported up before EVENT_DEV_OPEN is set, netif_carrier_on() may no
> longer be called.
> 
> Fix this by checking for EVENT_LINK_CARRIER_ON first in
> __handle_link_change(), before EVENT_DEV_OPEN.
> 
> References: https://bugs.debian.org/1118465
> Reported-by: Axel Beckert <axel@ethz.ch>
> Fixes: 0d9cfc9b8cb1 ("net: usbnet: Avoid potential RCU stall on LINK_CHANGE event")
> Fixes: 466d393700f9 ("net: usbnet: Fix the wrong netif_carrier_on() call")

Should that be
Fixes: 8466d393700f ("net: usbnet: Fix the wrong netif_carrier_on() call")
?

Spotted it while checking to see ee which other stable series are affected.

Regards,
Salvatore

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

#89731

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

Hi Ben,

Ben Hutchings wrote:
> Control: tag -1 upstream patch moreinfo
> 
> Does this patch fix it?

Thanks a lot for the prompt reply with a patch.

Unfortunately that patch does not seem to help. I've cross-checked
several times that the patch is really applied:

# uname -a
Linux XXXXX-mgmt-gw-XXXXXX 5.10.0-0.a.test-arm64 #1 SMP Debian 5.10.244-1a~test (2025-10-23) aarch64

$ fgrep usbnet-Report-link-up-even-when-the-interface-is-not.patch linux_5.10.244-1a~test_arm64.build
File series fully applied, ends at patch test/0001-usbnet-Report-link-up-even-when-the-interface-is-not.patch

But we still the same symptoms:

# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether e4:5f:01:3d:98:95 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
          ^^^^^^^^^^                                                   ^^^^^^^^^^
link/ether 2c:f7:f1:1b:eb:83 brd ff:ff:ff:ff:ff:ff
5: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/none 

Is there anything else I can do or extract while running under either
kernel, the one with this patch or the -36-?

Back on the -35- kernel for now.

Now I can also check further patches quicker as I now have the proper
arm64 package build setup to do so without wearing down the eMMC on
the production host nor with running out of disk space. :-)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

#89956

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

Control: fixed -1 6.1.153-1

Hi Ben,

> Ben Hutchings wrote:
> > Control: tag -1 upstream patch moreinfo
> > 
> > Does this patch fix it?
> 
> Thanks a lot for the prompt reply with a patch.
> 
> Unfortunately that patch does not seem to help.

I was locally at the host yesterday and experimented at bit. Something
else helped: Using the latest linux-image-6.1.0-40-arm64 kernel from
Debian 12 Bookworm (version 6.1.153-1) didn't show this issue.

I also see (only now) that there are linux-image-6.1.0-0.deb11.*
packages available in the bullseye-security repo—albeit no ABI number
40 yet—so I'd say the way forward to close this bug report is Bullseye
LTS switching to the 6.1 kernel series (which I assume is imminent
anyways).

For our specific case the way forward will be the dist-upgrade of the
whole host (not just the kernel) to at least Debian 12.

Thanks for all the help nevertheless!

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

#89963

Hi,

On Sat, Nov 08, 2025 at 06:33:17PM +0100, Axel Beckert wrote:
> Control: fixed -1 6.1.153-1
> 
> Hi Ben,
> 
> > Ben Hutchings wrote:
> > > Control: tag -1 upstream patch moreinfo
> > > 
> > > Does this patch fix it?
> > 
> > Thanks a lot for the prompt reply with a patch.
> > 
> > Unfortunately that patch does not seem to help.
> 
> I was locally at the host yesterday and experimented at bit. Something
> else helped: Using the latest linux-image-6.1.0-40-arm64 kernel from
> Debian 12 Bookworm (version 6.1.153-1) didn't show this issue.

Ok that is at least in part good news, myabe not yet or 5.10.y and
bullseye.

> I also see (only now) that there are linux-image-6.1.0-0.deb11.*
> packages available in the bullseye-security repo—albeit no ABI number
> 40 yet—so I'd say the way forward to close this bug report is Bullseye
> LTS switching to the 6.1 kernel series (which I assume is imminent
> anyways).
> 
> For our specific case the way forward will be the dist-upgrade of the
> whole host (not just the kernel) to at least Debian 12.

Note that linux-6.1 packages are not meant to replace the src:linux
(based on 5.10.y) but are somehow in a first stance a continuation of
the backports provided kernels from the upper suite of bullseye, as
backports is discontinued under LTS. But then, once bullseye moves
under freexian's ELTS as I understand there are provided several
stable series verisons from the upper suites as well in separate
packages.

Ben can probably explain better here.

IMHo if you can upgrade it is still the bet way forward that you
upgrade to at least bookworm, better trixie.

Regards,
Salvatore

[toc] | [prev] | [standalone]

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

csiph-web