Dell: Enable speaker mute hotkey LED indicator

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 2015972

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.

Hello koba, or anyone else affected,

Accepted alsa-ucm-conf into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.6.3-1ubuntu4.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello koba, or anyone else affected,

Accepted alsa-ucm-conf into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.6.3-1ubuntu1.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello koba, or anyone else affected,

Accepted alsa-ucm-conf into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.6.3-1ubuntu9 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Verified on Jammy, alsa-ucm-conf(1.2.6.3-1ubuntu1.6) and customized kernel(6.1-oem-1009 applied the kernel patch)
~~~
u@u-Dell-G16-7630:~$ sudo apt policy alsa-ucm-conf
[sudo] password for u:
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu1.6
  Candidate: 1.2.6.3-1ubuntu1.6
  Version table:
 *** 1.2.6.3-1ubuntu1.6 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     1.2.6.3-1ubuntu1.5 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     1.2.6.3-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

~~~

Verified on Lunar, alsa-ucm-conf(1.2.6.3-1ubuntu1.9) and customized kernel(6.1-oem-1009 applied the kernel patch)
~~~
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu9
  Candidate: 1.2.6.3-1ubuntu9
  Version table:
 *** 1.2.6.3-1ubuntu9 100
        100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1.2.6.3-1ubuntu8 500
        500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages

~~~

This bug is awaiting verification that the linux-oem-6.1/6.1.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 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!

Verified with 6.1.0-1011.11
~~~
u@u-Dell-G16-7630:~$ sudo apt policy systemd-hwe-hwdb
[sudo] password for u:
systemd-hwe-hwdb:
  Installed: 249.11.3
  Candidate: 249.11.3
  Version table:
 *** 249.11.3 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        100 /var/lib/dpkg/status
u@u-Dell-G16-7630:~$ sudo apt policy alsa-ucm-conf
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu1.6
  Candidate: 1.2.6.3-1ubuntu1.6
  Version table:
 *** 1.2.6.3-1ubuntu1.6 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     1.2.6.3-1ubuntu1.5 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     1.2.6.3-1ubuntu1 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy/main i386 Packages
u@u-Dell-G16-7630:~$ uname -a
Linux u-Dell-G16-7630 6.1.0-1011-oem #11-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 24 14:23:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

~~~

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu9

