[Kernel-packages] [Bug 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202

[You-Sheng Yang]

Accepted upstream as commit ec63120307a67 ("Bluetooth: Add support for
Intel Misty Peak - 8087:0038") in linux-next next-20230911.

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

Title:
  Missing BT IDs for support for Intel Discrete Misty Peak2/BE202

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware 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-firmware source package in Jammy:
  Incomplete
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-firmware source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

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

  [Impact]

  Missing BT IDs for support for Intel Discrete Misty Peak2/BE202.

  [Fix]

  Bluetooth:
  a. kernel driver:
 - 
https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t
 - Also depends on patches for Gale Peak(BE200) from bug 2028065.
  b. firmware (shared with Gale Peak, to be released):
 - intel/ibt-0191-0191.sfi
 - intel/ibt-0191-0191.ddc

  [Test Case]

  To boot with patched kernel and prereleased firmware blob and check
  basic Bluetooth functions.

  [Where problems could occur]

  New device. Expect incomplete functions and bugs.

  [Other Info]

  Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2033455/+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 2035051] [NEW] hevc encoding on intel igpu produces garbled output ubuntu 22.04

[Yensong Ted Li]

Public bug reported:

Please refer to this for more details:

https://github.com/intel/media-driver/issues/1503

Apparently the issue has been fixed since ffmpeg 5.1+; but unfortunately
since ubuntu 22.04 is still based off of the ffmpeg 4.4.2 software
stack, applications like OBS installed via the official PPA is unable to
use the system ffmpeg libraries like libavcodec58 to record using the
VAAPI hevc encoder without producing absolutely garbled videos.

I am more than happy to provide any additional information in order to
resolve this issue :)

** Affects: ffmpeg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

** Package changed: linux-signed-hwe-5.13 (Ubuntu) => ffmpeg (Ubuntu)

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

Title:
  hevc encoding on intel igpu produces garbled output ubuntu 22.04

Status in ffmpeg package in Ubuntu:
  New

Bug description:
  Please refer to this for more details:

  https://github.com/intel/media-driver/issues/1503

  Apparently the issue has been fixed since ffmpeg 5.1+; but
  unfortunately since ubuntu 22.04 is still based off of the ffmpeg
  4.4.2 software stack, applications like OBS installed via the official
  PPA is unable to use the system ffmpeg libraries like libavcodec58 to
  record using the VAAPI hevc encoder without producing absolutely
  garbled videos.

  I am more than happy to provide any additional information in order to
  resolve this issue :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/2035051/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Kai-Chuan Hsieh]

continue #116

Please be aware to remove ppa from source list after you install the working 
packages on your system.
It is because the ppa will keep updating packages from upstream, sometimes it 
might break your system since upstream didn't validate on all systems when they 
commit new code drop.

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: 

[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)

[xijunli]

** Tags removed: verification-needed-focal-linux-aws-5.15
** Tags added: verification-done-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 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1

[Andrew Liaw]

No crashes observed with the proposed kernel. Changed the tag to
'verification-done-jammy-linux'.

** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux

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

Title:
  Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel
  5.19.0-46.47-22.04.1

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

Bug description:
  Impact:
  We had reports of VM setups which would show intermediate crashes and after 
that locking up completely. This could be reproduced with large memory setups.
  The problem seems to be that fixes to performance regressions caused more 
problems in 5.15 kernels and the full fixes are too intrusive to be backported.

  Fix:
  The following patch was recently sent to the upstream stable mailing list and 
looks to be making its way into linux-5.15.y. This changes the default value of 
kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed 
back in config).

  Regression potential:
  VM hosts with many large memory tennants might see a performance impact which 
the TDP MMU approach tried to solve. If those did not see other problems they 
might turn this on again.

  Testcase:
  Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large 
