date:20221213

** Changed in: linux (Ubuntu Impish)
   Status: New => 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/1642368

Title:
  linux: Staging modules should be unsigned

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
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:
  New
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 1786013] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1015.16)

2022-12-13 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.19.0-1015.16) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-515-server/unknown (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/kinetic/update_excuses.html#linux-restricted-modules-azure

[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 packing 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 1999491] Re: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821

upgrade to linux-firmware-20220329, VNP.
@Ian, thanks

** Tags added: verification-done-jammy verification-done-kinetic

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

Title:
  Fix The Bluetooth connection cannot be established between two Ubuntu
  22.04 systems with Realtek 8821

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821.

  [Fix]
  Use the updated firmware for rtl8821c to fix issue.

  [Test]
  1. Prepare two Ubuntu 22.04 systems with Realtek 8821.
  2. Open Bluetooth Settings and launch research available device automatically.
  3. Found this two systems are visible in research list for connection, 
Bluetooth connection can be established normally without problem.

  [Where problems could occur]
  It's binary so anything would happen.

  [Other Info]
  This firmware has existed in Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999491/+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 1999556] Re: commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile

** Description changed:

+ [Impact]
+ 
  Added Linux kernel remote branch for Kinetic raspi to test with 22.04
  install (both master and master-next branches). When running "make
  clean" noticed error referencing "hio" driver that's been removed from
  Jammy kernels:
  
  $ make clean
  scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
  make[2]: *** No rule to make target 'ubuntu/hio/Makefile'.  Stop.
  make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
  make: *** [Makefile:1858: _clean_ubuntu] Error 2
  
  Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:
  
  commit cf58599cded35cf4affed1e659c0e2c742d3fda7
  Author: Thomas Lamprecht 
  Date:   Sat Mar 12 16:19:10 2022 +0100
  
  Ubuntu: remove leftover reference to ubuntu/hio driver
  
  A single reference to the hio driver was forgotten when it was removed
  recently. While this reference is not a problem for the build itself, it
  breaks the __clean target from 'scripts/Makefile.clean' here, as make
  cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.
  
  Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
  Signed-off-by: Thomas Lamprecht 
  Acked-by: Tim Gardner 
  Signed-off-by: Paolo Pisati 
  
  Here's some additional information for code repositories (didn't know if
  this was helpful),
  
  
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
  remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
  branch.kinetic-master-next.remote=kinetic-raspi
  branch.kinetic-master-next.merge=refs/heads/master-next
  branch.kinetic-master.remote=kinetic-raspi
  branch.kinetic-master.merge=refs/heads/master
+ 
+ [Test Case]
+ 
+ See above.
+ 
+ [Fix]
+ 
+ Pick commit cf58599cded35cf4affed1e659c0e2c742d3fda7 from jammy.
+ 
+ [Where Problems Could Occur]
+ 
+ Build failures.

** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Lunar)
   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/1999556

Title:
  commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in
  kinetic master to remove "hio" reference from Makefile

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  Added Linux kernel remote branch for Kinetic raspi to test with 22.04
  install (both master and master-next branches). When running "make
  clean" noticed error referencing "hio" driver that's been removed from
  Jammy kernels:

  $ make clean
  scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
  make[2]: *** No rule to make target 'ubuntu/hio/Makefile'.  Stop.
  make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
  make: *** [Makefile:1858: _clean_ubuntu] Error 2

  Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:

  commit cf58599cded35cf4affed1e659c0e2c742d3fda7
  Author: Thomas Lamprecht 
  Date:   Sat Mar 12 16:19:10 2022 +0100

  Ubuntu: remove leftover reference to ubuntu/hio driver

  A single reference to the hio driver was forgotten when it was removed
  recently. While this reference is not a problem for the build itself, it
  breaks the __clean target from 'scripts/Makefile.clean' here, as make
  cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.

  Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
  Signed-off-by: Thomas Lamprecht 
  Acked-by: Tim Gardner 
  Signed-off-by: Paolo Pisati 

  Here's some additional information for code repositories (didn't know
  if this was helpful),

  
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
  remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
  branch.kinetic-master-next.remote=kinetic-raspi
  branch.kinetic-master-next.merge=refs/heads/master-next
  branch.kinetic-master.remote=kinetic-raspi
  branch.kinetic-master.merge=refs/heads/master

  [Test Case]

  See above.

  [Fix]

  Pick commit cf58599cded35cf4affed1e659c0e2c742d3fda7 from jammy.

  [Where Problems Could Occur]

  Build failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999556/+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 1998727] Re: Fix System cannot detect bluetooth after running suspend stress test

Upgrade to linux-oem-6.0-1009 and didn't reproduce with 600 times.
@Ian, thanks

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

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

Title:
  Fix System cannot detect bluetooth after running suspend stress test

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 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
   System cannot detect bluetooth after running 
power-management/suspend-30-cycles-with-reboots

  [Fix]
   Enable BT recovery on Realtek 8852CE FW, FW would detect and recover.

  [Test Case]
  1. checkbox-cli run 
com.canonical.certification::power-management/suspend_30_cycles_with_reboots
  2. check settings > bluetooth

  [Where problems could occur]
  just enable a function from kernel and run the code in the fw.
  the main risk would be related to FW.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998727/+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 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)

After upgraded to linux-oem-6.0-1009 and plug the sim, the wwan connection is 
built.
@Ian, thanks

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

-- 
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:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
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 1998419] Re: Gnome doesn't run smooth when performing normal usage with RPL-P CPU

2022-12-13 Thread Andy Chi

Enable proposed pocket on TRBR-DVT1-C3_202211-30859, and install linux-
oem-6.0/6.0.0-1009.9, the screen movement works well.

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

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

Title:
  Gnome doesn't run smooth when performing normal usage with RPL-P CPU

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 source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Gnome desktop doesn't run smooth when performing normal usage, the cursor 
usually stops working and stuck, and then becomes back to normal.

  [Fix]
  Can't reproduce this issue with drm-tip kernel, so found below commit after 
bisected
  dc73ac63e63a drm/i915/rpl-p: Add stepping info

  [Test]
  Verified on the RPL-P machine and the cursor/window move smoothly.

  [Where problems could occur]
  Adding info for new RPL-P chipset should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998419/+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 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='

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

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

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


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  cgroup: all controllers mounted when using 'cgroup_no_v1='

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

Bug description:
  [Impact]

  When mounting a cgroup hierarchy with disabled controller in cgroup v1,
  all available controllers will be attached.
  For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
  mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
  enabled controllers will be attached except cpu.

  This exists since linux v5.1 and fixed in linux v5.11 with this commit:
  61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

  [Test Case]

  root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
  root@dut-vm:~# systemctl kexec
  root@dut-vm:~# mount | grep cgroup
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)

  
  => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
  Note that several reboots may be needed to reproduce the problem (it fails 
only when systemd tries to mount 'net_cls,net_prio' first, but the order is 
random).

  [Regression Potential]

  The patch is located in cgroup1_parse_param(), the potential
  regressions are low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988584/+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 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

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

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

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


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

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:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1983656

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

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

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

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


** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

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

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1990190] Re: Focal update: v5.4.211 upstream stable release

** Tags removed: verification-needed-focal

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

Title:
  Focal update: v5.4.211 upstream stable release

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

Bug description:
  SRU Justification

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

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

  Makefile: link with -z noexecstack --no-warn-rwx-segments
  x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
  scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover"
  ALSA: bcd2000: Fix a UAF bug on the error path of probing
  igc: Remove _I_PHY_ID checking
  wifi: mac80211_hwsim: fix race condition in pending packet
  wifi: mac80211_hwsim: add back erroneously removed cast
  wifi: mac80211_hwsim: use 32-bit skb cookie
  add barriers to buffer_uptodate and set_buffer_uptodate
  HID: wacom: Only report rotation for art pen
  HID: wacom: Don't register pad_input for touch switch
  KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case
  KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case
  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
  KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value
  KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
  KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
  mm/mremap: hold the rmap lock in write mode when moving page table entries.
  ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
  ALSA: hda/cirrus - support for iMac 12,1 model
  ALSA: hda/realtek: Add quirk for another Asus K42JZ model
  tty: vt: initialize unicode screen buffer
  vfs: Check the truncate maximum size in inode_newsize_ok()
  fs: Add missing umask strip in vfs_tmpfile
  thermal: sysfs: Fix cooling_device_stats_setup() error code path
  fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters
  usbnet: Fix linkwatch use-after-free on disconnect
  ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh()
  parisc: Fix device names in /proc/iomem
  parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode
  drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error
  drm/nouveau: fix another off-by-one in nvbios_addr
  drm/amdgpu: Check BO's requested pinning domains against its preferred_domains
  iio: light: isl29028: Fix the warning in isl29028_remove()
  fuse: limit nsec
  serial: mvebu-uart: uart2 error bits clearing
  md-raid10: fix KASAN warning
  ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr()
  PCI: Add defines for normal and subtractive PCI bridges
  powerpc/fsl-pci: Fix Class Code of PCIe Root Port
  powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E
  powerpc/powernv: Avoid crashing if rng is NULL
  MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
  coresight: Clear the connection field properly
  USB: HCD: Fix URB giveback issue in tasklet function
  ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC
  arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC
  netfilter: nf_tables: fix null deref due to zeroed list head
  epoll: autoremove wakers even more aggressively
  x86: Handle idle=nomwait cmdline properly for x86_idle
  arm64: Do not forget syscall when starting a new thread.
  arm64: fix oops in concurrently setting insn_emulation sysctls
  ext2: Add more validity checks for inode counts
  genirq: Don't return error on missing optional irq_request_resources()
  wait: Fix __wait_event_hrtimeout for RT/DL tasks
  ARM: dts: imx6ul: add missing properties for sram
  ARM: dts: imx6ul: change operating-points to uint32-matrix
  ARM: dts: imx6ul: fix csi node compatible
  ARM: dts: imx6ul: fix lcdif node compatible
  ARM: dts: imx6ul: fix qspi node compatible
  spi: synquacer: Add missing clk_disable_unprepare()
  ARM: OMAP2+: display: Fix refcount leak bug
  ACPI: EC: Remove duplicate ThinkPad X1 Carbon 6th entry from DMI quirks
  ACPI: PM: save NVS memory for Lenovo G40-45
  ACPI: LPSS: Fix missing check in register_device_clock()
  arm64: dts: qcom: ipq8074: fix NAND node name
  arm64: dts: allwinner: a64: orangepi-win: Fix LED node name
  ARM: shmobile: rcar-gen2: Increase refcount for new reference
  PM: hibernate: defer device probing when resuming from hibernation
  selinux: Add boundary check in put_entry()
  spi: spi-rspi: Fix PIO fallback on RZ platforms
  ARM:

[Kernel-packages] [Bug 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

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

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

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


** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu

  This is a new test case from bug 1988809

  Test failed with:
   Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
     INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: fib_nexthop_nongw.sh
   # Object "nexthop" is unknown, try "ip help".
   # Error: either "to" is duplicate, or "nhid" is a garbage.
   # TEST: nexthop: get route with nexthop without gw[FAIL]
   # TEST: nexthop: ping through nexthop without gw  [FAIL]
   not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1

  --

  [Impact]

  When running kselftests on Bionic with a 5.4 kernel, it would
  fail because of no nexthop capability.

  [Fix]

  We query the ip command help to know whether it is implemented
  or not, and we skip or execute the test accordingly

  [Test Plan]

  Running the test script directly in Bionic will throw a Skip,
  while running it in Focal will throw the test result.

  [Where problems could ocurr]

  The regression potential for this is low.

  [Other Info]

  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+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 1991156] Re: Focal update: v5.4.212 upstream stable release

** Tags removed: verification-needed-focal

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

Title:
  Focal update: v5.4.212 upstream stable release

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

