[Kernel-packages] [Bug 2051733] Re: Specifying nohz_full disables CPU frequency scaling

[Andrea Righi]

@dsmythies IIUC this happens also with a mainline kernel, right? Not
just the Ubuntu lowlatency one.

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

Title:
  Specifying nohz_full disables CPU frequency scaling

Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  With the lowlatency kernel, if I specify "nohz_full=1-15" boot
  parameter then CPU frequency scaling doesn't work for the logical
  cores 1-15. That is, only logical core 0 shows varying CPU frequency
  in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all
  other cores constantly show 80 in their scaling_cur_freq files
  (which is the lowest supported frequency) regardless of the CPU load.

  Steps to reproduce:

  1. Add "nohz_full=1-15" (specify the core numbers to include all logical 
cores except 0) to kernel boot options in /etc/default/grub.
  2. Run `sudo update-grub` and reboot.
  3. Upon booting, run a multithreaded workload. For example, run `openssl 
speed -multi $(nproc --all)`.
  4. In another console, monitor CPU frequencies by running `watch cat 
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

  Actual results:

  All cores specified in "nohz_full" parameter are always at their
  lowest frequency.

  Expected results:

  All cores must scale the frequency up with active load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
  Uname: Linux 6.5.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Jan 30 23:39:51 2024
  InstallationDate: Installed on 2015-05-01 (3196 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: linux-signed-lowlatency-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.5/+bug/2051733/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U

[You-Sheng Yang]

While the proposed firmware fix is already in upstream repository, it
shall be included when linux-firmware/noble is rebased to the latest
HEAD.

** Changed in: linux-firmware (Ubuntu Jammy)
   Importance: Undecided => High

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

** Changed in: linux-firmware (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Noble)
   Status: New => Triaged

** Changed in: linux-firmware (Ubuntu Noble)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  DP connection swap to break eDP behavior on AMD 7735U

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Won't Fix
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  Triaged
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Some OEM platforms swap DP connections on the Rembrandt-R, which causes 
improper eDP behavior.  The following issues will occur in these designs:

  - Fn key failed to control brightness
  - eDP remains black screen during S0i3 cycle

  AMD has fixed these issues, but it requires both a kernel patch and an
  updated DMCUB microcode.

  [Test Plan]
  Validate brightness control works.
  Validate that PSR works.
  Validate that eDP works after suspend/resume.
  Validate that external display works.

  Run above test plan on Rembrandt or Rembrandt-R system with swapped DP
  as well as one without swapped DP.

  [Where problems can occur]
  The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R 
systems.  Issues would occur specifically on these designs, which is why they 
should be tested.

  [Other Info]

  Patch:
  
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749

  DMCUB FW:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

I'm not sure we even need Plymouth installed in initrd because the
device_timeout experiment mentioned in comment #18 suggests plymouthd
was starting early enough already. It's not the root filesystem that
takes too long to appear, but the i915/amdgpu drivers to fully
initialize. Also all this talk of SimpleDRM and initrd really belongs
more in bug 1965303 and bug 1869655.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051418] Re: installed linux-image-6.5.0-15-generic package post-installation script subprocess returned error exit status 1

[atactic]

** Summary changed:

- Error in removing linux-image-6.5.0-14-generic
+ installed linux-image-6.5.0-15-generic package post-installation script 
subprocess returned error exit status 1

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

Title:
  installed linux-image-6.5.0-15-generic package post-installation
  script subprocess returned error exit status 1

Status in linux-meta-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Here is the error when trying to upgrade Ubuntu:

  $ sudo apt-get autoremove
  [sudo] password for XXX:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    linux-image-6.5.0-14-generic
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  2 not fully installed or removed.
  After this operation, 14.3 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 248924 files and directories currently installed.)
  Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ...
  /etc/kernel/postrm.d/initramfs-tools:
  update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic
  /etc/kernel/postrm.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not 
found
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: error processing package linux-image-6.5.0-14-generic (--remove):
   installed linux-image-6.5.0-14-generic package post-removal script 
subprocess returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   linux-image-6.5.0-14-generic
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb
 ./casper/minimal.standard.live.squashfs
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 10:39:26 2024
  InstallationDate: Installed on 2023-10-29 (90 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+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 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading

[Juerg Haefliger]

** Tags added: kern-9038

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

Title:
  AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
  loading

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-firmware source package in Noble:
  Triaged

Bug description:
  [SRU Justification]

  [Impact]

  With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
  within a few minutes or sometimes even quicker

  [Fix]

  Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and 
other prerequisites:
  * amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1 
firmware")
  * amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4 
firmware")
  * amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2 
firmware")
  * amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4 
firmware")
  * amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11 
firmware")

  [Test Case]

  Run stress tool like 3DMark or GravityMark.

  [Where problems could occur]

  Binary firmware update recommended by chip vendor. No known issue so
  far.

  [Other Info]

  Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy
  is also nominated for fix.

  == original bug report ==

  With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
  within a few minutes or sometimes even quicker. Also using mantic +
  v6.7 hit the hang, so need to update new FWs to fix this issue.

  PHX series
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85

  [ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 
timeout, signaled seq=27035, emitted seq=27037
  [ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: 
process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421
  [ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin!
  [ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.464226] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.464398] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.594247] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.594418] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.724265] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.724432] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.854275] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.854437] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.984284] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
[amdgpu]] *ERROR* MES failed to response msg=3
  [ 416.984456] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
unmap legacy queue
  [ 416.996743] amdgpu :0d:00.0: amdgpu: MODE2 reset
  [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to 
resume
  [ 417.026909] [drm] PCIE GART of 512M enabled (table 

[Kernel-packages] [Bug 2051763] [NEW] RTL8821CE did not work

[Tigran]

Public bug reported:

Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network
Adapter did not work on 6.5 kernels

** 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/2051763

Title:
  RTL8821CE did not work

Status in linux package in Ubuntu:
  New

Bug description:
  Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless
  Network Adapter did not work on 6.5 kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051763/+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 2051418] Re: Error in removing linux-image-6.5.0-14-generic

[atactic]

$ sudo dpkg --configure -a
[sudo] password for XXX: 
Setting up linux-image-6.5.0-15-generic (6.5.0-15.15) ...
Processing triggers for linux-image-6.5.0-15-generic (6.5.0-15.15) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.5.0-15-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
/usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not 
found
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
dpkg: error processing package linux-image-6.5.0-15-generic (--configure):
 installed linux-image-6.5.0-15-generic package post-installation script 
subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-6.5.0-15-generic


** Description changed:

  Here is the error when trying to upgrade Ubuntu:
  
  $ sudo apt-get autoremove
- [sudo] password for minisforum-um790pro-nicolas: 
+ [sudo] password for XXX:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
-   linux-image-6.5.0-14-generic
+   linux-image-6.5.0-14-generic
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  2 not fully installed or removed.
  After this operation, 14.3 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 248924 files and directories currently installed.)
  Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ...
  /etc/kernel/postrm.d/initramfs-tools:
  update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic
  /etc/kernel/postrm.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not 
found
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: error processing package linux-image-6.5.0-14-generic (--remove):
-  installed linux-image-6.5.0-14-generic package post-removal script 
subprocess returned error exit status 1
+  installed linux-image-6.5.0-14-generic package post-removal script 
subprocess returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
-  linux-image-6.5.0-14-generic
+  linux-image-6.5.0-14-generic
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb
 ./casper/minimal.standard.live.squashfs
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 10:39:26 2024
  InstallationDate: Installed on 2023-10-29 (90 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Error in removing linux-image-6.5.0-14-generic

Status in linux-meta-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Here is the error when trying to upgrade Ubuntu:

  $ sudo apt-get autoremove
  [sudo] password for XXX:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    linux-image-6.5.0-14-generic
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  2 not fully installed or removed.
  After this operation, 14.3 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 248924 files and directories currently installed.)
  Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ...
  /etc/kernel/postrm.d/initramfs-tools:
  update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic
  /etc/kernel/postrm.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not 
found
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: error processing package linux-image-6.5.0-14-generic (--remove):
   installed linux-image-6.5.0-14-generic package post-removal script 
subprocess returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   linux-image-6.5.0-14-generic
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
 

[Kernel-packages] [Bug 2051418] Re: Error in removing linux-image-6.5.0-14-generic

[atactic]

Bug titel changed as per error message suggestion.

Could not install 'linux-image-6.5.0-15-generic'

The upgrade will continue but the 'linux-image-6.5.0-15-generic' package
may not be in a working state. Please consider submitting a bug report
about it.

installed linux-image-6.5.0-15-generic package post-installation script
subprocess returned error exit status 1


Could not install the upgrades

The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

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

Title:
  Error in removing linux-image-6.5.0-14-generic

Status in linux-meta-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Here is the error when trying to upgrade Ubuntu:

  $ sudo apt-get autoremove
  [sudo] password for XXX:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    linux-image-6.5.0-14-generic
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  2 not fully installed or removed.
  After this operation, 14.3 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 248924 files and directories currently installed.)
  Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ...
  /etc/kernel/postrm.d/initramfs-tools:
  update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic
  /etc/kernel/postrm.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not 
found
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: error processing package linux-image-6.5.0-14-generic (--remove):
   installed linux-image-6.5.0-14-generic package post-removal script 
subprocess returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   linux-image-6.5.0-14-generic
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb
 ./casper/minimal.standard.live.squashfs
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 10:39:26 2024
  InstallationDate: Installed on 2023-10-29 (90 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+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 2006557] Re: Enable rdma-sniffer for libpcap

[Athos Ribeiro]

** Tags added: server-triage-discuss

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

Title:
  Enable rdma-sniffer for libpcap

Status in libpcap package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Invalid
Status in libpcap package in Debian:
  Won't Fix

Bug description:
  Hi,

  The request is to build and configure stock package libpcap with rdma-sniffer 
enabled.
  We'd like users of rdma devices to be able to sniff on them using stock 
tcpdump.
  Currently when using default tcpdump It does not list rdma devices.

  $ tcpdump -D |grep -i rdma
  $ 

  when using locally build tcpdump (with rdma enabled)
  $ cd 
  $ ./tcpdump -D |grep -i rdma
  24.rocep4s0 (RDMA sniffer)
  25.rocep7s0f0 (RDMA sniffer)
  26.rocep7s0f1 (RDMA sniffer)
  27.rocep10s0f0 (RDMA sniffer)
  28.rocep10s0f1 (RDMA sniffer)
  29.rocep33s0f0 (RDMA sniffer)
  30.rocep33s0f1 (RDMA sniffer)
  31.rocep36s0f0 (RDMA sniffer)
  32.ibp36s0f1 (RDMA sniffer)

  Locally build steps:
  clone sources:
  $ mkdir tcpdumpbuild
  $ cd tcpdumpbuild/
  $ git clone https://github.com/the-tcpdump-group/tcpdump.git
  $ git clone https://github.com/the-tcpdump-group/libpcap.git

  install required packages (including rdma packages so libpcap is built with 
rdma enabled):
  $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils
  configure and build
  $ cd libpcap
  $ ./autogen.sh 
  $ ./configure --enable-rdma=yes
  $ make 
  cd ../tcpdump/
  ./autogen.sh 
  ./configure 
  $ make

  now ./tcpdump -D can show rdma devices.

  Thanks !

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


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

[Kernel-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Lee Sheng Hung]

Sorry for the late reply. Proposed package 23.2.1-1ubuntu3.1~22.04.2
amd64 [installed,automatic], GUI displayed normally, thank you for the
help!

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

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

Bug description:
  [Impact]

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

  [Fix]

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

  [Test case]

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

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

  ---

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

  GUI crashed but still able to access system by ssh.

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

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

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

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

  [Stage]
  Issue reported.

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

[Ubfan]

And yet to me, it looks like things will just work if gcc-12 is simply 
installed, not as the default.
Checking some file dates, I see my gcc-12 was brought (by something) in last 
April, and has been just sitting around. My /bin/gcc and /bin/cc links are 
years old (and link to gcc-11). The 
/lib/modules/6.5.0-14-generic/kernel/nvidia-535/bits/nvidia.o was compiled 
(last week) with gcc-12.3 (correct for my kernel 6.5). It looks like if gcc-12 
is installed, it will be used for building an nvidia module, without changing 
the system /bin/gcc default of gcc-11. When you (MAFoElfen) were trying your 
workaround by changing links (/bin/gcc to gcc-12), did you ever try the nvidia 
driver install before changing links with gcc-12 present? If the right compiler 
gets used if present, that suggests a simple fix of adding a gcc-12 dependency 
on the hwe kernel package (to allow any modules to be build if they do what 
nvidia apparently does). I'll try out some jammy iso boots if I cannot find a 
spare partition to install to and see what happens (I've never bothered to 
figure out how to make my VMs use 
 Nvidia). I can understand not wanting to change the default gcc, but simply 
adding one should not cause problems.

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Won't Fix

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

> I belive /usr/share/initrams-tools/hooks/plymouth can be modified to stop 
> including any
> drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped.

Dropping the DRM modules would also allow us to use a near-zero
device_timeout in Plymouth now. It would then render to efifb without
needing SimpleDRM.

I don't *think* this would affect shutdown because plymouthd for that is
started while we still have the rootfs.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

Thanks. So it still sounds like SimpleDRM is in Ubuntu's future (bug
1965303). But in case that doesn't happen in time for Noble, or if we
simply want a solution that backports to jammy, then I will still focus
on plymouth/kernel changes only.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Yeah; so try forcing plymouth to the Ubuntu initrd like this:

echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash

Then if you rebuild the initrd you'll end up with plymouth in it.

This unfortunately DOUBLES the initramfs size; but it's because it puts all the 
drm modules in there.  
Here is where simpledrm really shines.  I belive 
/usr/share/initrams-tools/hooks/plymouth can be modified to stop including any 
drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped.

I believe this will guarantee plymouth wins the race.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Something "big" I notice different is that by default Ubuntu doesn't put
plymouth in the initramfs but Fedora does.

Maybe plymouthd really isn't running at the time systemd-fsckd is
running.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051733] Re: Specifying nohz_full disables CPU frequency scaling

[Doug Smythies]

I confirm your findings.

In my case I am using: The intel_pstate CPU frequency scaling driver;
powersave CPU frequency scaling governor; HWP, HardWare Pstate, control
is disabled; A mainline kernel, 6.8-rc1, compiled with the kernel
configuration changes being considered in that other bug report. My main
test server with Ubuntu 20.04.6.

Note also, in my case, the CPU frequencies actually seem to be scaling
properly, it is just that they are not being reported properly via
"/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq".

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

Title:
  Specifying nohz_full disables CPU frequency scaling

Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  With the lowlatency kernel, if I specify "nohz_full=1-15" boot
  parameter then CPU frequency scaling doesn't work for the logical
  cores 1-15. That is, only logical core 0 shows varying CPU frequency
  in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all
  other cores constantly show 80 in their scaling_cur_freq files
  (which is the lowest supported frequency) regardless of the CPU load.

  Steps to reproduce:

  1. Add "nohz_full=1-15" (specify the core numbers to include all logical 
cores except 0) to kernel boot options in /etc/default/grub.
  2. Run `sudo update-grub` and reboot.
  3. Upon booting, run a multithreaded workload. For example, run `openssl 