second level guest (32GB memory). Repeatedly starting and stopping the 2nd 
level guest.

  
  --- original description ---
  The crash occurred on a juju machine, and the juju agent was lost.
  The juju machine is on an openstack instance provision by juju.

  The openstack console log indicts the it is related to spin_lock and KVM MMU:
  [418200.348830]  ? _raw_spin_lock+0x22/0x30
  [418200.349588]  _raw_write_lock+0x20/0x30
  [418200.350196]  kvm_tdp_mmu_map+0x2b1/0x490 [kvm]
  [418200.351014]  kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm]
  [418200.351796]  direct_page_fault+0x206/0x310 [kvm]
  [418200.352667]  __mmu_notifier_invalidate_range_start+0x91/0x1b0
  [418200.353624]  kvm_tdp_page_fault+0x72/0x90 [kvm]
  [418200.354496]  try_to_migrate_one+0x691/0x730
  [418200.355436]  kvm_mmu_page_fault+0x73/0x1c0 [kvm]

  openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/

  syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/
  The syslog was rotated after the crash occurred, so the syslog at the time of 
the initial crash was lost.

  Other juju machine with 5.15.0.79.76 kernel seems to have the same
  issues.

  We previously have a similar issue with 5.15.0-73. The juju machine
  crashed with raw_spin_lock and kvm mmu in the logs as well:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Aug 21 08:59:46 2023
  Ec2AMI: ami-0c61
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: availability-zone-1
  Ec2InstanceType: builder-cpu4-ram72-disk20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 23 03:23 seq
   crw-rw 1 root audio 116, 33 Aug 23 03:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  DistroRelease: Ubuntu 22.04
  Ec2AMI: ami-0fbb
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: availability-zone-2
  Ec2InstanceType: builder-cpu2-ram44-disk20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: OpenStack Foundation OpenStack Nova
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  

[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

[Kai-Heng Feng]

Yes please file a different issue.

-- 
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 20220329.git681281e4-0ubuntu1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2029328] Re: [ADL-N][RPL-S] support ISHTP module

[Jian Hui Lee]

verified the version 5.15.0-1039.45 fixes the issue.

** Tags removed: verification-needed-jammy-linux-intel-iotg
** Tags added: verification-done-jammy-linux-intel-iotg

** Changed in: linux-intel-iotg (Ubuntu Jammy)
 Assignee: (unassigned) => Jian Hui Lee (jianhuilee)

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

Title:
  [ADL-N][RPL-S] support ISHTP module

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

Bug description:
  [Impact]
  support ishtp module on intel adl-n/rpl-s platform

  [Fix]
  add the corresponding pci id for each platform.
  the rest of the patches are requested by intel. they belong to code revised, 
bug fixed and device setup.

  [Test]
  1. compile test
  2. run the kernel on the target platform to see if the module is loaded 
correctly.
  3. run suspend/reboot to see if any error occurs.

  [Where problems could occur]
  all of the patches are quite clear and easy to understand, so the regression 
risk should be low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2029328/+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 2034908] Re: Add support 3 TDX subfeatures

[Khaled El Mously]

** Summary changed:

- Support 3 TDX subfeatures
+ Add support 3 TDX subfeatures

** Summary changed:

- Add support 3 TDX subfeatures
+ Add support for 3 TDX subfeatures

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

Title:
  Add support for 3 TDX subfeatures

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Lunar:
  New

Bug description:
  Support is requested for 3 TDX-specific features:

   - Unaccepted memory, aka "lazy memory accept"
   - TDX "Get Quote" - is needed for attestation 
   - Marking the TSC as reliable

  
  More information at: 
https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2034718] Re: Backport request: drm/amdgpu: fix clearing mappings for BOs that are always valid in VM

[kisak]

It appears that 5.15.0-85.95
(https://launchpad.net/ubuntu/+source/linux/5.15.0-85.95) is a general
rebase to 5.15.122, which includes this commit from upstream. Also,
Mantic looks like it's in the process of switching to 6.5.??
(https://launchpad.net/ubuntu/+source/linux/6.5.0-5.5).

If/when those ship, that should reduce the scope of this bug report to
the 6.2 based Jammy HWE and Lunar kernels.

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

Title:
  Backport request: drm/amdgpu: fix clearing mappings for BOs that are
  always valid in VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Good day Ubuntu kernel maintainers,

  Please evaluate
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5
  for backport into all actively maintained Ubuntu flavors of the Linux
  kernel.

  This commit is needed to stabilize Starfield with mesa/RADV. There was
  a stopgap workaround put into mesa 23.1.4, but that workaround harmed
  other games and it needed to be fixed properly in the kernel. The mesa
  workaround is removed in mesa 23.1.7 and mesa git main.

  As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+,
  6.1.40+ or 6.4.5+ baseline noted in
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

  There's what looks like an automated mailing list message that this
  commit was queued for the upstream 5.4 series at some point near
  5.4.250, but it's not in the linux changelog, so there might be a
  conflict denominating it from that kernel.

  Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE
  and Lunar (6.2 based), and Mantic (6.3 based)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034718/+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 2024479] Re: kdump fails on big arm64 systems when offset is not specified

[Ubuntu Kernel Bot]

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

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  

[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-
riscv-5.15/5.15.0-1041.45~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-
riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
riscv-5.15' to 'verification-failed-focal-linux-riscv-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-riscv-5.15-v2 
verification-needed-focal-linux-riscv-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/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-
riscv-5.15/5.15.0-1041.45~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-
riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
riscv-5.15' to 'verification-failed-focal-linux-riscv-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-riscv-5.15-v2 
verification-needed-focal-linux-riscv-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/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 

[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-
riscv-5.15/5.15.0-1041.45~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-
riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
riscv-5.15' to 'verification-failed-focal-linux-riscv-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-riscv-5.15-v2 
verification-needed-focal-linux-riscv-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/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 2028550] Re: Backport support to tolerate ZSTD compressed firmware files

[Ubuntu Kernel Bot]

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

Title:
  Backport support to tolerate ZSTD compressed firmware files

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * To ensure reliable dist-upgrades in case of partial upgrades or
  upgrade failures, it is desirable for LTS GA kernel to support
  features that next-LTS GA kernel will rely on.

   * Specifically it is being discussed to switch linux-firmware to ZSTD
  compressed one (see bug #1942260)

   * To ensure that failed dist-upgrades can still boot after-partial
  upgrade it is desirable to suppport zstd compressed firmware

  [ Test Plan ]

   * Boot new build of GA linux kernel with
  CONFIG_FW_LOADER_COMPRESS_ZSTD

   * Check that existing firmware files loaded on a given machine can be
  compressed with zstd and still loaded by this kernel

   * Check that depmod / initramfs-tools all support .zst compressed
  firmware

  [ Where problems could occur ]

   * Once this is inroduced in jammy-GA kernel it may cripple into
  focal-hwe kernels too, and people may start relying on this feature
  despite not universally supported by all other focal kernels. This
  should be trivial to catch in SRUs for example, do not accept SRUs of
  firmwares that ship themselves as .zst in Jammy  and lower.

  [ Other Info ]

   * See https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-July/042652.html and
  https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028550/+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 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold

[Ubuntu Kernel Bot]

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

Title:
  cifs: fix mid leak during reconnection after timeout threshold

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-azure source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  A regression in the Ubuntu 5.15 kernel has been causing problems for multiple 
customers on Azure.

  This bug has been fixed in the mainline kernel:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Reconnections could fail.

  [Other Info]

  SF: #00365185

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+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 2026028] Re: usbrtl sometimes doesn't reload firmware

[Ubuntu Kernel Bot]

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

Title:
  usbrtl sometimes doesn't reload firmware

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

Bug description:
  [Impact]

  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided
  by the linux-firmware package.

  This will show in logs like so:
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp 
subver d922, hci rev dfc6, hci ver 000a
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware 
upload needed

  The driver reads subver from the adapter to determine chip type. But
  that value is overwritten by a firmware load. In the above case, a
  firmware was already loaded which returns subver d922 which the driver
  does not recognize and it therefore won't load new firmware.

  [Test Case]

  1) Boot machine with USB adapter plugged in.
  2) Verify firmware is loaded.
  3) Reboot a couple of times and verify that firmware is reloaded every time.

  [Where Problems Could Occur]

  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+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-
