[Kernel-packages] [Bug 2060984] Re: FFe: New firmware release

[Łukasz Zemczak]

Does this upload fix any release-critical bugs? Since if not, I would
prefer to defer this for post-release. We are already in a critical
enough state as is.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2060984

Title:
  FFe: New firmware release

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  A new upstream release of linux-firmware was tagged on 2024.04.10,
  this would sync us with that. Changes:

   - imx: sdma: update firmware to v3.6/v4.6
   - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
   - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
   - Montage: update firmware for Mont-TSSE
   - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
   - rtw88: Add RTL8703B firmware v11.0.0
   - rtw89: 8922a: add firmware v0.35.18.0
   - rtw89: 8852c: update fw to v0.27.56.14
   - mekdiatek: Update mt8186 SOF firmware to v2.0.1
   - linux-firmware: update firmware for en8811h 2.5G ethernet phy
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - i915: Add DG2 HuC 7.10.15
   - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
   - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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

[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops

[Łukasz Zemczak]

Hello Chris, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.7 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.

** Tags removed: verification-failed-jammy
** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569

Title:
  Enable the mic-mute led on Dell MTL laptops

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]
  On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is 
working but the LED(on F4) state is not changed accordingly.

  [Fix]
  There's no problem on the same series on RPL platform. It needs MTL specific 
SoF driver and controls to support the registered mixer switch. It requires the 
patches in 
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
 and 
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only required for new sof-audio-pci-intel-mtl driver. The impact should 
be restricting.

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Intel MTL powered laptops.

  [Fix]
  For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add 
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the 
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control 
matches with the updated driver.

  [Test Case]
  1. enable -proposed pocket and install firmware-sof-signed
  2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.

  [Where problems could occur]
  The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all 
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+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

[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops

[Łukasz Zemczak]

Accepted into -proposed, but as part of firmware-sof verification,
please also verify audio function on MTL enpowered machines as mentioned
in the regression potential section. Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569

Title:
  Enable the mic-mute led on Dell MTL laptops

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]
  On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is 
working but the LED(on F4) state is not changed accordingly.

  [Fix]
  There's no problem on the same series on RPL platform. It needs MTL specific 
SoF driver and controls to support the registered mixer switch. It requires the 
patches in 
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
 and 
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only required for new sof-audio-pci-intel-mtl driver. The impact should 
be restricting.

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Intel MTL powered laptops.

  [Fix]
  For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add 
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the 
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control 
matches with the updated driver.

  [Test Case]
  1. enable -proposed pocket and install firmware-sof-signed
  2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.

  [Where problems could occur]
  The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all 
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+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

[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops

[Łukasz Zemczak]

Hello Chris, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.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.

** Changed in: firmware-sof (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569

Title:
  Enable the mic-mute led on Dell MTL laptops

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]
  On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is 
working but the LED(on F4) state is not changed accordingly.

  [Fix]
  There's no problem on the same series on RPL platform. It needs MTL specific 
SoF driver and controls to support the registered mixer switch. It requires the 
patches in 
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
 and 
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only required for new sof-audio-pci-intel-mtl driver. The impact should 
be restricting.

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Intel MTL powered laptops.

  [Fix]
  For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add 
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the 
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control 
matches with the updated driver.

  [Test Case]
  1. enable -proposed pocket and install firmware-sof-signed
  2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.

  [Where problems could occur]
  The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all 
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+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

[Kernel-packages] [Bug 2051199] Please test proposed package

[Łukasz Zemczak]

Hello ethan.hsieh, 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.11 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2051199

Title:
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Mantic:
  Fix Committed
Status in alsa-ucm-conf source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs.

  mt8370-evk (G510):
  https://github.com/alsa-project/alsa-ucm-conf/pull/380
  
https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97
  mt8390-evk (G700):
  https://github.com/alsa-project/alsa-ucm-conf/pull/321
  
https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b
  mt8395-evk (G1200):
  https://github.com/alsa-project/alsa-ucm-conf/pull/322
  
https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0
  Fix a file type issue:
  https://github.com/alsa-project/alsa-ucm-conf/pull/386
  
https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf
  mt8395-evk (G1200) HDMI RX:
  https://github.com/alsa-project/alsa-ucm-conf/pull/389
  
https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1

  [Where problems could occur]
  1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu 
archive was rejected by upstream. Replace them with new patches accepted by 
upstream.
  2. Add initial support for mt8370-evk
  3. Add mt8395-evk HDMI RX support

  [Test Case]
  Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and 
mt8395-evk).
  1. Headset Jack Playback
  2. Audio (Speaker) Jack Playback
  3. mt8395-evk: HDMI RX

  Play audio by following commands.
  $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav

  [Regression Potential]
  1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk.
  2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream 
and new configs have been verified by MediaTek. It should be low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+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

[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs

[Łukasz Zemczak]

Hello ethan.hsieh, or anyone else affected,

Accepted alsa-ucm-conf into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.9-1ubuntu3.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-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. 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.

** Changed in: alsa-ucm-conf (Ubuntu Mantic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-mantic

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2051199

Title:
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Mantic:
  Fix Committed
Status in alsa-ucm-conf source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs.

  mt8370-evk (G510):
  https://github.com/alsa-project/alsa-ucm-conf/pull/380
  
https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97
  mt8390-evk (G700):
  https://github.com/alsa-project/alsa-ucm-conf/pull/321
  
https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b
  mt8395-evk (G1200):
  https://github.com/alsa-project/alsa-ucm-conf/pull/322
  
https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0
  Fix a file type issue:
  https://github.com/alsa-project/alsa-ucm-conf/pull/386
  
https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf
  mt8395-evk (G1200) HDMI RX:
  https://github.com/alsa-project/alsa-ucm-conf/pull/389
  
https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1

  [Where problems could occur]
  1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu 
archive was rejected by upstream. Replace them with new patches accepted by 
upstream.
  2. Add initial support for mt8370-evk
  3. Add mt8395-evk HDMI RX support

  [Test Case]
  Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and 
mt8395-evk).
  1. Headset Jack Playback
  2. Audio (Speaker) Jack Playback
  3. mt8395-evk: HDMI RX

  Play audio by following commands.
  $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav

  [Regression Potential]
  1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk.
  2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream 
and new configs have been verified by MediaTek. It should be low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[Łukasz Zemczak]

Releasing early as we're in the middle of a point-release. Autopkgtests
look good, the actual testing will happen on the RCs.

-- 
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/2045586

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in livecd-rootfs source package in Jammy:
  Fix Released
Status in util-linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in livecd-rootfs source package in Mantic:
  New
Status in util-linux source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in util-linux source package in Noble:
  New

Bug description:
  [impact]
  In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, 
with the expectation that this would give us a reliable, race-free way of 
loop-mounting partitions from a disk image during image build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

    https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

    https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

  The losetup usage has been backported to Jammy, and sees frequent
  failures there.

  [test case]
  The autopkgtests will provide enough confidence that the changes are not 
completely broken. Whether the change helps with the races on riscv can be 
"tested in prod" just as well as any other way.

  [regression potential]
  If the backport has been done incorrectly, image builds can fail (and the 
autopkgtests will fail if it has been completely bungled). This can be quickly 
handled. There is no foreseeable way for this to result in successful builds 
but broken images, which would be a much more difficult failure mode to unpick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[Łukasz Zemczak]

Hello Steve, or anyone else affected,

Accepted livecd-rootfs into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.765.39 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.

** Changed in: livecd-rootfs (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
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/2045586

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in util-linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in livecd-rootfs source package in Mantic:
  New
Status in util-linux source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in util-linux source package in Noble:
  New

Bug description:
  [impact]
  In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, 
with the expectation that this would give us a reliable, race-free way of 
loop-mounting partitions from a disk image during image build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

    https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

    https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

  The losetup usage has been backported to Jammy, and sees frequent
  failures there.

  [test case]
  The autopkgtests will provide enough confidence that the changes are not 
completely broken. Whether the change helps with the races on riscv can be 
"tested in prod" just as well as any other way.

  [regression potential]
  If the backport has been done incorrectly, image builds can fail (and the 
autopkgtests will fail if it has been completely bungled). This can be quickly 
handled. There is no foreseeable way for this to result in successful builds 
but broken images, which would be a much more difficult failure mode to unpick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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

[Kernel-packages] [Bug 2042090] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for firmware-sof 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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

[Kernel-packages] [Bug 2044330] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for firmware-sof 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs/2044330

Title:
  Update soundwire topology files for Intel RPL platforms

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  Old RPL soundwire topology files are found to be muted when doing audio 
capture on left channel.

  [Fix]

  The commit from https://github.com/thesofproject/sof-bin/ is required.
  * 
https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d
 (Update v2.2.8 topology files for Intel RPL platforms)

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

  [Where problems could occur]
  Most topology files for Intel RPL are updated. Need more confirmation on 
Intel RPL platforms.

  [Other info]

  Lunar is skipped, as it'll be EOL soon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+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

[Kernel-packages] [Bug 2051068] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2051068

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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

[Kernel-packages] [Bug 2043059] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for kdump-tools 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2043059

Title:
  Installation errors out when installing in a chroot

Status in kdump-tools package in Ubuntu:
  Fix Released
Status in linux-nvidia package in Ubuntu:
  Invalid
Status in kdump-tools source package in Jammy:
  Fix Committed
Status in linux-nvidia source package in Jammy:
  Invalid
Status in kdump-tools source package in Mantic:
  Fix Released
Status in linux-nvidia source package in Mantic:
  Invalid
Status in kdump-tools source package in Noble:
  Fix Released
Status in linux-nvidia source package in Noble:
  Invalid

Bug description:
  [Impact]
  When installing in a chroot environment, the kdump-tools kernel hook will 
fail. This breaks certain OS image creation tools, such as BCM (which I assume 
is NVIDIA Base Command Manager from context). While BCM's image generation tool 
requires some additional tweaks to consume this, the proposed fix is necessary, 
and should be sufficient for other tools that use chroots.

  [Test Plan]
  1) debootstrap a chroot environment for the target Ubuntu release
  2) Install kdump-tools within that environment
  3) Install a kernel package and make sure it succeeds.
  4) do the same steps in a virtual machine, but with `ischroot` symlinked to 
/dev/true at install time. This should simulate a system that was just 
installed with an image prepared as above.
  5) Then restore ischroot, and reboot.
  6) Confirm the systemd service does generate an initramfs at boot, and
  7) that a crash dump can be triggered afterwords.

  [Where Problems Could Occur]
  The solution we implemented in noble was simply to detect a chroot 
environment with ischroot, and disable initramfs generation. The systemd 
service will detect that an initrd is missing, and generate one on first boot. 
A source of potential problems is if that does not happen for some reason, 
resulting in a kdump-tools service failure on first boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+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

[Kernel-packages] [Bug 2044657] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for zfs-linux 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Jammy:
  Fix Committed
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  Fix Released
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

   * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
 only makes it stronger and not weaker, thus if it were incorrect, likely
 only performance would be impacted (and it is unlikely to be incorrect
 given upstream reviews and attention to data corruption issues; also,
 there are no additional changes to that function upstream)

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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

[Kernel-packages] [Bug 1837227] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for systemd 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.

-- 
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/1837227

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1837227/+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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

[Łukasz Zemczak]

Hello Kellen, or anyone else affected,

Accepted makedumpfile into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.7-1ubuntu2.5 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Changed in: makedumpfile (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Łukasz Zemczak]

** Tags added: kernel-bug regression-update

-- 
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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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

