This bug was fixed in the package linux-nvidia-6.5 - 6.5.0-1013.13
---------------
linux-nvidia-6.5 (6.5.0-1013.13) jammy; urgency=medium
* jammy/linux-nvidia-6.5: 6.5.0-1013.13 -proposed tracker (LP:
#2053169)
* Fix soft lockup triggered by arm_smmu_mm_invalidate_range (LP: #2048966)
- Revert "iommu/arm-smmu-v3: Fix soft lockup triggered by
arm_smmu_mm_invalidate_range"
- iommu/arm-smmu-v3: Fix soft lockup triggered by
arm_smmu_mm_invalidate_range
* Pull request: address GPIO initialization regression on Grace systems
(LP: #2053148)
- NVIDIA: SAUCE: Revert "gpio: tegra186: Check GPIO pin permission before
access."
-- Ian May <ian....@canonical.com> Thu, 15 Feb 2024 15:54:25 -0600
** Changed in: linux-nvidia-6.5 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048815
Title:
Pull request to address TPM SPI devices
Status in linux-nvidia-6.5 package in Ubuntu:
Fix Released
Bug description:
TPM devices may insert wait state on last clock cycle of ADDR phase.
For SPI controllers that support full-duplex transfers, this can be
detected using software by reading the MISO line. For SPI controllers
that only support half-duplex transfers, such as the Tegra QSPI, it is
not possible to detect the wait signal from software.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2048815/+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