riscv-5.15/5.15.0-1041.45~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-
riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
riscv-5.15' to 'verification-failed-focal-linux-riscv-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-riscv-5.15-v2 
verification-needed-focal-linux-riscv-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 2035038] [NEW] tilt sensors (also known as accelerometers or gyroscope sensors) in my Dell Inspiron 7415 2-in-1 laptop are not working with Ubuntu

[Freddy Alarcon]

Public bug reported:

Title: Tilt Sensor Not Functional on Ubuntu 22.04.3

Description:

Issue:
I am experiencing an issue with the tilt sensor (accelerometer/gyroscope) on my 
Dell Inspiron 7415 2-in-1 laptop. The sensor is not functioning as expected on 
my Ubuntu 22.04.3 installation.

Expected Behavior:
The tilt sensor should detect changes in the laptop's orientation and provide 
data that can be used by software applications or system functions.

Actual Behavior:
The tilt sensor does not appear to be working, and there is no response or data 
output when I tilt or rotate the laptop.

Steps to Reproduce:

Boot the laptop into Ubuntu 22.04.3.
Open a terminal or any application that should utilize the tilt sensor data.
Tilt or rotate the laptop to observe the lack of response from the sensor.

Additional Information:

Laptop Model: Dell Inspiron 7415 2-in-1
Ubuntu Version: 22.04.3
Kernel Version: [Provide your kernel version here if known]
Any error messages or logs related to the issue.

Workarounds Attempted:
I have attempted the following troubleshooting steps without success:

Checked for updates using sudo apt update and sudo apt upgrade.
Verified that no relevant kernel modules are missing using lsmod.
Installed iio-sensor-proxy and enabled the service.

Notes:
This issue affects my laptop's usability and the functionality of applications 
or features that rely on sensor data. Any assistance in resolving this problem 
or information on potential fixes would be greatly appreciated.

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

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

Title:
  tilt sensors (also known as accelerometers or gyroscope sensors) in my
  Dell Inspiron 7415 2-in-1 laptop are not working with Ubuntu

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

Bug description:
  Title: Tilt Sensor Not Functional on Ubuntu 22.04.3

  Description:

  Issue:
  I am experiencing an issue with the tilt sensor (accelerometer/gyroscope) on 
my Dell Inspiron 7415 2-in-1 laptop. The sensor is not functioning as expected 
on my Ubuntu 22.04.3 installation.

  Expected Behavior:
  The tilt sensor should detect changes in the laptop's orientation and provide 
data that can be used by software applications or system functions.

  Actual Behavior:
  The tilt sensor does not appear to be working, and there is no response or 
data output when I tilt or rotate the laptop.

  Steps to Reproduce:

  Boot the laptop into Ubuntu 22.04.3.
  Open a terminal or any application that should utilize the tilt sensor 
data.
  Tilt or rotate the laptop to observe the lack of response from the sensor.

  Additional Information:

  Laptop Model: Dell Inspiron 7415 2-in-1
  Ubuntu Version: 22.04.3
  Kernel Version: [Provide your kernel version here if known]
  Any error messages or logs related to the issue.

  Workarounds Attempted:
  I have attempted the following troubleshooting steps without success:

  Checked for updates using sudo apt update and sudo apt upgrade.
  Verified that no relevant kernel modules are missing using lsmod.
  Installed iio-sensor-proxy and enabled the service.

  Notes:
  This issue affects my laptop's usability and the functionality of 