[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr

[Łukasz Zemczak]

I have promoted both packages to main:

$ change-override -S -s mantic -c main protection-domain-mapper
Override component to main
protection-domain-mapper 1.0-4ubuntu2 in mantic: universe/misc -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic amd64: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic arm64: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic armhf: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic ppc64el: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic riscv64: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic s390x: 
universe/net/optional/100% -> main
Override [y|N]? y
7 publications overridden.

$ change-override -S -s mantic -c main qrtr
Override component to main
qrtr 1.0-2ubuntu1 in mantic: universe/misc -> main
libqrtr-dev 1.0-2ubuntu1 in mantic amd64: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic arm64: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic armhf: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic ppc64el: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic riscv64: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic s390x: universe/libdevel/optional/100% -> 
main
libqrtr1 1.0-2ubuntu1 in mantic amd64: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic arm64: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic armhf: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic ppc64el: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic riscv64: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic s390x: universe/libs/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic amd64: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic arm64: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic armhf: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic ppc64el: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic riscv64: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic s390x: universe/net/optional/100% -> main
Override [y|N]? y
19 publications overridden.

** Changed in: protection-domain-mapper (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: qrtr (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2038942

Title:
  [MIR] protection-domain-mapper & qrtr

Status in protection-domain-mapper package in Ubuntu:
  Fix Released
Status in qrtr package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package protection-domain-mapper is already in Ubuntu universe.
  The package protection-domain-mapper build for the architectures it is 
designed to work on.
  It currently builds and works for architectures: any, verified as working on 
arm64
  Link to package https://launchpad.net/ubuntu/+source/protection-domain-mapper

  [Rationale]

  - The package protection-domain-mapper is required in Ubuntu main for
    ubuntu-desktop on ARM64, as it enables power-indicator (among other
    things) on most Windows on Arm laptops (qcom based laptops ~7 SKUs
    and more coming). There is no other way to implement this.

  - protection-domain-mapper depends on qrtr for library and a systemd
    service it provides.

  - There is no other/better way to solve this that is already in main
    or should go universe->main instead of this. As this is the only
    implementation of talking to the qcom hardware.

  - The package protection-domain-mapper is required in Ubuntu main no
    later than today due to Mantic release, if we want to have the best
    impression of Ubuntu Desktop in the live session on x13s.

  - If that fails, having it fixed as SRU is the next best option.

  [Security]

  - No CVEs/security issues in this software in the past. This is a
    reference open source implementation of these tools, which otherwise
    are used on qcom Android devices

  - no `suid` or `sgid` binaries no executables in `/sbin` and
    `/usr/sbin`

  - Package does install services: pd-mapper.service & qrtr-ns.service
    which allow runtime access to the qcom hardware which are run as
    root

  - Security has been kept in mind and common isolation/risk-mitigation
  patterns are in place utilizing the following features:

  - Packages does not open privileged ports (ports < 1024).

  - Package does not expose any external endpoints

  - Packages does not contain extensions to security-sensitive software
    (filters, scanners, plugins, UI skins, ...)

  [Quality assurance - function/usage]

  - The package works well right after install, i.e. power 

[Kernel-packages] [Bug 2000228] Update Released

[Łukasz Zemczak]

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2000228

Title:
  [SRU] Add initial support for Mediatek Genio boards

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and 
mt8395-evk)

  mt8365-evk:
  
https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886

  mt8390-evk (G700): (Still under review)
  https://github.com/alsa-project/alsa-ucm-conf/pull/321

  mt8395-evk (G1200): (Still under review)
  https://github.com/alsa-project/alsa-ucm-conf/pull/322

  [Where problems could occur]
  Audio function doesn't work on Mediatek Genio boards.
  mantic: mt8390-evk, and mt8395-evk
  lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk

  [Test Case]
  Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and 
mt8395-evk).
  1. Headset Jack Playback
  2. Audio (Speaker) Jack Playback
  3. HDMI Playback

  Play audio by following commands.
  $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav

  [Regression Potential]
  Add initial support for Mediatek Genio boards. There should be no risk.
  mantic: mt8390-evk, and mt8395-evk
  lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+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

[Kernel-packages] [Bug 1990621] Re: [SRU] PXE Boot contains wrong suggested link to ISO for live file system

[Łukasz Zemczak]

Hello James, or anyone else affected,

Accepted casper into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/casper/1.470.3 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  To properly test it you
will need to obtain and boot a daily build of a Live CD for jammy.  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.

** Changed in: casper (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
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/1990621

Title:
  [SRU] PXE Boot contains wrong suggested link to ISO for live file
  system

Status in casper package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in casper source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid

Bug description:
  [ Impact ]

   * What are the effects of the bug on users?
     casper's intercative netmount fails to download the latest
     Ubuntu LTS ISOs after the release of the first point release
     (e.g. 22.04.1)

   * What is the justification for backporting the fix to the
     There are at least 2 bug reports about this problem
     (LP: #1990621, #1948884) and this fix will improve the
     user experience with a low probaility of side effects.

   * How does the upload fix the bug?

     - The patch adds a '-latest' to the download URLs (see more
   details here: 
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
     - Additionaly Łukasz Zemczak (sil2100) created symlinks that
   (as the name of the urls imply) always points to the latest
   Ubuntu ISO for a given version.

  [ Test Plan ]

   * How to reproduce the bug?

     - Just run the failling parts of the casper script on a
   22.04.1 <= x < 22.10 machine:

   # would normally be set by initramfs-tools
   $ DPKG_ARCH=amd64

   # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
   $ source /etc/os-release

   # see 
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
   $ 
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso

   # see 
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
   $ wget "${server_url}" -O /dev/null

   # You should observe an ERROR 404: Not Found.

   * Test that the new links work:
     - Test Script: 
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
     - New -latest URLs
   - 
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
   - https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-arm64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-ppc64el.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso

   * Łukasz Zemczak (sil2100) tested that casper can handle
     HTTP 301 redirects. (See 
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497/comments/1193559)

  [ Where problems could occur ]

   * The Ubuntu Release Team could forget or the automation
     could stop working to update the -latest links, but this
     would, in the worst case, result in a not more worse
     situation than the current bug.

  [ Other Info ]

   * Nick Rosbrook (enr0n) pointed out in comment #3 that the
     script allows the user to provide their own url.
     This should only be considered a temporary workaround as
     a user has to be aware of this bug and has to aquire a
     URL by themself. Copy & pasting URLs from the web is
     potentialy error prone and unsafe.

   * As far as I am aware, there was a discussion between
     Łukasz Zemczak (sil2100), Brian Mur

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

[Łukasz Zemczak]

The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
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/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

[Łukasz Zemczak]

The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
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/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

[Łukasz Zemczak]

The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

** Changed in: lttng-modules (Ubuntu Kinetic)
   Status: Fix Committed => Confirmed

-- 
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/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)   

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

[Łukasz Zemczak]

The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
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/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |

[Kernel-packages] [Bug 2012612] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for dkms 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2012612

Title:
  Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Jammy:
  Fix Released
Status in dkms source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  Impact:
  Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG 
which prevent it from building if a specific configuration is enabled/disabled.
  This feature was released for kinetic but not for jammy.
  This backports the patch to jammy as well.

  [racb] This feature is required as the simplest way to deal with some
  of the HWE DKMS fixes needed in Jammy such as in bug 2012412.

  Fix:
  Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic.
  In order to be applied, I had to slightly modify the first junk. Other than 
that, it was a clean backport.

  [Testcase]

  $ sudo apt install linux-image-kvm linux-headers-kvm
  $ sudo apt install evdi-dkms

  Before the fix, it will fail with this error:
  DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64)
  Thu Mar 23 10:10:14 UTC 2023
  make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm'
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit 
declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
     49 | return i2c_add_adapter(adapter);
    |^~~
    |i2c_verify_adapter
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function 
‘evdi_i2c_remove’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit 
declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
     54 | i2c_del_adapter(adapter);
    | ^~~
    | i2c_verify_adapter
  cc1: some warnings being treated as errors
  make[1]: *** [scripts/Makefile.build:297: 
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1
  make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm'

  This fails because CONFIG_I2C=n for a KVM kernel derivative.
  Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C 
CONFIG_DRM"

  After the fix, it will not build:
  Building initial module for 5.15.0-1029-kvm
  Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf 
for module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch.
  The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for 
module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch/config.
  This indicates that it should not be built.
  Skipped.

  [Regression potential]

  Very low, this is just a simple feature to prevent building a module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2012612/+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

[Kernel-packages] [Bug 2025353] Update Released

[Łukasz Zemczak]

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2025353

Title:
  Add support of AMD Pink Sardine and RPL DMIC

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Released
Status in alsa-ucm-conf source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD 
platform with AMD Pink Sardine and RPL DMIC.

  [Fix]
  Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine.

  [Test]
  The mic mute LED works fine.

  [Where problems could occur]
  Low, upstream fix.
  It may break mic-mute LED.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2025353/+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

[Kernel-packages] [Bug 1968604] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-firmware 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1968604

Title:
  rtl8761b usb bluetooth doesn't work following reboot until
  unplug/replug

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip.
  0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio

  USB adapter very often stops working, can't connect or find other
  bluetooth devices. The adapter can't work even after reboots.

  The following entries appear in the log:
  апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout
  апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout
  апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout

  Firmware loaded correctly, but something is not working.
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814

  1) I use:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  2) linux-firmware: 20220329.git681281e4-0ubuntu1
  3) What you expected to happen? I expect a well working bluetooth adapter.
  4) What happened instead? My bluetooth adapter may work, may not. The adapter 
may stop finding and connecting to other devices.

  I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1
  I've downloaded Windows's archive 
http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab
  I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and 
replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted 
rtl8761bu_config.bin
  After I changed firmware my usb dongle work fine.

  Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other 
correct version?
  Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate 
packages. I will remove the RTL8761B firmware package and put them manually.

  bluetoothctl --version
  bluetoothctl: 5.64

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:E0:4C:FC:E2:03  ACL MTU: 1021:6  SCO MTU: 255:12
  UP RUNNING
  RX bytes:5751 acl:49 sco:0 events:489 errors:0
  TX bytes:219114 acl:398 sco:0 commands:83 errors:0
  Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH HOLD SNIFF PARK
  Link mode: PERIPHERAL ACCEPT
  Name: 'desktop'
  Class: 0x7c0104
  Service Classes: Rendering, Capturing, Object Transfer, Audio, 
Telephony
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x97b
  LMP Version: 5.1 (0xa)  Subversion: 0xec43
  Manufacturer: Realtek Semiconductor Corporation (93)

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  Realtek's worker updated these bad firmware.
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80

  [Test Case]

  Connect to and use a bluetooth device connected to a RTL8761B base USB
  BT controller.

  [Fix]

  Use latest rtl8761bu firmware blobs updates from linux-firmware.

  [Where Problems Could Occur]

  These firmwares are specific for the rtl8671b chips. So users of USB
  or UART BT controllers based on that chip could see problems when
  trying to connect to and use bluetooth devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More 

[Kernel-packages] [Bug 2016700] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-firmware 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2016700

Title:
  Add support for X13s wifi

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Wifi on a Lenovo X13s is not coming up. The board ID is unknown.

  [Fix]

  Uptream commit d1dc30480fef ("ath11k: WCN6855 hw2.0: update
  board-2.bin")

  [Test Case]

  Check that wifi comes up.

  [Where Problems Could Occur]

  ath11k based machines could experince Wifi issues if that upstream
  binary is broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2016700/+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

[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32

[Łukasz Zemczak]

Hello Heitor, or anyone else affected,

Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.15 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Changed in: zfs-linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964992

Title:
  ZFS ignores ARC sizes below allmem/32

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. 
This prevents users from properly restraining ARC sizes, and can cause 
increased memory contention in some systems.

  [Test Plan]
  1. Deploy test system with ZFS storage and 32GB RAM
  2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf
     # cat /etc/modprobe.d/99-zfs-arc.conf
     options zfs zfs_arc_min=536870912
     options zfs zfs_arc_max=966367641
  3. Reboot system
  4. Verify ARC sizes through "arc_summary"
     # arc_summary | grep -A3 "ARC size"
     ARC size (current):   < 0.1 %1.3 MiB
     Target size (adaptive):   100.0 %   15.7 GiB
     Min size (hard limit):  3.2 %  512.0 MiB
     Max size (high water):   31:1   15.7 GiB

  For a 32GB test system, we should be able to set max ARC sizes below
  1GB.

  [Fix]
  This has been fixed by upstream commit:
   - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32"
   - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max"

  The commit has been introduced in upstream zfs-2.0.0, so it's needed
  for Bionic and Focal. Releases starting with Impish already have this
  commit by default:

  $ git describe --contains 36a6e2335c45
  zfs-2.0.0-rc1~332
  $ rmadison zfs-linux
   zfs-linux | 0.7.5-1ubuntu15| bionic  | source
   zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates  | source
   zfs-linux | 0.8.3-1ubuntu12| focal   | source
   zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
   zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates   | source
   zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed  | source
   zfs-linux | 2.0.6-1ubuntu2 | impish  | source
   zfs-linux | 2.0.6-1ubuntu2.1   | impish-updates  | source
   zfs-linux | 2.1.2-1ubuntu3 | jammy   | source

  [Regression Potential]
  The introduced commit essentially removes the limitation of setting ARC 
tunables below allmem/32, and re-arranges the order of how some of the tunables 
are parsed. Regressions would possibly show up as other tunables being ignored 
or not being set correctly due to parsing errors. We should validate whether 
other ARC related tunables are still being set correctly, and whether ZFS is 
using the set values for the ARC memory thresholds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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

[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Łukasz Zemczak]

Hello Kleber, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Changed in: systemd (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [SRU Impact]

  Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
  sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
  This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).

  [Fix]
  Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.

  [Test to reproduce the issue]
  1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
  2. Run the autotests for upstream and/or root-unittests:
  autopkgtest --test-name=upstream systemd -- qemu 

  [Test to verify the fix]
  1. Same as above
  2. Apply the fix in your local repo and run the tests using your local repo
  autopkgtest --test-name=upstream  -- qemu 

  [Where problems could occur]
  This is not gonna affect end users since it is a change in the test only.
  It may impact autotests, but it's a very low probability.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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

[Kernel-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[Łukasz Zemczak]

Hello Stefan, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Changed in: systemd (Ubuntu Focal)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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

[Kernel-packages] [Bug 2007331] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007331

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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

[Kernel-packages] [Bug 1989705] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-signed-
lowlatency-hwe-5.19 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1989705

Title:
  SIGNEDv3: add a linux-generate ancillary package

Status in linux-signed package in Ubuntu:
  Fix Released

Bug description:
  Add a new linux-generate package as an ancillary package.  This allows
  us to avoid publishing the custom signing tarballs into the archive,
  which in turn helps ensure we never sign a kernel with an
  inappropriate key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1989705/+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

[Kernel-packages] [Bug 1996892] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1996892

Title:
  Expose built-in trusted and revoked certificates

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [ Impact ]

   * Kernels have a set of builtin trusted and revoked certificates as a bundle
   * It is not very easy to access them, one needs to either download linux 
kernel package source code; or boot the kernel look up builtin hashes; and then 
find certificates externally
   * It would be more convenient for inspection to expose these in the 
buildinfo package, which already exposes auxiliary kernel information

  [ Test Plan ]

   * sudo apt install linux-buildinfo-$(uname -r)
   * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and 
contains livepatch cert
   * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists 
and contains 2012 cert

  Example output:
  $ grep Subject: -r usr/lib/linux
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = 
Canonical Ltd. Live Patch Signing
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, 
ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel 
Module Signing
  usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: 
C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical 
Ltd. Secure Boot Signing

  
  [ Where problems could occur ]

   * buildinfo is an auxiliary package not installed by default, but
  used by developer tooling and packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+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

[Kernel-packages] [Bug 1998398] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1998398

Title:
  Kinetic update: upstream stable patchset 2022-11-30

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-11-30
     from git://git.kernel.org/

  clk: tegra: Fix Tegra PWM parent clock
  Revert "btrfs: call __btrfs_remove_free_space_cache_locked on cache load 
failure"
  UBUNTU: Upstream stable to v6.0.5
  ocfs2: clear dinode links count in case of error
  ocfs2: fix BUG when iput after ocfs2_mknod fails
  selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context()
  cpufreq: qcom: fix writes in read-only memory region
  i2c: qcom-cci: Fix ordering of pm_runtime_xx and i2c_add_adapter
  x86/microcode/AMD: Apply the patch early on every logical thread
  hwmon/coretemp: Handle large core ID value
  ata: ahci-imx: Fix MODULE_ALIAS
  ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS
  x86/resctrl: Fix min_cbm_bits for AMD
  cpufreq: qcom: fix memory leak in error path
  drm/amdgpu: fix sdma doorbell init ordering on APUs
  mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages
  kvm: Add support for arch compat vm ioctls
  KVM: arm64: vgic: Fix exit condition in scan_its_table()
  media: ipu3-imgu: Fix NULL pointer dereference in active selection access
  media: mceusb: set timeout to at least timeout provided
  media: venus: dec: Handle the case where find_format fails
  x86/topology: Fix multiple packages shown on a single-package system
  x86/topology: Fix duplicated core ID within a package
  btrfs: fix processing of delayed data refs during backref walking
  btrfs: fix processing of delayed tree block refs during backref walking
  drm/vc4: Add module dependency on hdmi-codec
  ACPI: extlog: Handle multiple records
  tipc: Fix recognition of trial period
  tipc: fix an information leak in tipc_topsrv_kern_subscr
  i40e: Fix DMA mappings leak
  HID: magicmouse: Do not set BTN_MOUSE on double report
  sfc: Change VF mac via PF as first preference if available.
  net/atm: fix proc_mpc_write incorrect return value
  net: phy: dp83867: Extend RX strap quirk for SGMII mode
  net: phylink: add mac_managed_pm in phylink_config structure
  scsi: lpfc: Fix memory leak in lpfc_create_port()
  udp: Update reuse->has_conns under reuseport_lock.
  cifs: Fix xid leak in cifs_create()
  cifs: Fix xid leak in cifs_copy_file_range()
  cifs: Fix xid leak in cifs_flock()
  cifs: Fix xid leak in cifs_ses_add_channel()
  dm: remove unnecessary assignment statement in alloc_dev()
  net: hsr: avoid possible NULL deref in skb_clone()
  ionic: catch NULL pointer issue on reconfig
  netfilter: nf_tables: relax NFTA_SET_ELEM_KEY_END set flags requirements
  nvme-hwmon: consistently ignore errors from nvme_hwmon_init
  nvme-hwmon: kmalloc the NVME SMART log buffer
  nvmet: fix workqueue MEM_RECLAIM flushing dependency
  net: sched: cake: fix null pointer access issue when cake_init() fails
  net: sched: delete duplicate cleanup of backlog and qlen
  net: sched: sfb: fix null pointer access issue when sfb_init() fails
  sfc: include vport_id in filter spec hash and equal()
  wwan_hwsim: fix possible memory leak in wwan_hwsim_dev_new()
  net: hns: fix possible memory leak in hnae_ae_register()
  net: sched: fix race condition in qdisc_graft()
  net: phy: dp83822: disable MDI crossover status change interrupt
  iommu/vt-d: Allow NVS regions in arch_rmrr_sanity_check()
  iommu/vt-d: Clean up si_domain in the init_dmars() error path
  ACPI: video: Force backlight native for more TongFang devices
  x86/Kconfig: Drop check for -mabi=ms for CONFIG_EFI_STUB
  mm: /proc/pid/smaps_rollup: fix no vma's null-deref
  smb3: interface count displayed incorrectly
  cpufreq: tegra194: Fix module loading
  KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter()
  KVM: x86: Add compat handler for 

[Kernel-packages] [Bug 1999079] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1999079

Title:
  Kinetic update: upstream stable patchset 2022-12-07

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-12-07

  Ported from the following upstream stable releases:
  v5.15.77, v6.0.7

     from git://git.kernel.org/

  can: j1939: transport: j1939_session_skb_drop_old(): spin_unlock_irqrestore() 
before kfree_skb()
  can: kvaser_usb: Fix possible completions during init_completion
  ALSA: Use del_timer_sync() before freeing timer
  ALSA: usb-audio: Add quirks for M-Audio Fast Track C400/600
  ALSA: au88x0: use explicitly signed char
  ALSA: rme9652: use explicitly signed char
  USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM
  usb: gadget: uvc: fix sg handling in error case
  usb: gadget: uvc: fix sg handling during video encode
  usb: dwc3: gadget: Stop processing more requests on IMI
  usb: dwc3: gadget: Don't set IMI for no_interrupt
  usb: bdc: change state when port disconnected
  usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 
controller
  mtd: rawnand: marvell: Use correct logic for nand-keep-config
  xhci: Add quirk to reset host back to default state at shutdown
  xhci-pci: Set runtime PM as default policy on all xHC 1.2 or later devices
  xhci: Remove device endpoints from bandwidth list when freeing the device
  tools: iio: iio_utils: fix digit calculation
  iio: light: tsl2583: Fix module unloading
  iio: temperature: ltc2983: allocate iio channels once
  iio: adxl372: Fix unsafe buffer attributes
  fbdev: smscufx: Fix several use-after-free bugs
  cpufreq: intel_pstate: Read all MSRs on the target CPU
  cpufreq: intel_pstate: hybrid: Use known scaling factor for P-cores
  fs/binfmt_elf: Fix memory leak in load_elf_binary()
  exec: Copy oldsighand->action under spin-lock
  mac802154: Fix LQI recording
  scsi: qla2xxx: Use transport-defined speed mask for supported_speeds
  drm/amdgpu: disallow gfxoff until GC IP blocks complete s2idle resume
  drm/msm/dsi: fix memory corruption with too many bridges
  drm/msm/hdmi: fix memory corruption with too many bridges
  drm/msm/dp: fix IRQ lifetime
  coresight: cti: Fix hang in cti_disable_hw()
  mmc: sdhci_am654: 'select', not 'depends' REGMAP_MMIO
  mmc: core: Fix kernel panic when remove non-standard SDIO card
  mmc: sdhci-pci-core: Disable ES for ASUS BIOS on Jasper Lake
  mmc: sdhci-esdhc-imx: Propagate ESDHC_FLAG_HS400* only on 8bit bus
  counter: microchip-tcb-capture: Handle Signal1 read and Synapse
  kernfs: fix use-after-free in __kernfs_remove
  pinctrl: Ingenic: JZ4755 bug fixes
  ARC: mm: fix leakage of memory allocated for PTE
  perf auxtrace: Fix address filter symbol name match for modules
  s390/futex: add missing EX_TABLE entry to __futex_atomic_op()
  s390/pci: add missing EX_TABLE entries to 
__pcistg_mio_inuser()/__pcilg_mio_inuser()
  mmc: block: Remove error check of hw_reset on reset
  ethtool: eeprom: fix null-deref on genl_info in dump
  net: ieee802154: fix error return code in dgram_bind()
  media: v4l2: Fix v4l2_i2c_subdev_set_name function documentation
  media: atomisp: prevent integer overflow in sh_css_set_black_frame()
  drm/msm: Fix return type of mdp4_lvds_connector_mode_valid
  KVM: selftests: Fix number of pages for memory slot in 
memslot_modification_stress_test
  ASoC: qcom: lpass-cpu: mark HDMI TX registers as volatile
  perf: Fix missing SIGTRAPs
  sched/core: Fix comparison in sched_group_cookie_match()
  arc: iounmap() arg is volatile
  mtd: rawnand: intel: Add missing of_node_put() in ebu_nand_probe()
  ASoC: qcom: lpass-cpu: Mark HDMI TX parity register as volatile
  ALSA: ac97: fix possible memory leak in snd_ac97_dev_register()
  perf/x86/intel/lbr: Use setup_clear_cpu_cap() instead of clear_cpu_cap()
  tipc: fix a 

[Kernel-packages] [Bug 2001618] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/2001618

Title:
  BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from
  ubuntu_kernel_selftests failed on K-5.19 P9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related 
tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are 
not supported.

   test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 
0x02
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to 
select_runtime err=-524
   ...
   test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to 
select_runtime err=-524
   ...
   test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return
   eBPF filter atomic op code c3 (@3) unsupported
   FAIL to select_runtime err=-524
   ...
   test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed]

  Please find attachment for the complete test log.

  [Fix]
  * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations
  * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations
  * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg
  These patches can be cherry-picked into Kinetic kernel.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/

  Steps:
  1. Reboot with the patched kernel
  2. Run:
    sudo dmesg -C
    sudo modprobe test_bpf
    sudo dmesg

  Tested with Power9 node baltar, with the patched kernel there will be no 
failure reported by the test_bpf:
    test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed]

  [Where problems could occur]
  This patchset just broaden the BPF operations support on ppc64, we might see 
some new failures when using these instruction somewhere in the future.

  Cascardo: The existing atomic operations may regress as well, since
  they now produce different code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+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

[Kernel-packages] [Bug 2002679] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2002679

Title:
  Unset versioned gcc-12 for hwe-5.19 build

Status in linux-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux-hwe-5.19 source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]
  In order to use the same compiler as used for kinetic:linux (gcc-12) we have 
made some changes to explicitly compile jammy:linux-hwe-5.19 with the same 
compiler. These changes were mainly part of bug 1999750 and bug 1991664. 
However, such changes are breaking the build of a number of dkms packages.

  [ Fix ]
  The proposed temporary workaround is to revert commit "UBUNTU: [Packaging] 
use versioned gcc-12", which would make the kernel compile with the default GCC 
in Jammy (gcc-11), while a proper solution is being worked on.

  [ Where problems could occur ]
  gcc-12 is necessary to enable some of the new security-related kernel 
configs, so going back to gcc-11 will disable such features. However, this 
would not regress users when upgrading from the generic kernel to hwe-5.19 in 
Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2002679/+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

[Kernel-packages] [Bug 1999828] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1999828

Title:
  Kinetic update: upstream stable patchset 2022-12-15

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-12-15

  Ported from the following upstream stable releases:
  v5.15.78, v6.0.8

     from git://git.kernel.org/

  serial: ar933x: Deassert Transmit Enable on ->rs485_config()
  KVM: x86: Trace re-injected exceptions
  RDMA/cma: Use output interface for net_dev check
  IB/hfi1: Correctly move list in sc_disable()
  RDMA/hns: Disable local invalidate operation
  NFSv4: Fix a potential state reclaim deadlock
  NFSv4.1: Handle RECLAIM_COMPLETE trunking errors
  NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot
  SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed
  NFSv4.2: Fixup CLONE dest file size for zero-length count
  nfs4: Fix kmemleak when allocate slot failed
  net: dsa: Fix possible memory leaks in dsa_loop_init()
  RDMA/core: Fix null-ptr-deref in ib_core_cleanup()
  RDMA/qedr: clean up work queue on failure in qedr_alloc_resources()
  net: dsa: fall back to default tagger if we can't load the one from DT
  nfc: fdp: Fix potential memory leak in fdp_nci_send()
  nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()
  nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send()
  nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send()
  net: fec: fix improper use of NETDEV_TX_BUSY
  ata: pata_legacy: fix pdc20230_set_piomode()
  net: sched: Fix use after free in red_enqueue()
  net: tun: fix bugs for oversize packet when napi frags enabled
  netfilter: nf_tables: netlink notifier might race to release objects
  netfilter: nf_tables: release flow rule object from commit path
  ipvs: use explicitly signed chars
  ipvs: fix WARNING in __ip_vs_cleanup_batch()
  ipvs: fix WARNING in ip_vs_app_net_cleanup()
  rose: Fix NULL pointer dereference in rose_send_frame()
  mISDN: fix possible memory leak in mISDN_register_device()
  isdn: mISDN: netjet: fix wrong check of device registration
  btrfs: fix inode list leak during backref walking at resolve_indirect_refs()
  btrfs: fix inode list leak during backref walking at find_parent_nodes()
  btrfs: fix ulist leaks in error paths of qgroup self tests
  netfilter: ipset: enforce documented limit to prevent allocating huge memory
  Bluetooth: virtio_bt: Use skb_put to set length
  Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del()
  Bluetooth: L2CAP: Fix memory leak in vhci_write
  net: mdio: fix undefined behavior in bit shift for __mdiobus_register
  ibmvnic: Free rwi on reset success
  stmmac: dwmac-loongson: fix invalid mdio_node
  net/smc: Fix possible leaked pernet namespace in smc_init()
  net, neigh: Fix null-ptr-deref in neigh_table_clear()
  ipv6: fix WARNING in ip6_route_net_exit_late()
  vsock: fix possible infinite sleep in vsock_connectible_wait_data()
  media: rkisp1: Don't pass the quantization to rkisp1_csm_config()
  media: rkisp1: Initialize color space on resizer sink and source pads
  media: rkisp1: Use correct macro for gradient registers
  media: rkisp1: Zero v4l2_subdev_format fields in when validating links
  media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE
  media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE
  media: dvb-frontends/drxk: initialize err to 0
  media: meson: vdec: fix possible refcount leak in vdec_probe()
  media: v4l: subdev: Fail graciously when getting try data for NULL state
  ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init()
  scsi: core: Restrict legal sdev_state transitions via sysfs
  HID: saitek: add madcatz variant of MMO7 mouse device ID
  drm/amdgpu: set vm_update_mode=0 as default for Sienna Cichlid in SRIOV case
  i2c: xiic: Add platform module alias
  efi/tpm: Pass correct address to memblock_reserve
  

[Kernel-packages] [Bug 1994069] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994069

Title:
  Kinetic update: v5.19.10 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.10 upstream stable release
     from git://git.kernel.org/

  iommu/vt-d: Fix kdump kernels boot failure with scalable mode
  net/mlx5: Introduce ifc bits for using software vhca id
  net/mlx5: Use software VHCA id when it's supported
  RDMA/mlx5: Rely on RoCE fw cap instead of devlink when setting profile
  RDMA/mlx5: Add a umr recovery flow
  RDMA/mlx5: Fix UMR cleanup on error flow of driver init
  ACPI: resource: skip IRQ override on AMD Zen platforms
  Input: goodix - add support for GT1158
  platform/surface: aggregator_registry: Add support for Surface Laptop Go 2
  drm/msm/rd: Fix FIFO-full deadlock
  peci: cpu: Fix use-after-free in adev_release()
  kvm: x86: mmu: Always flush TLBs when enabling dirty logging
  dt-bindings: iio: gyroscope: bosch,bmg160: correct number of pins
  HID: ishtp-hid-clientHID: ishtp-hid-client: Fix comment typo
  hid: intel-ish-hid: ishtp: Fix ishtp client sending disordered message
  Bluetooth: MGMT: Fix Get Device Flags
  tg3: Disable tg3 device on system reboot to avoid triggering AER
  r8152: add PID for the Lenovo OneLink+ Dock
  gpio: mockup: remove gpio debugfs when remove device
  ieee802154: cc2520: add rc code in cc2520_tx()
  Input: iforce - add support for Boeder Force Feedback Wheel
  drm/amdgpu: disable FRU access on special SIENNA CICHLID card
  drm/amd/pm: use vbios carried pptable for all SMU13.0.7 SKUs
  nvme-pci: add NVME_QUIRK_BOGUS_NID for Lexar NM610
  nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
  drm/amd/amdgpu: skip ucode loading if ucode_size == 0
  net: dsa: hellcreek: Print warning only once
  perf/arm_pmu_platform: fix tests for platform_get_irq() failure
  platform/x86: acer-wmi: Acer Aspire One AOD270/Packard Bell Dot keymap fixes
  usb: storage: Add ASUS <0x0b05:0x1932> to IGNORE_UAS
  platform/x86: asus-wmi: Increase FAN_CURVE_BUF_LEN to 32
  LoongArch: Fix section mismatch due to acpi_os_ioremap()
  LoongArch: Fix arch_remove_memory() undefined build error
  gpio: 104-dio-48e: Make irq_chip immutable
  gpio: 104-idio-16: Make irq_chip immutable
  RDMA/irdma: Use s/g array in post send only when its valid
  Input: goodix - add compatible string for GT1158
  Linux 5.19.10
  UBUNTU: Upstream stable to v5.19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994069/+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

[Kernel-packages] [Bug 1994070] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994070

Title:
  Kinetic update: v5.19.11 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.11 upstream stable release
     from git://git.kernel.org/

  of: fdt: fix off-by-one error in unflatten_dt_nodes()
  pinctrl: qcom: sc8180x: Fix gpio_wakeirq_map
  pinctrl: qcom: sc8180x: Fix wrong pin numbers
  pinctrl: rockchip: Enhance support for IRQ_TYPE_EDGE_BOTH
  pinctrl: sunxi: Fix name for A100 R_PIO
  SUNRPC: Fix call completion races with call_decode()
  NFSv4: Turn off open-by-filehandle and NFS re-export for NFSv4.0
  gpio: mpc8xxx: Fix support for IRQ_TYPE_LEVEL_LOW flow_type in mpc85xx
  NFSv4.2: Update mode bits after ALLOCATE and DEALLOCATE
  Revert "SUNRPC: Remove unreachable error condition"
  drm/panel-edp: Fix delays for Innolux N116BCA-EA1
  drm/meson: Correct OSD1 global alpha value
  drm/meson: Fix OSD1 RGB to YCbCr coefficient
  drm/rockchip: vop2: Fix eDP/HDMI sync polarities
  drm/i915/vdsc: Set VDSC PIC_HEIGHT before using for DP DSC
  drm/i915/guc: Don't update engine busyness stats too frequently
  drm/i915/guc: Cancel GuC engine busyness worker synchronously
  block: blk_queue_enter() / __bio_queue_enter() must return -EAGAIN for nowait
  parisc: ccio-dma: Add missing iounmap in error path in ccio_probe()
  of/device: Fix up of_dma_configure_id() stub
  io_uring/msg_ring: check file type before putting
  cifs: revalidate mapping when doing direct writes
  cifs: don't send down the destination address to sendmsg for a SOCK_STREAM
  cifs: always initialize struct msghdr smb_msg completely
  blk-lib: fix blkdev_issue_secure_erase
  parisc: Allow CONFIG_64BIT with ARCH=parisc
  tools/include/uapi: Fix  for parisc and xtensa
  drm/i915/gt: Fix perf limit reasons bit positions
  drm/i915: Set correct domains values at _i915_vma_move_to_active
  drm/amdgpu: make sure to init common IP before gmc
  drm/amdgpu: Don't enable LTR if not supported
  drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
  drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
  net: Find dst with sk's xfrm policy not ctl_sk
  dt-bindings: apple,aic: Fix required item "apple,fiq-index" in affinity 
description
  cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()
  ALSA: hda/sigmatel: Keep power up while beep is enabled
  ALSA: hda/sigmatel: Fix unused variable warning for beep power change
  Linux 5.19.11
  UBUNTU: Upstream stable to v5.19.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994070/+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

[Kernel-packages] [Bug 1992266] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1992266

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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

[Kernel-packages] [Bug 1993120] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1993120

Title:
  armhf kernel compiled with gcc-12 fails to boot on pi 3/2

Status in gcc-12 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in gcc-12 source package in Kinetic:
  Invalid
Status in linux source package in Kinetic:
  Fix Released
Status in linux-raspi source package in Kinetic:
  Fix Released

Bug description:
  Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang
  on Pi 3 and 2. Seems to work fine on Pi 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+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

[Kernel-packages] [Bug 1993315] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1993315

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+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

[Kernel-packages] [Bug 1994061] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994061

Title:
  Kinetic update: v5.19.8 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.8 upstream stable release
     from git://git.kernel.org/

  drm/msm/dp: make eDP panel as the first connected connector
  drm/msm/dsi: fix the inconsistent indenting
  drm/msm/dpu: populate wb or intf before reset_intf_cfg
  drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
  drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
  drm/msm/dsi: Fix number of regulators for SDM660
  platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
  platform/x86: x86-android-tablets: Fix broken touchscreen on Chuwi Hi8 with 
Windows BIOS
  xsk: Fix corrupted packets for XDP_SHARED_UMEM
  drm/msm/gpu: Drop qos request if devm_devfreq_add_device() fails
  peci: aspeed: fix error check return value of platform_get_irq()
  iio: adc: mcp3911: make use of the sign bit
  skmsg: Fix wrong last sg check in sk_msg_recvmsg()
  bpf: Restrict bpf_sys_bpf to CAP_PERFMON
  ip_tunnel: Respect tunnel key's "flow_flags" in IP tunnels
  bpf, cgroup: Fix kernel BUG in purge_effective_progs
  drm/i915/gvt: Fix Comet Lake
  ieee802154/adf7242: defer destroy_workqueue call
  bpf: Fix a data-race around bpf_jit_limit.
  drm/i915/ttm: fix CCS handling
  drm/i915/display: avoid warnings when registering dual panel backlight
  ALSA: hda: intel-nhlt: Correct the handling of fmt_config flexible array
  wifi: cfg80211: debugfs: fix return type in ht40allow_map_read()
  xhci: Fix null pointer dereference in remove if xHC has only one roothub
  Revert "xhci: turn off port power in shutdown"
  bpf: Allow helpers to accept pointers with a fixed size
  bpf: Tidy up verifier check_func_arg()
  bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO
  Bluetooth: hci_event: Fix vendor (unknown) opcode status handling
  Bluetooth: hci_sync: Fix suspend performance regression
  Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt
  Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
  net: sparx5: fix handling uneven length packets in manual extraction
  net: smsc911x: Stop and start PHY during suspend and resume
  openvswitch: fix memory leak at failed datapath creation
  nfp: flower: fix ingress police using matchall filter
  net: dsa: xrs700x: Use irqsave variant for u64 stats update
  net: sched: tbf: don't call qdisc_put() while holding tree lock
  net/sched: fix netdevice reference leaks in attach_default_qdiscs()
  net: phy: micrel: Make the GPIO to be non-exclusive
  net: lan966x: improve error handle in lan966x_fdma_rx_get_frame()
  ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler
  cachefiles: fix error return code in cachefiles_ondemand_copen()
  cachefiles: make on-demand request distribution fairer
  mlxbf_gige: compute MDIO period based on i1clk
  kcm: fix strp_init() order and cleanup
  sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
  tcp: annotate data-race around challenge_timestamp
  Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb"
  net/smc: Remove redundant refcount increase
  soundwire: qcom: fix device status array range
  mm/slab_common: Deleting kobject in kmem_cache_destroy() without holding 
slab_mutex/cpu_hotplug_lock
  platform/mellanox: mlxreg-lc: Fix coverity warning
  platform/mellanox: mlxreg-lc: Fix locking issue
  serial: fsl_lpuart: RS485 RTS polariy is inverse
  tty: serial: atmel: Preserve previous USART mode if RS485 disabled
  staging: rtl8712: fix use after free bugs
  staging: r8188eu: Add Rosewill USB-N150 Nano to device tables
  staging: r8188eu: add firmware dependency
  Revert "powerpc: Remove unused FW_FEATURE_NATIVE references"
  powerpc: align syscall table for ppc32
  powerpc/rtas: Fix RTAS MSR[HV] handling for Cell
  vt: 

[Kernel-packages] [Bug 1994068] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994068

Title:
  Kinetic update: v5.19.9 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.9 upstream stable release
     from git://git.kernel.org/

  efi: libstub: Disable struct randomization
  efi: capsule-loader: Fix use-after-free in efi_capsule_write
  wifi: mt76: mt7921e: fix crash in chip reset fail
  wifi: iwlegacy: 4965: corrected fix for potential off-by-one overflow in 
il4965_rs_fill_link_cmd()
  fs: only do a memory barrier for the first set_buffer_uptodate()
  soc: fsl: select FSL_GUTS driver for DPIO
  Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"
  scsi: qla2xxx: Disable ATIO interrupt coalesce for quad port ISP27XX
  scsi: core: Allow the ALUA transitioning state enough time
  scsi: megaraid_sas: Fix double kfree()
  drm/gem: Fix GEM handle release errors
  drm/amdgpu: Move psp_xgmi_terminate call from amdgpu_xgmi_remove_device to 
psp_hw_fini
  drm/amdgpu: fix hive reference leak when adding xgmi device
  drm/amdgpu: Check num_gfx_rings for gfx v9_0 rb setup.
  drm/amdgpu: Remove the additional kfd pre reset call for sriov
  drm/radeon: add a force flush to delay work when radeon
  scsi: ufs: core: Reduce the power mode change timeout
  Revert "parisc: Show error if wrong 32/64-bit compiler is being used"
  parisc: ccio-dma: Handle kmalloc failure in ccio_init_resources()
  parisc: Add runtime check to prevent PA2.0 kernels on PA1.x machines
  UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2457168
  arm64: errata: add detection for AMEVCNTR01 incrementing incorrectly
  netfilter: conntrack: work around exceeded receive window
  thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR
  cpufreq: check only freq_table in __resolve_freq()
  net/core/skbuff: Check the return value of skb_copy_bits()
  md: Flush workqueue md_rdev_misc_wq in md_alloc()
  fbdev: omapfb: Fix tests for platform_get_irq() failure
  fbdev: fbcon: Destroy mutex on freeing struct fb_info
  fbdev: chipsfb: Add missing pci_disable_device() in chipsfb_pci_init()
  x86/sev: Mark snp_abort() noreturn
  drm/amdgpu: add sdma instance check for gfx11 CGCG
  drm/amdgpu: mmVM_L2_CNTL3 register not initialized correctly
  ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC
  ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc()
  ALSA: hda: Once again fix regression of page allocations with IOMMU
  ALSA: aloop: Fix random zeros in capture data when using jiffies timer
  ALSA: usb-audio: Clear fixed clock rate at closing EP
  ALSA: usb-audio: Fix an out-of-bounds bug in __snd_usb_parse_audio_interface()
  tracefs: Only clobber mode/uid/gid on remount if asked
  tracing: hold caller_addr to hardirq_{enable,disable}_ip
  tracing: Fix to check event_mutex is held while accessing trigger list
  btrfs: zoned: set pseudo max append zone limit in zone emulation mode
  btrfs: zoned: fix API misuse of zone finish waiting
  vfio/type1: Unpin zero pages
  kprobes: Prohibit probes in gate area
  perf: RISC-V: fix access beyond allocated array
  debugfs: add debugfs_lookup_and_remove()
  sched/debug: fix dentry leak in update_sched_domain_debugfs
  drm/amd/display: fix memory leak when using debugfs_lookup()
  driver core: fix driver_set_override() issue with empty strings
  nvmet: fix a use-after-free
  drm/i915/bios: Copy the whole MIPI sequence block
  drm/i915/slpc: Let's fix the PCODE min freq table setup for SLPC
  scsi: mpt3sas: Fix use-after-free warning
  scsi: lpfc: Add missing destroy_workqueue() in error path
  cgroup: Elide write-locking threadgroup_rwsem when updating csses on an empty 
subtree
  cgroup: Fix threadgroup_rwsem <-> cpus_read_lock() deadlock
  cifs: remove useless parameter 'is_fsctl' from SMB2_ioctl()
  smb3: missing inode locks in zero range
  spi: 

[Kernel-packages] [Bug 1994075] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994075

Title:
  Kinetic update: v5.19.13 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.13 upstream stable release
     from git://git.kernel.org/

  Note: v5.19.13 consisted only of reverts to patches that were not
  applied to Ubuntu kinetic, hence this patch set is "empty".

  Linux 5.19.13
  UBUNTU: Upstream stable to v5.19.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994075/+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

[Kernel-packages] [Bug 1994074] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994074

Title:
  Kinetic update: v5.19.12 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.12 upstream stable release
     from git://git.kernel.org/

  smb3: Move the flush out of smb2_copychunk_range() into its callers
  smb3: fix temporary data corruption in collapse range
  smb3: fix temporary data corruption in insert range
  usb: add quirks for Lenovo OneLink+ Dock
  usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
  smb3: use filemap_write_and_wait_range instead of filemap_write_and_wait
  Revert "usb: add quirks for Lenovo OneLink+ Dock"
  Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
  xfrm: fix XFRMA_LASTUSED comment
  block: remove QUEUE_FLAG_DEAD
  block: stop setting the nomerges flags in blk_cleanup_queue
  block: simplify disk shutdown
  scsi: core: Fix a use-after-free
  drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES
  USB: core: Fix RST error in hub.c
  USB: serial: option: add Quectel BG95 0x0203 composition
  USB: serial: option: add Quectel RM520N
  ALSA: core: Fix double-free at snd_card_new()
  ALSA: hda/tegra: set depop delay for tegra
  ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation
  ALSA: hda: Fix Nvidia dp infoframe
  ALSA: hda: add Intel 5 Series / 3400 PCI DID
  ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
  ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5570 laptop
  ALSA: hda/realtek: Re-arrange quirk table entries
  ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
  ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
  ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
  ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
  ALSA: hda/realtek: Add a quirk for HP OMEN 16 (8902) mute LED
  iommu/vt-d: Check correct capability for sagaw determination
  exfat: fix overflow for large capacity partition
  btrfs: fix hang during unmount when stopping block group reclaim worker
  btrfs: fix hang during unmount when stopping a space reclaim worker
  btrfs: zoned: wait for extent buffer IOs before finishing a zone
  libperf evlist: Fix polling of system-wide events
  media: flexcop-usb: fix endpoint type check
  usb: dwc3: core: leave default DMA if the controller does not support 64-bit 
DMA
  thunderbolt: Add support for Intel Maple Ridge single port controller
  efi: x86: Wipe setup_data on pure EFI boot
  efi: libstub: check Shim mode using MokSBStateRT
  wifi: mt76: fix reading current per-tid starting sequence number for 
aggregation
  gpio: mockup: fix NULL pointer dereference when removing debugfs
  gpio: mockup: Fix potential resource leakage when register a chip
  gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
  riscv: fix a nasty sigreturn bug...
  riscv: fix RISCV_ISA_SVPBMT kconfig dependency warning
  drm/i915/gem: Flush contexts on driver release
  drm/i915/gem: Really move i915_gem_context.link under ref protection
  xen/xenbus: fix xenbus_setup_ring()
  kasan: call kasan_malloc() from __kmalloc_*track_caller()
  can: flexcan: flexcan_mailbox_read() fix return value for drop = true
  net: mana: Add rmb after checking owner bits
  mm/slub: fix to return errno if kmalloc() fails
  mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.
  KVM: x86: Reinstate kvm_vcpu_arch.guest_supported_xcr0
  KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES
  KVM: x86: Inject #UD on emulated XSETBV if XSAVES isn't enabled
  perf/arm-cmn: Add more bits to child node address offset field
  arm64: topology: fix possible overflow in amu_fie_setup()
  vmlinux.lds.h: CFI: Reduce alignment of jump-table to function alignment
  batman-adv: Fix hang up with small MTU hard-interface
  firmware: arm_scmi: Harden accesses to 

[Kernel-packages] [Bug 1994076] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994076

Title:
  Kinetic update: v5.19.14 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.14 upstream stable release
     from git://git.kernel.org/

  riscv: make t-head erratas depend on MMU
  tools/perf: Fix out of bound access to cpu mask array
  perf record: Fix cpu mask bit setting for mixed mmaps
  counter: 104-quad-8: Utilize iomap interface
  counter: 104-quad-8: Implement and utilize register structures
  counter: 104-quad-8: Fix skipped IRQ lines during events configuration
  uas: add no-uas quirk for Hiksemi usb_disk
  usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
  uas: ignore UAS for Thinkplus chips
  usb: typec: ucsi: Remove incorrect warning
  thunderbolt: Explicitly reset plug events delay back to USB4 spec value
  net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
  Input: snvs_pwrkey - fix SNVS_HPVIDR1 register address
  can: c_can: don't cache TX messages for C_CAN cores
  clk: ingenic-tcu: Properly enable registers before accessing timers
  wifi: mac80211: ensure vif queues are operational after start
  x86/sgx: Do not fail on incomplete sanitization on premature stop of ksgxd
  frontswap: don't call ->init if no ops are registered
  ARM: dts: integrator: Tag PCI host with device_type
  ntfs: fix BUG_ON in ntfs_lookup_inode_by_name()
  x86/uaccess: avoid check_object_size() in copy_from_user_nmi()
  mm/damon/dbgfs: fix memory leak when using debugfs_lookup()
  net: mt7531: only do PLL once after the reset
  Revert "firmware: arm_scmi: Add clock management to the SCMI power domain"
  powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush
  drm/i915/gt: Restrict forced preemption to the active context
  drm/amdgpu: Add amdgpu suspend-resume code path under SRIOV
  vduse: prevent uninitialized memory accesses
  libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205
  mm: fix BUG splat with kvmalloc + GFP_ATOMIC
  mptcp: factor out __mptcp_close() without socket lock
  mptcp: fix unreleased socket in accept queue
  mmc: moxart: fix 4-bit bus width and remove 8-bit bus width
  mmc: hsq: Fix data stomping during mmc recovery
  mm: gup: fix the fast GUP race against THP collapse
  mm/page_alloc: fix race condition between build_all_zonelists and page 
allocation
  mm: prevent page_frag_alloc() from corrupting the memory
  mm/page_isolation: fix isolate_single_pageblock() isolation behavior
  mm: fix dereferencing possible ERR_PTR
  mm/migrate_device.c: flush TLB while holding PTL
  mm/migrate_device.c: add missing flush_cache_page()
  mm/migrate_device.c: copy pte dirty bit to page
  mm: fix madivse_pageout mishandling on non-LRU page
  mm: bring back update_mmu_cache() to finish_fault()
  mm/hugetlb: correct demote page offset logic
  mm,hwpoison: check mm when killing accessing process
  media: dvb_vb2: fix possible out of bound access
  media: rkvdec: Disable H.264 error detection
  media: mediatek: vcodec: Drop platform_get_resource(IORESOURCE_IRQ)
  media: v4l2-compat-ioctl32.c: zero buffer passed to 
v4l2_compat_get_array_args()
  ARM: dts: am33xx: Fix MMCHS0 dma properties
  reset: imx7: Fix the iMX8MP PCIe PHY PERST support
  ARM: dts: am5748: keep usb4_tm disabled
  soc: sunxi: sram: Actually claim SRAM regions
  soc: sunxi: sram: Prevent the driver from being unbound
  soc: sunxi: sram: Fix probe function ordering issues
  soc: sunxi: sram: Fix debugfs info for A64 SRAM C
  ASoC: imx-card: Fix refcount issue with of_node_put
  clk: microchip: mpfs: fix clk_cfg array bounds violation
  clk: microchip: mpfs: make the rtc's ahb clock critical
  arm64: dts: qcom: sm8350: fix UFS PHY serdes size
  ASoC: tas2770: Reinit regcache on reset
  drm/bridge: lt8912b: add vsync hsync
  drm/bridge: lt8912b: set hdmi or dvi mode
  drm/bridge: lt8912b: fix 

[Kernel-packages] [Bug 1994078] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994078

Title:
  Kinetic update: v5.19.15 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.15 upstream stable release
     from git://git.kernel.org/

  sparc: Unbreak the build
  Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
  UBUNTU: [Config] updateconfigs for CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER
  hardening: Remove Clang's enable flag for -ftrivial-auto-var-init=zero
  docs: update mediator information in CoC docs
  xsk: Inherit need_wakeup flag for shared sockets
  firmware: arm_scmi: Improve checks in the info_get operations
  firmware: arm_scmi: Harden accesses to the sensor domains
  firmware: arm_scmi: Add SCMI PM driver remove routine
  arm64: dts: rockchip: fix upper usb port on BPI-R2-Pro
  dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
  dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
  dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API 
failure
  wifi: iwlwifi: don't spam logs with NSS>2 messages
  ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
  drm/amdgpu/mes: zero the sdma_hqd_mask of 2nd SDMA engine for SDMA 6.0.1
  scsi: qedf: Fix a UAF bug in __qedf_probe()
  net/ieee802154: fix uninit value bug in dgram_sendmsg
  net: marvell: prestera: add support for for Aldrin2
  ALSA: hda/hdmi: Fix the converter reuse for the silent stream
  um: Cleanup syscall_handler_t cast in syscalls_32.h
  um: Cleanup compiler warning in arch/x86/um/tls_32.c
  gpio: ftgpio010: Make irqchip immutable
  arch: um: Mark the stack non-executable to fix a binutils warning
  net: atlantic: fix potential memory leak in aq_ndev_close()
  KVM: s390: Pass initialized arg even if unused
  drm/amd/display: Fix double cursor on non-video RGB MPO
  drm/amd/display: Assume an LTTPR is always present on fixed_vs links
  drm/amd/display: update gamut remap if plane has changed
  drm/amd/display: skip audio setup when audio stream is enabled
  drm/amd/display: Fix DP MST timeslot issue when fallback happened
  drm/amd/display: increase dcn315 pstate change latency
  perf/x86/intel: Fix unchecked MSR access error for Alder Lake N
  don't use __kernel_write() on kmap_local_page()
  i2c: davinci: fix PM disable depth imbalance in davinci_i2c_probe
  usb: mon: make mmapped memory read only
  USB: serial: ftdi_sio: fix 300 bps rate for SIO
  gpiolib: acpi: Add support to ignore programming an interrupt
  gpiolib: acpi: Add a quirk for Asus UM325UAZ
  mmc: core: Replace with already defined values for readability
  mmc: core: Terminate infinite loop in SD-UHS voltage switch
  rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
  bpf: Gate dynptr API behind CAP_BPF
  net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
  bpf: Fix resetting logic for unreferenced kptrs
  Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
  Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
  Linux 5.19.15
  UBUNTU: Upstream stable to v5.19.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994078/+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

[Kernel-packages] [Bug 1994179] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994179

Title:
  Kinetic update: v5.19.17 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.17 upstream stable release
     from git://git.kernel.org/

  Revert "fs: check FMODE_LSEEK to control internal pipe splicing"
  ALSA: oss: Fix potential deadlock at unregistration
  ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free()
  ALSA: usb-audio: Fix potential memory leaks
  ALSA: usb-audio: Fix NULL dererence at error path
  ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530
  ALSA: hda/realtek: Correct pin configs for ASUS G533Z
  ALSA: hda/realtek: Add quirk for ASUS GV601R laptop
  ALSA: hda/realtek: Add Intel Reference SSID to support headset keys
  mtd: rawnand: atmel: Unmap streaming DMA mappings
  io_uring/rw: fix unexpected link breakage
  io_uring/net: fix fast_iov assignment in io_setup_async_msg()
  io_uring/net: don't update msg_name if not provided
  io_uring: correct pinned_vm accounting
  hv_netvsc: Fix race between VF offering and VF association message from host
  cifs: destage dirty pages before re-reading them for cache=none
  cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message
  iio: dac: ad5593r: Fix i2c read protocol requirements
  iio: ltc2497: Fix reading conversion results
  iio: adc: ad7923: fix channel readings for some variants
  iio: pressure: dps310: Refactor startup procedure
  iio: pressure: dps310: Reset chip after timeout
  xhci: dbc: Fix memory leak in xhci_alloc_dbc()
  usb: gadget: uvc: Fix argument to sizeof() in uvc_register_video()
  usb: add quirks for Lenovo OneLink+ Dock
  mmc: core: Add SD card quirk for broken discard
  can: kvaser_usb: Fix use of uninitialized completion
  can: kvaser_usb_leaf: Fix overread with an invalid command
  can: kvaser_usb_leaf: Fix TX queue out of sync after restart
  can: kvaser_usb_leaf: Fix CAN state after restart
  mmc: renesas_sdhi: Fix rounding errors
  mmc: sdhci-tegra: Use actual clock rate for SW tuning correction
  mmc: sdhci-sprd: Fix minimum clock limit
  i2c: designware: Fix handling of real but unexpected device interrupts
  fs: dlm: fix race between test_bit() and queue_work()
  fs: dlm: handle -EBUSY first in lock arg validation
  fs: dlm: fix invalid derefence of sb_lvbptr
  btf: Export bpf_dynptr definition
  HID: multitouch: Add memory barriers
  quota: Check next/prev free block number after reading from quota file
  platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure
  arm64: dts: qcom: sdm845-mtp: correct ADC settle time
  ASoC: wcd9335: fix order of Slimbus unprepare/disable
  ASoC: wcd934x: fix order of Slimbus unprepare/disable
  hwmon: (gsc-hwmon) Call of_node_get() before of_find_xxx API
  net: thunderbolt: Enable DMA paths only after rings are enabled
  regulator: qcom_rpm: Fix circular deferral regression
  arm64: topology: move store_cpu_topology() to shared code
  riscv: topology: fix default topology reporting
  RISC-V: Re-enable counter access from userspace
  RISC-V: Make port I/O string accessors actually work
  parisc: fbdev/stifb: Align graphics memory size to 4MB
  parisc: Fix userspace graphics card breakage due to pgtable special bit
  riscv: vdso: fix NULL deference in vdso_join_timens() when vfork
  riscv: Make VM_WRITE imply VM_READ
  riscv: always honor the CONFIG_CMDLINE_FORCE when parsing dtb
  riscv: Pass -mno-relax only on lld < 15.0.0
  UM: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
  nvmem: core: Fix memleak in nvmem_register()
  nvme-multipath: fix possible hang in live ns resize with ANA access
  dmaengine: mxs: use platform_driver_register
  dmaengine: qcom-adm: fix wrong sizeof config in slave_config
  dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg
  drm/virtio: Check whether transferred 2D BO is shmem
  

[Kernel-packages] [Bug 1994164] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1994164

Title:
  Kinetic update: v5.19.16 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.16 upstream stable release
     from git://git.kernel.org/

  nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
  nilfs2: fix use-after-free bug of struct nilfs_root
  nilfs2: fix leak of nilfs_root in case of writer thread creation failure
  nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
  ceph: don't truncate file in atomic_open
  nvme-pci: set min_align_mask before calculating max_hw_sectors
  random: restore O_NONBLOCK support
  random: clamp credited irq bits to maximum mixed
  ALSA: hda: Fix position reporting on Poulsbo
  ALSA: hda/realtek: Add quirk for HP Zbook Firefly 14 G9 model
  efi: Correct Macmini DMI match in uefi cert quirk
  USB: serial: qcserial: add new usb-id for Dell branded EM7455
  Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG -> 
peripheral if extcon is present""
  Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is present"
  Revert "powerpc/rtas: Implement reentrant rtas call"
  Revert "crypto: qat - reduce size of mapped region"
  random: avoid reading two cache lines on irq randomness
  random: use expired timer rather than wq for mixing fast pool
  mctp: prevent double key removal and unref
  Input: xpad - add supported devices as contributed on github
  Input: xpad - fix wireless 360 controller breaking after suspend
  misc: pci_endpoint_test: Aggregate params checking for xfer
  misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
  Linux 5.19.16
  UBUNTU: Upstream stable to v5.19.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994164/+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

[Kernel-packages] [Bug 1996540] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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.

-- 
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/1996540

Title:
  Kinetic update: upstream stable patchset 2022-11-14

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-11-14

  Ported from the following upstream stable releases:
  v5.15.74, v6.0.2
  v5.15.75, v6.0.3
v6.0.4

     from git://git.kernel.org/

  scsi: qla2xxx: Fix response queue handler reading stale packets
  UBUNTU: Upstream stable to v5.15.74, v6.0.2
  rcu-tasks: Convert RCU_LOCKDEP_WARN() to WARN_ONCE()
  mmc: sdhci-msm: add compatible string check for sdm670
  thermal: intel_powerclamp: Use first online CPU as control_cpu
  gcov: support GCC 12.1 and newer compilers
  io-wq: Fix memory leak in worker creation
  arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored
  serial: Deassert Transmit Enable on probe in driver-specific way
  KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1)
  drm/amd/display: Enable dpia support for dcn314
  drm/amdgpu: Enable F32_WPTR_POLL_ENABLE in mqd
  libbpf: Initialize err in probe_map_create
  libbpf: Fix crash if SEC("freplace") programs don't have attach_prog_fd set
  libbpf: Fix NULL pointer exception in API btf_dump__dump_type_data
  drm/vc4: drv: Call component_unbind_all()
  video/aperture: Disable and unregister sysfb devices via aperture helpers
  drm/bridge: anx7625: Fix refcount bug in anx7625_parse_dt()
  drm/i915/dg2: Bump up CDCLK for DG2
  drm/panel: use 'select' for Ili9341 panel driver helpers
  drm: fix drm_mipi_dbi build errors
  ALSA: hda/hdmi: change type for the 'assigned' variable
  ALSA: hda/hdmi: Fix the converter allocation for the silent stream
  arm64: dts: qcom: sc7280: Cleanup the lpasscc node
  arm64: dts: qcom: sc7280: Update lpasscore node
  arm64: dts: qcom: pm8350c: Drop PWM reg declaration
  arm64: dts: qcom: sc7180-trogdor: Keep pm6150_adc enabled for TZ
  arm64: dts: qcom: sm8350-sagami: correct TS pin property
  soc/tegra: fuse: Add missing of_node_put() in tegra_init_fuse()
  arm64: dts: qcom: ipq8074: fix PCIe PHY serdes size
  arm64: dts: qcom: sm8450: fix UFS PHY serdes size
  arm64: dts: exynos: fix polarity of "enable" line of NFC chip in TM2
  selftests/cpu-hotplug: Use return instead of exit
  selftests/cpu-hotplug: Delete fault injection related code
  selftests/cpu-hotplug: Reserve one cpu online at least
  usb: common: usb-conn-gpio: Simplify some error message
  HID: uclogic: Fix warning in uclogic_rdesc_template_apply
  tty: xilinx_uartps: Check clk_enable return value
  fpga: dfl-pci: Add IDs for Intel N6000, N6001 and C6100 cards
  iio: Use per-device lockdep class for mlock
  scsi: lpfc: Fix various issues reported by tools
  phy: qcom-qmp-usb: disable runtime PM on unbind
  block: Fix the enum blk_eh_timer_return documentation
  RDMA/rxe: Set pd early in mr alloc routines
  clk: imx8mp: tune the order of enet_qos_root_clk
  libbpf: Ensure functions with always_inline attribute are inline
  libbpf: Do not require executable permission for shared libraries
  micrel: ksz8851: fixes struct pointer issue
  net: ftmac100: fix endianness-related issues from 'sparse'
  net: sched: cls_u32: Avoid memcpy() false-positive warning
  libbpf: Fix overrun in netlink attribute iteration
  ALSA: usb-audio: Add quirk to enable Avid Mbox 3 support
  ASoC: sunxi: sun4i-codec: set debugfs_prefix for CPU DAI component
  ASoC: amd: yc: Add ASUS UM5302TA into DMI table
  ASoC: amd: yc: Add Lenovo Yoga Slim 7 Pro X to quirks table
  arm64: dts: qcom: sc7280-idp: correct ADC channel node name and unit address
  ARM: orion: fix include path
  hid: topre: Add driver fixing report descriptor
  UBUNTU: [Config] updateconfigs for HID_TOPRE
  fsi: master-ast-cf: Fix missing of_node_put in 

[Kernel-packages] [Bug 1981968] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for bcmwl 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1981968

Title:
  bcmwl fails to build on the latest kinetic kernel 5.19

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Released
Status in bcmwl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  bcmwl fails to build on kernel 5.19 with the following errors:

  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14: 
error: implicit declaration of function ‘pci_alloc_consistent’; did you mean 
‘osl_dma_alloc_consistent’? [-Werror=implicit-function-declaration]
603 | va = pci_alloc_consistent(osh->pdev, size, (dma_addr_t*)pap);
|  ^~~~
|  osl_dma_alloc_consistent

  
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26: 
error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? 
[-Werror=implicit-function-declaration]
   3307 | wl_info_t * wl = PDE_DATA(file_inode(filp));
|  ^~~~
|  NODE_DATA

  
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_dma_map’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: 
error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean 
‘DMA_TO_DEVICE’?
626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|  ^~~~
|  DMA_TO_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: 
note: each undeclared identifier is reported only once for each function it 
appears in
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:56: 
error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you 
mean ‘DMA_FROM_DEVICE’?
626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|
^~
|DMA_FROM_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:659:17: 
error: implicit declaration of function ‘pci_map_single’; did you mean 
‘dma_map_single’? [-Werror=implicit-function-declaration]
659 | return (pci_map_single(osh->pdev, va, size, dir));
| ^~
| dma_map_single
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_dma_unmap’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:38: 
error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean 
‘DMA_TO_DEVICE’?
668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|  ^~~~
|  DMA_TO_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:56: 
error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you 
mean ‘DMA_FROM_DEVICE’?
668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|
^~
|DMA_FROM_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:669:9: 
error: implicit declaration of function ‘pci_unmap_single’; did you mean 
‘dma_unmap_single’? [-Werror=implicit-function-declaration]
669 | pci_unmap_single(osh->pdev, (uint32)pa, size, dir);
| ^~~~
| dma_unmap_single

  
  [Test case]

  $ sudo apt install bcmwl-kernel-source

  [Fix]

  Patch bcmwl to support the new 5.18+ kernel ABI (PCI/DMA-related
  functions).

  [Regression potential]

  We may experience regressions with bcmwl in kernels >= 5.18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1998039] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for bcmwl 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1998039

Title:
  Network Freeze With Broadcom DKMS Wireless Driver

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  Fix Released

Bug description:
  Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
  Ubuntu Release: 22.10
  Kernel: 5.19.0-23-generic

  Symptoms:
  Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly 
related to suspend/resume).

  This has been fixed in Arch and Debian already [1].

  $ lsmod | grep wl
  wl   6467584  0
  cfg80211 1040384  1 wl

  $ dpkg -l | grep -i broadcom
  ii  bcmwl-kernel-source  
6.30.223.271+bdcom-0ubuntu9  amd64Broadcom 802.11 Linux STA 
wireless driver source

  Test Case:
  ==
  This is reproducible by forcing the computer to sleep and then waking it back 
up.

  Regression Potential:
  =
  Since this is due to an intentional ABI change in the upstream kernel, 
regression potential is low.

  [1] https://salsa.debian.org/diegoe/broadcom-
  sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+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

[Kernel-packages] [Bug 1999009] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for bcmwl 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1999009

Title:
  bcmwl: properly support linux 6.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  Fix Released