speed -multi $(nproc --all)`.
  4. In another console, monitor CPU frequencies by running `watch cat 
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

  Actual results:

  All cores specified in "nohz_full" parameter are always at their
  lowest frequency.

  Expected results:

  All cores must scale the frequency up with active load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
  Uname: Linux 6.5.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Jan 30 23:39:51 2024
  InstallationDate: Installed on 2015-05-01 (3196 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: linux-signed-lowlatency-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.5/+bug/2051733/+subscriptions


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

[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms

[Kai-Chuan Hsieh]

on MYBY-PIL-C4_202309-32142, install kernel >= 6.5.0-17-generic.

1. install mantic
2. enable proposed
3. $ sudo apt update
4. $ sudo apt dist-upgrade
5. $ sudo rm /var/lib/alsa/asound.state
6. # echo b > /proc/sysrq-trigger
7. $ amixer -c 1 name='PGA2.0 2 Master Capture Volume'
numid=53,iface=MIXER,name='PGA2.0 2 Master Capture Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=80,step=0
  : values=50,50
  | dBscale-min=-50.00dB,step=1.00dB,mute=1

The audio is working. and PGA 2.0 right/left volume are 50.

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

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

  [Other info]

  Lunar is skipped, as it'll be EOL soon

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

[Michael Rakijas]

I have this problem as well.  I've made multiple approaches trying to
install the stock package for CUDA:

cuda-repo-ubuntu2204-12-1-local_12.1.1-530.30.02-1_amd64.deb

but had problems with the 530 Nvidia driver.  Got suggestions to try to
install the 535 Nvidia driver first so that the 530 driver install would
be bypassed as deprecated.  The 535 package would not install with the
following packages being held back:

gjs libgjs0g

These attempts were both on a fresh install.  I may try the suggestion
in

https://ubuntuforums.org/showthread.php?t=2494273=2=14175164#post14175164

but this might be excessive for me and I've got work to do.

-Rocky714

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Won't Fix

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+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 2051733] Re: Specifying nohz_full disables CPU frequency scaling

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-lowlatency-hwe-6.5 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Specifying nohz_full disables CPU frequency scaling

Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  With the lowlatency kernel, if I specify "nohz_full=1-15" boot
  parameter then CPU frequency scaling doesn't work for the logical
  cores 1-15. That is, only logical core 0 shows varying CPU frequency
  in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all
  other cores constantly show 80 in their scaling_cur_freq files
  (which is the lowest supported frequency) regardless of the CPU load.

  Steps to reproduce:

  1. Add "nohz_full=1-15" (specify the core numbers to include all logical 
cores except 0) to kernel boot options in /etc/default/grub.
  2. Run `sudo update-grub` and reboot.
  3. Upon booting, run a multithreaded workload. For example, run `openssl 
speed -multi $(nproc --all)`.
  4. In another console, monitor CPU frequencies by running `watch cat 
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

  Actual results:

  All cores specified in "nohz_full" parameter are always at their
  lowest frequency.

  Expected results:

  All cores must scale the frequency up with active load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
  Uname: Linux 6.5.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Jan 30 23:39:51 2024
  InstallationDate: Installed on 2015-05-01 (3196 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: linux-signed-lowlatency-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.5/+bug/2051733/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

> I don't really know if Fedora does that better or they just failed to
notice the bug.

I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in 
Fedora with simpledrm; never see the console.  That's why I was thinking 
something might be missing and worth looking at.
* Fedora doesn't key off "splash", they key off "rhgb" (standing for red hat 
graphical boot).
* Ubuntu sets "vt.handoff=7", Fedora doesn't do anything.  Maybe it's part of 
this flow difference leading to the problem?  That's from ~10 years ago, does 
it still make sense?

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms

[Chris Chiu]

I verified on 6.5.0-17 mantic kernel built by myself and it passed. @Max
was trying to verify with the proposed mantic 6.5.0-17 kernel.

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

  [Other info]

  Lunar is skipped, as it'll be EOL soon

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


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

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

[dann frazier]

On Tue, Jan 30, 2024 at 6:21 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Oh wait, we've been through something very like this before
> https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
> a judicious application of flock may be the most correct solution
> available.

ACK - I'll switch over to flock and run another test.

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

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

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

"splash" is more appropriate than "quiet" (unfortunately) because we
would delay framebuffer takeover to the same event (primary DRM startup)
as Plymouth does.

I would also like to know why our Plymouth doesn't render on SimpleDRM
even when it's available (tested in bug 1965303). I don't really know if
Fedora does that better or they just failed to notice the bug. And I
don't have much time left for more tangents here.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

> But the feature would still be gated on the "splash" kernel parameter
which is Plymouth-specific and may cause pushback from kernel
developers.

If the patch is the way you go another idea for you is to use the
"quiet" keyword to key off instead for this behavior which is already
used by the kernel.  You'd be overloading it.

quiet   [KNL] Disable most log messages

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Have you already looked at everything Fedora is doing in this area?
They already have simpledrm; but from what you described I would have
thought they should still lose the fbcon race.

Is it just that they don't have systemd-fsckd patch?  I would think they
still end up showing ERR/WARN kernel messages which can be noisy too.

Just wondering if there is something else to look at.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051450] Re: Login loop

[Daniel van Vugt]

The log in comment #6 seems to show it's a problem in the nouveau kernel
driver preventing graphics from starting up:

ene 30 11:03:31 localhost kernel: nouveau :01:00.0: timeout
...
ene 30 11:03:31 localhost kernel: nouveau :01:00.0: 
fifo:c0:0001:0001:[gnome-shell[1853]] vctx 0[gr]: -110
ene 30 11:03:31 localhost org.gnome.Shell.desktop[1853]: 
nvc0_screen_create:1169 - Error allocating PGRAPH context for M2MF: -110
...
ene 30 11:05:14 localhost systemd[1]: session-c2.scope: Killing process 1853 
(gnome-shell) with signal SIGKILL.

To fix this, please:

1. Restart with kernel parameter 'nomodeset'.

2. Use the 'Additional Drivers' app to install a supported Nvidia
driver.

3. Restart without 'nomodeset'.


** Summary changed:

- Login loop
+ Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106

** Tags added: nouveau

** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)

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

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

Title:
  Nouveau kernel errors prevent reaching the login screen on NVIDIA
  GA106

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:29:28 2024
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-12-27 (31 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apport: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051450/+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 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive (on a PC)

[Daniel van Vugt]

Please check to see if the kernel is getting the button events by
running:

  sudo apt install evtest
  sudo evtest

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

Title:
  Raspberry Pi mouse buttons left and right unresponsive (on a PC)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using the event tracker tool 
  (
  xmodmap -pp > ~/xmodmap-pp
  xev | grep -i button 
  ), buttons 4 and 5 are responsive, optical works (the cursor moves across the 
screen).

  Left and right click buttons are unresponsive. Mouse connected via
  USB.

  MOUSE INFO:
  Raspberry Pi Mouse
  CAN ICES-3 (B)/NMB-3(B)
  Model No.: RPI-MOUSE

  This issue has been extant every since I have tried to use this mouse.
  Currently using Ubuntu Mantic Minotaur (23.10)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 21:24:11 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
  InstallationDate: Installed on 2023-12-16 (45 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 00V66M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3510
  dmi.product.sku: 09ED
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051617/+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 2051450] [NEW] Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

n/a

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-session-bin 42.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 28 09:29:28 2024
ExecutablePath: /usr/libexec/gnome-session-binary
InstallationDate: Installed on 2023-12-27 (31 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apport: [deleted]

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


** Tags: amd64 apport-bug jammy nouveau wayland-session
-- 
Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106
https://bugs.launchpad.net/bugs/2051450
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 in Ubuntu.

-- 
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 2051705] Re: Failed to start bluetooth.service: Unit bluetooth.service failed to load properly, please adjust/correct and reload service manager: File exists

[Daniel van Vugt]

It looks like the installation might have succeeded and just requires a
reboot. The error was:

Failed to start bluetooth.service: Unit bluetooth.service failed to load
properly, please adjust/correct and reload service manager: File exists

** Summary changed:

- package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
+ Failed to start bluetooth.service: Unit bluetooth.service failed to load 
properly, please adjust/correct and reload service manager: File exists

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

Title:
  Failed to start bluetooth.service: Unit bluetooth.service failed to
  load properly, please adjust/correct and reload service manager: File
  exists

Status in bluez package in Ubuntu:
  New

Bug description:
  I am unable to turn on my Bluetooth so I unable to connect to my mouse
  and earbuds to laptops

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   bluez:amd64: Install
   python3-gi-cairo:amd64: Install
   blueman:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 30 20:30:22 2024
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-07-28 (186 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   115  Done2024-01-30T20:08:13+05:30  2024-01-30T20:09:04+05:30  Install 
"bluez" snap
  SourcePackage: bluez
  Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
  dmi.bios.date: 06/13/2018
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 20:16:B9:30:5F:51  ACL MTU: 1021:5  SCO MTU: 96:6
DOWN 
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051705/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

I now expect the kernel patch would change before it gets proposed to
dri-devel. In particular the primary delay doesn't need to be
configurable (or even finite?), and the secondary delay probably doesn't
need to be more than zero. But the feature would still be gated on the
"splash" kernel parameter which is Plymouth-specific and may cause
pushback from kernel developers.

It's starting to make more sense to implement the console disabling
using ioctls in plymouthd itself. Because I think plymouthd is running
early enough to do that, it's only refusing to render for several
seconds so fbcon wins the race to the framebuffer.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

** Changed in: plymouth (Ubuntu)
   Status: Invalid => 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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

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

[Michael Hudson-Doyle]

Oh wait, we've been through something very like this before
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
a judicious application of flock may be the most correct solution
available.

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

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

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

I am also the author of the Plymouth feature that parses and renders the
fsck progress. What I think isn't being communicated here is that it's
currently useless on startup. Because Plymouth doesn't start rendering
until well after the fsck has already happened. See also bug 1869655.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

[Mike Ferreira]

** Also affects: dkms (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Won't Fix

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Kernel-packages] [Bug 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive (on a PC)

[N335T3R]

Hi. I'm sorry for left-out details. This is my first time reporting a bug.
The issue occurs when using a Raspberry Pi mouse plugged into a DELL
Latitude 3510 machine running Ubuntu 23.10.

On Tue, Jan 30, 2024 at 12:55 AM Daniel van Vugt <2051...@bugs.launchpad.net>
wrote:

> Also you don't seem to be using a Raspberry Pi or Xorg here. Was the
> mouse plugged into a different machine?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2051617
>
> Title:
>   Raspberry Pi mouse buttons left and right unresponsive (on a PC)
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Using the event tracker tool
>   (
>   xmodmap -pp > ~/xmodmap-pp
>   xev | grep -i button
>   ), buttons 4 and 5 are responsive, optical works (the cursor moves
> across the screen).
>
>   Left and right click buttons are unresponsive. Mouse connected via
>   USB.
>
>   MOUSE INFO:
>   Raspberry Pi Mouse
>   CAN ICES-3 (B)/NMB-3(B)
>   Model No.: RPI-MOUSE
>
>   This issue has been extant every since I have tried to use this mouse.
>   Currently using Ubuntu Mantic Minotaur (23.10)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 23.10
>   Package: xorg 1:7.7+23ubuntu2
>   ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
>   Uname: Linux 6.5.0-15-generic x86_64
>   ApportVersion: 2.27.0-0ubuntu5
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jan 29 21:24:11 2024
>   DistUpgraded: Fresh install
>   DistroCodename: mantic
>   DistroVariant: ubuntu
>   DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02)
> (prog-if 00 [VGA controller])
>  Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
>   InstallationDate: Installed on 2023-12-16 (45 days ago)
>   InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
> (20231016.1)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
>Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Lsusb-t:
>/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
>/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
>|__ Port 3: Dev 3, If 0, Class=Human Interface Device,
> Driver=usbhid, 1.5M
>|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
>|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
>   MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
> root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/05/2021
>   dmi.bios.release: 1.10
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.10.1
>   dmi.board.name: 00V66M
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
>   dmi.product.family: Latitude
>   dmi.product.name: Latitude 3510
>   dmi.product.sku: 09ED
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.115-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20210115-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.17-2build1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051617/+subscriptions
>
>

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

Title:
  Raspberry Pi mouse buttons left and right unresponsive (on a PC)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using the event tracker tool 
  (
  xmodmap -pp > ~/xmodmap-pp
  xev | grep -i button 
  ), buttons 4 and 5 are responsive, optical works (the cursor moves across the 
screen).

  Left and right 

[Kernel-packages] [Bug 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop

[Jeff Lane ]

Still no update, it's apparently a very low priority to be looked at.

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

Title:
  Could not switch uppercase/lowercase by using keyboard of laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Fresh install ubuntu server 22.04.1 on Lenovo server.
  2. Install console-data package 
  3. Get locale status: 
  # localectl status
 System Locale: LANG=en_US.UTF-8
 VC Keymap: n/a
X11 Layout: us
 X11 Model: pc105
  4. Fail to ist and set keymap with command "localectl", but the kmap file can 
be found in the /usr/share./keymaps/
  #localectl list-keymaps 
  Failed to read list of keymaps: No such file or directory 
  # localectl set-keymap us
  Failed to set keymap: Keymap us is not installed.
  # find /usr/ -name us.kmap.gz
  /usr/share/keymaps/i386/qwerty/us.kmap.gz 
  5. It need type "CapsLock" twice when want to switch uppercase/lowercase by 
using keyboard of laptop, not once, the other keyboard has no issue about it.
  # dumpkeys | grep -E "keymaps|58"
  keymaps 0-127
  keycode  58 = CtrlL_Lock 
  6. It can switch uppercase/lowercase normally after run command "loadkeys us".

  Please help check why need type twice "CapsLock" for switching 
uppercase/lowercase and how to fix it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  MachineType: Lenovo ThinkSystem SR630 V2
  Package: systemd 249.11-0ubuntu3.4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/21/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: Lenovo
  dmi.bios.version: AFE118I-1.30
  dmi.board.asset.tag: none
  dmi.board.name: 7Z70CTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.80
  dmi.modalias: 
dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR630 V2
  dmi.product.sku: 7Z70CTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+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 2051741] Re: Gnome Crashes Rendering Desktop Unusable

[Brett Holman]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051741/+attachment/5743702/+files/lspci-vnvn.log

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

Title:
  Gnome Crashes Rendering Desktop Unusable

Status in linux package in Ubuntu:
  New

Bug description:
  The issue is very reproducible. It happened within a minute or two of
  using my machine after updating from Lunar to Mantic. I tried
  upgrading to Noble to see if a newer kernel might have the fix - it
  didn't. My machine is unusable and I'm happy to repro if anyone has
  the fix

  
  [Tue Jan 30 16:04:51 2024] [drm] ring 0 timeout to preempt ib
  [Tue Jan 30 16:05:01 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
gfx_high timeout, signaled seq=1266, emitted seq=1268
  [Tue Jan 30 16:05:01 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process gnome-shell pid 8121 thread gnome-shel:cs0 pid 8152
  [Tue Jan 30 16:05:01 2024] amdgpu :1f:00.0: amdgpu: GPU reset begin!
  [Tue Jan 30 16:05:01 2024] [drm] psp gfx command UNLOAD_TA(0x2) failed and 
response status is (0x117)
  [Tue Jan 30 16:05:01 2024] amdgpu :1f:00.0: amdgpu: BACO reset
  [Tue Jan 30 16:05:02 2024] amdgpu :1f:00.0: amdgpu: GPU reset succeeded, 
trying to resume
  [Tue Jan 30 16:05:02 2024] [drm] PCIE GART of 512M enabled.


  
  package: linux-generic/noble,now 6.6.0-14.14 amd64 [installed]
  uname: Linux arc 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 30 
10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/vgubuntu-root 
ro quiet splash vt.handoff=7

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


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

[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

[DronKram]

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

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

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

Bug description:
  SRU Justification:

  [Impact]

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

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


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

  Expected Behavior:
  OS should boot without this Call Trace

  [Fix]

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

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

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

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

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

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

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

  [Test Plan]

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

  [Where problems could occur]

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

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


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

[Kernel-packages] [Bug 2051741] [NEW] Gnome Crashes Rendering Desktop Unusable

[Brett Holman]

Public bug reported:

The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone has the fix


[Tue Jan 30 16:04:51 2024] [drm] ring 0 timeout to preempt ib
[Tue Jan 30 16:05:01 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
gfx_high timeout, signaled seq=1266, emitted seq=1268
[Tue Jan 30 16:05:01 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process gnome-shell pid 8121 thread gnome-shel:cs0 pid 8152
[Tue Jan 30 16:05:01 2024] amdgpu :1f:00.0: amdgpu: GPU reset begin!
[Tue Jan 30 16:05:01 2024] [drm] psp gfx command UNLOAD_TA(0x2) failed and 
response status is (0x117)
[Tue Jan 30 16:05:01 2024] amdgpu :1f:00.0: amdgpu: BACO reset
[Tue Jan 30 16:05:02 2024] amdgpu :1f:00.0: amdgpu: GPU reset succeeded, 
trying to resume
[Tue Jan 30 16:05:02 2024] [drm] PCIE GART of 512M enabled.


package: linux-generic/noble,now 6.6.0-14.14 amd64 [installed]
uname: Linux arc 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 30 
10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/vgubuntu-root ro 
quiet splash vt.handoff=7

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

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/2051741/+attachment/5743701/+files/version.log

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

Title:
  Gnome Crashes Rendering Desktop Unusable

Status in linux package in Ubuntu:
  New

Bug description:
  The issue is very reproducible. It happened within a minute or two of
  using my machine after updating from Lunar to Mantic. I tried
  upgrading to Noble to see if a newer kernel might have the fix - it
  didn't. My machine is unusable and I'm happy to repro if anyone has
  the fix

  
  [Tue Jan 30 16:04:51 2024] [drm] ring 0 timeout to preempt ib
  [Tue Jan 30 16:05:01 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
gfx_high timeout, signaled seq=1266, emitted seq=1268
  [Tue Jan 30 16:05:01 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process gnome-shell pid 8121 thread gnome-shel:cs0 pid 8152
  [Tue Jan 30 16:05:01 2024] amdgpu :1f:00.0: amdgpu: GPU reset begin!
  [Tue Jan 30 16:05:01 2024] [drm] psp gfx command UNLOAD_TA(0x2) failed and 
response status is (0x117)
  [Tue Jan 30 16:05:01 2024] amdgpu :1f:00.0: amdgpu: BACO reset
  [Tue Jan 30 16:05:02 2024] amdgpu :1f:00.0: amdgpu: GPU reset succeeded, 
trying to resume
  [Tue Jan 30 16:05:02 2024] [drm] PCIE GART of 512M enabled.


  
  package: linux-generic/noble,now 6.6.0-14.14 amd64 [installed]
  uname: Linux arc 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 30 
10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/vgubuntu-root 
ro quiet splash vt.handoff=7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051741/+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 2051612] Re: False key press suspend wakeup on AMD Framework 13

[Matt Hartley]

Okay Bug Bot, updated.

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

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

Title:
  False key press suspend wakeup on AMD Framework 13

Status in Ubuntu:
  New
Status in linux-meta-oem-6.5 package in Ubuntu:
  New

Bug description:
  Affects: Ubuntu 22.04.3 OEM C kernel.

  What is expected: Close the lid to suspend, expecting it to remain in
  a suspended state.

  What is happening instead: The Laptop 13 (AMD Ryzen 7040Series) BIOS 03.03 
has a workaround
  included in the EC firmware that will cause the EC to emit a "spurious"
  key press during the resume from s0i3 [1].

  There is a workaround described as follows:

  /etc/udev/rules.d/20-suspend-fixes.rules

  with

  ACTION=="add", SUBSYSTEM=="serio", DRIVERS=="atkbd",
  ATTR{power/wakeup}="disabled"

  Provides a workaround.

  Mario Limonciello points out this is not backported to the OEM kernel, so the 
fix may need to happen here.
  
https://community.frame.work/t/responded-waking-from-sleep-when-plugged-in-amd-k-ubuntu-22-04/44168/10

  Here is the Linux commit itself:
  
https://github.com/torvalds/linux/commit/a55bdad5dfd1efd4ed9ffe518897a21ca8e4e193

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2051612/+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 2049966] Re: Linux version 6.5.0-14-generic, XFCE, black screen after log in

[Richard Bartczak]

This Bug report is a duplicate of :
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2051410

Bug solved by proposed version 6.5.0-17-generic.

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

Title:
  Linux version 6.5.0-14-generic, XFCE, black screen after log in

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

Bug description:
  Linux version 6.5.0-14-generic, dmesg.0
  ...
  [   27.944254] kernel: [drm] PCIE GART of 1024M enabled.
  [   27.944256] kernel: [drm] PTB located at 0x00F400A0
  [   27.945002] kernel: amdgpu: hwmgr_sw_init smu backed is smu10_smu
  [   27.947465] kernel: [drm] Found VCN firmware Version ENC: 1.13 DEC: 2 VEP: 
0 Revision: 3
  [   27.947495] kernel: amdgpu :03:00.0: amdgpu: Will use PSP to load VCN 
firmware
  [   27.970505] kernel: [drm] reserve 0x40 from 0xf47fc0 for PSP TMR
  [   28.039884] kernel: amdgpu :03:00.0: amdgpu: RAS: optional ras ta 
ucode is not available
  [   28.046476] kernel: amdgpu :03:00.0: amdgpu: RAP: optional rap ta 
ucode is not available
  [   28.050530] kernel: 

  [   28.050550] kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  [   28.050568] kernel: index 1 is out of range for type 'UCHAR [1]'
  [   28.050577] kernel: CPU: 1 PID: 333 Comm: systemd-udevd Not tainted 
6.5.0-14-generic #14~22.04.1-Ubuntu
  [   28.050582] kernel: Hardware name: ASUSTeK COMPUTER INC. 
VivoBook_ASUSLaptop X515DA_M515DA/X515DA, BIOS X515DA.302 10/19/2020
  [   28.050585] kernel: Call Trace:
  [   28.050589] kernel:  
  [   28.050595] kernel:  dump_stack_lvl+0x48/0x70
  [   28.050610] kernel:  dump_stack+0x10/0x20
  [   28.050615] kernel:  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   28.050623] kernel:  ? 
__pfx_smu10_dpm_get_pp_table_entry_callback+0x10/0x10 [amdgpu]
  [   28.051793] kernel:  pp_tables_get_entry+0x268/0x2a0 [amdgpu]
  [   28.052842] kernel:  smu10_dpm_get_pp_table_entry+0x23/0x50 [amdgpu]
  [   28.053884] kernel:  psm_init_power_state_table+0x161/0x250 [amdgpu]
  [   28.054923] kernel:  hwmgr_hw_init+0xe3/0x1e0 [amdgpu]
  [   28.055929] kernel:  pp_hw_init+0x16/0x50 [amdgpu]
  [   28.056854] kernel:  amdgpu_device_ip_init+0x48d/0x960 [amdgpu]
  [   28.057730] kernel:  amdgpu_device_init+0x9c8/0x1160 [amdgpu]
  [   28.058535] kernel:  amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu]
  [   28.059128] kernel:  amdgpu_pci_probe+0x182/0x450 [amdgpu]
  [   28.059650] kernel:  local_pci_probe+0x47/0xb0
  [   28.059658] kernel:  pci_call_probe+0x55/0x190
  [   28.059666] kernel:  pci_device_probe+0x84/0x120
  [   28.059670] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.059679] kernel:  really_probe+0x1cc/0x430
  [   28.059685] kernel:  __driver_probe_device+0x8c/0x190
  [   28.059691] kernel:  driver_probe_device+0x24/0xd0
  [   28.059696] kernel:  __driver_attach+0x10b/0x210
  [   28.059701] kernel:  ? __pfx___driver_attach+0x10/0x10
  [   28.059705] kernel:  bus_for_each_dev+0x8d/0xf0
  [   28.059713] kernel:  driver_attach+0x1e/0x30
  [   28.059718] kernel:  bus_add_driver+0x127/0x240
  [   28.059725] kernel:  driver_register+0x5e/0x130
  [   28.059731] kernel:  ? __pfx_amdgpu_init+0x10/0x10 [amdgpu]
  [   28.060289] kernel:  __pci_register_driver+0x62/0x70
  [   28.060297] kernel:  amdgpu_init+0x69/0xff0 [amdgpu]
  [   28.060856] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060864] kernel:  do_one_initcall+0x5e/0x340
  [   28.060876] kernel:  do_init_module+0x68/0x260
  [   28.060883] kernel:  load_module+0xb85/0xcd0
  [   28.060890] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060895] kernel:  ? security_kernel_post_read_file+0x75/0x90
  [   28.060905] kernel:  init_module_from_file+0x96/0x100
  [   28.060910] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060915] kernel:  ? init_module_from_file+0x96/0x100
  [   28.060919] kernel:  ? sysvec_call_function+0xa6/0xd0
  [   28.060931] kernel:  idempotent_init_module+0x11c/0x2b0
  [   28.060941] kernel:  __x64_sys_finit_module+0x64/0xd0
  [   28.060947] kernel:  do_syscall_64+0x5b/0x90
  [   28.060954] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060959] kernel:  ? ksys_mmap_pgoff+0x120/0x270
  [   28.060964] kernel:  ? __secure_computing+0x89/0xf0
  [   28.060970] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060975] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060980] kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  [   28.060986] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.060990] kernel:  ? syscall_exit_to_user_mode+0x37/0x60
  [   28.060995] kernel:  ? srso_return_thunk+0x5/0x10
  [   28.061000] kernel:  ? do_syscall_64+0x67/0x90
  [   28.061004] kernel:  ? sysvec_call_function+0x4b/0xd0
  [   28.061009] kernel:  

[Kernel-packages] [Bug 2049530] Re: apply nvidia-tegra patches for Jan 16

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1021.21

---
linux-nvidia-tegra (5.15.0-1021.21) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1021.21 -proposed tracker (LP:
#2049525)

  * apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
- NVIDIA: SAUCE: mmc: host: restrict min clk rate to 20MHz
- NVIDIA: SAUCE: arm64: configs: enable PCIe ethernet
- NVIDIA: SAUCE: mmc: sdhci-tegra: do not set padpipe_clk_override
- NVIDIA: SAUCE: arm64: configs: Sanitize defconfig
- NVIDIA: SAUCE: clocksource/drivers/timer-tegra186: add WDIOC_GETTIMELEFT
  support
- NVIDIA: SAUCE: clocksource/drivers/timer-tegra186: fix watchdog self-
  pinging.
- NVIDIA: SAUCE: arm64: configs: enable CONFIG_DMI
- NVIDIA: SAUCE: mmc: sdhci-tegra: Enable wake on SD card event
- NVIDIA: SAUCE: mmc: core: Update bus status on sd card removal
- [Config] Re-enable CONFIG_DMI

  * apply nvidia igx patches for Nov 29 - Dec 8 2023 (LP: #2046011)
- NVIDIA: SAUCE: arm64: configs: disable pps debug config
- NVIDIA: SAUCE: net: phy: aquantia: Poll for valid FW ID.

  * apply nvidia igx patches for Oct 19 - Nov 28 2023 (LP: #2045080)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: arm64: configs: enable cfs bandwidth for k8s
- NVIDIA: SAUCE: arm64: config: Disable DMI config

  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug

  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: arch: arm64: enable FB_SIMPLE config
- NVIDIA: SAUCE: (no-up) mm: mprotect: Avoid write-fault handler for dirty
  written PTEs

  * Apply 2023-07-20 + 2023-07-31 IGX PRs from NVIDIA (LP: #2029295)
- SAUCE: arm64: defconfig: enable CONFIG_ISO9660_FS

  * apply nvidia-tegra patches for Jan 16 (LP: #2049530)
- NVIDIA: SAUCE: tegra-epl: Set handshake retry count to 20
- NVIDIA: SAUCE: tegra-epl: publish kernel pm state to FSI
- NVIDIA: SAUCE: tegra-epl: Set default handshake retry count to 25
- NVIDIA: SAUCE: arm64: 

[Kernel-packages] [Bug 2049536] Re: apply nvidia-tegra patches 2024 Jan 1-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1021.21

---
linux-nvidia-tegra (5.15.0-1021.21) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1021.21 -proposed tracker (LP:
#2049525)

  * apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
- NVIDIA: SAUCE: mmc: host: restrict min clk rate to 20MHz
- NVIDIA: SAUCE: arm64: configs: enable PCIe ethernet
- NVIDIA: SAUCE: mmc: sdhci-tegra: do not set padpipe_clk_override
- NVIDIA: SAUCE: arm64: configs: Sanitize defconfig
- NVIDIA: SAUCE: clocksource/drivers/timer-tegra186: add WDIOC_GETTIMELEFT
  support
- NVIDIA: SAUCE: clocksource/drivers/timer-tegra186: fix watchdog self-
  pinging.
- NVIDIA: SAUCE: arm64: configs: enable CONFIG_DMI
- NVIDIA: SAUCE: mmc: sdhci-tegra: Enable wake on SD card event
- NVIDIA: SAUCE: mmc: core: Update bus status on sd card removal
- [Config] Re-enable CONFIG_DMI

  * apply nvidia igx patches for Nov 29 - Dec 8 2023 (LP: #2046011)
- NVIDIA: SAUCE: arm64: configs: disable pps debug config
- NVIDIA: SAUCE: net: phy: aquantia: Poll for valid FW ID.

  * apply nvidia igx patches for Oct 19 - Nov 28 2023 (LP: #2045080)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: arm64: configs: enable cfs bandwidth for k8s
- NVIDIA: SAUCE: arm64: config: Disable DMI config

  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug

  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: arch: arm64: enable FB_SIMPLE config
- NVIDIA: SAUCE: (no-up) mm: mprotect: Avoid write-fault handler for dirty
  written PTEs

  * Apply 2023-07-20 + 2023-07-31 IGX PRs from NVIDIA (LP: #2029295)
- SAUCE: arm64: defconfig: enable CONFIG_ISO9660_FS

  * apply nvidia-tegra patches for Jan 16 (LP: #2049530)
- NVIDIA: SAUCE: tegra-epl: Set handshake retry count to 20
- NVIDIA: SAUCE: tegra-epl: publish kernel pm state to FSI
- NVIDIA: SAUCE: tegra-epl: Set default handshake retry count to 25
- NVIDIA: SAUCE: arm64: 

[Kernel-packages] [Bug 2049536] Re: apply nvidia-tegra patches 2024 Jan 1-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1008.8

---
linux-nvidia-tegra-igx (5.15.0-1008.8) jammy; urgency=medium

  * jammy/linux-nvidia-tegra-igx: 5.15.0-1008.8 -proposed tracker (LP:
#2049526)

  * apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
- [Config] linux-nvidia-tegra-igx: Set CONFIG_OPTEE=y and CONFIG_TEE=y
- [Packaging] Out-of-tree Tegra modules are now built via separate source
  package
- [Packaging] Remove out-of-tree Tegra modules from ABI

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/d2024.01.02)

  [ Ubuntu: 5.15.0-1021.21 ]

  * jammy/linux-nvidia-tegra: 5.15.0-1021.21 -proposed tracker (LP: #2049525)
  * apply nvidia-tegra patches 2024 Jan 1-15 (LP: #2049536)
- NVIDIA: SAUCE: mmc: host: restrict min clk rate to 20MHz
- NVIDIA: SAUCE: arm64: configs: enable PCIe ethernet
- NVIDIA: SAUCE: mmc: sdhci-tegra: do not set padpipe_clk_override
- NVIDIA: SAUCE: arm64: configs: Sanitize defconfig
- NVIDIA: SAUCE: clocksource/drivers/timer-tegra186: add WDIOC_GETTIMELEFT
  support
- NVIDIA: SAUCE: clocksource/drivers/timer-tegra186: fix watchdog self-
  pinging.
- NVIDIA: SAUCE: arm64: configs: enable CONFIG_DMI
- NVIDIA: SAUCE: mmc: sdhci-tegra: Enable wake on SD card event
- NVIDIA: SAUCE: mmc: core: Update bus status on sd card removal
- [Config] Re-enable CONFIG_DMI
  * apply nvidia igx patches for Nov 29 - Dec 8 2023 (LP: #2046011)
- NVIDIA: SAUCE: arm64: configs: disable pps debug config
- NVIDIA: SAUCE: net: phy: aquantia: Poll for valid FW ID.
  * apply nvidia igx patches for Oct 19 - Nov 28 2023 (LP: #2045080)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: arm64: configs: enable cfs bandwidth for k8s
- NVIDIA: SAUCE: arm64: config: Disable DMI config
  * apply nvidia igx patches for Sep 20-29 (LP: #2038165)
- drm/format-helper: Add drm_fb_xrgb_to_rgb332()
- drm/format-helper: Add drm_fb_xrgb_to_rgb888()
- drm/gud: Add GUD_PIXEL_FORMAT_R8
- drm/gud: Add GUD_PIXEL_FORMAT_RGB332
- drm/gud: Add GUD_PIXEL_FORMAT_RGB888
- drm/format-helper: Export drm_fb_clip_offset()
- drm/format-helper: Rework format-helper memcpy functions
- drm/format-helper: Add destination-buffer pitch to drm_fb_swab()
- drm/format-helper: Rework format-helper conversion functions
- drm/format-helper: Streamline blit-helper interface
- drm/simpledrm: Enable FB_DAMAGE_CLIPS property
- drm/simpledrm: Support virtual screen sizes
- drm/format-helper: Add drm_fb_xrgb_to_xrgb2101010_toio()
- drm/simpledrm: Add [AX]RGB2101010 formats
- drm/simpledrm: Request memory region in driver
- drm/format-helper: Add drm_fb_xrgb_to_gray8_line()
- drm/format-helper: Add drm_fb_xrgb_to_mono_reversed()
- drm/repaper: Use format helper for xrgb to monochrome conversion
- drm/simpledrm: Use fbdev defaults for shadow buffering
- drm/format-helper: Rename drm_fb_xrgb_to_mono_reversed()
- drm/format-helper: Fix XRGB888 to monochrome conversion
- drm/format_helper: fix a kernel-doc typo
- drm/format-helper: Print warning on missing format conversion
- drm/format-helper: Add RGB888-to-XRGB conversion
- drm/format-helper: Add RGB565-to-XRGB conversion
- drm/format-helper: Implement drm_fb_swab() with per-line helpers
- drm/format-helper: Remove optional byte-swap from line convertion
- drm/format-helper: Unify the parameters of all per-line conversion helpers
- drm/format-helper: Share implementation among conversion helpers
- drm/atomic-helper: Add helper drm_atomic_helper_check_crtc_state()
- drm/fourcc: Add drm_format_info_bpp() helper
- drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers
- drm/simpledrm: Remove mem field from device structure
- drm/simpledrm: Inline device-init helpers
- drm/simpledrm: Remove pdev field from device structure
- drm/simpledrm: Compute framebuffer stride if not set
- drm/simpledrm: Convert to atomic helpers
- drm/format-helper: Provide drm_fb_blit()
- drm/format-helper: Add drm_fb_build_fourcc_list() helper
- drm/simpledrm: Compute linestride with drm_format_info_min_pitch()
- drm/simpledrm: Use drm_atomic_get_new_plane_state()
- drm/simpledrm: Remove !fb check from atomic_update
- drm/simpledrm: Iterate over damage clips
- drm/simpledrm: Synchronize access to GEM BOs
- drm/simpledrm: Set preferred depth from format of scanout buffer
- drm/simpledrm: Use struct iosys_map consistently
- drm/simpledrm: Add support for system memory framebuffers
- drm/simpledrm: Fix an NULL vs IS_ERR() bug
  * apply nvidia igx patches for Aug 29 - Sep 19 (LP: #2036672)
- NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
- NVIDIA: SAUCE: arch: arm64: enable FB_SIMPLE 

[Kernel-packages] [Bug 2042363] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cha...@us.ibm.com 2024-01-30 16:28 EDT---
Is there an update from Canonical please? Can we provide any further 
information or trace to help diagnose this issue ?

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

Title:
  AIX 7.3 NFS client frequently returns an EIO error to an application
  when reading or writing to a file that has been locked with fcntl() on
  a Ubuntu 20.04 NFSV4 server

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

  The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
   
  ---uname output---
  Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
   
  Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

  ---Steps to Reproduce---
   We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

  However, we can provide any requested trace or dumps from any or all
  of the involved machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress

[Mario Limonciello]

JFYI

WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 [1] is
reported to fix issues that were found in 36 in [2].


[1] 
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/5217b76bed90ae86d5f3fe9a5f4e2301868cdd02
[2] https://bugzilla.kernel.org/show_bug.cgi?id=217239

** Bug watch added: Linux Kernel Bug Tracker #217239
   https://bugzilla.kernel.org/show_bug.cgi?id=217239

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

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Triaged
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Due to a known silicon limitation, the following sequence is needed while
  initialing the PCIE device on a certain devices with ASMedia chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes from
  suspend.

  [Fix]

  Upstream commits:
  * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
  * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")

  And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
  update board-2.bin") to forfill git history dependency.

  And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
  bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
  has not yet accept the PR for bug 2042534, it has no such problem at this
  moment.

  [Test Case]

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
  Jammy for oem-6.5 included.

  == original bug report ==

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
    - This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
    - The FW is to support new China regulatory support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2051342] Re: Enable lowlatency settings in the generic kernel

[Lastique]

While testing locally, I have found this problem:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-
hwe-6.5/+bug/2051733

If this is indeed a valid bug and not something weirdly specific to my
system, I'd say `nohz_full` is non-functional.

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time options.

  Moreover, once these changes are applied we will be able to deprecate
  the lowlatency kernel, saving engineering time and also reducing power
  consumption (required to build the kernel and do all the testing).

  Optionally, we can also provide optimal "lowlatency" settings as 

[Kernel-packages] [Bug 2051733] [NEW] Specifying nohz_full disables CPU frequency scaling

[Lastique]

Public bug reported:

With the lowlatency kernel, if I specify "nohz_full=1-15" boot parameter
then CPU frequency scaling doesn't work for the logical cores 1-15. That
is, only logical core 0 shows varying CPU frequency in its
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all other
cores constantly show 80 in their scaling_cur_freq files (which is
the lowest supported frequency) regardless of the CPU load.

Steps to reproduce:

1. Add "nohz_full=1-15" (specify the core numbers to include all logical cores 
except 0) to kernel boot options in /etc/default/grub.
2. Run `sudo update-grub` and reboot.
3. Upon booting, run a multithreaded workload. For example, run `openssl speed 
-multi $(nproc --all)`.
4. In another console, monitor CPU frequencies by running `watch cat 
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

Actual results:

All cores specified in "nohz_full" parameter are always at their lowest
frequency.

Expected results:

All cores must scale the frequency up with active load.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
Uname: Linux 6.5.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Jan 30 23:39:51 2024
InstallationDate: Installed on 2015-05-01 (3196 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: linux-signed-lowlatency-hwe-6.5
UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Specifying nohz_full disables CPU frequency scaling

Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu:
  New

Bug description:
  With the lowlatency kernel, if I specify "nohz_full=1-15" boot
  parameter then CPU frequency scaling doesn't work for the logical
  cores 1-15. That is, only logical core 0 shows varying CPU frequency
  in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all
  other cores constantly show 80 in their scaling_cur_freq files
  (which is the lowest supported frequency) regardless of the CPU load.

  Steps to reproduce:

  1. Add "nohz_full=1-15" (specify the core numbers to include all logical 
cores except 0) to kernel boot options in /etc/default/grub.
  2. Run `sudo update-grub` and reboot.
  3. Upon booting, run a multithreaded workload. For example, run `openssl 
speed -multi $(nproc --all)`.
  4. In another console, monitor CPU frequencies by running `watch cat 
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

  Actual results:

  All cores specified in "nohz_full" parameter are always at their
  lowest frequency.

  Expected results:

  All cores must scale the frequency up with active load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
  Uname: Linux 6.5.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Jan 30 23:39:51 2024
  InstallationDate: Installed on 2015-05-01 (3196 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: linux-signed-lowlatency-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.5/+bug/2051733/+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 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic

[Simon Fels]

I gave this another spin today with 6.5.0-17-generic #17~22.04.1 and the
LRM modules of the 535 driver (6.5.0-17.17~22.04.1+1 of linux-modules-
nvidia-535-server-generic-hwe-22.04) on our Altra system with 2x L4 GPUs
and the same problem exists as with the DKMS modules:

[   39.437849] watchdog: BUG: soft lockup - CPU#62 stuck for 26s! 
[systemd-udevd:850]
[   39.445411] Modules linked in: nvidia(POE+) crct10dif_ce polyval_ce 
polyval_generic ghash_ce ast mlx5_core video drm_shmem_helper sm4 mlxfw sha2_ce 
drm_kms_helper nvme psample sha256_arm64 sha1_ce nvme_core igb drm tls xhci_pci 
nvme_common pci_hyperv_intf xhci_pci_renesas i2c_algo_bit aes_neon_bs 
aes_neon_blk aes_ce_blk aes_ce_cipher
[   39.474949] CPU: 62 PID: 850 Comm: systemd-udevd Tainted: P   OE 
 6.5.0-17-generic #17~22.04.1-Ubuntu
[   39.485196] Hardware name: GIGABYTE G242-P30-JG/MP32-AR0-JG, BIOS F07 
03/22/2021
[   39.492578] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   39.499526] pc : smp_call_function_many_cond+0x19c/0x720
[   39.504830] lr : smp_call_function_many_cond+0x1b8/0x720
[   39.510130] sp : 80008934b920
[   39.513431] x29: 80008934b920 x28: aef99146dd10 x27: 
[   39.520554] x26: 004f x25: 085dcfffbb80 x24: 0026
[   39.527677] x23: 0001 x22: 085dcfdd6708 x21: aef9914726e0
[   39.534799] x20: 085dcfadbb80 x19: 085dcfdd6700 x18: 800089341060
[   39.541921] x17:  x16:  x15: 43535f5f00656c75
[   39.549044] x14: 0c030b111b111303 x13: 0006 x12: 3931413337353339
[   39.556166] x11: 0101010101010101 x10: 004f x9 : aef98ee015b8
[   39.563289] x8 :  x7 :  x6 : 003e
[   39.570411] x5 : aef99146d000 x4 :  x3 : 085dcfadbb88
[   39.577533] x2 : 0026 x1 : 0011 x0 : 
[   39.584656] Call trace:
[   39.587090]  smp_call_function_many_cond+0x19c/0x720
[   39.592043]  kick_all_cpus_sync+0x50/0xa8
[   39.596040]  flush_module_icache+0x94/0xf8
[   39.600125]  load_module+0x448/0x8e0
[   39.603688]  init_module_from_file+0x94/0x110
[   39.608033]  idempotent_init_module+0x194/0x2b0
[   39.612551]  __arm64_sys_finit_module+0x74/0x100
[   39.617155]  invoke_syscall+0x7c/0x130
[   39.620892]  el0_svc_common.constprop.0+0x5c/0x170
[   39.625670]  do_el0_svc+0x38/0x68
[   39.628972]  el0_svc+0x30/0xe0
[   39.632016]  el0t_64_sync_handler+0x128/0x158
[   39.636360]  el0t_64_sync+0x1b0/0x1b8

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

Title:
  arm64 AWS host hangs during modprobe nvidia on lunar and mantic

Status in linux-aws package in Ubuntu:
  Incomplete
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Confirmed

Bug description:
  Loading the nvidia driver dkms modules with "modprove nvidia" will
  result in the host hanging and being completely unusable. This was
  reproduced using both the linux generic and linux-aws kernels on lunar
  and mantic using an AWS g5g.xlarge instance.

  To reproduce using the generic kernel:
  # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge.

  # Install the linux generic kernel from lunar-updates:
  $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o 
DPkg::Options::=--force-confold linux-generic

  # Boot to the linux-generic kernel (this can be accomplished by removing the 
existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel)
  $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o 
DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 
linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws 
linux-image-aws linux-modules-6.2.0-1008-aws  linux-headers-6.2.0-1008-aws 
linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws
  $ reboot

  # Install the Nvidia 535-server driver DKMS package:
  $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y 
nvidia-driver-535-server

  # Enable the driver
  $ sudo modprobe nvidia

  # At this point the system will hang and never return.
  # A reboot instead of a modprobe will result in a system that never boots up 
all the way. I was able to recover the console logs from such a system and 
found (the full captured log is attached):

  [1.964942] nvidia: loading out-of-tree module taints kernel.
  [1.965475] nvidia: module license 'NVIDIA' taints kernel.
  [1.965905] Disabling lock debugging due to kernel taint
  [1.980905] nvidia: module verification failed: signature and/or required 

[Kernel-packages] [Bug 2033348] Re: Wireless: Update RTL8852BE wifi driver

[Dave]

Any updates here?

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

Title:
  Wireless: Update RTL8852BE wifi driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Firmware 0.27 was added in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there
  has been an update submitted by Realtek which resolves crash issues of
  the driver related to DMA.

  New firmware file is up in kernel:
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/log/rtw89/rtw8852b_fw-1.bin?showmsg=1

  Ideally updated for both Lunar and Jammy :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348/+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 2051730] [NEW] vmlinuz-6.5.0-15-generic allows only one monitor to display on dual monitor video card.

[Frank Ford]

Public bug reported:

My system works fine using vmlinuz-5.15.0-92-generic. When I run
software update and the new kernel vmlinuz-6.5.0-15-generic is installed
I no longer have a dual monitor system. This is the second time this has
happened and I have to return to a prior kernel version to get the
second monitor to work. I noticed that the prior version is using
"GRAPHICS: Quadro 2000/PCIe/SSE2" found in the SETTINGS ABOUT
information and the new kernel is using "GRAPHICS:llvmpipe (LLVM
15.0.7.256 bits)". Both kernels are using the NVIDIA driver metapackage
from nvidia-driver-390(proprietary tested).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 30 14:29:15 2024
InstallationDate: Installed on 2024-01-21 (8 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: Upgraded to jammy on 2024-01-22 (8 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  vmlinuz-6.5.0-15-generic allows only one monitor to display on dual
  monitor video card.

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

Bug description:
  My system works fine using vmlinuz-5.15.0-92-generic. When I run
  software update and the new kernel vmlinuz-6.5.0-15-generic is
  installed I no longer have a dual monitor system. This is the second
  time this has happened and I have to return to a prior kernel version
  to get the second monitor to work. I noticed that the prior version is
  using "GRAPHICS: Quadro 2000/PCIe/SSE2" found in the SETTINGS ABOUT
  information and the new kernel is using "GRAPHICS:llvmpipe (LLVM
  15.0.7.256 bits)". Both kernels are using the NVIDIA driver
  metapackage from nvidia-driver-390(proprietary tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 30 14:29:15 2024
  InstallationDate: Installed on 2024-01-21 (8 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2024-01-22 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2051730/+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 2047853] Re: mlxbf_gige: replace SAUCE patch for RX race condition

[Feysel Mohammed]

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

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

Title:
  mlxbf_gige: replace SAUCE patch for RX race condition

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

Bug description:
  SRU Justification:

  [Impact]

  There is a SAUCE patch that addresses a mlxbf-gige RX race condition
 "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
  This SAUCE patch should be reverted and replaced with upstream content.

  [Fix]

  Bring in the following upstream commit from linux-next:
"mlxbf_gige: fix receive packet race condition"

  [Test Case]

  Boot BF3 platform and ensure oob_net0 interface is up and has IP address
  Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls 
occur

  [Regression Potential]

  Low risk change, cherry pick of upstream approved commit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2047853/+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 2051727] [NEW] tcp: Add memory barrier to tcp_push()

[Salvatore]

Public bug reported:

Recently a patch has been accepted on the Linux Kernel regarding the TCP
stack which fix an additional +40ms latency on ARM64 CPU architecture
without impacting other CPU types.

More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/

Would be possible to include the following patch as part of Linux image
on the most recent and LTS maintained Ubuntu versions?


Patch:
```
---
 net/ipv4/tcp.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
index ff6838ca2e58..7bce79beca2b 100644
--- a/net/ipv4/tcp.c
+++ b/net/ipv4/tcp.c
@@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
+   smp_mb__after_atomic();
}
/* It is possible TX completion already happened
 * before we set TSQ_THROTTLED.
-- 
```

** 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/2051727

Title:
  tcp: Add memory barrier to tcp_push()

Status in linux package in Ubuntu:
  New

Bug description:
  Recently a patch has been accepted on the Linux Kernel regarding the
  TCP stack which fix an additional +40ms latency on ARM64 CPU
  architecture without impacting other CPU types.

  More information can be find in here:
  https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/

  Would be possible to include the following patch as part of Linux
  image on the most recent and LTS maintained Ubuntu versions?

  
  Patch:
  ```
  ---
   net/ipv4/tcp.c | 1 +
   1 file changed, 1 insertion(+)

  diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
  index ff6838ca2e58..7bce79beca2b 100644
  --- a/net/ipv4/tcp.c
  +++ b/net/ipv4/tcp.c
  @@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
  + smp_mb__after_atomic();
}
/* It is possible TX completion already happened
 * before we set TSQ_THROTTLED.
  -- 
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U

[Mario Limonciello]

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  DP connection swap to break eDP behavior on AMD 7735U

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Won't Fix
Status in linux-firmware source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Some OEM platforms swap DP connections on the Rembrandt-R, which causes 
improper eDP behavior.  The following issues will occur in these designs:

  - Fn key failed to control brightness
  - eDP remains black screen during S0i3 cycle

  AMD has fixed these issues, but it requires both a kernel patch and an
  updated DMCUB microcode.

  [Test Plan]
  Validate brightness control works.
  Validate that PSR works.
  Validate that eDP works after suspend/resume.
  Validate that external display works.

  Run above test plan on Rembrandt or Rembrandt-R system with swapped DP
  as well as one without swapped DP.

  [Where problems can occur]
  The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R 
systems.  Issues would occur specifically on these designs, which is why they 
should be tested.

  [Other Info]

  Patch:
  
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749

  DMCUB FW:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2051342] Re: Enable lowlatency settings in the generic kernel

[Doug Smythies]

For the Stress-NG 0.16.04: pts/stress-ng-1.11.0 [Test: Socket Activity]
I get:

6633.31 Bogo Ops/s on a 1000Hz kernel. 0.9% improvement.
6572.92 Bogo Ops/s on a 250 Hz kernel.

I did this in a hurry, and will re-test tonight or tomorrow.

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time options.

  Moreover, once these changes are applied we will be able to deprecate
  the lowlatency kernel, saving engineering time and also reducing power
  consumption (required to build the kernel and do all the testing).

  Optionally, we can also provide optimal "lowlatency" settings as a
  user-space 

[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress

[Juerg Haefliger]

Do we need to revert the commits in Mantic as well?

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

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Triaged
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Due to a known silicon limitation, the following sequence is needed while
  initialing the PCIE device on a certain devices with ASMedia chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes from
  suspend.

  [Fix]

  Upstream commits:
  * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
  * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")

  And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
  update board-2.bin") to forfill git history dependency.

  And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
  bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
  has not yet accept the PR for bug 2042534, it has no such problem at this
  moment.

  [Test Case]

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
  Jammy for oem-6.5 included.

  == original bug report ==

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
    - This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
    - The FW is to support new China regulatory support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress

[Juerg Haefliger]

Reopening for Jammy as the bug is not really fixed but the previous
commits reverted and the bot apparently looks at the bug references in
the changes file.

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Released => Triaged

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

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Triaged
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Due to a known silicon limitation, the following sequence is needed while
  initialing the PCIE device on a certain devices with ASMedia chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes from
  suspend.

  [Fix]

  Upstream commits:
  * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
  * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")

  And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
  update board-2.bin") to forfill git history dependency.

  And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
  bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
  has not yet accept the PR for bug 2042534, it has no such problem at this
  moment.

  [Test Case]

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
  Jammy for oem-6.5 included.

  == original bug report ==

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
    - This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
    - The FW is to support new China regulatory support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters

[Andy Gospodarek]

Excellent!

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

Title:
  Update bnxt_en with bug fixes and support for Broadcom 5760X network
  adapters

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [IMPACT]

  This is requested by one of our larger server hardware partners and
  Broadcom to to update the bnxt_en network driver code to add some bug
  fixes and support for the newer 5760X adapters into Mantic.  The goal
  is to have these land in 22.04.4 HWE and the installer environment via
  the HWE kernel.

  Missing these patches will mean customers running this hardware will
  not be able to use it with Ubuntu Server 22.04 LTS until the much
  later 22.04.5 point release, setting up a months-long gap in support
  for these adapters.

  [FIXES]

  These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and
  pick cleanly with the exception of the two noted at the end of this
  section.  For Mantic all are picked. For Noble, only the subset
  currently in linux-next will be picked, depending on what happens in
  our Noble tree during the cycle.

  d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc
  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new
  firmware interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion
  types for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions
  8243345bfaec bnxt_en: Refactor RSS capability fields
  d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism
  on P7 chips
  d3c16475dc06 bnxt_en: Consolidate DB offset calculation
  a432a45bdba4 bnxt_en: Define basic P7 macros
  397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15
  08b386b132c6 bnxt_en: Fix backing store V2 logic
  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2
  firmware calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always
  free bp->ctx
  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings
  required for TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field
  9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters
  5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes
  64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API
  5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic
  94c89e73d377 bnxt_en: refactor speed independent ethtool modes
  d6263677bb1b bnxt_en: support lane configuration via ethtool
  ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode
  fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event
  55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI
  73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices
  c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV 
VLAN"
  cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs
  e76d44fe7227 bnxt_en: 

[Kernel-packages] [Bug 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters

[Jeff Lane ]

https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
the-24-04-noble-numbat-release/41958/2

Once we have a 6.8 kernel available for Noble, test that and then we can
just close this.

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

Title:
  Update bnxt_en with bug fixes and support for Broadcom 5760X network
  adapters

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [IMPACT]

  This is requested by one of our larger server hardware partners and
  Broadcom to to update the bnxt_en network driver code to add some bug
  fixes and support for the newer 5760X adapters into Mantic.  The goal
  is to have these land in 22.04.4 HWE and the installer environment via
  the HWE kernel.

  Missing these patches will mean customers running this hardware will
  not be able to use it with Ubuntu Server 22.04 LTS until the much
  later 22.04.5 point release, setting up a months-long gap in support
  for these adapters.

  [FIXES]

  These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and
  pick cleanly with the exception of the two noted at the end of this
  section.  For Mantic all are picked. For Noble, only the subset
  currently in linux-next will be picked, depending on what happens in
  our Noble tree during the cycle.

  d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc
  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new
  firmware interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion
  types for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions
  8243345bfaec bnxt_en: Refactor RSS capability fields
  d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism
  on P7 chips
  d3c16475dc06 bnxt_en: Consolidate DB offset calculation
  a432a45bdba4 bnxt_en: Define basic P7 macros
  397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15
  08b386b132c6 bnxt_en: Fix backing store V2 logic
  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2
  firmware calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always
  free bp->ctx
  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings
  required for TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field
  9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters
  5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes
  64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API
  5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic
  94c89e73d377 bnxt_en: refactor speed independent ethtool modes
  d6263677bb1b bnxt_en: support lane configuration via ethtool
  ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode
  fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event
  55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI
  73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices
 

[Kernel-packages] [Bug 2046270] Re: Add Support for Broadcom 5760X RoCE adapters to 24.04 (patches in 6.8)

[Jeff Lane ]

https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
the-24-04-noble-numbat-release/41958/2

Once we have a 6.8 kernel available for Noble, test that and then we can
just close this.

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

Title:
  Add Support for Broadcom 5760X RoCE adapters to 24.04 (patches in 6.8)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This request is to add support for the patches for the Broadcom RoCE
  driver included in v6.8 to 24.04.

  The thread where these were posted is here:
  https://lore.kernel.org/all/1701946060-13931-1-git-send-email-
  selvin.xav...@broadcom.com/

  These are the commits from linux-rdma:

  07f830ae4913 RDMA/bnxt_re: Adds MSN table capability for Gen P7 adapters
  cdae3936b2fe RDMA/bnxt_re: Doorbell changes
  6027c20dad1a RDMA/bnxt_re: Get the toggle bits from CQ completions
  880a5dd1880a RDMA/bnxt_re: Update the HW interface definitions
  a62d68581441 RDMA/bnxt_re: Update the BAR offsets
  1801d87b3598 RDMA/bnxt_re: Support new 5760X P7 devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046270/+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 2051342] Re: Enable lowlatency settings in the generic kernel

[Andrea Righi]

@andysem correct, without `nohz_full` specified at boot
CONFIG_NO_HZ_FULL has no effect, except for the little extra overhead
that it's adding to the tick handler (there is still some overhead with
this option enabled, even if it's not used). That's why I'd like to
measure the time spent in some of the tick callbacks (using bpftrace)
with generic vs lowlatency, to have a better understanding of this extra
overhead.

Then, yes, repeating the tests disabling the ticks on some CPUs (booting
with nohz_full) would be another interesting metric.

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time 

[Kernel-packages] [Bug 2051720] Re: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218416.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-01-24T14:29:28+00:00 nickolas wrote:

This issue is still present on kernel 6.7.1 and firmware 20240115. 
Opening a new bug for this as directed in this old bug: 
https://bugzilla.kernel.org/show_bug.cgi?id=215167

$ uname -a
Linux andromeda 6.7.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:14:10 
+ x86_64 GNU/Linux

$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl -b | egrep -i bluetooth
egrep: warning: egrep is obsolescent; using grep -E
Jan 24 00:20:24 andromeda kernel: Bluetooth: Core ver 2.22
Jan 24 00:20:24 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI device and connection manager 
initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: SCO socket layer initialized
Jan 24 00:20:25 andromeda systemd[1]: Reached target Bluetooth Support.
Jan 24 00:20:25 andromeda NetworkManager[790]:   [1706077225.3441] Loaded 
device plugin: NMBluezManager 
(/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: Reading Intel version 
command failed (-110)

Not sure what other logs or info you need, but just let me know if it
would help.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720/comments/0


On 2024-01-30T14:21:11+00:00 nickolas wrote:

This issue is still present in kernel 6.7.2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720/comments/1


On 2024-01-30T17:05:12+00:00 dustin wrote:

I'm also experiencing this issue. It started with kernel 6.5. Bluetooth
has been broken ever since. The issue was not present in earlier
versions of the kernel.

```
$ uname -a

Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```

```
$ lsusb | grep -i bluetooth

Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
```

```
$ journalctl -b | egrep -i bluetooth

Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
```

```
linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

** Bug watch added: Linux Kernel Bug Tracker #215167
   https://bugzilla.kernel.org/show_bug.cgi?id=215167

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

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

Bug description:
  ```
  kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  ```

  This issue started with kernel 6.5. Bluetooth has been broken ever
  since. The issue was not present in earlier versions of the kernel.

  ```
  $ uname -a

  Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth

  Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  ```

  ```
  $ journalctl -b | egrep -i bluetooth

  Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
  Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
  Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
  ```

  ```
  linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2051720/+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 2051721] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1: bcmwl kernel module failed to build

[Gregory Mitchell]

Public bug reported:

Installing some python packages (numpy, matplotlib, pandas) and this
occurred.  New Ubuntu install on pretty old laptop (Dell Latitude E6420)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
DKMSKernelVersion: 6.5.0-15-generic
Date: Tue Jan 30 06:16:31 2024
InstallationDate: Installed on 2024-01-29 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageVersion: 6.30.223.271+bdcom-0ubuntu10~22.04.1
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1: bcmwl kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Installing some python packages (numpy, matplotlib, pandas) and this
  occurred.  New Ubuntu install on pretty old laptop (Dell Latitude
  E6420)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  DKMSKernelVersion: 6.5.0-15-generic
  Date: Tue Jan 30 06:16:31 2024
  InstallationDate: Installed on 2024-01-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu10~22.04.1
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2051721/+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 2051720] [NEW] Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

[Dustin Falgout]

Public bug reported:

```
kernel: Bluetooth: hci0: command 0xfc05 tx timeout
```

This issue started with kernel 6.5. Bluetooth has been broken ever
since. The issue was not present in earlier versions of the kernel.

```
$ uname -a

Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```

```
$ lsusb | grep -i bluetooth

Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
```

```
$ journalctl -b | egrep -i bluetooth

Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
```

```
linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
```

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


** Tags: hw-specific

** Bug watch added: Linux Kernel Bug Tracker #218416
   https://bugzilla.kernel.org/show_bug.cgi?id=218416

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=218416
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  ```
  kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  ```

  This issue started with kernel 6.5. Bluetooth has been broken ever
  since. The issue was not present in earlier versions of the kernel.

  ```
  $ uname -a

  Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth

  Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  ```

  ```
  $ journalctl -b | egrep -i bluetooth

  Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
  Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
  Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
  ```

  ```
  linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2051720/+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 2006557] Re: Enable rdma-sniffer for libpcap

[Chris Moore]

This is functionality is going to be important for our customers.  RDMA
/ RoCE are used extensively in our clusters, and we're going to run into
more cases where people need to be able to trace the RDMA traffic.
There are other tools in Ubuntu to manage OFED devices and RDMA, so RDMA
support is there in general, but this one piece is missing.  In short,
tcpdump is intended to capture a variety of traffic protocols, and RDMA
is one of those protocols which is seeing increased use.

Apparently Fedora has already created an RDMA enabled libpcap.  A
container based on fedora:latest is able to capture RDMA traffic with
tcpdump.  Is there maybe something there that could be leveraged?

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

Title:
  Enable rdma-sniffer for libpcap

Status in libpcap package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Invalid
Status in libpcap package in Debian:
  Won't Fix

Bug description:
  Hi,

  The request is to build and configure stock package libpcap with rdma-sniffer 
enabled.
  We'd like users of rdma devices to be able to sniff on them using stock 
tcpdump.
  Currently when using default tcpdump It does not list rdma devices.

  $ tcpdump -D |grep -i rdma
  $ 

  when using locally build tcpdump (with rdma enabled)
  $ cd 
  $ ./tcpdump -D |grep -i rdma
  24.rocep4s0 (RDMA sniffer)
  25.rocep7s0f0 (RDMA sniffer)
  26.rocep7s0f1 (RDMA sniffer)
  27.rocep10s0f0 (RDMA sniffer)
  28.rocep10s0f1 (RDMA sniffer)
  29.rocep33s0f0 (RDMA sniffer)
  30.rocep33s0f1 (RDMA sniffer)
  31.rocep36s0f0 (RDMA sniffer)
  32.ibp36s0f1 (RDMA sniffer)

  Locally build steps:
  clone sources:
  $ mkdir tcpdumpbuild
  $ cd tcpdumpbuild/
  $ git clone https://github.com/the-tcpdump-group/tcpdump.git
  $ git clone https://github.com/the-tcpdump-group/libpcap.git

  install required packages (including rdma packages so libpcap is built with 
rdma enabled):
  $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils
  configure and build
  $ cd libpcap
  $ ./autogen.sh 
  $ ./configure --enable-rdma=yes
  $ make 
  cd ../tcpdump/
  ./autogen.sh 
  ./configure 
  $ make

  now ./tcpdump -D can show rdma devices.

  Thanks !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2006557/+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 1613393] Re: Provide linux-perf package

[Kleber Sacilotto de Souza]

The request from comment#3 is being handled separately via bug 2051560.

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

Title:
  Provide linux-perf package

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Debian renamed their linux-tools package to linux-perf a year ago.

  
https://anonscm.debian.org/cgit/kernel/linux.git/commit/debian/changelog?id=c2faa8

  The Debian package perf-tools-unstable followed the new name so I had
  to upload an Ubuntu version to revert that change. It would be nice if
  we didn't have to maintain that difference in Ubuntu.

  https://bugs.debian.org/795090

  https://launchpad.net/ubuntu/+source/perf-tools-
  unstable/0.0.1~20160212+git0c13e83-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393/+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 2051700] Re: Missing fuse backport: "fuse: add feature flag for expire-only"

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Missing fuse backport: "fuse: add feature flag for expire-only"

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

Bug description:
  Hello,

  I just noticed that the backport of this patch was not done for
  linux-6.2 and linux-6.3, I guess because there had been a merge
  conflict. I think in the mean time these versions are not maintained
  anymore, so sending a version that fixes the merge conflict is
  probably not going to help.

  Issue is that libfuse currently uses a version check instead of
  testing for the corresponding feature, which is troublesome with any
  kind of feature back port. I.e., if the feature back port increases
  the version number, it would enable the "FUSE_EXPIRE_ONLY" although
  possibly not back ported. If the back port does not increase the
  version number, it might be used by libfuse...

  commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
  Author: Miklos Szeredi 
  Date:   Mon Mar 27 16:14:49 2023 +0200

  fuse: add feature flag for expire-only
  
  Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
  FUSE_NOTIFY_INVAL_ENTRY is effective.
  
  This is needed for backports of this feature, otherwise the server could
  just check the protocol version.
  
  Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to 
FUSE_NOTIFY_INVAL_ENTRY")
  Cc:  # v6.2
  Signed-off-by: Miklos Szeredi 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+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 2051342] Re: Enable lowlatency settings in the generic kernel

[Lastique]

I couldn't find this in the benchmark description on Phoronix, so I'm
assuming the lowlatency kernel was booted with default parameters. Which
means CONFIG_NO_HZ_FULL basically had no effect. This is probably fair
for most users who won't specify `nohz_full` kernel parameter and will
observe the performance difference between generic and lowlatency as
shown by Phoronix tests.

But the claim in this ticket is that `nohz_full` can potentially win
back some performance losses caused by CONFIG_HZ=1000. It would be
useful if testing could confirm or disprove that. Ideally, Phoronix Test
Suite would need to be run on generic, lowlatency without any extra
kernel parameters and lowlatency with `nohz_full` parameter.

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a 

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

[Dimitri John Ledkov]

** Description changed:

  [ Impact ]
  
-  * Multiple data corruption issues have been identified and fixed in
+  * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables to
  possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.
  
-  * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
+  * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).
  
+  * In the absence of the upgrade a cherry-pick will address this
+ particular popular issue alone - without addressing other issues w.r.t.
+ Redbleed / SLS, bugfixes around trim support, and other related
+ improvements that were discovered and fixed around the same time as this
+ popular issue.
+ 
  [ Test Plan ]
  
-  * !!! Danger !!! use reproducer from
+  * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and
  confirm if that issue is resolved or not. Do not run on production ZFS
  pools / systems.
  
-  * autopkgtest pass (from https://ubuntu-archive-
+  * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )
  
-  * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
+  * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
  
-  * kernel regression zfs testsuite pass (from Kernel team RT test
+  * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)
  
-  * zsys integration test pass (upgrade of zsys installed systems for all
+  * zsys integration test pass (upgrade of zsys installed systems for all
  releases)
  
-  * zsys install test pass (for daily images of LTS releases only that
+  * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)
  
-  * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
+  * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)
- 
  
  [ Where problems could occur ]
  
-  * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
-  
-  * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.
+  * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
+ introduce slight slow down on amd64 (for hw accelerated assembly code-
+ paths only in the encryption primitives)
+ 
+  * Uncertain of the perfomance impact of the extra checks in dnat patch
+ fix itself. Possibly affecting speed of operation, at the benefit of
+ correctness.
  
  [ Other Info ]
-  
-  * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs
+ 
+  * https://github.com/openzfs/zfs/pull/15571 is most current
+ consideration of affairs

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

Title:
  Multiple data corruption issues in zfs

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

Bug description:
  [ Impact ]

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

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

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

  [ 

[Kernel-packages] [Bug 2031492] Re: zfs-dkms: support Linux 6.5

[Dimitri John Ledkov]

** Changed in: zfs-linux (Ubuntu Mantic)
   Status: New => Fix Released

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

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

Title:
  zfs-dkms: support Linux 6.5

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  zfs-dkms fails to build with the latest 6.5 kernel in Mantic:

  
  configure: error: 
*** None of the expected "bops->release()" interfaces were detected.
*** This may be because your kernel version is newer than what is
*** supported, or you are using a patched custom kernel with
*** incompatible modifications.
***
*** ZFS Version: zfs-2.2.0~rc1-0ubuntu2
*** Compatible Kernels: 3.10 - 6.3

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  Upstream zfs can now be compiled with kernel 6.5, cherry pick the
  minimum subset of patches to support the new kernel ABI.

  [Regression potential]

  We may experience filesystem regressions or potentially kernel crashes
  with kernels >= 6.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: zfs-dkms 2.2.0~rc1-0ubuntu2
  ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0-rc6
  Uname: Linux 6.5.0-4-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230801
  CloudSubPlatform: config-disk (/dev/vdb)
  Date: Wed Aug 16 07:45:37 2023
  PackageArchitecture: all
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2031492/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040

[You-Sheng Yang]

** Description changed:

+ [SRU Justification]
+ 
+ BugLink: https://bugs.launchpad.net/bugs/2049220
+ 
+ [Impact]
+ 
+ MT7921 - IPv6 no longer working (Not receiving Multicast).
+ 
+ [Fix]
+ 
+ Update WiFi/Bluetooth firmware to upstream commits:
+ * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi 
device")
+ * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for 
mediatek bluetooth chip (MT7921)")
+ 
+ [Test Case]
+ 
+ 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter
+ and connect it to a Dual-stack network leveraging Router Advertisements
+ for IPv6.
+ 
+ 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the 
following:
+- IPv6 stateless autoconfiguration works and a public/global address is 
assigned.
+- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
+ 
+ 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the 
following:
+- IPv6 only configures link-local address (fe80::) and no public/global 
address.
+- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
+ 
+ [Where problems could occur]
+ 
+ Opaque binary. No known dependency to kernel version.
+ 
+ [Other Info]
+ 
+ Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
+ Mantic. All the commits are in upstream repository, so Noble should have
+ them after rebased.
+ 
+ == original bug report ==
+ 
  The current firmware for MT7921 WiFi is giving me problems like dropping 
multicast packets (mDNS).
  I manually updated the firmware files and that fixed the issue.
  To be more specific, please include this commit:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
  And possibly also this:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
  Thanks!
  
  We also need:
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04.3 LTS
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  linux-firmware 20220329.git681281e4-0ubuntu3.24 all  Firmware for 
Linux kernel drivers
  
  3) What you expected to happen
  WiFi working
  
  4) What happened instead
  Multicast packets dropped, mDNS not working

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

Title:
  Update firmware for MT7921 in order to fix Framework 13 AMD 7040

Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-firmware source package in Noble:
  Triaged

Bug description:
  [SRU Justification]

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

  [Impact]

  MT7921 - IPv6 no longer working (Not receiving Multicast).

  [Fix]

  Update WiFi/Bluetooth firmware to upstream commits:
  * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi 
device")
  * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for 
mediatek bluetooth chip (MT7921)")

  [Test Case]

  1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
  adapter and connect it to a Dual-stack network leveraging Router
  Advertisements for IPv6.

  2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the 
following:
 - IPv6 stateless autoconfiguration works and a public/global address is 
assigned.
 - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.

  3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the 
following:
 - IPv6 only configures link-local address (fe80::) and no public/global 
address.
 - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.

  [Where problems could occur]

  Opaque binary. No known dependency to kernel version.

  [Other Info]

  Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
  Mantic. All the commits are in upstream repository, so Noble should
  have them after rebased.

  == original bug report ==

  The current firmware for MT7921 WiFi is giving me problems like dropping 
multicast packets (mDNS).
  I manually updated the firmware files and that fixed the issue.
  To be more specific, please include this commit:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
  And possibly also this:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
  Thanks!

  We also need:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04.3 LTS

  2) The version of the package you are using, via 'apt-cache 

[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel

[Andrea Righi]

@colin-king noticed, I just left a thank you message in the article.
I'll still do the tests, but it's nice to see that someone else is
contributing to this!

Another thing that I'd like to measure is to bpftrace the time spent in
the tick handler before and after these changes applied, because we call
the tick handler more often with HZ=1000, so it'd be nice to see how
much is the distribution of such overhead.

And another cool thing that I've been told is that HZ=1000 can actually
help in terms of power consumption, because apparently the CPUs have
more chances to enter the idle states more quickly. This is also
something that I'd like to measure.

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, 

[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040

[You-Sheng Yang]

SRU:
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/9 (jammy)
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/10 (mantic)

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

Title:
  Update firmware for MT7921 in order to fix Framework 13 AMD 7040

Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-firmware source package in Noble:
  Triaged

Bug description:
  The current firmware for MT7921 WiFi is giving me problems like dropping 
multicast packets (mDNS).
  I manually updated the firmware files and that fixed the issue.
  To be more specific, please include this commit:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
  And possibly also this:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
  Thanks!

  We also need:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04.3 LTS

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  linux-firmware 20220329.git681281e4-0ubuntu3.24 all  Firmware for 
Linux kernel drivers

  3) What you expected to happen
  WiFi working

  4) What happened instead
  Multicast packets dropped, mDNS not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Nick Rosbrook]

AFAIK, the systemd-fsckd patch is still required, but we have vague
plans to get rid of it by making plymouth learn this functionality (i.e.
reading /run/systemd/fsck.progress directly). I have no idea about the
re-ordering, but it would be easy to test with a drop-in config.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051342] Re: Enable lowlatency settings in the generic kernel

[Colin Ian King]

Looks like Michael Larabel has done some analysis for you already :-)
https://www.phoronix.com/news/Ubuntu-Generic-LL-Kernel

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time options.

  Moreover, once these changes are applied we will be able to deprecate
  the lowlatency kernel, saving engineering time and also reducing power
  consumption (required to build the kernel and do all the testing).

  Optionally, we can also provide optimal "lowlatency" settings as a
  user-space package that would set the proper options in the kernel
  boot command line (GRUB, or similar).

  [Test case]

  

[Kernel-packages] [Bug 2051705] Re: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  I am unable to turn on my Bluetooth so I unable to connect to my mouse
  and earbuds to laptops

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   bluez:amd64: Install
   python3-gi-cairo:amd64: Install
   blueman:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 30 20:30:22 2024
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-07-28 (186 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   115  Done2024-01-30T20:08:13+05:30  2024-01-30T20:09:04+05:30  Install 
"bluez" snap
  SourcePackage: bluez
  Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
  dmi.bios.date: 06/13/2018
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 20:16:B9:30:5F:51  ACL MTU: 1021:5  SCO MTU: 96:6
DOWN 
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051705/+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 2051705] [NEW] package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

[Sachin]

Public bug reported:

I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
 bluez:amd64: Install
 python3-gi-cairo:amd64: Install
 blueman:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 30 20:30:22 2024
ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2023-07-28 (186 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SnapChanges:
 ID   Status  Spawn  Ready  Summary
 115  Done2024-01-30T20:08:13+05:30  2024-01-30T20:09:04+05:30  Install 
"bluez" snap
SourcePackage: bluez
Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
dmi.bios.date: 06/13/2018
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: 8TCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IKB
dmi.ec.firmware.release: 1.44
dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
dmi.product.family: ideapad 330-15IKB
dmi.product.name: 81DE
dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
dmi.product.version: Lenovo ideapad 330-15IKB
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 20:16:B9:30:5F:51  ACL MTU: 1021:5  SCO MTU: 96:6
DOWN 
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0

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


** Tags: amd64 apport-package mantic

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

Title:
  package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  I am unable to turn on my Bluetooth so I unable to connect to my mouse
  and earbuds to laptops

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   bluez:amd64: Install
   python3-gi-cairo:amd64: Install
   blueman:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 30 20:30:22 2024
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-07-28 (186 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   115  Done2024-01-30T20:08:13+05:30  

[Kernel-packages] [Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

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

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

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

Title:
  Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4
  Ubuntu 20.04 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  We in the Canonical Public Cloud team have received report from our
  colleagues in Google regarding a potential performance regression with
  the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were
  performed using the linux-gkeop and linux-gkeop-5.15 kernels.

  I have verified with the generic Ubuntu 20.04 5.4 linux-generic and
  the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels.

  The tests were run using `fio`

  fio commands:

  * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`
  * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`

  
  My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the 
results are below:

  Using 5.4 kernel

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.4.0-164-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] 
  fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov  2 09:15:22 2023
write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets
  slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61
  clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38
   lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80
  clat percentiles (usec):
   |  1.00th=[  775],  5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024],
   | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261],
   | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932],
   | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676],
   | 99.99th=[32113]
 bw (  MiB/s): min=  524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, 
samples=4232
 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, 
samples=4232
lat (nsec)   : 500=0.01%, 750=0.01%, 1000=0.01%
lat (usec)   : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01%
lat (usec)   : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93%
lat (msec)   : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07%
lat (msec)   : 100=0.01%
cpu  : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103
IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
   submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.0%
   complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.1%
   issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0
   latency   : target=0, window=0, percentile=100.00%, depth=128

  Run status group 0 (all jobs):
WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), 
io=320GiB (344GB), run=264837-264837msec

  Disk stats (read/write):
sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, 
util=100.00%
  ```

  
  After upgrading to linux-generic-hwe-20.04 kernel and rebooting

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.15.0-88-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s]
  fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov  2 09:46:49 2023
write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets
  slat (nsec): min=660, max=325426k, 

[Kernel-packages] [Bug 2043542] Update Released

[Timo Aaltonen]

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

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

Title:
  Support Mediatek MT7925 WiFi/BT

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

Bug description:
  [kernel SRU Justification]

  [Impact]

  Mediatek MT7925 WiFi/Bluetooth not supported yet.

  [Fix]

  For WiFi, there are tons of patches to be backported from upstream
  kernel v6.7 due to a massive refactoring was done to integrate
  multiple mt79xx drivers into one before landing support for mt7925.
  While these changes, mostly clean cherry-picks, are tied to each
  other, and separating them may cause more efforts in the future, a
  huge patchset of total number 144 is proposed.

  For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
  support Mediatek MT7925") is required.

  [Test Case]

  Initial hardware support. One should be able to find WiFi/BT
  interfaces up available along with proposed kernels.

  [Where problems could occur]

  Features for MT7925 are not all available at this moment, and expect
  more fixes for every corner case.

  [Other Info]

  MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
  Nominate for Jammy and Noble.

  

  [linux-firmware SRU Justification]

  [Impact]

  Missing firmware for Mediatek MT7925 WiFi/BT.

  [Fix]

  Upstream firmware commits:
  - WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
  - Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek 
bluetooth
    chip (MT7925)")

  [Test Case]

  Initial hardware support. One should be able to find WiFi/BT interfaces up
  available along with proposed kernels.

  [Where problems could occur]

  Features for MT7925 are not all available at this moment, and expect more 
fixes
  for every corner case.

  [Other Info]

  MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
  for Jammy and Noble.

  == original bug report ==

  * WiFi
    - kernel: 
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
  * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
  * 3c1199134874 wifi: mt76: connac: add more unified command IDs
  * 473f26fb167e wifi: mt76: connac: add data field in struct tlv
  * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
  * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
  * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
  * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
  * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
    - firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
  * Bluetooth
    - kernel: 
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
    - firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26

---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: Update list of known files
  * Revert "WCN6856 Wi-FI Unavailable and no function during suspend stress 
(LP: #2048977)"
- Revert "ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.25) jammy; urgency=medium

  * Dell dock station WD22TB4 loses ether dev after reboot/power off (LP: 
#2048747)
- rtl_nic: update firmware of USB devices
  * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start 
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core81-65 release
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
  * Support Mediatek MT7925 WiFi/BT (LP: #2043542)
- linux-firmware: add firmware for MT7925
- linux-firmware: add firmware for mediatek bluetooth chip (MT7925)
  * upstream Intel VSC firmware paths moved to intel/vsc/ (LP: #2048991)
- intel: vsc: Add firmware for Visual Sensing Controller
- SAUCE: intel: vsc: use upstream binaries

 -- Juerg Haefliger   Tue, 30 Jan 2024
11:04:32 +0100

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048747

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26

---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: Update list of known files
  * Revert "WCN6856 Wi-FI Unavailable and no function during suspend stress 
(LP: #2048977)"
- Revert "ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.25) jammy; urgency=medium

  * Dell dock station WD22TB4 loses ether dev after reboot/power off (LP: 
#2048747)
- rtl_nic: update firmware of USB devices
  * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start 
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core81-65 release
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
  * Support Mediatek MT7925 WiFi/BT (LP: #2043542)
- linux-firmware: add firmware for MT7925
- linux-firmware: add firmware for mediatek bluetooth chip (MT7925)
  * upstream Intel VSC firmware paths moved to intel/vsc/ (LP: #2048991)
- intel: vsc: Add firmware for Visual Sensing Controller
- SAUCE: intel: vsc: use upstream binaries

 -- Juerg Haefliger   Tue, 30 Jan 2024
11:04:32 +0100

** Changed in: linux-firmware (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.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542

Title:
  Support Mediatek MT7925 WiFi/BT

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

Bug description:
  [kernel SRU Justification]

  [Impact]

  Mediatek MT7925 WiFi/Bluetooth not supported yet.

  [Fix]

  For WiFi, there are tons of patches to be backported from upstream
  kernel v6.7 due to a massive refactoring was done to integrate
  multiple mt79xx drivers into one before landing support for mt7925.
  While these changes, mostly clean cherry-picks, are tied to each
  other, and separating them may cause more efforts in the future, a
  huge patchset of total number 144 is proposed.

  For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
  support Mediatek MT7925") is required.

  [Test Case]

  Initial hardware support. One should be able to find WiFi/BT
  interfaces up available along with proposed kernels.

  [Where problems could occur]

  Features for MT7925 are not all available at this moment, and expect
  more fixes for every corner case.

  [Other Info]

  MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
  Nominate for Jammy and Noble.

  

  [linux-firmware SRU Justification]

  [Impact]

  Missing firmware for Mediatek MT7925 WiFi/BT.

  [Fix]

  Upstream firmware commits:
  - WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
  - Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek 
bluetooth
    chip (MT7925)")

  [Test Case]

  Initial hardware support. One should be able to find WiFi/BT interfaces up
  available along with proposed kernels.

  [Where problems could occur]

  Features for MT7925 are not all available at this moment, and expect more 
fixes
  for every corner case.

  [Other Info]

  MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
  for Jammy and Noble.

  == original bug report ==

  * WiFi
    - kernel: 
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
  * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
  * 3c1199134874 wifi: mt76: connac: add more unified command IDs
  * 473f26fb167e wifi: mt76: connac: add data field in struct tlv
  * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
  * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode 

[Kernel-packages] [Bug 2048747] Update Released

[Timo Aaltonen]

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

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

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

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

[Timo Aaltonen]

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

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

Title:
  occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
  start RT ucode: -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Triaged

Bug description:
  [SRU Justification]

  [Impact]

  Within stress reboot tests, iwlwifi may fail to load firmware, triggers 
retries,
  and finally makes wifi operative.

iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0 
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
  ..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).

  [Fix]

  Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for 
core80-165
  release").

  While the iwlwifi firmware updates come with a sequential manner, it pulls a 
few
  more:

  * 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
  * a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
  * f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")

  These contain firmware blob for ucore 84/86, and are not used by
  kernels < v6.7.

  [Test Case]

  Use checkbox reboot stress test case to observe iwlwifi dmesg logs:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects series with kernels that load iwlwifi ucode 83 firmware, namely
  Noble, Mantic, and for oem-6.5, Jammy.

  == original bug report ==

  Within stress reboot tests, iwlwifi may fail to load firmware and
  triggers retry, and finally makes wifi operative.

  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | 
trm_hw_status0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x | 
trm_hw_status1
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE | 
interruptlink1
  ..
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC: 
0x8026934e
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1: 
0x8026934c
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode: 
-110
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).

  Test steps:

  $ checkbox-cli run com.canonical.certification::stress/reboot

  Proposed fix:

  * https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
  firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26

---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: Update list of known files
  * Revert "WCN6856 Wi-FI Unavailable and no function during suspend stress 
(LP: #2048977)"
- Revert "ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.25) jammy; urgency=medium

  * Dell dock station WD22TB4 loses ether dev after reboot/power off (LP: 
#2048747)
- rtl_nic: update firmware of USB devices
  * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start 
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core81-65 release
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
  * Support Mediatek MT7925 WiFi/BT (LP: #2043542)
- linux-firmware: add firmware for MT7925
- linux-firmware: add firmware for mediatek bluetooth chip (MT7925)
  * upstream Intel VSC firmware paths moved to intel/vsc/ (LP: #2048991)
- intel: vsc: Add firmware for Visual Sensing Controller
- SAUCE: intel: vsc: use upstream binaries

 -- Juerg Haefliger   Tue, 30 Jan 2024
11:04:32 +0100

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853

Title:
  occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
  start RT ucode: -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Triaged

Bug description:
  [SRU Justification]

  [Impact]

  Within stress reboot tests, iwlwifi may fail to load firmware, triggers 
retries,
  and finally makes wifi operative.

iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0 
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
  ..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).

  [Fix]

  Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for 
core80-165
  release").

  While the iwlwifi firmware updates come with a sequential manner, it pulls a 
few
  more:

  * 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
  * a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
  * f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")

  These contain firmware blob for ucore 84/86, and are not used by
  kernels < v6.7.

  [Test Case]

  Use checkbox reboot stress test case to observe iwlwifi dmesg logs:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects series with kernels that load iwlwifi ucode 83 firmware, namely
  Noble, Mantic, and for oem-6.5, Jammy.

  == original bug report ==

  Within stress reboot tests, iwlwifi may fail to load firmware and
  triggers retry, and finally makes wifi operative.

  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | 
trm_hw_status0
  Oct 12 

[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26

---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: Update list of known files
  * Revert "WCN6856 Wi-FI Unavailable and no function during suspend stress 
(LP: #2048977)"
- Revert "ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.25) jammy; urgency=medium

  * Dell dock station WD22TB4 loses ether dev after reboot/power off (LP: 
#2048747)
- rtl_nic: update firmware of USB devices
  * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start 
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core81-65 release
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
  * Support Mediatek MT7925 WiFi/BT (LP: #2043542)
- linux-firmware: add firmware for MT7925
- linux-firmware: add firmware for mediatek bluetooth chip (MT7925)
  * upstream Intel VSC firmware paths moved to intel/vsc/ (LP: #2048991)
- intel: vsc: Add firmware for Visual Sensing Controller
- SAUCE: intel: vsc: use upstream binaries

 -- Juerg Haefliger   Tue, 30 Jan 2024
11:04:32 +0100

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Due to a known silicon limitation, the following sequence is needed while
  initialing the PCIE device on a certain devices with ASMedia chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes from
  suspend.

  [Fix]

  Upstream commits:
  * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
  * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")

  And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
  update board-2.bin") to forfill git history dependency.

  And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
  bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
  has not yet accept the PR for bug 2042534, it has no such problem at this
  moment.

  [Test Case]

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
  Jammy for oem-6.5 included.

  == original bug report ==

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
    - This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
    - The FW is to support new China regulatory support.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2048991] Update Released

[Timo Aaltonen]

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

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

Title:
  upstream Intel VSC firmware paths moved to intel/vsc/

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

Bug description:
  [SRU Justification]

  [Impact]

  In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
  char-misc-next targeting v6.8, the VSC firmware paths have been changed to
  intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
  existing Intel IPU6 camera platforms.

  [Fix]

  Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
  Sensing Controller").

  In order to keep backward compatibility for Jammy oem/hwe kernels, an 
additional
  patch adds symlinks for each moved binary.

  [Test Case]

  The binaries are bit-to-bit identical, except for the destination path
  installed. With extra symlinks created, all the IPU6 platforms should keep
  working as usual.

  [Where problems could occur]

  No problem is expected.

  [Other Info]

  We're switching to upstreamed binaries in Jammy and Noble, because they're
  likely to receive furhter updates for both linux-firmware and vsc drivers.

  == original bug report ==

  In upstream commit
  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
  misc.git/commit/?h=char-misc-
  next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
  targeting v6.8, the VSC firmware paths have been changed to intel/vsc
  instead of the original vsc/soc_a1_prod that has been used for all
  existing Intel IPU6 camera platforms.

  The corresponding linux-firmware commit is in
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.26

---
linux-firmware (20220329.git681281e4-0ubuntu3.26) jammy; urgency=medium

  * Miscellaneous Ubuntu changes
- [Workflow] Add initial gitea workflow files
- SAUCE: [Workflow] check_whence.py: Update list of known files
  * Revert "WCN6856 Wi-FI Unavailable and no function during suspend stress 
(LP: #2048977)"
- Revert "ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"
- Revert "ath11k: WCN6855 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.25) jammy; urgency=medium

  * Dell dock station WD22TB4 loses ether dev after reboot/power off (LP: 
#2048747)
- rtl_nic: update firmware of USB devices
  * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start 
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core81-65 release
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
  * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: 
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
  * Support Mediatek MT7925 WiFi/BT (LP: #2043542)
- linux-firmware: add firmware for MT7925
- linux-firmware: add firmware for mediatek bluetooth chip (MT7925)
  * upstream Intel VSC firmware paths moved to intel/vsc/ (LP: #2048991)
- intel: vsc: Add firmware for Visual Sensing Controller
- SAUCE: intel: vsc: use upstream binaries

 -- Juerg Haefliger   Tue, 30 Jan 2024
11:04:32 +0100

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048991

Title:
  upstream Intel VSC firmware paths moved to intel/vsc/

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

Bug description:
  [SRU Justification]

  [Impact]

  In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
  char-misc-next targeting v6.8, the VSC firmware paths have been changed to
  intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
  existing Intel IPU6 camera platforms.

  [Fix]

  Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
  Sensing Controller").

  In order to keep backward compatibility for Jammy oem/hwe kernels, an 
additional
  patch adds symlinks for each moved binary.

  [Test Case]

  The binaries are bit-to-bit identical, except for the destination path
  installed. With extra symlinks created, all the IPU6 platforms should keep
  working as usual.

  [Where problems could occur]

  No problem is expected.

  [Other Info]

  We're switching to upstreamed binaries in Jammy and Noble, because they're
  likely to receive furhter updates for both linux-firmware and vsc drivers.

  == original bug report ==

  In upstream commit
  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
  misc.git/commit/?h=char-misc-
  next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
  targeting v6.8, the VSC firmware paths have been changed to intel/vsc
  instead of the original vsc/soc_a1_prod that has been used for all
  existing Intel IPU6 camera platforms.

  The corresponding linux-firmware commit is in
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Switching status for Noble to In Progress.
Target release for Noble is 6.8 (which includes fix) but it's not out yet, 
status will be changed once 6.8 will be introduced.

** Changed in: linux (Ubuntu Noble)
   Status: Invalid => 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/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config

[Kernel-packages] [Bug 2051410] Re: AMD-GPU, decrease video resolution leads to black screen

[Richard Bartczak]

@Mario Limonciello, thank you for help.

I did try the proposed version.

uname -r
6.5.0-17-generic works.

Obviously, this Bug report 2051410 is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867.

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

Title:
  AMD-GPU, decrease video resolution leads to black screen

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

Bug description:
  Only the highest resolution can be set (1920x1080).
  If the resolution will be set to e.g,: 1280x720, only a black screen will be 
seen.

  Also games, or "Wine" application does not work, former resolution
  settings can not be changed, start the "Wine" application leads also
  to a black screen (rebooting necessary).

  Additionalinformation  Xorg.0.log, resolution modified :

  [  4028.159] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4028.170] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4028.170] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4253.595] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank 
counter
  [  4254.499] (WW) AMDGPU(0): flip queue failed: Invalid argument
  [  4254.499] (WW) AMDGPU(0): Page flip failed: Invalid argument
  [  4254.508] (II) AMDGPU(0): Allocate new frame buffer 1280x720
  [  4254.509] (II) AMDGPU(0):  => pitch 5120 bytes
  [  4254.859] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4254.859] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4254.859] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4255.673] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4255.674] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4255.674] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4256.307] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4256.307] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4256.307] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4256.768] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4256.768] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4256.768] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4274.945] (WW) AMDGPU(0): flip queue failed: Invalid argument
  [  4274.945] (WW) AMDGPU(0): Page flip failed: Invalid argument
  [  4274.969] (II) AMDGPU(0): Allocate new frame buffer 1920x1080
  [  4274.984] (II) AMDGPU(0):  => pitch 7680 bytes
  [  4276.213] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4276.213] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4276.213] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4276.327] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4276.327] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4276.327] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4277.060] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4277.060] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4277.060] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4277.180] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4277.180] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4277.180] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4292.371] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank 
counter
  [  4293.277] (WW) AMDGPU(0): flip queue failed: Invalid argument
  [  4293.277] (WW) AMDGPU(0): Page flip failed: Invalid argument
  [  4293.293] (II) AMDGPU(0): Allocate new frame buffer 1680x1050
  [  4293.294] (II) AMDGPU(0):  => pitch 7168 bytes
  [  4293.642] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4293.642] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4293.642] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4294.332] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4294.332] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4294.332] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  [  4294.416] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685
  [  4294.416] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [  4294.416] (II) AMDGPU(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 
2100  1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
  

[Kernel-packages] [Bug 2051700] Re: Missing fuse backport: "fuse: add feature flag for expire-only"

[Bernd Schubert]

This is a back port of the patch to hwe-6.2-next, conflicts had been in
the section below, as 6.2 does not have FUSE_CREATE_SUPP_GROUP

Initial patch for 6.5
```
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index d66070af145d0..660be31aaabc2 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -1254,7 +1254,8 @@ void fuse_send_init(struct fuse_mount *fm)
FUSE_ABORT_ERROR | FUSE_MAX_PAGES | FUSE_CACHE_SYMLINKS |
FUSE_NO_OPENDIR_SUPPORT | FUSE_EXPLICIT_INVAL_DATA |
FUSE_HANDLE_KILLPRIV_V2 | FUSE_SETXATTR_EXT | FUSE_INIT_EXT |
-   FUSE_SECURITY_CTX | FUSE_CREATE_SUPP_GROUP;
+   FUSE_SECURITY_CTX | FUSE_CREATE_SUPP_GROUP |
+   FUSE_HAS_EXPIRE_ONLY;

```

Back ported version:
```
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 06876afe5ae46..a86270fa2bf5f 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -1255,7 +1255,7 @@ void fuse_send_init(struct fuse_mount *fm)
FUSE_ABORT_ERROR | FUSE_MAX_PAGES | FUSE_CACHE_SYMLINKS |
FUSE_NO_OPENDIR_SUPPORT | FUSE_EXPLICIT_INVAL_DATA |
FUSE_HANDLE_KILLPRIV_V2 | FUSE_SETXATTR_EXT | FUSE_INIT_EXT |
-   FUSE_SECURITY_CTX;
+   FUSE_SECURITY_CTX | FUSE_HAS_EXPIRE_ONLY;
 #ifdef CONFIG_FUSE_DAX
if (fm->fc->dax)
flags |= FUSE_MAP_ALIGNMENT;
```


Right now I didn't try to compile it yet, but could do if needed. 

** Patch added: "FUSE_HAS_EXPIRE_ONLY-feature-flag.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+attachment/5743550/+files/FUSE_HAS_EXPIRE_ONLY-feature-flag.patch

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

Title:
  Missing fuse backport: "fuse: add feature flag for expire-only"

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

Bug description:
  Hello,

  I just noticed that the backport of this patch was not done for
  linux-6.2 and linux-6.3, I guess because there had been a merge
  conflict. I think in the mean time these versions are not maintained
  anymore, so sending a version that fixes the merge conflict is
  probably not going to help.

  Issue is that libfuse currently uses a version check instead of
  testing for the corresponding feature, which is troublesome with any
  kind of feature back port. I.e., if the feature back port increases
  the version number, it would enable the "FUSE_EXPIRE_ONLY" although
  possibly not back ported. If the back port does not increase the
  version number, it might be used by libfuse...

  commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
  Author: Miklos Szeredi 
  Date:   Mon Mar 27 16:14:49 2023 +0200

  fuse: add feature flag for expire-only
  
  Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
  FUSE_NOTIFY_INVAL_ENTRY is effective.
  
  This is needed for backports of this feature, otherwise the server could
  just check the protocol version.
  
  Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to 
FUSE_NOTIFY_INVAL_ENTRY")
  Cc:  # v6.2
  Signed-off-by: Miklos Szeredi 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+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 2051700] [NEW] Missing fuse backport: "fuse: add feature flag for expire-only"

[Bernd Schubert]

Public bug reported:

Hello,

I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is probably
not going to help.

Issue is that libfuse currently uses a version check instead of testing
for the corresponding feature, which is troublesome with any kind of
feature back port. I.e., if the feature back port increases the version
number, it would enable the "FUSE_EXPIRE_ONLY" although possibly not
back ported. If the back port does not increase the version number, it
might be used by libfuse...

commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
Author: Miklos Szeredi 
Date:   Mon Mar 27 16:14:49 2023 +0200

fuse: add feature flag for expire-only

Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
FUSE_NOTIFY_INVAL_ENTRY is effective.

This is needed for backports of this feature, otherwise the server could
just check the protocol version.

Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to 
FUSE_NOTIFY_INVAL_ENTRY")
Cc:  # v6.2
Signed-off-by: Miklos Szeredi 

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

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

Title:
  Missing fuse backport: "fuse: add feature flag for expire-only"

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

Bug description:
  Hello,

  I just noticed that the backport of this patch was not done for
  linux-6.2 and linux-6.3, I guess because there had been a merge
  conflict. I think in the mean time these versions are not maintained
  anymore, so sending a version that fixes the merge conflict is
  probably not going to help.

  Issue is that libfuse currently uses a version check instead of
  testing for the corresponding feature, which is troublesome with any
  kind of feature back port. I.e., if the feature back port increases
  the version number, it would enable the "FUSE_EXPIRE_ONLY" although
  possibly not back ported. If the back port does not increase the
  version number, it might be used by libfuse...

  commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
  Author: Miklos Szeredi 
  Date:   Mon Mar 27 16:14:49 2023 +0200

  fuse: add feature flag for expire-only
  
  Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
  FUSE_NOTIFY_INVAL_ENTRY is effective.
  
  This is needed for backports of this feature, otherwise the server could
  just check the protocol version.
  
  Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to 
FUSE_NOTIFY_INVAL_ENTRY")
  Cc:  # v6.2
  Signed-off-by: Miklos Szeredi 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+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 2043542] Please test proposed package

[Timo Aaltonen]

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.26 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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542

Title:
  Support Mediatek MT7925 WiFi/BT

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

Bug description:
  [kernel SRU Justification]

  [Impact]

  Mediatek MT7925 WiFi/Bluetooth not supported yet.

  [Fix]

  For WiFi, there are tons of patches to be backported from upstream
  kernel v6.7 due to a massive refactoring was done to integrate
  multiple mt79xx drivers into one before landing support for mt7925.
  While these changes, mostly clean cherry-picks, are tied to each
  other, and separating them may cause more efforts in the future, a
  huge patchset of total number 144 is proposed.

  For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
  support Mediatek MT7925") is required.

  [Test Case]

  Initial hardware support. One should be able to find WiFi/BT
  interfaces up available along with proposed kernels.

  [Where problems could occur]

  Features for MT7925 are not all available at this moment, and expect
  more fixes for every corner case.

  [Other Info]

  MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
  Nominate for Jammy and Noble.

  

  [linux-firmware SRU Justification]

  [Impact]

  Missing firmware for Mediatek MT7925 WiFi/BT.

  [Fix]

  Upstream firmware commits:
  - WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
  - Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek 
bluetooth
    chip (MT7925)")

  [Test Case]

  Initial hardware support. One should be able to find WiFi/BT interfaces up
  available along with proposed kernels.

  [Where problems could occur]

  Features for MT7925 are not all available at this moment, and expect more 
fixes
  for every corner case.

  [Other Info]

  MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
  for Jammy and Noble.

  == original bug report ==

  * WiFi
    - kernel: 
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
  * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
  * 3c1199134874 wifi: mt76: connac: add more unified command IDs
  * 473f26fb167e wifi: mt76: connac: add data field in struct tlv
  * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
  * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
  * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
  * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
  * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
    - firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
  * Bluetooth
    - kernel: 
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
    - firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2

To manage notifications about 

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

[Timo Aaltonen]

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.26 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/2048747

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in OEM Priority Project:
  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 Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

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

[Timo Aaltonen]

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.26 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/2048853

Title:
  occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
  start RT ucode: -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Triaged

Bug description:
  [SRU Justification]

  [Impact]

  Within stress reboot tests, iwlwifi may fail to load firmware, triggers 
retries,
  and finally makes wifi operative.

iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0 
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
  ..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).

  [Fix]

  Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for 
core80-165
  release").

  While the iwlwifi firmware updates come with a sequential manner, it pulls a 
few
  more:

  * 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
  * a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
  * f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")

  These contain firmware blob for ucore 84/86, and are not used by
  kernels < v6.7.

  [Test Case]

  Use checkbox reboot stress test case to observe iwlwifi dmesg logs:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects series with kernels that load iwlwifi ucode 83 firmware, namely
  Noble, Mantic, and for oem-6.5, Jammy.

  == original bug report ==

  Within stress reboot tests, iwlwifi may fail to load firmware and
  triggers retry, and finally makes wifi operative.

  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | 
trm_hw_status0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x | 
trm_hw_status1
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE | 
interruptlink1
  ..
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC: 
0x8026934e
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1: 
0x8026934c
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
  Oct 12 

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

[Timo Aaltonen]

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.26 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/2048991

Title:
  upstream Intel VSC firmware paths moved to intel/vsc/

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Noble:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]

  In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
  char-misc-next targeting v6.8, the VSC firmware paths have been changed to
  intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
  existing Intel IPU6 camera platforms.

  [Fix]

  Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
  Sensing Controller").

  In order to keep backward compatibility for Jammy oem/hwe kernels, an 
additional
  patch adds symlinks for each moved binary.

  [Test Case]

  The binaries are bit-to-bit identical, except for the destination path
  installed. With extra symlinks created, all the IPU6 platforms should keep
  working as usual.

  [Where problems could occur]

  No problem is expected.

  [Other Info]

  We're switching to upstreamed binaries in Jammy and Noble, because they're
  likely to receive furhter updates for both linux-firmware and vsc drivers.

  == original bug report ==

  In upstream commit
  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
  misc.git/commit/?h=char-misc-
  next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
  targeting v6.8, the VSC firmware paths have been changed to intel/vsc
  instead of the original vsc/soc_a1_prod that has been used for all
  existing Intel IPU6 camera platforms.

  The corresponding linux-firmware commit is in
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2051470] Re: Finding wifi is unstable in this release

[Russell Harper]

Research on StackOverflow suggested to restrict to just the 2.4GHz band
because they noticed the issues might arise from switching bands. I did
that but still seeing the connections drop randomly.

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

Title:
  Finding wifi is unstable in this release

Status in linux package in Ubuntu:
  New

Bug description:
  After a recent upgrade noticing wifi disconnects randomly, speeds vary
  back and forth from 0.1Mbps to 100Mbps within a few seconds, can be up
  for a few seconds, or a few hours, not predictable.

  This might be some relevant information, but I looked through the
  modules and don't see anything like `rtw_8821ce`, there are `rtw88_*`
  modules which might be relevant, but in any case I can't map these to
  any packages as far as I can tell.

  ```
  Distributor ID: Ubuntu
  Description:Ubuntu 23.10
  Release:23.10
  Codename:   mantic
  ```

  ```
*-network
 description: Wireless interface
 product: Realtek Semiconductor Co., Ltd.
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:b0:24:d4:d7:ea
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=rtw_8821ce 
driverversion=6.5.0-15-generic firmware=N/A ip=192.168.2.52 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11
 resources: irq:33 ioport:e000(size=256) memory:f7c0-f7c0
  ```

  ```
  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b821
  Subsystem: Realtek Semiconductor Co., Ltd. Device b821
  Flags: bus master, fast devsel, latency 0, IRQ 33
  I/O ports at e000 [size=256]
  Memory at f7c0 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [40] Power Management version 3
  Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [70] Express Endpoint, MSI 00
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-c8-21-01
  Capabilities: [158] Latency Tolerance Reporting
  Capabilities: [160] L1 PM Substates
  Capabilities: [170] Precision Time Measurement
  Capabilities: [17c] Vendor Specific Information: ID=0003 Rev=1 
Len=054 
  Kernel driver in use: rtw_8821ce
  Kernel modules: rtw88_8821ce
  ```

  This was the best reference I can find: [WiFi frequently and randomly
  disconnects, rtw_8821ce driver][1], but even though it's in the
  "Newbie Corner" section, I'm not able to follow what they're doing.
  Like "Have you tried connecting with just wpa_supplicant (and a DHCP
  client if needed)?" is way over my skill level.

  

  This is the relevant output from `iwconfig`, I had just rebooted, as
  that sometimes helps for a bit, so the stats might not be
  representative:

  ```
  wlp2s0IEEE 802.11  ESSID:""  
Mode:Managed  Frequency:5.785 GHz  Access Point: 0E:**:**:**:**:0F  
 
Bit Rate=13 Mb/s   Tx-Power=30 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=50/70  Signal level=-60 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:92  Invalid misc:0   Missed beacon:0
  ```

  

  And another output a few minutes later:

  ```
  wlp2s0IEEE 802.11  ESSID:""  
Mode:Managed  Frequency:2.412 GHz  Access Point: 0C:**:**:**:**:0D  
 
Bit Rate=58.5 Mb/s   Tx-Power=30 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=62/70  Signal level=-48 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:9  Invalid misc:1   Missed beacon:0
  ```

  

  And after a few hours, note the speed looks really good, but the
  connection isn't working. I'm running off a hot spot now.

  ```
  wlp2s0IEEE 802.11  ESSID:""  
Mode:Managed  Frequency:5.785 GHz  Access Point: 0E:**:**:**:**:0F  
 
Bit Rate=175.5 Mb/s   Tx-Power=30 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=39/70  Signal level=-71 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:146  Invalid misc:66   Missed beacon:0
  ```

[1]: https://bbs.archlinux.org/viewtopic.php?id=273440

  ProblemType: 

[Kernel-packages] [Bug 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off

[Andy Chi]

** Tags added: originate-from-2045942

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

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in OEM Priority Project:
  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 Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 1908090] Re: Default 192MB crashkernel reservation is never enough (kdump fails on 20.04)

[Dimitri John Ledkov]

** Also affects: kdump-tools (Ubuntu Noble)
   Importance: Medium
   Status: Confirmed

** Also affects: kdump-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: kdump-tools (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: kdump-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Summary changed:

- Default 192MB crashkernel reservation is never enough (kdump fails on 20.04)
+ kdump-gaps: Default 192MB crashkernel reservation is never enough (kdump 
fails on 20.04)

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

Title:
  kdump-gaps: Default 192MB crashkernel reservation is never enough
  (kdump fails on 20.04)

Status in kdump-tools package in Ubuntu:
  Confirmed
Status in kdump-tools source package in Focal:
  New
Status in kdump-tools source package in Jammy:
  New
Status in kdump-tools source package in Mantic:
  New
Status in kdump-tools source package in Noble:
  Confirmed

Bug description:
  When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS,
  everything appears to be in good working order, according to
  "systemctl status kdump-tools" and "kdump-config status". However,
  upon an actual crash, the system hangs, and no crash files are
  produced. I've investigated and have learned that the capture kernel
  does indeed start, but it is unable to unpack the rootfs/initrd, and
  thus fails and hangs.

  [1.070469] Trying to unpack rootfs image as initramfs...
  [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), 
order=0, oom_score_adj=0
  [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic 
#30-Ubuntu 
  [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [1.336396] Call Trace:
  [1.336396]  dump_stack+0x6d/0x9a
  [1.336396]  dump_header+0x4f/0x1eb
  [1.336396]  out_of_memory.part.0.cold+0x39/0x83
  [1.336396]  out_of_memory+0x6d/0xd0
  ...
  [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on 
memory ]---

  
  On this system with 8G of memory, the crash memory as specified on the kernel 
command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now 
kdump works.

  Not sure how the 192M value is chosen, but it does not work. I think
  this used value used to work for 16.04 and maybe 18.04 (I didn't try),
  but is no longer useful for 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1908090/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

You can use the 'fastboot' kernel parameter to bypass the systemd-fsckd
issue. So overall most systems can work around the bug in full using
kernel parameters:

  quiet splash loglevel=2 fastboot

After that I've only encountered one weird laptop that refused to stay
silent (even with loglevel=0).

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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