This bug was fixed in the package linux-intel-iotg - 5.15.0-1030.35
---
linux-intel-iotg (5.15.0-1030.35) jammy; urgency=medium
* jammy/linux-intel-iotg: 5.15.0-1030.35 -proposed tracker (LP:
#2019028)
* net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable
intel helped to verify the kernel 5.15.0-1030.35
** 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-intel-iotg in Ubuntu.
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1029.34 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
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2012755
Title:
[IOTG][RPL] Enable
** Description changed:
Description
Time Coordinated Compute (TCC)
Pseudo SRAM interface support on top of Cache Allocation Technology
Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake & Raptor
Lake
Target Release: 22.04
Target Kernel: TBD
External links:
Rebased the changes on top of the latest iotg kernel and these are the
changes now required:
0005-tcc-driver-should-exit-if-no-psram-entry-found-in-PTCT.tcc
0006-tcc-tcc-drvier-should-not-exit-even-if-no-psram-entry.tcc
0013-Add-new-IOCTL-to-read-error-log-buffer.tcc
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-intel-iotg
7 matches
Mail list logo