---------------
alsa-ucm-conf (1.2.6.3-1ubuntu9) lunar; urgency=medium

  * d/p/0006-sof-hda-dsp-Add-speaker-led-support.patch
     - Backport patch to fix speaker mute led (LP: #2015972)

 -- Koba Ko <email address hidden> Wed, 19 Apr 2023 09:50:30 +0800

I see this is verified against the proposed kernel for Jammy. But Lunar and Kinetic look like they have been tested only against locally patched kernels, rather than the Ubuntu archive. I would expect SRU verifications for hardware enablements to be tested exclusively against the Ubuntu archive before releasing them into -updates. What's the plan for Lunar and Kinetic, please?

Also is there any testing being done to ensure that other use cases of alsa-ucm-conf haven't regressed?

@Robie, let me check it,

I SRUed for L/K/J/OEM-6.1 and got ACKed.
https://lists.ubuntu.com/archives/kernel-team/2023-April/138680.html

i verified on machines, one equipped mute-led and another is w/o.
Is there any issues you are facing?

This bug is awaiting verification that the linux/5.15.0-74.81 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/5.19.0-44.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

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 was fixed in the package linux-oem-6.1 - 6.1.0-1012.12

---------------
linux-oem-6.1 (6.1.0-1012.12) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1012.12 -proposed tracker (LP: #2018993)

  * A deadlock issue in scsi rescan task while resuming from S3 (LP: #2018566)
    - SAUCE: PM: suspend: Define pm_suspend_target_state
    - SAUCE: ata: libata: Defer rescan on suspended device

  * Miscellaneous Ubuntu changes
    - [Packaging] actually enforce set -e in dkms-build--nvidia-N
    - [Packaging] Preserve the correct log file variable value

 -- Timo Aaltonen <email address hidden> Tue, 09 May 2023 15:46:57 +0300

Hi @kobako

> I SRUed for L/K/J/OEM-6.1 and got ACKed.
> https://lists.ubuntu.com/archives/kernel-team/2023-April/138680.html
>
> i verified on machines, one equipped mute-led and another is w/o.
> Is there any issues you are facing?

I see you tested alsa-ucm-conf with an oem-specific kernel, but what about the normal non-oem kernel that exists in jammy, kinetic, and lunar? Does this alsa-ucm-conf change have any effect on those non-oem kernels? We ask because alsa-ucm-conf will be delivered to all ubuntu users, and not just those who are on dell machines with the oem kernel.

the target kernels is in jammy/lunar proposed now and verified them.

@Andreas,
I'm waiting for l and k proposed kernel.

Sorry, I'm just not clear on what has been tested.

Please could you detail precisely what version of what package has been tested against what version of what kernel?

[Test cases]
1. machine w/ speaker mute led, led should be controlled and speaker mute must work fine.
2. machine w/o speaker mute led, speaker mute must work well.

@Lunar, verified against kernel 6.2.0-23.23 and alsa-ucm-conf(1.2.6.3-1ubuntu9)
$ uname -a
Linux 6.2.0-23-generic #23-Ubuntu SMP PREEMPT_DYNAMIC Wed May 17 16:55:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt policy alsa-ucm-conf
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu9
  Candidate: 1.2.6.3-1ubuntu9
  Version table:
 *** 1.2.6.3-1ubuntu9 100
        100 http://tw.archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1.2.6.3-1ubuntu8 500
        500 http://tw.archive.ubuntu.com/ubuntu lunar/main amd64 Packages

@Kinetic, verified against kernel 5.19.0-44.45 and alsa-ucm-conf(1.2.6.3-1ubuntu4.3)
$ uname -a
Linux 5.19.0-44-generic #45-Ubuntu SMP PREEMPT_DYNAMIC Tue May 16 11:35:01 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt policy alsa-ucm-conf
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu4.3
  Candidate: 1.2.6.3-1ubuntu4.3
  Version table:
 *** 1.2.6.3-1ubuntu4.3 500
        500 http://tw.archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu kinetic-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     1.2.6.3-1ubuntu4.2 500
        500 http://tw.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu kinetic-updates/main i386 Packages
     1.2.6.3-1ubuntu2 500
        500 http://tw.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu kinetic/main i386 Packages

@Jammy, verified against 5.15.0-74.81 and alsa-ucm-conf(1.2.6.3-1ubuntu1.6)
~~~
# uname -a
Linux 5.15.0-74-generic #81-Ubuntu SMP Fri May 12 15:05:17 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
# sudo apt policy alsa-ucm-conf
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu1.6
  Candidate: 1.2.6.3-1ubuntu1.6
  Version table:
 *** 1.2.6.3-1ubuntu1.6 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     1.2.6.3-1ubuntu1.5 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
     1.2.6.3-1ubuntu1 500
        500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://tw.archive.ubuntu.com/ubuntu jammy/main i386 Packages
~~~

Thank you, so we have verification on the oem kernels, and the proposed kernels, for jammy, kinetic, and lunar.

Did you try alsa-ucm-conf with the currently released kernels for those ubuntu releases? I wouldn't expect the LED to work, if it requires a newer kernel, but just to check if nothing breaks with the currently released kernels and this new alsa-ucm-conf package.

Yes, I tried alsa-ucm-conf on kernels w/ w/o patches.

On Thu, May 25, 2023, 9:46 PM Andreas Hasenack <email address hidden>
wrote:

> Thank you, so we have verification on the oem kernels, and the proposed
> kernels, for jammy, kinetic, and lunar.
>
> Did you try alsa-ucm-conf with the currently released kernels for those
> ubuntu releases? I wouldn't expect the LED to work, if it requires a
> newer kernel, but just to check if nothing breaks with the currently
> released kernels and this new alsa-ucm-conf package.
>
> --
> You received this bug notification because you are a member of Canonical
> Hardware Enablement, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/2015972
>
> Title:
> Dell: Enable speaker mute hotkey LED indicator
>
> Status in HWE Next:
> New
> Status in OEM Priority Project:
> New
> Status in alsa-ucm-conf package in Ubuntu:
> Fix Released
> Status in linux package in Ubuntu:
> In Progress
> Status in linux-oem-6.1 package in Ubuntu:
> Invalid
> Status in alsa-ucm-conf source package in Jammy:
> Fix Committed
> Status in linux source package in Jammy:
> Fix Committed
> Status in linux-oem-6.1 source package in Jammy:
> Fix Released
> Status in alsa-ucm-conf source package in Kinetic:
> Fix Committed
> Status in linux source package in Kinetic:
> Fix Committed
> Status in linux-oem-6.1 source package in Kinetic:
> Invalid
> Status in alsa-ucm-conf source package in Lunar:
> Fix Committed
> Status in linux source package in Lunar:
> Fix Committed
> Status in linux-oem-6.1 source package in Lunar:
> Invalid
>
> Bug description:
> [Feature Description]
> When users press the speaker mute hotkey and the speaker is muted,
> the speaker mute LED indicator will light up.
> When the speaker is not muted,
> the speaker mute LED indicator will light out.
>
> [Test Case]
> 1. run G16 with target kernel.
> 2. press the mute hotkey
> 3. check if speaker mute led can be switched.
>
> [Where problems could occur]
> Low, just register a speaker mute led control for dell-laptop.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions
>
>

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu9

---------------
alsa-ucm-conf (1.2.6.3-1ubuntu9) lunar; urgency=medium

  * d/p/0006-sof-hda-dsp-Add-speaker-led-support.patch
     - Backport patch to fix speaker mute led (LP: #2015972)

 -- Koba Ko <email address hidden> Wed, 19 Apr 2023 09:50:30 +0800

The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu4.3

---------------
alsa-ucm-conf (1.2.6.3-1ubuntu4.3) kinetic; urgency=medium

  * d/p/0006-sof-hda-dsp-Add-speaker-led-support.patch
     - Backport patch to fix speaker mute led (LP: #2015972)

 -- Koba Ko <email address hidden> Wed, 19 Apr 2023 09:40:32 +0800

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.6

---------------
alsa-ucm-conf (1.2.6.3-1ubuntu1.6) jammy; urgency=medium

  * d/p/0006-sof-hda-dsp-Add-speaker-led-support.patch
     - Backport patch to fix speaker mute led (LP: #2015972)

 -- Koba Ko <email address hidden> Wed, 19 Apr 2023 09:14:07 +0800

This bug is awaiting verification that the linux-nvidia-5.19/5.19.0-1014.14 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-hwe-6.2/6.2.0-23.23~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 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-nvidia-6.2/6.2.0-1003.3~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 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-1033.38~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 was fixed in the package linux - 5.15.0-75.82

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

  * jammy/linux: 5.15.0-75.82 -proposed tracker (LP: #2023065)

  * Jammy update: v5.15.102 upstream stable release (LP: #2020393)
    - wifi: cfg80211: Partial revert "wifi: cfg80211: Fix use after free for wext"

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync getabis

  * fix typo in config-checks invocation (LP: #2020413)
    - [Packaging] fix typo when calling the old config-check
    - [Packaging] fix typo in 4-checks.mk

  * support python < 3.9 with annotations (LP: #2020531)
    - [Packaging] kconfig/annotations.py: support older way of merging dicts

linux (5.15.0-74.81) jammy; urgency=medium

  * jammy/linux: 5.15.0-74.81 -proposed tracker (LP: #2019420)

  * smartpqi: Update 22.04 driver to include recent bug fixes and support
    current generation devices (LP: #1998643)
    - scsi: smartpqi: Switch to attribute groups
    - scsi: smartpqi: Fix rmmod stack trace
    - scsi: smartpqi: Add PCI IDs
    - scsi: smartpqi: Enable SATA NCQ priority in sysfs
    - scsi: smartpqi: Eliminate drive spin down on warm boot
    - scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
    - scsi: smartpqi: Fix a name typo and cleanup code
    - scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
    - scsi: smartpqi: Resolve delay issue with PQI_HZ value
    - scsi: smartpqi: Avoid drive spin-down during suspend
    - scsi: smartpqi: Update volume size after expansion
    - scsi: smartpqi: Speed up RAID 10 sequential reads
    - scsi: smartpqi: Expose SAS address for SATA drives
    - scsi: smartpqi: Fix NUMA node not updated during init
    - scsi: smartpqi: Fix BUILD_BUG_ON() statements
    - scsi: smartpqi: Fix hibernate and suspend
    - scsi: smartpqi: Fix lsscsi -t SAS addresses
    - scsi: smartpqi: Update version to 2.1.14-035
    - scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
    - scsi: smartpqi: Stop using the SCSI pointer
    - scsi: smartpqi: Fix typo in comment
    - scsi: smartpqi: Shorten drive visibility after removal
    - scsi: smartpqi: Add controller fw version to console log
    - scsi: smartpqi: Add PCI IDs for ramaxel controllers
    - scsi: smartpqi: Close write read holes
    - scsi: smartpqi: Add driver support for multi-LUN devices
    - scsi: smartpqi: Fix PCI control linkdown system hang
    - scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
    - scsi: smartpqi: Add PCI IDs for Lenovo controllers
    - scsi: smartpqi: Stop logging spurious PQI reset failures
    - scsi: smartpqi: Fix RAID map race condition
    - scsi: smartpqi: Add module param to disable managed ints
    - scsi: smartpqi: Update deleting a LUN via sysfs
    - scsi: smartpqi: Add ctrl ready timeout module parameter
    - scsi: smartpqi: Update copyright to current year
    - scsi: smartpqi: Update version to 2.1.18-045
    - scsi: smartpqi: Convert to host_tagset
    - scsi: smartpqi: Add new controller PCI IDs
    - scsi: smartpqi: Correct max LUN number
    - scsi: smartpqi: Change sysfs raid_level attribute to N/A for controllers
    - scsi: smar...

This bug was fixed in the package linux - 5.19.0-45.46

---------------
linux (5.19.0-45.46) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-45.46 -proposed tracker (LP: #2023057)

  * Kinetic update: upstream stable patchset 2023-05-23 (LP: #2020599)
    - wifi: cfg80211: Partial revert "wifi: cfg80211: Fix use after free for wext"

linux (5.19.0-44.45) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-44.45 -proposed tracker (LP: #2019827)

  * Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
    (LP: #2018470)
    - drm/amdgpu: Fix for BO move issue

  * CVE-2023-32233
    - netfilter: nf_tables: deactivate anonymous set from preparation phase

  * CVE-2023-2612
    - SAUCE: shiftfs: prevent lock unbalance in shiftfs_create_object()

  * CVE-2023-31436
    - net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg

  * CVE-2023-1380
    - wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies()

  * conntrack mark is not advertised via netlink (LP: #2016269)
    - netfilter: ctnetlink: revert to dumping mark regardless of event type

  * 5.19 not reporting cgroups v1 blkio.throttle.io_serviced (LP: #2016186)
    - SAUCE: blk-throttle: Fix io statistics for cgroup v1

  * [SRU] Backport request for hpwdt from upstream 6.1 to Jammy (LP: #2008751)
    - watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems.
    - watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING
    - [Config] Add arm64 option to CONFIG_HP_WATCHDOG

  * vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
    (LP: #2007001)
    - SAUCE: Revert "video/aperture: Disable and unregister sysfb devices via
      aperture helpers"

  * Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)
    (LP: #2012335)
    - ice: Allow operation with reduced device MSI-X

  * Dell: Enable speaker mute hotkey LED indicator (LP: #2015972)
    - platform/x86: dell-laptop: Register ctl-led for speaker-mute

  * [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is
    taking longer than expected (LP: #2008527)
    - cpufreq: ACPI: Defer setting boost MSRs

  * [SRU][Jammy] CONFIG_PCI_MESON is not enabled (LP: #2007745)
    - [Config] arm64: Enable PCI_MESON module

  * Kinetic update: upstream stable patchset 2023-05-08 (LP: #2018948)
    - HID: asus: use spinlock to protect concurrent accesses
    - HID: asus: use spinlock to safely schedule workers
    - powerpc/mm: Rearrange if-else block to avoid clang warning
    - ARM: OMAP2+: Fix memory leak in realtime_counter_init()
    - arm64: dts: qcom: qcs404: use symbol names for PCIe resets
    - arm64: dts: qcom: msm8996-tone: Fix USB taking 6 minutes to wake up
    - arm64: dts: qcom: sm8150-kumano: Panel framebuffer is 2.5k instead of 4k
    - arm64: dts: qcom: sm6125: Reorder HSUSB PHY clocks to match bindings
    - arm64: dts: imx8m: Align SoC unique ID node unit address
    - ARM: zynq: Fix refcount leak in zynq_early_slcr_init
    - arm64: dts: mediatek: mt8183: Fix systimer 13 MHz clock description
    - arm64: dts: qcom: sdm845-db845c: fix audio codec interrupt pin name
    - arm64: dts: qcom: sc7180: correct SPMI bus addres...

This bug was fixed in the package linux - 6.2.0-23.23

---------------
linux (6.2.0-23.23) lunar; urgency=medium

  * lunar/linux: 6.2.0-23.23 -proposed tracker (LP: #2019845)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/2023.05.15)

  * Fix flicker display problem on some panels which support PSR2 (LP: #2002968)
    - drm/i915/psr: Add continuous full frame bit together with single

  * Kernel 6.1 bumped the disk consumption on default images by 15%
    (LP: #2015867)
    - [Packaging] introduce a separate linux-lib-rust package

  * Update I915 PSR calculation on Linux 6.2 (LP: #2018655)
    - drm/i915: Fix fast wake AUX sync len
    - drm/i915: Explain the magic numbers for AUX SYNC/precharge length

  * Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
    (LP: #2017444)
    - [Config]: Disable CONFIG_INTEL_ATOMISP

  * udev fails to make prctl() syscall with apparmor=0 (as used by maas by
    default) (LP: #2016908)
    - SAUCE: (no-up) Stacking v38: Fix prctl() syscall with apparmor=0

  * CVE-2023-32233
    - netfilter: nf_tables: deactivate anonymous set from preparation phase

  * CVE-2023-2612
    - SAUCE: shiftfs: prevent lock unbalance in shiftfs_create_object()

  * CVE-2023-31436
    - net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg

  * CVE-2023-1380
    - wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies()

  * 5.19 not reporting cgroups v1 blkio.throttle.io_serviced (LP: #2016186)
    - SAUCE: blk-throttle: Fix io statistics for cgroup v1

  * LSM stacking and AppArmor for 6.2: additional fixes (LP: #2017903)
    - SAUCE: (no-up) apparmor: fix policy_compat perms remap for file dfa
    - SAUCE: (no-up) apparmor: fix profile verification and enable it
    - SAUCE: (no-up) apparmor: fix: add missing failure check in
      compute_xmatch_perms
    - SAUCE: (no-up) apparmor: fix: kzalloc perms tables for shared dfas

  * Lunar update: v6.2.12 upstream stable release (LP: #2017219)
    - Revert "pinctrl: amd: Disable and mask interrupts on resume"
    - drm/amd/display: Pass the right info to drm_dp_remove_payload
    - drm/i915: Workaround ICL CSC_MODE sticky arming
    - ALSA: emu10k1: fix capture interrupt handler unlinking
    - ALSA: hda/sigmatel: add pin overrides for Intel DP45SG motherboard
    - ALSA: i2c/cs8427: fix iec958 mixer control deactivation
    - ALSA: hda: patch_realtek: add quirk for Asus N7601ZM
    - ALSA: hda/realtek: Add quirks for Lenovo Z13/Z16 Gen2
    - ALSA: firewire-tascam: add missing unwind goto in
      snd_tscm_stream_start_duplex()
    - ALSA: emu10k1: don't create old pass-through playback device on Audigy
    - ALSA: hda/sigmatel: fix S/PDIF out on Intel D*45* motherboards
    - ALSA: hda/hdmi: disable KAE for Intel DG2
    - Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}
    - Bluetooth: Fix race condition in hidp_session_thread
    - bluetooth: btbcm: Fix logic error in forming the board name.
    - Bluetooth: Free potentially unfreed SCO connection
    - Bluetooth: hci_conn: Fix possible UAF
    - btrfs: restore the thread_pool=...

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1015.15 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-nvidia-tegra-igx/5.15.0-1001.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 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-1043.50 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/6.2.0-1009.9 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'.

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-1041.46 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-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!