This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2019543
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2019543
Title:
crypto / qat: unable to init GEN4 device
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Target]
Jammy kernel.
[Impact]
The PCI device cannot be initialized.
This has been fixed in linux v5.18 with the below commits:
- a9dc0d966605 ("crypto: qat - add PFVF support to the GEN4 host driver")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a9dc0d966605
- 642a7d49c249 ("crypto: qat - fix access to PFVF interrupt registers for
GEN4")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=642a7d49c249
[Test Case]
Boot a machine with this device.
Before the patches, the following errors are logged:
> EAL: Probe PCI driver: qat (8086:4941) device: 0000:00:08.0 (socket -1)
> qat_pf2vf_exch_msg(): ACK not received from remote
[Regression Potential]
The patches enable new code for this kind of device only.
It is living in linux for more than 1 years.
The potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019543/+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
