[Kernel-packages] [Bug 2053049] Re: cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS
Same on 5.15.0-102-generic. Is there some kernel parameter that needs to be set? Something changed from 5.4.0-150-generic Ubuntu 18.04.6LTS, where module worked fine. root@n005:~# modprobe -D cppc_cpufreq insmod /lib/modules/5.15.0-102-generic/kernel/drivers/cpufreq/cppc_cpufreq.ko root@n005:~# ll /lib/modules/5.15.0-102-generic/kernel/drivers/cpufreq/cppc_cpufreq.ko -rw-r--r-- 1 root root 26977 Mar 5 16:22 /lib/modules/5.15.0-102-generic/kernel/drivers/cpufreq/cppc_cpufreq.ko root@n005:~# modprobe -vvv cppc_cpufreq modprobe: INFO: ../libkmod/libkmod.c:367 kmod_set_log_fn() custom logging function 0x5970 registered modprobe: DEBUG: ../libkmod/libkmod-index.c:757 index_mm_open() file=/lib/modules/5.15.0-102-generic/modules.dep.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:757 index_mm_open() file=/lib/modules/5.15.0-102-generic/modules.alias.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:757 index_mm_open() file=/lib/modules/5.15.0-102-generic/modules.symbols.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:757 index_mm_open() file=/lib/modules/5.15.0-102-generic/modules.builtin.alias.bin modprobe: DEBUG: ../libkmod/libkmod-index.c:757 index_mm_open() file=/lib/modules/5.15.0-102-generic/modules.builtin.bin modprobe: DEBUG: ../libkmod/libkmod-module.c:556 kmod_module_new_from_lookup() input alias=cppc_cpufreq, normalized=cppc_cpufreq modprobe: DEBUG: ../libkmod/libkmod-module.c:562 kmod_module_new_from_lookup() lookup modules.dep cppc_cpufreq modprobe: DEBUG: ../libkmod/libkmod.c:597 kmod_search_moddep() use mmaped index 'modules.dep' modname=cppc_cpufreq modprobe: DEBUG: ../libkmod/libkmod.c:405 kmod_pool_get_module() get module name='cppc_cpufreq' found=(nil) modprobe: DEBUG: ../libkmod/libkmod.c:413 kmod_pool_add_module() add 0xaaad8490 key='cppc_cpufreq' modprobe: DEBUG: ../libkmod/libkmod-module.c:202 kmod_module_parse_depline() 0 dependencies for cppc_cpufreq modprobe: DEBUG: ../libkmod/libkmod-module.c:589 kmod_module_new_from_lookup() lookup cppc_cpufreq=0, list=0xaaad7f20 modprobe: DEBUG: ../libkmod/libkmod.c:502 lookup_builtin_file() use mmaped index 'modules.builtin' modname=cppc_cpufreq modprobe: DEBUG: ../libkmod/libkmod-module.c:1760 kmod_module_get_initstate() could not open '/sys/module/cppc_cpufreq/initstate': No such file or directory modprobe: DEBUG: ../libkmod/libkmod-module.c:1770 kmod_module_get_initstate() could not open '/sys/module/cppc_cpufreq': No such file or directory modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=snd_pcsp mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=snd_usb_audio mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=cx88_alsa mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=snd_atiixp_modem mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=snd_intel8x0m mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=snd_via82xx_modem mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=ib_ipoib mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=md_mod mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=bonding mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=dummy mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=net mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=iommu mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=arm_smmu mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1404 kmod_module_get_options() modname=ipv6 mod->name=cppc_cpufreq mod->alias=(null) modprobe: DEBUG: ../libkmod/libkmod-module.c:1760 kmod_module_get_initstate() could not open '/sys/module/cppc_cpufreq/initstate': No such file or directory modprobe: DEBUG: ../libkmod/libkmod-module.c:1770 kmod_module_get_initstate() could not open '/sys/module/cppc_cpufreq': No such file or directory modprobe: DEBUG: ../libkmod/libkmod-module.c:750 kmod_module_get_path() name='cppc_cpufreq' path='/lib/modules/5.15.0-102-generic/kernel/drivers/cpufreq/cppc_cpufreq.ko' modprobe: DEBUG: ../libkmod/libkmod-module.c:750 kmod_module_get_path() name='cppc_cpufreq'
[Kernel-packages] [Bug 2053049] Re: cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS
Still not working on $ uname -ar Linux n009 5.15.0-100-generic #110-Ubuntu SMP Wed Feb 7 13:28:04 UTC 2024 aarch64 aarch64 aarch64 GNU/Linu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053049 Title: cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS Status in linux package in Ubuntu: New Bug description: [Bug Description] cpufreq governor fails to start after installing Ubuntu 22.04.3LTS w/ latest kernel [Steps to Reproduce] 1) Booted Ubuntu 22.04.3 LTS w/ 5.15.0-94-generic 2) dmesg | grep cppc shows no driver 3) lsmod | grep cppc shows that cppc-cpufreq is not loaded 4) lsmod | grep thunderx2 is loaded and perf works root@n008:~# lsmod |grep thunder thunderx2_pmu 24576 0 [Actual Results] root@n008:~# modprobe cppc-cpufreq modprobe: ERROR: could not insert 'cppc_cpufreq': No such device root@n008:~# cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel root@n005:~# [Expected Results] Can set frequency governor on Ubuntu 22.04.3LT w/ 5.15.0-94-generic or linux-hwe kernels Used to work Ubuntu 18.04.6LTS w/ 5.4.0-150-generic [Reproducibility] 100% [Additional information] root@n008:/etc/default# inxi -b System: Host: n008 Kernel: 5.15.0-94-generic aarch64 bits: 64 Console: pty pts/0 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish) Machine: Type: Server System: GIGABYTE product: R281-T94-00 v: 0100 serial: X Mobo: GIGABYTE model: MT91-FS4-00 v: 00030101 serial: XXXUEFI: GIGABYTE v: F34 date: 08/13/2020 CPU: Info: 2x 32-core Model N/A [MT MCP SMP] speed: 0 Graphics: Device-1: ASPEED Graphics Family driver: ast v: kernel Display: server: N/A driver: X: loaded: modesetting gpu: ast tty: 118x27 Message: GL data unavailable in console for root. Network: Device-1: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-2: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-3: QLogic FastLinQ QL41000 Series 10/25/40/50GbE driver: qede Device-4: QLogic FastLinQ QL41000 Series 10/25/40/50GbE driver: qede Device-5: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-6: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-7: Mellanox MT27710 Family [ConnectX-4 Lx] driver: mlx5_core Drives: Local Storage: total: raw: 7.2 TiB usable: 5.46 TiB used: 1.74 TiB (31.9%) Info: Processes: 2282 Uptime: 1h 3m Memory: 1001.64 GiB used: 8.65 GiB (0.9%) Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.13 [Resolution] Related to bug # 1745007 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053049] Re: cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS
https://access.redhat.com/articles/7011459 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053049 Title: cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS Status in linux package in Ubuntu: New Bug description: [Bug Description] cpufreq governor fails to start after installing Ubuntu 22.04.3LTS w/ latest kernel [Steps to Reproduce] 1) Booted Ubuntu 22.04.3 LTS w/ 5.15.0-94-generic 2) dmesg | grep cppc shows no driver 3) lsmod | grep cppc shows that cppc-cpufreq is not loaded 4) lsmod | grep thunderx2 is loaded and perf works root@n008:~# lsmod |grep thunder thunderx2_pmu 24576 0 [Actual Results] root@n008:~# modprobe cppc-cpufreq modprobe: ERROR: could not insert 'cppc_cpufreq': No such device root@n008:~# cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel root@n005:~# [Expected Results] Can set frequency governor on Ubuntu 22.04.3LT w/ 5.15.0-94-generic or linux-hwe kernels Used to work Ubuntu 18.04.6LTS w/ 5.4.0-150-generic [Reproducibility] 100% [Additional information] root@n008:/etc/default# inxi -b System: Host: n008 Kernel: 5.15.0-94-generic aarch64 bits: 64 Console: pty pts/0 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish) Machine: Type: Server System: GIGABYTE product: R281-T94-00 v: 0100 serial: X Mobo: GIGABYTE model: MT91-FS4-00 v: 00030101 serial: XXXUEFI: GIGABYTE v: F34 date: 08/13/2020 CPU: Info: 2x 32-core Model N/A [MT MCP SMP] speed: 0 Graphics: Device-1: ASPEED Graphics Family driver: ast v: kernel Display: server: N/A driver: X: loaded: modesetting gpu: ast tty: 118x27 Message: GL data unavailable in console for root. Network: Device-1: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-2: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-3: QLogic FastLinQ QL41000 Series 10/25/40/50GbE driver: qede Device-4: QLogic FastLinQ QL41000 Series 10/25/40/50GbE driver: qede Device-5: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-6: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-7: Mellanox MT27710 Family [ConnectX-4 Lx] driver: mlx5_core Drives: Local Storage: total: raw: 7.2 TiB usable: 5.46 TiB used: 1.74 TiB (31.9%) Info: Processes: 2282 Uptime: 1h 3m Memory: 1001.64 GiB used: 8.65 GiB (0.9%) Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.13 [Resolution] Related to bug # 1745007 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053049] [NEW] cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS
Public bug reported: [Bug Description] cpufreq governor fails to start after installing Ubuntu 22.04.3LTS w/ latest kernel [Steps to Reproduce] 1) Booted Ubuntu 22.04.3 LTS w/ 5.15.0-94-generic 2) dmesg | grep cppc shows no driver 3) lsmod | grep cppc shows that cppc-cpufreq is not loaded 4) lsmod | grep thunderx2 is loaded and perf works root@n008:~# lsmod |grep thunder thunderx2_pmu 24576 0 [Actual Results] root@n008:~# modprobe cppc-cpufreq modprobe: ERROR: could not insert 'cppc_cpufreq': No such device root@n008:~# cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel root@n005:~# [Expected Results] Can set frequency governor on Ubuntu 22.04.3LT w/ 5.15.0-94-generic or linux-hwe kernels Used to work Ubuntu 18.04.6LTS w/ 5.4.0-150-generic [Reproducibility] 100% [Additional information] root@n008:/etc/default# inxi -b System: Host: n008 Kernel: 5.15.0-94-generic aarch64 bits: 64 Console: pty pts/0 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish) Machine: Type: Server System: GIGABYTE product: R281-T94-00 v: 0100 serial: X Mobo: GIGABYTE model: MT91-FS4-00 v: 00030101 serial: XXXUEFI: GIGABYTE v: F34 date: 08/13/2020 CPU: Info: 2x 32-core Model N/A [MT MCP SMP] speed: 0 Graphics: Device-1: ASPEED Graphics Family driver: ast v: kernel Display: server: N/A driver: X: loaded: modesetting gpu: ast tty: 118x27 Message: GL data unavailable in console for root. Network: Device-1: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-2: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-3: QLogic FastLinQ QL41000 Series 10/25/40/50GbE driver: qede Device-4: QLogic FastLinQ QL41000 Series 10/25/40/50GbE driver: qede Device-5: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-6: Mellanox MT28908 Family [ConnectX-6] driver: mlx5_core Device-7: Mellanox MT27710 Family [ConnectX-4 Lx] driver: mlx5_core Drives: Local Storage: total: raw: 7.2 TiB usable: 5.46 TiB used: 1.74 TiB (31.9%) Info: Processes: 2282 Uptime: 1h 3m Memory: 1001.64 GiB used: 8.65 GiB (0.9%) Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.13 [Resolution] Related to bug # 1745007 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053049 Title: cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu 22.04.3 LTS Status in linux package in Ubuntu: New Bug description: [Bug Description] cpufreq governor fails to start after installing Ubuntu 22.04.3LTS w/ latest kernel [Steps to Reproduce] 1) Booted Ubuntu 22.04.3 LTS w/ 5.15.0-94-generic 2) dmesg | grep cppc shows no driver 3) lsmod | grep cppc shows that cppc-cpufreq is not loaded 4) lsmod | grep thunderx2 is loaded and perf works root@n008:~# lsmod |grep thunder thunderx2_pmu 24576 0 [Actual Results] root@n008:~# modprobe cppc-cpufreq modprobe: ERROR: could not insert 'cppc_cpufreq': No such device root@n008:~# cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel root@n005:~# [Expected Results] Can set frequency governor on Ubuntu 22.04.3LT w/ 5.15.0-94-generic or linux-hwe kernels Used to work Ubuntu 18.04.6LTS w/ 5.4.0-150-generic [Reproducibility] 100% [Additional information] root@n008:/etc/default# inxi -b System: Host: n008 Kernel: 5.15.0-94-generic aarch64 bits: 64 Console: pty pts/0 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish) Machine: Type: Server System: GIGABYTE product: R281-T94-00 v: 0100 serial: X Mobo: GIGABYTE model: MT91-FS4-00 v: 00030101 serial: XXXUEFI: GIGABYTE v: F34 date: 08/13/2020 CPU: Info: 2x 32-core Model N/A [MT MCP SMP] speed: 0 Graphics: Device-1: ASPEED Graphics Family driver: ast v: kernel Display: server: N/A driver: X: loaded: modesetting gpu: ast tty: 118x27 Message: GL data unavailable in console for root. Network:
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
cc. Same issue with 6.2.0-34-generic on an old i5 machine and Logitech K400 kbd w/integrated mousepad. # dmesg |grep -i logitech [5.648913] usb 2-1.1: Manufacturer: Logitech [ 13.148210] input: Logitech USB Receiver as /devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:046D:C52B.0001/input/input3 [ 13.208627] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-:00:1a.0-1.1/input0 [ 13.208971] input: Logitech USB Receiver Mouse as /devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52B.0002/input/input4 [ 13.209214] input: Logitech USB Receiver Consumer Control as /devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52B.0002/input/input5 [ 13.268569] input: Logitech USB Receiver System Control as /devices/pci:00/:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:046D:C52B.0002/input/input6 [ 13.269157] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:00:1a.0-1.1/input1 [ 13.269713] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:1a.0-1.1/input2 When it was working # cat /var/log/Xorg.1.log.old | grep -i Logi [110891.923] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_3438 [110891.925] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 15 paused 0 [110891.927] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 16 paused 0 [110891.940] (II) systemd-logind: releasing fd for 226:1 [110892.180] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 42 paused 0 [110892.213] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 45 paused 0 [110892.220] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 46 paused 0 [110892.228] (II) config/udev: Adding input device Logitech K400 Plus (/dev/input/event3) [110892.228] (**) Logitech K400 Plus: Applying InputClass "evdev pointer catchall" [110892.228] (**) Logitech K400 Plus: Applying InputClass "evdev keyboard catchall" [110892.228] (**) Logitech K400 Plus: Applying InputClass "libinput pointer catchall" [110892.228] (**) Logitech K400 Plus: Applying InputClass "libinput keyboard catchall" [110892.228] (II) Using input driver 'libinput' for 'Logitech K400 Plus' [110892.229] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 47 paused 0 [110892.229] (**) Logitech K400 Plus: always reports core events [110892.232] (II) event3 - Logitech K400 Plus: is tagged by udev as: Keyboard Mouse [110892.232] (II) event3 - Logitech K400 Plus: device is a pointer [110892.232] (II) event3 - Logitech K400 Plus: device is a keyboard [110892.233] (II) event3 - Logitech K400 Plus: device removed [110892.233] (II) libinput: Logitech K400 Plus: needs a virtual subdevice [110892.233] (II) XINPUT: Adding extended input device "Logitech K400 Plus" (type: MOUSE, id 9) [110892.233] (**) Logitech K400 Plus: (accel) selected scheme none/0 [110892.233] (**) Logitech K400 Plus: (accel) acceleration factor: 2.000 [110892.233] (**) Logitech K400 Plus: (accel) acceleration threshold: 4 [110892.235] (II) event3 - Logitech K400 Plus: is tagged by udev as: Keyboard Mouse [110892.236] (II) event3 - Logitech K400 Plus: device is a pointer [110892.236] (II) event3 - Logitech K400 Plus: device is a keyboard [110892.237] (II) config/udev: Adding input device Logitech K400 Plus (/dev/input/mouse0) [110892.247] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 48 paused 0 [110892.263] (**) Logitech K400 Plus: Applying InputClass "evdev pointer catchall" [110892.263] (**) Logitech K400 Plus: Applying InputClass "evdev keyboard catchall" [110892.263] (**) Logitech K400 Plus: Applying InputClass "libinput pointer catchall" [110892.263] (**) Logitech K400 Plus: Applying InputClass "libinput keyboard catchall" [110892.263] (II) Using input driver 'libinput' for 'Logitech K400 Plus' [110892.263] (II) systemd-logind: returning pre-existing fd for /dev/input/event3 13:67 [110892.263] (**) Logitech K400 Plus: always reports core events [110892.263] (II) libinput: Logitech K400 Plus: is a virtual subdevice [110892.263] (II) XINPUT: Adding extended input device "Logitech K400 Plus" (type: KEYBOARD, id 11) [110892.263] (II) systemd-logind: returning pre-existing fd for /dev/input/event4 13:68 [110938.912] (EE) event3 - Logitech K400 Plus: client bug: event processing lagging behind by 29ms, your system is too slow [466904.557] (EE) event3 - Logitech K400 Plus: client bug: event processing lagging behind by 26ms, your system is too slow [467200.761] (EE) event3 - Logitech K400 Plus: client bug: event processing lagging behind by 30ms, your system is too slow [467202.027] (EE) event3 - Logitech K400 Plus: client bug: event processing lagging behind by 24ms, your system is too slow [467596.881] (EE) event3 - Logitech K400 Plus: client bug: event processing lagging behind
[Kernel-packages] [Bug 1940690] Re: amdgpu kernel crash
*** This bug is a duplicate of bug 1956845 *** https://bugs.launchpad.net/bugs/1956845 Hardware: DP Epyc Milan 7763 node with 2 qty AMD Instinct Mi100 Kernel: ubuntu 18.04.6LTS w/linux-hwe 5.4.0-107-generic ROCm 5.1.0 and AMDGPU version: 5.13.20.5.1 driver Homegrown software developed using ROCm 5.1.0. Might this be related? Logs: [304726.475355] beegfs: enabling unsafe global rkey [304734.912424] amdgpu :23:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process hyprep pid 122284 thread hyprep pid 122284) [304734.928526] amdgpu :23:00.0: amdgpu: in page starting at address 0x01753000 from IH client 0x1b (UTCL2) [304734.939972] amdgpu :23:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [304734.948130] amdgpu :23:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [304734.955858] amdgpu :23:00.0: amdgpu: MORE_FAULTS: 0x1 [304734.962115] amdgpu :23:00.0: amdgpu: WALKER_ERROR: 0x0 [304734.968441] amdgpu :23:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [304734.975196] amdgpu :23:00.0: amdgpu: MAPPING_ERROR: 0x0 [304734.981580] amdgpu :23:00.0: amdgpu: RW: 0x0 [304735.568400] amdgpu :23:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process pid 0 thread pid 0) [304735.582318] amdgpu :23:00.0: amdgpu: in page starting at address 0x01753000 from IH client 0x1b (UTCL2) [304735.593722] amdgpu :23:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [304735.601851] amdgpu :23:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) [304735.609465] amdgpu :23:00.0: amdgpu: MORE_FAULTS: 0x0 [304735.615686] amdgpu :23:00.0: amdgpu: WALKER_ERROR: 0x0 [304735.621994] amdgpu :23:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [304735.628737] amdgpu :23:00.0: amdgpu: MAPPING_ERROR: 0x0 [304735.635104] amdgpu :23:00.0: amdgpu: RW: 0x0 [321839.599489] beegfs: enabling unsafe global rkey Driver Apr 02 22:19:59 n004 kernel: [drm] amdgpu kernel modesetting enabled. Apr 02 22:19:59 n004 kernel: [drm] amdgpu version: 5.13.20.5.1 Apr 02 22:19:59 n004 kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Apr 02 22:19:59 n004 kernel: amdgpu: Virtual CRAT table created for CPU Apr 02 22:19:59 n004 kernel: amdgpu: Topology: Add CPU node Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: remove_conflicting_pci_framebuffers: bar 0: 0x678 -> 0x67f Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: remove_conflicting_pci_framebuffers: bar 2: 0x680 -> 0x680001f Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xeb40 -> 0xeb47 Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: enabling device ( -> 0003) Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: Fetched VBIOS from ROM BAR Apr 02 22:19:59 n004 kernel: amdgpu: ATOM BIOS: 113-D3431401-100 Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: MEM ECC is active. Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: SRAM ECC is active. Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: RAS INFO: ras initialized successfully, hardware ability[7fff] ras_mask[7fff] Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: VRAM: 32752M 0x0080 - 0x0087FEFF (32752M used) Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: GART: 512M 0x - 0x1FFF Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: AGP: 267878400M 0x0088 - 0x Apr 02 22:19:59 n004 kernel: [drm] amdgpu: 32752M of VRAM memory ready Apr 02 22:19:59 n004 kernel: [drm] amdgpu: 2064153M of GTT memory ready. Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: PSP runtime database doesn't exist Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: Will use PSP to load VCN firmware Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: HDCP: optional hdcp ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: DTM: optional dtm ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: RAP: optional rap ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: use vbios provided pptable Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: smc_dpm_info table revision(format.content): 4.6 Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: PMFW based fan control disabled Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: SMU is initialized successfully! Apr 02 22:19:59 n004 kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart Apr 02 22:19:59 n004 kernel: amdgpu: Virtual CRAT table created for
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
*** This bug is a duplicate of bug 1859756 ***
https://bugs.launchpad.net/bugs/1859756
Small comment; - Any reason why hns3 is not version 1.0.2 as the
proprietary driver for 18.04.1 LTS kernel 4.15.0-29-generic?
root@n012:~# find
/lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3
-name "*.ko" -type f -exec modinfo {} \; | egrep -i -e "name|version|srcv"
filename:
/lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge.ko
version:1.0.2
srcversion: C608A5D8EF6F248597CA9E5
name: hclge
filename:
/lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf.ko
version:1.0.2
srcversion: 83B44FBC5FE1D6324B5F3D6
name: hclgevf
filename:
/lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hnae3.ko
version:1.0.2
srcversion: 9097930440A454C1B6A0217
name: hnae3
filename:
/lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3.ko
version:1.0.2
srcversion: 0EF59799F6C1BB69074D893
name: hns3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892347
Title:
HiSilicon HNS3 ethernet broken
Status in kunpeng920:
Incomplete
Status in kunpeng920 ubuntu-18.04 series:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu
18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920
SOCs. Huawei provides binary distributed driver
NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel
4.15.0-29-generic.
root@n012:~# uname -ar
Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux
root@n012:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
root@n012:~# dmesg |grep hns3
[3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family -
version
[3.789796] hns3: Copyright (c) 2017 Huawei Corporation.
[4.295868] hns3 :7d:00.0: The firmware version is 01092806
[4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for
speed(-1)
[4.498584] hns3 :7d:00.1: The firmware version is 01092806
[4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for
speed(-1)
[4.671546] hns3 :7d:00.2: The firmware version is 01092806
[4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for
speed(-1)
[4.813538] hns3 :7d:00.3: The firmware version is 01092806
[4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for
speed(-1)
[4.937256] hns3 :bd:00.0: The firmware version is 01092806
[4.994060] hns3 :bd:00.1: The firmware version is 01092806
[5.049951] hns3 :bd:00.2: The firmware version is 01092806
[5.107165] hns3 :bd:00.3: The firmware version is 01092806
[5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0
[5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6
[5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5
[5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3
[5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1
[6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2
[6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4
[6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7
[ 18.031167] hns3 :7d:00.0 enp125s0f0: link up
[77661.965968] beegfs: enabling unsafe global rkey
[7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found
[error status=0x1]
[7.642466] hns3 :7d:00.0: PF Reset requested
[7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF
[7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5!
[7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF
[7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5!
[7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF
[7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5!
[7.689650] hns3 :7d:00.0 enp125s0f0: link down
[7.797516] hns3 :7d:00.0: prepare wait ok
[7.908488] hns3 :7d:00.0: The firmware version is 01092806
[7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization
finished.
[7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found
[error status=0x1]
[7.945976] hns3 :7d:00.0: PF Reset requested
[7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF
[7.950200] hns3 :7d:00.0: inform reset to
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Tested 4.15.0-114-generic it works fine. Thx! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04 series: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Ike, Do you mean the 4.15.0-103 kernel in https://kernel.ubuntu.com/~ikepanhc/lp1859756/? Linux.-hwe 5.4 is not an option for me as it breaks parallel filesystem BeeGFS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04 series: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF
[Kernel-packages] [Bug 1892347] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403412/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send
[Kernel-packages] [Bug 1892347] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403406/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to
[Kernel-packages] [Bug 1892347] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403408/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to
[Kernel-packages] [Bug 1892347] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403407/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF
[Kernel-packages] [Bug 1892347] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403403/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to
[Kernel-packages] [Bug 1892347] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403410/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Had to login on different interface (ib0) and unload and load hns3 module to get primary network up. Then I could run apport-collect 1892347. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send
[Kernel-packages] [Bug 1892347] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403409/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5)
[Kernel-packages] [Bug 1892347] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403411/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox
[Kernel-packages] [Bug 1892347] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403404/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox
[Kernel-packages] [Bug 1892347] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1892347/+attachment/5403405/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
apport information ** Tags added: apport-collected ** Description changed: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.280295] hns3 :7d:00.0: inform reset to vf(3) failed -5! [80001.305621] hns3 :7d:00.0 enp125s0f0: link down [80001.413473] hns3 :7d:00.0: prepare wait ok [80001.523836] hns3 :7d:00.0: The firmware version is 01092806 [80001.530925] hns3 :7d:00.0: Reset done, hclge driver
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Installed kernel 4.15.0-29-generic and Huawei's propriatory hns3 driver package NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb which obviously is 1.0.2 rather that 1.0 on 4.15.0-112 and 5.4.0-42. Obviously the hns3 1.0 driver in 5.4.0-42 is different to the 1.0 driver in 4.15.0-112. Anyway, using downrev kernel and binary hse3 drver seem to work fine, but would like to be on latest kernel for security reasons. root@n009:~# uname -ar Linux n009 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:41:03 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux root@n009:~# modinfo hns3 filename: /lib/modules/4.15.0-29-generic/updates/drivers/net/ethernet/hisilicon/hns3/hns3.ko version:1.0.2 alias: pci:hns-nic license:GPL author: Huawei Tech. Co., Ltd. description:HNS3: Hisilicon Ethernet Driver srcversion: 0EF59799F6C1BB69074D893 alias: pci:v19E5dA22Fsv*sd*bc*sc*i* alias: pci:v19E5dA22Esv*sd*bc*sc*i* alias: pci:v19E5dA226sv*sd*bc*sc*i* alias: pci:v19E5dA225sv*sd*bc*sc*i* alias: pci:v19E5dA224sv*sd*bc*sc*i* alias: pci:v19E5dA223sv*sd*bc*sc*i* alias: pci:v19E5dA222sv*sd*bc*sc*i* alias: pci:v19E5dA221sv*sd*bc*sc*i* alias: pci:v19E5dA220sv*sd*bc*sc*i* depends:hnae3 name: hns3 vermagic: 4.15.0-29-generic SMP mod_unload aarch64 parm: debug: Network interface message level setting (int) root@n009:~# dmesg | grep hns3 [4.067119] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [4.067119] hns3: Copyright (c) 2017 Huawei Corporation. [4.859148] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [4.909343] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [5.086063] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.169404] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.349699] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [5.437326] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [5.589360] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [5.709287] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [ 11.575815] hns3 :7d:00.0 enp125s0f0: net open [ 15.885156] hns3 :7d:00.0 enp125s0f0: link up -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Note! ntttcp is not sufficient to trigger issue. Some heavy MPI or NFS traffic is needed to trigger issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in linux package in Ubuntu: New Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.280295] hns3
[Kernel-packages] [Bug 1892347] [NEW] HiSilicon HNS3 ethernet broken
Public bug reported: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.280295] hns3 :7d:00.0: inform reset to vf(3) failed -5! [80001.305621] hns3 :7d:00.0 enp125s0f0: link down [80001.413473] hns3 :7d:00.0: prepare wait ok [80001.523836] hns3 :7d:00.0: The firmware version is 01092806 [80001.530925] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80002.581453] hns3 :7d:00.0 enp125s0f0: link up [80002.869622] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80002.869649] hns3
[Kernel-packages] [Bug 1729674]
Ref. bug # 1600126 I updated r8152 to v2.11 per https://aur.archlinux.org/packages/r8152-dkms/ makes things more stable. # cd /usr/src/r8152-2.11.0 # patch -p1 <./linux-4.20.0-add-guard-fix.patch # more /usr/src/r8152-2.11.0/dkms.conf PACKAGE_NAME="r8152" PACKAGE_VERSION="2.11.0" BUILT_MODULE_NAME[0]="r8152" DEST_MODULE_LOCATION[0]="/kernel/drivers/net/usb" AUTOINSTALL="yes" # ll /var/lib/dkms/r8152/2.11.0/source lrwxrwxrwx. 1 root root 21 Mar 1 15:22 /var/lib/dkms/r8152/2.11.0/source -> /usr/src/r8152-2.11.0 # dracut -f At least my kbd is still working after 30 minutes. A record on kernels above 4.18.18-300.fc29. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729674]
cc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667750]
cc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Confirmed Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx
[Kernel-packages] [Bug 1667750]
Ref. bug # 1600126 I updated r8152 to v2.11 per https://aur.archlinux.org/packages/r8152-dkms/ makes things more stable. # cd /usr/src/r8152-2.11.0 # patch -p1 <./linux-4.20.0-add-guard-fix.patch # more /usr/src/r8152-2.11.0/dkms.conf PACKAGE_NAME="r8152" PACKAGE_VERSION="2.11.0" BUILT_MODULE_NAME[0]="r8152" DEST_MODULE_LOCATION[0]="/kernel/drivers/net/usb" AUTOINSTALL="yes" # ll /var/lib/dkms/r8152/2.11.0/source lrwxrwxrwx. 1 root root 21 Mar 1 15:22 /var/lib/dkms/r8152/2.11.0/source -> /usr/src/r8152-2.11.0 # dracut -f At least my kbd is still working after 30 minutes. A record on kernels above 4.18.18-300.fc29. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Confirmed Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0:
[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Tested latest kernel 4.15.0-72-generic on bionic.
root@srl-mds1:~# dpkg -l | grep -i ndctl
ii libndctl6 61.2-0ubuntu1~18.04.1
amd64Utility library for managing the libnvdimm subsystem
ii ndctl 61.2-0ubuntu1~18.04.1
amd64Utility for managing the nvdimm subsystem
root@srl-mds1:~# ndctl create-namespace -e "namespace0.0" -m fsdax -f -vvv
enable_labels:945: region0: failed to initialize labels
namespace_reconfig:977: region0: no idle namespace seed
failed to reconfigure namespace: No such device
root@srl-mds1:~#
But if I add --no-autolabel it works
root@srl-mds1:~# ndctl create-namespace --no-autolabel --mode fsdax --map dev
-e namespace0.0 -f -vvv
{
"dev":"namespace0.0",
"mode":"fsdax",
"map":"dev",
"size":"189.00 GiB (202.94 GB)",
"uuid":"4c9523f5-8442-4356-9133-0e48c88c8d8f",
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
root@srl-mds1:~# ndctl create-namespace --no-autolabel --mode fsdax --map dev
-e namespace1.0 -f -vvv
{
"dev":"namespace1.0",
"mode":"fsdax",
"map":"dev",
"size":"189.00 GiB (202.94 GB)",
"uuid":"2a16dd16-df10-4737-abb5-060266070d7e",
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
}
Bionic LTS kernel still needs kernel fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in ndctl:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in ndctl package in Ubuntu:
Fix Released
Status in ndctl source package in Bionic:
Incomplete
Status in ndctl source package in Disco:
Incomplete
Status in ndctl source package in Eoan:
Fix Released
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label
[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Needed --no-autolabel to get it working. New ndctl didn't help. Which is
nice as I didn't have to interrupt metadata operations of the servers
with nvdimm's.
# uname -ar
Linux localhost 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
# ndctl create-namespace --no-autolabel --mode fsdax --map dev -e namespace0.0
-f -vvv
# ndctl create-namespace --no-autolabel --mode fsdax --map dev -e namespace1.0
-f -vvv
# mkfs.xfs -f -m reflink=0 -L PMEM0 /dev/pmem0
# mkfs.ext4 -L PMEM1 -F /dev/pmem1
# mount -o dax /dev/pmem1 /mnt/pmem1-ext4/
# mount -o dax /dev/pmem0 /mnt/pmem0-xfs
# mount | grep dax
/dev/pmem0 on /mnt/pmem0-xfs type xfs (rw,relatime,attr2,dax,inode64,noquota)
/dev/pmem1 on /mnt/pmem1-ext4 type ext4 (rw,relatime,dax,data=ordered)
Nice if this could be fixed in kernels above 4.15.0-62. Thx!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in ndctl:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
Confirmed
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl:
[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
Possible to provide nfit kmod with fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible [Regression Potential] The Regression Risk is low, Intel not impacted but Dell is. [Other Info] Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
Khaled, could you build a test kernel 4.15.0-60-generic with fix please? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible [Regression Potential] The Regression Risk is low, Intel not impacted but Dell is. [Other Info] Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
Tested latest ndctl version 66 with ubuntu 4.15.0-60-generic Still the same issue. Do I need a kernel fix? root@srl-mds2:~# module load ndctl/66 root@srl-mds2:~# which ndctl /cm/shared/apps/ndctl/66/bin/ndctl root@srl-mds2:~# ldd /cm/shared/apps/ndctl/66/bin/ndctl linux-vdso.so.1 (0x77ffa000) libndctl.so.6 => /cm/shared/apps/ndctl/66/usr/lib/libndctl.so.6 (0x77985000) libdaxctl.so.1 => /cm/shared/apps/ndctl/66/usr/lib/libdaxctl.so.1 (0x7777d000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x77576000) libjson-c.so.3 => /lib/x86_64-linux-gnu/libjson-c.so.3 (0x7736b000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x77167000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x76d76000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x76b58000) libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x76941000) /lib64/ld-linux-x86-64.so.2 (0x77dd5000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x76739000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7651a000) root@srl-mds2:~# ndctl create-namespace --mode fsdax --map dev -e namespace0.0 -f -vvv enable_labels:1029: region0: failed to initialize labels namespace_reconfig:1061: region0: no idle namespace seed failed to reconfigure namespace: No such device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible [Regression Potential] The Regression Risk is low, Intel not impacted but Dell is. [Other Info] Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
Seeing this on bionic with 4.15.0-60-generic x86_64 kernel.
Any movement on this issue?
root@srl-mds2:~# uname -ar
Linux srl-mds2 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
root@srl-mds2:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":206158430208,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":206158430208,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@srl-mds2:~# ndctl create-namespace -e "namespace0.0" -m fsdax -f -vvv
enable_labels:945: region0: failed to initialize labels
namespace_reconfig:977: region0: no idle namespace seed
failed to reconfigure namespace: No such device
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811660
Title:
[SRU] Unable to modify/create-namespace over NVDIMM-N
Status in The Dell-poweredge project:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
Users are unable to modify or create namespaces over NVDIMM-N
[Test Case]
Steps to Reproduce:
1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS &
NVDIMM firmware to latest available to customers.
2. Install and boot to Ubuntu 18.04
3. Notice that no pmems are enumerated.
4. Try #ndctl create-namespace -> Failure with device or resource busy.
Actual results:
No pmems are enumerated, cannot create namespaces.
If pmems are already present, then cannot modify the namespaces.
Expected results:
namespace creation should be possible
[Regression Potential]
The Regression Risk is low, Intel not impacted but Dell is.
[Other Info]
Additional Info:
* Seen with upstream linux-4.20.2 also.
* Upstream bug report -
https://github.com/pmem/ndctl/issues/78
* Upstream kernel patch:
https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html
Request you to incorporate it in bionic and xenial kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Dell 5530 fw1.8.1 w/TB16 fw 1.0.2. Tested on 5.0.9-200.fc29.x86_64. Can confirm that my WAR still works. If I reboot Win10 prior to booting Linux, it is stable. Even if I undock and dock it through the day. If I reboot Linux twice, it fails after minutes, definitely within 15min. Haven't tested yet on Ubuntu 19.04 with 5.0.9-050009-generic mainline (PPA) yet, but I expect it will be the same. Things were pretty stable on 1.0.0 fw and kernels upto 4.18.18. Is it a xhci_hcd return code that is not handled properly from Dell TB16 (and some other thunderbolt) docks? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Still seeing this on 5.0.6. PPA mainline. Booting windows prior to linux is WAR for me. Dell 5530 w/TB16. Don't think it is fixed in 5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
** Attachment added: "Flasing TB16 fails on MST2 firmware" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/+attachment/5245802/+files/Capture-thunderbird-flash-fails-MST2-no-serial.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber:
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Dell M5530 1.8.1 w/TB16 1.0.2. TB16 firmware flashed in Win10 fails on MST2 firmware. Seeing the same on Fedora 29 w/ 5.0.1-300.fc30.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1600126 WorkARound for me is booting Win10 before booting Linux. Then I can hotplug as much as I want. If I boot linux twice, it fails after minutes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Seeing the same on fedora 29 4.20.13-200. Dell Precision 5530 w/bios 1.8.1 and TB16 w/fw 1.0.2, i.e. latest firmware. Updated r8152-dkms v2.11 which seem to have improves stability. [ 4973.999515] xhci_hcd :0a:00.0: ERROR unknown event type 15 [ 4979.397428] xhci_hcd :0a:00.0: xHCI host not responding to stop endpoint command. [ 4979.397475] xhci_hcd :0a:00.0: xHCI host controller not responding, assume dead [ 4979.397480] xhci_hcd :0a:00.0: xHCI host not responding to stop endpoint command. [ 4979.397538] r8152 6-1.2:1.0 ens4u1u2: Stop submitting intr, status -108 [ 4979.397539] hub 6-1:1.0: hub_ext_port_status failed (err = -22) [ 4979.397542] usb 6-1.1: Port disable: can't disable remote wake [ 4979.397545] usb 6-1-port1: cannot disable (err = -22) [ 4979.397548] usb 5-1.5: Failed to suspend device, error -22 [ 4979.397550] xhci_hcd :0a:00.0: HC died; cleaning up [ 4979.397563] usb 5-1: USB disconnect, device number 2 [ 4979.397565] usb 5-1.1: USB disconnect, device number 3 [ 4979.397566] usb 5-1.1.1: USB disconnect, device number 6 [ 4979.397568] usb 5-1.1.1.4: USB disconnect, device number 9 [ 4979.397619] usb 6-1: USB disconnect, device number 2 [ 4979.397621] usb 6-1.1: USB disconnect, device number 3 [ 4979.398000] usb 6-1.2: USB disconnect, device number 4 [ 4979.513039] usb 5-1.1.2: USB disconnect, device number 7 [ 4979.540818] usb 5-1.1.5: USB disconnect, device number 8 [ 4979.541293] usb 5-1.4: USB disconnect, device number 4 [ 4979.541437] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 [ 4979.541460] pl2303 5-1.4:1.0: device disconnected [ 4979.541613] usb 5-1.5: USB disconnect, device number 5 [ 4979.608182] userif-3: sent link down event. [ 4979.608184] userif-3: sent link up event. # echo -n ":0a:00.0" >/sys/bus/pci/drivers/xhci_hcd/unbind # echo -n ":0a:00.0" >/sys/bus/pci/drivers/xhci_hcd/bind https://bugzilla.redhat.com/show_bug.cgi?id=1600126 ** Bug watch added: Red Hat Bugzilla #1600126 https://bugzilla.redhat.com/show_bug.cgi?id=1600126 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107]
