[Kernel-packages] [Bug 2051871] [NEW] mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full
Public bug reported: SRU Justification: [Impact] This is a cherry-pick fix from upstream to drop Tx network packet when Tx TmFIFO is full. [Fix] Starting from Linux 5.16 kernel, Tx timeout mechanism was added in the virtio_net driver which prints the "Tx timeout" warning message when a packet stays in Tx queue for too long. Below is an example of the reported message: "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since last trans: 3079892256". This issue could happen when external host driver which drains the FIFO is restared, stopped or upgraded. To avoid such confusing "Tx timeout" messages, this commit adds logic to drop the outstanding Tx packet if it's not able to transmit in two seconds due to Tx FIFO full, which can be considered as congestion or out-of-resource drop. This commit also handles the special case that the packet is half- transmitted into the Tx FIFO. In such case, the packet is discarded with remaining length stored in vring->rem_padding. So paddings with zeros can be sent out when Tx space is available to maintain the integrity of the packet format. The padded packet will be dropped on the receiving side. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2051871 Title: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This is a cherry-pick fix from upstream to drop Tx network packet when Tx TmFIFO is full. [Fix] Starting from Linux 5.16 kernel, Tx timeout mechanism was added in the virtio_net driver which prints the "Tx timeout" warning message when a packet stays in Tx queue for too long. Below is an example of the reported message: "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since last trans: 3079892256". This issue could happen when external host driver which drains the FIFO is restared, stopped or upgraded. To avoid such confusing "Tx timeout" messages, this commit adds logic to drop the outstanding Tx packet if it's not able to transmit in two seconds due to Tx FIFO full, which can be considered as congestion or out-of-resource drop. This commit also handles the special case that the packet is half- transmitted into the Tx FIFO. In such case, the packet is discarded with remaining length stored in vring->rem_padding. So paddings with zeros can be sent out when Tx space is available to maintain the integrity of the packet format. The padded packet will be dropped on the receiving side. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2051871/+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 2002689] [NEW] mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3 SoC
Public bug reported: SRU Justification: [Impact] This is a porting commit from https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253. [Fix] * N/A [Test Case] * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from external rshim driver. The rshim MAC address will show up. # cat /dev/rshim0/misc DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log) BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap) BOOT_TIMEOUT 100 (seconds) DROP_MODE 0 (0:normal, 1:drop) SW_RESET 0 (1: reset) DEV_NAME usb-1-1.1 DEV_INFO BlueField-2(Rev 0) OPN_STR MBF2M516A-EEEO BOOT_RESET_SKIP 0 (1: skip) PEER_MAC 00:1a:ca:ff:ff:01 (rw) PXE_ID 0x (rw) VLAN_ID 0 0 (rw) * echo "PEER_MAC xx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC address, which will take effect in next boot. [Regression Potential] * This is a new enhancement and is backward-compatible with previous behavior. ** Affects: linux-bluefield (Ubuntu) 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/2002689 Title: mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3 SoC Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This is a porting commit from https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253. [Fix] * N/A [Test Case] * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from external rshim driver. The rshim MAC address will show up. # cat /dev/rshim0/misc DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log) BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap) BOOT_TIMEOUT 100 (seconds) DROP_MODE 0 (0:normal, 1:drop) SW_RESET 0 (1: reset) DEV_NAME usb-1-1.1 DEV_INFO BlueField-2(Rev 0) OPN_STR MBF2M516A-EEEO BOOT_RESET_SKIP 0 (1: skip) PEER_MAC 00:1a:ca:ff:ff:01 (rw) PXE_ID 0x (rw) VLAN_ID 0 0 (rw) * echo "PEER_MAC xx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC address, which will take effect in next boot. [Regression Potential] * This is a new enhancement and is backward-compatible with previous behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002689/+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 1927253] Re: mlxbf-tmfifo: Add ctrl message and MAC configuration
I couldn't see the change in https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-bluefield/+git/jammy. Is this the correct repo I should see this commit, or probably takes some time? -- 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/1927253 Title: mlxbf-tmfifo: Add ctrl message and MAC configuration Status in linux-bluefield package in Ubuntu: Fix Released Bug description: THis one is created to track the commit merge of the mlxbf-tmfifo driver to support ctrl message and MAC configuration. SRU Justification: [Impact] * N/A. [Fix] * N/A. [Test Case] * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from external rshim driver. The rshim MAC address will show up. # cat /dev/rshim0/misc DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log) BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap) BOOT_TIMEOUT100 (seconds) DROP_MODE 0 (0:normal, 1:drop) SW_RESET0 (1: reset) DEV_NAMEusb-1-1.1 DEV_INFOBlueField-2(Rev 0) OPN_STR MBF2M516A-EEEO BOOT_RESET_SKIP 0 (1: skip) PEER_MAC00:1a:ca:ff:ff:01 (rw) PXE_ID 0x (rw) VLAN_ID 0 0 (rw) * echo "PEER_MACxx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC address, which will take effect in next boot. [Regression Potential] * This is a new enhancement and is backward-compatible with previous behavior. [Other] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253/+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 2015307] [NEW] mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3
Public bug reported: SRU Justification: [Impact] This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is idle [Fix] The fix implements the runtime PM operations for BlueField-3 SoC to disable the card clock when idle. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2015307 Title: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3 Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is idle [Fix] The fix implements the runtime PM operations for BlueField-3 SoC to disable the card clock when idle. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015307/+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 2016039] [NEW] mlxbf-tmfifo: fix potential race
Public bug reported: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2016039 Title: mlxbf-tmfifo: fix potential race Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+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 2015307] Re: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3
** 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/2015307 Title: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3 Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is idle [Fix] The fix implements the runtime PM operations for BlueField-3 SoC to disable the card clock when idle. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015307/+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 2039325] [NEW] mmc: sdhci-of-dwcmshc: Intermittent data error under stress test
Public bug reported: sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110 SRU Justification: [Impact] This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110" error under stress test [Fix] The fix added a quirk for the BF3 sdhci driver to avoid such data error. [Test Case] 1. Same functionality and testing as on BlueField-1/2. 2. Install OS on NVME, and run the FIO test on EMMC. fio --name=mmcblk0_randrw_stress_round_1 \ --ioengine=libaio --direct=1 --time_based=1 \ --end_fsync=1 --ramp_time=5 --norandommap=1 \ --randrepeat=0 --group_reporting=1 --numjobs=8 \ --iodepth=128 --rw=randrw --overwrite=1 \ --runtime=3600 --bs=4K --filename=/dev/mmcblk0 & [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2039325 Title: mmc: sdhci-of-dwcmshc: Intermittent data error under stress test Status in linux-bluefield package in Ubuntu: New Bug description: sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110 SRU Justification: [Impact] This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110" error under stress test [Fix] The fix added a quirk for the BF3 sdhci driver to avoid such data error. [Test Case] 1. Same functionality and testing as on BlueField-1/2. 2. Install OS on NVME, and run the FIO test on EMMC. fio --name=mmcblk0_randrw_stress_round_1 \ --ioengine=libaio --direct=1 --time_based=1 \ --end_fsync=1 --ramp_time=5 --norandommap=1 \ --randrepeat=0 --group_reporting=1 --numjobs=8 \ --iodepth=128 --rw=randrw --overwrite=1 \ --runtime=3600 --bs=4K --filename=/dev/mmcblk0 & [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039325/+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 2021749] [NEW] mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
Public bug reported: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+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 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
Fixes have been posted for review for both Jammy and Focal. ** Description changed: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] - Same functionality and testing as on BlueField-1/2/2. No functionality change. - Add negative tests: + Same functionality and testing as on BlueField-1/2/3. No functionality change. + Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. -- 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/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+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 2046657] [NEW] mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits
Public bug reported: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a ** Affects: linux-bluefield (Ubuntu) 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/2046657 Title: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2046657/+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 2064184] [NEW] sdhci_of_dwcmshc: sync up "disable PM runtime in dwcmshc_remove()" from upstream
Public bug reported: SRU Justification: [Impact] It shouldn't affect normal functionalities. With this fix, it'll remove a warning when unloading and loading the sdhci_of_dwcmshc kernel driver. [Fix] The fix unload the runtime PM when unloading the sdhci_of_dwcmshc driver. [Test Case] Normal regression; Unload and load sdhci_of_dwcmshc.ko again. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2064184 Title: sdhci_of_dwcmshc: sync up "disable PM runtime in dwcmshc_remove()" from upstream Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] It shouldn't affect normal functionalities. With this fix, it'll remove a warning when unloading and loading the sdhci_of_dwcmshc kernel driver. [Fix] The fix unload the runtime PM when unloading the sdhci_of_dwcmshc driver. [Test Case] Normal regression; Unload and load sdhci_of_dwcmshc.ko again. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2064184/+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 1999309] [NEW] mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC
Public bug reported: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC. [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. ** Affects: linux-bluefield (Ubuntu) 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/1999309 Title: mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC. [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1999309/+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 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
** 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+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 2002689] Re: mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3 SoC
Tim, Thanks for the code review. I got the Acked-by email but haven't seen it in the jammy repo yet. Do you know when this change might be pushed? -- 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/2002689 Title: mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3 SoC Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: In Progress Bug description: SRU Justification: [Impact] This is a porting commit from https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253. [Fix] * N/A [Test Case] * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from external rshim driver. The rshim MAC address will show up. # cat /dev/rshim0/misc DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log) BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap) BOOT_TIMEOUT 100 (seconds) DROP_MODE 0 (0:normal, 1:drop) SW_RESET 0 (1: reset) DEV_NAME usb-1-1.1 DEV_INFO BlueField-2(Rev 0) OPN_STR MBF2M516A-EEEO BOOT_RESET_SKIP 0 (1: skip) PEER_MAC 00:1a:ca:ff:ff:01 (rw) PXE_ID 0x (rw) VLAN_ID 0 0 (rw) * echo "PEER_MAC xx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC address, which will take effect in next boot. [Regression Potential] * This is a new enhancement and is backward-compatible with previous behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002689/+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 2004645] [NEW] mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
Public bug reported: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. ** Affects: linux-bluefield (Ubuntu) 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+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 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
** Description changed: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] - The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC. + This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. -- 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+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 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
** Description changed: SRU Justification: [Impact] - This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. + This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] - This fix adds the missing device table IDs for acpi + add the missing device table IDs for acpi [Test Case] - Same functionality as on BlueField-1/2. + Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] - Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. + No changes to driver funtionality. -- 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+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 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
Any suggestion how to upgrade the -propose? I followed the instruction but got failure when running "apt update" Fetched 270 kB in 2s (116 kB/s) Reading package lists... Done E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. -- 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+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 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
I searched a little bit and still got errors even with the correct link (I think)... Reading package lists... Done E: The repository 'http://archive.ubuntu.com/ubuntu/dists/jammy-proposed restricted Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+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 2016039] Re: mlxbf-tmfifo: fix potential race
** 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/2016039 Title: mlxbf-tmfifo: fix potential race Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+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 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
** Tags removed: verification-needed-focal ** 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/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors 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] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+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 2016039] Re: mlxbf-tmfifo: fix potential race
** Tags removed: verification-needed-focal ** 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/2016039 Title: mlxbf-tmfifo: fix potential race 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] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+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 2028457] [NEW] tee-supplicant package is too old
Public bug reported: The current tee-supplicant package seems too old. root@localhost:/usr/sbin# ./tee-supplicant --help ERR [10181] TEES:main:717: failed to open "--help" The upstream repo is https://github.com/OP-TEE/optee_client.git In next BF3 release, we would expect OPTEE/RPMB support, which needs a new version of optee_client and CID support in optee_client/tee- supplicant/src/rpmb.c During make, we would need "RPMB_EMU=0" on the make command line to enable real RPMB. Below is an output of the new version. # ./tee-supplicant-new --help Usage: tee-supplicant [options] [] -h, --help: this help -d, --daemonize: run as a daemon (fork and return after child has opened the TEE device or on error) -f, --fs-parent-path: secure fs parent path [/data/tee] -t, --ta-dir: TAs dirname under /lib [optee_armtz] -p, --plugin-path: plugin load path [/usr/lib/tee-supplicant/plugins/] -r, --rpmb-cid: RPMB device identification register (CID) in hexadecimal ** Affects: linux-bluefield (Ubuntu) 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/2028457 Title: tee-supplicant package is too old Status in linux-bluefield package in Ubuntu: New Bug description: The current tee-supplicant package seems too old. root@localhost:/usr/sbin# ./tee-supplicant --help ERR [10181] TEES:main:717: failed to open "--help" The upstream repo is https://github.com/OP-TEE/optee_client.git In next BF3 release, we would expect OPTEE/RPMB support, which needs a new version of optee_client and CID support in optee_client/tee- supplicant/src/rpmb.c During make, we would need "RPMB_EMU=0" on the make command line to enable real RPMB. Below is an output of the new version. # ./tee-supplicant-new --help Usage: tee-supplicant [options] [] -h, --help: this help -d, --daemonize: run as a daemon (fork and return after child has opened the TEE device or on error) -f, --fs-parent-path: secure fs parent path [/data/tee] -t, --ta-dir: TAs dirname under /lib [optee_armtz] -p, --plugin-path: plugin load path [/usr/lib/tee-supplicant/plugins/] -r, --rpmb-cid: RPMB device identification register (CID) in hexadecimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028457/+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 2089455] Re: BF2: Add support for eMMC HW reset
Patch posted: https://lists.ubuntu.com/archives/kernel-team/2024-November/155539.html https://lists.ubuntu.com/archives/kernel-team/2024-November/155540.html https://lists.ubuntu.com/archives/kernel-team/2024-November/155541.html -- 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/2089455 Title: BF2: Add support for eMMC HW reset Status in linux-bluefield package in Ubuntu: New Bug description: This is a cherry-pick of https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2072675 from jammy to focal. SRU Justification: [Impact] This is a cherry-pick fix from upstream to Add support for BF2 eMMC HW reset [Fix] BLueField eMMC RST_N register is implemented as secure, thus the default hw_reset() implementation won't work. This patch provides BlueField specific hw_reset() which send SMC call to ATF to update the same RST_N register. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2089455/+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 2089455] [NEW] BF2: Add support for eMMC HW reset
Public bug reported: This is a cherry-pick of https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2072675 from jammy to focal. SRU Justification: [Impact] This is a cherry-pick fix from upstream to Add support for BF2 eMMC HW reset [Fix] BLueField eMMC RST_N register is implemented as secure, thus the default hw_reset() implementation won't work. This patch provides BlueField specific hw_reset() which send SMC call to ATF to update the same RST_N register. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) 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/2089455 Title: BF2: Add support for eMMC HW reset Status in linux-bluefield package in Ubuntu: New Bug description: This is a cherry-pick of https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2072675 from jammy to focal. SRU Justification: [Impact] This is a cherry-pick fix from upstream to Add support for BF2 eMMC HW reset [Fix] BLueField eMMC RST_N register is implemented as secure, thus the default hw_reset() implementation won't work. This patch provides BlueField specific hw_reset() which send SMC call to ATF to update the same RST_N register. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2089455/+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