Bug description:
  SRU Justification

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

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

  audit: fix potential double free on error path from fsnotify_add_inode_mark
  parisc: Fix exception handler for fldw and fstw instructions
  kernel/sys_ni: add compat entry for fadvise64_64
  usb: cdns3: Fix issue for clear halt endpoint
  pinctrl: amd: Don't save/restore interrupt status and wake status bits
  sched/deadline: Unthrottle PI boosted threads while enqueuing
  sched/deadline: Fix stale throttling on de-/boosted tasks
  sched/deadline: Fix priority inheritance with multiple scheduling classes
  kernel/sched: Remove dl_boosted flag comment
  xfrm: fix refcount leak in __xfrm_policy_check()
  af_key: Do not call xfrm_probe_algs in parallel
  SUNRPC: RPC level errors should set task->tk_rpc_status
  rose: check NULL rose_loopback_neigh->loopback
  net/mlx5e: Properly disable vlan strip on non-UL reps
  net: moxa: get rid of asymmetry in DMA mapping/unmapping
  bonding: 802.3ad: fix no transmission of LACPDUs
  net: ipvtap - add __init/__exit annotations to module init/exit funcs
  netfilter: ebtables: reject blobs that don't provide all entry points
  bnxt_en: fix NQ resource accounting during vf creation on 57500 chips
  netfilter: nft_payload: report ERANGE for too long offset and length
  netfilter: nft_payload: do not truncate csum_offset and csum_type
  netfilter: nft_osf: restrict osf to ipv4, ipv6 and inet families
  netfilter: nft_tunnel: restrict it to netdev family
  net: Fix data-races around weight_p and dev_weight_[rt]x_bias.
  net: Fix data-races around netdev_tstamp_prequeue.
  ratelimit: Fix data-races in ___ratelimit().
  net: Fix a data-race around sysctl_tstamp_allow_data.
  net: Fix a data-race around sysctl_net_busy_poll.
  net: Fix a data-race around sysctl_net_busy_read.
  net: Fix a data-race around netdev_budget.
  net: Fix a data-race around netdev_budget_usecs.
  net: Fix a data-race around sysctl_somaxconn.
  ixgbe: stop resetting SYSTIME in ixgbe_ptp_start_cyclecounter
  btrfs: fix silent failure when deleting root reference
  btrfs: replace: drop assert for suspended replace
  btrfs: add info when mount fails due to stale replace target
  btrfs: check if root is readonly while setting security xattr
  x86/unwind/orc: Unwind ftrace trampolines with correct ORC entry
  loop: Check for overflow while configuring loop
  asm-generic: sections: refactor memory_intersects
  s390: fix double free of GS and RI CBs on fork() failure
  ACPI: processor: Remove freq Qos request for all CPUs
  mm/hugetlb: fix hugetlb not supporting softdirty tracking
  md: call __md_stop_writes in md_stop
  perf/x86/intel/uncore: Fix broken read_counter() for SNB IMC PMU
  scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq
  mm: Force TLB flush for PFNMAP mappings before unlink_file_vma()
  s390/mm: do not trigger write fault when vma does not allow VM_WRITE
  x86/bugs: Add "unknown" reporting for MMIO Stale Data
  kbuild: Fix include path in scripts/Makefile.modpost
  Bluetooth: L2CAP: Fix build errors in some archs
  HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
  udmabuf: Set the DMA mask for the udmabuf device (v2)
  media: pvrusb2: fix memory leak in pvr_probe
  HID: hidraw: fix memory leak in hidraw_release()
  fbdev: fb_pm2fb: Avoid potential divide by zero error
  ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is 
dead
  bpf: Don't redirect packets with invalid pkt_len
  mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
  btrfs: introduce btrfs_lookup_match_dir
  btrfs: do not pin logs too early during renames
  btrfs: unify lookup return value when dir entry is missing
  drm/amd/display: Avoid MPC infinite loop
  drm/amd/display: clear optc underflow before turn off odm clock
  neigh: fix possible DoS due to net iface start/stop loop
  s390/hypfs: avoid error message under KVM
  drm/amd/display: Fix pixel clock programming
  netfilter: conntrack: NF_CONNTRACK_PROCFS should no longer default to y
  btrfs: tree-checker: check for overlapping extent items
  lib/vdso: Let do_coarse() return 0 to simplify

[Kernel-packages] [Bug 1990794] Re: ubuntu_bpf failed to build on F-azure-5.4 / B-azure-5.4 ( error: ‘bpf_object_open_opts’ undeclared)

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

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

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


** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  ubuntu_bpf failed to build on F-azure-5.4 / B-azure-5.4 ( error:
  ‘bpf_object_open_opts’ undeclared)

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released

Bug description:
  Issue found on B-azure-5.4.0-1092.97~18.04.1

  This is a regression as the test can be built and run in the last
  cycle.

  Error log:
  prog_tests/tcp_estats.c prog_tests/obj_name.c prog_tests/map_lock.c 
prog_tests/xdp_noinline.c prog_tests/global_data.c prog_tests/pkt_access.c 
-lcap -lelf -lrt -lpthread -o 
/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_progs
../lib.mk:146: recipe for target 
'/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_progs'
 failed
make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
Makefile:143: recipe for target 'all' failed
make: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs 
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs 
from latest version at 'include/uapi/linux/if_link.h'
prog_tests/send_signal.c: In function ‘test_send_signal_common’:
prog_tests/send_signal.c:52:3: warning: ignoring return value of ‘write’, 
declared with attribute warn_unused_result [-Wunused-result]
   write(pipe_c2p[1], buf, 1);
   ^~
prog_tests/send_signal.c:55:3: warning: ignoring return value of ‘read’, 
declared with attribute warn_unused_result [-Wunused-result]
   read(pipe_p2c[0], buf, 1);
   ^
prog_tests/send_signal.c:61:4: warning: ignoring return value of ‘write’, 
declared with attribute warn_unused_result [-Wunused-result]
write(pipe_c2p[1], "2", 1);
^~
prog_tests/send_signal.c:63:4: warning: ignoring return value of ‘write’, 
declared with attribute warn_unused_result [-Wunused-result]
write(pipe_c2p[1], "0", 1);
^~
prog_tests/send_signal.c:66:3: warning: ignoring return value of ‘read’, 
declared with attribute warn_unused_result [-Wunused-result]
   read(pipe_p2c[0], buf, 1);
   ^
prog_tests/send_signal.c:109:2: warning: ignoring return value of ‘read’, 
declared with attribute warn_unused_result [-Wunused-result]
  read(pipe_c2p[0], buf, 1);
  ^
prog_tests/send_signal.c:117:2: warning: ignoring return value of ‘write’, 
declared with attribute warn_unused_result [-Wunused-result]
  write(pipe_p2c[1], buf, 1);
  ^~
prog_tests/send_signal.c:131:2: warning: ignoring return value of ‘write’, 
declared with attribute warn_unused_result [-Wunused-result]
  write(pipe_p2c[1], buf, 1);
  ^~
prog_tests/stacktrace_build_id_nmi.c: In function 
‘read_perf_max_sample_freq’:
prog_tests/stacktrace_build_id_nmi.c:12:2: warning: ignoring return value 
of ‘fscanf’, declared with attribute warn_unused_result [-Wunused-result]
  fscanf(f, "%llu", _freq);
  ^~~
prog_tests/probe_user.c: In function ‘test_probe_user’:
prog_tests/probe_user.c:9:2: warning: implicit declaration of function 
‘DECLARE_LIBBPF_OPTS’ [-Wimplicit-function-declaration]
  DECLARE_LIBBPF_OPTS(bpf_object_open_opts, opts, );
  ^~~
prog_tests/probe_user.c:9:22: error: ‘bpf_object_open_opts’ undeclared 
(first use in this function); did you mean ‘bpf_object_open_attr’?
  DECLARE_LIBBPF_OPTS(bpf_object_open_opts, opts, );
  ^~~~
  bpf_object_open_attr
prog_tests/probe_user.c:9:22: note: each undeclared identifier is reported 
only once for each function it appears in

[Kernel-packages] [Bug 1994974] Re: Azure: hv_netvsc: Fix race between VF offering and VF association message from host

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

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

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


** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
  Azure: hv_netvsc: Fix race between VF offering and VF association
  message from host

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

Bug description:
  SRU Justification

  [Impact]

  During vm boot, there might be possibility that vf registration call
  comes before the vf association from host to vm.

  And this might break netvsc vf path, this is in order to prevent the
  same block vf registration until vf bind message comes from host.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  The 5.4 backport patch could hang waiting for a VF addition to
  complete.

  [Other Info]

  SF: #00347129

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994974/+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 1994987] Re: Azure: RMB Patch to backport on the Azure Linux Images

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

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

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

** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal

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

Title:
Azure: RMB Patch to backport on the Azure Linux Images

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

Bug description:
SRU Justification

[Impact]

MANA driver is not conforming to the HW specification in one small
instance.

This request from Azure LSG team to backport the rmb patch to be
backported in all the azure images.
(https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-

next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69)

Jammy and Kinetic will get this patch via stable updates.

[Test Case]

Microsoft tested

[Where things could go wrong]

At worst there might be a small performance impact.

[Other Info]

SF: #00346991

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994987/+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 1996678] Re: containerd sporadic timeouts

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

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

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


** Tags added: kernel-spammed-focal-linux-azure

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

Title:
  containerd sporadic timeouts

Status in containerd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in containerd source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  This morning I routinely upgraded security upgrades on number of
  machines.

  Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me
  `1.5.9-0ubuntu1~20.04.5`.

  What happened next:

  at some random time on machines with new containerd something happens
  with containerd tasks and/or cgroups.

  This is how it's seen in syslog:

  containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error
  msg="get state for
  2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a"
  error="context deadline exceeded: unknown"

  
  And some ctr commands:

  # ctr --namespace k8s.io task ls|grep 
2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a
  2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0
UNKNOWN

  See that the status of the task is UNKNOWN (!!!)

  # ctr --namespace k8s.io container ls|grep 
2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a
  2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a
k8s.gcr.io/pause:3.5   
io.containerd.runc.v2

  Cgroups:

  ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice 
  │ 
├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope
 …
  │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock 
--k…
  │ 
├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope
 …
  │ │ └─3264 /usr/local/bin/cephcsi --type=liveness 
--endpoint=unix:///csi/cs…
  │ 
├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope
 …
  │ │ └─2960 /usr/local/bin/cephcsi 
--nodeid=nas-decent-bobcat.dev-k8s-1.hq.w…
  │ 
└─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope
 …
  │   └─2414 /pause


  # ps auxf|grep 2414 -B 2
  root2279  0.1  0.0 114100  4956 ?Sl   Nov15   0:42 
/usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 
2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address 
/run/containerd/containerd.sock
  65535   2414  0.0  0.0964 4 ?Ss   Nov15   0:00  \_ /pause


  It happens not immediately - but after some random time. Sometimes
  it's several minutes, sometimes it's around an hour. But nonetheless -
  all machines with the new package get into this weird state.

  As long as I revert package - it all returns to run as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+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 1998576] Re: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c)

2022-12-13 Thread Kai-Heng Feng

Thanks for the report. Does the issue happen on newer 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/1998576

Title:
  UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello all!

  On Ubuntu 20.04.5 LTS, when I use the mdk3 tool
  (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA),
  it raises a kernel exception in the Wi-Fi driver:

  UBSAN: shift-out-of-bounds in 
/build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22
  shift exponent 65535 is too large for 64-bit type 'long unsigned int'

  The exact command I use is :

  mdk3 wlp2s0 b -f somefile.txt -a -s 200

  (Where wlp2s0 is my main Wi-Fi interface.)
  Here is the full logs:

  Dec  2 09:22:38 red-october kernel: [ 1228.100538] 

  Dec  2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds 
in 
/build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22
  Dec  2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is 
too large for 64-bit type 'long unsigned int'
  Dec  2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: 
ifconfig Tainted: P   OE 5.15.0-53-generic #59~20.04.1-Ubuntu
  Dec  2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK 
COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 
03/14/2022
  Dec  2 09:22:38 red-october kernel: [ 1228.102693] Call Trace:
  Dec  2 09:22:38 red-october kernel: [ 1228.102696]  
  Dec  2 09:22:38 red-october kernel: [ 1228.102701]  dump_stack_lvl+0x4a/0x63
  Dec  2 09:22:38 red-october kernel: [ 1228.102713]  dump_stack+0x10/0x16
  Dec  2 09:22:38 red-october kernel: [ 1228.102718]  ubsan_epilogue+0x9/0x49
  Dec  2 09:22:38 red-october kernel: [ 1228.102723]  
__ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e
  Dec  2 09:22:38 red-october kernel: [ 1228.102734]  
iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm]
  Dec  2 09:22:38 red-october kernel: [ 1228.102770]  
iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm]
  Dec  2 09:22:38 red-october kernel: [ 1228.102798]  
iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm]
  Dec  2 09:22:38 red-october kernel: [ 1228.102821]  
iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm]
  Dec  2 09:22:38 red-october kernel: [ 1228.102847]  
drv_add_interface+0x4a/0x100 [mac80211]
  Dec  2 09:22:38 red-october kernel: [ 1228.102912]  
ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211]
  Dec  2 09:22:38 red-october kernel: [ 1228.102980]  
ieee80211_do_open+0x867/0x970 [mac80211]
  Dec  2 09:22:38 red-october kernel: [ 1228.103041]  ? 
ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211]
  Dec  2 09:22:38 red-october kernel: [ 1228.103104]  ieee80211_open+0x70/0x90 
