[Kernel-packages] [Bug 2017148] [NEW] USB devices stops working on ASUS Z790-A motherboard
Public bug reported: >From time to time especially when multiple decice are connected there's total >freeze of USB devices, so external soundcard, camera, keyboard, mouse stops >working at the same time. Replugin does not help and you can only reboot the >machine, but beyond that all seems working. It can freeze during the online meeting with Google Meet on Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 17:19:33 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Summary changed: - USB devices stops working ASUS Z790-A motherboard + USB devices stops working on ASUS Z790-A motherboard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017148 Title: USB devices stops working on ASUS Z790-A motherboard Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: From time to time especially when multiple decice are connected there's total freeze of USB devices, so external soundcard, camera, keyboard, mouse stops working at the same time. Replugin does not help and you can only reboot the machine, but beyond that all seems working. It can freeze during the online meeting with Google Meet on Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 17:19:33 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2017148/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
It seems like it is heavily related to bond driver.
Here's another case
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008781
As this might be related.
--
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/2004262
Title:
Intel E810 NICs driver in causing hangs when booting and bonds
configured
Status in linux package in Ubuntu:
Confirmed
Bug description:
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
After beonding is enabled on switch and server side, the system will hang at
initialing ubuntu. The kernel loads but around starting the Network Services
the system can hang for sometimes 5 minutes, and in other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start
and never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup
and all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy
uec-images
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/14/2022
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 0PJ7YJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge R650
dmi.product.sku: SKU=0912;ModelName=PowerEdge R650
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card
** Changed in: linux (Ubuntu) Status: Incomplete => 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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root audio 116, 33 Feb 27 13:33 timer AplayDevices: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card
** Attachment added: "sosreport-compute-05-2004262-2023-02-28-wubkvmj.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008781/+attachment/5650469/+files/sosreport-compute-05-2004262-2023-02-28-wubkvmj.tar.xz -- 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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices:
[Kernel-packages] [Bug 2008781] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650468/+files/acpidump.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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root
[Kernel-packages] [Bug 2008781] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650467/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1
[Kernel-packages] [Bug 2008781] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650466/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root audio
[Kernel-packages] [Bug 2008781] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650465/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1
[Kernel-packages] [Bug 2008781] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650464/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq
[Kernel-packages] [Bug 2008781] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650463/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1
[Kernel-packages] [Bug 2008781] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650462/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq
[Kernel-packages] [Bug 2008781] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650461/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1
[Kernel-packages] [Bug 2008781] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650460/+files/Lsusb-v.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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root
[Kernel-packages] [Bug 2008781] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650459/+files/Lspci-vt.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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root
[Kernel-packages] [Bug 2008781] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650457/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1
[Kernel-packages] [Bug 2008781] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650458/+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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root audio
[Kernel-packages] [Bug 2008781] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2008781/+attachment/5650456/+files/CRDA.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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 13:33 seq crw-rw 1 root audio 116,
[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card
apport information ** Tags added: apport-collected focal uec-images ** Description changed: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-provider2:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. 64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.99.0.213 PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data. 64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am referring to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Feb 27 13:33 seq + crw-rw 1 root audio 116, 33 Feb 27 13:33 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.25 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card
Also checked the correct ovn trace As the packets should reach the destination if driver was behaving correctly ubuntu@juju-7639a4-3-lxd-6:~$ network="provider1-net-external" inport="4679fbb8-3d4d-4dcd-b986-4ec4c0fb9000" ip4_src="10.99.0.88" ip4_dst="10.99.0.254" eth_src="fa:16:3e:ab:87:ad" ubuntu@juju-7639a4-3-lxd-6:~$ sudo ovn-trace "$network" "inport == \"$inport\" && ip4.src == "$ip4_src" && ip4.dst == "$ip4_dst" && eth.src == "$eth_src" && ip.ttl == 64 && icmp4.type == 8" # icmp,reg14=0x3,vlan_tci=0x,dl_src=fa:16:3e:ab:87:ad,dl_dst=00:00:00:00:00:00,nw_src=10.99.0.88,nw_dst=10.99.0.254,nw_tos=0,nw_ecn=0,nw_ttl=64,icmp_type=8,icmp_code=0 ingress(dp="provider1-net-external", inport="4679fb") --- 0. ls_in_port_sec_l2 (northd.c:5516): inport == "4679fb", priority 50, uuid 03e0a90b next; 6. ls_in_pre_lb (northd.c:5663): ip && inport == "4679fb", priority 110, uuid f5e890b2 next; 24. ls_in_l2_lkup (northd.c:7577): 1, priority 0, uuid 3aba4e5b outport = get_fdb(eth.dst); next; 25. ls_in_l2_unknown (northd.c:7581): outport == "none", priority 50, uuid 0bf357af outport = "_MC_unknown"; output; multicast(dp="provider1-net-external", mcgroup="_MC_unknown") --- egress(dp="provider1-net-external", inport="4679fb", outport="provnet-8d6ece") 0. ls_out_pre_lb (northd.c:5666): ip && outport == "provnet-8d6ece", priority 110, uuid ddd2f5b5 next; 9. ls_out_port_sec_l2 (northd.c:5613): outport == "provnet-8d6ece", priority 50, uuid 966e0b90 output; /* output to "provnet-8d6ece", type "localnet" */ -- 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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan
[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card
** Description changed: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - - The test instance with provider network floating ip 10.40.0.213 cannot reach the provider network gateway - openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net analyse-private-net ubuntu-analyse + The test instance with provider network floating ip 10.99.0.213 cannot reach the provider network gateway + openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net provider1-private-net ubuntu-provider1 ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 - ubuntu@ubuntu-analyse:~$ ping 10.40.0.254 - PING 10.40.0.254 (10.40.0.254) 56(84) bytes of data. + ubuntu@ubuntu-provider1:~$ ping 10.99.0.254 + PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data. ^C - --- 10.40.0.254 ping statistics --- + --- 10.99.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms - I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' - tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.40.0.254 tell 10.40.0.88, length 28 - fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.40.0.254 tell 10.40.0.88, length 28 - fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.40.0.254 tell 10.40.0.88, length 28 + tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 + fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 + fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.99.0.254 tell 10.99.0.88, length 28 For the test you may ping .254 indifenetely - The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error - tx_errors: 12 - tx_errors.nic: 0 - rx_length_errors.nic: 0 - rx_crc_errors.nic: 0 + tx_errors: 12 + tx_errors.nic: 0 + rx_length_errors.nic: 0 + rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 - ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) - RX packets 53784 bytes 22064970 (22.0 MB) - RX errors 0 dropped 0 overruns 0 frame 0 - TX packets 52163 bytes 18393142 (18.3 MB) - TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 + ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) + RX packets 53784 bytes 22064970 (22.0 MB) + RX errors 0 dropped 0 overruns 0 frame 0 + TX packets 52163 bytes 18393142 (18.3 MB) + TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem - so that creates opportunity for + so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device - - Anonother thing I tried was to install the HWE kernel + Another thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux - Fortunately traffic was still going out from compute-09 after reboot, + Fortunately traffic was still
[Kernel-packages] [Bug 2008781] [NEW] OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card
Public bug reported: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether 31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) 31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) The test instance with provider network floating ip 10.40.0.213 cannot reach the provider network gateway openstack server create --key-name ubuntu-keypair --image auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small --net analyse-private-net ubuntu-analyse ubuntu@compute-05:~$ sudo -E ip netns exec ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123 ubuntu@ubuntu-analyse:~$ ping 10.40.0.254 PING 10.40.0.254 (10.40.0.254) 56(84) bytes of data. ^C --- 10.40.0.254 ping statistics --- 419 packets transmitted, 0 received, 100% packet loss, time 428035ms I found the compute from which the outside traffic is going out and I see ARP requests with no response compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)' tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.40.0.254 tell 10.40.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.40.0.254 tell 10.40.0.88, length 28 fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.40.0.254 tell 10.40.0.88, length 28 For the test you may ping .254 indifenetely The error count grows on tx packets on bond1 and the card ens2f0 (which happens to push the traffic) ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error tx_errors: 12 tx_errors.nic: 0 rx_length_errors.nic: 0 rx_crc_errors.nic: 0 ubuntu@compute-09:~$ ifconfig ens2f0 ens2f0: flags=6211 mtu 9000 ether b4:83:51:00:83:d1 txqueuelen 1000 (Ethernet) RX packets 53784 bytes 22064970 (22.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52163 bytes 18393142 (18.3 MB) TX errors 12 dropped 0 overruns 0 carrier 0 collisions 0 If I create vlan interface directly on bond1 I can ping the gateway with no problem so that creates opportunity for WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on computes as for physnet device Anonother thing I tried was to install the HWE kernel ubuntu@compute-09:~$ uname -a Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Fortunately traffic was still going out from compute-09 after reboot, that fixed the issue so we have WORKAROUND 2 ubuntu@ubuntu-analyse:~$ ping 10.40.0.254 PING 10.40.0.254 (10.40.0.254) 56(84) bytes of data. 64 bytes from 10.40.0.254: icmp_seq=1 ttl=63 time=2.15 ms 64 bytes from 10.40.0.254: icmp_seq=2 ttl=63 time=0.896 ms 64 bytes from 10.40.0.254: icmp_seq=3 ttl=63 time=1.12 ms ^C ubuntu@infra-1:~$ ping 10.40.0.213 PING 10.40.0.213 (10.40.0.213) 56(84) bytes of data. 64 bytes from 10.40.0.213: icmp_seq=1 ttl=62 time=5.12 ms 64 bytes from 10.40.0.213: icmp_seq=2 ttl=62 time=2.17 ms 64 bytes from 10.40.0.213: icmp_seq=3 ttl=62 time=0.948 ms 64 bytes from 10.40.0.213: icmp_seq=4 ttl=62 time=1.00 ms 64 bytes from 10.40.0.213: icmp_seq=5 ttl=62 time=0.891 ms 64 bytes from 10.40.0.213: icmp_seq=6 ttl=62 time=1.05 ms Now I can ping both ways However I am afraid that we may encounter same issue like for Jammy for the cards when booting, as it happens randomly for the kernel with the same number 5.15.0-60 Here's the bug I am reffering https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug openstack ovn vlan -- 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/2008781 Title: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04.5 LTS ubuntu@compute-09:~$ uname -a Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@compute-09:~$ sudo update-pciids ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
[Kernel-packages] [Bug 1997172] [NEW] package nvidia-dkms-520 520.56.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error
Public bug reported: I got nvidia-dkms-520-open installed. When trying to install nvidia-dkms-520 (proprietary) it will fail. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-520 520.56.06-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 20 16:08:43 2022 ErrorMessage: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-520 Title: package nvidia-dkms-520 520.56.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-520 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1997172 Title: package nvidia-dkms-520 520.56.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: I got nvidia-dkms-520-open installed. When trying to install nvidia-dkms-520 (proprietary) it will fail. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-520 520.56.06-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 20 16:08:43 2022 ErrorMessage: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-520 Title: package nvidia-dkms-520 520.56.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1997172/+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 1972831] Re: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3
That was after upgrade from Focal to Jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1972831 Title: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3 Status in bluez package in Ubuntu: New Bug description: I think that the issue might be partly because I have pulseaudio-bt- modules package with alternative codecs I removed tht package but still same issue lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53 lut 07 22:14:40 graf systemd[1]: Started Bluetooth service. lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 initialized lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/SBC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/SBC lut 08 08:37:50 graf bluetoothd[1366]: Terminating ...skipping... maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:58:45 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:59:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:01:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:02:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:03:23 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:04:33 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:05:42
[Kernel-packages] [Bug 1972831] Re: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3
Seems there's no default dependency neither on ubuntu-desktop or bluetooth meta package -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1972831 Title: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3 Status in bluez package in Ubuntu: New Bug description: I think that the issue might be partly because I have pulseaudio-bt- modules package with alternative codecs I removed tht package but still same issue lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53 lut 07 22:14:40 graf systemd[1]: Started Bluetooth service. lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 initialized lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/SBC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/SBC lut 08 08:37:50 graf bluetoothd[1366]: Terminating ...skipping... maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:58:45 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:59:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:01:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:02:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:03:23 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:04:33 graf bluetoothd[1293]: Controller
[Kernel-packages] [Bug 1972831] Re: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3
Ok,seems the culprit was missing package, not installed $ sudo apt install pulseaudio-module-bluetooth Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: pulseaudio-module-bluetooth 0 upgraded, 1 newly installed, 0 to remove and 16 not upgraded. Need to get 99,0 kB of archives. After this operation, 430 kB of additional disk space will be used. Get:1 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 pulseaudio-module-bluetooth amd64 1:15.99.1+dfsg1-1ubuntu1 [99,0 kB] Fetched 99,0 kB in 0s (758 kB/s) Selecting previously unselected package pulseaudio-module-bluetooth. (Reading database ... 310011 files and directories currently installed.) Preparing to unpack .../pulseaudio-module-bluetooth_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ... Unpacking pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu1) ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1972831 Title: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3 Status in bluez package in Ubuntu: New Bug description: I think that the issue might be partly because I have pulseaudio-bt- modules package with alternative codecs I removed tht package but still same issue lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53 lut 07 22:14:40 graf systemd[1]: Started Bluetooth service. lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 initialized lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/SBC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/SBC lut 08 08:37:50 graf bluetoothd[1366]: Terminating ...skipping... maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10
[Kernel-packages] [Bug 1972831] [NEW] Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3
Public bug reported: I think that the issue might be partly because I have pulseaudio-bt- modules package with alternative codecs I removed tht package but still same issue lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53 lut 07 22:14:40 graf systemd[1]: Started Bluetooth service. lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 initialized lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/SBC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/SBC lut 08 08:37:50 graf bluetoothd[1366]: Terminating ...skipping... maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:58:45 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:59:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:01:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:02:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:03:23 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:04:33 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:05:42 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:06:52 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:08:01 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:08:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:10:26 graf bluetoothd[1293]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:1B:66:E9:99:8F: Protocol not available maj
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
I confirm on focal. WORKAROUND, install linux-firmware package from Impish (1.201) instead of one from focal (1.187) The many kernel errors about PCI devices dissapear during the boot time. Not sure about the real impact on the system itself. sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Bug description: Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris
