[Kernel-packages] [Bug 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
This bug was fixed in the package linux-bluefield - 5.4.0-1047.52 --- linux-bluefield (5.4.0-1047.52) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1047.52 -proposed tracker (LP: #1989866) * Focal update: v5.4.208 upstream stable release (LP: #1988225) - [Config] bluefield: updateconfigs for IMA_TEMPLATE - [Config] bluefield: updateconfigs for REFCOUNT_FULL * mlxbf-pmc: error when reading unprogrammed events (LP: #1989172) - SAUCE: mlxbf-pmc: Fix error when reading unprogrammed events * mlxbf_gige: need to clear MDIO gateway lock after read (LP: #1989495) - SAUCE: mlxbf_gige: clear MDIO gateway lock after read [ Ubuntu: 5.4.0-128.144 ] * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' [ Ubuntu: 5.4.0-127.143 ] * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap
[Kernel-packages] [Bug 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
This bug is awaiting verification that the linux- bluefield/5.15.0-1008.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
This bug is awaiting verification that the linux-bluefield/5.4.0-1047.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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