[mac80211]
  Dec  2 09:22:38 red-october kernel: [ 1228.103165]  __dev_open+0xe8/0x1a0
  Dec  2 09:22:38 red-october kernel: [ 1228.103172]  
__dev_change_flags+0x190/0x200
  Dec  2 09:22:38 red-october kernel: [ 1228.103178]  dev_change_flags+0x26/0x70
  Dec  2 09:22:38 red-october kernel: [ 1228.103183]  devinet_ioctl+0x5f2/0x780
  Dec  2 09:22:38 red-october kernel: [ 1228.103192]  inet_ioctl+0x169/0x190
  Dec  2 09:22:38 red-october kernel: [ 1228.103199]  sock_do_ioctl+0x47/0x100
  Dec  2 09:22:38 red-october kernel: [ 1228.103206]  sock_ioctl+0xf3/0x310
  Dec  2 09:22:38 red-october kernel: [ 1228.103211]  ? 
syscall_exit_to_user_mode+0x27/0x50
  Dec  2 09:22:38 red-october kernel: [ 1228.103218]  ? do_syscall_64+0x69/0xc0
  Dec  2 09:22:38 red-october kernel: [ 1228.103223]  __x64_sys_ioctl+0x95/0xd0
  Dec  2 09:22:38 red-october kernel: [ 1228.103232]  do_syscall_64+0x5c/0xc0
  Dec  2 09:22:38 red-october kernel: [ 1228.103236]  ? 
irqentry_exit_to_user_mode+0x9/0x20
  Dec  2 09:22:38 red-october kernel: [ 1228.103241]  ? irqentry_exit+0x1d/0x30
  Dec  2 09:22:38 red-october kernel: [ 1228.103246]  ? 
exc_page_fault+0x89/0x170
  Dec  2 09:22:38 red-october kernel: [ 1228.103252]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Dec  2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab
  Dec  2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 
7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 
1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 
d8 64 89 01 48
  Dec  2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 
EFLAGS: 0202 ORIG_RAX: 0010
  Dec  2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 
7ffc147740b0 RCX: 7f487d3b63ab
  Dec  2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7ffc147740b0 RSI: 
8914 RDI: 0004
  Dec  2

[Kernel-packages] [Bug 1994974] Re: Azure: hv_netvsc: Fix race between VF offering and VF association message from host

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

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

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


** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  Azure: hv_netvsc: Fix race between VF offering and VF association
  message from host

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

Bug description:
  SRU Justification

  [Impact]

  During vm boot, there might be possibility that vf registration call
  comes before the vf association from host to vm.

  And this might break netvsc vf path, this is in order to prevent the
  same block vf registration until vf bind message comes from host.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  The 5.4 backport patch could hang waiting for a VF addition to
  complete.

  [Other Info]

  SF: #00347129

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994974/+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 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning

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

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

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


** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  [Azure][Arm64] Unable to detect all VF nics / Failing provisioning

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

Bug description:
  SRU Justification

  [Impact]

  SRIOV tests fail where sometimes 0 and other times only 6 VF devices are 
detected instead of 8.
  This is using the 5.19 Edge kernel.
  Example failure from LISA test run -
  Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. 
AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected 
<6> to be equal to <8>, but was not.

  Microsoft has requested the inclusion of [1], now in linux-next.

  1 -
  
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
  fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  VNICs could go undetected.

  [Other Info]

  SF: #00346751

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+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 1996740] Re: 5.15.0-53-generic no longer boots

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

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

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


** Tags added: kernel-spammed-jammy-linux-azure

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

Title:
  5.15.0-53-generic no longer boots

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

Bug description:
  == SRU Justification ==
  [Impact]
  "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp
  displays" caused AMD Navi10 GFX to panic at boot.

  [Fix]
  Backport the revised version of "drm/amd/display: Add helper for
  blanking all dp displays".

  [Test]
  Users confirmed the issue went away with this fix.
  We also verified the original issue we fixed didn't reappear.

  [Where problems could occur]
  We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many
  cases are untested, hence the potential risk is there.

  == Original Bug Report ==

  Running Ubuntu 22.04.1 Jammy.
  After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no 
longer fully boots.
  After the normal splash screen the screen goes black and the computer is not 
reachable on the network. Changing to another TTY does not work.

  New kernel version: 5.15.0-53.59

  I will attach the output of journalctl -b -1, please let me know what other 
info you need.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johan  2549 F pulseaudio
   /dev/snd/controlC0:  johan  2549 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-12-01 (714 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.

   wgnfs no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C52
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.G0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M-A PRO MAX (MS-7C52)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C52
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1996806] Re: Azure: Jammy fio test causes panic

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

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

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

** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
Azure: Jammy fio test causes panic

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

Bug description:
SRU Justification

[Impact]

During Storage performance tests, 16 disks are attached and fio is
ran. The fio command does not consistently result in a kernel panic,
but the test runs fio enough times to result in consistent kernel
panic. The panic is most often observed on instances with many cores
and disks.

[Test Case]

Using an instance with 96 cores and 16 disks:

sudo fio --ioengine=libaio --bs=1024K

--filename=/dev/sda:/dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi:/dev/sdj:/dev/sdk:/dev/sdl:/dev/sdm:/dev/sdn:/dev/sdo:/dev/sdp
--readwrite=read --runtime=120 --iodepth=32 --numjob=96
--name=iteration23 --direct=1 --size=8192M --group_reporting
--overwrite=1

Test results from Microsoft and myself are positive. No panics were
observed.

[Regression Potential]

The fix is an upstream patch from 5.17, commit
0bd2fbee9d0b7f801a9c0264d90b1e0d8053f395 ('scsi: storvsc: Fix unsigned
comparison to zero'). Regression potential is low.

[Other Info]

SF: #00346757

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

[Kernel-packages] [Bug 1998351] Re: Azure: MANA New Feature MANA XDP_Redirect Action

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

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

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


** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  Azure: MANA New Feature MANA XDP_Redirect Action

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

Bug description:
  SRU Justification

  [Impact]

  XDP Redirection is not implemented in 5.15 Azure tuned kernels.

  Microsoft has requested the addition of this feature:

  commit 7a8938cd024d383c12bb1e08025db6ea3d551103 ("net: mana: Add
  support of XDP_REDIRECT action")

  [Test Plan]

  Microsoft tested with positive results.

  [Where things could go wrong]

  Network skb routing could go awry.

  [Other info]

  SF: #00340222

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1998351/+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 1998838] Re: Azure: Jammy fio test hangs, swiotlb buffers exhausted

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

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

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


** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy

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

Title:
  Azure: Jammy fio test hangs, swiotlb buffers exhausted

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Hello Canonical Team,

  This issue was found while doing the validation on CPC's Jammy CVM
  image. We are up against a tight timeline to deliver this to a partner
  on 10/5. Would appreciate prioritizing this.

  While running fio, the command fails to exit after 2 minutes. I
  watched `top` as the command hung and I saw kworkers getting blocked.

  sudo fio --ioengine=libaio --bs=4K
  
--filename=/dev/sdc1:/dev/sdd1:/dev/sde1:/dev/sdf1:/dev/sdg1:/dev/sdh1:/dev/sdi1:/dev/sdj1:/dev/sdk1:/dev/sdl1:/dev/sdm1:/dev/sdn1:/dev/sdo1:/dev/sdp1:/dev/sdq1:/dev/sdr1
  --readwrite=randwrite --runtime=120 --iodepth=1 --numjob=96
  --name=iteration9 --direct=1 --size=8192M --group_reporting
  --overwrite=1

  
  Example system logs:
  
---
  [ 1096.297641] INFO: task kworker/u192:0:8 blocked for more than 120 seconds.
  [ 1096.302785] Tainted: G W 5.15.0-1024-azure #30-Ubuntu
  [ 1096.306312] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1096.310489] INFO: task jbd2/sda1-8:1113 blocked for more than 120 seconds.
  [ 1096.313900] Tainted: G W 5.15.0-1024-azure #30-Ubuntu
  [ 1096.317481] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1096.324117] INFO: task systemd-journal:1191 blocked for more than 120 
seconds.
  [ 1096.331219] Tainted: G W 5.15.0-1024-azure #30-Ubuntu
  [ 1096.335332] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  
---
  
---
  [ 3241.013230] systemd-udevd[1221]: sdl1: Worker [6686] processing 
SEQNUM=13323 killed
  [ 3261.492691] systemd-udevd[1221]: sdl1: Worker [6686] failed
  
---

  TOP report:
  
---
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
  417 root 20 0 0 0 0 R 66.2 0.0 0:34.61 ksoftirqd/59
  435 root 20 0 0 0 0 I 24.5 0.0 0:09.03 kworker/59:1-mm_percpu_wq
  416 root rt 0 0 0 0 S 23.5 0.0 0:01.86 migration/59
  366 root 0 -20 0 0 0 I 19.2 0.0 0:16.64 kworker/49:1H-kblockd
  378 root 0 -20 0 0 0 I 17.9 0.0 0:15.71 kworker/51:1H-kblockd
  455 root 0 -20 0 0 0 I 17.9 0.0 0:14.76 kworker/62:1H-kblockd
  135 root 0 -20 0 0 0 I 17.5 0.0 0:13.08 kworker/17:1H-kblockd
  420 root 0 -20 0 0 0 I 16.9 0.0 0:14.63 kworker/58:1H-kblockd
  ...
  
---

  
  LISAv3 Testcase: perf_premium_datadisks_4k
  Image : "canonical-test 0001-com-ubuntu-confidential-vm-jammy-preview 
22_04-lts-cvm latest"
  VMSize : "Standard_DC96ads_v5"

  For repro-ability, I am seeing this every time I run the storage perf
  tests. It always seems to happen on iteration 9 or 10. When running
  manually, I had to run the command three or four times to reproduce
  the issue.

  [Test Case]

  Microsoft tested, requires lots of cores (96) and disks (16)

  [Where things could go wrong]

  swiotlb buffers could be double freed.

  [Other Info]

  SF: #00349781

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1998838/+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 1999589] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1999589

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x
  Kinetic

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  All of the sm4* ciper testcases are failing in net:tls for kinetic
  linux 5.19.0-27.28

  These seem like new testcases that have not been run before.

  and this has only been seen as far as I am aware of on s390x
  - 
  21:31:48 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendfile ...
  21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0)
  21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion
  21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendfile
  21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile
  21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.send_then_sendfile 
...
  21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) 
== 0 (0)
  21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion
  21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.send_then_sendfile
  21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile
  21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.recv_max ...
  21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0)
  21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion
  21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.recv_max
  21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max
  21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.recv_small ...
  21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0)
  21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion
  21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.recv_small
  21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small
  21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.msg_more ...
  21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0)
  21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion
  21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.msg_more
  21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more
  21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.msg_more_unsent ...
  21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 
(0)
  21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion
  21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.msg_more_unsent
  21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent
  21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_single ...
  21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 
(0)
  21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion
  21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_single
  21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single
  21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_fragmented 
...
  21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) 
== 0 (0)
  21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion
  21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_fragmented
  21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented
  21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_large ...
  21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 
(0)
  21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion
  21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_large
  21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large
  21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_multiple 
...
  21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 
0 (0)
  21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion
  21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_multiple
  21:31:50 DEBUG| [stdout] #

[Kernel-packages] [Bug 1999589] [NEW] net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic

2022-12-13 Thread Luke Nowakowski-Krijger

Public bug reported:

All of the sm4* ciper testcases are failing in net:tls for kinetic linux
5.19.0-27.28

These seem like new testcases that have not been run before.

