From: Stephen Hemminger <stephen@networkplumber.org>
To: linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Fw: [Bug 212741] New: unregister_netdevice: waiting for enp0s20f0u1 to become free.
Date: Wed, 21 Apr 2021 09:49:10 -0700 [thread overview]
Message-ID: <20210421094910.2ccf58b3@hermes.local> (raw)
Looks like a USB driver network device ref count bug.
Begin forwarded message:
Date: Wed, 21 Apr 2021 08:39:38 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 212741] New: unregister_netdevice: waiting for enp0s20f0u1 to become free.
https://bugzilla.kernel.org/show_bug.cgi?id=212741
Bug ID: 212741
Summary: unregister_netdevice: waiting for enp0s20f0u1 to
become free.
Product: Networking
Version: 2.5
Kernel Version: 5.11.14
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: dexter+kernelbugzilla@beetjevreemd.nl
Regression: No
This problem exists for years by now, I could work around it until now.
Somewhere around kernel 4.9 ish this problem started to appear.
I have an USB network adapter and whenever the connection is severed (because I
touch the cable, USB reset, sleep, cosmic rays) the kernel starts logging below
message every 10~ish seconds. The usagecount is always different, but increases
with uptime. I can replicate this on all my laptops and workstations.
My setup is quite straigtforward, just (networkmanager)DHCP and a wireguard
VPN. Running Fedora 33 (but exists since like 26 or so).
[ 992.787930] unregister_netdevice: waiting for enp0s20f0u1 to become free.
Usage count = 8113
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-04-21 16:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210421094910.2ccf58b3@hermes.local \
--to=stephen@networkplumber.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.