applications or features that rely on sensor data. Any assistance in resolving 
this problem or information on potential fixes would be greatly appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2035038/+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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

[Gannet]

-- 
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 20220329.git681281e4-0ubuntu1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  

[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

[Gannet]

On Linux 6.5.x the similar issue appeared (do I need to raise a separate
report?):

вер 10 21:16:35 p5q3 kernel: 

вер 10 21:16:35 p5q3 kernel: fbcon: Taking over console
вер 10 21:16:35 p5q3 kernel: UBSAN: array-index-out-of-bounds in 
/home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43
вер 10 21:16:35 p5q3 kernel: index 1 is out of range for type 'UCHAR [1]'
вер 10 21:16:35 p5q3 kernel: CPU: 3 PID: 310 Comm: systemd-udevd Not tainted 
6.5.1-060501-generic #202309020842
вер 10 21:16:35 p5q3 kernel: Hardware name: System manufacturer System Product 
Name/P5Q3, BIOS 110206/11/2010
вер 10 21:16:35 p5q3 kernel: Call Trace:
вер 10 21:16:35 p5q3 kernel:  
вер 10 21:16:35 p5q3 kernel:  dump_stack_lvl+0x48/0x70
вер 10 21:16:35 p5q3 kernel:  dump_stack+0x10/0x20
вер 10 21:16:35 p5q3 kernel:  __ubsan_handle_out_of_bounds+0xc6/0x110
вер 10 21:16:35 p5q3 kernel:  radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 
[radeon]
вер 10 21:16:35 p5q3 kernel:  radeon_atombios_get_power_modes+0x205/0x210 
[radeon]
вер 10 21:16:35 p5q3 kernel:  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
вер 10 21:16:35 p5q3 kernel:  radeon_pm_init+0xd0/0x100 [radeon]
вер 10 21:16:35 p5q3 kernel:  rv770_init+0x1fa/0x3d0 [radeon]
вер 10 21:16:35 p5q3 kernel:  radeon_device_init+0x540/0xa90 [radeon]
вер 10 21:16:35 p5q3 kernel:  radeon_driver_load_kms+0xcc/0x2f0 [radeon]
вер 10 21:16:35 p5q3 kernel:  drm_dev_register+0x10e/0x240 [drm]
вер 10 21:16:35 p5q3 kernel:  radeon_pci_probe+0xec/0x180 [radeon]
вер 10 21:16:35 p5q3 kernel:  local_pci_probe+0x47/0xb0
вер 10 21:16:35 p5q3 kernel:  pci_call_probe+0x55/0x190
вер 10 21:16:35 p5q3 kernel:  pci_device_probe+0x84/0x120
вер 10 21:16:35 p5q3 kernel:  really_probe+0x1c7/0x410
вер 10 21:16:35 p5q3 kernel:  __driver_probe_device+0x8c/0x180
вер 10 21:16:35 p5q3 kernel:  driver_probe_device+0x24/0xd0
вер 10 21:16:35 p5q3 kernel:  __driver_attach+0x10b/0x210
вер 10 21:16:35 p5q3 kernel:  ? __pfx___driver_attach+0x10/0x10
вер 10 21:16:35 p5q3 kernel:  bus_for_each_dev+0x8d/0xf0
вер 10 21:16:35 p5q3 kernel:  driver_attach+0x1e/0x30
вер 10 21:16:35 p5q3 kernel:  bus_add_driver+0x127/0x240
вер 10 21:16:35 p5q3 kernel:  driver_register+0x5e/0x130
вер 10 21:16:35 p5q3 kernel:  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC1200: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:
speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:
dig-out=0x11/0x1e
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
вер 10 21:16:35 p5q3 kernel:  __pci_register_driver+0x62/0x70
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:  Front 
Mic=0x19
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:  Rear 
Mic=0x18
вер 10 21:16:35 p5q3 kernel: snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
вер 10 21:16:35 p5q3 kernel:  radeon_module_init+0x4c/0xff0 [radeon]
вер 10 21:16:35 p5q3 kernel:  do_one_initcall+0x5e/0x340
вер 10 21:16:35 p5q3 kernel:  do_init_module+0x68/0x260
вер 10 21:16:35 p5q3 kernel:  load_module+0xba1/0xcf0
вер 10 21:16:35 p5q3 kernel:  ? find_vmap_area+0x42/0x70
вер 10 21:16:35 p5q3 kernel:  __do_sys_init_module+0x1a7/0x1e0
вер 10 21:16:35 p5q3 kernel:  ? __do_sys_init_module+0x1a7/0x1e0
вер 10 21:16:35 p5q3 kernel:  __x64_sys_init_module+0x1a/0x30
вер 10 21:16:35 p5q3 kernel:  do_syscall_64+0x5c/0x90
вер 10 21:16:35 p5q3 kernel:  ? do_syscall_64+0x68/0x90
вер 10 21:16:35 p5q3 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
вер 10 21:16:35 p5q3 kernel:  ? syscall_exit_to_user_mode+0x37/0x60
вер 10 21:16:35 p5q3 kernel:  ? do_syscall_64+0x68/0x90
вер 10 21:16:35 p5q3 kernel:  ? irqentry_exit_to_user_mode+0x17/0x20
вер 10 21:16:35 p5q3 kernel:  ? irqentry_exit+0x43/0x50
вер 10 21:16:35 p5q3 kernel:  ? exc_page_fault+0x94/0x1b0
вер 10 21:16:35 p5q3 kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
вер 10 21:16:35 p5q3 kernel: RIP: 0033:0x7f8c1711ed8e
вер 10 21:16:35 p5q3 kernel: Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 
ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 
05 <48> 3d 01 f0 ff ff 73>
вер 10 21:16:35 p5q3 kernel: RSP: 002b:7fff7e0f4448 EFLAGS: 0246 
ORIG_RAX: 00af
вер 10 21:16:35 p5q3 kernel: RAX: ffda RBX: 5578c64adfd0 RCX: 
7f8c1711ed8e
вер 10 21:16:35 p5q3 kernel: RDX: 7f8c17485458 RSI: 00441061 RDI: 
7f8c1515f010
вер 10 21:16:35 p5q3 kernel: RBP: 7f8c17485458 R08: 00261000 R09: 

вер 10 21:16:35 p5q3 kernel: R10: 00015221 R11: 0246 

[Kernel-packages] [Bug 2035028] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
  between headset and handsfree profiles and I think also ended up
  cycling it on/off, causing a kernel bug in the memory management.

  Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
  Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
  Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
  Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
  Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 
21CF004PGE/21CF004PGE, BIOS R23ET65W (1.35 ) 03/21/2023
  Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
  Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 
84 c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 
24 08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
  Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
  Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 
9c0dc0042c00 RCX: 801f
  Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 
9c11644ba800 RDI: ae30a77fbcf0
  Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 
0001 R09: 8bfd9f77 
  Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11: 
 R12: 9c11644ba800
  Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: 
ec1352912e00 R15: 
  Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
  Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
  Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 
00068703a000 CR4: 00750ee0
  Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
  Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
  Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
  Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
  Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 
videobuf2_memops cdc_ncm videobuf2_v4l2 option cdc_ether usb_wwan usbnet 
videodev usbserial mii videobuf2_common mc xfs 

[Kernel-packages] [Bug 2035028] Re: 6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

[Julian Andres Klode]

Complete journal from 15:40 to 16:00

** Attachment added: "JournalAt1540To1600.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5699730/+files/JournalAt1540To1600.log

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

Title:
  6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
  between headset and handsfree profiles and I think also ended up
  cycling it on/off, causing a kernel bug in the memory management.

  Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
  Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
  Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
  Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
  Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 
21CF004PGE/21CF004PGE, BIOS R23ET65W (1.35 ) 03/21/2023
  Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
  Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 
84 c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 
24 08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
  Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
  Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 
9c0dc0042c00 RCX: 801f
  Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 
9c11644ba800 RDI: ae30a77fbcf0
  Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 
0001 R09: 8bfd9f77 
  Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11: 
 R12: 9c11644ba800
  Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: 
ec1352912e00 R15: 
  Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
  Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
  Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 
00068703a000 CR4: 00750ee0
  Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
  Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
  Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
  Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
  Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 
videobuf2_memops 

[Kernel-packages] [Bug 2035028] [NEW] 6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

[Julian Andres Klode]

Public bug reported:

In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
between headset and handsfree profiles and I think also ended up cycling
it on/off, causing a kernel bug in the memory management.

Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 21CF004PGE/21CF004PGE, 
BIOS R23ET65W (1.35 ) 03/21/2023
Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 84 
c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 24 
08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 9c0dc0042c00 
RCX: 801f
Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 9c11644ba800 
RDI: ae30a77fbcf0
Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 0001 
R09: 8bfd9f77 
Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11:  
R12: 9c11644ba800
Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: ec1352912e00 
R15: 
Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 00068703a000 
CR4: 00750ee0
Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
Sep 08 15:54:45 jak-t14-g3 kernel:  
Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
Sep 08 15:54:45 jak-t14-g3 kernel:  
Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 
videobuf2_memops cdc_ncm videobuf2_v4l2 option cdc_ether usb_wwan usbnet 
videodev usbserial mii videobuf2_common mc xfs nls_iso8859_1 snd_soc_dmic 
snd_acp6x_pdm_dma intel_rapl_msr snd_soc_acp6x_mach intel_rapl_common 
snd_sof_amd_rembrandt snd_sof_amd_renoir snd_ctl_led joydev snd_sof_amd_acp 
snd_hda_codec_realtek snd_sof_pci snd_hda_codec_generic snd_sof_xtensa_dsp 
snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils qrtr snd_intel_dspcfg 
edac_mce_amd snd_soc_core s
 nd_intel_sdw_acpi ath11k_pci snd_hda_codec snd_compress
Sep 08 15:54:45 jak-t14-g3 kernel:  ac97_bus ath11k 

[Kernel-packages] [Bug 2035024] [NEW] touchpad not working on startup

[Gabriele]

Public bug reported:

I have a Samsung Galaxy Book 2 and I have installed Ubuntu 22.04.3. 
Occasionally, on startup the touchpad is not recognized, and it does not work.
I attach the content of /proc/bus/input/devices.

ProblemType: Bug
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-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 10 14:12:23 2023
InstallationDate: Installed on 2023-08-31 (9 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "Output of /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/2035024/+attachment/5699699/+files/devices

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

Title:
  touchpad not working on startup

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

Bug description:
  I have a Samsung Galaxy Book 2 and I have installed Ubuntu 22.04.3. 
Occasionally, on startup the touchpad is not recognized, and it does not work.
  I attach the content of /proc/bus/input/devices.

  ProblemType: Bug
  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-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 14:12:23 2023
  InstallationDate: Installed on 2023-08-31 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-6.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/2035024/+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 2033654] Re: amdgpu: Fixes for S0i3 resume on Phoenix

[Timo Aaltonen]

** Tags removed: verification-needed-jammy verification-needed-lunar-linux
** Tags added: verification-done-jammy-linux-oem-6.1 
verification-done-lunar-linux

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

Title:
  amdgpu: Fixes for S0i3 resume on Phoenix

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 Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]

  Hard hangs in some cases on resume from suspend on AMD Phoenix

  [Fix]

  pick three commits from v6.5-rc7 (also in 6.1.47):

  730d44e1fa306a2 drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU 
v13.0.4/11
  f1740b1ab2703b2 drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix
  a7b7d9e8aee4f71 drm/amd: flush any delayed gfxoff on suspend entry

  
  [Test Case]

  Check the updated kernel on a failing system, and test resume from
  suspend.

  [Where problems could occur]

  These are cherry-picks from upstream stable, and limited to Phoenix

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