and this has only been seen as far as I am aware of on s390x
- 
21:31:48 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendfile ...
21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0)
21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion
21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendfile
21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile
21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.send_then_sendfile 
...
21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) == 
0 (0)
21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion
21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.send_then_sendfile
21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile
21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.recv_max ...
21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0)
21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion
21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.recv_max
21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max
21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.recv_small ...
21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0)
21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion
21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.recv_small
21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small
21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.msg_more ...
21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0)
21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion
21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.msg_more
21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more
21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.msg_more_unsent ...
21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 
(0)
21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion
21:31:49 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.msg_more_unsent
21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent
21:31:49 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_single ...
21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 (0)
21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion
21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_single
21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single
21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_fragmented 
...
21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) == 
0 (0)
21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion
21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_fragmented
21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented
21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_large ...
21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 (0)
21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion
21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_large
21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large
21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.sendmsg_multiple ...
21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 0 
(0)
21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion
21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.sendmsg_multiple
21:31:50 DEBUG| [stdout] # not ok 206 tls.13_sm4_gcm.sendmsg_multiple
21:31:50 DEBUG| [stdout] # #  RUN   
tls.13_sm4_gcm.sendmsg_multiple_stress ...
21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple_stress:Expected ret 
(-1) == 0 (0)
21:31:50 DEBUG| [stdout] # # sendmsg_multiple_stress: Test terminated by 
assertion
21:31:50 DEBUG| [stdout] # #  FAIL  
tls.13_sm4_gcm.sendmsg_multiple_stress
21:31:50 DEBUG| [stdout] # not ok 207 tls.13_sm4_gcm.sendmsg_multiple_stress
21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.splice_from_pipe ...
21:31:50 DEBUG| [stdout] # # tls.c:314:splice_from_pipe:Expected ret (-1) == 0 
(0)
21:31:50 DEBUG| [stdout] # # splice_from_pipe: Test terminated by assertion
21:31:50 DEBUG| [stdout] # #  FAIL  tls.13_sm4_gcm.splice_from_pipe
21:31:50 DEBUG| [stdout] # not ok 208 tls.13_sm4_gcm.splice_from_pipe
21:31:50 DEBUG| [stdout] # #  RUN   tls.13_sm4_gcm.splice_from_pipe2 ...
21:31:50 DEBUG| [stdout] # # tls.c:314:splice_from_pipe2:Expected ret (-1) == 0 
(0)
21:31:50 DEBUG| [stdout] # #

[Kernel-packages] [Bug 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

2022-12-13 Thread Kai-Heng Feng

So it's actually a regression in iwlwifi driver? Hopefully it's fixed in
later kernels...

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [DEL] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG]

[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash

2022-12-13 Thread Mauro Amico

Same issue. 
None of the workarounds tried solved the problem.

* Ubuntu 22.10 (fresh install)
* HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC/89C0, BIOS U97 Ver. 
01.03.00 08/24/2022
* nvidia-driver-525 (525.60.11-0ubuntu0.22.10.1)
* Linux kernel 5.19.0-26-generic

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

Title:
  No video after wake from S3 due to Nvidia driver crash

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1946303] Re: No video after wake from S3 due to Nvidia driver crash

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: New => Confirmed

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

Title:
  No video after wake from S3 due to Nvidia driver crash

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1946303] Re: No video after wake from S3 due to Nvidia driver crash

2022-12-13 Thread Mauro Amico

** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No video after wake from S3 due to Nvidia driver crash

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1996112] Re: Virtual GPU driver packaging regression

2022-12-13 Thread Luke Nowakowski-Krijger

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

** Changed in: linux (Ubuntu Lunar)
   Status: Confirmed => Fix Committed

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

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

Title:
  Virtual GPU driver packaging regression

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

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  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.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _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

[Kernel-packages] [Bug 1918252] Re: WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c]

2022-12-13 Thread Alexander Stukanov

The linked entry seems to mention the same HW and might help to reduce the 
complexity of implementation:
https://forums.lenovo.com/t5/Other-Linux-Discussions/Finally-X55-5G-modem-works-under-linux/m-p/5082236

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

Title:
  WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is no driver for it [03f0:0a6c].

  using 5.10 kernel.

  $ sudo lspci -nnnv -s 55:00.0
  55:00.0 Wireless controller [0d40]: Device [03f0:0a6c]
Subsystem: Hewlett-Packard Company Device [103c:877f]
Flags: fast devsel
Memory at 6e30 (64-bit, non-prefetchable) [disabled] [size=4K]
Memory at 6e301000 (64-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Secondary PCI Express
Capabilities: [168] Physical Layer 16.0 GT/s 
Capabilities: [18c] Lane Margining at the Receiver 
Capabilities: [19c] Transaction Processing Hints
Capabilities: [228] Latency Tolerance Reporting
Capabilities: [230] L1 PM Substates
Capabilities: [240] Data Link Feature 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918252/+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 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org

2022-12-13 Thread Don Brace

ok, I am spoiled by git-backport.

Here is the list that will work for you.

git cherry-pick -xs 0ca190805784
git cherry-pick -xs 64fc9015fbeb
git cherry-pick -xs c4ff687d25c0
git cherry-pick -xs c57ee4ccb358
git cherry-pick -xs 2a47834d9452
git cherry-pick -xs 70ba20be4bb1
git cherry-pick -xs 94a68c814328
git cherry-pick -xs b4dc06a9070e
git cherry-pick -xs 9e98e60bfca3
git cherry-pick -xs 42dc0426fbbb
git cherry-pick -xs b73357a1fd39
git cherry-pick -xs 27655e9db479
git cherry-pick -xs 5d8fbce04d36
git cherry-pick -xs 00598b056aa6
git cherry-pick -xs c52efc923856
git cherry-pick -xs 5e6935864d81
git cherry-pick -xs c66e078ad89e
git cherry-pick -xs 291c2e0071ef
git cherry-pick -xs 62ed6622aaf0
git cherry-pick -xs 31b17c3aeb5e
git cherry-pick -xs c1ea387d998a
git cherry-pick -xs 8946ea283808
git cherry-pick -xs 4e7d26029ee7
git cherry-pick -xs 1d393227fc76
git cherry-pick -xs dab5378485f6
git cherry-pick -xs 297bdc540f0e
git cherry-pick -xs 904f2bfda65e
git cherry-pick -xs 331f7e998b20
git cherry-pick -xs 44e68c4af5d2
git cherry-pick -xs 2a9c2ba2bc47
git cherry-pick -xs 85b41834b0f4
git cherry-pick -xs 69695aeaa662
git cherry-pick -xs 6ce3cfb365eb
git cherry-pick -xs cf15c3e734e8
git cherry-pick -xs 2d80f4054f7f
git cherry-pick -xs 6d567dfee0b7
git cherry-pick -xs e4b73b3fa2b9
git cherry-pick -xs f54f85dfd757
git cherry-pick -xs b27ac2faa2fc
git cherry-pick -xs 0b93cf2a9097
git cherry-pick -xs 7c56850637ea
git cherry-pick -xs cbe42ac15698
git cherry-pick -xs cc9befcbbb5e
git cherry-pick -xs 14063fb625c4
git cherry-pick -xs 921800a1deea
git cherry-pick -xs 2ae45329a956

-- 
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 latest kernel.org

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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.

  [impact]
  This patches correct some bugs and add support for more PCI devices. Also, 
the in-box driver is largely out-of-date with kernel.org.

  [fix]

[Kernel-packages] [Bug 1982582] Re: [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)

2022-12-13 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR
  nor z/VM guest)

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in kdump-tools package in Ubuntu:
  Fix Released
Status in kdump-tools source package in Jammy:
  Fix Released
Status in kdump-tools source package in Kinetic:
  Fix Released
Status in kdump-tools source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * Unable to install the kdump-tools package in Jammy (or newer),
 neither on LPARs, nor on z/VM guests.

   * The issue is in debian/kdump-tools.postinst, function 'update_zipl()',
 where there is a '--debconf-ok' argument missing for ucf.

  [ Fixes ]

   * Add argument '--debconf-ok' to ucf call in 'update_zipl()' in the
 kdump-tools postinst script.

  [ Test Plan ]

   * Have an Ubuntu Server on s390x (Jammy or newer) installation
 on LPAR and z/VM and install the kdump-tools package with:
 sudo apt install kdump-tools

   * The broken package fails with an error message like this:
 "ErrorMessage:
  installed kdump-tools package post-installation script subprocess
  returned error exit status 2
  ...
  Setting up kdump-tools (1:1.6.10ubuntu1) ...
  *** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok to ucf. The maintainer
script should be fixed to not stop debconf before calling ucf,
and pass it this parameter. For now, ucf will revert to using
old-style, non-debconf prompting. Ugh!
  
  Please inform the package maintainer about this problem.
  Need debconf to interact 'dpkg' error processing package kdump-tools 
(--configure):
  installed kdump-tools package post-installation script subprocess
  returned error exit status 2"

   * The fixes package will just flawlessly install.

  [ Where problems could occur ]

   * It's just a one line change adding the argument '--debconf-ok' to ucf;
 like in other occurrences in the postinst script.

   * So the change is fortunately very traceable.

   * If done at a wrong spot, it may accidentally indicate that it's ok for ucf
 to use an existing debconf instance for prompting, even if not desired.

   * It can cuase issue with maintainer scripts that used debconf where
 ucf had to disable/cripple debconf before running ucf.

   * The argument tells the maintainer script that it's safe to use debconf,
 even when the script discovers that debconf is already running.
  __

  Unable to install kdump-tools on 22.04 (Jammy) on s390x (LPAR nor z/VM guest)
  Errors were encountered while processing:
   kdump-tools
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Contact Information = Vanessa Baeza/vanessa.ba...@ibm.com

  ---uname output---
  Linux ilzlnx15 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:22:27 UTC 2022 
