Swisslinux.org

sssammm · 03 Apr 2022 12:30:21

Bonjour,

Utilisateur très satisfait d'un why! N131ZU depuis environs deux ans, je rencontre depuis peu un problème avec l'USB ethernet. La machine (Debian Bullseye avec Gnome et le pilote displaylink-debian) est connectée à un dock Lenovo ThinkPad USB-C Dock Gen2, lui-même connecté à plusieurs périphériques, dont un switch via ethernet.

Après environs 3-4 heures, pendant l'utilisation active de la machine, je perds la connexion réseau. Concrètement, alors que l'applet réseau indique "Ethernet USB connecté", il m'est impossible de naviguer sur Internet ou d'accéder à une autre machine en réseau local. Si je tente alors d'exécuter une commande quelconque avec `sudo`, le curseur de la console se bloque avant même que je puisse entrer un mot de passe. Cette situation dure une dizaine de minutes. Il en va de même si j'essaie de désactiver l'USB ethernet depuis l'applet, d'accéder aux paramètres réseau ou au moniteur système. Pendant ce temps, tout le rester fonctionne (connexions usb, écrans, autres programmes).

Finalement, la situation se débloque et j'obtiens un retour des commandes (ex: je peux entrer le mot de passe après un `sudo`). Toutefois, l'interface USB ethernet, bien qu'indiqué comme "connectée", reste inopérante. Je peux toutefois la désactiver, suite à quoi mon portable bascule immédiatement en wifi et la connexion réseau est pleinement rétablie. Si je tente ensuite de réactiver l'USB ethernet, j'obtiens un timeout. La seule solution trouvée jusqu'ici pour la réactiver est un reboot de la machine. Si je procède ainsi, je rencontre à nouveau le problème, mais cette fois après 30-45 minutes seulement.

J'ai tenté plusieurs actions, comme changer le câble USB-C, débrancher et rebrancher le câble ethernet sur le dock, malheureusement sans succès. Débrancher et rebrancher le câble USB-C "à chaud" cause un crash, ce qui est apparemment attendu (https://wiki.archlinux.org/title/Displa … ot_plugged). J'ai également trouvé ce lien: https://forum.manjaro.org/t/usb-etherne … ably/44755 . Si j'utilise bien tlp, le contenu du fichier `/etc/tlp.conf` est entièrement commenté. Je suppose donc qu'aucune mise en veille automatique n'a lieu. Il y a finalement ce fil de discussion sur le forum de Lenovo (https://forums.lenovo.com/t5/Optionen-u … -p/5029021) qui mentionne un bug du noyau (https://bugzilla.kernel.org/show_bug.cgi?id=198931 ), mais je ne suis pas certain qu'il s'agisse du même problème, étant donné que je retrouve un code `Tx status -2` et non pas `Tx status -71` dans `/var/log/syslog`.

J'utilise également le dock avec une machine Lenovo sous Windows et ne rencontre pas ce problème dans ce contexte.

Voici un extrait de ma configuration (commandes exécutées après l'apparition du problème):

Code:

$ inxi -Fxz
System:    Kernel: 5.10.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.6 
           Distro: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: WHY product: WHY v: N/A serial: <filter> 
           Mobo: WHY model: N13_N140ZU serial: <filter> UEFI: INSYDE v: 1.07.07RTR1 date: 05/13/2019 
Battery:   ID-1: BAT0 charge: 33.7 Wh condition: 33.7/35.3 Wh (95%) model: Notebook BAT status: Full 
           Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard charge: 55% (should be ignored) 
           status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Performance MX charge: 55% (should be ignored) status: Discharging 
CPU:       Info: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake note: check rev: C L2 cache: 8 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999 
           Speed: 700 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700 8: 700 
Graphics:  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 
           Display: wayland server: X.Org 1.20.11 compositor: gnome-shell driver: loaded: modesetting resolution: 
           1: 1920x1080~60Hz 2: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 
           Device-2: Lenovo ThinkPad USB-C Dock Gen2 USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus ID: 1-3.3.3.2:8 
           Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-3.3.3.4:10 
           Sound Server: ALSA v: k5.10.0-13-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel 
           port: 3000 bus ID: 39:00.1 
           IF: enp57s0f1 state: down mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: 3000 bus ID: 3a:00.0 
           IF: wlp58s0 state: up mac: <filter> 
           Device-3: Lenovo USB-C Dock Ethernet type: USB driver: r8152 bus ID: 4-1.1:3 
           IF: enx482ae39f03a1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           IF-ID-1: docker0 state: down mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus ID: 1-10:4 
           Report: ID: hci0 state: up running pscan iscan bt-v: 2.1 lmp-v: 4.2 address: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 1.54 TiB (84.8%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB size: 1.82 TiB temp: 39.9 C 
Partition: ID-1: / size: 1.76 TiB used: 1.54 TiB (87.8%) fs: ext4 dev: /dev/dm-0 
           mapped: luks-8a94add2-428a-4a15-998f-6f946c47e988 
           ID-2: /boot/efi size: 299.4 MiB used: 3.4 MiB (1.1%) fs: vfat dev: /dev/nvme0n1p1 
Swap:      ID-1: swap-1 type: partition size: 34.24 GiB used: 0 KiB (0.0%) dev: /dev/dm-1 
           mapped: luks-58c54596-fc1a-4088-841d-68af415574a1 
Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 329 Uptime: 40m Memory: 31.08 GiB used: 4.92 GiB (15.8%) Init: systemd runlevel: 5 Compilers: 
           gcc: 10.2.1 Packages: 5344 Shell: Bash v: 5.1.4 inxi: 3.3.01

Un extrait de dmesg

Code:

[ 1843.014670] NETDEV WATCHDOG: enx482ae39f03a1 (r8152): transmit queue 0 timed out
[ 1843.014712] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24d/0x260
[ 1843.014715] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc xfrm_user xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc ctr ccm rfcomm overlay vboxnetadp(OE) vboxnetflt(OE) cmac algif_hash algif_skcipher af_alg vboxdrv(OE) snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device bnep binfmt_misc cdc_ether usbnet r8152 mii btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 jitterentropy_rng videobuf2_common drbg videodev ansi_cprng ecdh_generic mc ecc snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_sof_intel_hda snd_hda_codec_realtek snd_soc_skl intel_rapl_msr snd_soc_hdac_hda snd_hda_codec_generic snd_hda_ext_core snd_soc_sst_ipc intel_rapl_common ledtrig_audio
[ 1843.014865]  snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_intel snd_intel_dspcfg mei_hdcp soundwire_intel iwlmvm soundwire_generic_allocation x86_pkg_temp_thermal intel_powerclamp snd_soc_core coretemp mac80211 snd_compress squashfs libarc4 soundwire_cadence kvm_intel snd_hda_codec kvm iwlwifi irqbypass snd_hda_core rapl snd_hwdep soundwire_bus intel_cstate nls_ascii intel_uncore snd_pcm nls_cp437 cfg80211 vfat fat joydev snd_timer mei_me intel_wmi_thunderbolt efi_pstore snd pcspkr iTCO_wdt intel_pmc_bxt iTCO_vendor_support serio_raw ee1004 watchdog rfkill mei soundcore intel_pch_thermal tpm_crb tpm_tis tpm_tis_core tpm intel_hid rng_core intel_pmc_core sparse_keymap acpi_pad ac evdev loop msr evdi(OE) parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic hid_logitech_hidpp hid_logitech_dj dm_crypt dm_mod hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
[ 1843.015030]  raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod crc32_pclmul crc32c_intel i915 ahci rtsx_pci_sdmmc libahci xhci_pci i2c_algo_bit ghash_clmulni_intel mmc_core xhci_hcd libata nvme drm_kms_helper aesni_intel nvme_core r8169 cec realtek libaes crypto_simd drm t10_pi crc_t10dif usbcore crct10dif_generic mdio_devres cryptd thunderbolt psmouse glue_helper libphy scsi_mod rtsx_pci i2c_i801 battery i2c_smbus crct10dif_pclmul crct10dif_common wmi usb_common video button
[ 1843.015122] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G           OE     5.10.0-13-amd64 #1 Debian 5.10.106-1
[ 1843.015126] Hardware name: WHY WHY/N13_N140ZU                      , BIOS 1.07.07RTR1 05/13/2019
[ 1843.015132] RIP: 0010:dev_watchdog+0x24d/0x260
[ 1843.015139] Code: c9 c9 fd ff eb a9 4c 89 f7 c6 05 d8 61 10 01 01 e8 48 9a fa ff 44 89 e9 4c 89 f6 48 c7 c7 18 b9 56 92 48 89 c2 e8 32 3b 14 00 <0f> 0b eb 8a 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44
[ 1843.015143] RSP: 0018:ffffb45b401c8eb8 EFLAGS: 00010286
[ 1843.015148] RAX: 0000000000000000 RBX: ffff9db4a3cb7000 RCX: ffff9dbbf071ca08
[ 1843.015151] RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff9dbbf071ca00
[ 1843.015154] RBP: ffff9db4860da3dc R08: 0000000000000000 R09: ffffb45b401c8cd8
[ 1843.015157] R10: ffffb45b401c8cd0 R11: ffffffff92acb408 R12: ffff9db4860da480
[ 1843.015160] R13: 0000000000000000 R14: ffff9db4860da000 R15: ffff9db4a3cb7080
[ 1843.015164] FS:  0000000000000000(0000) GS:ffff9dbbf0700000(0000) knlGS:0000000000000000
[ 1843.015168] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1843.015171] CR2: 00001dc9e86b8000 CR3: 00000006cba0a005 CR4: 00000000003706e0
[ 1843.015174] Call Trace:
[ 1843.015180]  <IRQ>
[ 1843.015190]  ? pfifo_fast_enqueue+0x150/0x150
[ 1843.015197]  call_timer_fn+0x29/0xf0
[ 1843.015202]  __run_timers.part.0+0x1d3/0x240
[ 1843.015209]  ? ktime_get+0x38/0xa0
[ 1843.015215]  ? lapic_next_deadline+0x28/0x30
[ 1843.015222]  ? clockevents_program_event+0x8d/0xf0
[ 1843.015227]  run_timer_softirq+0x26/0x50
[ 1843.015235]  __do_softirq+0xc5/0x275
[ 1843.015242]  asm_call_irq_on_stack+0xf/0x20
[ 1843.015245]  </IRQ>
[ 1843.015254]  do_softirq_own_stack+0x37/0x40
[ 1843.015264]  irq_exit_rcu+0x8e/0xc0
[ 1843.015273]  sysvec_apic_timer_interrupt+0x36/0x80
[ 1843.015278]  asm_sysvec_apic_timer_interrupt+0x12/0x20
[ 1843.015285] RIP: 0010:cpuidle_enter_state+0xc7/0x350
[ 1843.015290] Code: 8b 3d 1d 23 57 6e e8 28 d8 a1 ff 49 89 c5 0f 1f 44 00 00 31 ff e8 39 e3 a1 ff 45 84 ff 0f 85 fa 00 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 06 01 00 00 49 63 c6 4c 2b 2c 24 48 8d 14 40 48 8d
[ 1843.015293] RSP: 0018:ffffb45b400fbea8 EFLAGS: 00000246
[ 1843.015298] RAX: ffff9dbbf072fcc0 RBX: 0000000000000006 RCX: 000000000000001f
[ 1843.015301] RDX: 0000000000000000 RSI: 000000004041d0d2 RDI: 0000000000000000
[ 1843.015304] RBP: ffffd45b3fd26600 R08: 000001ad1c3b684b R09: 0000000000000018
[ 1843.015307] R10: 0000000000001901 R11: 0000000000000a8f R12: ffffffff92bae7c0
[ 1843.015309] R13: 000001ad1c3b684b R14: 0000000000000006 R15: 0000000000000000
[ 1843.015318]  ? cpuidle_enter_state+0xb7/0x350
[ 1843.015323]  cpuidle_enter+0x29/0x40
[ 1843.015331]  do_idle+0x1ef/0x2b0
[ 1843.015338]  cpu_startup_entry+0x19/0x20
[ 1843.015345]  secondary_startup_64_no_verify+0xb0/0xbb
[ 1843.015352] ---[ end trace 4b74c6419ca5a3d6 ]---
[ 1843.015363] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1845.574571] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
[ 1845.574611] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
[ 1845.574713] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
[ 1845.574825] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
[ 1847.878505] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1852.998780] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1858.122624] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1864.010822] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1869.126842] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1875.014967] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1879.879023] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1884.999234] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1890.119147] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1896.011279] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1901.127317] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1907.015460] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1911.879493] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1916.999606] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1922.119654] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1928.007749] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1933.127906] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1939.015945] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1943.880047] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1949.000065] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1954.120150] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1960.008285] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1965.128363] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1971.016481] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1975.880515] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1981.000638] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1986.120716] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1992.008812] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 1997.132905] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2003.017003] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2007.881096] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2013.001330] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2018.121534] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2024.009617] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2029.129444] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2035.017499] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2039.881620] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2045.001653] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2050.122059] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2056.010131] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2061.129997] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2067.018099] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2071.882173] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2077.006513] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2082.122604] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2088.010779] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2093.134542] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2099.018603] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2103.886728] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2109.002814] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2114.123128] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2120.011243] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2125.135100] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2131.019215] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2135.883248] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2141.003386] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2146.123703] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2152.011830] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2157.131630] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2163.020017] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2167.883812] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2173.003901] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2178.124006] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2184.012403] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2189.132246] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2195.020334] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2199.884379] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2205.004534] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2210.124857] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2216.012645] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2221.132828] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2227.020920] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2231.885012] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2237.005261] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2242.125159] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2248.013567] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2253.133405] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2259.021454] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2263.885603] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2269.005682] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2274.125752] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2280.014159] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2285.133923] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2291.022084] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2295.886382] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2301.006251] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2306.126512] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2312.014418] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2317.138727] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2323.022635] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2327.891001] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2333.006827] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2338.127184] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2344.015107] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2349.135150] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2352.883039] rfkill: input handler enabled
[ 2355.023481] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2359.887319] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2365.007834] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2368.175594] hub 4-1:1.0: hub_ext_port_status failed (err = -110)
[ 2369.199601] usb 4-1-port1: cannot reset (err = -110)
[ 2370.127824] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2370.223643] usb 4-1-port1: cannot reset (err = -110)
[ 2371.247526] usb 4-1-port1: cannot reset (err = -110)
[ 2372.271580] usb 4-1-port1: cannot reset (err = -110)
[ 2373.295951] usb 4-1-port1: cannot reset (err = -110)
[ 2373.296213] usb 4-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 2374.319717] usb 4-1-port1: cannot disable (err = -110)
[ 2376.015871] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2379.439835] hub 4-1:1.0: hub_ext_port_status failed (err = -110)
[ 2380.464105] usb 4-1-port1: cannot reset (err = -110)
[ 2381.135735] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
[ 2381.487804] usb 4-1-port1: cannot reset (err = -110)
[ 2382.512124] usb 4-1-port1: cannot reset (err = -110)
[ 2383.535879] usb 4-1-port1: cannot reset (err = -110)
[ 2384.560149] usb 4-1-port1: cannot reset (err = -110)
[ 2384.560437] usb 4-1-port1: Cannot enable. Maybe the USB cable is bad?

et de /var/log/syslog

Code:

Apr  2 21:12:27 sam-why-debian kernel: [ 1843.014670] NETDEV WATCHDOG: enx482ae39f03a1 (r8152): transmit queue 0 timed out
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.014712] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24d/0x260
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.014715] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc xfrm_user xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc ctr ccm rfcomm overlay vboxnetadp(OE) vboxnetflt(OE) cmac algif_hash algif_skcipher af_alg vboxdrv(OE) snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device bnep binfmt_misc cdc_ether usbnet r8152 mii btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 jitterentropy_rng videobuf2_common drbg videodev ansi_cprng ecdh_generic mc ecc snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_sof_intel_hda snd_hda_codec_realtek snd_soc_skl intel_rapl_msr snd_soc_hdac_hda snd_hda_codec_generic snd_hda_ext_core snd_soc_sst_ipc intel_rapl_common ledtrig_audio
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.014865]  snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_intel snd_intel_dspcfg mei_hdcp soundwire_intel iwlmvm soundwire_generic_allocation x86_pkg_temp_thermal intel_powerclamp snd_soc_core coretemp mac80211 snd_compress squashfs libarc4 soundwire_cadence kvm_intel snd_hda_codec kvm iwlwifi irqbypass snd_hda_core rapl snd_hwdep soundwire_bus intel_cstate nls_ascii intel_uncore snd_pcm nls_cp437 cfg80211 vfat fat joydev snd_timer mei_me intel_wmi_thunderbolt efi_pstore snd pcspkr iTCO_wdt intel_pmc_bxt iTCO_vendor_support serio_raw ee1004 watchdog rfkill mei soundcore intel_pch_thermal tpm_crb tpm_tis tpm_tis_core tpm intel_hid rng_core intel_pmc_core sparse_keymap acpi_pad ac evdev loop msr evdi(OE) parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic hid_logitech_hidpp hid_logitech_dj dm_crypt dm_mod hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015030]  raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod crc32_pclmul crc32c_intel i915 ahci rtsx_pci_sdmmc libahci xhci_pci i2c_algo_bit ghash_clmulni_intel mmc_core xhci_hcd libata nvme drm_kms_helper aesni_intel nvme_core r8169 cec realtek libaes crypto_simd drm t10_pi crc_t10dif usbcore crct10dif_generic mdio_devres cryptd thunderbolt psmouse glue_helper libphy scsi_mod rtsx_pci i2c_i801 battery i2c_smbus crct10dif_pclmul crct10dif_common wmi usb_common video button
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015122] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G           OE     5.10.0-13-amd64 #1 Debian 5.10.106-1
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015126] Hardware name: WHY WHY/N13_N140ZU                      , BIOS 1.07.07RTR1 05/13/2019
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015132] RIP: 0010:dev_watchdog+0x24d/0x260
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015139] Code: c9 c9 fd ff eb a9 4c 89 f7 c6 05 d8 61 10 01 01 e8 48 9a fa ff 44 89 e9 4c 89 f6 48 c7 c7 18 b9 56 92 48 89 c2 e8 32 3b 14 00 <0f> 0b eb 8a 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015143] RSP: 0018:ffffb45b401c8eb8 EFLAGS: 00010286
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015148] RAX: 0000000000000000 RBX: ffff9db4a3cb7000 RCX: ffff9dbbf071ca08
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015151] RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff9dbbf071ca00
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015154] RBP: ffff9db4860da3dc R08: 0000000000000000 R09: ffffb45b401c8cd8
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015157] R10: ffffb45b401c8cd0 R11: ffffffff92acb408 R12: ffff9db4860da480
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015160] R13: 0000000000000000 R14: ffff9db4860da000 R15: ffff9db4a3cb7080
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015164] FS:  0000000000000000(0000) GS:ffff9dbbf0700000(0000) knlGS:0000000000000000
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015168] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015171] CR2: 00001dc9e86b8000 CR3: 00000006cba0a005 CR4: 00000000003706e0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015174] Call Trace:
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015180]  <IRQ>
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015190]  ? pfifo_fast_enqueue+0x150/0x150
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015197]  call_timer_fn+0x29/0xf0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015202]  __run_timers.part.0+0x1d3/0x240
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015209]  ? ktime_get+0x38/0xa0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015215]  ? lapic_next_deadline+0x28/0x30
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015222]  ? clockevents_program_event+0x8d/0xf0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015227]  run_timer_softirq+0x26/0x50
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015235]  __do_softirq+0xc5/0x275
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015242]  asm_call_irq_on_stack+0xf/0x20
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015245]  </IRQ>
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015254]  do_softirq_own_stack+0x37/0x40
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015264]  irq_exit_rcu+0x8e/0xc0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015273]  sysvec_apic_timer_interrupt+0x36/0x80
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015278]  asm_sysvec_apic_timer_interrupt+0x12/0x20
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015285] RIP: 0010:cpuidle_enter_state+0xc7/0x350
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015290] Code: 8b 3d 1d 23 57 6e e8 28 d8 a1 ff 49 89 c5 0f 1f 44 00 00 31 ff e8 39 e3 a1 ff 45 84 ff 0f 85 fa 00 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 06 01 00 00 49 63 c6 4c 2b 2c 24 48 8d 14 40 48 8d
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015293] RSP: 0018:ffffb45b400fbea8 EFLAGS: 00000246
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015298] RAX: ffff9dbbf072fcc0 RBX: 0000000000000006 RCX: 000000000000001f
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015301] RDX: 0000000000000000 RSI: 000000004041d0d2 RDI: 0000000000000000
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015304] RBP: ffffd45b3fd26600 R08: 000001ad1c3b684b R09: 0000000000000018
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015307] R10: 0000000000001901 R11: 0000000000000a8f R12: ffffffff92bae7c0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015309] R13: 000001ad1c3b684b R14: 0000000000000006 R15: 0000000000000000
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015318]  ? cpuidle_enter_state+0xb7/0x350
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015323]  cpuidle_enter+0x29/0x40
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015331]  do_idle+0x1ef/0x2b0
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015338]  cpu_startup_entry+0x19/0x20
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015345]  secondary_startup_64_no_verify+0xb0/0xbb
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015352] ---[ end trace 4b74c6419ca5a3d6 ]---
Apr  2 21:12:27 sam-why-debian kernel: [ 1843.015363] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:12:30 sam-why-debian kernel: [ 1845.574571] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
Apr  2 21:12:30 sam-why-debian kernel: [ 1845.574611] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
Apr  2 21:12:30 sam-why-debian kernel: [ 1845.574713] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
Apr  2 21:12:30 sam-why-debian kernel: [ 1845.574825] r8152 4-1.1:1.0 enx482ae39f03a1: Tx status -2
Apr  2 21:12:30 sam-why-debian dbus-daemon[3885]: [session uid=1000 pid=3885] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=3881 comm="/usr/libexec/tracker-miner-fs ")
Apr  2 21:12:30 sam-why-debian systemd[3860]: Starting Tracker metadata extractor...
Apr  2 21:12:30 sam-why-debian tracker-extract[14196]: Set scheduler policy to SCHED_IDLE
Apr  2 21:12:30 sam-why-debian tracker-extract[14196]: Setting priority nice level to 19
Apr  2 21:12:30 sam-why-debian dbus-daemon[3885]: [session uid=1000 pid=3885] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Apr  2 21:12:30 sam-why-debian systemd[3860]: Started Tracker metadata extractor.
Apr  2 21:12:32 sam-why-debian kernel: [ 1847.878505] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:12:37 sam-why-debian kernel: [ 1852.998780] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:12:41 sam-why-debian systemd[3860]: tracker-extract.service: Succeeded.
Apr  2 21:12:42 sam-why-debian kernel: [ 1858.122624] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:12:42 sam-why-debian dbus-daemon[3885]: [session uid=1000 pid=3885] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=3881 comm="/usr/libexec/tracker-miner-fs ")
Apr  2 21:12:42 sam-why-debian systemd[3860]: Starting Tracker metadata extractor...
Apr  2 21:12:42 sam-why-debian tracker-extract[14223]: Set scheduler policy to SCHED_IDLE
Apr  2 21:12:42 sam-why-debian tracker-extract[14223]: Setting priority nice level to 19
Apr  2 21:12:42 sam-why-debian dbus-daemon[3885]: [session uid=1000 pid=3885] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Apr  2 21:12:42 sam-why-debian systemd[3860]: Started Tracker metadata extractor.
Apr  2 21:12:48 sam-why-debian kernel: [ 1864.010822] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:12:53 sam-why-debian kernel: [ 1869.126842] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:12:59 sam-why-debian kernel: [ 1875.014967] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:13:04 sam-why-debian kernel: [ 1879.879023] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:13:05 sam-why-debian systemd[3860]: tracker-extract.service: Succeeded.
Apr  2 21:13:05 sam-why-debian systemd[3860]: tracker-extract.service: Consumed 1.143s CPU time.
Apr  2 21:13:06 sam-why-debian gnome-shell[4027]: libinput error: event9  - Logitech Performance MX: client bug: event processing lagging behind by 29ms, your system is too slow
Apr  2 21:13:06 sam-why-debian gnome-shell[4027]: libinput error: event9  - Logitech Performance MX: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
Apr  2 21:13:09 sam-why-debian kernel: [ 1884.999234] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:13:11 sam-why-debian baloo_file.desktop[14283]: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Apr  2 21:13:14 sam-why-debian kernel: [ 1890.119147] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout

