cdc_ncm floods syslog unneccessarily

[Ernst Ahlers]

Upon plugging in a USB adapter for NBase-T ethernet with an Realtek chip RTL8156 the kernel module cdc_ncm starts flooding /var/log/syslog with unneccessary status info.

The status lines either say that there's no ethernet link or show the interface as connected and state the link speed.

The relevant parts from /var/log/syslog after attaching the adapter without ethernet link read like this:

[...]
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.398485] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419463] usb 2-3: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=30.00
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419469] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419472] usb 2-3: Product: USB 10/100/1G/2.5G LAN
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419475] usb 2-3: Manufacturer: Realtek
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419477] usb 2-3: SerialNumber: 000000001
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447769] cdc_ncm 2-3:2.0: MAC-Address: 00:13:3b:68:00:e9
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447775] cdc_ncm 2-3:2.0: setting rx_max = 16384
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447929] cdc_ncm 2-3:2.0: setting tx_max = 16384
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.448901] cdc_ncm 2-3:2.0 usb0: register 'cdc_ncm' at usb-0000:00:14.0-3, CDC NCM, 00:13:3b:68:00:e9
Jun 12 10:48:58 resdz-v13 NetworkManager[916]: <info> [1560329338.1872] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8)
Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device
Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Using default interface naming scheme 'v240'.
Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.466476] cdc_ncm 2-3:2.0 enx00133b6800e9: renamed from usb0
Jun 12 10:48:58 resdz-v13 NetworkManager[916]: <info> [1560329338.2315] device (usb0): interface index 7 renamed iface from 'usb0' to 'enx00133b6800e9'
Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Process 'vlan-network-interface UDEV' failed with exit code 1.
Jun 12 10:48:58 resdz-v13 NetworkManager[916]: <info> [1560329338.2431] device (enx00133b6800e9): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 12 10:48:58 resdz-v13 charon: 12[KNL] interface enx00133b6800e9 activated
Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.524052] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.556109] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.588054] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.620383] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected
Jun 12 10:48:58 resdz-v13 kernel: [ 4240.652415] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected
[...]

Upon plugging in the ethernet cable I see
[...]
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.372273] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.404278] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
[...]
and Network Manager starts its work.

After the interface is up the flooding continues:
[...]
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.564056] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.596051] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4
Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4
Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4
Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] online
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.628055] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.660060] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.692055] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.724054] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.756060] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.788053] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.820056] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.852060] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.884064] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.916054] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.948055] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4243.980049] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
Jun 12 10:49:01 resdz-v13 kernel: [ 4244.012056] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
Jun 12 10:49:01 resdz-v13 kernel: [ 4244.044053] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected
[...]

Expected behavior is showing the status lines only once after link status changes.

Kernel version is: 5.0.0-16-generic, OS: Kubuntu 19.04

Module info for cdc_ncm:

