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-
aws-5.15/5.15.0-1046.51~20.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-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36
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-aws/5.15.0-1031.35
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,
This bug is awaiting verification that the linux-azure/5.15.0-1034.41
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,
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
Hi,
We tried to repro issue with kernel 'linux-image-
unsigned-5.15.0-59-generic_5.15.0-59.65_amd64.deb' from -proposed
repository. The issue is not observed.
After link down/up sequence, nvme controllers 4, 68, 69 and 70 reconnect
successfully.
[ 793.550538] nvme nvme4: queue 0: timeout
This bug is awaiting verification that the linux/5.15.0-59.65 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
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target
after link down event if the number of queues have changed post link down.
[Fix]
Following upstream patch set helps address the issue.
1.
nvmet: Expose max queues to
10 matches
Mail list logo