This bug is awaiting verification that the linux-mtk/5.15.0-1030.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-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-lowlatency-
hwe-5.19/5.19.0-1017.18~22.04.1 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
This bug is awaiting verification that the linux-
aws-5.19/5.19.0-1019.20~22.04.1 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
This bug is awaiting verification that the linux-azure/5.19.0-1017.18
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1020.24 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
This bug is awaiting verification that the linux-azure/5.4.0-1100.106
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,
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
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
This bug is awaiting verification that the linux/5.19.0-27.28 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
tested kernel linux/5.15.0-53.59 on both jammy and focal
* Create 2 jammy instances
* Add SRIOV interface with vlan tag
* Configure interface with mtu 9000, and errors in dmesg
* Enabled proposed and installing the linux-image-generic package
* reboot both instances
* network with MTU up via
This bug is awaiting verification that the linux/5.15.0-53.59 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 kernel was tested on 2 instances below is my testing transcript
1. Enable proposed on one of the VMs
2. Install linux-image-generic, which installed kernel 5.4.0-132.148
3. Rebooted the node, and was able to set the IP, and ping another VM
4. Set the MTU to 9000, and was still able to ping
This bug is awaiting verification that the linux/5.4.0-132.148 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
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you
** Tags added: focal jammy kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983656
Title:
iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
Status in linux
** Summary changed:
- SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
+ iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance:
20 matches
Mail list logo
