[Bug 2076216] Re: Ubuntu 24.04 LTS kernel 6.8.0-35 fails to boot up and get stuck at efi stub measured initrd data into pcr 9
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-ubuntu-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076216 Title: Ubuntu 24.04 LTS kernel 6.8.0-35 fails to boot up and get stuck at efi stub measured initrd data into pcr 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
hey Olivier Gayot, One further question, we are indeed using "user-data" automated installer methodology, so we can simply append it(i did notice the last line is version :1) with the following to our user-data file to work around this issue, right? debconf-selections: | grub-pc grub-efi/cloud_style_installation boolean false interactive-sections: ["*"] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
hey Olivier Gayot, The workaround you provided works like a charm, also thanks for the elaboration. I finally got Ubuntu 24.04 Beta installed successfully on my system. You are my lifesaver! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
Couple of questions: 1.sounds like this is a catastrophic issue that block fresh Ubuntu 24.04 Beta installation, isn't it? 2. so we have to wait for the new ISO image that includes the new grub2? If yes, when do we expect to get the new ISO image. Now we are doing some early evaluation work for Ubuntu 24.04 Beta with a tight schedule. It would be greatly helpful if there is a workaround. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
looks like i am hitting the exact same issue, may i know what can i do to get the Ubuntu 24.04 daily build installation to complete successfully instead of trying new ISO? Thanks a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969342] Re: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04
we have learned that the in-tree ice driver support for OP_SET_RSS_HENA has never been upstreamed, so we will track this issue as a future requirement, and will revisit this issue once the in-tree ice driver support for OP_SET_RSS_HENA has been upstreamed and backported. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969342 Title: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970077] Re: efivars file system missing in Ubuntu 22.04 real-time kernel
# uname -r 5.15.0-1009-realtime -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970077 Title: efivars file system missing in Ubuntu 22.04 real-time kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970077] Re: efivars file system missing in Ubuntu 22.04 real-time kernel
we have tried the latest available RT kernel 5.15.0-1009-realtime, it's still not there. Could u please help check? Let me know if you need other logs. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970077 Title: efivars file system missing in Ubuntu 22.04 real-time kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970077] Re: efivars file system missing in Ubuntu 22.04 real-time kernel
~# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=98812568k,nr_inodes=24703142,mode=755,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=19773308k,mode=755,inode64) /dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime,stripe=64) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=138479) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) none on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) /var/lib/snapd/snaps/core20_1405.snap on /snap/core20/1405 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /var/lib/snapd/snaps/lxd_22923.snap on /snap/lxd/22923 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /var/lib/snapd/snaps/snapd_15534.snap on /snap/snapd/15534 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /dev/sda2 on /boot type ext4 (rw,relatime,stripe=64) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=19773308k,mode=755,inode64) nsfs on /run/snapd/ns/lxd.mnt type nsfs (rw) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=19773304k,nr_inodes=4943326,mode=700,inode64) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970077 Title: efivars file system missing in Ubuntu 22.04 real-time kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970077] [NEW] efivars file system missing in Ubuntu 22.04 real-time kernel
Public bug reported: In Ubuntu 22.04 generic kernel like 5.15.0-23, efivars file system is mounted and is visible in the output of mount command, however in Ubuntu 22.04 real-time kernel like 5.15.0-1005-realtime or 5.15.0-1007-realtime, efivars file system is missing. Intel SGX feature relies on efivars file system to function, could u please investigate this issue? Thanks. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970077 Title: efivars file system missing in Ubuntu 22.04 real-time kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1970077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969454] Re: dpdk-testpmd test shows "init vf failed" with in-tree driver on ubuntu22.04
DPDK 20.11 or DPDK 21.11, the same result -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969454 Title: dpdk-testpmd test shows "init vf failed" with in-tree driver on ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969452] Re: packets fail to be distributed to the right queue and marked with expected FDIR ID with DPDK AVF
/root/dpdk-21.11/build/app/dpdk-testpmd -c 0xff -n 6 -a 00:06.0 --file-prefix=vf -- -i --rxq=16 --txq=16 testpmd> set fwd rxonly testpmd> set verbose 1 testpmd> start the flow director rule examples are like below: flow create 0 ingress pattern eth / ipv4 src is 192.168.100.1 dst is 192.168.100.2 ttl is 2 tos is 4 / udp src is 22 dst is 23 / end actions queue index 11 / mark id 0 / end flow create 0 ingress pattern eth / ipv4 src is 192.168.100.1 dst is 192.168.100.2 ttl is 2 tos is 4 / tcp src is 22 dst is 23 / end actions rss queues 0 1 2 3 end / mark id 4294967294 / end flow create 0 ingress pattern eth / ipv4 src is 192.168.100.1 dst is 192.168.100.2 ttl is 2 tos is 4 / tcp src is 22 dst is 23 / end actions queue index 11 / mark id 0 / end flow create 0 ingress pattern eth / ipv4 src is 192.168.100.1 dst is 192.168.100.2 ttl is 2 tos is 4 / udp src is 22 dst is 23 / end actions rss queues 0 1 2 3 end / mark id 4294967293 / end -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969452 Title: packets fail to be distributed to the right queue and marked with expected FDIR ID with DPDK AVF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969454] [NEW] dpdk-testpmd test shows "init vf failed" with in-tree driver on ubuntu22.04
Public bug reported: run ./dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 with vf port ,the detail log root@sp:/opt/APP/utility/dpdk-stable-20.11.3/build/app# ./dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 EAL: Detected 128 lcore(s) EAL: Detected 2 NUMA nodes EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: No available hugepages reported in hugepages-2048kB EAL: Probing VFIO support... EAL: VFIO support initialized EAL: using IOMMU type 1 (Type 1) EAL: Probe PCI driver: net_iavf (8086:1889) device: :16:01.0 (socket 0) iavf_init_vf(): VF is still resetting iavf_dev_init(): Init vf failed EAL: Releasing pci mapped resource for :16:01.0 EAL: Calling pci_unmap_resource for :16:01.0 at 0x22 EAL: Calling pci_unmap_resource for :16:01.0 at 0x220002 EAL: Requested device :16:01.0 cannot be used EAL: using IOMMU type 1 (Type 1) EAL: Probe PCI driver: net_iavf (8086:1889) device: :16:09.0 (socket 0) iavf_init_vf(): VF is still resetting iavf_dev_init(): Init vf failed EAL: Releasing pci mapped resource for :16:09.0 EAL: Calling pci_unmap_resource for :16:09.0 at 0x2200024000 EAL: Calling pci_unmap_resource for :16:09.0 at 0x2200044000 EAL: Requested device :16:09.0 cannot be used EAL: No legacy callbacks, legacy socket not created testpmd: No probed ethernet devices Interactive-mode selected testpmd: create a new mbuf pool : n=171456, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc Done testpmd> ** Affects: dpdk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969454 Title: dpdk-testpmd test shows "init vf failed" with in-tree driver on ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969452] [NEW] packets fail to be distributed to the right queue and marked with expected FDIR ID with DPDK AVF
Public bug reported: the expected result is packets are distributed to the specified queue and marked with specified FDIR matched ID, but the actual result is NOT. -DPDK 21.11 or DPDK 20.11, the same result. -we have tried at least out-of-tree driver 1.8.3, it works as expected. So basically we can conclude that the AVF functionality of intree ice driver doesn't work as expected. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969452 Title: packets fail to be distributed to the right queue and marked with expected FDIR ID with DPDK AVF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969342] Re: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04
ok, thanks for moving this around. Feel free to let me know if you need further info to debug this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969342 Title: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874161] Re: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file
I see! Thank you very much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874161 Title: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpcli/+bug/1874161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874161] Re: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file
I have a correction to my previous comment: Instead of asking, "Is this behavior of Keepass new?" I want to convey, "Is this behavior of KeePassX new?" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874161 Title: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpcli/+bug/1874161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874161] Re: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file
The file command shows that my file is a 2.x KDBX file. I tried creating a new database file with KeePassX with the KDBX extension. The file command shows the new database file is also a 2.x KDBX file. I also tried creating a database file with KeePassX with the KDB extension. The file command also shows this second new file is a 2.x KDBX file. It seems like the installation of KeePassX from Ubuntu 18.04's repos generates v2 Keepass file. Is this behavior of Keepass new? Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874161 Title: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpcli/+bug/1874161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874161] Re: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file
Hello Lester, Thank you for your guidance. I tried renaming the kdbx file to end with a kdb extension instead. I then used kpcli to try opening the kdb file with the same key file, but I still encountered the same error: Couldn't load the file kpstuff2.kdb: The database key appears invalid or else the database is corrupt. Is there another way to test if the file is a v1 or v2 Keepass file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874161 Title: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpcli/+bug/1874161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874161] [NEW] kpcli is unable to open a kdbx file if the file is locked by both a password and a key file
Public bug reported: I created a kdbx file through the KeePassX GUI application. This database is locked with both a password and a key file. I try to unlock the database through the kpcli command line tool with the following commands inside the kpcli prompt: open I am then prompted for my password. After I enter my password, kpcli presents to me the following error message: Couldn't load the file kpstuff2.kdbx: The database key appears invalid or else the database is corrupt. However, I am able to unlock the file through the KeePassX GUI application. I am also able to unlock other database files that are locked only with a password. I am unable to unlock databases that are locked with both a password and a key file. Expected behavior: I think kpcli should be able to unlock a database with a password and a key file if the key file is generated through KeePassX. System information: Description:Ubuntu 18.04.4 LTS Release:18.04 kpcli package info: kpcli: Installed: 3.1-3 Candidate: 3.1-3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kpcli 3.1-3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 21 18:01:58 2020 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: kpcli UpgradeStatus: Upgraded to bionic on 2019-03-06 (412 days ago) ** Affects: kpcli (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874161 Title: kpcli is unable to open a kdbx file if the file is locked by both a password and a key file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpcli/+bug/1874161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807411] [NEW] VLAN stripping function will be called after running "ethtool -K rx off" to change the rx checksum setting
Private bug reported: check the ftrace ,it shows VLAN stripping setting was changed Description of problem: When running “ethtool –K rx off” for VF, the i40evf will also change the VLAN stripping setting unexpectedly. We tried to create a VF on Ubuntu18.04.1 in-tree i40e driver then ran "ethtool -K rx off" for it with the in-tree i40evf driver. The ftrace showed as below: i40evf_set_features [i40evf] -> i40evf_enable_vlan_stripping [i40evf]-> i40e_vlan_stripping_enable [i40e]. Version-Release number of selected component (if applicable): RHEL7.6 Alpha kernel: 3.10.0-924.el7.x86_64 i40e driver: 2.1.14-k i40evf driver: 3.0.1-k ethtool version 4.15 repro steps and logs: root@unassigned-hostname:~# echo i40evf_set_features >> /sys/kernel/debug/tracing/set_graph_function root@unassigned-hostname:~# echo i40evf_enable_vlan_stripping >> /sys/kernel/debug/tracing/set_graph_function root@unassigned-hostname:~# echo 20 > /sys/kernel/debug/tracing/max_graph_depth root@unassigned-hostname:~# echo function_graph > /sys/kernel/debug/tracing/current_tracer root@unassigned-hostname:~# echo 1 > /sys/kernel/debug/tracing/tracing_on root@unassigned-hostname:~# cat /sys/kernel/debug/tracing/trace # tracer: function_graph # # CPU DURATION FUNCTION CALLS # | | | | | | | root@unassigned-hostname:~# ethtool -K enp175s2 rx off root@unassigned-hostname:~# cat /sys/kernel/debug/tracing/trace # tracer: function_graph # # CPU DURATION FUNCTION CALLS # | | | | | | | 60) 0.254 us| i40evf_set_features [i40evf](); 20) | i40evf_enable_vlan_stripping [i40evf]() { 20) |i40evf_send_pf_msg [i40evf]() { 20) | i40e_aq_send_msg_to_pf [i40evf]() { 20) 0.137 us|i40evf_fill_default_direct_cmd_desc [i40evf](); 20) |i40evf_asq_send_command [i40evf]() { 20) | mutex_lock() { 20) |_cond_resched() { 20) 0.144 us| rcu_all_qs(); 20) 1.215 us|} 20) 2.350 us| } 20) 0.145 us| i40evf_debug_d [i40evf](); 20) 0.105 us| i40evf_debug_d [i40evf](); 20) 0.148 us| i40evf_debug_aq [i40evf](); 20) 0.112 us| i40evf_debug_d [i40evf](); 20) 0.117 us| i40evf_debug_aq [i40evf](); 20) 0.163 us| mutex_unlock(); 20) + 13.471 us |} 20) + 15.886 us | } 20) + 17.167 us |} 20) + 18.831 us | } 22) | i40e_vlan_stripping_enable [i40e]() { 22) |i40e_vlan_stripping_enable.part.86 [i40e]() { 22) | i40e_aq_update_vsi_params [i40e]() { 22) 0.172 us|i40e_fill_default_direct_cmd_desc [i40e](); 22) |i40e_asq_send_command [i40e]() { 22) | mutex_lock() { 22) |_cond_resched() { 22) 0.124 us| rcu_all_qs(); 22) 1.183 us|} 22) 2.220 us| } 22) 0.124 us| i40e_debug_aq [i40e](); 22) + 49.861 us | delay_tsc(); 22) 0.121 us| i40e_debug_aq [i40e](); 22) 0.113 us| mutex_unlock(); 22) + 61.631 us |} 22) + 63.982 us | } 22) + 65.264 us |} 22) + 66.720 us | } ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807411 Title: VLAN stripping function will be called after running "ethtool -K rx off" to change the rx checksum setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806845] Re: The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working
Here're the reproduce steps of this issue, also attached the errors in dmesg log which were triggered by this issue. root@unassigned-hostname:~# ethtool -i enp24s0f0 driver: i40e version: 2.1.14-k firmware-version: 6.02 0x80003620 1.1747.0 expansion-rom-version: bus-info: :18:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes root@unassigned-hostname:~# echo 1 > /sys/bus/pci/devices/\:18\:00.0/sriov_numvfs root@unassigned-hostname:~# ip link set dev enp24s0f0 vf 0 mac 00:10:00:00:00:00 root@unassigned-hostname:~# echo "dump vf 0" > /sys/kernel/debug/i40e/\:18\:00.0/command root@unassigned-hostname:~# echo "dump vsi 394" > /sys/kernel/debug/i40e/\:18\:00.0/command root@unassigned-hostname:~# ip link set dev enp24s2 address 00:10:00:00:00:00 root@unassigned-hostname:~# ip link set dev enp24s2 address 00:20:00:00:00:00 root@unassigned-hostname:~# echo "dump vsi 394" > /sys/kernel/debug/i40e/\:18\:00.0/command ** Attachment added: "dmesg_log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806845/+attachment/5219663/+files/dmesg_log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806845 Title: The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806845] [NEW] The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working
Public bug reported: The unsigned vf->num_mac in Ubuntu18.04.1 LTS i40e driver 2.1.14-k will be decreased to below zero when VF is trying to delete the MAC address which is added by PF and then add a new MAC address. And after this issue happens, VF won't be able to send/receive packets, and excepting for broadcast address, mac_filter_hash is empty in dumped VSI info. Ubuntu18.04.1 LTS kernel: 4.15.0-38-generic i40e driver: 2.1.14-k i40evf driver: 3.0.1-k Actual results: The unsigned vf->num_mac should decrease to below zero. The VF port doesn't work. Expected results: The unsigned vf->num_mac range is from 0 to 65535; or the vf is not allowed to delete the MAC addr which is added by PF Corresponding Patch is required for resolving this i40e driver issue i40e: Prevent deleting MAC address from VF when set by PF https://patchwork.ozlabs.org/patch/963036/ ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bot-comment i40e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806845 Title: The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1806845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400026] [NEW] Geeqie only prints 1-letter keywords
Public bug reported: Description:Ubuntu 14.04.1 LTS Release:14.04 geeqie package version 1:1.1-8 What I expected to happen: Keywords can be entered without having a newline break apart every character. Pressing delete would delete characters. What happened instead: Keywords longer than 1 letter can not be entered into Geeqie. Attempting to enter any word as a keyword ends up with Geeqie inserting a newline after every character. Pressing backspace does not delete any characters. No key can be entered consecutively. Screenshot attached. ** Affects: geeqie (Ubuntu) Importance: Undecided Status: New ** Tags: geeqie ** Attachment added: "Shows the keyword issue. Enter was not pressed while pressing keys" https://bugs.launchpad.net/bugs/1400026/+attachment/4275560/+files/JExIfCx.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400026 Title: Geeqie only prints 1-letter keywords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geeqie/+bug/1400026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs