[Kernel-packages] [Bug 2035014] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-32-generic package post-installation script subproce

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to
  install/upgrade: installed linux-image-6.2.0-32-generic package post-
  installation script subprocess returned error exit status 2

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  the tilt sensor does not work so the screen do not rotate

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Sep  5 23:02:39 2023
  ErrorMessage: installed linux-image-6.2.0-32-generic package 
post-installation script subprocess returned error exit status 2
  InstallationDate: Installed on 2023-01-14 (234 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: linux-signed-hwe-6.2
  Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-32-generic package 
post-installation script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2035014/+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 2035014] [NEW] package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-32-generic package post-installation script subpro

[Freddy Alarcon]

Public bug reported:

the tilt sensor does not work so the screen do not rotate

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Sep  5 23:02:39 2023
ErrorMessage: installed linux-image-6.2.0-32-generic package post-installation 
script subprocess returned error exit status 2
InstallationDate: Installed on 2023-01-14 (234 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
SourcePackage: linux-signed-hwe-6.2
Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-32-generic package 
post-installation script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-6.2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to
  install/upgrade: installed linux-image-6.2.0-32-generic package post-
  installation script subprocess returned error exit status 2

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  the tilt sensor does not work so the screen do not rotate

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Sep  5 23:02:39 2023
  ErrorMessage: installed linux-image-6.2.0-32-generic package 
post-installation script subprocess returned error exit status 2
  InstallationDate: Installed on 2023-01-14 (234 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: linux-signed-hwe-6.2
  Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-32-generic package 
post-installation script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2035014/+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 2029372] Re: Remove force_probe for i915 on MTL platforms to ease the development process

[You-Sheng Yang]

** Also affects: linux-oem-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-6.5 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => Fix Released

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
   Status: New => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Mantic)
   Status: Incomplete => Won't Fix

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

Title:
  Remove force_probe for i915 on MTL platforms to ease the development
  process

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  To remove force_probe for i915 on MTL platforms to ease the
  development process.

  [Fix]

  Sauced fix to remove force_probe flag.

  [Test Case]

  i915 should then be enabled automatically without the need of
  i915.force_probe= in boot parameters.

  [Where problems could occur]

  This is for the convenience of early development. i915 may not be
  stable/fully functional on MTL platforms.

  [Other Info]

  While this is only meant for kernel >= 6.5, only oem-6.5 is nominated
  for fix so far.

  == original bug report ==

  i915 on MTL platforms still takes an additional boot parameter
  i915.force_probe= to drive the graphic device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029372/+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 1786013] Autopkgtest regression report (linux-meta-aws-5.15/5.15.0.1046.51~20.04.34)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws-5.15 
(5.15.0.1046.51~20.04.34) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.22 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-aws-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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