filename: /lib/modules/5.0.0-16-generic/kernel/drivers/net/usb/cdc_ncm.ko
license: Dual BSD/GPL
description: USB CDC NCM host driver
author: Hans Petter Selasky
srcversion: 9CC08FECEC9EC4AF1DBA207
alias: usb:v*p*d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v1546p1010d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v1519p0443d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v12D1p*d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v0930p*d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v413Cp*d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v413Cp81BCd*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v413Cp81BBd*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v1BC7p0036d*dc*dsc*dp*ic02isc0Dip00in*
alias: usb:v0BDBp*d*dc*dsc*dp*ic02isc0Dip00in*
depends: usbnet
retpoline: Y
intree: Y
name: cdc_ncm
vermagic: 5.0.0-16-generic SMP mod_unload
sig_id: PKCS#7
signer:
sig_key:
sig_hashalgo: md4
signature: 30:82:02:A5:06:09:2A:86:48:86:F7:0D:01:07:02:A0:82:02:96:30:
  82:02:92:02:01:01:31:0D:30:0B:06:09:60:86:48:01:65:03:04:02:
  03:30:0B:06:09:2A:86:48:86:F7:0D:01:07:01:31:82:02:6F:30:82:
  02:6B:02:01:01:30:46:30:2E:31:2C:30:2A:06:03:55:04:03:0C:23:
  42:75:69:6C:64:20:74:69:6D:65:20:61:75:74:6F:67:65:6E:65:72:
  61:74:65:64:20:6B:65:72:6E:65:6C:20:6B:65:79:02:14:6C:D7:37:
  E7:FA:BA:B9:CE:27:58:03:41:8C:55:76:76:23:DB:D6:27:30:0B:06:
  09:60:86:48:01:65:03:04:02:03:30:0D:06:09:2A:86:48:86:F7:0D:
  01:01:01:05:00:04:82:02:00:4D:14:7A:17:B0:09:83:C0:B7:24:84:
  3C:33:F0:C6:CA:70:11:69:13:F5:CC:57:11:1F:DA:AD:05:5A:A5:44:
  7F:A1:3C:9E:C1:A0:F5:0F:D1:1E:29:A9:A3:5C:61:24:0E:59:EA:83:
  C5:B2:1D:A5:2A:FD:22:E0:B3:22:0F:CC:62:D8:EB:DE:51:22:FB:D4:
  19:78:FA:36:65:BE:81:58:F2:D8:F8:4C:76:07:6A:4F:99:01:DC:DD:
  73:10:3C:D4:60:0A:CE:1E:E3:30:58:83:1F:1E:A1:ED:FF:01:D2:8F:
  74:01:74:3E:A7:56:DC:E8:3C:56:BA:DB:2A:EE:69:B0:16:88:46:41:
  2F:18:19:01:46:F0:A9:22:C9:48:C7:DA:DB:43:67:8A:97:9E:CB:AB:
  63:36:9E:31:61:34:5A:D3:77:76:01:19:A0:08:B3:C0:83:B0:53:FE:
  F3:92:7C:38:ED:41:A3:FB:84:29:86:04:B0:08:50:B1:C8:28:49:0D:
  9C:22:30:43:62:7F:BC:F2:88:08:09:50:0F:FE:09:AD:E4:22:FA:3B:
  B6:5F:95:7E:48:E0:0D:62:D2:F0:35:6C:21:BD:8B:54:9A:5A:32:CE:
  0D:71:F5:80:1B:52:3D:1F:45:4D:B2:10:6C:7B:49:E0:3D:D7:5A:22:
  94:A1:8B:99:8E:09:90:A7:41:43:FF:FC:DC:FE:21:D3:90:87:F9:34:
  C3:7C:2D:46:A9:3F:20:36:D3:99:1F:D5:34:5C:E6:F2:D5:B2:8D:09:
  15:ED:D1:E7:ED:DE:49:4C:B4:A9:FD:5E:35:47:86:75:A7:64:BB:1F:
  1C:85:58:8C:CF:C0:F7:52:DB:79:3F:76:22:6D:13:ED:5B:99:E1:5A:
  D2:01:1D:54:80:20:78:D8:33:B2:61:15:3A:44:BC:0D:C5:2C:7D:32:
  C6:26:CE:39:46:DA:64:9D:83:95:A3:01:82:D3:87:7F:48:DC:CA:40:
  F5:41:DC:BA:0F:96:C0:88:97:DD:5B:B4:80:0C:33:B9:CE:C0:97:D0:
  C4:94:B2:24:5E:D3:9C:0D:1E:99:27:13:51:9D:8A:1D:F7:04:9C:7C:
  11:DD:78:7A:29:DE:06:1A:61:C4:D7:4B:49:C7:4C:EE:0D:6A:15:47:
  AF:E7:31:4B:1E:C8:A0:B5:A2:24:EB:3F:37:2A:98:93:A0:D5:CE:A3:
  EE:78:38:FC:11:7D:4B:8C:2E:FF:9C:95:0E:CE:03:2A:73:A3:A1:FC:
  48:71:97:3B:C3:09:F3:D5:AD:99:AB:8E:51:18:DC:6B:1A:85:DA:E3:
  40:4B:D2:E8:E4:AF:82:1E:F5:19:D2:ED:35:D5:1A:83:D7:2D:20:4A:
  1C
