[SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support

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 1971151

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.

Please ignore the commit ids provided in the last comment.
Below patches/commit ids are sitting in Linux SCSI repo:
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/ (branch 5.19/scsi-staging)

f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0
7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough
986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs
43ca11005098 scsi: mpi3mr: Add support for PEL commands
506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands
f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header
f5e6d5a34376 scsi: mpi3mr: Add support for driver commands
4268fa751365 scsi: mpi3mr: Add bsg device support

Soon these patches will be pushed to Linux mainline when Linus pulls subsystem(scsi) staging patches.

Hi Sumit,

All of the patches in comment #2 cherry-pick cleanly. I noticed that the following patch is in the description but missing from comment #2:

ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h

Is this patch still needed? I see that it has been applied to 5.19/scsi-staging
(https://www.spinics.net/lists/linux-scsi/msg172765.html). I am having trouble locating it when I try to cherry-pick it. Has anything changed about this patch? commit ID, etc?

Below patch is not needed-

ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h

Please ignore the commit ids posted in initial bug description as they are superseded by new set of patches.

Below are the final commit ids to be picked:

f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0
7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough
986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs
43ca11005098 scsi: mpi3mr: Add support for PEL commands
506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands
f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header
f5e6d5a34376 scsi: mpi3mr: Add support for driver commands
4268fa751365 scsi: mpi3mr: Add bsg device support

Please let me know if you have any questions.

Hi,

Can you please post the test kernel link which should contain below commits:

f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0
7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough
986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs
43ca11005098 scsi: mpi3mr: Add support for PEL commands
506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands
f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header
f5e6d5a34376 scsi: mpi3mr: Add support for driver commands
4268fa751365 scsi: mpi3mr: Add bsg device support

Thanks,
Sumit

Please pick below additional commits also:

1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc
4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings
9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes
e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes
bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails
a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init()
256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR
2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset
1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s

I applied all of the patches as they did cherry pick cleanly. I had to make the following changes to get it to build:

On line 4007 I made this change:
drivers/scsi/mpi3mr/mpi3mr_os.c
- scsi_done(scmd);
+ scmd->scsi_done(scmd);

On line 4149 I made this change
drivers/scsi/mpi3mr/mpi3mr_os.c:4149
- .shost_groups = mpi3mr_host_groups,

Can you check into why these changes were needed to build the kernel? I need the patches that will build the kernel without any intervention from me after the clean cherry pick.

Hi Sumit,

Any updates on my question from comment #7 ?

Build failure as decsribed in comment#7 is due to below patch:

1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly

Revert/drop this patch from the list of commit IDs provided.
It was a cleanup/optimization done in recent kernels(beyond 5.15) and
necessary code is missing in Ubuntu 22.04(5.15) kernel.
It’s not functional so safe to drop.

Thanks,
Sumit

Hi Michael,

Any updates on the test kernel with BSG patches included ?

Thanks,
Sumit

Hi Sumit,

That addresses the first error but I do not see where this patch removes the second error where I had to remove line 4149

On line 4149 I made this change
drivers/scsi/mpi3mr/mpi3mr_os.c:4149
- .shost_groups = mpi3mr_host_groups,

Hi Michael,

This compilation failure is due to OS APIs/interface difference between 5.15(Ubuntu 22.04.1) kernel and the latest upstream kernel. I have attached the patch which would make the driver code compile-able on 5.15 kernel. Please check and let me know if you still face any issue.

Thanks,
Sumit

Hi Michael,

Are you able to compile the driver ?

Thanks,
Sumit

Hi Michael,

Any updates on it ?

Thanks,
Sumit

Hi Michael,

Gentle reminder!
Do we have any update ?

Thanks,
Sumit

Hi Sumit,

I do not think the patch from comment #9 is the issue. That is not among the patches I applied as far as I can tell. I applied the patches from comments #5 and comment #6. The issue is with the following 2 patches:

This patch introduces the issue with scsi_done(scmd) where it should be scmd->scsi_done(scmd);

256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR
https://www.spinics.net/lists/linux-scsi/msg173118.html

The second patch adds this line .shost_groups = mpi3mr_host_groups,

986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs
https://patchwork.kernel.org<email address hidden>/

@Sumit - Any update on the above query?

Hi Michael,

Could you please help with the test kernel ?

Thanks,
Sumit

Hi Michael,

Any update on the test kernel ?

Thanks,
Sumit

Michael, Gentle reminder !

Hi Sumit,

Referencing comment #9 this patch is not the issue

1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly

The patch that is causing an issue is

256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with

Otherwise I could build the test kernel very quickly.

Michael,

Problem is- the patch- "256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR" is calling "scmd_done(scmd)" directly whereas Ubuntu kernel expects "scmd->scsi_done(scmd)".

So the patch causing issue has to be adjusted for Ubuntu kernel as below [scmd_done(scmd) replaced with scmd->scsi_done(scmd)]:

-------
 drivers/scsi/mpi3mr/mpi3mr_os.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/scsi/mpi3mr/mpi3mr_os.c b/drivers/scsi/mpi3mr/mpi3mr_os.c
index 89a4918..5c57519 100644
--- a/drivers/scsi/mpi3mr/mpi3mr_os.c
+++ b/drivers/scsi/mpi3mr/mpi3mr_os.c
@@ -3996,6 +3996,12 @@ static int mpi3mr_qcmd(struct Scsi_Host *shost,
  int iprio_class;
  u8 is_pcie_dev = 0;

+ if (mrioc->unrecoverable) {
+ scmd->result = DID_ERROR << 16;
+ scmd->scsi_done(scmd);
+ goto out;
+ }
+
  sdev_priv_data = scmd->device->hostdata;
  if (!sdev_priv_data || !sdev_priv_data->tgt_priv_data) {
   scmd->result = DID_NO_CONNECT << 16;
------

Please let me know if it works for you.

Hi Sumit,

I have created a test kernel.

https://people.canonical.com/~mreed/dell/lp_1971151_bsg_support/

Hi Michael,

Provided test kernel does not have BSG code. BSG enabled management application does not work with this driver. Could you please re-check and if possible share the driver source code ?

Thanks,
Sumit

Hi Sumit

Here is the source.

https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support

Is the code not there? or is there a config variable I need to enable?

Source has the BSG code: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support

Driver version is :8.0.0.69.0
Ref: https://git.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/tree/drivers/scsi/mpi3mr/mpi3mr.h?h=mpi3mr_bsg_support

But the test kernel shared through the link: https://people.canonical.com/~mreed/dell/lp_1971151_bsg_support/ does not have BSG code and the driver version is 8.0.0.68.0. Below is the modinfo output of this driver:

version: 8.0.0.68.0
license: GPL
description: MPI3 Storage Controller Device Driver
author: Broadcom Inc. <email address hidden>
srcversion: 4892EF29E9979CF10BBDFCC
alias: pci:v00001000d000000A5sv*sd*bc*sc*i*
depends:
retpoline: Y
intree: Y
name: mpi3mr
vermagic: 5.15.0-47-generic SMP mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 15:95:69:55:43:26:3C:20:A6:14:88:F3:D0:65:0A:3F:4A:53:7C:35
sig_hashalgo: sha512
signature: 46:6F:DB:C6:11:DA:78:AA:DC:78:F9:6C:A7:53:46:A9:26:C9:C3:44:
  DE:FE:62:7D:7C:21:4A:AD:5B:53:DE:AE:79:E1:D1:67:6D:E5:79:23:
  12:E1:DB:A7:AB:B5:85:74:DF:AD:77:23:9A:09:B9:8D:E4:07:A4:CB:
  24:13:7E:29:9F:64:90:C9:AC:E4:16:E8:50:C7:2A:65:68:1F:CA:85:
  06:9F:C5:A3:47:BD:86:F2:E0:05:92:B5:69:C7:5A:13:25:4E:64:88:
  D2:A9:60:23:89:0B:47:74:47:2E:C0:49:09:B2:58:CF:DF:81:C9:25:
  56:74:BB:C2:51:95:B7:13:C6:4A:B7:CA:93:42:D6:4D:3E:16:95:98:
  29:65:6E:46:98:23:DF:24:A3:77:B6:B9:3E:17:D9:BB:57:8F:DE:62:
  42:73:CD:B1:D1:2C:C1:8B:69:E8:B4:F7:A6:44:50:8D:2B:A9:CC:8A:
  94:D0:39:A8:A0:8E:C4:F7:16:A7:0E:E6:87:9F:DA:AE:08:65:4E:61:
  71:91:8D:BF:73:8D:74:5C:B7:C6:6A:1A:7D:D9:45:3E:D2:E9:04:63:
  44:AE:7C:F2:92:5E:3B:25:05:CD:5E:A5:48:70:D6:3A:9F:70:2F:A6:
  DA:78:2A:C9:EA:02:44:42:81:C6:F0:CB:7E:90:50:35:05:94:54:05:
  68:07:F7:D6:31:DF:BF:D0:7D:72:21:10:1E:80:23:7A:1C:DC:38:AC:
  AA:25:9C:11:1B:36:82:30:23:C7:AC:C7:34:70:FF:86:44:BF:53:6A:
  01:7F:7F:7A:73:6B:64:5A:6A:F1:1B:20:23:DC:DB:F5:F9:A5:0E:18:
  AD:47:BA:D9:88:AB:44:78:A8:EF:23:84:CB:78:9E:88:80:39:B5:83:
  06:22:E2:1B:3F:2D:E5:22:25:DE:68:17:0B:F4:6D:FB:73:DA:9C:53:
  27:CC:81:E4:85:1B:E6:E0:32:FE:11:63:6C:15:4F:5D:FD:F2:BA:C0:
  2C:20:8C:56:1F:C2:10:12:C1:B0:A1:A0:CC:F8:D8:04:2E:1A:8F:E0:
  57:6A:CB:3C:CB:A3:9A:D9:12:51:D6:AC:C8:89:E9:75:D1:71:9F:07:
  1B:25:B5:0E:2D:FC:F8:B0:75:12:BC:84:30:C1:4E:81:3D:D7:13:CD:
  80:8B:1B:48:20:77:6A:B0:44:88:EC:76:51:1B:F7:49:81:82:C8:5C:
  17:9E:8D:A0:B5:F0:BC:31:22:E5:6E:E1:5E:40:AD:D2:33:74:14:61:
  50:E0:E8:B9:2F:7D:D1:38:29:F4:0E:EB:B7:84:B6:77:AB:B4:B5:93:
  B6:AE:9B:D5:D8:FE:04:4A:7F:E5:A7:0D
parm: poll_queues:Number of queues for io_uring poll mode. (Range 1 - 126) (int)
parm: prot_mask:Host protection capabilities mask, def=0x07 (int)
parm: prot_guard_mask: Host protection guard mask, def=3 (int)
parm: logging_level: bits for enabling additional logging info (default=0) (int)

Hi Michael,

Friendly reminder !

Thanks,
Sumit

Hi Sumit

I did link an older version of the source but the debs were built from the correct source below:

https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support

It is inconsequential because the patch that updates the version is included in the debs and in both source versions.

 git --no-pager log | grep -B 10 -i "Update driver version to 8.0.0.69.0"
    Link: https://<email address hidden>
    Signed-off-by: Sreekanth Reddy <email address hidden>
    Signed-off-by: Martin K. Petersen <email address hidden>
    (cherry picked from commit 1aa529d400253eda76733dbb95b62f6cca7b274a)
    Signed-off-by: Michael Reed <email address hidden>

commit 3511175b43b74a055ff26a95ba4dbf66f6b068b3
Author: Sumit Saxena <email address hidden>
Date: Fri Apr 29 17:16:41 2022 -0400

    scsi: mpi3mr: Update driver version to 8.0.0.69.0
^C
ubuntu@toadsworth:~/code_bsg/latest_08/jammy$ git --no-pager log | grep -A 10 -i "Update driver version to 8.0.0.69.0"
    scsi: mpi3mr: Update driver version to 8.0.0.69.0

    BugLink: https://bugs.launchpad.net/bugs/1971151

    Link: https://<email address hidden>
    Signed-off-by: Sumit Saxena <email address hidden>
    Signed-off-by: Martin K. Petersen <email address hidden>
    (cherry picked from commit f304d35e59958ea4be399f78e5be08d4a0c4db75)
    Signed-off-by: Michael Reed <email address hidden>

I think I do know what happened as to why the latest version of the driver did not load. I suspect that the kernel I built is older than the current version of the kernel that is deployed in new installs of Jammy. If this is the case it may not properly install or become the default kernel to boot when it is installed. The way to fix this is to modify grub so you can properly install and then select the older kernel.

Steps
1. Modify /etc/default/grub.d/50-curtin-settings.cfg and change GRUB_DISABLE_OS_PROBER="true" to false.

2. Modify /etc/default/grub and change GRUB_TIMEOUT_STYLE=hidden to menu and GRUB_TIMEOUT=0 to 1.

3. Sudo grub-update2

4. Reinstall the kernel debs. sudo dpkg -i (this should also re-run update-grub2)

5. Reboot and from console select the correct kernel 5.15.0-47-generic #53

6. This is not the ideal way to do this, and in the future I will rename the built kernel in such a way that will prevent this from happening, however it should work fine for testing purposes. If you have any issues let me know.

we are able to install and test the kernel provided here https://people.canonical.com/~mreed/dell/lp_1971151_bsg_support/

and executed boot and IO test cases successfully.

This bug is awaiting verification that the linux/5.15.0-70.77 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 tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Tested against H965i, resolved my problem.

This bug was fixed in the package linux - 5.15.0-70.77

---------------
linux (5.15.0-70.77) jammy; urgency=medium

  * jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)

  * CVE-2023-26545
    - net: mpls: fix stale pointer if allocation fails during device rename

  * CVE-2023-1281
    - net/sched: tcindex: update imperfect hash filters respecting rcu

  * [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG)
    support (LP: #1971151)
    - scsi: mpi3mr: Add bsg device support
    - scsi: mpi3mr: Add support for driver commands
    - scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi
      header
    - scsi: mpi3mr: Add support for MPT commands
    - scsi: mpi3mr: Add support for PEL commands
    - scsi: mpi3mr: Expose adapter state to sysfs
    - scsi: mpi3mr: Add support for NVMe passthrough
    - scsi: mpi3mr: Update driver version to 8.0.0.69.0
    - scsi: mpi3mr: Increase I/O timeout value to 60s
    - scsi: mpi3mr: Hidden drives not removed during soft reset
    - scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR
    - scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init()
    - scsi: mpi3mr: Return error if dma_alloc_coherent() fails
    - scsi: mpi3mr: Add shost related sysfs attributes
    - scsi: mpi3mr: Add target device related sysfs attributes
    - scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings
    - scsi: mpi3mr: Fix kernel-doc

  * cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids
    (LP: #2008519)
    - cpufreq: intel_pstate: Update EPP for AlderLake mobile
    - cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire Rapids

  * Fail to output sound to external monitor which connects via docking station
    (LP: #2009024)
    - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM

  * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118)
    - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read

  * Jammy update: v5.15.92 upstream stable release (LP: #2011472)
    - ARM: dts: imx: Fix pca9547 i2c-mux node name
    - ARM: dts: vf610: Fix pca9548 i2c-mux node names
    - arm64: dts: freescale: Fix pca954x i2c-mux node names
    - arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI
    - firmware: arm_scmi: Clear stale xfer->hdr.status
    - bpf: Skip task with pid=1 in send_signal_common()
    - erofs/zmap.c: Fix incorrect offset calculation
    - blk-cgroup: fix missing pd_online_fn() while activating policy
    - HID: playstation: sanity check DualSense calibration data.
    - dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init
    - cifs: fix return of uninitialized rc in dfs_cache_update_tgthint()
    - extcon: usbc-tusb320: fix kernel-doc warning
    - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt
    - tools: fix ARRAY_SIZE defines in tools and selftests hdrs
    - selftests/vm: remove ARRAY_SIZE define from individual tests
    - selftests: Provide local define of __cpuid_count()
    - net: fix NULL pointer in skb_segment_list
    - net: mctp: purge receive queues on sk destruction
    - Linux 5.15.92

  * Jammy update: v5.15....

This bug is awaiting verification that the linux-hwe-5.15/5.15.0-71.78~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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-aws/5.15.0-1036.40 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 tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-azure/5.15.0-1038.45 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 tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-intel-iotg-5.15/5.15.0-1029.34~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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1021.25 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 tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

it's not the requirement for focal/intel-iotg kernel

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 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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 problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!