...

Apr  2 21:21:29 sam-why-debian kernel: [ 2384.560437] usb 4-1-port1: Cannot enable. Maybe the USB cable is bad?
Apr  2 21:21:30 sam-why-debian kernel: [ 2385.583923] usb 4-1-port1: cannot disable (err = -110)
Apr  2 21:21:31 sam-why-debian kernel: [ 2387.023850] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:21:35 sam-why-debian kernel: [ 2390.704010] hub 4-1:1.0: hub_ext_port_status failed (err = -110)
Apr  2 21:21:36 sam-why-debian kernel: [ 2391.728303] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:36 sam-why-debian kernel: [ 2391.887890] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:21:37 sam-why-debian kernel: [ 2392.752040] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:38 sam-why-debian kernel: [ 2393.776039] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:39 sam-why-debian kernel: [ 2394.800093] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:40 sam-why-debian kernel: [ 2395.824124] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:40 sam-why-debian kernel: [ 2395.824411] usb 4-1-port1: Cannot enable. Maybe the USB cable is bad?
Apr  2 21:21:41 sam-why-debian kernel: [ 2396.848389] usb 4-1-port1: cannot disable (err = -110)
Apr  2 21:21:41 sam-why-debian kernel: [ 2397.008035] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:21:46 sam-why-debian kernel: [ 2401.968241] hub 4-1:1.0: hub_ext_port_status failed (err = -110)
Apr  2 21:21:46 sam-why-debian kernel: [ 2402.128395] r8152 4-1.1:1.0 enx482ae39f03a1: Tx timeout
Apr  2 21:21:47 sam-why-debian kernel: [ 2402.992492] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:48 sam-why-debian kernel: [ 2404.016702] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:49 sam-why-debian kernel: [ 2405.040303] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:50 sam-why-debian kernel: [ 2406.064581] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:51 sam-why-debian kernel: [ 2407.088274] usb 4-1-port1: cannot reset (err = -110)
Apr  2 21:21:51 sam-why-debian kernel: [ 2407.088748] usb 4-1-port1: Cannot enable. Maybe the USB cable is bad?