Re: [Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

[denisj...@gmail.com]

Running on a production desktop, I can’t do any testing.

Sent from my iPhone

> On Sep 9, 2023, at 10:33 AM, Ubuntu Kernel Bot <1970...@bugs.launchpad.net> 
> wrote:
> 
> This bug is awaiting verification that the linux-
> aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
> Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-focal-linux-
> aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
> still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
> to 'verification-failed-focal-linux-aws-5.15'.
> 
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
> 
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed. Thank you!
> 
> 
> ** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
> verification-needed-focal-linux-aws-5.15
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1970074
> 
> Title:
>  UBSAN: array-index-out-of-bounds in
>  /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
> 
> Status in linux package in Ubuntu:
>  Confirmed
> Status in linux source package in Jammy:
>  Fix Released
> 
> Bug description:
>  Something wrong with ata driver in dmesg found:
> 
>  [1.980693] kernel: 
> 
>  [1.980699] kernel: fbcon: Taking over console
>  [1.980703] kernel: UBSAN: array-index-out-of-bounds in 
> /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
>  [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
>  [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 
> 5.15.0-25-generic #25-Ubuntu
>  [1.980716] kernel: Hardware name: System manufacturer System Product 
> Name/P5Q3, BIOS 110206/11/2010
>  [1.980718] kernel: Call Trace:
>  [1.980721] kernel:  
>  [1.980723] kernel:  show_stack+0x52/0x58
>  [1.980729] kernel:  dump_stack_lvl+0x4a/0x5f
>  [1.980734] kernel:  dump_stack+0x10/0x12
>  [1.980736] kernel:  ubsan_epilogue+0x9/0x45
>  [1.980739] kernel:  __ubsan_handle_out_of_bounds.cold+0x44/0x49
>  [1.980742] kernel:  ahci_qc_issue+0x166/0x170 [libahci]
>  [1.980748] kernel:  ata_qc_issue+0x135/0x240
>  [1.980752] kernel:  ata_exec_internal_sg+0x2c4/0x580
>  [1.980754] kernel:  ? vprintk_default+0x1d/0x20
>  [1.980759] kernel:  ata_exec_internal+0x67/0xa0
>  [1.980762] kernel:  sata_pmp_read+0x8d/0xc0
>  [1.980765] kernel:  sata_pmp_read_gscr+0x3c/0x90
>  [1.980768] kernel:  sata_pmp_attach+0x8b/0x310
>  [1.980771] kernel:  ata_eh_revalidate_and_attach+0x28c/0x4b0
>  [1.980775] kernel:  ata_eh_recover+0x6b6/0xb30
>  [1.980778] kernel:  ? ahci_do_hardreset+0x180/0x180 [libahci]
>  [1.980783] kernel:  ? ahci_stop_engine+0xb0/0xb0 [libahci]
>  [1.980787] kernel:  ? ahci_do_softreset+0x290/0x290 [libahci]
>  [1.980792] kernel:  ? 
> trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
>  [1.980795] kernel:  sata_pmp_eh_recover.isra.0+0x214/0x560
>  [1.980799] kernel:  sata_pmp_error_handler+0x23/0x40
>  [1.980802] kernel:  ahci_error_handler+0x43/0x80 [libahci]
>  [1.980806] kernel:  ata_scsi_port_error_handler+0x2b1/0x600
>  [1.980810] kernel:  ata_scsi_error+0x9c/0xd0
>  [1.980813] kernel:  scsi_error_handler+0xa1/0x180
>  [1.980817] kernel:  ? scsi_unjam_host+0x1c0/0x1c0
>  [1.980820] kernel:  kthread+0x12a/0x150
>  [1.980823] kernel:  ? set_kthread_struct+0x50/0x50
>  [1.980826] kernel:  ret_from_fork+0x22/0x30
>  [1.980831] kernel:  
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 22.04
>  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
>  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
>  Uname: Linux 5.15.0-25-generic x86_64
>  ApportVersion: 2.20.11-0ubuntu82
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  eugene16798 F pulseaudio
>   /dev/snd/pcmC0D0p:   eugene16798 F...m pulseaudio
>   /dev/snd/controlC1:  eugene16798 F pulseaudio
>  CasperMD5CheckResult: unknown
>  CurrentDesktop: KDE
>  Date: Sun Apr 24 05:13:34 2022
>  HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
>  InstallationDate: Installed on 2019-04-13 (1106 days ago)
>  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
>  IwConfig:
>   lono wireless extensions.
> 
>   enp2s0no wireless extensions.
> 
>   virbr0no wireless extensions.
>  MachineType: System manufacturer System Product Name
>  ProcEnviron:
>   LANGUAGE=
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=uk_UA.UTF-8
>   SHELL=/bin/bash
>  ProcFB: 0 radeondrmfb
>  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2034705] Re: efivar fails to read variables

[Heinrich Schuchardt]

Patch sent upstream https://lore.kernel.org/linux-
efi/20230909180812.10904-1-heinrich.schucha...@canonical.com/T/#u.

Without this patch the Ubuntu installer on systems using U-Boot (e.g.
riscv64) will fail.

** Changed in: linux-meta-riscv (Ubuntu)
 Assignee: Heinrich Schuchardt (xypron) => (unassigned)

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

Title:
  efivar fails to read variables

Status in efivar package in Ubuntu:
  Invalid
Status in linux-meta-riscv package in Ubuntu:
  In Progress

Bug description:
  On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel
  6.5.0-2-generic we see this output:

  
  root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/
  AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
  VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c

  root@ubuntu-server:/var# efivar -l
  efivar: error listing variables: Function not implemented

  root@ubuntu-server:/var# efibootmgr -v
  EFI variables are not supported on this system.

  Expected behavior would be to display the variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04

[Gre0]

After a dist-upgrade from 22.10 to 23.04 my Intel(R) Wi-Fi 6 AX200
wasn't working.

After an hour of searching for the problem, I came here and after the
command…

sudo apt remove --purge linux-modules-iwlwifi*   …and a reboot, Wi-Fi is
working again. Nice :)

gre0_@u2304:~$ sudo dmesg |grep iwlwifi
[5.296217] iwlwifi :07:00.0: enabling device ( -> 0002)
[5.304378] iwlwifi :07:00.0: api flags index 2 larger than supported by 
driver
[5.304396] iwlwifi :07:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
89.3.35.37
[5.305133] iwlwifi :07:00.0: loaded firmware version 72.daa05125.0 
cc-a0-72.ucode op_mode iwlmvm
[5.394353] iwlwifi :07:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
[5.568351] iwlwifi :07:00.0: Detected RF HR B3, rfid=0x10a100
[5.632254] iwlwifi :07:00.0: base HW address: 28:6b:35:c8:68:bf
[5.647483] iwlwifi :07:00.0 wlp7s0: renamed from wlan0

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

Title:
  Intel Wi-Fi 6 AX201 failing in 23.04

Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 23.04 the intel wifi driver is not
  loading, I am seeing the following in dmesg:

  [  215.024382] Loading of unsigned module is rejected
  [  262.051998] [ cut here ]
  [  262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 
genl_validate_ops+0x1cc/0x270
  [  262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc 
vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac 
algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport 
snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek 
snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common 
soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match 
snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus 
x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether 
coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 
snd_intel_sdw_acpi
  [  262.052038]  mii hid_plantronics hid_logitech_dj snd_usbmidi_lib 
snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp 
intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni 
snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel 
sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc 
hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d 
hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd 
hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel 
processor_thermal_device_pci_legacy cryptd cmdlinepart 
industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm 
dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device 
hid_sensor_iio_common processor_thermal_rfim intel_cstate 
firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor 
wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec 
processor_thermal_mbox soundcore rc_core mei ecdh_generic
  [  262.052068]  processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc 
ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea 
intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal 
soc_button_array int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds 
mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs 
ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi 
spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci 
xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus 
intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake
  [  262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW  O   
6.2.0-1003-lowlatency #3-Ubuntu
  [  262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 
02/24/2023
  [  262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270
  [  262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 
c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb 
b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d
  [  262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206
  [  262.052105] RAX: 0003 RBX: 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-6.2/6.2.0.1013.13~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws-6.2 
(6.2.0.1013.13~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-aws-6.2/6.2.0-1013.13~22.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-aws-6.2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1046.45)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1046.45) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dm-writeboost/2.2.13-1ubuntu3 (amd64, arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.1 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Luca Boccassi]

** Tags removed: verification-needed-focal-linux-aws-5.15

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  In Progress
Status in linux-kvm source package in Mantic:
  In Progress
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 1639924] Re: Kernel livepatch support for for s390x

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Kernel livepatch support for for s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in kpatch package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in gcc-11 source package in Jammy:
  Fix Released
Status in kpatch source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in gcc-11 source package in Kinetic:
  Fix Released
Status in kpatch source package in Kinetic:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * kpatch upstream has gained support for more architectures which we
  would like to enable on LTS release. Since building livepatches using
  the kpatch tooling makes the most sense on LTS kernels.

   * This SRU is to enable s390x builds of kpatch on kinetic & jammy.

   * Separately linux kernel patches for s390x will also be backported
  to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to
  support livepatches.

  [ Test Plan ]

   * Attempt to run and load sample integration livepatches from the
  kpatch integration source code, against v5.15 & v5.19 kernels. These
  should succeed on:

   - amd64 jammy v5.15
   - amd64 & s390x jammy v5.19
   - amd64 & s390x kinetic v5.19

  [ Where problems could occur ]

   * The newly generated livepatches produced by this kpatch may have
  different content (more or less sections/sybmols/relocations/etc), but
  remain compatible with all prior kernels and tool-chains.

   * This is a fairly large upstream update to the tooling.

   * One command line option to kpatch-build is no longer supported
  '-e', instead long form command line option must be used '--oot-
  module'. And '--ott-module-src' becomes mandatory in such cases,
  previously '--sourcedire' was required.

  Additional command line options added '--oot-module-src, -R|--non-
  replace'.

  '--skip-gcc-check' is still supported but prints warnings, it is
  deprecated in favour of '--skip-compiler-check'.

  kpatch-cc utility is added, which is a toolchain wrapper.

  Thus adjustments might be needed to scripts used to invoke and create
  kpatch modules.

   * Majority of non-test/non-doc changes are to do with:
     - add support for s390x and 32bit powerpc
     - add support for newer kernels and compilers (support & bugfixes to 
various sections and symbols)
     - more strict checking and bugfixes w.r.t. livepatch generation
     - refactoring and better build support for cross-compiled modules, 
compilation for various linux distributions, and code cleanups.

  * Some of the fixes from these new upstream releases have already been
  cherry-picked in the kpatch, but others might soon be needed on x84,
  i.e. to support gcc-12 built kernels.

  $ git log  --no-merges  --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-
  build/ > shortlog.txt

  d46fea98ef kpatch-build: strengthen conditions for changed sections
  9fac261ed0 kpatch-build: rela section could disappear after patched
  fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules
  8cc0fedefb kpatch-build: use err.h instead of error.h for musl support
  07433e98c0 kpatch-cc: fix stripping of source tree prefix
  33368a88cd create-diff-object: add support for .return_sites section (x86)
  e921c557f9 macros: tweak syscall patching macros
  a1171b112e create-diff-object: Create missing section symbol
  0308d52bcd kpatch/s390: Enable kpatch build support
  b0330ab18e kpatch/s390: Add additional bundled symbols.
  eb4a85f778 kpatch/s390: Add exclusion lists
  f0d00a9290 kpatch/s390: Add initial support for kpatch
  10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch
  c6d0b5450b lookup: fix symtab parsing
  52863dace0 create-diff-object: fix endianness in 
kpatch_no_sibling_calls_ppc64le()
  017015a725 create-diff-object: make kpatch_check_relocations() more precise
  f0e3da336c create-diff-object: fix string extraction
  86d5208b46 create-diff-object: error on symbol 

[Kernel-packages] [Bug 1642368] Re: linux: Staging modules should be unsigned

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  linux: Staging modules should be unsigned

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  Modules under the drivers/staging hierarchy get little attention when
  it comes to vulnerabilities. It is possible that memory mapping tricks
  that expose kernel internals would go unnoticed. Therefore, do not
  sign staging modules so that they cannot be loaded in a secure boot
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642368/+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 1806488] Re: Support non-strict iommu mode on arm64

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Support non-strict iommu mode on arm64

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Released
Status in linux-aws source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-aws source package in Disco:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Invalid
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.

  There's a significant performance gain to be had by removing the need
  to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
  performance gain w/ fio reads on a single NVMe device.

  This mode of operation is available for x86 via the
  "intel_iommu=strict" parameter. Upstream now exposes an equivalent
  feature for ARM platforms via the "iommu.strict=[0|1]" parameter,
  while retaining the default strict-enabled mode.

  [Test Case]
  Run fio with the following config before and after applying the patches and 
collection IOPS count. Run again after applying the patches. Finally, run a 3rd 
time after adding iommu.strict=0 to the kernel commandline.

  Performance should not regress after the update. Performance should
  further improve after adding iommu.strict=0 - but if it doesn't for
  some reason, that is not a regression.

  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1

  [job1]
  filename=/dev/nvme0n1

  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()

  [Regression Risk]
  Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"

  2 patches do touch arch-indep code however:

  > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.

  > 2da274cdf998a iommu/dma: Add support for non-strict mode
  This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:

  -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
  +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
  +   if (!cookie->fq_domain)
  +   iommu_tlb_sync(domain);

  In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
    iommu_unmap_fast()
    iommu_tlb_sync()

  Looking at the source to iommu_unmap() confirms that this is
  functionally equivalent.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x -
  kernel part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * Currently the PCI passthrough implementation for s390x is based on
     intercepting PCI I/O instructions, which leads to a reduced I/O performance
     compared to the execution of PCI instructions directly in LPAR.

   * Hence users may face I/O bottlenecks when using PCI devices in passthrough
     mode based on the current implementation.

   * For avoiding this and to improve performance, the interpretive execution
     of the PCI store and PCI load instructions get enabled.

   * A further improvement is achieved by enabling the 
Adapter-Event-Notification
     Interpretation (AENI).

   * Since LTS releases are the main focus for stable and long running KVM
     workloads, it is highly desired to get this backported to the jammy kernel
     (and because the next LTS is still some time away).

  [ Test Plan ]

  * Hardware used: z14 or greater LPAR, PCI-attached devices
(RoCE VFs, ISM devices, NVMe drive)

  * Setup: Both the kernel and QEMU features are needed for the feature
to function (an upstream QEMU can be used to verify the kernel early),
and the facility is only avaialble on z14 or newer.
When any of those pieces is missing,
the interpretation facility will not be used.
When both the kernel and QEMU features are included in their respective
packages, and running in an LPAR on a z14 or newer machine,
this feature will be enabled automatically.
Existing supported devices should behave as before with no changes
required by an end-user (e.g. no changes to libvirt domain definitions)
-- but will now make use of the interpretation facility.
Additionally, ISM devices will now be eligible for vfio-pci passthrough
(where before QEMU would exit on error if attempting to provide an ISM
device for vfio-pci passthrough, preventing the guest from starting)

  * Testing will include the following scenarios, repeated each for RoCE,
ISM and NVMe:

1) Testing of basic device passthrough (create a VM with a vfio-pci
   device as part of the libvirt domain definition, passing through
   a RoCE VF, an ISM device, or an NVMe drive. Verify that the device
   is available in the guest and functioning)
2) Testing of device hotplug/unplug (create a VM with a vfio-pci device,
   virsh detach-device to remove the device from the running guest,
   verify the device is removed from the guest, then virsh attach-device
   to hotplug the device to the guest again, verify the device functions
   in the guest)
3) Host power off testing: Power off the device from the host, verify
   that the device is unplugged from the guest as part of the poweroff
4) Guest power off testing: Power off the device from within the guest,
   verify that the device is unusuable in the guest,
   power the device back on within the guest and verify that the device
   is once again usable.
5) Guest reboot testing: (create a VM with a vfio-pci device,
   verify the device is in working condition, reboot the guest,
   verify that the device is still usable after reboot)

  Testing will include the following scenarios specifically for ISM
  devices:

  1) Testing of SMC-D v1 fallback: Using 2 ISM devices on the same VCHID
 that share a PNETID, create 2 guests and pass one ISM device
 via vfio-pci device to each guest.
 Establish TCP connectivity between the 2 guests using the libvirt
 default network, and then use smc_run
 (https://manpages.ubuntu.com/manpages/jammy/man8/smc_run.8.html)
 to run an iperf workload 

[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  rtcpie in timers from ubuntu_kernel_selftests randomly failing

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
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:
  Fix Released

Bug description:
  Node: Standard_D11_v2
  Kernel: 4.18.0-1008.8~18.04.1

   selftests: timers: rtcpie
   
   Periodic IRQ rate is 1024Hz.
   Counting 20 interrupts at:
   2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
   32Hz:1 2 3 4 5 6 7
   PIE delta error: 0.034667 should be close to 0.031250
  181.  01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: 
timers: rtcpie [FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+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 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
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:
  Fix Released

Bug description:
  [Impact]
  On s390x LPAR instances, this test will fail with:
  #   File "linux/tools/testing/selftests/net/devlink_port_split.py", line 
64, in get_if_names
  # if ports[port]['flavour'] == 'physical':
  # KeyError: 'flavour'
not ok 1 selftests: net: devlink_port_split.py # exit=1

  This is because the mlx4 driver in use on this instance does not set
  attributes, therefore `devlink -j port show` command output does not
  contain this "flavour" key.

  [Fix]
  * 3de66d08d3 selftests: net: devlink_port_split.py: skip test if no
suitable device available

  This patch can be cherry-picked into our J/K/L kernels.

  [Test]
  Run the patched devlink_port_split.py on s390x LPAR, and it won't
  fail with # KeyError: 'flavour' but marked as SKIP instead.

  [Where problems could occur]
  If this change is incorrect, it may affect the test result, however it's
  limited to testing tools, no actual impact to kernel functions.


  [Original Bug Report]
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25

  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+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 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

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

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

Bug description:
  SRU Justification:

  [Impact]

  Request to include below mpi3mr driver bug fix patches in Ubuntu
  22.04.1(5.15 kernel). These patches got accepted by the upstream and
  please find the corresponding commit IDs as below:

  f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0
  7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough
  986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs
  43ca11005098 scsi: mpi3mr: Add support for PEL commands
  506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands
  f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers 
to uapi header
  f5e6d5a34376 scsi: mpi3mr: Add support for driver commands
  4268fa751365 scsi: mpi3mr: Add bsg device support
  1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc
  4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings
  9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes
  e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes
  bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails
  a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init()
  256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR
  2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset
  1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s

  [Test Plan]

  1.  Install and boot kernel
  2.  Run basic I/O tests

  [Where problems could occur]

  Moderate to low regression risk for the kernel as most changes are in
  the driver

  [Other Info]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  ubuntu_kernel_selftests: net:udpgso_bench.sh failed

Status in ubuntu-kernel-tests:
  In Progress
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:
  04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh
  04:41:59 DEBUG| [stdout] # ipv4
  04:41:59 DEBUG| [stdout] # tcp
  04:42:00 DEBUG| [stdout] # tcp tx:   2736 MB/s46415 calls/s  46415 msg/s
  04:42:00 DEBUG| [stdout] # tcp rx:   2737 MB/s46161 calls/s
  04:42:01 DEBUG| [stdout] # tcp tx:   2735 MB/s46392 calls/s  46392 msg/s
  04:42:01 DEBUG| [stdout] # tcp rx:   2739 MB/s46226 calls/s
  04:42:02 DEBUG| [stdout] # tcp tx:   2717 MB/s46092 calls/s  46092 msg/s
  04:42:02 DEBUG| [stdout] # tcp zerocopy
  04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused

  04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1
  04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m
  04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1
  04:42:54 DEBUG| [stdout] make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  04:42:54 ERROR| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
 line 252, in run_once
  raise error.TestError(test_name + ' failed.')
  TestError: net:udpgso_bench.sh failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+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 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-kvm / L-kvm

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  ftrace in ubuntu_kernel_selftests failed with "check if duplicate
  events are caught" on J-kvm / L-kvm

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  (Thibf got this issue fixed for KVM kernels, for PPC please refer to
  bug 2026592)

  Issue found on Jammy 5.15.0-36.37 with Power9 node baltar

  Test failed with:
  # [15] Generic dynamic event - check if duplicate events are caught [FAIL]

  Test Log:
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
   TAP version 13
   1..1
   # selftests: ftrace: ftracetest
   # === Ftrace unit tests ===
   # [1] Basic trace file check [PASS]
   # [2] Basic test for tracers [PASS]
   # [3] Basic trace clock test [PASS]
   # [4] Basic event tracing check  [PASS]
   # [5] Change the ringbuffer size [PASS]
   # [6] Snapshot and tracing setting   [PASS]
   # [7] trace_pipe and trace_marker[PASS]
   # [8] Test ftrace direct functions against tracers   [UNRESOLVED]
   # [9] Test ftrace direct functions against kprobes   [UNRESOLVED]
   # [10] Generic dynamic event - add/remove eprobe events  [PASS]
   # [11] Generic dynamic event - add/remove kprobe events  [PASS]
   # [12] Generic dynamic event - add/remove synthetic events   [PASS]
   # [13] Generic dynamic event - selective clear (compatibility)   [PASS]
   # [14] Generic dynamic event - generic clear event   [PASS]
   # [15] Generic dynamic event - check if duplicate events are caught  [FAIL]
   # [16] event tracing - enable/disable with event level files [PASS]
   # [17] event tracing - restricts events based on pid notrace filtering   
[PASS]
   # [18] event tracing - restricts events based on pid [PASS]
   # [19] event tracing - enable/disable with subsystem level files [PASS]
   # [20] event tracing - enable/disable with top level files   [PASS]
   # [21] Test trace_printk from module [PASS]
   # [22] ftrace - function graph filters with stack tracer [PASS]
   # [23] ftrace - function graph filters   [PASS]
   # [24] ftrace - function pid notrace filters [PASS]
   # [25] ftrace - function pid filters [PASS]
   # [26] ftrace - stacktrace filter command[PASS]
   # [27] ftrace - function trace with cpumask  [PASS]
   # [28] ftrace - test for function event triggers [PASS]
   # [29] ftrace - function trace on module [PASS]
   # [30] ftrace - function profiling   [PASS]
   # [31] ftrace - function profiler with function tracing  [PASS]
   # [32] ftrace - test reading of set_ftrace_filter[PASS]
   # [33] ftrace - test for function traceon/off triggers   [PASS]
   # [34] ftrace - test tracing error log support   [PASS]
   # [35] Test creation and deletion of trace instances while setting an event  
[PASS]
   # [36] Test creation and deletion of trace instances [PASS]
   # [37] Kprobe dynamic event - adding and removing[PASS]
   # [38] Kprobe dynamic event - busy event check   [PASS]
   # [39] Kprobe dynamic event with arguments   [PASS]
   # [40] Kprobe event with comm arguments  [PASS]
   # [41] Kprobe event string type argument [PASS]
   # [42] Kprobe event symbol argument  [PASS]
   # [43] Kprobe event argument syntax  [PASS]
   # [44] Kprobes event arguments with types[PASS]
   # [45] Kprobe event user-memory access   [UNSUPPORTED]
   # [46] Kprobe event auto/manual naming   [PASS]
   # [47] Kprobe dynamic event with function tracer [PASS]
   # [48] Create/delete multiprobe on kprobe event  [PASS]
   # [49] Kprobe event parser error log check   [PASS]
   # [50] Kretprobe dynamic event with arguments[PASS]
   # [51] Kretprobe dynamic event with maxactive[PASS]
   # [52] Kretprobe %return suffix test [PASS]
   # [53] Register/unregister many 

[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

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

Bug description:
  Something wrong with ata driver in dmesg found:

  [1.980693] kernel: 

  [1.980699] kernel: fbcon: Taking over console
  [1.980703] kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
  [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
  [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 
5.15.0-25-generic #25-Ubuntu
  [1.980716] kernel: Hardware name: System manufacturer System Product 
Name/P5Q3, BIOS 110206/11/2010
  [1.980718] kernel: Call Trace:
  [1.980721] kernel:  
  [1.980723] kernel:  show_stack+0x52/0x58
  [1.980729] kernel:  dump_stack_lvl+0x4a/0x5f
  [1.980734] kernel:  dump_stack+0x10/0x12
  [1.980736] kernel:  ubsan_epilogue+0x9/0x45
  [1.980739] kernel:  __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [1.980742] kernel:  ahci_qc_issue+0x166/0x170 [libahci]
  [1.980748] kernel:  ata_qc_issue+0x135/0x240
  [1.980752] kernel:  ata_exec_internal_sg+0x2c4/0x580
  [1.980754] kernel:  ? vprintk_default+0x1d/0x20
  [1.980759] kernel:  ata_exec_internal+0x67/0xa0
  [1.980762] kernel:  sata_pmp_read+0x8d/0xc0
  [1.980765] kernel:  sata_pmp_read_gscr+0x3c/0x90
  [1.980768] kernel:  sata_pmp_attach+0x8b/0x310
  [1.980771] kernel:  ata_eh_revalidate_and_attach+0x28c/0x4b0
  [1.980775] kernel:  ata_eh_recover+0x6b6/0xb30
  [1.980778] kernel:  ? ahci_do_hardreset+0x180/0x180 [libahci]
  [1.980783] kernel:  ? ahci_stop_engine+0xb0/0xb0 [libahci]
  [1.980787] kernel:  ? ahci_do_softreset+0x290/0x290 [libahci]
  [1.980792] kernel:  ? 
trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
  [1.980795] kernel:  sata_pmp_eh_recover.isra.0+0x214/0x560
  [1.980799] kernel:  sata_pmp_error_handler+0x23/0x40
  [1.980802] kernel:  ahci_error_handler+0x43/0x80 [libahci]
  [1.980806] kernel:  ata_scsi_port_error_handler+0x2b1/0x600
  [1.980810] kernel:  ata_scsi_error+0x9c/0xd0
  [1.980813] kernel:  scsi_error_handler+0xa1/0x180
  [1.980817] kernel:  ? scsi_unjam_host+0x1c0/0x1c0
  [1.980820] kernel:  kthread+0x12a/0x150
  [1.980823] kernel:  ? set_kthread_struct+0x50/0x50
  [1.980826] kernel:  ret_from_fork+0x22/0x30
  [1.980831] kernel:  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene16798 F pulseaudio
   /dev/snd/pcmC0D0p:   eugene16798 F...m pulseaudio
   /dev/snd/controlC1:  eugene16798 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Apr 24 05:13:34 2022
  HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
  InstallationDate: Installed on 2019-04-13 (1106 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   virbr0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic 
root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  == Impact ==
  We applied a set of patches early as the upstreaming got delayed. The patch 
now is in upstream linux. Since it differs somewhat from the patch we carry and 
in order to get potential security and other updates right, we want to replace 
the SAUCE patch by its upstream counterpart.

  == Fix ==
  “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is 
discovered.”
   to be replaced by:
  commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next
   “thunderbolt: Add DP OUT resource when DP tunnel is discovered”

  == Testcase ==
  Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 
1983143)

  == Regression Potential ==
  Previously working external connections might no longer work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+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 1989990] Re: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target
  after  link down/link up sequence

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

Bug description:
  [Impact]
  Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target 
after link down event if the number of queues have changed post link down.

  [Fix]
  Following upstream patch set helps address the issue.

  1.
  nvmet: Expose max queues to configfs
  
https://git.infradead.org/nvme.git/commit/2c4282742d049e2a5ab874e2b359a2421b9377c2

  2.
  nvme-tcp: Handle number of queue changes
  
https://git.infradead.org/nvme.git/commit/516204e486a19d03962c2757ef49782e6c1cacf4

  3.
  nvme-rdma: Handle number of queue changes
  
https://git.infradead.org/nvme.git/commit/e800278c1dc97518eab1970f8f58a5aad52b0f86

  The patch in Point 2 above helps address the failure to reconnect in
  NVMe TCP scenario.

  Also, following patch addresses error code parsing issue in the
  reconnect sequence.

  nvme-fabrics: parse nvme connect Linux error codes
  
https://git.infradead.org/nvme.git/commit/ec9e96b5230148294c7abcaf3a4c592d3720b62d

  [Test Plan]
  1.  Boot into Ubuntu 22.04 kernel without fix.

  2.  Establish connection to NVMe TCP target.

  3.  Toggle NIC link and bring link up after 10 seconds. When the NIC
  link is down, on the target increase the number of queues assigned to
  the controller.

  4.  Observe that connection to target is lost and after link comes up,
  controller from host tries to re-establish connection.

  5.  With patch, reconnection succeeds with higher number of queues

  [Where problems could occur]

  Regression risk is low to medium.

  [Other Info]

  Test Kernel Source

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989990/+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 1990167] Re: cma alloc failure in large 5.15 arm instances

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  cma alloc failure in large 5.15 arm instances

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released

Bug description:
  When launching large arm64 instances on the focal or jammy ami, cma
  allocation errors appear in the dmesg out:

  [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096
  pages, ret: -12

  As far as I can tell, this does not impact instance launch in a
  meaningful way, but I am unsure of the other implications of this. I
  was able to confirm that these messages are only present in 5.15, as
  they do not show up in the bionic image, and rolling back focal to
  linux-aws 5.4 avoids them as well.

  This was present in at least 2 instance types and only appears to pop
  up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge)
  does)

  This could be as simple as just disabling CMA in the linux-aws pkg, as
  it appears this is already the case in linux-azure(LP:  #1949770).

  Attaching dmesg out to the report.

  
  # Replication
  + Launch a large arm64 instance (c6gn.16xlarge)
  + Observe the messages in kern.log / dmesg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in zfs-linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Released
Status in zfs-linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Released
Status in zfs-linux source package in Lunar:
  Confirmed

Bug description:
  Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS
  are broken.

  Reproducer steps:

  ```
  sudo snap install lxd
  sudo snap set lxd shiftfs.enable=true
  sudo lxd init --auto
  lxc storage create zfs zfs
  lxc launch images:ubuntu/jammy c1 -s zfs
  lxc exec c1 -- touch /root/foo
  touch: cannot touch '/root/foo': Value too large for defined data type
  ```

  Expected result can be achieved by disabling shiftfs:

  ```
  sudo snap set lxd shiftfs.enable=false
  sudo systemctl reload snap.lxd.daemon
  lxc launch images:ubuntu/jammy c2 -s zfs
  lxc exec c2 -- touch /root/foo
  lxc exec c2 -- ls -la /root/foo
  -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo
  ```

  Kernel 5.15.0-47-generic does not exhibit this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-48-generic 5.15.0-48.54
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2240 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 14:55:52 2022
  InstallationDate: Installed on 2022-03-04 (205 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  MachineType: LENOVO 20R1000RUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET40W(1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20R1000RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20R1000RUS
  dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in
  kmalloc-2k slabs

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

Bug description:
  Since updating to kernel 5.15.0-46-generic (package version
  5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel
  memory; our first server with 8 GB of RAM just fatally OOMed, causing
  us to detect this. Inspection of OOM reports, /proc/meminfo, and
  /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k
  slabs:

  Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab 
info:
  Aug 23 12:51:11 cluster kernel: [361299.864757] Name  
Used  Total
  [...]
  Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k   
6676584KB6676596KB

  Most of our machines appear to be leaking slab memory at a rate of
  around 20 to 40 Mbytes/hour, with some machines leaking much faster;
  the champions are leaking kernel memory at 145 Mbytes/hour and 237
  Mbytes/hour.

  We aren't running any proprietary kernel modules and our only unusual
  kernel configuration is that we've disabled AppArmor with 'apparmor=0'
  on the kernel command line.

  /proc/version_signature:
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Full kernel command line from the Dell R240 system that fatally OOMd:
  BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 
console=tty0 apparmor=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+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 1991951] Re: RCU stalls

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  RCU stalls

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  our RCU Stall Timeouts are different to upstream defaults; with
  regular one 3x longer; and expedited one 1000x shorter.

  not sure why.

  Let's harmonize on 60 & 0, which is 60 for regular ones that are set
  on most architectures; and upstream default for the expedited ones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+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 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror
  mode

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The Screen is shaking connected monitor to Onboard HDMI port.

  [Fix]
  The interlaced mode is not supported for Intel Gen 12 onwards.
  Disable interlaced mode for DP on Display >= 12.

  Due to schedule, SRU for OEM kernels first.
  After these patches are merged to mainline/drmtip kernel, will SRU for 
generic kernels.

  [Test Case]
  1.Connected two external Monitor to the onboard HDMI/DP port .
  2.Boot OS.
  2.set mirror mode. (onboard HDMI / onboard DP)
  3.check if screen shakes.

  [Where problems could occur]
  Low, Remove interlace support for Display >= 12 so it wouldn't cause a 
regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1993561/+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 1993563] Re: support for same series backports versioning numbers

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  support for same series backports versioning numbers

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

Bug description:
  packaging support for sameport versioning numbers

  Allow generating kernel packages, that use backports mechanism within
  the same series. For example linux-lowlatancy linux-riscv.

  Those kernels already have customized packaging to achieve the above,
  this is introducing standard support for this in the main kernels for
  jammy and kinetic series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+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 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  Included in v6.2-rc1
  d899aa668498 PCI: vmd: Disable MSI remapping after suspend

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1996048/+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 1998106] Re: Fix AMD-PState driver for Genoa CPU

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix AMD-PState driver for Genoa CPU

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  During AMD Genoa development, the datacenter team identified
  performance regressions that were root caused in the amd-pstate
  driver. A first round of fixes already landed upstream (v6.1-rc7) in
  the amd-pstate driver, and should be backported to all the affected
  kernels.

  [Fix]

  Backport the upstream amd-pstate fixes:

  https://lore.kernel.org/linux-
  
pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a

  [Regression potential]

  Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a
  single driver (amd-pstate) and the new mode (passive) is disabled by
  default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Mediatek WLAN RZ616(MT7922) SAR table control

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  In order to make sure the amount of RF energy being absorbed by our bodies is 
safe according to the FCC’s guidelines, products must undergo and pass SAR 
testing.

  [Fix]
  Add ACPI SAR table control to pass the testing.

  [Test]
  the unit is 0.5dBm in following:

  Without the SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 40 40 40 40 40 40 40 40
  HT20 (user) : 40 40 40 40 40 40 40 40
  HT40 (user) : 40 40 40 40 40 40 40 40 
40
  VHT20 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT40 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT80 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT160 (user)   : 40 40 40 40 40 40 40 40 
40 40  0  0
  HE26 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE52 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE106 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE242 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE484 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996x2 (user)  : 40 40 40 40 40 40 40 40 
40 40 40 40

  After enabled SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 26 26 26 26 26 26 26 26
  HT20 (user) : 26 26 26 26 26 26 26 26
  HT40 (user) : 26 26 26 26 26 26 26 26 
26
  VHT20 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT40 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT80 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT160 (user)   : 26 26 26 26 26 26 26 26 
26 26  0  0
  HE26 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE52 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE106 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE242 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE484 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996x2 (user)  : 26 26 26 26 26 26 26 26 
26 26 26 26

  

[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  smartpqi: Update 22.04 driver to include recent bug fixes and support
  current generation devices

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

Bug description:
  [Impact]
  These patches provide bug fixes and add support for the latest generation of 
OEM PCI devices to ensure customers are able to use Jammy on the recent 
generations of server hardware. This will bring us in line with the other major 
linux distros.

  [Fix]
  There are some outstanding patches already in Linus's tree that can be 
applied to 22.04.
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  The following patches apply to
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

  f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
  e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
  6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
  2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
  cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
  6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
  69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
  85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
  2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
  44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
  331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
  904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
  297bdc540f0e scsi: smartpqi: Close write read holes
  dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
  1d393227fc76 scsi: smartpqi: Add controller fw version to console log
  4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
  8946ea283808 scsi: smartpqi: Fix typo in comment
  c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
  31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
  62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
  291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
  c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
  5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
  c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
  00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
  5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
  27655e9db479 scsi: smartpqi: Update volume size after expansion
  b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
  42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
  9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
  b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
  94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
  70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
  2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
  c57ee4ccb358 scsi: smartpqi: Add PCI IDs
  c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
  64fc9015fbeb scsi: smartpqi: Switch to attribute groups
  0ca190805784 scsi: smartpqi: Call scsi_done() directly

  I added the above SHA1 IDs to a file called:
  backport_linus_6.1_into_22.04

  git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
  git am -s /tmp/patches/*.diff

  All patches applied without any conflicts.

  [Test Plan]
  The upstream driver has undergone extensive testing by Microchip's test team 
before submitting those patches to the upstream kernel. All patches are tested 
and accepted in the upstream kernel at this time.

  One should be able to load the smartpqi driver and verify the version
  is at 2.1.18-045

  [Other Info]

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

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix iosm: WWAN cannot build the connection (DW5823e)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
   WWAN(DW5823e) can't build the connection successfully.

  [Fix]
   With INTEL_IOMMU disable config or by forcing intel_iommu=off from
   grub some of the features of IOSM driver like browsing, flashing &
   coredump collection is not working.
  
   When driver calls DMA API - dma_map_single() for tx transfers. It is
   resulting in dma mapping error.
  
   Set the device DMA addressing capabilities using dma_set_mask() and
   remove the INTEL_IOMMU dependency in kconfig so that driver follows
   the platform config either INTEL_IOMMU enable or disable.
   
   Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY 
   CONFIGs yet on iosm module, the single patch is necessary for Jammy.

  [Test Case]
   1. boot up with kernel applied the FIX.
   2. check the status of wwan by "mmcli -m 0"
   Status| unlock retries: sim-pin (3)
 |  state: ^[32mconnected^[0m
 |power state: on
 |access tech: lte
 | signal quality: 45% (recent)
--
3GPP |   imei: ##
 |  enabled locks: sim, fixed-dialing
 |operator id: 46692
 |  operator name: Chunghwa Telecom
 |   registration: home
 |   packet service state: attached
 |pco:
 | 0: (complete)

  
  [Where problems could occur]
  remove the dependency for intel_iommu, iosm would fit better on other 
platforms not only Intel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998115/+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 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Rear Audio port sometimes has no audio output after reboot(Cirrus
  Logic)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  On the development, we found sometimes there is no audio output device when 
headphone is connected to the rear audio jack.

  [Fix]
  Cirrus Logic provides a patch to fix this
  
https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/

  The patch is included in v6.2-rc1
  9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and 
lock.

  
  [Test]
  Verified by our QA and ODM.

  [Where problems could occur]
  It extends the delay time, should be no harm for existing platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998905/+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 1998883] Re: Micron NVME storage failure [1344, 5407]

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Micron NVME storage failure [1344,5407]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Micron NVME storage fails to init with below error messages
  [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys 
nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting
  [ 8.966111] nvme nvme1: Removing after probe failure status: -22

  [Fix]
  The patch from v5.19 add a quirk for Micron NVME fixes this issue
 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH

  [Test]
  Verified with 5.17 OEM kernel on the reported machine.
  Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be 
compiled.

  [Where problems could occur]
  The impact should be low as it adds one device ID into a quirk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998883/+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 2003053] Re: NFS: client permission error after adding user to permissible group

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  NFS: client permission error after adding user to permissible group

Status in linux package in Ubuntu:
  Fix Committed
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:
  Fix Committed

Bug description:
  [Impact]
  The NFS client's access cache becomes stale due to the user's group 
membership changing on the server after the user has already logged in on the 
client.
  The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or 
timeout (without delegation).
  Adding a user to a group in the NFS server will not cause any file attributes 
to change.
  The client will encounter permission errors until other file attributes are 
changed or the memory cache is dropped.

  [Fix]

  The access cache shall be cleared once the user logs out and logs back
  in again.

  0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache 
upon login
  029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's 
timestamp in rcu path
  5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning

  [Test Plan]
  1.[client side] testuser is not part of testgroup
testuser@kinetic:~$ ls -ld /mnt/private/
drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied
  2.[server side] add testuser into testgroup, which has access to folder
root@kinetic:~$ usermod -aG testgroup testuser &&
echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush
  3.[client side] create a file again but still fail
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied

  [Where problems could occur]
  The fix will apply upstream commits, so the regression can be considered as 
low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+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 2000299] Re: Fix W6400 hang after resume of S3 stress

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix W6400 hang after resume of S3 stress

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  amdgpu hang when stress S3 on AMD W6400 GPU.

  [Fix]
  Add a WA to manually adjust strobe calculation using FCLK restrict.

  [Test]
  Suspend AMD W6400 for 40 times, it works fine.

  [Where problems could occur]
  Low risk, upstream fix.
  It may cause AMD GPU hang.

  The patch is in 5.16, only Jammy kernel needs it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000299/+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 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and
  later

Status in linux package in Ubuntu:
  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 ==

  Since we split the lowlatency kernel into its own source package the
  check in the regression test suite is missing a case and will not run,
  even though the kernel can be booted in a VM instance.

  == Fix ==

  Add the missing case to the test script which is used by ADT testing.
  The test scripts are inherited from the primary/distro kernel. The fix
  should be made there instead of changing the lowlatency tree.

  == Test ==

  Inspecting the ADT logs we should start to see tests executed instead of:
    autopkgtest [19:22:21]: test ubuntu-regression-suite: [-
    ubuntu-regression-suite is pointless, if one cannot boot the kernel

  == Regression Potential ==

  There are a couple of flaky tests which will start to show up, rather
  than only successful runs (which should have been a suspicious thing).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+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 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  5.15.0-58.64 breaks xen bridge networking (pvh domU)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
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

Bug description:
  [Impact]  

   
  Xen guests will not have network access. This fixes a regression due to the 
fix 
 
  for CVE-2022-3643.

   


   
  [Testing] 

   
  This has only been build-tested.  

   


   
  [Potential regression]

   
  Xen guests might not have network access.
  --


  With 5.15.0-58.64-generic, bridge networking on xen is broken :

   no packet (check with tcpdump)  flowing between dom0 and any domUs 
  attached to a network bridge.
   downgrading to  5.15.0-57-generic fix the issue. Thus the patch to the 
netback driver seems the cause.

  relevant network config :

  brtctl show :
  br0   8000.XXXno  eno1
     vif1.0

  relevant domU config :

  kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin'
  type = 'pvh'

  vif = [ 'ip=192.168.10.10 ,bridge=br0' ]

  No message in dmesg, journal, xen logs..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+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 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix speaker mute hotkey doesn't work on Dell G16 series

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

Bug description:
  [Impact]
  Speaker mute and Mic mute hotkey no function on the G16.

  [Fix]
  speaker mute event is sent by EC then dell-wmi can't recognize it.

  Add a new keymap for KEY_MUTE.

  Send for OEM kernels first then will SRU for generic kernel once the
  patch is merged.

  [Test Case]
  1. boot-up with the kernel applied the fix.
  2. Play video/audio.
  3. Press the speak-mute hotkey
  4. can't hear any sounds.

  [Where problems could occur]
  Low, only add a keymap the affect would be very limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2003161/+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 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
  release

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == SRU Justification ==
  Intel has requested the following patches which enable enable Intel_idle for 
eagle stream.

  Intel has customers that would like to use the intel_idle driver on latest 
SPR (Sapphire Rapids).
  These patches have all landed upstream, but are not in Jammy.

  These patches will enable customers to use Ubuntu 22.04 on new hardware
  from Intel.

  
  == Fixes ==
  9edf3c0ffef0 ("intel_idle: add SPR support")
  da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
  3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
  03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
  39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
  7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
  1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")

  
  == Regression Potential ==
  Medium. These patches are specific to enable intel_idle support for Sapphire 
Rapids.  Changes
  are specific to Intel and tested by Intel.

  
  == Test Case ==
  A test kernel was built with these patches and tested by Intel.
  Intel tested on SPR-SP machine and see the correct 190us and 600us residency 
for the C6 state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2003267/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Intel E810 NICs driver in causing hangs when booting and bonds
  configured

Status in linux package in Ubuntu:
  Confirmed
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]
* Intel E810-family NICs cause system hangs when booting with bonding 
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock 
where the RDMA driver waits for the RNL lock to complete removal

  [Test Plan]
* Users have reported that after setting up bonding on switch and server 
side, the system will hang when starting network services

  [Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device, 
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under 
RTNL lock

  [Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
  have been added to a bond
* We should look out for auxiliary devices that haven't been properly
  unplugged, or that cause further issues with
  ice_plug_aux_dev()/ice_unplug_aux_dev()

  
  [Original Description]
  jammy 22.04.1
  linux-image-generic 5.15.0-58-generic
  Intel E810-XXV Dual Port NICs in Dell PowerEdge 650

  - 5.15 in jammy -> reproducible
  - 5.19 in hwe-edge -> reproducible
  - 6.2.rc6 in the mainline build -> works
  - Intel's ice driver 1.10.1.2.2 -> works

  After beonding is enabled on switch and server side, the system will
  hang at initialing ubuntu.  The kernel loads but around starting the
  Network Services the system can hang for sometimes 5 minutes, and in
  other cases, indefinitely.

  The message of:

  echo 0 > /proc/sys/kernel/hung_task_timeout_sec”  systemd-resolve
  blocked for more than 120 seconds

  appears, and eventually the Network services just attempts to start
  and never does.  This is with or without DHCP enabled.

  Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
  linux-oem kernels and all exhibit the same failure.

  To work around this. installing the Intel 'ice' driver of version
  1.10.1.2.2 works.  The system doesn't even remotely hang at startup
  and all networking functions remain working (ping, DNS, general
  accessibility).

  The driver can be found at 
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 13:08 seq
   crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5json:
   {
     "result": "skip"
   }DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia: 
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R650
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags:  jammy 
uec-images
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 2003374] Re: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols

Status in dh-kpatches:
  Unknown
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in kpatch package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in kpatch source package in Jammy:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in kpatch source package in Kinetic:
  Won't Fix

Bug description:
  [ Impact ]

   * When UBSAN is enabled in an s390x kernel configuration, kpatch-
  build can fail to find matching symbols in the vmlinux symbol table
  (see attached example_livepatch.patch). This was discovered in both
  Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled
  (releases up to Focal did not enable UBSAN). See attached kpatch-build
  console output (output.log) and kpatch-build log (build.log).

  * Disabling UBAAN in s390x kernel configurations resolved the issue
  for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in
  kpatch/kpatch-build to continue to enable UBSAN while still allowing
  Livepatch functionality.

  [ Test Plan ]

   * Use kpatch-build testcases to build and load a fs/proc/meminfo.c
  Livepatch on s390x kernel (see attached example_livepatch.patch). This
  should be successful.

  [ Where problems could occur ]

   * A fix in kpatch/kpatch-build to properly handle UBSAN objects
  shouldn't yield any regressions. If UBSAN is disabled to ultimately
  get past this issue, it could lead to undefined behavior not being
  caught.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dh-kpatches/+bug/2003374/+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 2003816] Re: Regression in ext4 during online resize

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Regression in ext4 during online resize

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in cloud-init source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Invalid
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released
Status in linux-gcp source package in Kinetic:
  Fix Released

Bug description:
  Issue

  resize2fs utility is used to resize the filesystem and is idempotent
  in nature. But in the 5.15 kernel, successive execution of resize2fs
  is returning error.

  Reproduction step (on AWS):

  Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 
5.15.0-1022-aws) in us-west-2 region and attach an EBS volume.
  Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p 
/mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0
  Increase the size of EBS volume.
  Run sudo resize2fs /dev/xvdb multiple times.

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  The filesystem is already 5242880 (4k) blocks long.  Nothing to do!

  When you run the same step on the latest image ami-0a1d6d351894df6cc
  (Linux 5.15.0-1026-aws).

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/xvdb
  Couldn't find valid filesystem superblock.


  FIX:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+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 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix the ACPI _CPC not found error from kernel dmesg on some dynamic
  SSDT table loaded firmwares

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

Bug description:
  [Impact]
  Some machines which have dynamically loaded SSDT tables, will not be loaded 
and get the CPPC not worked.

  [Fix]
  Fix the regression by some load supports for CPPC from an SSDT dynamically 
when _OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone.

  [Test]
  Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], 
AE_NOT_FOUND" error exist or not on demesg .

  [Where problems could occur]
  Low risk, It only helps to CPPC support loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+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 2004807] Re: RDMA Back port DMA buffer fix

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  RDMA Back port DMA buffer fix

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  When registering a new DMA MR after selecting the best aligned page size
  for it, we iterate over the given sglist to split each entry to smaller,
  aligned to the selected page size, DMA blocks.

  In given circumstances where the sg entry and page size fit certain
  sizes and the sg entry is not aligned to the selected page size, the
  total size of the aligned pages we need to cover the sg entry is >= 4GB.
  Under this circumstances, while iterating page aligned blocks, the
  counter responsible for counting how much we advanced from the start of
  the sg entry is overflowed because its type is u32 and we pass 4GB in
  size. This can lead to an infinite loop inside the iterator function
  because the overflow prevents the counter to be larger
  than the size of the sg entry.

  Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
  contiguous memory blocks")

  [Test Plan]

  AWS tested

  [Where things could go wrong]

  What could possibly go wrong with Remote DMA scatter/gather list
  errors ?

  [Other Info]

  SF: #00353710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+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 2006453] Re: Fix selftests/ftracetests/Meta-selftests

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix selftests/ftracetests/Meta-selftests

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  == Impact ==
  This subtest checks for bashisms in the test scripts of ftracetests. A recent 
stable change added such a case. This is harmless but causes the Meta-selftests 
to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer 
for test_event_enable" which adds:
  +   if [ "$e" == $val ]; then

  == Fix ==
  Replace the test with
  +   if [ "$e" = $val ]; then

  == Testcase ==
  Running the kernel selftests/ftracetest (done in ADT and RT) should no longer 
show "Meta-selftests" as FAILed.

  == Regression Potential ==
  This affects only the selftest suite and only ftrace subtests. Any change 
would only be observable there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+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 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
  while

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  Audio playback becomes silent on some Intel SoF systems.

  [Fix]
  Revert offending commit.

  [Test]
  The speaker can always play sound after the commit gets reverted.

  [Where problems could occur]
  Audio on linux 5.15 has been working fine without the patch for a long
  time, so this only restore it to where it was.

  == Original Bug Report ==
  [Summary]
  During the kernel SRU testing on focal-hwe, I found the audio output of some 
machines are broken.
  I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and 
haven't seen this happened.

  The volume bars in settings react to what sound is played correctly
  and device is detected as well.

  [Reproduce steps]
  1. install focal
  2. enable -proposed
  3. run apt dist-upgrade.
  4. reboot.
  5. press fn keys to volume up then volume down or play a short youtube video.
  6. after a while can't hear any sound from the speaker.

  [Failure rate]
  10/10

  [Additional info]
  If I run "sudo alsa force-reload" can make audio work again, but after a 
while it breaks again.
  These are machines that impacted by this bug:
  https://certification.canonical.com/hardware/202007-28045/
  https://certification.canonical.com/hardware/201906-27109/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/202007-28047/
  https://certification.canonical.com/hardware/202007-28055/
  https://certification.canonical.com/hardware/202005-27899/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1303 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb 19 21:24:59 2023
  InstallationDate: Installed on 2020-08-03 (930 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: Feb 19 20:53:23 
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7590
  dmi.product.sku: 0922
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+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 2007745] Re: [SRU][Jammy] CONFIG_PCI_MESON is not enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [SRU][Jammy] CONFIG_PCI_MESON is not enabled

Status in linux package in Ubuntu:
  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:
  Fix Released

Bug description:
  SRU justification:

  [ Impact ]

  The PCI driver for the amlogic-based Meson platforms
  (CONFIG_PCI_MESON) is not enabled as a module in the kernel
  configuration: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=master#n7036

  [ Test Plan ]

  Check if pci_meson.ko is compiled and present in the linux-modules
  package.

  [ Where problems could occur ]

  * Enabling the driver could enable undesired dependencies 
  * Kernel module does not compile and breaks the build

  [ Other Info ]

  This driver is important for systems like the ODROID HC4, which uses a
  PCIE-SATA bridge to provide a storage interface. This system is fully
  supported by the kernel (including a device tree), except for the fact
  that this PCI driver is disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+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 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  net:fcnal-test.sh didn't return a non-zero value even with some sub-
  tests failed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  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

Bug description:
  [Impact]
  The net/fcnal-test.sh on F/J won't return a non-zero value even with
  some sub test cases failed, here is an example on Jammy:

   # Tests passed: 857
   # Tests failed: 5
   ok 1 selftests: net: fcnal-test.sh

  Therefore it's marked as PASSED on our report and making it difficult
  to spot these failures:
  # With VRF
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping local, VRF bind - VRF IP [FAIL]
  # TEST: ping local, device bind - ns-A IP [FAIL]
  # SYSCTL: net.ipv4.ping_group_range=0 2147483647
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping local, VRF bind - VRF IP [FAIL]
  # TEST: ping local, device bind - ns-A IP [FAIL]
  # With VRF
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # SYSCTL: net.ipv4.ping_group_range=0 2147483647
  # SYSCTL: net.ipv4.raw_l3mdev_accept=1
  # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL]

  [Fix]
  * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code

  This patch can be cherry-picked into Focal and Jammy kernel.
  We don't have this test in Bionic, and this patch has already landed
  on Kinetic and OEM-5.17

  [Test]
  Run the patched test, the return value will be 1 whenever the number
  of failed test cases is not 0.

  [Where problems could occur]
  Change limited to testing tools, but we're expected to see new failures
  in Jammy. With bug 2006391 fixed later on, we will see failures
  reported in F/K as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+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 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  cpufreq: intel_pstate: Update Balance performance EPP for Sapphire
  Rapids

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  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:
  Fix Released

Bug description:
  [SRU Justification]

  == Impact ==
  See original description. The goal is to adjust the behavior of the balanced 
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there 
should be no impact on laptop users). While the initial request was Jammy/5.15 
only we should do this to Kinetic and Lunar as well so the experience is the 
same regardless of release.

  == Fix ==
  This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model. For Jammy/5.15 this requires one additional change 
  which introduces the EPP tweak for Alderlake.

  == Test case ==
  

  == Regression Potential ==
  The change modifies how quickly CPUs scale up (and probably down) depending 
on workload. Power usage unlikely is of that much concern in server space. 
Maybe increased heat would be observed.
  For Jammy there is the additional risk of havind a different power usage
  on Alderlake which is a Laptop CPU. However that change is part of v5.17
  and thus would already be in effect with current 22.04 HWE.

  == Original description ==

  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.

  Report is published: www.Phoronix.com showing difference of 37%

  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.

  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.

  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.

  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)

  [HW/SW Information]
  Sapphire Rapids

  [Business Justification]
  Performance Improvements

  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008519/+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 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace
  multiple times on Ubuntu 22.04.1 OS during boot

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

Bug description:
  SRU Justification:

  [Impact]

  When booted into Ubuntu 22.04.1 OS after installation, observed "Array
  Index out of bounds" Call Trace multiple times in dmesg.

  Call Trace is as follow:
  [ 6.125704] UBSAN: array-index-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32
  [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'
  [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic 
#59-Ubuntu
  [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022
  [ 6.125710] Workqueue: events work_for_cpu_fn
  [ 6.125716] Call Trace:
  [ 6.125718] 
  [ 6.125720] show_stack+0x52/0x5c
  [ 6.125725] dump_stack_lvl+0x4a/0x63
  [ 6.125731] dump_stack+0x10/0x16
  [ 6.125732] ubsan_epilogue+0x9/0x49
  [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas]
  [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas]
  [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas]
  [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas]
  [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas]
  [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas]
  [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas]
  [ 6.125779] local_pci_probe+0x48/0x90
  [ 6.125783] work_for_cpu_fn+0x17/0x30
  [ 6.125785] process_one_work+0x228/0x3d0
  [ 6.125786] worker_thread+0x223/0x420
  [ 6.125787] ? process_one_work+0x3d0/0x3d0
  [ 6.125788] kthread+0x127/0x150
  [ 6.125790] ? set_kthread_struct+0x50/0x50
  [ 6.125791] ret_from_fork+0x1f/0x30
  [ 6.125796] 
  [ 6.125796] 


  Steps to reproduce:
  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  5. Multiple Call Traces of "array-index-out-of-bounds" are seen

  Expected Behavior:
  OS should boot without this Call Trace

  [Fix]

  [PATCH v3 0/6] Replace one-element arrays with flexible-array members
  
https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/

  48658213 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_PD_CFG_SEQ_NUM_SYNC

  41e83026 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_FW_RAID_MAP

  ee92366a scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_PD_CFG_SEQ_NUM_SYNC

  eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_DRV_RAID_MAP

  204a29a1 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP_DYNAMIC

  ac23b92b scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP

  [Test Plan]

  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  OS should boot without the Call Trace listed in the Impact field

  [Where problems could occur]

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/+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 2008971] Re: Do not sort the task scan result from /proc when synthesizing perf events

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Do not sort the task scan result from /proc when synthesizing perf
  events

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

Bug description:
  [Impact]
  The perf tool use scandir() to iterate threads and sort in alphabetical order 
when synthesizing PERF_RECORD_ events.
  If the process ID is  and it has one thread (tid = 1), the thread 
will be processed before the process.
  It results in PERF_RECORD_FORK events that come before PERF_RECORD_MMAP2 
events.
  The callstack will have missing symbols for threads where `PERF_RECORD_FORK` 
events are processed before the `PERF_RECORD_MMAP2` event for the corresponding 
process. 

  [Fix]
  Do not use alphasort when calling scandir()

  363afa3aef24f5e08df6a539f5dc3aae4cddcc1a (perf synthetic-events: Don't
  sort the task scan result from /proc)

  [Test Plan]
  
  function update_last_pid()
local file  = io.open("/proc/sys/kernel/ns_last_pid", "w")
file:write(9997)
  end

  update_last_pid()
  os.execute("~/reproducer")

  
  #include 
  #include 
  #include 

  constexpr int kThreadNum = 10;

  void thread_job() { sleep(30); }

  int main(void) {
std::thread threads[kThreadNum];

std::cout << "Parent process with pid " << getpid() << std::endl;

for (int i = 0; i < kThreadNum; ++i) {
  threads[i] = std::thread(thread_job);
}

for (int i = 0; i < kThreadNum; ++i) {
  threads[i].join();
}

std::cout << "All threads have finished" << std::endl;
return 0;
  }

  The flow is to set /proc/sys/kernel/ns_last_pid first, which represents the 
last pid allocated in the current pid namespace.
  The script (test.lua) sets ns_last_pid to 9997 and executes the reproducer 
(reproducer.cpp).
  After the reproducer creates ten threads, we execute the perf command as 
follows: perf record -F 49 -e cpu-clock -a -g sleep 20.
  Here is the result of command: perf report -f --tasks --mmaps -D | egrep -i 
'perf_record_fork|perf_record_mmap' | grep 

  Before applying the patch, the output of the perf command was as follows:
  0 0 0x34910 [0x40]: PERF_RECORD_FORK(:1):(:)
  0 0 0x34990 [0x40]: PERF_RECORD_FORK(:10001):(:)
  0 0 0x34a10 [0x40]: PERF_RECORD_FORK(:10002):(:)
  0 0 0x34a90 [0x40]: PERF_RECORD_FORK(:10003):(:)
  0 0 0x34b10 [0x40]: PERF_RECORD_FORK(:10004):(:)
  0 0 0x34b90 [0x40]: PERF_RECORD_FORK(:10005):(:)
  0 0 0x34c10 [0x40]: PERF_RECORD_FORK(:10006):(:)
  0 0 0x34c90 [0x40]: PERF_RECORD_FORK(:10007):(:)
  0 0 0x34d10 [0x40]: PERF_RECORD_FORK(:10008):(:)
  0 0 0x34d90 [0x40]: PERF_RECORD_FORK(:10009):(:)
  0 0 0x34e10 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
  0 0 0x34e90 [0x80]: PERF_RECORD_MMAP2 /: [0x555de0159000(0x1000) @ 
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
  0 0 0x34f10 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd17f8000(0x7c000) @ 
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
  0 0 0x34fa0 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd18f9000(0x195000) @ 
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
  0 0 0x35030 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd1afc000(0x17000) @ 
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
  0 0 0x350c0 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1bb3000(0x11) @ 
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
  0 0 0x35158 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1d4e000(0x2a000) @ 
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  0 0 0x351f0 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffc983bb000(0x2000) @ 0 
00:00 0 0]: r-xp [vdso]
  0 0 0x35260 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000) 
@ 0 00:00 0 0]: --xp [vsyscall]

  After applying the patch, the output of the perf command is as follows:
  0 0 0x30c28 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
  

[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup
  time is taking longer than expected

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

Bug description:
  SRU Justification:

  [Impact]

  A Dell system that has a profile setting of "Performance Per Watt
  (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot
  into OS as quickly as expected.

  How reproducible:

  Steps to Reproduce:

  1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS.
  2. Install Ubuntu-22.04
  3. Boot into OS
  4. Check the bootup time

  Expected results:
  OS should boot normally and need to consume less bootup time

  [Fix]

  13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs

  [Test Plan]

  1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting
  2. Install Ubuntu-22.04
  3. Boot into OS
  4. Check the bootup time

  [Where problems could occur]

  Regression risk: low to medium.

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc

  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+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 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [SRU] Backport request for hpwdt from upstream 6.1 to Jammy

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

Bug description:
  SRU Justification:

  [Impact]

  Please pick up the latest hpwdt from the upstream 6.1 kernel for
  Jammy. This version enables hpwdt on RL300 aarch64.

  [Fix]
  ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING

  891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems.

  [Test Plan]
  Boot system with the hpwdt enabled on an arm64 system

  [Where Problems Could Occur]

  Regression Risk is Low

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1

  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+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 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Currently Ubuntu kernel has this kernel config disabled.
  But in some cases, Intel's Sapphire Rapids High Bandwith
  Memory (SPR-HBM) needs this option.

  Memory bandwidth has been a bottleneck of increasingly memory bound
  workloads. Sapphire Rapids plus HBM is specifically targeted to
  cater to these workloads, traditionally served using overprovisioning
  of memory devices.

  Please search the keyword "fake numa" in
  https://community.intel.com/t5/Blogs/Products-and-
  Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-
  Applications-for/post/1335100

  [Fix]

  Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later

  [Test Plan]
   Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no 
fake NUMA, 2U fake NUMA and 4U fake NUMA).

  * 
https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html
  ** 
https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html

  An improvement to performance on a Sapphire Rapids CPU with HBM should
  be observed

  [Where problems could occur]

  The regression risk is low

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2

  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic

  Lunar
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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 2009024] Re: Fail to output sound to external monitor which connects via docking station

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fail to output sound to external monitor which connects via docking
  station

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  No sound output from the external monitor which connect via some docking 
station. It only happens when user boot the system with docking station 
connected. Re-plug the docking station can fix this issue. Or plug the docking 
station later won't trigger this problem.

  [Fix]
  Turn on the CONFIG_SND_HDA_INTEL_HDMI_SILENT in kernel config. It will start 
sending an "audio keepalive" to the monitor as soon as it is connected.

  [Test]
  Connect the external monitor to the Atomic Type-C Dock (HD22Q) and boot the 
system with the dock connected. Play sound via HDMI/DP port and check if 
there's any audio output from the external monitor.

  [Where problems could occur]
  It sends the "audio keepalive"(silent stream) to the monitor when connected. 
Doesn't affect original workflow of the audio system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2009024/+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 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Fix mediatek wifi driver crash when loading wrong SAR table

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Mediatek MT7922 wifi driver crashed on some laptops.

  [Fix]
  WiFi driver should not continue initializing SAR table when it's
  invalid.

  [Test]
  Verified on hardware and stress netword passed.

  [Where problems could occur]
  Low risk.
  It may cause issues on mt76 driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2009118/+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 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores
  (256)

Status in linux package in Ubuntu:
  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]

  There is a user reporting errors in setup with their Intel E810 NIC with
  error messages saying that the driver cannot allocate enough MSI-X vectors
  on their 256 cpu-count system.

  It seems the ICE ethernet driver has an all or nothing approach to
  allocating MSI-X vectors and could request more MSI-X vectors than it
  finds available, which could lead to the driver failing to initialize and
  start.

  [Fix]

  The patch that fixes this allocates as many MSI-X vectors as it can to 
continue
  functionality by reducing the number of requested MSI-X vectors if it does
  not have enough to do full allocation.

  [Backport]

  In Jammy we do not carry patches for switchdev support in the driver so do not
  allocate the switchdev MSI-X vector for it. Also in Jammy use the older
  way of checking RDMA support by testing the RDMA bit is set as opposed to the 
newer
  ice_is_rdma_ena that the patch uses.

  [Test Plan]

  Install and startup Ice driver with an Intel 800 series NIC and check that we
  do not have the failure:

  Not enough device MSI-X vectors, requested = 260, available = 253

  and check that everything works as expected.

  The backported patch for Jammy has been tested by the original user who
  submited the bug report with their high cpu count system and confirmed no 
errors.

  [Where problems could occur]

  There could be problems with the logic of reducing the MSI-X vector
  usage leading to more errors in the driver, but otherwise minimal
  regression potential as the code is mostly refactoring initial MSI-X
  setup.

  
  --

  System Configuration
  OS: Ubuntu 22.04 LTS
  Kernel: 5.15.0-25-generic
  CPUs: 256
  NIC: Intel E810 NIC with 512 MSIx vectors each function

  Errors
  Not enough device MSI-X vectors, requested = 260, available = 253

  Findings
  (1) the current ice kernel driver (ice_main.c) will pre-allocate all 
required number of msix (even it's not enough for big core CPUs)
  (2) the commit 
https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99
 has improved this logic, and it seems merged into kernel version from v6.1

  So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu
  kernel backport above patch to the current kernel (v5.15) ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012335/+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 2011616] Re: Connection timeout due to conntrack limits

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Connection timeout due to conntrack limits

Status in linux package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-gcp source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-gcp source package in Lunar:
  New

Bug description:
  Customers of GKE 1.25 and 1.26 are affected by the conntrack
  performance issue that causes random connection timeouts. The fix has
  been committed to to the upstream's net git repo and to prodkernel and
  needs to be backported to Ubuntu versions with kernel 5.15.

  https://partnerissuetracker.corp.google.com/issues/272090522

  Fix:

  
https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

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

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or 

[Kernel-packages] [Bug 2011926] Re: Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs"

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue
  pfifo child qdiscs"

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

Bug description:
  Upstream commit: af7b29b1deaac6da3bb7637f0e263dfab7bfc7a3

  Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo 
child qdiscs"
  taprio_attach() has this logic at the end, which should have been
  removed with the blamed patch (which is now being reverted):

/* access to the child qdiscs is not needed in offload mode */
if (FULL_OFFLOAD_IS_ENABLED(q->flags)) {
kfree(q->qdiscs);
q->qdiscs = NULL;
}

  because otherwise, we make use of q->qdiscs[] even after this array was
  deallocated, namely in taprio_leaf(). Therefore, whenever one would try
  to attach a valid child qdisc to a fully offloaded taprio root, one
  would immediately dereference a NULL pointer.

  $ tc qdisc replace dev eno0 handle 8001: parent root taprio \
num_tc 8 \
map 0 1 2 3 4 5 6 7 \
queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \
max-sdu 0 0 0 0 0 200 0 0 \
base-time 200 \
sched-entry S 80 2 \
sched-entry S a0 2 \
sched-entry S 5f 6 \
flags 2
  $ max_frame_size=1500
  $ data_rate_kbps=2
  $ port_transmit_rate_kbps=100
  $ idleslope=$data_rate_kbps
  $ sendslope=$(($idleslope - $port_transmit_rate_kbps))
  $ locredit=$(($max_frame_size * $sendslope / $port_transmit_rate_kbps))
  $ hicredit=$(($max_frame_size * $idleslope / $port_transmit_rate_kbps))
  $ tc qdisc replace dev eno0 parent 8001:7 cbs \
idleslope $idleslope \
sendslope $sendslope \
hicredit $hicredit \
locredit $locredit \
offload 0

  Unable to handle kernel NULL pointer dereference at virtual address 
0030
  pc : taprio_leaf+0x28/0x40
  lr : qdisc_leaf+0x3c/0x60
  Call trace:
   taprio_leaf+0x28/0x40
   tc_modify_qdisc+0xf0/0x72c
   rtnetlink_rcv_msg+0x12c/0x390
   netlink_rcv_skb+0x5c/0x130
   rtnetlink_rcv+0x1c/0x2c

  The solution is not as obvious as the problem. The code which deallocates
  q->qdiscs[] is in fact copied and pasted from mqprio, which also
  deallocates the array in mqprio_attach() and never uses it afterwards.

  Therefore, the identical cleanup logic of priv->qdiscs[] that
  mqprio_destroy() has is deceptive because it will never take place at
  qdisc_destroy() time, but just at raw ops->destroy() time (otherwise
  said, priv->qdiscs[] do not last for the entire lifetime of the mqprio
  root), but rather, this is just the twisted way in which the Qdisc API
  understands error path cleanup should be done (Qdisc_ops :: destroy() is
  called even when Qdisc_ops :: init() never succeeded).

  Side note, in fact this is also what the comment in mqprio_init()
  says:

  /* pre-allocate qdisc, attachment can't fail */

  Or reworded, mqprio's priv->qdiscs[] scheme is only meant to serve as
  data passing between Qdisc_ops :: init() and Qdisc_ops :: attach().

  [ this comment was also copied and pasted into the initial taprio
commit, even though taprio_attach() came way later ]

  The problem is that taprio also makes extensive use of the q->qdiscs[]
  array in the software fast path (taprio_enqueue() and taprio_dequeue()),
  but it does not keep a reference of its own on q->qdiscs[i] (you'd think
  that since it creates these Qdiscs, it holds the reference, but nope,
  this is not completely true).

  To understand the difference between taprio_destroy() and mqprio_destroy()
  one must look before commit 13511704f8d7 ("net: taprio offload: enforce
  qdisc to netdev queue mapping"), because that just muddied the waters.

  In the "original" taprio design, taprio always attached itself (the root
  Qdisc) to all netdev TX queues, so that dev_qdisc_enqueue() would go
  through taprio_enqueue().

  It also called qdisc_refcount_inc() on itself for as many times as 

[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Kernel livepatch ftrace graph fix

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  * Additional patch required to support Livepatch for s390x
  * Fixes Livepatch transition issues when using ftrace graph tracing

  [Test Case]
  * Compile test
  * Boot test
  * Test a Livepatch (patch to /proc/meminfo module)
  * Test Livepatch from ftrace graphed function (via 
https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh)

  [Where things could go wrong]
  * Functionality already exists upstream, once kernel is boot and Livepatch 
tested - should have no regressions

  [Other info]
  * Additional required patch was identified 
(https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1)
 due to ftrace graph livepatch transition issue 
(https://github.com/SUSE/qa_test_klp/issues/17).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  kernel: fix __clear_user() inline assembly constraints

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
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:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * In case clear_user() crosses two pages and faults on the second page
 the kernel may write lowcore contents to the first page, instead of
     clearing it.

   * The __clear_user() inline assembly misses earlyclobber constraint
     modifiers. Depending on compiler and compiler options this may lead to
     incorrect code which copies kernel lowcore contents to user space 
 instead of clearing memory, in case clear_user() faults.

  [Fix]

   * For Kinetic and Jammy cherrypick of
 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3
 "s390/uaccess: add missing earlyclobber annotations to __clear_user()"

   * For Focal and Bionic a backport of the above commit is needed:
 https://launchpadlibrarian.net/659551648/s390-uaccess.patch

  [ Test Plan ]

   * A test program in C is needed and used for testing.

   * The test will be done by IBM.

  [ Where problems could occur ]

   * The modification is limited to function 'long __clear_user'.

   * And there, just to one inline assembly constraints line.

   * This is usually difficult to trace.

   * A erroneous modification may lead to a wrong behavior in
     'long __clear_user',

   * and maybe returning a wrong size (in uaccess.c).

  [ Other Info ]

   * This affects all Ubuntu releases in service, down to 18.04.

   * Since we are close to 23.04 kernel freeze, I submit a patch request for
     23.04 separately, and submit the SRU request for the all other
     Ubuntu releases later.

  __

  Description:   kernel: fix __clear_user() inline assembly constraints

  Symptom:   In case clear_user() crosses two pages and faults on the
     second page the kernel may write lowcore contents to the
     first page, instead of clearing it.

  Problem:   The __clear_user() inline assembly misses earlyclobber
     constraint modifiers. Depending on compiler and compiler
     options this may lead to incorrect code which copies kernel
     lowcore contents to user space instead of clearing memory,
     in case clear_user() faults.

  Solution:  Add missing earlyclobber constraint modifiers.
  Preventive:yes

  Upstream-ID:   89aba4c26fae4e459f755a18912845c348ee48f3

  Affected Releases:
     18.04
     20.04
     22.04
     22.10
     23.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2013209] Re: expoline.o is packaged unconditionally for s390x

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  expoline.o is packaged unconditionally for s390x

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-hwe-5.15 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:
  Fix Released

Bug description:
  https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN
  for s390x in Jammy. While this works as expected on Jammy, it won't
  work on some derivatives of it: for example focal:hwe-5.15. On Focal,
  this config can't be enabled due to the GCC version it comes with.
  CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with
  90400.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+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 2015097] Re: Kernel crash during Mellanox performance testing

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Kernel crash during Mellanox performance testing

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

Bug description:
  [Impact]

  * When performance testing using Mellanox driver, an early decrement
  within an if condition rather than as a result of an if condition is
  causing null pointer crashes.

  [Fix]

  * Clean cherry-pick from upstream 
(https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/)
  * Change landed v5.19 upstream, Kinetic onward not affected

  [Test Case]

  * Compile test
  * Boot test
  * Performance test

  [Where things could go wrong]

  * Regression risk is low, localized fix, purely fixes incorrect logic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+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 2015956] Re: selftest: fib_tests: Always cleanup before exit

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
   selftest: fib_tests: Always cleanup before exit

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Copied from the commit message:
  Usage of `set -e` before executing a command causes immediate exit
  on failure, without cleanup up the resources allocated at setup.
  This can affect the next tests that use the same resources,
  leading to a chain of failures.

  A simple fix is to always call cleanup function when the script exists.
  This approach is already used by other existing tests.

  [Fix]
  * b60417a9f2 selftest: fib_tests: Always cleanup before exit

  This patch can be cherry-picked into affected kernels.

  [Test]
  Run the patched fib_tests.sh on KVM kernels, which is expected to fail 
  due to bug 2007458.
  Check with `ip netns`, the ns1 added during setup() should be removed.

  [Where problems could occur]
  Test robustness improvement, this should not break things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+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 2015855] Re: Add split lock detection for EMR

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Add split lock detection for EMR

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

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU. 
  It was backported to Jammy in #lp2015372
   
  The remaining feature needed to fully support EMR is the split lock detection 
mechanism.
  So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is 
supported or not, but this is not architectural, meaning that this should be 
trusted only if it’s confirmed that a specific CPU model implements it. This 
lead to a mapping between a CPU model and whether it supports split lock 
detection by default (no need to check IA32_CORE_CAPABILITIES) or they may 
support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be 
checked.

  With more and more CPU models, this becomes hard to maintain. Moreover, the 
December 2022 edition of the Intel Instruction Set Extensions manual defined 
that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and 
retrospectively always has been) architectural. Documentation also mentions 
  “All processors that enumerate support for MSR_IA32_CORE_CAPS and set 
MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.”

  Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8:
  “ x86/split_lock: Enumerate architectural split lock disable bit” from 
linux-next removes the need of adding a new CPU model in that mapping.

  This is needed to support split lock detection for the new EMR CPU and future 
models that don’t suffer architectural changes.
   
  [Testing]
   Kernel was built on cbd and boot tested on a VM.
  Intel was asked to install and test the new kernel from this ppa 
https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855

  [Regression potential]
   Very low, it is a small refactor and in essence, it does the exact same 
thing for existing cpu models:
  1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes 
the mechanism is supported.
  2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES 
without the extra step of checking the map if the CPU supports this (which was 
always true)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015855/+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 2015372] Re: Add support for intel EMR cpu

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Intel has introduced support for their new Emerald Rapids CPU.
  This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
  and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.

  More information about each commit is addressed inline.

  [Commits]

  1. 9c252ecf3036:
  "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  Adjusted the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  2. 5a8a05f165fb18d37526062419774d9088c2a9b9
  "perf/x86/intel/cstate: Add Emerald Rapids"
  Small context adjustment in intel_cstates_match array
  because of missing SPR, RPL and MDL cpu models introduced in
  528c9f1daf20d

  3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  "perf/x86/rapl: Add support for Intel Emerald Rapids"

  Context adjustment due to missing 
  - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
  - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
  - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
  - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"

  4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick

  5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick

  6. 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick

  7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick

  8. e4b2bc6616e21
  clean cherry-pick

  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  Very low, these are minimal new features, which actually reuse a lot of the 
existing cpu structures/functions.

  

  The following changes since commit
  8feeaa9039a290b978e7855ab82955cd9348fc13

  "platform/x86: intel-uncore-freq: add Emerald Rapids support"

  are available in the Git repository at:

    git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy
  lp2015372

  for you to fetch changes up to commit
  7d88565e6777082265b373733fd93eb3e0914e12

  "EDAC/i10nm: Add Intel Emerald Rapids server support"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015372/+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 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  Fix Released
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:
  Fix Released

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions


-- 
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 2019000] Re: Use new annotations model

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Use new annotations model

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Focal:
  Triaged
Status in linux-gcp source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Confirmed
Status in linux-gcp source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Starting with lunar we have introduced a new way to manage kernel
  configs, unifying the duplicated information defined in the
  annotations file + config chunks into an annotations-only model.

  [Test case]

  A kernel build can be considered a valid test case, in particular the
  specific command that is used to update the .config's for all the
  supported architectures and flavours:

   $ fakeroot debian/rules updateconfigs

  [Fix]

  Import the required changes in debian/ from lunar (with the required
  adjustments) to support the annotations-only model also in all the
  previous releases.

  [Regression potential]

  We may experience regressions during the updateconfigs step,
  especially with derivatives. Moreover, derivatives that want to
  transition to the new annotations model require to adjust the header
  in the annotations file as following (make sure to define the
  corresponding architectures and flavours):

  # FORMAT: 4
  # ARCH: amd64 arm64 armhf ppc64el s390x
  # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k 
arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae 
ppc64el-generic s390x-generic

  After adjusting the header a special command is provided to transition
  to the new annotations-only model:

   $ fakeroot debian/rules migrateconfigs

  This command should automatically import the old configs into the new
  annotations file.

  A kernel with this change applied can still support the old
  annotations+configs model, the transition to the new model is not
  mandatory.

  Basically without using `fakeroot debian/rules migrateconfigs` the
  updateconfigs step will continue to use the old model and the old
  scripts (that is the safest approach to avoid potential unexpected
  .config changes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  A deadlock issue in scsi rescan task while resuming from S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  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:
  Fix Released
Status in linux source package in Lunar:
  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 linux source package in Mantic:
  Fix Released
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  During the S3 stress test, the system sometimes hangs when resuming. This is 
due to the SCSI rescan task being unable to acquire the mutex lock during the 
resumption from S3. The mutex lock has already been acquired by EH and is 
waiting for the device to be ready for a rescan. Unfortunately, the mutex lock 
is never released by either party, leading to a deadlock.

  [Fix]
  Kaiheng submitted a patch to fix this issue which defers the rescan if the 
disk is still suspended so the resume process of the disk device can proceed.
  
https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/

  Since the patch has not been accepted by the upstream yet, so submit
  it to the OEM kernel for now.

  The similiar patch has been included in v6.4-rc7
  6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume

  [Test]
  Verified on the machines by me and ODM.

  [Where problems could occur]
  It only defers the rescan task, and should not have any impact to current 
systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2016269] Re: conntrack mark is not advertised via netlink

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  conntrack mark is not advertised via netlink

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

Bug description:
  SRU justification sent to ML:

  [Impact]
  There was a commit 95fcb42e5f20
  ("netfilter: ctnetlink: fix compilation warning after data race fixes in ct 
mark")
  that introduces a regression where the "mark" variable is no longer
  dumped in netlink netfilter conntrack messages, which userspace tools use
  to mark and track connections.

  [Fix]
  Introduce the upstream fix 9f7dd42f0db1
  ("netfilter: ctnetlink: revert to dumping mark regardless of event type")
  that always dumps the 'mark' variable for conntrack entries.
  This fix has also landed in 5.15 upstream stable.

  [Test]
  Run 'conntrack -E' and check the output of connection entries.

  The 'mark' variable should now be present in connection entries after
  the fix.

  before fix:
  > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345 
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
  after fix:
  > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345 
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1

  [Where problems could occur]
  The fixes are pretty straight forward so regression potential should be
  minimal. 


  
  

  [Impact]

  The last merge of the v5.15 stable (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
  introduced a bug on netlink netfilter conntrack messages.

  The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix 
compilation warning after data race fixes in ct mark"):
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20

  This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter: 
ctnetlink: revert to dumping mark regardless of event type"):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1

  which has been backported in v5.15.103:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c

  [Test Case]

  Run 'conntrack -E' and check the output.

  Before the problematic commit:
  > tcp  6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] 
mark=0 use=1

  'mark=' is seen on connrtack event

  after:
  > tcp  6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1

  => 'mark=' is not seen.

  [Regression Potential]

  The patch is quite simple. It has been backported in the official 5.15
  stable. The risk of regression should be contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+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 2019131] Re: Add PPIN support for Intel EMR cpu

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Add  PPIN support for Intel EMR cpu

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

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU.
  It was backported to Jammy in #lp2015372 and in #lp2015855.

  The remaining feature needed to fully support EMR is PPIN (the Protected 
Processor Inventory/Identification Number).
  This was recently pushed to upstream in 6.4 in commit 
36168bc061b4368ad19e82b06a6463c95d3bb9a7.
  The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X 
in the cpuids table where cpus that support ppin are listed. The table is then 
used in `ppin_init`.

  In Jammy, this implementation is missing. Both Amd and Intel have their own 
implementation which is doing pretty much the same. Instead of a list of cpus 
supported, a switch case is used instead in their init functions 
(amd_detect_ppin and intel_ppin_init).
  To reduce duplication of code and to help backport smoothly the new addition 
of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918
  “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too.

  Thus commits: 
  - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD 
ppin_init() functions"
  - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids 
to list of CPUs that support PPIN"
  are needed to support PPIN for EMR.

  [Testing]
   Kernel was built on cbd and boot tested on a VM.

  [Regression potential]
   Very low, it is a small refactor that removes duplication and it should not 
affect the functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+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 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Enable Tracing Configs for OSNOISE and TIMERLAT

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  In Progress

Bug description:
  == SRU Justification ==
  These config changes will allow tracing with the OSNOISE and TIMERLAT tracing 
tools.

  These tracers can be enabled at run-time and should not affect
  performance or add any additional overhead.

  == Fix ==
  UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs

  == Regression Potential ==
  Low.  These config changes will just allow the use of tracing tools.

  == Test Case ==
  Test build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  In Progress
Status in linux-kvm source package in Mantic:
  In Progress
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Encountering an issue with memcpy_fromio causing failed boot of SEV-
  enabled guest

Status in linux package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  When launching a SEV-enabled guest, the guest kernel panics with the 
following call trace,
  indicating a critical error in the system.

  ==
  [1.090638] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers
  [1.092105] Linux agpgart interface v0.103
  [1.092716] BUG: unable to handle page fault for address: 9b820003d068
  [1.093445] #PF: supervisor read access in kernel mode
  [1.093966] #PF: error_code(0x) - not-present page
  [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 
8001001da067 PTE 8000fed40173
  [1.094629] Oops:  [#1] SMP NOPTI
  [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic 
#49-Ubuntu
  [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 
02/06/2015
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 
0002
  [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 
9b820001ba90
  [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 
0f80
  [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 
8cc7068eca48
  [1.094629] R13: 8cc700a64288 R14:  R15: 
fed40080
  [1.094629] FS:  () GS:8cc77bd0() 
knlGS:
  [1.094629] CS:  0010 DS:  ES:  CR0: 80050033
  [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 
00350ee0
  [1.094629] Call Trace:
  [1.094629]  
  [1.094629]  crb_map_io+0x315/0x870
  [1.094629]  ? radix_tree_iter_tag_clear+0x12/0x20
  [1.094629]  ? _raw_spin_unlock_irqrestore+0xe/0x30
  [1.094629]  crb_acpi_add+0xc2/0x140
  [1.094629]  acpi_device_probe+0x4c/0x170
  [1.094629]  really_probe+0x222/0x420
  [1.094629]  __driver_probe_device+0x119/0x190
  [1.094629]  driver_probe_device+0x23/0xc0
  [1.094629]  __driver_attach+0xbd/0x1e0
  [1.094629]  ? __device_attach_driver+0x120/0x120
  [1.094629]  bus_for_each_dev+0x7e/0xd0
  [1.094629]  driver_attach+0x1e/0x30
  [1.094629]  bus_add_driver+0x139/0x200
  [1.094629]  driver_register+0x95/0x100
  [1.094629]  ? init_tis+0xfd/0xfd
  [1.094629]  acpi_bus_register_driver+0x39/0x50
  [1.094629]  crb_acpi_driver_init+0x15/0x1b
  [1.094629]  do_one_initcall+0x48/0x1e0
  [1.094629]  do_initcalls+0x12f/0x159
  [1.094629]  kernel_init_freeable+0x162/0x1b5
  [1.094629]  ? rest_init+0x100/0x100
  [1.094629]  kernel_init+0x1b/0x150
  [1.094629]  ? rest_init+0x100/0x100
  [1.094629]  ret_from_fork+0x22/0x30
  [1.094629]  
  [1.094629] Modules linked in:
  [1.094629] CR2: 9b820003d068
  [1.094629] ---[ end trace 3d6d81c42a3c2030 ]---
  [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50
  [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 
c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02  a5 f6 
c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66
  [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212
  [1.094629] 

[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  support python < 3.9 with annotations

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  At the moment we can't use the annotations scripts in focal, because
  we are using the'|=' update operator for merging dicts, that has been
  introduced with python 3.9.

  Rewrite the code that is using this operator in a more portable way
  and apply this change everywhere, so that annotations will work on any
  backport/derivative kernels.

  [Test case]

  Run `fakeroot debian/rules updateconfigs` in focal (using the new
  annotations model).

  [Fix]

  Try to use the '|=' operator in a try/except block, if it fails
  fallback to a more portable way.

  [Regression potential]

  With this change applied we may experience regressions during the
  updateconfigs phase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+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 2020413] Re: fix typo in config-checks invocation

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  fix typo in config-checks invocation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  After migrating to the new annotations-only model in jammy we
  introduced a typo in debian/rules.d/4-checks.mk, that is triggered if
  we opt to not migrate to the new model and still use the old
  configs+annotations.

  [Test case]

  With debian./config/config.common.ubuntu present run the
  following command:

   $ fakeroot debian/rules clean updateconfigs

  [Fix]

  Replace @perl -> perl.

  [Regression potential]

  It's a trivial typo fix. Regressions can be introduced only if we are
  still using the old configs+annotations model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+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 2022098] Re: Severe NFS performance degradation after LP #2003053

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Severe NFS performance degradation after LP #2003053

Status in linux package in Ubuntu:
  Confirmed
Status in linux-gke package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-gke source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-gke source package in Jammy:
  Fix Released

Bug description:
  The fix to LP #2003053 has caused massively increased NFS server
  access in some use-cases, which caused severe performance degradation
  to the point of being unusable in some cases.

  The solution to this issue, at least temporarily and at least for
  linux-gke, is to make the new behaviour optional using the
  "nfs_fasc=1" module parameter. Without this parameter specified, (or
  specified as =0) will keep the old behaviour.

  
  Regresion potential:
   - Regression potential is considered low considering the scope of the change 
and is limited to NFS only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+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 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  Incomplete
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:
  Fix Released

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  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:
  Fix Released

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2

  [Fix]
  Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

  These 2 patches are already in Unstable and OEM-6.1 already got them
  via stable updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023539/+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 2023311] Re: Resolve synchronous exception on arm64

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Resolve synchronous exception on arm64

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

Bug description:
  SRU Justification

  [Impact]

  MSFT has requested the inclusion of commit
  e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64: efi: Recover from
  synchronous exceptions occurring in firmware'). It looks generic
  enough to apply to the master kernel.

  Unlike x86, which has machinery to deal with page faults that occur
  during the execution of EFI runtime services, arm64 has nothing like
  that, and a synchronous exception raised by firmware code brings down
  the whole system.

  [Test Plan]

  This looks like a hard one to reproduce. Boot and regression testing
  should be sufficient.

  [Regression Potential]

  Firmware exceptions could still take down the system.

  [Other Info]

  SF: #00362062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023311/+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 2023650] Re: Add microphone support of the front headphone port on P3 Tower

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Add microphone support of the front headphone port on P3 Tower

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The 3.5mm headphone port in front panel cannot detect the microphone. 

  [Fix]
  Add quirk for headset mic pin on P3 Tower.

  [Test]
  Tested with alsa audio, mic works fine.

  [Where problems could occur]
  Low risk to add specific hardware ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023650/+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 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present

Status in linux package in Ubuntu:
  Fix Committed
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:
  Won't Fix
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  If the daemon is started and the vmbus is not present it will just
  exit with an error: https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424

  Thus, it would make sense to add
  "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools-
  common.hv-kvp-daemon.service to prevent systemd from starting the
  daemon if the device is not there.

  [Test Plan]

  Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that 
hv-kvp-daemon is running.
  Start a non-Azure cloud instance and check that hv-kvp-daemon is not running.

  
  [Regression potential]

  Its possible that kv-hvp-daemon is not started when it should be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+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 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 
verification-needed-focal-linux-aws-5.15

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

Title:
  libgnutls report "trap invalid opcode" when trying to install packages
  over https

Status in ubuntu-kernel-tests:
  New
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in gnutls28 source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in gnutls28 source package in Jammy:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in gnutls28 source package in Lunar:
  Confirmed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When booting linux with Gather Data Sampling mitigations without updated 
microcode on an affected CPU, AVX will be disabled. This will cause programs 
connecting to https using gnutls on Jammy to break, including apt and git.

  [Test case]
  git clone 
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
  Cloning into 'autotest-client-tests'...
  error: git-remote-https died of signal 4

  dmesg:
  [  806.072080] traps: git-remote-http[2561] trap invalid opcode 
ip:7fa2e7dac44a sp:7ffed6796480 error:0 in 
libgnutls.so.30.31.0[7fa2e7c85000+129000]

  Works fine with the mitigation disabled by default.

  [Potential regressions]
  Users booting on affected parts without microcode updates will be subject to 
Gather Data Sampling attacks (which can be done by local untrusted attackers), 
which may leak confidential data, including keys.

  
  -

  When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be 
the only affected instance) with Jammy 5.15.0-81-generic, it will get 
interrupted with:
  E: Method https has died unexpectedly!
  E: Sub-process https received signal 4.

  $ sudo apt install linux-libc-dev
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
    linux-libc-dev
  0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded.
  Need to get 1353 kB of archives.
  After this operation, 6943 kB of additional disk space will be used.
  E: Method https has died unexpectedly!
  E: Sub-process https received signal 4.

  From dmesg you will see:
  [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be 
sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000]

  Also, git clone is not working as well.

  $ git clone --depth=1 
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
  Cloning into 'autotest-client-tests'...
  error: git-remote-https died of signal 4

  dmesg:
  [  806.072080] traps: git-remote-http[2561] trap invalid opcode 
ip:7fa2e7dac44a sp:7ffed6796480 error:0 in 
libgnutls.so.30.31.0[7fa2e7c85000+129000]

  libgnutls30 version:3.7.3-4ubuntu1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+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 2015397] Re: [Lenovo Legion 5i pro] 90 second delay during boot (Failed to start systemd-backlight@backlight:nvidia_0.service)

[Francois Thirioux]

Solved in recent kernels and/or nvidia drivers

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [Lenovo Legion 5i pro] 90 second delay during boot (Failed to start
  systemd-backlight@backlight:nvidia_0.service)

Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Lunar, 525.105.17

  I get a very very very slow boot using dynamic graphics in my Lenovo Legion 
5i pro i7/3070 Ti.
  Using discrete graphics is ok.
  Using Nouveau with hybrid graphics is ok.

  After some research, it seems the culprit is:

  Failed to start systemd-backlight@backlight:nvidia_0.service -
  Load/Save Screen Backlight Brightness of backlight:nvidia_0.

  systemd blame:

  1min 34.046s plymouth-quit-wait.service
  1min 30.278s gpu-manager.service

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

Re: [Kernel-packages] [Bug 2029332] Re: Reboot command powers off the system

[ogwel emmanuel]

not solved

On Sat, 9 Sept 2023 at 14:26, Ubuntu Kernel Bot <2029...@bugs.launchpad.net>
wrote:

> This bug is awaiting verification that the linux-
> aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
> Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-jammy-linux-
> aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
> still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
> to 'verification-failed-jammy-linux-aws-6.2'.
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2
> verification-needed-jammy-linux-aws-6.2
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2032786).
> https://bugs.launchpad.net/bugs/2029332
>
> Title:
>   Reboot command powers off the system
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux-hwe-6.2 package in Ubuntu:
>   Confirmed
> Status in linux-hwe-6.2 source package in Jammy:
>   Fix Released
> Status in linux source package in Lunar:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   Issue: When a reboot (or init 6) command is issued the server shuts
>   down instead.
>
>   Expected behaviour: To reboot and NOT shutdown
>
>   Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core
>   count greater than 16 (like 24,28 or 32)
>
>   Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15
>
>   When the CPU count is 1, issue is not observed. When core count is
>   less than 24 (like 16) issue not observed.
>
>   [Fix]
>
>   Problem introduced in v5.18 with commit:
>   08f253ec3767 x86/cpu: Clear SME feature flag when not in use
>
>   Fixes for the above:0
>   9b040453d444 x86/smp: Dont access non-existing CPUID leaf
>   1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust
>
>   [Test Case]
>
>   $ sudo reboot
>   Server should reboot and not power off.
>
>   [Where Problems Could Occur]
>
>   The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines
>   could be affected.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+subscriptions
>
>

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

Title:
  Reboot command powers off the system

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  Issue: When a reboot (or init 6) command is issued the server shuts
  down instead.

  Expected behaviour: To reboot and NOT shutdown

  Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core
  count greater than 16 (like 24,28 or 32)

  Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15

  When the CPU count is 1, issue is not observed. When core count is
  less than 24 (like 16) issue not observed.

  [Fix]

  Problem introduced in v5.18 with commit:
  08f253ec3767 x86/cpu: Clear SME feature flag when not in use

  Fixes for the above:0
  9b040453d444 x86/smp: Dont access non-existing CPUID leaf
  1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust

  [Test Case]

  $ sudo reboot
  Server should reboot and not power off.

  [Where Problems Could Occur]

  The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines
  could be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+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 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  losetup with mknod fails on jammy with kernel 5.15.0-69-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

   * Regression in the loop block driver in Jammy kernel
     between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable),
     due to a change in the default behavior (value) of
     kernel parameter `max_loop` (from 0 to 8) in commit:
     `loop: Fix the max_loop commandline argument treatment
     when it is set to 0` (comment #6).

   * Users of loop devices (major 7) with minor >= 8 now
     fail to `open()` a loop device created with `mknod()`.

   * This is a corner case, as most people use `losetup`
     with usual /dev/loopNUMBER (or `--find`) which are
     not affected as it uses a different code path.
     (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.)

   * Workaround: kernel parameter `max_loop=0`.

  [ Test Steps ]

   * Run the test cases (losetup and test-loop.c in comment #6):
     - max_loop not set (default)
     - max_loop=0
     - max_loop=8

   * Verify the default behavior (max_loop not set) is restored.

   * Verify the modified behavior (max_loop is set) is unchanged.

  [ Regression Potential ]

   * Regressions would be limited to the loop block driver,
     more specifically its default behavior (but it's that now)
     or specific usage of max_loop parameter (tested; looks OK).

  [ Other Info ]

   * Patch 1 [1] is not quite a fix, but adds CONFIG guards that
 Patch 2 [2] depends on. (Alternatively, a Patch 2 backport
 with that could be done, but Patch 1 seems trivial enough.)

   * The fix on Jammy is only Patch 2, with a trivial backport
 (that CONFIG option is not in Jammy/v5.15, only in v5.18).

   * The fix on Lunar is both patches; clean cherry-picks.

   * The fix on Mantic is both patches too,
 now in v6.5-rc3, which should be automatically incorporated
 as Mantic apparently will release with the 6.5 kernel [3]

     [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358
     [2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a
     [3] 
https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release

  Original Description:
  ---

  losetup fails with devices created manually by mknod on kernel
  5.15.0-69-generic

  # fallocate -l 1G test
  # mknod -m 660 /dev/loop8 b 7 8
  # chown root:disk /dev/loop8
  # losetup /dev/loop8 ./test
  losetup: ./test: failed to set up loop device: Device or resource busy

  Possibly as a result of this patch:
  
https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/

  which was introduced in 5.15.0-68:
  
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

  On a machine prior to this change (no issue with losetup):
  # cat /sys/module/loop/parameters/max_loop
  0
  # uname -r
  5.15.0-58-generic

  On a machine after the change (has losetup issue as described above):
  # cat /sys/module/loop/parameters/max_loop
  8
  # uname -r
  5.15.0-69-generic

  So it looks like the default changed and the max amount of loop
  devices that can be created with mknod (not loop-control) is 8. If we
  set max_loop=0 on the kernel command line, it works as before. Cannot
  unload and reload module on a running system to change the parameter
  because it is built into the kernel.

  Another workaround is to use `losetup --find` but that means you
  cannot create with named devices created with mknod.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  stacked overlay file system mounts that have chroot() called against
  them appear to be getting locked (by the kernel most likely?)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Impact]

  Opened files reported in /proc/pid/map_files can be shows with the
  wrong mount point using overlayfs with filesystem namspaces.

  This incorrect behavior is fixed:

UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
  map_files

  However, the fix introduced a new regression, the reference to the
  original file stored in vma->vm_prfile is not properly released when
  vma->vm_prfile is replaced with a new file.

  This can cause a reference counter unbalance, leading errors such as
  "target is busy" when trying to unmount overlayfs, even if the
  filesystem has not active reference.

  [Test case]

  Reproducer provided by original bug reporter:
  https://launchpadlibrarian.net/663151659/overlayfsscript_example

  [Fix]

  Fix by properly releasing the original file stored in vm_prfile.

  [Regression potential]

  This fix seems to solve the reported bug (verified with the
  reproducer) and it doesn't seem to introduce other regressions or
  behavior change.

  However, we may experience regressions in overlayfs or potentially
  other "target is busy" errors when unmounting overlayfs filesystems
  with this fix applied, if there are still other corner cases not
  covered properly.

  [Original bug report]

  Hi

  BACKGROUND:
  ---
  I have a set of scripts that debootstraps and builds vanilla Debian installs, 
where the only modifications are what packages are installed. Then that becomes 
the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and 
then that becomes the chroot where config changes are made with more scripts. 
This overlayfs is mounted in its own mount namespace as the script is unshare'd

  Within these scripts, I make packages with a fork of checkinstall I
  made which uses the / as the lowerdir, as overlayfs allows that, a
  tmpfs as the upperdir, the install command is run with chroot, and
  then the contents are copied.

  THE ISSUE:
  --
  I noticed that it appears that my ramdisks are remaining in memory, I have 
isolated it out to the overlayfs mounts with the overlayfs as the lowerdir 
where chroot is being called on it. I tried entering the namespace myself and 
umounting it, and notice I get the error "Target is busy"

  With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and
  `lsfd` as much as I could, but every user mode tool shows absolutely
  NO files open at all

  I was using Kubuntu 18.04, it was an old install and 32 bit, so I had
  no upgrade path to be using more recent versions. Now I am on 23.04,
  but I also think this is happening on a 22.10 laptop

  DIAGNOSIS:
  --
  I am able to isolate it out, and get this to replicate in the smallest script 
that I could that is now attached. the chroot is important. I am able to 
unmount the second overlayfs if chroot is never called. Nothing ever has to run 
IN the chroot, trying to call a binary that does not exist, and then trying to 
unmount it results in "target is busy" with no open files reportable by user 
mode tools

  FURTHER TESTING:
  
  Trying to find out the version of Linux this was introduced, I made a script 
that builds a very minimal ext4 file for a VM with a small debootstrapped 
system, builds a kernel, and runs the kernel with QEMU..
  but when I started, after all that, I can't replicate it at all with a 
vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, 
only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the 
second filesystem actually 

[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  Include the MAC address pass through function on RTL8153DD-CG

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

Bug description:
  [Impact]
  When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it 
should show pass through MAC address set in BIOS. But the LAN MAC address pass 
through doesn't function on RTL8153DD-CG sku.

  [Fix]
  Commit in v6.3-rc1 fixes the issue.
  ec51fbd1b8a2 r8152: add USB device driver for config selection

  [Test]
  Verified by OEM.

  [Where problems could occur]
  It won't affect the old behavior if there is no preferred cfg is configured 
and will select the preferred one while probing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020295/+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 2022354] Re: sysfs msi_irqs directory empty with kernel-5.19 when being a xen guest

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  sysfs msi_irqs directory empty with kernel-5.19 when being a xen guest

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: See below

  Fix: Upstream commit from v6.4-rc4 cherry-picked into 5.19 and 6.2

  Test case: Check of sysfs running Xen.

  Regression potential: Change adds additional calls to populate sysfs
  related to MSI devices. Any issues would be withing those limits.

  --- Original Description ---

  Let's say you launch a Xen-based EC2 instance with enhanced
  networking, then under kernel-5.19 you'll not see anything under

  $ ls /sys/class/net/ens3/device/msi_irqs/

  This can be fixed by backporting
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=335b4223466dd75f9f3ea4918187afbadd22e5c8
  (It got already backported to 6.1 and 6.3)

  With this patch applied, you'll correctly see the sysfs files:

  $ ls /sys/class/net/ens3/device/msi_irqs/
  690  691  692  693  694  695  696  697  698

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022354/+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 2023197] Re: Fix speaker volume too low on HP G10 laptops

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  Fix speaker volume too low on HP G10 laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  New
Status in linux source package in Mantic:
  Incomplete
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]
  HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to 
enable all amplifiers to output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The quirk is for Cirrus codec on particular HP series laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023197/+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 2023638] Re: Various backlight issues with the 6.0/6.1 kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  Various backlight issues with the 6.0/6.1 kernel

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  There are some new patches for new method to decide which backlight driver 
should be registered introduced since 6.1. And we backport some of them to 
6.0-oem kernel which are not enough to solved all backlight issues.
  1. dell_laptop created a non-working backlight driver before nvidia is 
loaded, that leads to the system can't adjust the display brightness.
  2. acpi_backlight0 sometimes will be generated together with intel_backlight.

  [Fix]
  Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being 
registered automatically(which have been included into ubuntu kernels through 
stable update)
  e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU 
driver
  78dfc9d1d1ab ACPI: video: Add auto_detect arg to 
__acpi_video_get_backlight_type()

  Below patch prevents platform driver(dell_laptop) from creating backlight 
driver after win8.
  aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on 
laptops from after ~2012
  
https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/

  [Test]
  Verified on the dell platform which reports this issue.

  [Where problems could occur]
  The assumption of the not-yet-upstreamed commit regarding backlight control 
is that, after Windows 8, all laptop backlights are controlled either by ACPI 
or the native graphics driver. It impacts the laptops that do not follow the 
assumption and will lead to broken backlight interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023638/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  Fix AMDGPU: the screen freeze with W7500

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [impact]
  While booting into OOBE, the screen freeze [AMD W7500 only]

  [fix]
  AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled.
  Intel CPU may not support the dynamic lane/speed switching.

  Solution is,
  - Detect Intel x86 systems that don't support dynamic switching
  - Override the input caps to maximum supported for that system
  - Force all PCIe levels to use the same settings, rather than try to 
configure each level differently.

  [test cases]
  1. boot with w7500
  2. the screen doesn't freeze and can't find the error message in dmesg.
  "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out"

  [where the issue could happen]
  low, this could lead issue when setting higher speeds than supported.

  [Misc]
  1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic.
  2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic.
  3. Passed cbd build against Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2027773] Re: UBSAN: shift-out-of-bounds in amd_sfh

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  UBSAN: shift-out-of-bounds in amd_sfh

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  UBSAN: shift-out-of-bounds in 
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
  [ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned 
int'
  [ 9.877309] Workqueue: events amd_sfh_work_buffer \[amd_sfh]
  [ 9.877327] Call Trace:
  [ 9.877331] \
  [ 9.877335] dump_stack_lvl+0x49/0x63
  [ 9.877346] dump_stack+0x10/0x16
  [ 9.877348] ubsan_epilogue+0x9/0x36
  [ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 9.877363] ? _raw_spin_lock+0x17/0x50
  [ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
  [ 9.877378] ? psi_group_change+0x1e2/0x4a0
  [ 9.877385] float_to_int.cold+0x18/0xc8 \[amd_sfh]
  [ 9.877394] ? get_feature_rep+0xb0/0xb0 \[amd_sfh]
  [ 9.877402] get_input_rep+0x219/0x2f0 \[amd_sfh]
  [ 9.877409] ? up+0x37/0x70
  [ 9.877414] ? hid_input_report+0x104/0x170 \[hid]
  [ 9.877428] amd_sfh_work_buffer+0x94/0x150 \[amd_sfh]
  [ 9.877436] process_one_work+0x21f/0x3f0
  [ 9.877443] worker_thread+0x50/0x3e0
  [ 9.877446] ? process_one_work+0x3f0/0x3f0
  [ 9.877449] kthread+0xfd/0x130
  [ 9.877452] ? kthread_complete_and_exit+0x20/0x20
  [ 9.877454] ret_from_fork+0x22/0x30
  [ 9.877463] \

  [Fix]

  Fixes in:
  * commit c1685a862a4b ("HID: amd_sfh: Rename the float32 variable")
  * commit 878543661764 ("HID: amd_sfh: Fix for shift-out-of-bounds")

  [Test Case]

  The affected platform should no longer has such error dumped in kernel dmesg 
at
  boot.

  [Where problems could occur]

  This renamed a variable and corrected the way shift offset is calculated. No
  known side effect.

  [Other Info]

  The affects kernel >= v6.0 and < v6.5, so Unstable/Mantis/Lunar/OEM-6.1 are
  nominated for fix.

  == original bug report ==

  UBSAN: shift-out-of-bounds in 
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
  [ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned 
int'
  [ 9.877309] Workqueue: events amd_sfh_work_buffer [amd_sfh]
  [ 9.877327] Call Trace:
  [ 9.877331] 
  [ 9.877335] dump_stack_lvl+0x49/0x63
  [ 9.877346] dump_stack+0x10/0x16
  [ 9.877348] ubsan_epilogue+0x9/0x36
  [ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 9.877363] ? _raw_spin_lock+0x17/0x50
  [ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
  [ 9.877378] ? psi_group_change+0x1e2/0x4a0
  [ 9.877385] float_to_int.cold+0x18/0xc8 [amd_sfh]
  [ 9.877394] ? get_feature_rep+0xb0/0xb0 [amd_sfh]
  [ 9.877402] get_input_rep+0x219/0x2f0 [amd_sfh]
  [ 9.877409] ? up+0x37/0x70
  [ 9.877414] ? hid_input_report+0x104/0x170 [hid]
  [ 9.877428] amd_sfh_work_buffer+0x94/0x150 [amd_sfh]
  [ 9.877436] process_one_work+0x21f/0x3f0
  [ 9.877443] worker_thread+0x50/0x3e0
  [ 9.877446] ? process_one_work+0x3f0/0x3f0
  [ 9.877449] kthread+0xfd/0x130
  [ 9.877452] ? kthread_complete_and_exit+0x20/0x20
  [ 9.877454] ret_from_fork+0x22/0x30
  [ 9.877463] 

  Fixes in:
  
https://github.com/torvalds/linux/commit/c1685a862a4bea863537f06abaa37a123aef493c
  
https://github.com/torvalds/linux/commit/87854366176403438d01f368b09de3ec2234e0f5

  This affects kernel >= v6.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027773/+subscriptions


-- 
Mailing 

[Kernel-packages] [Bug 2024273] Re: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  Fix eDP only displays 3/4 area after switching to mirror mode with
  external HDMI 4K monitor

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Panel on laptops connect to some 4K monitors via HDMI only display 3/4 area 
on eDP after switching to mirror mode.

  [Fix]
  Backport a fix from Intel on 
https://cgit.freedesktop.org/drm-tip/commit/?id=a2da67028cd05516343533c1609fcaf037237fed.
 

  [Test]
  1. Power on the laptop
  2. Connect a 4K monitor (4k Benq EL2870U, 4k HP z27Kg3, 2k ASUS PA27AC) to 
the laptop with HDMI cable.
  3. Switch to mirror mode from default Joint Mode
  4. Verify there's no obvious blank space on the leftmost/rightmost side of 
the laptop's panel.

  [Where problems could occur]
  Only observed after connecting with some particular 4K monitors. It's a 
generic fix to accept arbitrary refresh rate for more advanced panels. Should 
be low risk to old machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024273/+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 2020743] Re: FM350(mtk_t7xx) failed to suspend, or early wake while suspending

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
to 'verification-failed-jammy-linux-aws-6.2'.

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

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


** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 
verification-needed-jammy-linux-aws-6.2

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

Title:
  FM350(mtk_t7xx) failed to suspend, or early wake while suspending

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

Bug description:
  [Impact]
  FM350(mtk_t7xx) can't suspend sometimes.

  kernel: [ 12.917396] mtk_t7xx :57:00.0: [PM] Exiting suspend, modem in 
invalid state
  kernel: [ 12.917406] mtk_t7xx :57:00.0: PM: pci_pm_suspend(): 
t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -14
  kernel: [ 12.917446] mtk_t7xx :57:00.0: PM: dpm_run_callback(): 
pci_pm_suspend+0x0/0x1b0 returns -14
  kernel: [ 12.917462] mtk_t7xx :57:00.0: PM: failed to suspend async: 
error -14

  [Fix]
  The commit in v6.4-rc3 waits for the device to be ready before suspending.
  ab87603b2511 net: wwan: t7xx: Ensure init is completed before system sleep

  [Test]
  Verified on the machine with FM350 wwan module.

  [Where problems could occur]
  If the wwan is not ready before the time is up, it results in -ETIMEDOUT. 
However, in this scenario, we will encounter the same issue where the system 
fails to enter suspend mode. Therefore, it will not introduce regressions or 
new issues.

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