Status in bcmwl source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar.

  Moreover, with kernels >= 5.17 there's an incorrect access to struct
  netdev (see LP: #1998039).

  [Test case]

  $ sudo apt install bcmwl-kernel-source

  [Fix]

  The following upstream commits have change the cfg80211 ABI in linux
  >= 6.1:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=efbabc11650040c64884ff3019b88c7bcc0ceb1d
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7a7b84e33178db4a839c5e1773247be17597c1f

  Change bcmwl to properly support the new ABI changes.

  Moreover, to fix the incorrect netdev access with kernels >= 5.17 we
  can apply this patch
  https://raw.githubusercontent.com/archlinux/svntogit-
  community/master/broadcom-wl-dkms/trunk/012-linux517.patch (see LP:
  #1998039 - thanks to Brett Holman for the backport and for reporting
  the problem).

  [Regression potential]

  We may experience regressions with kernels >= 6.1 using the bcmwl-
  kernel-source dkms. The code for the previous kernels remains
  unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+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

[Kernel-packages] [Bug 1980484] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for v4l2loopback 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.

-- 
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/1980484

Title:
  temporarily disable CONFIG_X86_KERNEL_IBT

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2loopback source package in Jammy:
  Fix Released
Status in backport-iwlwifi-dkms source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in v4l2loopback source package in Kinetic:
  Fix Released

Bug description:
  Enabling IBT in the kernel is going to be problematic at the moment,
  because dkms' that have a precompiled binary need to be linked against
  non-IBT kernels and IBT kernels (see nvidia drivers for example).

  For this reason it's safer to keep IBT disabled at the moment, until
  all the kernels will have IBT enabled and the kernel modules /
  binaries will use the proper flags to generate IBT-compliant binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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

[Kernel-packages] [Bug 2003174] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for zfs-linux 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2003174

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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

[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

[Łukasz Zemczak]

Can someone upload this to kinetic then? Basing on xnox's comment on #5.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2002636

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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

[Kernel-packages] [Bug 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted zfs-linux into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.1.5-1ubuntu6~22.04.1 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.

** Changed in: zfs-linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2003174

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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

[Kernel-packages] [Bug 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19

[Łukasz Zemczak]

Thank you Dimitri! If these will be run for the package in -proposed as
part of the validation, I'll accept the new upload from the Rejected
queue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2003174

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  In Progress

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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

[Kernel-packages] [Bug 2001896] Update Released

[Łukasz Zemczak]

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2001896

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2001896/+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

[Kernel-packages] [Bug 2002373] Update Released

[Łukasz Zemczak]

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2002373

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002373/+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

[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes

[Łukasz Zemczak]

Dimitri thank you for the upload! I'd like to accept it soonish, but
since this SRU bug is missing the usual Test Case, Impact and Regression
Potential, could you fill that up before I accept it? I'd like to know
more about the fix that you performed, what it changes and what could go
wrong with it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993318

Title:
  ZFS + Encryption installations of Ubuntu Desktop do not come up
  correctly on first boot, systemd unmounts many of the zfs volumes

Status in Ubuntu Manual Tests:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zsys package in Ubuntu:
  Invalid

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM,
  50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Install Ubuntu" and proceed with the installation process.
  3. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  4. Proceed with the rest of the installation as normal.
  5. Reboot into the newly installed system.
  6. Log in.
  7. Run "sudo apt update" in a terminal.

  Expected result: The package database should be updated normally.

  Actual result: You are presented with the following errors at the end
  of the apt output:

  Reading package lists... Error!
  E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or 
directory)
  E: Could not open file  - open (2: No such file or directory)
  E: Problem opening 
  E: The package lists or status file could not be parsed or opened.

  
  Notes: Switching to a TTY will print a crash error message related to the 
same missing /var/lib/dpkg/status file. Running "sudo touch 
/var/lib/dpkg/status" will allow "sudo apt update" to function and fix the 
crashed process in the TTY.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages was related to
  update-manager in my experience, and another one was from "check-new-
  release-gtk".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 09:55:27 2022
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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

[Kernel-packages] [Bug 2002636] Please test proposed package

[Łukasz Zemczak]

Hello Paolo, or anyone else affected,

Accepted broadcom-sta into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/broadcom-
sta/6.30.223.271-23~22.04.1 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2002636

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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

[Kernel-packages] [Bug 2003174] Proposed package upload rejected

[Łukasz Zemczak]

An upload of zfs-linux to jammy-proposed has been rejected from the
upload queue for the following reason: "Please see
https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2003174/comments/3 for the rationale.".

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2003174

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  In Progress

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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

[Kernel-packages] [Bug 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19

[Łukasz Zemczak]

I don't feel comfortable accepting this SRU in the current form. I'm
happy to hear that there's 'no significant ABI changes' in this version,
but basically doing a new upstream release with a diff of 556 files
changed, 48365 insertions(+), 23626 deletions(-) with only "$ sudo apt
install zfs-dkms" as the test case is not acceptable.

This should ideally be a cherry-picked fix. Will reject it for now.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2003174

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  In Progress

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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

[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

[Łukasz Zemczak]

Also: I assume there are no plans/needs to have this in kinetic? Only
asking because now jammy version > kinetic version, which is never
ideal.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2002636

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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

[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

[Łukasz Zemczak]

I'll accept this this time as the changes feel sane, but please be sure
not to include patches without any description in uploads that are later
pushed as SRUs to stable series.

** Changed in: broadcom-sta (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2002636

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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

[Kernel-packages] [Bug 2003332] Re: jammy linux-riscv-5.19 promote from universe to main

[Łukasz Zemczak]

Both should now be in main.

** Changed in: linux-meta-riscv-5.19 (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: linux-riscv-5.19 (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2003332

Title:
  jammy linux-riscv-5.19 promote from universe to main

Status in linux-meta-riscv-5.19 package in Ubuntu:
  Fix Committed
Status in linux-riscv-5.19 package in Ubuntu:
  Fix Committed

Bug description:
  jammy linux-riscv-5.19 promote from universe to main

  new kernel published in the wrong component.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv-5.19/+bug/2003332/+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

[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler

[Łukasz Zemczak]

Hello Dimitri, or anyone else affected,

Accepted v4l2loopback into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/v4l2loopback/0.12.7-2ubuntu2~22.04.1
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.

** Changed in: v4l2loopback (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991664

Title:
  backport dkms fixes to build modules correctly for hwe-5.19+ kernels
  with custom compiler

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in ipu6-drivers package in Ubuntu:
  New
Status in ivsc-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in backport-iwlwifi-dkms source package in Jammy:
  New
Status in dkms source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Jammy:
  New
Status in ivsc-driver source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in v4l2loopback source package in Jammy:
  Fix Committed
Status in zfs-linux source package in Jammy:
  New

Bug description:
  [ Impact ]

   * hwe-5.19 kernel has to be compiled with gcc-12+ for the new
  security kernel config options that have been enabled in that kernel
  (init zero structs).

   * dkms needs to be patched to attempt to use the same compiler as was
  used to build the kernel, specifically use gcc for v5.15 but gcc-12
  for v5.19+ in jammy

   * dkms autopkgtests also need to be improved to ensure there are no
  false negatives when kernel has module under test already built-in at
  the same version.

   * because linux-headers packages in Ubuntu do not depend on a
  toolchain, and it is very hard to correctly depend on a native or
  cross-toolchain, add gcc-12 dependency in the dkms package.

  [ Test Plan ]

   * Retrigger dkms module test for a built-in package of the same
  version as already built into the kernel, for example zfs-linux dkms.
  It should pass.

   * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel
  from proposed. dkms module should be built with gcc and gcc-12
  respectively.

  [ Where problems could occur ]

   * New gcc-12 dependency on the dkms package may result in two
  compilers being installed in the Ubuntu Desktop Live image

   * New gcc-12 dependency may prevent automatic upgrade/installation of
  the dkms package update via unattended upgrades.

  [ Other Info ]

   * It is questionable for dkms to depend on any c-compiler, given that
  a module for a given kernel can really be built with the same
  toolchain and the same compiler features.

   * In debian, linux kernel packages ship and extra configuration file
  in the kernel headers, dkms uses said configuration file to use a
  matching compiler, and linux-headers packages depend on the toolchain
  used to build a given kernel. Maybe in the future Ubuntu could
  consider using the same packaging.

   * Some DKMS modules need further fixes to preserve and not loose the
  compiler setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+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

[Kernel-packages] [Bug 1980484] Please test proposed package

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted v4l2loopback into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/v4l2loopback/0.12.7-2ubuntu2~22.04.1
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.

-- 
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/1980484

Title:
  temporarily disable CONFIG_X86_KERNEL_IBT

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2loopback source package in Jammy:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in v4l2loopback source package in Kinetic:
  Fix Released

Bug description:
  Enabling IBT in the kernel is going to be problematic at the moment,
  because dkms' that have a precompiled binary need to be linked against
  non-IBT kernels and IBT kernels (see nvidia drivers for example).

  For this reason it's safer to keep IBT disabled at the moment, until
  all the kernels will have IBT enabled and the kernel modules /
  binaries will use the proper flags to generate IBT-compliant binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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

[Kernel-packages] [Bug 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT

[Łukasz Zemczak]

Can we please get a test case for this one, since we'll be getting this
into jammy-proposed as an SRU?

** Changed in: v4l2loopback (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
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/1980484

Title:
  temporarily disable CONFIG_X86_KERNEL_IBT

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2loopback source package in Jammy:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in v4l2loopback source package in Kinetic:
  Fix Released

Bug description:
  Enabling IBT in the kernel is going to be problematic at the moment,
  because dkms' that have a precompiled binary need to be linked against
  non-IBT kernels and IBT kernels (see nvidia drivers for example).

  For this reason it's safer to keep IBT disabled at the moment, until
  all the kernels will have IBT enabled and the kernel modules /
  binaries will use the proper flags to generate IBT-compliant binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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

[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver

[Łukasz Zemczak]

Hello Brett, or anyone else affected,

Accepted bcmwl into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu10~22.10.1
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.

** Changed in: bcmwl (Ubuntu Kinetic)
   Status: New => Fix Committed

** Tags added: verification-needed-kinetic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1998039

Title:
  Network Freeze With Broadcom DKMS Wireless Driver

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  Fix Committed

Bug description:
  Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
  Ubuntu Release: 22.10
  Kernel: 5.19.0-23-generic

  Symptoms:
  Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly 
related to suspend/resume).

  A search found a related issue[1].

  $ lsmod | grep wl
  wl   6467584  0
  cfg80211 1040384  1 wl

  $ dpkg -l | grep -i broadcom
  ii  bcmwl-kernel-source  
6.30.223.271+bdcom-0ubuntu9  amd64Broadcom 802.11 Linux STA 
wireless driver source

  [1] https://salsa.debian.org/diegoe/broadcom-
  sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+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

[Kernel-packages] [Bug 1999009] Re: bcmwl: properly support linux 6.1

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted bcmwl into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu10~22.10.1
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.

** Changed in: bcmwl (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-kinetic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1999009

Title:
  bcmwl: properly support linux 6.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  Fix Committed
Status in bcmwl source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar.

  Moreover, with kernels >= 5.17 there's an incorrect access to struct
  netdev (see LP: #1998039).

  [Test case]

  $ sudo apt install bcmwl-kernel-source

  [Fix]

  The following upstream commits have change the cfg80211 ABI in linux
  >= 6.1:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=efbabc11650040c64884ff3019b88c7bcc0ceb1d
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7a7b84e33178db4a839c5e1773247be17597c1f

  Change bcmwl to properly support the new ABI changes.

  Moreover, to fix the incorrect netdev access with kernels >= 5.17 we
  can apply this patch
  https://raw.githubusercontent.com/archlinux/svntogit-
  community/master/broadcom-wl-dkms/trunk/012-linux517.patch (see LP:
  #1998039 - thanks to Brett Holman for the backport and for reporting
  the problem).

  [Regression potential]

  We may experience regressions with kernels >= 6.1 using the bcmwl-
  kernel-source dkms. The code for the previous kernels remains
  unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+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

[Kernel-packages] [Bug 1981968] Re: bcmwl fails to build on the latest kinetic kernel 5.19

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted bcmwl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu10~22.04.1
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.

** Changed in: bcmwl (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1981968

Title:
  bcmwl fails to build on the latest kinetic kernel 5.19

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  bcmwl fails to build on kernel 5.19 with the following errors:

  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14: 
error: implicit declaration of function ‘pci_alloc_consistent’; did you mean 
‘osl_dma_alloc_consistent’? [-Werror=implicit-function-declaration]
603 | va = pci_alloc_consistent(osh->pdev, size, (dma_addr_t*)pap);
|  ^~~~
|  osl_dma_alloc_consistent

  
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26: 
error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? 
[-Werror=implicit-function-declaration]
   3307 | wl_info_t * wl = PDE_DATA(file_inode(filp));
|  ^~~~
|  NODE_DATA

  
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_dma_map’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: 
error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean 
‘DMA_TO_DEVICE’?
626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|  ^~~~
|  DMA_TO_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:38: 
note: each undeclared identifier is reported only once for each function it 
appears in
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:626:56: 
error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you 
mean ‘DMA_FROM_DEVICE’?
626 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|
^~
|DMA_FROM_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:659:17: 
error: implicit declaration of function ‘pci_map_single’; did you mean 
‘dma_map_single’? [-Werror=implicit-function-declaration]
659 | return (pci_map_single(osh->pdev, va, size, dir));
| ^~
| dma_map_single
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_dma_unmap’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:38: 
error: ‘PCI_DMA_TODEVICE’ undeclared (first use in this function); did you mean 
‘DMA_TO_DEVICE’?
668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|  ^~~~
|  DMA_TO_DEVICE
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:668:56: 
error: ‘PCI_DMA_FROMDEVICE’ undeclared (first use in this function); did you 
mean ‘DMA_FROM_DEVICE’?
668 | dir = (direction == DMA_TX)? PCI_DMA_TODEVICE: 
PCI_DMA_FROMDEVICE;
|
^~
| 

[Kernel-packages] [Bug 1998039] Please test proposed package

[Łukasz Zemczak]

Hello Brett, or anyone else affected,

Accepted bcmwl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu10~22.04.1
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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1998039

Title:
  Network Freeze With Broadcom DKMS Wireless Driver

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  Fix Committed

Bug description:
  Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
  Ubuntu Release: 22.10
  Kernel: 5.19.0-23-generic

  Symptoms:
  Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly 
related to suspend/resume).

  A search found a related issue[1].

  $ lsmod | grep wl
  wl   6467584  0
  cfg80211 1040384  1 wl

  $ dpkg -l | grep -i broadcom
  ii  bcmwl-kernel-source  
6.30.223.271+bdcom-0ubuntu9  amd64Broadcom 802.11 Linux STA 
wireless driver source

  [1] https://salsa.debian.org/diegoe/broadcom-
  sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+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

[Kernel-packages] [Bug 1999009] Re: bcmwl: properly support linux 6.1

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted bcmwl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu10~22.04.1
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.

** Changed in: bcmwl (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1999009

Title:
  bcmwl: properly support linux 6.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed
Status in bcmwl source package in Kinetic:
  In Progress
Status in bcmwl source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar.

  Moreover, with kernels >= 5.17 there's an incorrect access to struct
  netdev (see LP: #1998039).

  [Test case]

  $ sudo apt install bcmwl-kernel-source

  [Fix]

  The following upstream commits have change the cfg80211 ABI in linux
  >= 6.1:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=efbabc11650040c64884ff3019b88c7bcc0ceb1d
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7a7b84e33178db4a839c5e1773247be17597c1f

  Change bcmwl to properly support the new ABI changes.

  Moreover, to fix the incorrect netdev access with kernels >= 5.17 we
  can apply this patch
  https://raw.githubusercontent.com/archlinux/svntogit-
  community/master/broadcom-wl-dkms/trunk/012-linux517.patch (see LP:
  #1998039 - thanks to Brett Holman for the backport and for reporting
  the problem).

  [Regression potential]

  We may experience regressions with kernels >= 6.1 using the bcmwl-
  kernel-source dkms. The code for the previous kernels remains
  unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+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

[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver

[Łukasz Zemczak]

Can we get the description updated with a test case and some regression
potential? Thank you.

** Changed in: bcmwl (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1998039

Title:
  Network Freeze With Broadcom DKMS Wireless Driver

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Jammy:
  Fix Committed

Bug description:
  Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
  Ubuntu Release: 22.10
  Kernel: 5.19.0-23-generic

  Symptoms:
  Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly 
related to suspend/resume).

  A search found a related issue[1].

  $ lsmod | grep wl
  wl   6467584  0
  cfg80211 1040384  1 wl

  $ dpkg -l | grep -i broadcom
  ii  bcmwl-kernel-source  
6.30.223.271+bdcom-0ubuntu9  amd64Broadcom 802.11 Linux STA 
wireless driver source

  [1] https://salsa.debian.org/diegoe/broadcom-
  sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+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

[Kernel-packages] [Bug 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2

[Łukasz Zemczak]

Hey, is there anything that needs to be fixed for gcc-12 here? Or was
this kernel specific? Can someone confirm?

** Changed in: gcc-12 (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/1993120

Title:
  armhf kernel compiled with gcc-12 fails to boot on pi 3/2

Status in gcc-12 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in gcc-12 source package in Kinetic:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-raspi source package in Kinetic:
  Invalid

Bug description:
  Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang
  on Pi 3 and 2. Seems to work fine on Pi 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+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

[Kernel-packages] [Bug 1991664] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for dkms 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991664

Title:
  backport dkms fixes to build modules correctly for hwe-5.19+ kernels
  with custom compiler

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in backport-iwlwifi-dkms source package in Jammy:
  New
Status in dkms source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Incomplete
Status in v4l2loopback source package in Jammy:
  New
Status in zfs-linux source package in Jammy:
  New

Bug description:
  [ Impact ]

   * hwe-5.19 kernel has to be compiled with gcc-12+ for the new
  security kernel config options that have been enabled in that kernel
  (init zero structs).

   * dkms needs to be patched to attempt to use the same compiler as was
  used to build the kernel, specifically use gcc for v5.15 but gcc-12
  for v5.19+ in jammy

   * dkms autopkgtests also need to be improved to ensure there are no
  false negatives when kernel has module under test already built-in at
  the same version.

   * because linux-headers packages in Ubuntu do not depend on a
  toolchain, and it is very hard to correctly depend on a native or
  cross-toolchain, add gcc-12 dependency in the dkms package.

  [ Test Plan ]

   * Retrigger dkms module test for a built-in package of the same
  version as already built into the kernel, for example zfs-linux dkms.
  It should pass.

   * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel
  from proposed. dkms module should be built with gcc and gcc-12
  respectively.

  [ Where problems could occur ]

   * New gcc-12 dependency on the dkms package may result in two
  compilers being installed in the Ubuntu Desktop Live image

   * New gcc-12 dependency may prevent automatic upgrade/installation of
  the dkms package update via unattended upgrades.

  [ Other Info ]

   * It is questionable for dkms to depend on any c-compiler, given that
  a module for a given kernel can really be built with the same
  toolchain and the same compiler features.

   * In debian, linux kernel packages ship and extra configuration file
  in the kernel headers, dkms uses said configuration file to use a
  matching compiler, and linux-headers packages depend on the toolchain
  used to build a given kernel. Maybe in the future Ubuntu could
  consider using the same packaging.

   * Some DKMS modules need further fixes to preserve and not loose the
  compiler setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

[Łukasz Zemczak]

I know this is a bit of a special package, but please always include
more information about the verification. Since I had some verification
details for kinetic, but for jammy it was just a comment switching the
tags - please always give some context on which versions have been used
for verification etc.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1992714

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in firmware-sof source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Incomplete
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992714/+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

[Kernel-packages] [Bug 1992714] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for firmware-sof 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1992714

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in firmware-sof source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Incomplete
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992714/+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

[Kernel-packages] [Bug 1991725] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for dkms 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725

Title:
  fails to sign kernel modules

Status in Release Notes for Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  With the current state of the DKMS package, if a user attempts to
  install any package that includes a third-party driver (Broadcom WiFi,
  VirtualBox, v4l2loobpack, etc.), the process of signing the newly
  built driver with a MOK key will fail silently. This means that any
  packages and hardware that require third-party drivers are currently
  unusable on a system with Secure Boot. This bug has been tested and
  verified to occur with the bcmwl-kernel-source package, but also is
  very likely to affect any other packages that use DKMS modules.

  This fix for this is in the -proposed pocket at the moment, and has
  been tested to work.

  [Test plan]

  1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom 
WiFi is not an option, install VirtualBox in Step 9 rather than 
bcmwl-kernel-source.)
  2. Install Ubuntu on the system, but do not enable the installation of 
third-party drivers.
  3. When installation finishes, reboot.
  4. When the system boots into the Ubuntu desktop, connect to the Internet 
without WiFi, and update all packages on the system.
  5. Enable -proposed.
  6. Update *just* the DKMS package with "sudo apt install dkms".
  7. Disable -proposed.
  8. Run "sudo apt install bcmwl-kernel-source".
  9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should 
begin working once Ubuntu boots.

  [Where problems could occur]

  Theoretically, a bug in the code could result in DKMS drivers still
  not being signed in some instances (though there are no known
  instances where this happens). But as Secure Boot + DKMS is already
  entirely broken, even this kind of breakage would be an improvement
  beyond what we already have. Given the rather obvious nature of such
  breakage, thorough testing should be able to detect it with ease.

  ---

  Original bug reports:

  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

  ---

  dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve
  this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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

[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules

[Łukasz Zemczak]

@Gianfranco - this is why I added the verification-needed tags and was
poking Aaron on IRC because I wanted confirmation that this update is
verified. Previously I only got a written confirmation on IRC which I
wanted to have here as the papertrail (+ the other comments on the bug
were a bit confusing).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725

Title:
  fails to sign kernel modules

Status in Release Notes for Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  With the current state of the DKMS package, if a user attempts to
  install any package that includes a third-party driver (Broadcom WiFi,
  VirtualBox, v4l2loobpack, etc.), the process of signing the newly
  built driver with a MOK key will fail silently. This means that any
  packages and hardware that require third-party drivers are currently
  unusable on a system with Secure Boot. This bug has been tested and
  verified to occur with the bcmwl-kernel-source package, but also is
  very likely to affect any other packages that use DKMS modules.

  This fix for this is in the -proposed pocket at the moment, and has
  been tested to work.

  [Test plan]

  1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom 
WiFi is not an option, install VirtualBox in Step 9 rather than 
bcmwl-kernel-source.)
  2. Install Ubuntu on the system, but do not enable the installation of 
third-party drivers.
  3. When installation finishes, reboot.
  4. When the system boots into the Ubuntu desktop, connect to the Internet 
without WiFi, and update all packages on the system.
  5. Enable -proposed.
  6. Update *just* the DKMS package with "sudo apt install dkms".
  7. Disable -proposed.
  8. Run "sudo apt install bcmwl-kernel-source".
  9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should 
begin working once Ubuntu boots.

  [Where problems could occur]

  Theoretically, a bug in the code could result in DKMS drivers still
  not being signed in some instances (though there are no known
  instances where this happens). But as Secure Boot + DKMS is already
  entirely broken, even this kind of breakage would be an improvement
  beyond what we already have. Given the rather obvious nature of such
  breakage, thorough testing should be able to detect it with ease.

  ---

  Original bug reports:

  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

  ---

  dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve
  this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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

[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules

[Łukasz Zemczak]

Hello Mike, or anyone else affected,

Accepted dkms into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/3.0.6-2ubuntu2 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.

** Changed in: dkms (Ubuntu Kinetic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725

Title:
  fails to sign kernel modules

Status in Release Notes for Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  With the current state of the DKMS package, if a user attempts to
  install any package that includes a third-party driver (Broadcom WiFi,
  VirtualBox, v4l2loobpack, etc.), the process of signing the newly
  built driver with a MOK key will fail silently. This means that any
  packages and hardware that require third-party drivers are currently
  unusable on a system with Secure Boot. This bug has been tested and
  verified to occur with the bcmwl-kernel-source package, but also is
  very likely to affect any other packages that use DKMS modules.

  This fix for this is in the -proposed pocket at the moment, and has
  been tested to work.

  [Test plan]

  1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom 
WiFi is not an option, install VirtualBox in Step 9 rather than 
bcmwl-kernel-source.)
  2. Install Ubuntu on the system, but do not enable the installation of 
third-party drivers.
  3. When installation finishes, reboot.
  4. When the system boots into the Ubuntu desktop, connect to the Internet 
without WiFi, and update all packages on the system.
  5. Enable -proposed.
  6. Update *just* the DKMS package with "sudo apt install dkms".
  7. Disable -proposed.
  8. Reboot.
  9. Run "sudo apt install bcmwl-kernel-source". The WiFi module should 
immediately begin working properly.

  [Where problems could occur]

  Theoretically, a bug in the code could result in DKMS drivers still
  not being signed in some instances (though there are no known
  instances where this happens). But as Secure Boot + DKMS is already
  entirely broken, even this kind of breakage would be an improvement
  beyond what we already have. Given the rather obvious nature of such
  breakage, thorough testing should be able to detect it with ease.

  ---

  Original bug reports:

  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

  ---

  dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve
  this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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

[Kernel-packages] [Bug 1990945] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-firmware 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1990945

Title:
  i915: Add GuC v70.1.1 for all platforms

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]  
 

 
  Intel Quake N i915 for kernel 5.19+ will need v70.1.1 firmware files. 
 

 
  [Fix] 
 

 
  Upstream commit ab0d8c137d42 ("i915: Add GuC v70.1.1 for all platforms"). 
 

 
  [Test Case]   
 

 
  With v69 firmware, kernel prints: 
 

 
kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin  
 
is recommended, but only i915/adlp_guc_69.0.3.bin was found

 
  New firmware would silence this line. 
 

 
  [Where problems could occur]  
 

 
  Firmware update, little knowledge to what was actually fixed, and the 
 
  actual revision being used is guarded by kernel.   

 
  [Other Info]  
 

 
  This update already exists in Kinetic, so only Jammy is nominated.

  == original bug report ==

  Quake N i915 for kernel 5.19+ will need the firmware files listed in the 
following mail post:
  https://www.spinics.net/lists/intel-gfx/msg295995.html

  We are targeting Quake N to release with 6.0-oem kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990945/+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

[Kernel-packages] [Bug 1992435] Re: sof-hda-dsp Dmic0 not initial correctly

[Łukasz Zemczak]

Hello Dirk, 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.1 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.

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1992435

Title:
  sof-hda-dsp Dmic0 not initial correctly

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Device use sof-hda-dsp driver will not able to initial the Dmic0 status 
correctly

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Dmic should be on and volume set to 70%

  [Where problems could occur]
  Only fix for Dmic0 control and upstream already merged the code. The risk 
will be low

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/132

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1992435/+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

[Kernel-packages] [Bug 1992435] Re: sof-hda-dsp Dmic0 not initial correctly

[Łukasz Zemczak]

Sponsored. Will accept in a moment.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1992435

Title:
  sof-hda-dsp Dmic0 not initial correctly

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [Impact]
  Device use sof-hda-dsp driver will not able to initial the Dmic0 status 
correctly

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Dmic should be on and volume set to 70%

  [Where problems could occur]
  Only fix for Dmic0 control and upstream already merged the code. The risk 
will be low

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/132

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1992435/+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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Łukasz Zemczak]

Okay, as this is needed for the new batch of kernels, is verified and no
errors related to the package seem to be present in errors.ubuntu.com,
let me release this earlier.

-- 
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/1986921

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in lttng-modules source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in lttng-modules source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

[Łukasz Zemczak]

Hello Stefan, or anyone else affected,

Accepted lttng-modules into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/lttng-
modules/2.10.8-1ubuntu2~18.04.4 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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.

** Changed in: lttng-modules (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
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/1986921

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in lttng-modules source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Won't Fix
Status in lttng-modules source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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

[Kernel-packages] [Bug 1983291] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-firmware 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1983291

Title:
  Update firmware for DCN316/GFX1037

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Jammy already has firmware for upcoming product with GFX1037 and DCN316.  
However this firmware has some stability problems under stress and it should be 
updated to latest on linux-firmware.git to support systems that will take this 
firmware.

  [Fix]
  Upgrade following binaries:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122

  [Test]
  Verify suspend/resume works.
  Verify that accelerated graphics works.
  Verify video playback works.

  [Where problems could occur]
  Firmware is only loaded to product with GFX1037/DCN316
  This isn't yet on the market and regressions are not possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+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

[Kernel-packages] [Bug 1984004] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-firmware 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1984004

Title:
  Linux Firmware drops AMD RX6650 XT Performance

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  In e.g. the Unigine benchmark, the linux-firmware packages drops the
  performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to
  23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu
  20.04 based).

  Getting the firmware directly from git brings the performance back to about 
100 FPS:
  git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
  cd linux-firmware
  sudo make install
  sudo update-initramfs -c -k all

  [Fix]

  Update amdgpu/dimgrey_cavefish_* firmware files to latest versions
  from kernel.org.

  [Test Case]

  See original description.

  [Where Problems Could Occur]

  Isolated to AMD GPUs that use dimgrey_cavefish firmware blobs.

  [Original Description]

  Kernel: 5.15.0-43-generic
  linux-firmware: 20220329.git681281e4-0ubuntu3.3
  Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based)

  In e.g. the Unigine benchmark, the linux-firmware packages drops the
  performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to
  23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu
  20.04 based).

  Getting the firmware directly from git brings the performance back to about 
100 FPS:
  git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
  cd linux-firmware
  sudo make install
  sudo update-initramfs -c -k all

  Re-installing the linux-firmware package causes the performance to
  drop again. So there is a problem with the linux firmware at least for
  the RX 6650 XT, maybe for the whole RX 6000 series.

  The linux-firmware package in Ubuntu 22.04 should be updated.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  daelach1352 F pulseaudio
   /dev/snd/controlC0:  daelach1352 F pulseaudio
   /dev/snd/controlC1:  daelach1352 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu]
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2020-08-24 (714 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet 
loglevel=3 splash
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:

  Tags: vanessa third-party-packages
  Uname: Linux 5.15.0-43-generic x86_64
  UnreportableReason: This does not seem to be an official Linux package. 
Please retry after updating the indexes of available packages. If that does not 
work, then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4901
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications 

[Kernel-packages] [Bug 1986743] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-firmware 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1986743

Title:
  REQUEST add meson vdec firmware to arm64 linux-firmware package

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  22.04.1 LTS

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  20220329.git681281e40ubuntu3.4

  3) What you expected to happen
  Linux Firmware would include meson vdec blobs
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec

  4) What happened instead
  Linux Firmware does not include meson vdec blobs

  [Test case]

  Load meson-vdec driver on HW that supports it and watch firmware load
  failure.

  [Fix]

  Include firmware blobs.

  [Where Problems Could Occur]

  This only affects very specific HW. And the blobs have shipped in
  older series but were dropped incorrectly in Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+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

[Kernel-packages] [Bug 1988143] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-restricted-
modules-hwe-5.15 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in
Ubuntu.
https://bugs.launchpad.net/bugs/1988143

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * Linux-restricted-modules for the 390 drivers were disabled
  temporarily back in January, however they were not re-enabled when
  support for the new kernel was added.

   * Including the 390 release in the ISO causes the 5.13 packages to be
  pulled in.

  [Test Plan]

   * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver
  can be installed with its linux-restricted-modules.

  [Where problems could occur]

   * The addition of modules for an already existing driver series would not
     cause any regressions, since the whole package generation process is 
automated, and this is the only commit that we are going to revert:
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020

  [Other Info]

   * Other kernel releases support the 390 series.
  _

  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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

[Kernel-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages

[Łukasz Zemczak]

...discussed this with the kernel team and it seems to be a bug in the
5.15 hwe lrm kernel packages. Apparently because of an error, the
nvidia-390 packages have not been prepared for this kernel. And since we
pull in 390 (and should), this causes the build infrastructure to pull
in the old 5.13 kernels along with them.

The kernel team is working on a lrm-only respin.

** Also affects: linux-restricted-modules-hwe-5.15 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in
Ubuntu.
https://bugs.launchpad.net/bugs/1988143

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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

[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32

[Łukasz Zemczak]

Hey Heitor! Thank you for following up on Robie's questions. As this is
a bug in the current upstream versions of zfs-linux + currently LTS
upgrades to jammy are enabled, I'm starting to lean towards getting this
accepted into focal-proposed. Out of curiosity, what is the situation on
bionic btw.? What is the behavior there?

Too bad there's simply no way of knowing how many people would be
potentially affected by the inversion of the behavior. Did we see any
reports of this being a problem on jammy, after we switched upgrades
from focal? The thing is that, potentially, some might want to stay of
focal to not have to deal with incompatibilities like that after
upgrades. So we need to be considerate of such people. Although I do
agree the reducing of ZFS memory footprint being much more common.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964992

Title:
  ZFS ignores ARC sizes below allmem/32

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Focal:
  Incomplete

Bug description:
  [Impact]
  ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. 
This prevents users from properly restraining ARC sizes, and can cause 
increased memory contention in some systems.

  [Test Plan]
  1. Deploy test system with ZFS storage and 32GB RAM
  2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf
     # cat /etc/modprobe.d/99-zfs-arc.conf
     options zfs zfs_arc_min=536870912
     options zfs zfs_arc_max=966367641
  3. Reboot system
  4. Verify ARC sizes through "arc_summary"
     # arc_summary | grep -A3 "ARC size"
     ARC size (current):   < 0.1 %1.3 MiB
     Target size (adaptive):   100.0 %   15.7 GiB
     Min size (hard limit):  3.2 %  512.0 MiB
     Max size (high water):   31:1   15.7 GiB

  For a 32GB test system, we should be able to set max ARC sizes below
  1GB.

  [Fix]
  This has been fixed by upstream commit:
   - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32"

  The commit has been introduced in upstream zfs-2.0.0, so it's needed
  for Bionic and Focal. Releases starting with Impish already have this
  commit by default:

  $ git describe --contains 36a6e2335c45
  zfs-2.0.0-rc1~332
  $ rmadison zfs-linux
   zfs-linux | 0.7.5-1ubuntu15| bionic  | source
   zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates  | source
   zfs-linux | 0.8.3-1ubuntu12| focal   | source
   zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
   zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates   | source
   zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed  | source
   zfs-linux | 2.0.6-1ubuntu2 | impish  | source
   zfs-linux | 2.0.6-1ubuntu2.1   | impish-updates  | source
   zfs-linux | 2.1.2-1ubuntu3 | jammy   | source

  [Regression Potential]
  The introduced commit essentially removes the limitation of setting ARC 
tunables below allmem/32, and re-arranges the order of how some of the tunables 
are parsed. Regressions would possibly show up as other tunables being ignored 
or not being set correctly due to parsing errors. We should validate whether 
other ARC related tunables are still being set correctly, and whether ZFS is 
using the set values for the ARC memory thresholds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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

[Kernel-packages] [Bug 1981525] Re: Add support for Raptor Lake CPUs

[Łukasz Zemczak]

Hello Dirk, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.1 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.

** Changed in: thermald (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1981525

Title:
  Add support for Raptor Lake CPUs

Status in OEM Priority Project:
  In Progress
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * Support thermald on Raptor Lake CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Raptor Lake in thermald, which
  won't impact other hardware.

  [Other Info]

   * https://github.com/intel/thermal_daemon/issues/354

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1981525/+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

[Kernel-packages] [Bug 1983474] Re: No HDMI output on Nezha board

[Łukasz Zemczak]

Thanks for reporting! For a moment I was worried it was a general HDMI
output error, which seemed unexpected as Alex originally did not see
such issues while testing the Nezha images.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1983474

Title:
  No HDMI output on Nezha board

Status in linux-allwinner-5.17 package in Ubuntu:
  New

Bug description:
  I followed the instructions in
  
http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results

  The board does not provide HDMI output.

  Monitor: Samsung LU28R550UQRXEN (see appended EDID information)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.17.0-1003-allwinner.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: riscv64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Package: linux (not installed)
  PciMultimedia:
   
  ProcCpuinfo:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner 
root=LABEL=cloudimg-rootfs ro quiet splash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RelatedPackageVersions:
   linux-restricted-modules-5.17.0-1003-allwinner N/A
   linux-backports-modules-5.17.0-1003-allwinner  N/A
   linux-firmware 
20220329.git681281e4-0ubuntu3.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  StagingDrivers: sunxi_cedrus
  Tags:  jammy uec-images staging
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+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

[Kernel-packages] [Bug 1980145] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for wireless-regdb 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1980145

Title:
  New upstream release 2022.06.06

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Impish:
  In Progress
Status in wireless-regdb source package in Jammy:
  Fix Released
Status in wireless-regdb source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1980145/+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

[Kernel-packages] [Bug 1980145] Re: New upstream release 2022.06.06

[Łukasz Zemczak]

Thanks! I'll release it for both -updates and -security. The package has
been built against -proposed, but that should be fine as this is a pure-
data package.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1980145

Title:
  New upstream release 2022.06.06

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Impish:
  In Progress
Status in wireless-regdb source package in Jammy:
  Fix Released
Status in wireless-regdb source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1980145/+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