parm: prefer_mbim:Prefer MBIM setting on dual NCM/MBIM functions (bool)
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ea 1471 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.04
HibernationDevice: RESUME=UUID=9fa3d55c-f7fc-46af-b84e-f841e37ac50c
InstallationDate: Installed on 2016-06-30 (1077 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Acer Aspire V3-372
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=26301cd2-9196-4509-9d2a-43d821b74945 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-16-generic N/A
 linux-backports-modules-5.0.0-16-generic N/A
 linux-firmware 1.178.1
Tags: disco
Uname: Linux 5.0.0-16-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-04-24 (49 days ago)
UserGroups: adm lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 06/06/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V3-372
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd06/06/2016:svnAcer:pnAspireV3-372:pvrV1.08:rvnAcer:rnAspireV3-372:rvrV1.08:cvnAcer:ct10:cvrV1.08:
dmi.product.family: SKL
dmi.product.name: Aspire V3-372
dmi.product.sku: Aspire V3-372_104C_1.08
dmi.product.version: V1.08
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ea 1471 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.04
HibernationDevice: RESUME=UUID=9fa3d55c-f7fc-46af-b84e-f841e37ac50c
InstallationDate: Installed on 2016-06-30 (1077 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 003: ID 04f2:b526 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire V3-372
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=26301cd2-9196-4509-9d2a-43d821b74945 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-16-generic N/A
 linux-backports-modules-5.0.0-16-generic N/A
 linux-firmware 1.178.1
Tags: disco
Uname: Linux 5.0.0-16-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-04-24 (49 days ago)
UserGroups: adm lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 06/06/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V3-372
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd06/06/2016:svnAcer:pnAspireV3-372:pvrV1.08:rvnAcer:rnAspireV3-372:rvrV1.08:cvnAcer:ct10:cvrV1.08:
dmi.product.family: SKL
dmi.product.name: Aspire V3-372
dmi.product.sku: Aspire V3-372_104C_1.08
dmi.product.version: V1.08
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-06-30 (1082 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
Tags: disco
Uname: Linux 5.2.0-050200rc5-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to disco on 2019-04-24 (54 days ago)
UserGroups: adm lpadmin plugdev sambashare sudo users
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-06-30 (1082 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
Tags: disco
Uname: Linux 5.2.0-050200rc5-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to disco on 2019-04-24 (54 days ago)
UserGroups: adm lpadmin plugdev sambashare sudo users
_MarkForUpload: True

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1832472

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/

[Ernst Ahlers (eactde)]

With 5.2.0-050200rc5-generic I'm getting the same behavior. Apport follows.

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Ernst Ahlers (eactde)]

apport information

[Gauthier Provost (gprovost)]

Same exact issue with TRENDnet TUC-ET2G (USB-C 3.1 to 2.5GBASE-T Ethernet Adapter) on Ubuntu 18.04.2 with kernel 4.18.0-22-generic.

[Gauthier Provost (gprovost)]

Not sure if it could be related to this old bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371

Which has been fixed through this commit : https://lists.ubuntu.com/archives/kernel-team/2016-December/081565.html

BTW the TRENDnet TUC-ET2G based on Aquantia AQtion AQC112U controller has the following ids:
idVendor=20f4, idProduct=e02b.

[Kai-Heng Feng (kaihengfeng)]

This is because the upstream driver doesn't support Realtek 8156 (yet).

Please ask Realtek to upstream their driver, and use [1] for the interim.

[1] https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-usb-3-0-software

[Gauthier Provost (gprovost)]

I was mistaken, the TRENDnet TUC-ET2G is actually based on RTL8156 while the TUC-ET5G is effectively based on Aquantia IC. I made wrong assumption since Aquantia also has a USB3.0 to ETH 2.5Gbe bridge.

Anyhow, so I tested with RTL8156 driver you linked (which actually is part of RTL8152 driver) under Ubuntu 18.04.2. I had to tweaked driver to support TUC-ET2G by adding the idVendor and idProduct of the device. Could have used a modprobe conf file instead of tweaking the code.

Now the device works well without flooding anymore the logs !

[stuart naylor (stuartiannaylor68)]

Apols but looking you guys are knowledgeable with cdc_ncm

With the RTL8156 the rk3399 struggles slighlty with iperf3 @ 2.5gb but almost gets there.

Needs affinity to a big core though

[root@rockpi4 ~]# echo 5 > /proc/irq/221/smp_affinity_list
[root@rockpi4 ~]# iperf3 -c 192.168.1.9
Connecting to host 192.168.1.9, port 5201
[ 5] local 192.168.1.12 port 50268 connected to 192.168.1.9 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 251 MBytes 2.10 Gbits/sec 10 252 KBytes
[ 5] 1.00-2.00 sec 263 MBytes 2.21 Gbits/sec 0 252 KBytes
[ 5] 2.00-3.00 sec 255 MBytes 2.13 Gbits/sec 10 211 KBytes
[ 5] 3.00-4.00 sec 258 MBytes 2.17 Gbits/sec 20 182 KBytes
[ 5] 4.00-5.00 sec 258 MBytes 2.16 Gbits/sec 10 214 KBytes
[ 5] 5.00-6.00 sec 263 MBytes 2.22 Gbits/sec 0 214 KBytes
[ 5] 6.00-7.01 sec 257 MBytes 2.14 Gbits/sec 20 264 KBytes
[ 5] 7.01-8.00 sec 264 MBytes 2.22 Gbits/sec 0 264 KBytes
[ 5] 8.00-9.00 sec 257 MBytes 2.16 Gbits/sec 10 232 KBytes
[ 5] 9.00-10.00 sec 258 MBytes 2.17 Gbits/sec 10 234 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 2.52 GBytes 2.17 Gbits/sec 90 sender
[ 5] 0.00-10.00 sec 2.52 GBytes 2.17 Gbits/sec

What is confusing me is on Arm64 when you act as server/slave to a client the throughput drops drastically.

[root@rockpi4 ~]# iperf3 -c 192.168.1.9 -R
Connecting to host 192.168.1.9, port 5201
Reverse mode, remote host 192.168.1.9 is sending
[ 5] local 192.168.1.12 port 50280 connected to 192.168.1.9 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 51.9 MBytes 435 Mbits/sec
[ 5] 1.00-2.00 sec 46.2 MBytes 388 Mbits/sec
[ 5] 2.00-3.00 sec 48.4 MBytes 406 Mbits/sec
[ 5] 3.00-4.00 sec 46.2 MBytes 387 Mbits/sec
[ 5] 4.00-5.00 sec 59.9 MBytes 502 Mbits/sec
[ 5] 5.00-6.00 sec 53.2 MBytes 446 Mbits/sec
[ 5] 6.00-7.00 sec 48.6 MBytes 408 Mbits/sec
[ 5] 7.00-8.00 sec 56.8 MBytes 477 Mbits/sec
[ 5] 8.00-9.00 sec 45.8 MBytes 384 Mbits/sec
[ 5] 9.00-10.00 sec 48.9 MBytes 410 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 506 MBytes 424 Mbits/sec sender
[ 5] 0.00-10.00 sec 506 MBytes 424 Mbits/sec receiver

I don't understand why acting as a client to server should have this much difference?
Please post on Armbian https://forum.armbian.com/messenger/1867/?tab=comments#comment-14491 if you have any idea and apols but really struggling to find any info or mention about the rtl8156

[cookiEoverdose (cookieoverdose)]

Is there a way for a normal user to fix the log spamming? I bought a RTL8156 based USB adapter but it's making the journal unusable. It is adding 30+ kernel messages per second and consuming pointless io / cpu cycles (system-journald, i.e. 5% permanent cpu usage on my Pi4).

[Kai-Heng Feng (kaihengfeng)]

Well, use the Realtek r8156 driver until they made it upstream.

[Grant Grundler (grundler-google)]

Chrome OS also can't support RTL8156 until this is fixed. Every kernel version Chrome OS uses spams /var/log/syslog with ~30 messages/second (~200MB/day or ~1GB/week). We can not use the Realtek "proprietary" (though open source) driver.

Realtek needs to look at this and I've contacted Realtek directly about this.

I can't determine what is triggering the repeated link status messages from USB CDC specs. From what I understand in the spec, USB_CDC_NOTIFY_SPEED_CHANGE and USB_CDC_NOTIFY_NETWORK_CONNECTION (in that order) messages should only be sent once after device is enumerated and again when link state actually changes. This is in fact how cdc_ether devices behave using the same messages.