s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   apt-get install kdump-tools
  or
  apt-get install linux-crashdump

  == Comment: #1 - Ruth Vanessa Baeza Elizalde  -
  2022-07-21 14:09:21 ==

  == Comment: #6 - Steffen Maier  - 2022-07-22 06:15:06 ==
  (In reply to comment #1)
  > Created attachment 155027 [details]
  > sosreport-ilzlnx15-199072-2022-07-21-cpplakh

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat sos_commands/kdump/kdump-config_show
   * /etc/default/kdump-tools: USE_KDUMP is not set or zero
   * no crashkernel= parameter in the kernel cmdline

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat ./proc/cmdline
  
root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat etc/zipl.conf
  # This has been modified by the MAAS curtin installer
  [defaultboot]
  default=ubuntu
  [ubuntu]
  target = /boot
  image = /boot/vmlinuz
  ramdisk = /boot/initrd.img
  parameters = 
root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH

  Looks like some preconditions for kdump are not fulfilled.
  [https://ubuntu.com/server/docs/kernel-crash-dump]
  Are those supposed to be created by the installation of kdump-tools or does 
that package require those pre-reqs to already be

[Kernel-packages] [Bug 1998487] Re: zfs-dkms: support linux 6.1

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  zfs-dkms: support linux 6.1

Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  The current version of zfs-dkms available in lunar (2.1.5) fails to
  build with kernels >= 6.1.

  [Test case]

  $ apt install zfs-dkms

  [Fix]

  Resync with the latest zfs-linux from debian unstable and apply the
  following upstream patch to properly support linux 6.1:

  ecb6a5081 ("Linux 6.1 compat: change order of sys/mutex.h includes")

  [Regression potential]

  Newer version of zfs can introduce potential regressions, so this
  change should be limited to lunar for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1998487/+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 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org

2022-12-13 Thread Don Brace

Here is the list I pulled from linux-next
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

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
2ae45329a956 scsi: smartpqi: Change version to 2.1.20-035
921800a1deea scsi: smartpqi: Initialize feature section info
14063fb625c4 scsi: smartpqi: Add controller cache flush during rmmod
cc9befcbbb5e scsi: smartpqi: Correct device removal for multi-actuator devices
cbe42ac15698 scsi: smartpqi: Change sysfs raid_level attribute to N/A for 
controllers
7c56850637ea scsi: smartpqi: Correct max LUN number
0b93cf2a9097 scsi: smartpqi: Add new controller PCI IDs
b27ac2faa2fc scsi: smartpqi: Convert to host_tagset


Steps:
1. Save the above list to file git_backport_6.2_scsi-next
2. git remote add linux_next 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
3. git fetch linux_next
4. git-backport  --sort -d /tmp/patches_scsi_next 
../../linux/git_backport_6.2_scsi-next
5. git am -s /tmp/patches_scsi_next/*.diff

No conflicts.
3. 
1.

-- 
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 latest kernel.org

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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:

[Kernel-packages] [Bug 1982582] Re: [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)

This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2.1

---
kdump-tools (1:1.6.10ubuntu2.1) jammy; urgency=medium

  * Modifed ucf call in d/kdump-tools.postinst to use option
'--debconf-ok' to fix a package install issue (LP: #1982582).

 -- Frank Heimes   Wed, 23 Nov 2022 19:12:58
+0100

** Changed in: kdump-tools (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR
  nor z/VM guest)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in kdump-tools package in Ubuntu:
  Fix Released
Status in kdump-tools source package in Jammy:
  Fix Released
Status in kdump-tools source package in Kinetic:
  Fix Released
Status in kdump-tools source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * Unable to install the kdump-tools package in Jammy (or newer),
 neither on LPARs, nor on z/VM guests.

   * The issue is in debian/kdump-tools.postinst, function 'update_zipl()',
 where there is a '--debconf-ok' argument missing for ucf.

  [ Fixes ]

   * Add argument '--debconf-ok' to ucf call in 'update_zipl()' in the
 kdump-tools postinst script.

  [ Test Plan ]

   * Have an Ubuntu Server on s390x (Jammy or newer) installation
 on LPAR and z/VM and install the kdump-tools package with:
 sudo apt install kdump-tools

   * The broken package fails with an error message like this:
 "ErrorMessage:
  installed kdump-tools package post-installation script subprocess
  returned error exit status 2
  ...
  Setting up kdump-tools (1:1.6.10ubuntu1) ...
  *** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok to ucf. The maintainer
script should be fixed to not stop debconf before calling ucf,
and pass it this parameter. For now, ucf will revert to using
old-style, non-debconf prompting. Ugh!
  
  Please inform the package maintainer about this problem.
  Need debconf to interact 'dpkg' error processing package kdump-tools 
(--configure):
  installed kdump-tools package post-installation script subprocess
  returned error exit status 2"

   * The fixes package will just flawlessly install.

  [ Where problems could occur ]

   * It's just a one line change adding the argument '--debconf-ok' to ucf;
 like in other occurrences in the postinst script.

   * So the change is fortunately very traceable.

   * If done at a wrong spot, it may accidentally indicate that it's ok for ucf
 to use an existing debconf instance for prompting, even if not desired.

   * It can cuase issue with maintainer scripts that used debconf where
 ucf had to disable/cripple debconf before running ucf.

   * The argument tells the maintainer script that it's safe to use debconf,
 even when the script discovers that debconf is already running.
  __

  Unable to install kdump-tools on 22.04 (Jammy) on s390x (LPAR nor z/VM guest)
  Errors were encountered while processing:
   kdump-tools
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Contact Information = Vanessa Baeza/vanessa.ba...@ibm.com

  ---uname output---
  Linux ilzlnx15 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:22:27 UTC 2022 
s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   apt-get install kdump-tools
  or
  apt-get install linux-crashdump

  == Comment: #1 - Ruth Vanessa Baeza Elizalde  -
  2022-07-21 14:09:21 ==

  == Comment: #6 - Steffen Maier  - 2022-07-22 06:15:06 ==
  (In reply to comment #1)
  > Created attachment 155027 [details]
  > sosreport-ilzlnx15-199072-2022-07-21-cpplakh

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat sos_commands/kdump/kdump-config_show
   * /etc/default/kdump-tools: USE_KDUMP is not set or zero
   * no crashkernel= parameter in the kernel cmdline

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat ./proc/cmdline
  
root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat etc/zipl.conf
  # This has been modified by the MAAS curtin installer
  [defaultboot]
  default=ubuntu
  [ubuntu]
  target = /boot
  image = /boot/vmlinuz
  ramdisk = /boot/initrd.img
  parameters =

[Kernel-packages] [Bug 1982582] Re: [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)

This bug was fixed in the package kdump-tools - 1:1.8ubuntu1.1

---
kdump-tools (1:1.8ubuntu1.1) kinetic; urgency=medium

  * Modifed ucf call in d/kdump-tools.postinst to use option
'--debconf-ok' to fix a package install issue (LP: #1982582).

 -- Frank Heimes   Wed, 23 Nov 2022 19:07:18
+0100

** Changed in: kdump-tools (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR
  nor z/VM guest)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in kdump-tools package in Ubuntu:
  Fix Released
Status in kdump-tools source package in Jammy:
  Fix Released
Status in kdump-tools source package in Kinetic:
  Fix Released
Status in kdump-tools source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * Unable to install the kdump-tools package in Jammy (or newer),
 neither on LPARs, nor on z/VM guests.

   * The issue is in debian/kdump-tools.postinst, function 'update_zipl()',
 where there is a '--debconf-ok' argument missing for ucf.

  [ Fixes ]

   * Add argument '--debconf-ok' to ucf call in 'update_zipl()' in the
 kdump-tools postinst script.

  [ Test Plan ]

   * Have an Ubuntu Server on s390x (Jammy or newer) installation
 on LPAR and z/VM and install the kdump-tools package with:
 sudo apt install kdump-tools

   * The broken package fails with an error message like this:
 "ErrorMessage:
  installed kdump-tools package post-installation script subprocess
  returned error exit status 2
  ...
  Setting up kdump-tools (1:1.6.10ubuntu1) ...
  *** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok to ucf. The maintainer
script should be fixed to not stop debconf before calling ucf,
and pass it this parameter. For now, ucf will revert to using
old-style, non-debconf prompting. Ugh!
  
  Please inform the package maintainer about this problem.
  Need debconf to interact 'dpkg' error processing package kdump-tools 
(--configure):
  installed kdump-tools package post-installation script subprocess
  returned error exit status 2"

   * The fixes package will just flawlessly install.

  [ Where problems could occur ]

   * It's just a one line change adding the argument '--debconf-ok' to ucf;
 like in other occurrences in the postinst script.

   * So the change is fortunately very traceable.

   * If done at a wrong spot, it may accidentally indicate that it's ok for ucf
 to use an existing debconf instance for prompting, even if not desired.

   * It can cuase issue with maintainer scripts that used debconf where
 ucf had to disable/cripple debconf before running ucf.

   * The argument tells the maintainer script that it's safe to use debconf,
 even when the script discovers that debconf is already running.
  __

  Unable to install kdump-tools on 22.04 (Jammy) on s390x (LPAR nor z/VM guest)
  Errors were encountered while processing:
   kdump-tools
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Contact Information = Vanessa Baeza/vanessa.ba...@ibm.com

  ---uname output---
  Linux ilzlnx15 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:22:27 UTC 2022 
s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   apt-get install kdump-tools
  or
  apt-get install linux-crashdump

  == Comment: #1 - Ruth Vanessa Baeza Elizalde  -
  2022-07-21 14:09:21 ==

  == Comment: #6 - Steffen Maier  - 2022-07-22 06:15:06 ==
  (In reply to comment #1)
  > Created attachment 155027 [details]
  > sosreport-ilzlnx15-199072-2022-07-21-cpplakh

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat sos_commands/kdump/kdump-config_show
   * /etc/default/kdump-tools: USE_KDUMP is not set or zero
   * no crashkernel= parameter in the kernel cmdline

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat ./proc/cmdline
  
root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH

  
[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$
 cat etc/zipl.conf
  # This has been modified by the MAAS curtin installer
  [defaultboot]
  default=ubuntu
  [ubuntu]
  target = /boot
  image = /boot/vmlinuz
  ramdisk = /boot/initrd.img
  parameters =

[Kernel-packages] [Bug 1968701] Re: [amdgpu] GPU freezes sometimes after suspend

2022-12-13 Thread Ville Aakko

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1968701

Title:
  [amdgpu] GPU freezes sometimes after suspend

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Sometimes (but not always) the GPU fails to wake up properly from
  suspend. Sometimes the laptop will work correctly.

  The user (using X.org) will experience a black screen and an apparent
  freeze. If one waits long enough (tens of seconds - up to a few
  minutes), there will be very slow updates of the screen display
  (typically a lock screen) and some intermittent corruption.

  CAPS LOCK works One can change to a VT, but there can be a long delay
  until the system responds. Once in a VT, the system can be restarted
  properly.

  H/W: Lenovo P14s Gen2 AMD (5850U). I didn't experience this bug on
  Impish Indri, it surfaced after installing Jammy. I'm using X.org (KDE
  Plasma).

  Attaching a trace from a failed resume.

  Very likely related / the same upstream bug:
  https://gitlab.freedesktop.org/drm/amd/-/issues/1850

  I also get similar Fence fallback timer messages in log until
  rebooted:

  Apr 12 12:33:36 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:36 catonthemove kernel: [drm] Fence fallback timer expired on 
ring gfx 
  Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on 
ring gfx 
  Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on 
ring gfx 
  Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0

  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-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ville  1890 F pulseaudio
   /dev/snd/pcmC1D0p:   ville  1890 F...m pulseaudio
   /dev/snd/controlC2:  ville  1890 F pulseaudio
   /dev/snd/controlC0:  ville  1890 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Apr 12 12:55:10 2022
  InstallationDate: Installed on 2021-12-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 
(20211013)
  MachineType: LENOVO 21A0CTO1WW
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro 
resume=UUID=e12c5a05-a085-4ccc-bbf1-8cd5f6511d99
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-31 (11 days ago)
  dmi.bios.date: 03/01/2022
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET45W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  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:bvrR1MET45W(1.15):bd03/01/2022:br1.15:efr1.15:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968701/+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 1986717] Re: Update ice driver to support E823 devices

2022-12-13 Thread Jeff Lane 

** Changed in: linux (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  Update ice driver to support E823 devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification:

  Impact:
  Ice driver does not support E823 in 5.4.  This was introduced in 5.7, but is 
part of the Ice Lake D platform which is otherwise supported in 5.4.  One of 
the hardware vendors has requested that we update Ice in 5.4 to support E823.

  Fix:
  After talking with engineers upstream this should be the only patch needed to 
add the support that is missing in 5.4

  e36aeec0f4e5 ice: add support for E823 devices

  Testcase:
  Load ice driver on system with E823 device present and ensure the device is 
seen by the system

  Other Info:

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+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 1999554] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1999554

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  LTP uevent01 will fail on GCP n2d-standard-64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Because udev takes too long to release the loop device, LTP test
  uevent01 (and some other tests) may warn about not being able to
  detach the loop device. This is identified as a failure.

  
  ubuntu@selfprovisioned-cascardo-n2d:~$ sudo ./uevent01 
  tst_test.c:1423: TINFO: Timeout per run is 0h 05m 00s
  tst_device.c:88: TINFO: Found free device 6 '/dev/loop6'
  uevent01.c:24: TINFO: Attaching device /dev/loop6
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: DISK_MEDIA_CHANGE=1
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2959
  uevent.h:140: TPASS: Got expected UEVENT
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2960
  uevent.h:140: TPASS: Got expected UEVENT
  uevent01.c:26: TINFO: Detaching device /dev/loop6
  tst_device.c:254: TWARN: ioctl(/dev/loop6, LOOP_CLR_FD, 0) no ENXIO for too 
long

  Summary:
  passed   2
  failed   0
  broken   0
  skipped  0
  warnings 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999554/+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 1999556] [NEW] commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile

2022-12-13 Thread Brian Wood

Public bug reported:

Added Linux kernel remote branch for Kinetic raspi to test with 22.04
install (both master and master-next branches). When running "make
clean" noticed error referencing "hio" driver that's been removed from
Jammy kernels:

$ make clean
scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
make[2]: *** No rule to make target 'ubuntu/hio/Makefile'.  Stop.
make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
make: *** [Makefile:1858: _clean_ubuntu] Error 2

Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:

commit cf58599cded35cf4affed1e659c0e2c742d3fda7
Author: Thomas Lamprecht 
Date:   Sat Mar 12 16:19:10 2022 +0100

Ubuntu: remove leftover reference to ubuntu/hio driver

A single reference to the hio driver was forgotten when it was removed
recently. While this reference is not a problem for the build itself, it
breaks the __clean target from 'scripts/Makefile.clean' here, as make
cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.

Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
Signed-off-by: Thomas Lamprecht 
Acked-by: Tim Gardner 
Signed-off-by: Paolo Pisati 

Here's some additional information for code repositories (didn't know if
this was helpful),

remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
branch.kinetic-master-next.remote=kinetic-raspi
branch.kinetic-master-next.merge=refs/heads/master-next
branch.kinetic-master.remote=kinetic-raspi
branch.kinetic-master.merge=refs/heads/master

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in
  kinetic master to remove "hio" reference from Makefile

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Added Linux kernel remote branch for Kinetic raspi to test with 22.04
  install (both master and master-next branches). When running "make
  clean" noticed error referencing "hio" driver that's been removed from
  Jammy kernels:

  $ make clean
  scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
  make[2]: *** No rule to make target 'ubuntu/hio/Makefile'.  Stop.
  make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
  make: *** [Makefile:1858: _clean_ubuntu] Error 2

  Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:

  commit cf58599cded35cf4affed1e659c0e2c742d3fda7
  Author: Thomas Lamprecht 
  Date:   Sat Mar 12 16:19:10 2022 +0100

  Ubuntu: remove leftover reference to ubuntu/hio driver

  A single reference to the hio driver was forgotten when it was removed
  recently. While this reference is not a problem for the build itself, it
  breaks the __clean target from 'scripts/Makefile.clean' here, as make
  cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.

  Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
  Signed-off-by: Thomas Lamprecht 
  Acked-by: Tim Gardner 
  Signed-off-by: Paolo Pisati 

  Here's some additional information for code repositories (didn't know
  if this was helpful),

  
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
  remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
  branch.kinetic-master-next.remote=kinetic-raspi
  branch.kinetic-master-next.merge=refs/heads/master-next
  branch.kinetic-master.remote=kinetic-raspi
  branch.kinetic-master.merge=refs/heads/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1999556/+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 1999554] Re: LTP uevent01 will fail on GCP n2d-standard-64

2022-12-13 Thread Thadeu Lima de Souza Cascardo

On focal, this reproduces with 5.4 and 5.15 kernels.

One of the causes for the delay is that udev is reading efivars for
secure boot, which takes 0.3 seconds. And it does it multiple times.

When running a 5.19 kernel on focal, however, the test seems to be able
to detach the device before udev starts reading the efivars. Same udev
version here. Perhaps events are pushed in a different order?

Cascardo.

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

Title:
  LTP uevent01 will fail on GCP n2d-standard-64

Status in linux package in Ubuntu:
  New

Bug description:
  Because udev takes too long to release the loop device, LTP test
  uevent01 (and some other tests) may warn about not being able to
  detach the loop device. This is identified as a failure.

  
  ubuntu@selfprovisioned-cascardo-n2d:~$ sudo ./uevent01 
  tst_test.c:1423: TINFO: Timeout per run is 0h 05m 00s
  tst_device.c:88: TINFO: Found free device 6 '/dev/loop6'
  uevent01.c:24: TINFO: Attaching device /dev/loop6
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: DISK_MEDIA_CHANGE=1
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2959
  uevent.h:140: TPASS: Got expected UEVENT
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2960
  uevent.h:140: TPASS: Got expected UEVENT
  uevent01.c:26: TINFO: Detaching device /dev/loop6
  tst_device.c:254: TWARN: ioctl(/dev/loop6, LOOP_CLR_FD, 0) no ENXIO for too 
long

  Summary:
  passed   2
  failed   0
  broken   0
  skipped  0
  warnings 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999554/+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 1999554] [NEW] LTP uevent01 will fail on GCP n2d-standard-64

2022-12-13 Thread Thadeu Lima de Souza Cascardo

Public bug reported:

Because udev takes too long to release the loop device, LTP test
uevent01 (and some other tests) may warn about not being able to detach
the loop device. This is identified as a failure.


ubuntu@selfprovisioned-cascardo-n2d:~$ sudo ./uevent01 
tst_test.c:1423: TINFO: Timeout per run is 0h 05m 00s
tst_device.c:88: TINFO: Found free device 6 '/dev/loop6'
uevent01.c:24: TINFO: Attaching device /dev/loop6
uevent.h:49: TINFO: Got uevent:
uevent.h:52: TINFO: change@/devices/virtual/block/loop6
uevent.h:52: TINFO: ACTION=change
uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
uevent.h:52: TINFO: SUBSYSTEM=block
uevent.h:52: TINFO: DISK_MEDIA_CHANGE=1
uevent.h:52: TINFO: MAJOR=7
uevent.h:52: TINFO: MINOR=6
uevent.h:52: TINFO: DEVNAME=loop6
uevent.h:52: TINFO: DEVTYPE=disk
uevent.h:52: TINFO: DISKSEQ=7
uevent.h:52: TINFO: SEQNUM=2959
uevent.h:140: TPASS: Got expected UEVENT
uevent.h:49: TINFO: Got uevent:
uevent.h:52: TINFO: change@/devices/virtual/block/loop6
uevent.h:52: TINFO: ACTION=change
uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
uevent.h:52: TINFO: SUBSYSTEM=block
uevent.h:52: TINFO: MAJOR=7
uevent.h:52: TINFO: MINOR=6
uevent.h:52: TINFO: DEVNAME=loop6
uevent.h:52: TINFO: DEVTYPE=disk
uevent.h:52: TINFO: DISKSEQ=7
uevent.h:52: TINFO: SEQNUM=2960
uevent.h:140: TPASS: Got expected UEVENT
uevent01.c:26: TINFO: Detaching device /dev/loop6
tst_device.c:254: TWARN: ioctl(/dev/loop6, LOOP_CLR_FD, 0) no ENXIO for too long

Summary:
passed   2
failed   0
broken   0
skipped  0
warnings 1

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

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

Title:
  LTP uevent01 will fail on GCP n2d-standard-64

Status in linux package in Ubuntu:
  New

Bug description:
  Because udev takes too long to release the loop device, LTP test
  uevent01 (and some other tests) may warn about not being able to
  detach the loop device. This is identified as a failure.

  
  ubuntu@selfprovisioned-cascardo-n2d:~$ sudo ./uevent01 
  tst_test.c:1423: TINFO: Timeout per run is 0h 05m 00s
  tst_device.c:88: TINFO: Found free device 6 '/dev/loop6'
  uevent01.c:24: TINFO: Attaching device /dev/loop6
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: DISK_MEDIA_CHANGE=1
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2959
  uevent.h:140: TPASS: Got expected UEVENT
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2960
  uevent.h:140: TPASS: Got expected UEVENT
  uevent01.c:26: TINFO: Detaching device /dev/loop6
  tst_device.c:254: TWARN: ioctl(/dev/loop6, LOOP_CLR_FD, 0) no ENXIO for too 
long

  Summary:
  passed   2
  failed   0
  broken   0
  skipped  0
  warnings 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999554/+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 1999530] Re: Introduce the 525 (ERD) NVIDIA driver series in Bionic, Focal, Jammy, Kinetic

2022-12-13 Thread Alberto Milone

** Also affects: nvidia-graphics-drivers-515-server (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-515-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-515-server (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-515-server (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Kinetic)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Jammy)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Kinetic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Introduce the 525 (ERD) NVIDIA driver series in Bionic, Focal, Jammy,
  Kinetic

Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-515-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515-server/+bug/1999530/+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 1999375] Re: Update dg2_dmc to 2.08

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: New => Fix Committed

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

Title:
  Update dg2_dmc to 2.08

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

Bug description:
  [Impact]

  i915/dg2 needs this new firmware version to fix some undisclosed bugs

  [Test case]

  Boot a system with the new firmware and a kernel that uses it, and
  check that the correct version is loaded.

  [Where things could go wrong]

  If the kernel is updated before the firmware is available, then
  loading i915 fails as it can't find the firmware it requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1999375/+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 1999530] [NEW] Introduce the 525 (ERD) NVIDIA driver series in Bionic, Focal, Jammy, Kinetic

2022-12-13 Thread Alberto Milone

Public bug reported:

[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates

Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.

[Discussion]

[Changelog]

** Affects: nvidia-graphics-drivers-515-server (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

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

Title:
  Introduce the 525 (ERD) NVIDIA driver series in Bionic, Focal, Jammy,
  Kinetic

Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515-server/+bug/1999530/+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

2022-12-13 Thread Stefan Bader

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Kinetic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Kinetic)
   Status: New => In Progress

-- 
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:
  Triaged
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

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 1999528] [NEW] [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later

2022-12-13 Thread Stefan Bader

Public bug reported:

[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).

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Stefan Bader (smb)
 Status: Triaged

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Description changed:

  [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
+   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).

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
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:
  Triaged
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  New

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 1945868] Re: focal kvm virtio_net set_features failed (-22)

2022-12-13 Thread fxpester

just hit it with 5.4.17-2011.6.2.el7uek.x86_64
switching to e1000 as well

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

Title:
  focal kvm virtio_net set_features failed (-22)

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Setup linux-modules-5.4.0-88-generic within focal guest on a (equal)
  ubuntu 20.04 kvm bare metal machine.

  When using virtio as network driver it is failing with:

  net eth0: Fail to set guest offload.
  virtio_net virtio1 eth0: set_features() failed (-22); wanted 
0x008000174a29, left 0x0
  0800017ca29

  followed by further kern log entries:
  [ cut here ]
   netdevice: br0: failed to disable 0x8000 on eth0!
   WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 
__netdev_update_features+0x4d1/0x9f0
   Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops 
input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid 
sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng 
ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover 
failover pata_acpi floppy
   CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic 
#99-Ubuntu
   Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
   RIP: 0010:__netdev_update_features+0x4d1/0x9f0
   Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d 
b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 
8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7
   RSP: 0018:bf1840e0ba98 EFLAGS: 00010282
   RAX:  RBX: 000f RCX: 0006
   RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0
   RBP: bf1840e0bb10 R08: 02d1 R09: 0004
   R10:  R11: 0001 R12: 9c2c0b258000
   R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f
   FS:  7f98be558580() GS:9c2c13a0() knlGS:
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0
   Call Trace:
    netdev_update_features+0x25/0x60
    br_device_event+0x20f/0x300 [bridge]
    notifier_call_chain+0x55/0x80
    raw_notifier_call_chain+0x16/0x20
    call_netdevice_notifiers_info+0x2e/0x60
    netdev_update_features+0x59/0x60
    dev_disable_lro+0x21/0xf0
    br_add_if+0x301/0x650 [bridge]
    add_del_if+0x67/0x80 [bridge]
    br_dev_ioctl+0x54/0x80 [bridge]
    dev_ifsioc+0xe5/0x3e0
    ? _cond_resched+0x19/0x30
    dev_ioctl+0x2dd/0x470
    sock_do_ioctl+0xa8/0x140
    ? evict+0x14c/0x1b0
    sock_ioctl+0x24f/0x3c0
    ? _cond_resched+0x19/0x30
    ? get_max_files+0x20/0x20
    do_vfs_ioctl+0x407/0x670
    ksys_ioctl+0x67/0x90
    __x64_sys_ioctl+0x1a/0x20
    do_syscall_64+0x57/0x190
    entry_SYSCALL_64_after_hwframe+0x44/0xa9
   RIP: 0033:0x7f98be47c50b
   Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 
ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 
01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
   RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010
   RAX: ffda RBX: 0002 RCX: 7f98be47c50b
   RDX: 7ffd78332210 RSI: 89a2 RDI: 0003
   RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74
   R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e
   R13: 7ffd78333e7e R14:  R15: 
   ---[ end trace 240d361752e8f3f0 ]---
   [ cut here ]

  Temporary solution is to return to the old rtl8139 driver and slow
  network down

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+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 1999406] Re: Update firmware for hwe/oem kernel migrations

2022-12-13 Thread You-Sheng Yang

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-December/135657.html 
(focal)
* https://lists.ubuntu.com/archives/kernel-team/2022-December/135658.html 
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2022-December/135659.html 
(lunar)

** Summary changed:

- Update firmware for hwe kernel migration
+ Update firmware for hwe/oem kernel migrations

** Also affects: linux-firmware (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Description changed:

- TBD.
+ [SRU Justification]
+ 
+ [Impact]
+ 
+ When migrating to a new hwe kernel or introduced a oem kernel of a
+ newer version, the firmware blobs might not match the expectation of
+ the new kernel. For example, a hwe-5.15 on Focal may include new
+ drivers that relies on firmware blobs that are only available in Jammy.
+ 
+ [Fix]
+ 
+ A previously obsoleted (and removed in Kinetic and Lunar) script
+ `list-lts-update-files` is used to enumerate firmware blobs to be
+ backported. It's retored and revised with additional support to
+ pick the right blobs especially in regard to ath and iwlwifi drivers.
+ 
+ On Focal, the commits in need are enumerated by:
+ 
+   $ debian/scripts/list-lts-update-files focal jammy \
+ ../jammy/debian.master/abi/fwinfo | \
+ xargs git log --graph --oneline focal..jammy --
+   * 36f2ea9f7 ath11k: WCN6855 hw2.0: add 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3
+   * 05b5dc001 ath11k: WCN6855 hw2.0: add board-2.bin and regdb.bin
+   * 7a3005059 brcm: Add 43455 based AP6255 NVRAM for the ACEPC T8 Mini PC
+   * ad185afa1 cypress: update firmware for cyw4373 sdio
+   * 77d3eb8ef cypress: update firmware for cyw43570 pcie
+   * 92e9acdbd cypress: update firmware for cyw4356 sdio
+   * 5f88084be cypress: update firmware for cyw4354 sdio
+   * f97e31677 cypress: update firmware for cyw43455 sdio
+   * 3df9ea0b9 cypress: update firmware for cyw43430 sdio
+   * 6150015cf cypress: update firmware for cyw43012 sdio
+   * 2548d065b brcm: Add nvram for the Chuwi Hi8 (CWI509) tablet
+   * e45c137e7 brcm: Add nvram for the Predia Basic tablet
+   * d52886242 brcm: Add NVRAM for Vamrs 96boards Rock960
+   *   b503c9660 Merge branch 'ath10k-20201023' of 
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main
+   |\
+   | * 34cb5fce2 ath11k: IPQ8074 hw2.0: add to 
WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2
+   | * c0a8efd24 ath11k: IPQ8074 hw2.0: add board-2.bin
+   | * ac7f5e93f ath11k: IPQ6018 hw1.0: add to 
WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2
+   | * 2594e510a ath11k: IPQ6018 hw1.0: add board-2.bin
+   * 04f71fe56 cypress: add Cypress firmware and clm_blob files
+ 
+ Commit 05b5dc001 and 36f2ea9f7 include updates to other existing files,
+ so they are dropped from this SRU. An additional commit that modifies
+ only WHENCE, commit 0b558e8a7, found when resolving conflicts, were also
+ added.
+ 
+ On Jammy,
+ 
+   $ debian/scripts/list-lts-update-files jammy kinetic \
+ ../kinetic/debian.master/abi/fwinfo | \
+ xargs git log --graph --oneline jammy..kinetic --
+   * 35f8de521 UBUNTU: Add pre-compiled echoaudio firmware
+   * c954892f6 Add initial AzureWave AW-CM256SM NVRAM file
+   * 86f0c5642 ath10k: WCN3990 hw1.0: add board-2.bin
+   *   c3624ebd6 Merge branch 'ath10k-20220423' of 
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main
+   |\
+   | * 1962cbab3 ath10k: QCA99X0 hw2.0: add board-2.bin
+   | * 0d5e9f7e0 ath11k: WCN6750 hw1.0: add to 
WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1
+   | * a50132f7f ath11k: WCN6750 hw1.0: add board-2.bin
+   | * 97f8b7563 ath11k: QCN9074 hw1.0: add to 
WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1
+   | * f56505fe2 ath11k: QCN9074 hw1.0: add board-2.bin
+   * | dfa3c4c30 qcom: add firmware files for Adreno a420 & related generations
+   * | 4a43f1a84 qcom: add firmware files for Adreno a330
+   * | ac21ab5d1 Mellanox: Add lc_ini_bundle for xx.2010.1006
+   |/
+   * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it
+ 
+ Commit 4ffcf980a involves rename existing files in WHENCE, so ignored.
+ 
+ While Jammy has 3 additional oem kernels, they were also tested:
+ 
+   $ debian/scripts/list-lts-update-files jammy kinetic \
+ ../oem-5.17/debian.oem/abi/fwinfo | \
+ xargs git log --graph --oneline jammy..kinetic --
+   (no new commits)
+ 
+   $ debian/scripts/list-lts-update-files jammy lunar \
+ ../oem-6.0/debian.oem/abi/fwinfo | \
+ xargs git log --graph --oneline jammy..lunar --
+   * 06dbfbc74 iwlwifi: add new FWs from core69-81 release
+ 
+   $ debian/scripts/list-lts-update-files jammy lunar \
+ ../oem-6.1/debian.oem/abi/fwinfo | \
+ xargs git log --graph --oneline jammy..lunar --
+   * 51fff4e69 i915: Add versionless HuC files for current

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

2022-12-13 Thread mario buoninfante

Hi,

I got the same as described by Ángel Luis Fernández Presa (alf-tk85) 2 posts 
above.
One thing I noticed though, is that my GPU seems to affect the results.
When using a kernel exhibiting the issue, I tried installing the proprietary 
AMD drivers for my AMD FirePro W2100.
That made the video really sluggish, but solved my audio issues.
Unfortunately video performance was so bad that I had to get rid of the driver.

Hope this is somehow useful.

I'm now using 5.13.0-35-lowlatency and the crackling noise is gone, but I'm 
getting more xruns than on another machine way less powerful than the one in 
question.
I tried with a Focusrite Scarlett 2i2 3rd Gen and a Focusrite Clarett 8pre USB 
C, same results.

BTW I tried the daemon.conf workaround, but that didn't work.

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
  next packet size") landed in 5.13.0-35 introduced regression to USB
  audio device.

  It's because this patch introduced the available frame size check, but
  the conversion forgot to initialize the temporary variable properly.

  A workaround is to modify /etc/pulse/daemon.conf, set the
  default-sample-rate to 48000, uncomment it by removing the semicolon
  at the beginning of the line. And restart pulseaudio with: 
systemctl --user restart pulseaudio.service

  [Fix]
  * 23939115 ALSA: usb-audio: Fix packet size calculation regression
  This patch can be cherry-picked into Impish kernel, and it's already in
  the master-next branch of Jammy tree.

  [Test]
  Test kernels built with 5.13.0-37 + this patch, can be found in:
  * Focal-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
  * Impish-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/

  Both kernels were tested by affected users and they're working as
  expected.

  [Where problems could occur]
  If this patch is incorrect, it might affect USB audio devices.

  
  [Original Bug Report]
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

2022-12-13 Thread Sebastien Bacher

The 1.20 components have been uploaded to the 22.04 SRU queue now.

@oem it would be nice if you could improve the bug description to have a
more detailed testcase and regression potential section

** Description changed:

  * Impact
  
  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.
  
  * Test case
  
- Try connecting to 5G using a FM350 modem
+ - install modemmanager, libmbim, and libqmi from -proposed
+ - reboot and try WWAN function to see if any regression there.
+ - perform dogfooding of its reverse dependencies (network-
+    manager, gnome-control-center etc.)
+ 
+ The verification should be done on FM350 to ensure it's correctly
+ handled but also on other hardware to verify that there are no
+ regressions
  
  * Regression potential
  
  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are no
  regression.
  
- 
  ---
- 
  
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]
  
  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  
  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525
  
  ---
  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-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

** Changed in: modemmanager (Ubuntu)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu)
   Status: Confirmed => 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/1950282

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no

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

Hello AaronMa, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.9 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Mediatek WLAN RZ616(MT7922) SAR table control

Status in HWE Next:
  In Progress
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 Committed
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
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

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

Hello AaronMa, or anyone else affected,

Accepted linux-firmware into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220923.gitf09bebf3-0ubuntu1.3 in a few hours, and then in the
-proposed repository.

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

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

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

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

-- 
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:
  In Progress
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 Committed
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
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):

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

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.9 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  New DMCUB FW for AMD amdgpu DCN 3.1.6

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Multiple issues in DP alt mode, PSR-SU(Panel Self Refresh–Selective
  Update), and HDMI signal integrity.

  [Fix]

  Upstream commit b0f995cd61cd ("amdgpu: update DMCUB firmware for DCN
  3.1.6") that updates binary firmware.

  [Test Case]

  Can only be verified with dedicated equipment from vendor.

  [Where problems could occur]

  Binary firmware, everything can go wrong.

  [Other Info]

  Already in korg upstream, included in Lunar, too. Only Jammy and
  Kinetic will be nominated for fix.

  == original bug report ==

  Some fixes for DP alt mode and PSR-SU(Panel Self Refresh–Selective
  Update), and also improve HDMI signal integrity. This FW would be
  tuning PHY of HDMI to enhance signal integrity in eye diagram to reach
  HDMI spec(2.0/1.4b), and also avoid any risk on monitor with multiple
  resolutions over HDMI output.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=b0f995cd61cd29e7eee1dc22aeeacb2eadc21227

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998468/+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 1998468] Please test proposed package

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220923.gitf09bebf3-0ubuntu1.3 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  New DMCUB FW for AMD amdgpu DCN 3.1.6

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Multiple issues in DP alt mode, PSR-SU(Panel Self Refresh–Selective
  Update), and HDMI signal integrity.

  [Fix]

  Upstream commit b0f995cd61cd ("amdgpu: update DMCUB firmware for DCN
  3.1.6") that updates binary firmware.

  [Test Case]

  Can only be verified with dedicated equipment from vendor.

  [Where problems could occur]

  Binary firmware, everything can go wrong.

  [Other Info]

  Already in korg upstream, included in Lunar, too. Only Jammy and
  Kinetic will be nominated for fix.

  == original bug report ==

  Some fixes for DP alt mode and PSR-SU(Panel Self Refresh–Selective
  Update), and also improve HDMI signal integrity. This FW would be
  tuning PHY of HDMI to enhance signal integrity in eye diagram to reach
  HDMI spec(2.0/1.4b), and also avoid any risk on monitor with multiple
  resolutions over HDMI output.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=b0f995cd61cd29e7eee1dc22aeeacb2eadc21227

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998468/+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 1999491] Please test proposed package

Hello koba, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.9 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Fix The Bluetooth connection cannot be established between two Ubuntu
  22.04 systems with Realtek 8821

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821.

  [Fix]
  Use the updated firmware for rtl8821c to fix issue.

  [Test]
  1. Prepare two Ubuntu 22.04 systems with Realtek 8821.
  2. Open Bluetooth Settings and launch research available device automatically.
  3. Found this two systems are visible in research list for connection, 
Bluetooth connection can be established normally without problem.

  [Where problems could occur]
  It's binary so anything would happen.

  [Other Info]
  This firmware has existed in Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999491/+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 1999491] Please test proposed package

Hello koba, or anyone else affected,

Accepted linux-firmware into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220923.gitf09bebf3-0ubuntu1.3 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Fix The Bluetooth connection cannot be established between two Ubuntu
  22.04 systems with Realtek 8821

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821.

  [Fix]
  Use the updated firmware for rtl8821c to fix issue.

  [Test]
  1. Prepare two Ubuntu 22.04 systems with Realtek 8821.
  2. Open Bluetooth Settings and launch research available device automatically.
  3. Found this two systems are visible in research list for connection, 
Bluetooth connection can be established normally without problem.

  [Where problems could occur]
  It's binary so anything would happen.

  [Other Info]
  This firmware has existed in Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999491/+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 1999501] Re: Login Loop

2022-12-13 Thread António Oliveira

I was not able to get any logs from the virtual machine itself as there
was no way to authenticate into the system. Furthermore, I have move on
and started using another distro.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1999501

Title:
  Login Loop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of Ubuntu 22.04 LTS, installing the ISO file on a virtual machine
  using VirtualBox 7.0.4 r154605 on Windows 10 version 21H2, the
  operating system gets stuck on the login page, even after inputing the
  correct  password.

  Some specs of the machine in question:

  --
  System Information
  --
   Machine name: ---
 Machine Id: ---
   Operating System: Windows 10 Home 64-bit (10.0, Build 19044) 
(19041.vb_release.191206-1406)
   Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
   System Model: ROG Zephyrus G15 GA503QR_GA503QR
   BIOS: GA503QR.413 (type: UEFI)
  Processor: AMD Ryzen 9 5900HS with Radeon Graphics 
(16 CPUs), ~3.3GHz
 Memory: 16384MB RAM
Available OS Memory: 15776MB RAM
  Page File: 12722MB used, 7405MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
   User DPI Setting: 96 DPI (100 percent)
 System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
   Miracast: Available, with HDCP
  Microsoft Graphics Hybrid: Supported

  ---
  Display Devices
  ---
 Card name: AMD Radeon(TM) Graphics
  Manufacturer: Advanced Micro Devices, Inc.
 Chip type: AMD Radeon Graphics Processor (0x1638)
Display Memory: 8384 MB
  Dedicated Memory: 496 MB
 Shared Memory: 7888 MB
  Current Mode: 2560 x 1440 (32 bit) (165Hz)

 Card name: NVIDIA GeForce RTX 3070 Laptop GPU
  Manufacturer: NVIDIA
 Chip type: NVIDIA GeForce RTX 3070 Laptop GPU
Display Memory: 15921 MB
  Dedicated Memory: 8033 MB
 Shared Memory: 7888 MB

  The problem seems to be with the usage of both integrated GPU and
  dedicated GPU, as the problem persists when the integrated GPU is the
  one in usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999501/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

2022-12-13 Thread Sebastien Bacher

** Description changed:

+ * Impact
+ 
+ Fibocom FM350 modems aren't working with the current version of
+ modemmanager in 22.04.
+ 
+ * Test case
+ 
+ Try connecting to 5G using a FM350 modem
+ 
+ * Regression potential
+ 
+ The SRU does an update to new modemmanager serie so we should do a
+ complete round of testing on different hardware and confirm there are no
+ regression.
+ 
+ 
+ ---
+ 
+ 
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]
  
  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  
  Modemmanager requires >= 1.19.1, the detail info is in
- lp:1962525 
+ lp:1962525
  
  ---
  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-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  Try connecting to 5G using a FM350 modem

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  
  ---

  
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  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-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58

[Kernel-packages] [Bug 1999501] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1999501

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Login Loop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As of Ubuntu 22.04 LTS, installing the ISO file on a virtual machine
  using VirtualBox 7.0.4 r154605 on Windows 10 version 21H2, the
  operating system gets stuck on the login page, even after inputing the
  correct  password.

  Some specs of the machine in question:

  --
  System Information
  --
   Machine name: ---
 Machine Id: ---
   Operating System: Windows 10 Home 64-bit (10.0, Build 19044) 
(19041.vb_release.191206-1406)
   Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
   System Model: ROG Zephyrus G15 GA503QR_GA503QR
   BIOS: GA503QR.413 (type: UEFI)
  Processor: AMD Ryzen 9 5900HS with Radeon Graphics 
(16 CPUs), ~3.3GHz
 Memory: 16384MB RAM
Available OS Memory: 15776MB RAM
  Page File: 12722MB used, 7405MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
   User DPI Setting: 96 DPI (100 percent)
 System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
   Miracast: Available, with HDCP
  Microsoft Graphics Hybrid: Supported

  ---
  Display Devices
  ---
 Card name: AMD Radeon(TM) Graphics
  Manufacturer: Advanced Micro Devices, Inc.
 Chip type: AMD Radeon Graphics Processor (0x1638)
Display Memory: 8384 MB
  Dedicated Memory: 496 MB
 Shared Memory: 7888 MB
  Current Mode: 2560 x 1440 (32 bit) (165Hz)

 Card name: NVIDIA GeForce RTX 3070 Laptop GPU
  Manufacturer: NVIDIA
 Chip type: NVIDIA GeForce RTX 3070 Laptop GPU
Display Memory: 15921 MB
  Dedicated Memory: 8033 MB
 Shared Memory: 7888 MB

  The problem seems to be with the usage of both integrated GPU and
  dedicated GPU, as the problem persists when the integrated GPU is the
  one in usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999501/+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 1999491] Re: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821

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

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

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

Title:
  Fix The Bluetooth connection cannot be established between two Ubuntu
  22.04 systems with Realtek 8821

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821.

  [Fix]
  Use the updated firmware for rtl8821c to fix issue.

  [Test]
  1. Prepare two Ubuntu 22.04 systems with Realtek 8821.
  2. Open Bluetooth Settings and launch research available device automatically.
  3. Found this two systems are visible in research list for connection, 
Bluetooth connection can be established normally without problem.

  [Where problems could occur]
  It's binary so anything would happen.

  [Other Info]
  This firmware has existed in Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999491/+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 1999501] [NEW] Login Loop

2022-12-13 Thread António Oliveira

Public bug reported:

As of Ubuntu 22.04 LTS, installing the ISO file on a virtual machine
using VirtualBox 7.0.4 r154605 on Windows 10 version 21H2, the operating
system gets stuck on the login page, even after inputing the correct
password.

Some specs of the machine in question:

--
System Information
--
 Machine name: ---
   Machine Id: ---
 Operating System: Windows 10 Home 64-bit (10.0, Build 19044) 
(19041.vb_release.191206-1406)
 Language: English (Regional Setting: English)
  System Manufacturer: ASUSTeK COMPUTER INC.
 System Model: ROG Zephyrus G15 GA503QR_GA503QR
 BIOS: GA503QR.413 (type: UEFI)
Processor: AMD Ryzen 9 5900HS with Radeon Graphics (16 
CPUs), ~3.3GHz
   Memory: 16384MB RAM
  Available OS Memory: 15776MB RAM
Page File: 12722MB used, 7405MB available
  Windows Dir: C:\Windows
  DirectX Version: DirectX 12
  DX Setup Parameters: Not found
 User DPI Setting: 96 DPI (100 percent)
   System DPI Setting: 96 DPI (100 percent)
  DWM DPI Scaling: Disabled
 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported

---
Display Devices
---
   Card name: AMD Radeon(TM) Graphics
Manufacturer: Advanced Micro Devices, Inc.
   Chip type: AMD Radeon Graphics Processor (0x1638)
  Display Memory: 8384 MB
Dedicated Memory: 496 MB
   Shared Memory: 7888 MB
Current Mode: 2560 x 1440 (32 bit) (165Hz)

   Card name: NVIDIA GeForce RTX 3070 Laptop GPU
Manufacturer: NVIDIA
   Chip type: NVIDIA GeForce RTX 3070 Laptop GPU
  Display Memory: 15921 MB
Dedicated Memory: 8033 MB
   Shared Memory: 7888 MB

The problem seems to be with the usage of both integrated GPU and
dedicated GPU, as the problem persists when the integrated GPU is the
one in usage.

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


** Tags: 22.04 amd nvidia

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

Title:
  Login Loop

Status in linux package in Ubuntu:
  New

Bug description:
  As of Ubuntu 22.04 LTS, installing the ISO file on a virtual machine
  using VirtualBox 7.0.4 r154605 on Windows 10 version 21H2, the
  operating system gets stuck on the login page, even after inputing the
  correct  password.

  Some specs of the machine in question:

  --
  System Information
  --
   Machine name: ---
 Machine Id: ---
   Operating System: Windows 10 Home 64-bit (10.0, Build 19044) 
(19041.vb_release.191206-1406)
   Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
   System Model: ROG Zephyrus G15 GA503QR_GA503QR
   BIOS: GA503QR.413 (type: UEFI)
  Processor: AMD Ryzen 9 5900HS with Radeon Graphics 
(16 CPUs), ~3.3GHz
 Memory: 16384MB RAM
Available OS Memory: 15776MB RAM
  Page File: 12722MB used, 7405MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
   User DPI Setting: 96 DPI (100 percent)
 System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
   Miracast: Available, with HDCP
  Microsoft Graphics Hybrid: Supported

  ---
  Display Devices
  ---
 Card name: AMD Radeon(TM) Graphics
  Manufacturer: Advanced Micro Devices, Inc.
 Chip type: AMD Radeon Graphics Processor (0x1638)
Display Memory: 8384 MB
  Dedicated Memory: 496 MB
 Shared Memory: 7888 MB
  Current Mode: 2560 x 1440 (32 bit) (165Hz)

 Card name: NVIDIA GeForce RTX 3070 Laptop GPU
  Manufacturer: NVIDIA
 Chip type: NVIDIA GeForce RTX 3070 Laptop GPU
Display Memory: 15921 MB
  Dedicated Memory: 8033 MB
 Shared Memory: 7888 MB

  The problem seems to be with the usage of both integrated GPU and
  dedicated GPU, as the problem persists when the integrated GPU is the
  one in usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999501/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-12-13 Thread ybdjkfd

juliank, edited and removed more notes as you advised. I hope my edits
per your advice help clarify things and help anyone to see if a new bug
is necessary to report. Thanks for your input.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:

[Kernel-packages] [Bug 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

2022-12-13 Thread Petter Sundlöf

I installed backport-iwlwifi-dkms and BT now works...

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [DEL] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37

[Kernel-packages] [Bug 1992723] Re: Enable DP tunneling functionality on AMD Pink Sardine

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

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

Title:
  Enable DP tunneling functionality on AMD Pink Sardine

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:
  Invalid
Status in linux-oem-6.0 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

Bug description:
  [SRU Justification]

  [Impact]

  DP tunneling on a certain thunderbolt docking doesn't work well.

  [Fix]

  Add a new IP version in the switch cases that supports DPIA.

  [Test Case]

  Connect an external monitor via thunderbolt docking station.

  [Where problems could occur]

  DPIA is supported on AMD DCN314 gpu platforms. With or without it may
  both introduce compatibility issues as what to be solve here.

  [Other Info]

  While this applies to AMD Phoenix/Phoenix2 platforms, only oem-6.0 or
  above are nominated for fix.

  == original bug description ==

  Observed unsuccessfully light-up on some TBT docking with the single
  monitor connected, adding a new IP version to enable DPIA
  functionality.

  
https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992723/+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 1995041] Re: Fix ath11k deadlock on WCN6855

this is in 6.0-1008

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

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

Title:
  Fix ath11k deadlock on WCN6855

Status in HWE Next:
  In Progress
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 Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1995957] Re: Add cs35l41 firmware loading support

this was supposed to be in 6.0-1008 but isn't, so it won't be there
before next year

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

Title:
  Add cs35l41 firmware loading support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
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:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware 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

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995957/+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 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

2022-12-13 Thread Petter Sundlöf

Bluetooth works fine on tested devices with daily jammy build downloaded
12/12.

Is there a way to use a port of that firmware on 22.10?

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [DEL] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37

[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

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

-- 
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:
  In Progress
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:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
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:
  In Progress
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 has been accepted but still not shown in the upstream tree,
  so submit this patch to oem kernels first, and will submit it to other
  generic ubuntu kernels.

  [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 1996198] Re: Fix rfkill causing soft blocked wifi

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

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1862760] Re: Unreliable 802.11ac connection on our raspi images

There were some missing fw blobs added a while ago and I think the
problem is solved now. Can this ticket be closed?

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  Won't Fix
Status in netplan.io source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2-5.3 source package in Eoan:
  Won't Fix
Status in netplan.io source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi source package in Focal:
  New
Status in netplan.io source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+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 1992409] Re: USB disk not detected at boot since 5.15.0-1015-raspi

Sorry, this doesn't make sense then and I can't make any progress
without being able to reproduce the problem locally. Since you have a
work-around I'll close the ticket. Please open a new one should you run
into this again.

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

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

Title:
  USB disk not detected at boot since 5.15.0-1015-raspi

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  The RPI4 setup is composed by two USB disks running on Ubuntu desktop 22.04:
  - USB SSD containing the OS (ASM1153)
  - USB disk for the data, on its own power supply (ASM1051E)

  This setup worked fine the last months but since 5.15.0-1015-raspi the
  USB disk (data) is not recognized at boot (cool start or reboot). The
  same is valid with 5.15.0-1016-raspi. The disk is powered (power led)
  but not spinning so I simply need to disconnect/connect the USB cable
  or reset the power (of the disk) to make it works. Once the disk is
  recognized it runs w/o problem for days and even weeks (24/7 running
  setup). The USB SSD with the OS is always fine, no miss in boot.

  PS: I want to keep it in UASP mode

  Some details:
  lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 003: ID 174c:1153 ASMedia Technology Inc. ASM1153 SATA 3Gb/s 
bridge
  Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s 
bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 
6Gb/s bridge
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  
--
  sudo dmesg|grep scsi
  [2.343664] scsi host0: uas
  [2.344714] scsi 0:0:0:0: Direct-Access Inateck  ASM1153E 0
PQ: 0 ANSI: 6
  [2.346284] sd 0:0:0:0: Attached scsi generic sg0 type 0
  [2.354045] scsi host1: uas
  [2.355083] scsi 1:0:0:0: Direct-Access WDC WD60 EFRX-68MYMN1 0
PQ: 0 ANSI: 6
  [2.356890] sd 1:0:0:0: Attached scsi generic sg1 type 0
  
--
  sudo dmesg|grep usb
  [0.159937] usbcore: registered new interface driver usbfs
  [0.159986] usbcore: registered new interface driver hub
  [0.160042] usbcore: registered new device driver usb
  [0.729235] usbcore: registered new interface driver lan78xx
  [0.729288] usbcore: registered new interface driver smsc95xx
  [1.442961] usb_phy_generic phy: supply vcc not found, using dummy 
regulator
  [1.443112] usb_phy_generic phy: dummy supplies not allowed for exclusive 
requests
  [1.509268] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.15
  [1.509285] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [1.509291] usb usb1: Product: xHCI Host Controller
  [1.509296] usb usb1: Manufacturer: Linux 5.15.0-1016-raspi xhci-hcd
  [1.509301] usb usb1: SerialNumber: :01:00.0
  [1.511924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, 
bcdDevice= 5.15
  [1.511941] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [1.511946] usb usb2: Product: xHCI Host Controller
  [1.511952] usb usb2: Manufacturer: Linux 5.15.0-1016-raspi xhci-hcd
  [1.511956] usb usb2: SerialNumber: :01:00.0
  [1.573196] dwc2 fe98.usb: supply vusb_d not found, using dummy 
regulator
  [1.573513] dwc2 fe98.usb: supply vusb_a not found, using dummy 
regulator
  [1.783600] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in 
SPRAM
  [1.783872] dwc2 fe98.usb: DWC OTG Controller
  [1.783892] dwc2 fe98.usb: new USB bus registered, assigned bus number 
3
  [1.783918] dwc2 fe98.usb: irq 20, io mem 0xfe98
  [1.784066] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.15
  [1.784075] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [1.784080] usb usb3: Product: DWC OTG Controller
  [1.784086] usb usb3: Manufacturer: Linux 5.15.0-1016-raspi dwc2_hsotg
  [1.784091] usb usb3: SerialNumber: fe98.usb
  [1.847534] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [1.998154] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, 
bcdDevice= 4.21
  [1.998178] usb 1-1: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [1.998191] usb 1-1: Product: USB2.0 Hub
  [2.123982] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [2.145228] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa, 
bcdDevice= 1.00

[Kernel-packages] [Bug 1999491] Re: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821