Auriez-vous une idée sur la cause de cette erreur et les moyens de la résoudre ?

Merci d'avance pour toute aide.

Dernière modification par sssammm (03 Apr 2022 12:42:13)

François Marthaler · 06 Apr 2022 22:17:07

Bonsoir,

Personnellement, je n'ai pas les compétences nécessaire et n'ai jamais utilisé l'OS Linux Debian Bullsey.

Si j'avais la machine sous la main, je commencerait par démarrer sur une clé Live-USB Ubuntu 20.04 pour voir si ces problèmes demeurent...

Surtout je tenterais d'utiliser la machine sans la docking station Lenovo ThinkPad USB-C Dock Gen2, afin de savoir si cette dernière n'est pas en cause (déjà vu avec d'autres modèles).

Si la machine fonctionne bien sans la docking station, je pense que je verrais si mon fournisseur est en mesure de la tester pour éventuellement identifier un problème hardware. Surtout si elle a fonctionné avec satisfaction durant deux ans...

Merci de partager ici vos conclusions.

Cordialement.

sssammm · 08 Apr 2022 07:58:50

Bonjour,

Tout d'abord, merci pour la réponse

Bonne idée pour le live-USB. Je vais essayer ces prochains jours.

En ce qui concerne l'état de santé du dock, j'ai quelques doutes. En effet, ce dernier fonctionne sans problème avec une machine Windows utilisée en parallèle. Mais tester l'ordinateur sur un autre dock ne ferait pas de mal. Je vais tenter de m'en procurer un.

Je partagerai avec plaisir mes conclusions ici.

Cordialement

François Marthaler · 08 Apr 2022 22:39:54

On se réjouit de connaître vos conclusions...

Cordialement.

sssammm · 18 Apr 2022 18:56:51

Rebonjour,

J'ai finalement eu l'opportunité de tester la machine avec un autre dock et n'ai pas rencontré de problème. N'ayant pas de problème sous Windows, je soupçonne qu'il s'agit d'une interaction entre mon système et le dock.

J'ai relu plus attentivement le rapport de bug sur le noyau mentionné plus haut et il semblerait que les messages d'erreur `Tx status -2` et `Tx status -71` soient liés (voir ici: https://bugzilla.kernel.org/show_bug.cgi?id=198931#c51).

Dès lors, il semblerait qu'il s'agisse d'un problème de gestion de l'autosuspend. Il semblerait que le noyau 5.16 n'a plus ce problème (voir dernier commentaire: https://bugzilla.kernel.org/show_bug.cgi?id=198931#c96)

Sinon, les solutions proposées par le fil (voir ici: https://bugzilla.kernel.org/show_bug.cgi?id=198931#c7) sont notamment:

* désactiver l'autosuspend (en général ou pour le périphérique) dans TLP
* désactiver l'autosuspend (en général ou pour le périphérique) dans le noyau
* Activer le paramètre suivant: usbcore.quirks=0bda:8153:k

Je vais tester la mise à jour du noyau comme prochaine étape.

sssammm · 18 Apr 2022 20:58:27

A peine la mise à jour du noyau effectuée avec `sudo apt install linux-headers-5.16.0-0.bpo.4-amd64 linux-image-5.16.0-0.bpo.4-amd64` que j'ai à nouveau la même erreur.

Je vais donc tenter une désactivation de l'USB_AUTOSUSPEND en décommentant la ligne USB_AUTOSUSPEND=0 dans /etc/tlp.conf.

sssammm · 18 Apr 2022 22:13:40

La désactivation de l'USB_AUTOSUSPEND n'a pas non plus fonctionné. Je tente donc d'ajouter `usbcore.autosuspend=-1` à la ligne `GRUB_CMDLINE_LINUX_DEFAULT` du fichier `/etc/default/grub` comme indiqué ici: https://unix.stackexchange.com/a/175035.

François Marthaler · 20 Apr 2022 12:49:55

Bonjour sssammm,

Merci de prendre le temps de documenter ici tous vos tests. Et j'espère que vous trouverez bientôt la solution...

Cordialement.

sssammm · 25 Apr 2022 20:09:16

Rebonjour.

Merci de prendre le temps de documenter ici tous vos tests. Et j'espère que vous trouverez bientôt la solution...

Avec plaisir. J'en ai moi-même profité pendant de nombreuses années.

Malheureusement, l'option `usbcore.autosuspend=-1` n'a pas fonctionné non-plus. J'avoue être à court d'idée. Peut-être vaut-il la peine de faire tout de même un test avec une autre distribution. Si le problème persiste, peut-être s'agit-il effectivement d'un problème hardware avec la doc. Sinon, il faudra soit creuser plus profondément, soit renoncer à l'ethernet-USB, je pense.

Swisslinux.org

− Le carrefour GNU/Linux en Suisse −

Recherche

Menu

Forum

Identification

Inscription

Langue

Le Forum

#1 03 Apr 2022 12:30:21

[Net] Coupure de l'ethernet par USB-C sur N131ZU

Code:

Code:

Code:

#2 06 Apr 2022 22:17:07

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#3 08 Apr 2022 07:58:50

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#4 08 Apr 2022 22:39:54

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#5 18 Apr 2022 18:56:51

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#6 18 Apr 2022 20:58:27

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#7 18 Apr 2022 22:13:40

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#8 20 Apr 2022 12:49:55

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

#9 25 Apr 2022 20:09:16

Re: [Net] Coupure de l'ethernet par USB-C sur N131ZU

Pied de page des forums