[Kernel-packages] [Bug 2043542] Re: Support Mediatek MT7925 WiFi/BT

[You-Sheng Yang]

** Description changed:

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

-- 
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:
  Confirmed
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:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  Confirmed
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 

[Kernel-packages] [Bug 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148071.html (jammy)

** Description changed:

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

-- 
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:
  In Progress
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/

[You-Sheng Yang]

For noble, bug 2042074 is still not yet accepted. Mark this as CONFIRMED
at this moment.

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

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

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

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

-- 
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:
  In Progress
Status in linux-firmware source package in Noble:
  Confirmed

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

[You-Sheng Yang]

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

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

-- 
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:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Noble:
  New

Bug description:
  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 2048827] Re: [amdgpu] Mouse cursor theme is grey instead of black

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  [amdgpu] Mouse cursor theme is grey instead of black

Status in Linux:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Triaged

Bug description:
  - this is a fresh install of the latest Ubuntu 24.04

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

  - the strange thing is the cursor looks normal when I boot off the USB
  and then looks grey on first boot

  - even more strange is when I went to screenshot the cursor for this
  bug report, it looked normal in the screenshot

  - For graphics I have AMD 6600XT

  
  - I will try in X11 as well to see if this is a Wayland-only issue

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yaru-theme-gtk 22.04.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 21:57:08 2024
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-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/

[You-Sheng Yang]

** Summary changed:

- upstream Intel VSC firmware paths changed to intel/vsc/
+ upstream Intel VSC firmware paths moved to intel/vsc/

-- 
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:
  New

Bug description:
  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 2048827] Re: [amdgpu] Mouse cursor theme is grey instead of black

[Daniel van Vugt]

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/2803
   Importance: Unknown
   Status: Unknown

** Changed in: linux-hwe-6.2 (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux-hwe-6.2 (Ubuntu)
   Status: New => Triaged

** Tags added: fixed-upstream

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

Title:
  [amdgpu] Mouse cursor theme is grey instead of black

Status in Linux:
  Unknown
Status in linux-hwe-6.2 package in Ubuntu:
  Triaged

Bug description:
  - this is a fresh install of the latest Ubuntu 24.04

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

  - the strange thing is the cursor looks normal when I boot off the USB
  and then looks grey on first boot

  - even more strange is when I went to screenshot the cursor for this
  bug report, it looked normal in the screenshot

  - For graphics I have AMD 6600XT

  
  - I will try in X11 as well to see if this is a Wayland-only issue

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yaru-theme-gtk 22.04.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 21:57:08 2024
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2045992] Re: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot

[Cole Risch]

This affects me too... I run a different GPU, so I will post my DMESG
here as well:

   13.349657] 

[   13.349666] UBSAN: array-index-out-of-bounds in 
/build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4
[   13.349672] index 3 is out of range for type 
'ATOM_Tonga_MCLK_Dependency_Record [1]'

[   13.355130] 

[   13.355135] 

[   13.355138] UBSAN: array-index-out-of-bounds in 
/build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3673:4
[   13.355143] index 7 is out of range for type 
'ATOM_Tonga_SCLK_Dependency_Record [1]'

It is worth noting that I have had performance issues on this GPU since
before the upgrade to 23.10 as well.  One can only hope that maybe
fixing this will cause it to overclock properly while under load?

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

Title:
  Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Apologies if what this post will entail is not the correct way to
  report a bug. This is my first time reporting one for a linux distro,
  and I'm more or less doing so based on information I was told while
  investigating a separate issue related to my audio devices.

  On boot, along with the error I was looking for, I noticed a number of
  UBSan errors pop up. I asked about them in a linux-related discord
  server and their first question was whether the kernel was compiled
  with Clang. Now, because I never mess with the kernel, I told them I
  wasn't sure. That was when they told me that it's a kernel bug that
  invoked undefined behavior and left my kernel in an erroneous state.
  Here are the errors in question:

  [   5.036942] UBSAN: array-index-out-of-bounds in 
/build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4
  [   5.036951] index 2 is out of range for type 
'ATOM_Tonga_MCLK_Dependency_Record [1]'
  [   5.041843] UBSAN: array-index-out-of-bounds in 
/build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [   5.041852] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  Because I'm not 100% sure what all goes into a bug report like this, I
  will be providing the output of lsb_release -rd, hyfetch, and creating
  a list of my system's specs in hopes that it will help provide some
  sort of clarity.

  lsb_release -rd Output:
  ---
  No LSB modules are available.
  Description: Ubuntu 23.10
  Release: 23.10

  Hyfetch Output:
  ---
  OS: Kubuntu 23.10 x86_64
  Kernel: 6.5.0-14-generic
  Uptime: 28 mins
  Packages: 3 (pipx), 4178 (dpkg), 43 (flatpak), 24 (snap)
  Shell: fish 3.6.1 (yes I know it's deprecated but I prefer it over other 
shells)
  Resolution: 1920x1080, 1920x1080
  DE: Plasma 5.27.8 [KF5 5.110.0] [Qt 5.15.10] (x11)
  WM: KWin

  System Specs:
  -
  CPU: AMD Ryzen 5 2600x
  GPU: Sapphire NITRO+ Radeon RX 570
  MOBO: ASUS PRIME B450M-A II
  RAM: TEAMGROUP TUFF Gaming 2x8 GB at 2400 MHz
  PSU: Corsair RM850x (850W PSU)
  SSD: Western Digital Blue 1 TB SSD

  I'll be honest and say I'm not even sure if my system specs are
  required for a bug report like this, but just in case I figured I'd
  provide them anyway, as maybe it's a hardware-specific thing, or
  something specific to my system entirely. I'm not sure though. I also
  went ahead and included an attachment of the photo I took of the error
  itself, maybe it'll help in some way. I'm also unsure if there's a
  package related to this bug, or what that package would be. Sorry.

  As for the last two things stated in the guidelines for reporting a
  bug, what I expected to happen was to see the error about my USB
  device along with some of the general jargon that pops up on boot that
  I typically don't have to worry about. Instead what happened is that
  based on what someone else told me, I found a bug in my kernel,
  although I'm not knowledgeable enough to know if it's a serious bug,
  or something that's really not that big of a deal. I'll leave that one
  up to you guys

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


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

[Kernel-packages] [Bug 2048827] Re: [amdgpu] Mouse cursor theme is grey instead of black

[Chase Clark]

Can confirm the issue is fixed when running 6.6.11

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

Title:
  [amdgpu] Mouse cursor theme is grey instead of black

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

Bug description:
  - this is a fresh install of the latest Ubuntu 24.04

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

  - the strange thing is the cursor looks normal when I boot off the USB
  and then looks grey on first boot

  - even more strange is when I went to screenshot the cursor for this
  bug report, it looked normal in the screenshot

  - For graphics I have AMD 6600XT

  
  - I will try in X11 as well to see if this is a Wayland-only issue

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yaru-theme-gtk 22.04.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 21:57:08 2024
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049086] Re: General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf]

[Launchpad Bug Tracker]

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

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

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

Title:
  General upgrade to 22.04 leads to second monitor not being recognised
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified:
  usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed
  nvidia-dkms-390 package post-installation script subprocess returned
  error exit status 10

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Upgraded using sudo apt upgrade 
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  
  system fails to boot - blank screen - no activity

  recovery mode coaxed system to startup but error happens with nvidia
  drivers

  system has two monitors, one works (DVI) the second (VGA) does not.

  suspect ancient video card (geforce 610) and issues with compatibility

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jan 11 15:20:51 2024
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2022-07-30 (529 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed 
nvidia-dkms-390 package post-installation script subprocess returned error exit 
status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049086/+subscriptions


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

[Kernel-packages] [Bug 2048815] Re: Pull request to address TPM SPI devices

[Ian May]

** Changed in: linux-nvidia-6.5 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Pull request to address TPM SPI devices

Status in linux-nvidia-6.5 package in Ubuntu:
  Fix Committed

Bug description:
  TPM devices may insert wait state on last clock cycle of ADDR phase.
  For SPI controllers that support full-duplex transfers, this can be
  detected using software by reading the MISO line. For SPI controllers
  that only support half-duplex transfers, such as the Tegra QSPI, it is
  not possible to detect the wait signal from software.

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


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

[Kernel-packages] [Bug 2048966] Re: Fix soft lockup triggered by arm_smmu_mm_invalidate_range

[Ian May]

** Changed in: linux-nvidia-6.5 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Fix soft lockup triggered by arm_smmu_mm_invalidate_range

Status in linux-nvidia-6.5 package in Ubuntu:
  Fix Committed

Bug description:
  [Problem]

  When running an SVA case, the following soft lockup is triggered:
  
  watchdog: BUG: soft lockup - CPU#244 stuck for 26s!
  pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
  pc : arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
  lr : arm_smmu_cmdq_issue_cmdlist+0x150/0xa50
  sp : 8000d83ef290
  x29: 8000d83ef290 x28: 3b9aca00 x27: 
  x26: 8000d83ef3c0 x25: da86c0812194a0e8 x24: 
  x23: 0040 x22: 8000d83ef340 x21: c63980c0
  x20: 0001 x19: c6398080 x18: 
  x17:  x16:  x15: 3000b4a3bbb0
  x14: 3000b4a30888 x13: 3000b4a3cf60 x12: 
  x11:  x10:  x9 : c08120e4d6bc
  x8 :  x7 :  x6 : 00048cfa
  x5 :  x4 : 0001 x3 : 000a
  x2 : 8000 x1 :  x0 : 0001
  Call trace:
   arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
   __arm_smmu_tlb_inv_range+0x118/0x254
   arm_smmu_tlb_inv_range_asid+0x6c/0x130
   arm_smmu_mm_invalidate_range+0xa0/0xa4
   __mmu_notifier_invalidate_range_end+0x88/0x120
   unmap_vmas+0x194/0x1e0
   unmap_region+0xb4/0x144
   do_mas_align_munmap+0x290/0x490
   do_mas_munmap+0xbc/0x124
   __vm_munmap+0xa8/0x19c
   __arm64_sys_munmap+0x28/0x50
   invoke_syscall+0x78/0x11c
   el0_svc_common.constprop.0+0x58/0x1c0
   do_el0_svc+0x34/0x60
   el0_svc+0x2c/0xd4
   el0t_64_sync_handler+0x114/0x140
   el0t_64_sync+0x1a4/0x1a8
  

  
  [Fix]

  backport the following upstream stable patch
  d5afb4b47e13161b3f33904d45110f9e6463bad6

  Link:
  https://lore.kernel.org/r/20230920052257.8615-1-nicol...@nvidia.com

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


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

[Kernel-packages] [Bug 2049107] Re: Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

[Michael Hankins]

In case my hardware config is useful:

mhankins@mediabox:~$ inxi -F
System:
  Host: mediabox Kernel: 6.2.0-39-generic x86_64 bits: 64 Console: pty pts/0
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
  Type: Desktop System: Intel product: KBL-R MRD v: 0.1
serial: 
  Mobo: Intel model: MIR1 v: RVP7 serial: 
UEFI: American Megatrends v: 5.12 date: 08/27/2018
CPU:
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache:
L2: 1024 KiB
  Speed (MHz): avg: 1850 min/max: 400/4000 cores: 1: 2000 2: 2000 3: 2000
4: 2000 5: 2000 6: 2000 7: 2000 8: 800
Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
  Display: server: No display server data found. Headless machine?
tty: 80x24 resolution: 2560x1440
  Message: GL data unavailable in console. Try -G --display
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
  Sound Server-1: ALSA v: k6.2.0-39-generic running: yes
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e
  IF: wlp1s0 state: up mac: 14:13:33:8c:7d:85
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:e0:4c:e0:01:2f
  IF-ID-1: br-54cbdf234280 state: up speed: 1 Mbps duplex: unknown
mac: 02:42:38:64:12:9e
  IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown
mac: 02:42:3c:ad:bd:5b
  IF-ID-3: veth103090f state: up speed: 1 Mbps duplex: full
mac: 42:16:28:32:fc:93
  IF-ID-4: veth87768e9 state: up speed: 1 Mbps duplex: full
mac: 0e:41:45:ea:c8:32
  IF-ID-5: vethc256878 state: up speed: 1 Mbps duplex: full
mac: 4e:b7:f2:ba:cb:96
Bluetooth:
  Device-1: IMC Networks Wireless_Device type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: 14:13:33:8C:7D:84 bt-v: 3.0
Drives:
  Local Storage: total: 5.55 TiB used: 2.65 TiB (47.8%)
  ID-1: /dev/nvme0n1 vendor: Silicon Power model: SPCC M.2 PCIe SSD
size: 3.73 TiB
  ID-2: /dev/sda vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB
Partition:
  ID-1: / size: 97.87 GiB used: 21.31 GiB (21.8%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot size: 1.9 GiB used: 410.1 MiB (21.1%) fs: ext4
dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 1.05 GiB used: 6.1 MiB (0.6%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) file: /swap.img
Sensors:
  System Temperatures: cpu: 55.0 C pch: 49.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 231 Uptime: 1h 8m Memory: 15.4 GiB used: 1.32 GiB (8.6%)
  Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.13

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

Title:
  Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

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

Bug description:
  After server boots up, outbound network connectivity over wifi
  interface is okay but inbound is not.  Jellyfin app clients are unable
  to connect to Jellyfin server running on this server.  From my desktop
  PC I cannot ping the ip for the wifi interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Jan 11 22:13:46 2024
  InstallationDate: Installed on 2023-10-29 (74 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-6.5
  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/2049107/+subscriptions


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

[Kernel-packages] [Bug 2049107] [NEW] Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

[Michael Hankins]

Public bug reported:

After server boots up, outbound network connectivity over wifi interface
is okay but inbound is not.  Jellyfin app clients are unable to connect
to Jellyfin server running on this server.  From my desktop PC I cannot
ping the ip for the wifi interface.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Jan 11 22:13:46 2024
InstallationDate: Installed on 2023-10-29 (74 days ago)
InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230810)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

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

Bug description:
  After server boots up, outbound network connectivity over wifi
  interface is okay but inbound is not.  Jellyfin app clients are unable
  to connect to Jellyfin server running on this server.  From my desktop
  PC I cannot ping the ip for the wifi interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Jan 11 22:13:46 2024
  InstallationDate: Installed on 2023-10-29 (74 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-6.5
  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/2049107/+subscriptions


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

[Kernel-packages] [Bug 2048934] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab de

[Johan Ljunggren]

I'm also affected by this. Here's some output from apt:

Building initial module for 6.5.0-14-generic
Error! Bad return status for module build on kernel: 6.5.0-14-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.157/build/make.log for more information.
dpkg: error processing package nvidia-dkms-390 (--configure):
 installed nvidia-dkms-390 package post-installation script subprocess returned 
error exit status 10

Attaching /var/lib/dkms/nvidia/390.157/build/make.log where the
compilation error is clearly seen.

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2048934/+attachment/5738576/+files/make.log

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

Title:
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to
  install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes
  post-installation«-Unterprozess gab den Fehlerwert 10 zurück

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  driver bug while update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 10 21:00:05 2024
  ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2023-04-21 (263 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to 
install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2048934/+subscriptions


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

[Kernel-packages] [Bug 2049097] [NEW] Last nvidia drivers update cause unable to connect external monitor

[Piotr Pszonka]

Public bug reported:

Hi!
I'm new there. First: a lot of thanks for Ubuntu for all involved in this 
project.

Today after /usr/bin/unattended-upgrade my laptop is unable to display on 
external monitor using DisplayPort. External monitor is not visible at all in 
Ubuntu displays settings.
It worked perfectly before todays update.

My setup is:

HP Zbook 17 Gen2
Ubuntu 22.04.3 LTS
Mesa Intel® HD Graphics 4600 (HSW GT2)
uname -r output: 6.5.0-14-generic

Logs from /var/log/apt/history.log.

Start-Date: 2024-01-11  07:47:21
Commandline: /usr/bin/unattended-upgrade
Upgrade: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40~22.04.1, 
6.2.0-39.40~22.04.1+1), linux-modules-nvidia-390-generic-hwe-22.04:amd64 
(6.2.0-39.40~22.04.1, 6.2.0-39.40~22.04.1+1), 
linux-modules-nvidia-390-6.2.0-39-generic:amd64 (6.2.0-39.40~22.04.1, 
6.2.0-39.40~22.04.1+1), linux-objects-nvidia-390-6.2.0-39-generic:amd64 
(6.2.0-39.40~22.04.1, 6.2.0-39.40~22.04.1+1)
End-Date: 2024-01-11  07:47:47

Start-Date: 2024-01-11  07:49:25
Commandline: /usr/bin/unattended-upgrade
Remove: linux-objects-nvidia-390-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-modules-nvidia-390-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1)
End-Date: 2024-01-11  07:49:32

Start-Date: 2024-01-11  07:49:36
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-extra-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-signatures-nvidia-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-modules-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-image-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1)
End-Date: 2024-01-11  07:49:40

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

** Description changed:

  Hi!
  I'm new there. First: a lot of thanks for Ubuntu for all involved in this 
project.
  
- Today after /usr/bin/unattended-upgrade my laptop is unable to display
- on external monitor using DisplayPort. It worked perfectly before todays
- update.
+ Today after /usr/bin/unattended-upgrade my laptop is unable to display on 
external monitor using DisplayPort. External monitor is not visible at all in 
Ubuntu displays settings.
+ It worked perfectly before todays update.
  
  My setup is:
  
  HP Zbook 17 Gen2
  Ubuntu 22.04.3 LTS
  Mesa Intel® HD Graphics 4600 (HSW GT2)
  uname -r output: 6.5.0-14-generic
- 
  
  Logs from /var/log/apt/history.log.
  
  Start-Date: 2024-01-11  07:47:21
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40~22.04.1, 
6.2.0-39.40~22.04.1+1), linux-modules-nvidia-390-generic-hwe-22.04:amd64 
(6.2.0-39.40~22.04.1, 6.2.0-39.40~22.04.1+1), 
linux-modules-nvidia-390-6.2.0-39-generic:amd64 (6.2.0-39.40~22.04.1, 
6.2.0-39.40~22.04.1+1), linux-objects-nvidia-390-6.2.0-39-generic:amd64 
(6.2.0-39.40~22.04.1, 6.2.0-39.40~22.04.1+1)
  End-Date: 2024-01-11  07:47:47
  
  Start-Date: 2024-01-11  07:49:25
  Commandline: /usr/bin/unattended-upgrade
  Remove: linux-objects-nvidia-390-6.2.0-37-generic:amd64 
(6.2.0-37.38~22.04.1), linux-modules-nvidia-390-6.2.0-37-generic:amd64 
(6.2.0-37.38~22.04.1)
  End-Date: 2024-01-11  07:49:32
  
  Start-Date: 2024-01-11  07:49:36
  Commandline: /usr/bin/unattended-upgrade
  Remove: linux-modules-extra-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-signatures-nvidia-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-modules-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1), 
linux-image-6.2.0-37-generic:amd64 (6.2.0-37.38~22.04.1)
  End-Date: 2024-01-11  07:49:40

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

Title:
  Last nvidia drivers update cause unable to connect external monitor

Status in linux-restricted-modules-hwe-6.2 package in Ubuntu:
  New

Bug description:
  Hi!
  I'm new there. First: a lot of thanks for Ubuntu for all involved in this 
project.

  Today after /usr/bin/unattended-upgrade my laptop is unable to display on 
external monitor using DisplayPort. External monitor is not visible at all in 
Ubuntu displays settings.
  It worked perfectly before todays update.

  My setup is:

  HP Zbook 17 Gen2
  Ubuntu 22.04.3 LTS
  Mesa Intel® HD Graphics 4600 (HSW GT2)
  uname -r output: 6.5.0-14-generic

  Logs from /var/log/apt/history.log.

  Start-Date: 2024-01-11  07:47:21
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40~22.04.1, 
6.2.0-39.40~22.04.1+1), linux-modules-nvidia-390-generic-hwe-22.04:amd64 
(6.2.0-39.40~22.04.1, 6.2.0-39.40~22.04.1+1), 
linux-modules-nvidia-390-6.2.0-39-generic:amd64 (6.2.0-39.40~22.04.1, 
6.2.0-39.40~22.04.1+1), linux-objects-nvidia-390-6.2.0-39-generic:amd64 
(6.2.0-39.40~22.04.1, 6.2.0-39.40~22.04.1+1)
  End-Date: 2024-01-11  07:47:47

  Start-Date: 2024-01-11  07:49:25
  Commandline: /usr/bin/unattended-upgrade
  Remove: 

[Kernel-packages] [Bug 2048934] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab de

[Launchpad Bug Tracker]

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

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

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

Title:
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to
  install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes
  post-installation«-Unterprozess gab den Fehlerwert 10 zurück

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  driver bug while update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 10 21:00:05 2024
  ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2023-04-21 (263 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to 
install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2048934/+subscriptions


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

[Kernel-packages] [Bug 2048934] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab de

[Sunit]

I just hit this one on my Dell Optiplex 7010 this morning after an update. 
Probably not matching the kernel, I get the following:
Errors were encountered while processing:
 nvidia-dkms-390
E: Sub-process /usr/bin/dpkg returned an error code (1)
And the following from the make.log:
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:251: 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-gpu-numa.o] Error 1
make[3]: *** Waiting for unfinished jobs
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:251: 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.o] Error 1
cc1: some warnings being treated as errors
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:251: 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-frontend.o] Error 1
make[3]: *** [scripts/Makefile.build:251: 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:2037: 
/var/lib/dkms/nvidia/390.157/build] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'
make: *** [Makefile:81: modules] Error 2

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

Title:
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to
  install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes
  post-installation«-Unterprozess gab den Fehlerwert 10 zurück

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  driver bug while update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 10 21:00:05 2024
  ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2023-04-21 (263 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to 
install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2048934/+subscriptions


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

[Kernel-packages] [Bug 2049092] [NEW] summary of a possible bug fix. I have not seen this bug for some time.

[Jont Allen]

Public bug reported:

Some years ago I had this bug with my Lenovo X1 computers.
The problem was that a left mouse click was received, but then releasing the 
button, the click was not turned off.

I used this program to test the problem:
>> sudo evtest /dev/input/event15 | grep EV_KEY

This will tell you which event to type in. The left mouse key seems to be  8
then I click on left most mouse button.
Nothing happens.

The command should report an error when the mouse-left is released

I just tried to trigger the bug, and it seems to be fixed.
I would suggest setting this bug "CLOSED"
If needed you can contact me at
http://auditorymodels.org

I suspect this was fixed a long time ago, but was never confirmed.
I consider it fixed, and someone who can, should close the bug report.
Version log:
Ubuntu 5.15.0-1045.51-intel-iotg 5.15.126
00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host 
Bridge/DRAM Registers [8086:9a14] (rev 01)
Subsystem: Lenovo 11th Gen Core Processor Host Bridge/DRAM Registers 
[17aa:22d5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: igen6_edac

00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 
[Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-

   MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
Address: fee40004  Data: 0024
Masking:   Pending: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+


Jont Allen Jan 11 2024.

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

Title:
  summary of a possible bug fix.  I have not seen this bug for some
  time.

Status in linux package in Ubuntu:
  New

Bug description:
  Some years ago I had this bug with my Lenovo X1 computers.
  The problem was that a left mouse click was received, but then releasing the 
button, the click was not turned off.

  I used this program to test the problem:
  >> sudo evtest /dev/input/event15 | grep EV_KEY

  This will tell you which event to type in. The left mouse key seems to be  8
  then I click on left most mouse button.
  Nothing happens.

  The command should report an error when the mouse-left is released

  I just tried to trigger the bug, and it seems to be fixed.
  I would suggest setting this bug "CLOSED"
  If needed you can contact me at
  http://auditorymodels.org

  I suspect this was fixed a long time ago, but was never confirmed.
  I consider it fixed, and someone who can, should close the bug report.
  Version log:
  Ubuntu 5.15.0-1045.51-intel-iotg 5.15.126
  00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host 
Bridge/DRAM Registers [8086:9a14] (rev 01)
  Subsystem: Lenovo 11th Gen Core Processor Host 

[Kernel-packages] [Bug 2048966] Re: Fix soft lockup triggered by arm_smmu_mm_invalidate_range

[Ian May]

** Description changed:

+ [Problem]
+ 
  When running an SVA case, the following soft lockup is triggered:
- 
- watchdog: BUG: soft lockup - CPU#244 stuck for 26s!
- pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
- pc : arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
- lr : arm_smmu_cmdq_issue_cmdlist+0x150/0xa50
- sp : 8000d83ef290
- x29: 8000d83ef290 x28: 3b9aca00 x27: 
- x26: 8000d83ef3c0 x25: da86c0812194a0e8 x24: 
- x23: 0040 x22: 8000d83ef340 x21: c63980c0
- x20: 0001 x19: c6398080 x18: 
- x17:  x16:  x15: 3000b4a3bbb0
- x14: 3000b4a30888 x13: 3000b4a3cf60 x12: 
- x11:  x10:  x9 : c08120e4d6bc
- x8 :  x7 :  x6 : 00048cfa
- x5 :  x4 : 0001 x3 : 000a
- x2 : 8000 x1 :  x0 : 0001
- Call trace:
-  arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
-  __arm_smmu_tlb_inv_range+0x118/0x254
-  arm_smmu_tlb_inv_range_asid+0x6c/0x130
-  arm_smmu_mm_invalidate_range+0xa0/0xa4
-  __mmu_notifier_invalidate_range_end+0x88/0x120
-  unmap_vmas+0x194/0x1e0
-  unmap_region+0xb4/0x144
-  do_mas_align_munmap+0x290/0x490
-  do_mas_munmap+0xbc/0x124
-  __vm_munmap+0xa8/0x19c
-  __arm64_sys_munmap+0x28/0x50
-  invoke_syscall+0x78/0x11c
-  el0_svc_common.constprop.0+0x58/0x1c0
-  do_el0_svc+0x34/0x60
-  el0_svc+0x2c/0xd4
-  el0t_64_sync_handler+0x114/0x140
-  el0t_64_sync+0x1a4/0x1a8
- 
+ 
+ watchdog: BUG: soft lockup - CPU#244 stuck for 26s!
+ pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
+ pc : arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
+ lr : arm_smmu_cmdq_issue_cmdlist+0x150/0xa50
+ sp : 8000d83ef290
+ x29: 8000d83ef290 x28: 3b9aca00 x27: 
+ x26: 8000d83ef3c0 x25: da86c0812194a0e8 x24: 
+ x23: 0040 x22: 8000d83ef340 x21: c63980c0
+ x20: 0001 x19: c6398080 x18: 
+ x17:  x16:  x15: 3000b4a3bbb0
+ x14: 3000b4a30888 x13: 3000b4a3cf60 x12: 
+ x11:  x10:  x9 : c08120e4d6bc
+ x8 :  x7 :  x6 : 00048cfa
+ x5 :  x4 : 0001 x3 : 000a
+ x2 : 8000 x1 :  x0 : 0001
+ Call trace:
+  arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
+  __arm_smmu_tlb_inv_range+0x118/0x254
+  arm_smmu_tlb_inv_range_asid+0x6c/0x130
+  arm_smmu_mm_invalidate_range+0xa0/0xa4
+  __mmu_notifier_invalidate_range_end+0x88/0x120
+  unmap_vmas+0x194/0x1e0
+  unmap_region+0xb4/0x144
+  do_mas_align_munmap+0x290/0x490
+  do_mas_munmap+0xbc/0x124
+  __vm_munmap+0xa8/0x19c
+  __arm64_sys_munmap+0x28/0x50
+  invoke_syscall+0x78/0x11c
+  el0_svc_common.constprop.0+0x58/0x1c0
+  do_el0_svc+0x34/0x60
+  el0_svc+0x2c/0xd4
+  el0t_64_sync_handler+0x114/0x140
+  el0t_64_sync+0x1a4/0x1a8
+ 
+ 
+ 
+ [Fix]
+ 
+ backport the following upstream stable patch
+ d5afb4b47e13161b3f33904d45110f9e6463bad6
+ 
+ Link:
+ https://lore.kernel.org/r/20230920052257.8615-1-nicol...@nvidia.com

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

Title:
  Fix soft lockup triggered by arm_smmu_mm_invalidate_range

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

Bug description:
  [Problem]

  When running an SVA case, the following soft lockup is triggered:
  
  watchdog: BUG: soft lockup - CPU#244 stuck for 26s!
  pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
  pc : arm_smmu_cmdq_issue_cmdlist+0x178/0xa50
  lr : arm_smmu_cmdq_issue_cmdlist+0x150/0xa50
  sp : 8000d83ef290
  x29: 8000d83ef290 x28: 3b9aca00 x27: 
  x26: 8000d83ef3c0 x25: da86c0812194a0e8 x24: 
  x23: 0040 x22: 8000d83ef340 x21: c63980c0
  x20: 0001 x19: c6398080 x18: 
  x17:  x16:  x15: 3000b4a3bbb0
  x14: 3000b4a30888 x13: 

[Kernel-packages] [Bug 2043542] Re: Support Mediatek MT7925 WiFi/BT

[You-Sheng Yang]

linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148065.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148066.html (noble)

** Description changed:

+ [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/
+   - 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
+   - 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
+   - firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2

-- 
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:
  Confirmed
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:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  Confirmed
Status in linux-firmware source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

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

[Kernel-packages] [Bug 2043542] Re: Support Mediatek MT7925 WiFi/BT

[You-Sheng Yang]

So far Wifi kernel driver will be ready since v6.7-rc1 (with fixes from
-rc7), and Bluetooth since v6.6. While linux/noble is currently at v6.6,
mark it as confirmed at this moment.

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

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

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Incomplete => In Progress

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
 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/2043542

Title:
  Support Mediatek MT7925 WiFi/BT

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

Bug description:
  [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 2043542] Re: Support Mediatek MT7925 WiFi/BT

[You-Sheng Yang]

Three more fixes available in v6.7-rc4 and -rc7:
* cd607f2cbbbec wifi: mt76: fix crash with WED rx support enabled
* 695bfba7ca781 wifi: mt76: mt7925: fix typo in mt7925_init_he_caps
* 7a934b5cc3f45 wifi: mt76: mt7921: fix 6GHz disabled by the missing default 
CLC config

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

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

-- 
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:
  Confirmed
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:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  Confirmed
Status in linux-firmware source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [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 2043542] Re: Support Mediatek MT7925 WiFi/BT

[You-Sheng Yang]

** Summary changed:

- Add MT7925 WiFi/BT support
+ Support Mediatek MT7925 WiFi/BT

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

Bug description:
  * 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 2049086] [NEW] General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf

[Andrew]

Public bug reported:

Upgraded using sudo apt upgrade 
Description:Ubuntu 22.04.3 LTS
Release:22.04


system fails to boot - blank screen - no activity

recovery mode coaxed system to startup but error happens with nvidia
drivers

system has two monitors, one works (DVI) the second (VGA) does not.

suspect ancient video card (geforce 610) and issues with compatibility

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf]
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 nvidia-kernel-source-390:amd64: Install
 nvidia-kernel-common-390:amd64: Install
 nvidia-dkms-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Jan 11 15:20:51 2024
ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2022-07-30 (529 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: nvidia-graphics-drivers-390
Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed 
nvidia-dkms-390 package post-installation script subprocess returned error exit 
status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  General upgrade to 22.04 leads to second monitor not being recognised
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified:
  usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed
  nvidia-dkms-390 package post-installation script subprocess returned
  error exit status 10

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Upgraded using sudo apt upgrade 
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  
  system fails to boot - blank screen - no activity

  recovery mode coaxed system to startup but error happens with nvidia
  drivers

  system has two monitors, one works (DVI) the second (VGA) does not.

  suspect ancient video card (geforce 610) and issues with compatibility

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jan 11 15:20:51 2024
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2022-07-30 (529 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed 
nvidia-dkms-390 package post-installation script subprocess returned error exit 
status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049086/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-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: Add MT7925 WiFi/BT support

[You-Sheng Yang]

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

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

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

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

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

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

Title:
  Support Mediatek MT7925 WiFi/BT

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Incomplete
Status in linux-firmware source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  * 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 2049022] Re: virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

[vcarceler]

** Summary changed:

- virtualbox-dkms.0.crash VirtualBox DMKS module NOT working
+ virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

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

Title:
  virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  vcarceler@zvezda:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  vcarceler@zvezda:~$

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  vcarceler@zvezda:~$ apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Instalados: 6.5.0.14.14~22.04.7
Candidato:  6.5.0.14.14~22.04.7
Tabla de versión:
   *** 6.5.0.14.14~22.04.7 500
  500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  vcarceler@zvezda:~$

  3) What you expected to happen

  VirtualBox works

  4) What happened instead

  VirtualBox not working

  Building virtualbox module fails. It's not possible to run virtual
  machines with virtualbox.

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[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-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

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

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049084] [NEW] Focal update: v5.4.263 upstream stable release

[Manuel Diewald]

Public bug reported:


SRU Justification

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

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

driver core: Release all resources during unbind before updating device links
RDMA/irdma: Prevent zero-length STAG registration
PCI: keystone: Drop __init from ks_pcie_add_pcie_{ep,port}()
afs: Make error on cell lookup failure consistent with OpenAFS
drm/panel: simple: Fix Innolux G101ICE-L01 bus flags
drm/panel: simple: Fix Innolux G101ICE-L01 timings
ata: pata_isapnp: Add missing error check for devm_ioport_map()
drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP full
HID: core: store the unique system identifier in hid_device
HID: fix HID device resource race between HID core and debugging support
ipv4: Correct/silence an endian warning in __ip_do_redirect
net: usb: ax88179_178a: fix failed operations during ax88179_reset
arm/xen: fix xen_vcpu_info allocation alignment
amd-xgbe: handle corner-case during sfp hotplug
amd-xgbe: handle the corner-case during tx completion
amd-xgbe: propagate the correct speed and duplex status
net: axienet: Fix check for partial TX checksum
afs: Return ENOENT if no cell DNS record can be found
afs: Fix file locking on R/O volumes to operate in local mode
nvmet: remove unnecessary ctrl parameter
nvmet: nul-terminate the NQNs passed in the connect command
MIPS: KVM: Fix a build warning about variable set but not used
ext4: add a new helper to check if es must be kept
ext4: factor out __es_alloc_extent() and __es_free_extent()
ext4: use pre-allocated es in __es_insert_extent()
ext4: use pre-allocated es in __es_remove_extent()
ext4: using nofail preallocation in ext4_es_remove_extent()
ext4: using nofail preallocation in ext4_es_insert_delayed_block()
ext4: using nofail preallocation in ext4_es_insert_extent()
ext4: fix slab-use-after-free in ext4_es_insert_extent()
ext4: make sure allocate pending entry not fail
arm64: cpufeature: Extract capped perfmon fields
KVM: arm64: limit PMU version to PMUv3 for ARMv8.1
ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA
bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce()
s390/dasd: protect device queue against concurrent access
USB: serial: option: add Luat Air72*U series products
hv_netvsc: Fix race of register_netdevice_notifier and VF register
hv_netvsc: Mark VF as slave before exposing it to user-mode
dm-delay: fix a race between delay_presuspend and delay_bio
bcache: check return value from btree_node_alloc_replacement()
bcache: prevent potential division by zero error
USB: serial: option: add Fibocom L7xx modules
USB: serial: option: fix FM101R-GL defines
USB: serial: option: don't claim interface 4 for ZTE MF290
USB: dwc2: write HCINT with INTMASK applied
usb: dwc3: set the dma max_seg_size
USB: dwc3: qcom: fix resource leaks on probe deferral
USB: dwc3: qcom: fix wakeup after probe deferral
io_uring: fix off-by one bvec index
pinctrl: avoid reload of p state in list iteration
firewire: core: fix possible memory leak in create_units()
mmc: block: Do not lose cache flush during CQE error recovery
ALSA: hda: Disable power-save on KONTRON SinglePC
ALSA: hda/realtek: Headset Mic VREF to 100%
ALSA: hda/realtek: Add supported ALC257 for ChromeOS
dm-verity: align struct dm_verity_fec_io properly
dm verity: don't perform FEC for failed readahead IO
bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
powerpc: Don't clobber f0/vs0 during fp|altivec register save
btrfs: fix off-by-one when checking chunk map includes logical address
btrfs: send: ensure send_fd is writable
btrfs: make error messages more clear when getting a chunk map
Input: xpad - add HyperX Clutch Gladiate Support
net: stmmac: xgmac: Disable FPE MMC interrupts
ravb: Fix races between ravb_tx_timeout_work() and net related ops
net: ravb: Use pm_runtime_resume_and_get()
net: ravb: Start TX queues after HW initialization succeeded
smb3: fix touch -h of symlink
s390/mm: fix phys vs virt confusion in mark_kernel_pXd() functions family
s390/cmma: fix detection of DAT pages
mtd: cfi_cmdset_0001: Support the absence of protection registers
mtd: cfi_cmdset_0001: Byte swap OTP info
fbdev: stifb: Make the STI next font pointer a 32-bit signed offset
ima: annotate iint mutex to avoid lockdep false positive warnings
ovl: skip overlayfs superblocks at global sync
ima: detect changes to the backing overlay file
scsi: qla2xxx: Simplify the code for aborting SCSI commands
scsi: core: Introduce the scsi_cmd_to_rq() function
scsi: qla2xxx: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
scsi: 

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

[Lucas Magnien]

Hello, got the same issue with Ubuntu 22.04.3 LTS (GNU/Linux
5.15.0-91-generic x86_64). Also tried 5.19 kernel and got the same
problem.

Jan  7 02:28:26 cache4 systemd[1]: Starting MD array scrubbing...
Jan  7 02:28:26 cache4 root: mdcheck start checking /dev/md0
Jan  7 08:28:44 cache4 kernel: [2914434.326024] md: md0: data-check interrupted.
Jan  7 08:32:08 cache4 kernel: [2914638.397357] INFO: task jbd2/md0-8:1337 
blocked for more than 120 seconds.
Jan  7 08:32:08 cache4 kernel: [2914638.397420]   Not tainted 
5.15.0-91-generic #99-Ubuntu
Jan  7 08:32:08 cache4 kernel: [2914638.397457] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan  7 08:32:08 cache4 kernel: [2914638.397505] task:jbd2/md0-8  state:D 
stack:0 pid: 1337 ppid: 2 flags:0x4000
Jan  7 08:32:08 cache4 kernel: [2914638.397512] Call Trace:
Jan  7 08:32:08 cache4 kernel: [2914638.397515]  
Jan  7 08:32:08 cache4 kernel: [2914638.397520]  __schedule+0x24e/0x590
Jan  7 08:32:08 cache4 kernel: [2914638.397530]  schedule+0x69/0x110
Jan  7 08:32:08 cache4 kernel: [2914638.397535]  
md_write_start.part.0+0x174/0x220
Jan  7 08:32:08 cache4 kernel: [2914638.397540]  ? wait_woken+0x70/0x70
Jan  7 08:32:08 cache4 kernel: [2914638.397547]  md_write_start+0x14/0x30
Jan  7 08:32:08 cache4 kernel: [2914638.397553]  raid5_make_request+0x77/0x540 
[raid456]
Jan  7 08:32:08 cache4 kernel: [2914638.397566]  ? 
jbd2_transaction_committed+0x1b/0x60
Jan  7 08:32:08 cache4 kernel: [2914638.397573]  ? ext4_set_iomap+0x5a/0x1d0
Jan  7 08:32:08 cache4 kernel: [2914638.397579]  ? wait_woken+0x70/0x70
Jan  7 08:32:08 cache4 kernel: [2914638.397584]  md_handle_request+0x12d/0x1b0
Jan  7 08:32:08 cache4 kernel: [2914638.397589]  ? submit_bio_checks+0x1a5/0x560
Jan  7 08:32:08 cache4 kernel: [2914638.397595]  md_submit_bio+0x76/0xc0
Jan  7 08:32:08 cache4 kernel: [2914638.397600]  __submit_bio+0x1a5/0x220
Jan  7 08:32:08 cache4 kernel: [2914638.397603]  ? mempool_alloc_slab+0x17/0x20
Jan  7 08:32:08 cache4 kernel: [2914638.397611]  __submit_bio_noacct+0x85/0x200
Jan  7 08:32:08 cache4 kernel: [2914638.397614]  ? kmem_cache_alloc+0x1ab/0x2f0
Jan  7 08:32:08 cache4 kernel: [2914638.397619]  submit_bio_noacct+0x4e/0x120
Jan  7 08:32:08 cache4 kernel: [2914638.397623]  submit_bio+0x4a/0x130
Jan  7 08:32:08 cache4 kernel: [2914638.397627]  submit_bh_wbc+0x18d/0x1c0
Jan  7 08:32:08 cache4 kernel: [2914638.397632]  submit_bh+0x13/0x20
Jan  7 08:32:08 cache4 kernel: [2914638.397635]  
jbd2_journal_commit_transaction+0x861/0x17a0
Jan  7 08:32:08 cache4 kernel: [2914638.397640]  ? __update_idle_core+0x93/0x120
Jan  7 08:32:08 cache4 kernel: [2914638.397649]  kjournald2+0xa9/0x280
Jan  7 08:32:08 cache4 kernel: [2914638.397653]  ? wait_woken+0x70/0x70
Jan  7 08:32:08 cache4 kernel: [2914638.397657]  ? 
load_superblock.part.0+0xc0/0xc0
Jan  7 08:32:08 cache4 kernel: [2914638.397662]  kthread+0x12a/0x150
Jan  7 08:32:08 cache4 kernel: [2914638.397667]  ? set_kthread_struct+0x50/0x50
Jan  7 08:32:08 cache4 kernel: [2914638.397672]  ret_from_fork+0x22/0x30
Jan  7 08:32:08 cache4 kernel: [2914638.397680]  


# cat /sys/block/md0/md/array_state
write-pending

This is happening on all our servers with NVMe devices.

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] 

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

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148054.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148056.html (lunar)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148057.html 
(mantic)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148058.html (noble)

** Description changed:

+ [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
+   - 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.
+   - The FW is to support new China regulatory support.

-- 
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:
  In Progress
Status in linux-firmware source package in Lunar:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress
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 

[Kernel-packages] [Bug 2049082] [NEW] FIPS kernels should default to fips mode

[Dimitri John Ledkov]

Public bug reported:

[ Impact ]

 * Ubuntu builds regular kernels without FIPS configuration enabled at compile 
time
 * Canonical also builds FIPS kernels with FIPS configuration enabled at 
compile time, intended to only be used in FIPS mode
 * Currently, due to upstream patches, this thus requires additional runtime 
configuration of bootloader to always specify `fips=1` to turn on FIPS mode at 
runtime, as it is off by default
 * This adds additional complexity when performing autopkgtests, creating 
Ubuntu Core images, switching to/from Pro FIPS, drafting and verify security 
policy
 * Instead all of this can be avoided, if fips=1 is the implicit default for 
the FIPS kernels.
 * This has no effect on regular kernels

[ Test Plan ]

 * generic kernel build should have no effect / no changes, as dead code
is patched. I.e. /proc/sys/crypto/fips_enabled not present

 * fips kernel build should have the following content in the 
/proc/sys/crypto/fips_enabled file:
   + without any fips= setting fips_enabled should be set to 1 (new behaviour)
   + with fips=1 setting fips_enabled should be set to 1 (double check existing 
behaviour)
   + with fips=0 setting fips_enabled should be set to 0 (double check existing 
behaviour)

 * pro client can continue to set fips=1, just in case, as older
certified fips kernels still require this setting.

[ Where problems could occur ]

 * Some 3rd party tools do not consult /proc/sys/crypto/fips_enabled and
rely on access to the kernel cmdline "fips=1", they are wrong, but also
there is no current intention to break any such users, as pro client
will continue to set fips=1 for now.

[ Other Info ]
 
 * Intention is to land this for noble; for the future noble fips kernels. FIPS 
Updates kernels, if at all possible.

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


** Tags: fips

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

Title:
  FIPS kernels should default to fips mode

Status in linux package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * Ubuntu builds regular kernels without FIPS configuration enabled at 
compile time
   * Canonical also builds FIPS kernels with FIPS configuration enabled at 
compile time, intended to only be used in FIPS mode
   * Currently, due to upstream patches, this thus requires additional runtime 
configuration of bootloader to always specify `fips=1` to turn on FIPS mode at 
runtime, as it is off by default
   * This adds additional complexity when performing autopkgtests, creating 
Ubuntu Core images, switching to/from Pro FIPS, drafting and verify security 
policy
   * Instead all of this can be avoided, if fips=1 is the implicit default for 
the FIPS kernels.
   * This has no effect on regular kernels

  [ Test Plan ]

   * generic kernel build should have no effect / no changes, as dead
  code is patched. I.e. /proc/sys/crypto/fips_enabled not present

   * fips kernel build should have the following content in the 
/proc/sys/crypto/fips_enabled file:
 + without any fips= setting fips_enabled should be set to 1 (new behaviour)
 + with fips=1 setting fips_enabled should be set to 1 (double check 
existing behaviour)
 + with fips=0 setting fips_enabled should be set to 0 (double check 
existing behaviour)

   * pro client can continue to set fips=1, just in case, as older
  certified fips kernels still require this setting.

  [ Where problems could occur ]

   * Some 3rd party tools do not consult /proc/sys/crypto/fips_enabled
  and rely on access to the kernel cmdline "fips=1", they are wrong, but
  also there is no current intention to break any such users, as pro
  client will continue to set fips=1 for now.

  [ Other Info ]
   
   * Intention is to land this for noble; for the future noble fips kernels. 
FIPS Updates kernels, if at all possible.

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


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

[Kernel-packages] [Bug 2046434] Re: TPM2 Problem in 6.2.0 kernel

[Peter Treman]

It seems to be fixed in the new kernal 6.5.0-14-generic.

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

Title:
  TPM2 Problem in 6.2.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after updating to kernel 6.2.0-39 i`ve got a problem with TPM on variuos 
notebooks or desktops. I`ve got this error
  sudo dmesg |grep tpm
  [0.359797] tpm_tis NTC0702:00: 2.0 TPM (device-id 0xFC, rev-id 1)
  [0.372552] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling 
instead
  I havent this problem on previuos kernael

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


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

[Kernel-packages] [Bug 2048373] Re: Copying big files to a mounted Synology NAS crashes the NAS

[pjotter]

** Description changed:

  Situation:
  
  OS: Xubuntu 22.04.3
  Kernel version: 6.2.0-39-generic
  Network driver: r8169
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller (rev 01)
  NAS model: Synology DiskStation DS223
  
  The problem:
  
- On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted a Synology
+ On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted Synology
  DS223 NAS. It mounts without any problems and at first glance everything
  seems to be working fine, until you start uploading large(r) files
  (200MB+) to the NAS. The NAS will then randomly and for unknown reasons
  crash or halt, causing the Xubuntu OS to halt or crash in turn. It does
  so in any application (Thunar, copying files in bash, tuxcommander etc).
  So, this problem doesn't seem to be application-related. I tried
  mounting the NAS with different/additional mount-options and tried
  several network settings and even checked the physical cables but
  nothing had any effect.
  
  The solution:
  
  Eventually, I managed to trace the problem to my network device and I
  replaced the r8169 driver for the r8168 version. This immediately solved
  my problem. Now, copying from-and-to the mounted NAS works as expected.
  
  Even though my problem is solved by installing the r8168 version of the
  driver, there probably still remains a bug in the default r8169 driver
  that causes this problem with my current setup.
  
  Note: The r8169 driver is integrated in the kernel whereas the r8168
  driver can be installed by installing the r8168-dkms package and
  disabling (blacklisting) the r8169 driver in the 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/2048373

Title:
  Copying big files to a mounted Synology NAS crashes the NAS

Status in linux package in Ubuntu:
  New

Bug description:
  Situation:

  OS: Xubuntu 22.04.3
  Kernel version: 6.2.0-39-generic
  Network driver: r8169
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI 
Express Gigabit Ethernet Controller (rev 01)
  NAS model: Synology DiskStation DS223

  The problem:

  On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted Synology
  DS223 NAS. It mounts without any problems and at first glance
  everything seems to be working fine, until you start uploading
  large(r) files (200MB+) to the NAS. The NAS will then randomly and for
  unknown reasons crash or halt, causing the Xubuntu OS to halt or crash
  in turn. It does so in any application (Thunar, copying files in bash,
  tuxcommander etc). So, this problem doesn't seem to be application-
  related. I tried mounting the NAS with different/additional mount-
  options and tried several network settings and even checked the
  physical cables but nothing had any effect.

  The solution:

  Eventually, I managed to trace the problem to my network device and I
  replaced the r8169 driver for the r8168 version. This immediately
  solved my problem. Now, copying from-and-to the mounted NAS works as
  expected.

  Even though my problem is solved by installing the r8168 version of
  the driver, there probably still remains a bug in the default r8169
  driver that causes this problem with my current setup.

  Note: The r8169 driver is integrated in the kernel whereas the r8168
  driver can be installed by installing the r8168-dkms package and
  disabling (blacklisting) the r8169 driver in the kernel.

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


-- 
Mailing list: https://launchpad.net/~kernel-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] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110

[You-Sheng Yang]

** Description changed:

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

-- 
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:
  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]

  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: 

[Kernel-packages] [Bug 2049069] [NEW] Focal update: v5.4.262 upstream stable release

[Manuel Diewald]

Public bug reported:


SRU Justification

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

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

locking/ww_mutex/test: Fix potential workqueue corruption
perf/core: Bail out early if the request AUX area is out of bound
clocksource/drivers/timer-imx-gpt: Fix potential memory leak
clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware
x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size
wifi: mac80211_hwsim: fix clang-specific fortify warning
wifi: mac80211: don't return unset power in ieee80211_get_tx_power()
wifi: ath9k: fix clang-specific fortify warnings
wifi: ath10k: fix clang-specific fortify warning
net: annotate data-races around sk->sk_tx_queue_mapping
net: annotate data-races around sk->sk_dst_pending_confirm
wifi: ath10k: Don't touch the CE interrupt registers after power up
Bluetooth: Fix double free in hci_conn_cleanup
platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e
drm/komeda: drop all currently held locks if deadlock happens
drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7
drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga
drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL
selftests/efivarfs: create-read: fix a resource leak
crypto: pcrypt - Fix hungtask for PADATA_RESET
RDMA/hfi1: Use FIELD_GET() to extract Link Width
fs/jfs: Add check for negative db_l2nbperpage
fs/jfs: Add validity check for db_maxag and db_agpref
jfs: fix array-index-out-of-bounds in dbFindLeaf
jfs: fix array-index-out-of-bounds in diAlloc
ARM: 9320/1: fix stack depot IRQ stack filter
ALSA: hda: Fix possible null-ptr-deref when assigning a stream
PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields
atm: iphase: Do PCI error checks on own line
scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()
HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W
tty: vcc: Add check for kstrdup() in vcc_probe()
usb: gadget: f_ncm: Always set current gadget in ncm_bind()
i2c: sun6i-p2wi: Prevent potential division by zero
media: gspca: cpia1: shift-out-of-bounds in set_flicker
media: vivid: avoid integer overflow
gfs2: ignore negated quota changes
media: cobalt: Use FIELD_GET() to extract Link Width
drm/amd/display: Avoid NULL dereference of timing generator
kgdb: Flush console before entering kgdb on panic
ASoC: ti: omap-mcbsp: Fix runtime PM underflow warnings
pwm: Fix double shift bug
wifi: iwlwifi: Use FW rate for non-data frames
NFSv4.1: fix SP4_MACH_CRED protection for pnfs IO
ipvlan: add ipvlan_route_v6_outbound() helper
tty: Fix uninit-value access in ppp_sync_receive()
net: hns3: fix variable may not initialized problem in hns3_init_mac_addr()
tipc: Fix kernel-infoleak due to uninitialized TLV value
ppp: limit MRU to 64K
xen/events: fix delayed eoi list handling
ptp: annotate data-race around q->head and q->tail
bonding: stop the device in bond_setup_by_slave()
net: ethernet: cortina: Fix max RX frame define
net: ethernet: cortina: Handle large frames
net: ethernet: cortina: Fix MTU max setting
netfilter: nf_conntrack_bridge: initialize err to 0
net: stmmac: Rework stmmac_rx()
net: stmmac: fix rx budget limit check
net/mlx5_core: Clean driver version and name
net/mlx5e: Check return value of snprintf writing to fw_version buffer for 
representors
macvlan: Don't propagate promisc change to lower dev in passthru
tools/power/turbostat: Fix a knl bug
cifs: spnego: add ';' in HOST_KEY_LEN
media: venus: hfi: add checks to perform sanity on queue pointers
randstruct: Fix gcc-plugin performance mode to stay in group
bpf: Fix precision tracking for BPF_ALU | BPF_TO_BE | BPF_END
scsi: megaraid_sas: Increase register read retry rount from 3 to 30 for 
selected registers
x86/cpu/hygon: Fix the CPU topology evaluation for real
KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
KVM: x86: Ignore MSR_AMD64_TW_CFG access
audit: don't take task_lock() in audit_exe_compare() code path
audit: don't WARN_ON_ONCE(!current->mm) in audit_exe_compare()
hvc/xen: fix error path in xen_hvc_init() to always register frontend driver
PCI/sysfs: Protect driver's D3cold preference from user space
ACPI: resource: Do IRQ override on TongFang GMxXGxx
mmc: meson-gx: Remove setting of CMD_CFG_ERROR
genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware
PCI: keystone: Don't discard .remove() callback
PCI: keystone: Don't discard .probe() callback
parisc/pdc: Add width field to struct pdc_model
clk: qcom: ipq8074: drop the CLK_SET_RATE_PARENT flag from PLL 

[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71

[Simon Quigley]

It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)

After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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

[Kernel-packages] [Bug 2049065] [NEW] netfilter: nf_nat: fix action not being set for all ct states

[Frode Nordahl]

Public bug reported:

Long story short there is a regression that affects the datapath of Open
vSwitch based systems starting with the 6.2 kernel which is fixed by
[0].

0:
https://patchwork.ozlabs.org/project/openvswitch/patch/20231221224311.130319-1-b...@faucet.nz/

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

Title:
  netfilter: nf_nat: fix action not being set for all ct states

Status in linux package in Ubuntu:
  New

Bug description:
  Long story short there is a regression that affects the datapath of
  Open vSwitch based systems starting with the 6.2 kernel which is fixed
  by [0].

  0:
  
https://patchwork.ozlabs.org/project/openvswitch/patch/20231221224311.130319-1-b...@faucet.nz/

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


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

[Kernel-packages] [Bug 2038587] Re: Turning COMPAT_32BIT_TIME off on ppc64el

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  Turning COMPAT_32BIT_TIME off on ppc64el

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This will prevent existing 32-bit powerpcle binaries to operate
  correctly, if they are still using 32bit time. And even exists?

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2038587/+subscriptions


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

[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

[Frank Heimes]

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

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

Title:
  [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * Today no s390x-specific vfio-pci devices (zPCI) can be passed
 from a KVM host to a KVM guest (incl. secure execution guests
 in the context of confidential computing).

   * s390x PCI passthrough needs various changes in the s390x kernel zPCI
 code (incl. the new s390x-specific Kernel config option
 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0
 and got backported to 22.04/jammy as part of LP: #1853306.

   * Lunar an newer Ubuntu releases have the code already included from
 upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the
 config option is not set, hence zPCI pass-through is still not possible.

  [Fix]

   * To be able to make use of VFIO zPCI pass-through on s390x running newer
 Ubuntu releases (especially needed in the context of secure execution)
 the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs
 to be enabled and set to 'y'.

  [Test Case]

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

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

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

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

  [Regression Potential]

   * The regression potential is moderate, since the code is upstream
 for quite a while and already enabled in jammy.

   * The general way on using passthrough has not changed, with this
 change (config option) it's now just possible to passthrough
 zPCI on top.

   * CCW devices are not affected.

   * And this is s390x-specific anyway, so no other architectures are
  affected.

  [Other]

   * The enabling of the kernel config option is exactly the same for L, M
 and U/N, but I submitted separate patches due to slightly different context
 and offsets.
  __

  === Description by mjros...@us.ibm.com  ===

  LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to
  enable enhanced interpretation of PCI passthrough on s390.  It also
  included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which
  is necessary to activate this kernel feature.

  For lunar and mantic, the kernel code did not require backporting due
  to the base kernel version already containing it, but 

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Frank Heimes]

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

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2038587] Re: Turning COMPAT_32BIT_TIME off on ppc64el

[Kleber Sacilotto de Souza]

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

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

Title:
  Turning COMPAT_32BIT_TIME off on ppc64el

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This will prevent existing 32-bit powerpcle binaries to operate
  correctly, if they are still using 32bit time. And even exists?

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2038587/+subscriptions


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

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

[Frank Heimes]

Thx for the hint, klebers - I missed that.
With that I can also set the project entry to Fix Released and close this bug.

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

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 2 0 0 0 0 0 0
   Reqs 18 0 0 0 0 0 0 1
 Extras
   Special socket calls 0
 cork 0
 nodelay 0
 sendpage 0
 splice 0
 urgent data 0

   * Instead of including the payload in the wrong >512 KB buckets,
 the output should be to have 19 reqs in the 8 KB buckets for TX stats
 and 9 reqs in the 8 KB bucket for RX stats.

  [Where problems could occur]

   * The changes are in common code /net/smc/smc_stats.h
 hence any potential negativ impact is not limited to a specific platform.
 but limited to statistics for shared memory communication (SMC)
 hardware statistics.

   * But limited to the 

[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

[Kleber Sacilotto de Souza]

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

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

Title:
  [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * Today no s390x-specific vfio-pci devices (zPCI) can be passed
 from a KVM host to a KVM guest (incl. secure execution guests
 in the context of confidential computing).

   * s390x PCI passthrough needs various changes in the s390x kernel zPCI
 code (incl. the new s390x-specific Kernel config option
 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0
 and got backported to 22.04/jammy as part of LP: #1853306.

   * Lunar an newer Ubuntu releases have the code already included from
 upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the
 config option is not set, hence zPCI pass-through is still not possible.

  [Fix]

   * To be able to make use of VFIO zPCI pass-through on s390x running newer
 Ubuntu releases (especially needed in the context of secure execution)
 the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs
 to be enabled and set to 'y'.

  [Test Case]

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

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

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

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

  [Regression Potential]

   * The regression potential is moderate, since the code is upstream
 for quite a while and already enabled in jammy.

   * The general way on using passthrough has not changed, with this
 change (config option) it's now just possible to passthrough
 zPCI on top.

   * CCW devices are not affected.

   * And this is s390x-specific anyway, so no other architectures are
  affected.

  [Other]

   * The enabling of the kernel config option is exactly the same for L, M
 and U/N, but I submitted separate patches due to slightly different context
 and offsets.
  __

  === Description by mjros...@us.ibm.com  ===

  LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to
  enable enhanced interpretation of PCI passthrough on s390.  It also
  included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which
  is necessary to activate this kernel feature.

  For lunar and mantic, the kernel code did not require backporting due
  to the base kernel version already containing it, 

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Kleber Sacilotto de Souza]

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

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

[Georgia Garcia]

Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue
tests from the AppArmor test suite and they all passed as expected.

georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ uname -a
Linux sec-jammy-amd64 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 
2024 x86_64 x86_64 x86_64 GNU/Linux

georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py 
.
--
Ran 62 tests in 1252.754s

OK (skipped=2)

georgia@sec-jammy-amd64:~$ apt source apparmor
georgia@sec-jammy-amd64:~$ cd apparmor-3.0.4/tests/regression/apparmor/
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ 
USE_SYSTEM=1 make
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ sudo 
./posix_mq.sh 
BAD PASSWORD: The password fails the dictionary check - it is based on a 
dictionary word
xpass: POSIX MQUEUE (confined root - mqueue label 1)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined root - mqueue label 2)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll)


[1] https://launchpad.net/qa-regression-testing

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

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

Title:
  AppArmor patch for mq-posix interface is missing in jammy

Status in linux package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Jammy:
  New

Bug description:
  [ Impact ]

  mq-posix snapd interface does not work on Ubuntu Core 22. It results
  in permission denied even all interfaces are connected.

  Our brandstore customer is using posix message queue for IPC between
  snaps. They added mq-posix interface and connected them properly but
  getting permission denied error.

  The AppArmor patch for posix message queue created for other customer
  did not land in the standard jammy kernel.

  Userspace support for AppArmor message queue handling is already
  present in Ubuntu Core 22, it is just missing from the kernel.

  [ Test Plan ]

   * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or 
Classic 22.04 with the standard kernel.
   * Example snaps for testing: 
https://code.launchpad.net/~itrue/+git/mqtest-provider and 
https://code.launchpad.net/~itrue/+git/mqtest-client

  [ Where problems could occur ]

   * The patches already exist for 5.15 and have been used on other
  private customer kernels and all kernels released after 22.04, so
  there is already a good track record for this patchset and it
  shouldn't create any issues.

  [ Other Info ]
   
   * This is a time-sensitive issue for a paying customer

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


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

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

[Kleber Sacilotto de Souza]

The fix for the Mantic kernel has already been released with linux 6.5.0-14.14:
https://launchpad.net/ubuntu/+source/linux/6.5.0-14.14

This version was promoted to -updates/-security on 2023-12-05, therefore
the bug should have been marked automatically as "Fix Released".
Assuming this was an issue with Launchpad janitor, I'll mark it manually
as released.

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

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 2 0 0 0 0 0 0
   Reqs 18 0 0 0 0 0 0 1
 Extras
   Special socket calls 0
 cork 0
 nodelay 0
 sendpage 0
 splice 0
 urgent data 0

   * Instead of including the payload in the wrong >512 KB buckets,
 the output should be to have 19 reqs in the 8 KB buckets for TX stats
 and 9 reqs in the 8 KB bucket for RX stats.

  [Where problems could occur]

   * The changes 

[Kernel-packages] [Bug 2049049] Re: Focal update: v5.4.261 upstream stable release

[Manuel Diewald]

** Description changed:

  
  SRU Justification
  
  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:
  
 v5.4.261 upstream stable release
 from git://git.kernel.org/
  
  vfs: fix readahead(2) on block devices
  genirq/matrix: Exclude managed interrupts in irq_matrix_allocated()
  i40e: fix potential memory leaks in i40e_remove()
  tcp: call tcp_try_undo_recovery when an RTOd TFO SYNACK is ACKed
  wifi: rtw88: debug: Fix the NULL vs IS_ERR() bug for debugfs_create_file()
  wifi: mt76: mt7603: rework/fix rx pse hang check
  tcp_metrics: add missing barriers on delete
  tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics()
  tcp_metrics: do not create an entry from tcp_init_metrics()
  wifi: rtlwifi: fix EDCA limit set by BT coexistence
  can: dev: can_restart(): don't crash kernel if carrier is OK
  can: dev: can_restart(): fix race condition between controller restart and 
netif_carrier_on()
  thermal: core: prevent potential string overflow
  r8169: use tp_to_dev instead of open code
  r8169: fix rare issue with broken rx after link-down on RTL8125
  chtls: fix tp->rcv_tstamp initialization
  tcp: Remove one extra ktime_get_ns() from cookie_init_timestamp
  tcp: fix cookie_init_timestamp() overflows
  ACPI: sysfs: Fix create_pnp_modalias() and create_of_modalias()
  ipv6: avoid atomic fragment on GSO packets
  net: add DEV_STATS_READ() helper
  ipvlan: properly track tx_errors
  regmap: debugfs: Fix a erroneous check after snprintf()
  clk: qcom: clk-rcg2: Fix clock rate overflow for high parent frequencies
  clk: qcom: gcc-sm8150: use ARRAY_SIZE instead of specifying num_parents
  clk: qcom: gcc-sm8150: Fix gcc_sdcc2_apps_clk_src
  clk: imx: Select MXC_CLK for CLK_IMX8QXP
  clk: keystone: pll: fix a couple NULL vs IS_ERR() checks
  clk: npcm7xx: Fix incorrect kfree
  clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt7629-eth: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt7629: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data
  platform/x86: wmi: Fix probe failure when failing to register WMI devices
  platform/x86: wmi: remove unnecessary initializations
  platform/x86: wmi: Fix opening of char device
  hwmon: (coretemp) Fix potentially truncated sysfs attribute name
  drm/rockchip: vop: Fix reset of state in duplicate state crtc funcs
  drm/rockchip: vop: Fix call to crtc reset helper
  drm/radeon: possible buffer overflow
  drm/rockchip: cdn-dp: Fix some error handling paths in cdn_dp_probe()
  arm64: dts: qcom: sdm845-mtp: fix WiFi configuration
  ARM: dts: qcom: mdm9615: populate vsdcc fixed regulator
  soc: qcom: llcc cleanup to get rid of sdm845 specific driver file
  UBUNTU: [Config] remove CONFIG_QCOM_SDM845_LLCC
  soc: qcom: Rename llcc-slice to llcc-qcom
+ UBUNTU: [Config] remove llcc-slice module
  soc: qcom: llcc: Handle a second device without data corruption
  firmware: ti_sci: Replace HTTP links with HTTPS ones
  firmware: ti_sci: Mark driver as non removable
  clk: scmi: Free scmi_clk allocated when the clocks with invalid info are 
skipped
  hwrng: geode - fix accessing registers
  libnvdimm/of_pmem: Use devm_kstrdup instead of kstrdup and check its return 
value
  sched/rt: Provide migrate_disable/enable() inlines
  nd_btt: Make BTT lanes preemptible
  crypto: caam/qi2 - fix Chacha20 + Poly1305 self test failure
  crypto: caam/jr - fix Chacha20 + Poly1305 self test failure
  HID: cp2112: Use irqchip template
  hid: cp2112: Fix duplicate workqueue initialization
  ARM: 9321/1: memset: cast the constant byte to unsigned char
  ext4: move 'ix' sanity check to corrent position
  scsi: ufs: core: Leave space for '\0' in utf8 desc string
  RDMA/hfi1: Workaround truncation compilation error
  sh: bios: Revive earlyprintk support
  ASoC: Intel: Skylake: Fix mem leak when parsing UUIDs fails
  ASoC: ams-delta.c: use component after check
  mfd: dln2: Fix double put in dln2_probe
  leds: pwm: simplify if condition
  leds: pwm: convert to atomic PWM API
  leds: pwm: Don't disable the PWM when the LED should be off
  ledtrig-cpu: Limit to 8 CPUs
  leds: trigger: ledtrig-cpu:: Fix 'output may be truncated' issue for 'cpu'
  tty: tty_jobctrl: fix pid memleak in disassociate_ctty()
  usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency
  dmaengine: ti: edma: handle irq_of_parse_and_map() errors
  misc: st_core: Do not call kfree_skb() under spin_lock_irqsave()
  tools: iio: privatize globals and functions in 

[Kernel-packages] [Bug 2048796] Re: post-installation script subprocess returned error exit status 1

[Valtýr Kári Daníelsson]

The issue is apparently with the displaylink-driver and evdi packages
provided by Synaptics. Judging by make.log the errors were occurring
because the evdi dkms module failed to compile, so I tried running sudo
apt remove evdi and then sudo apt install evdi-dkms, which is provided
by the noble repository. I was worried my dock wouldn't work right
without the displaylink-driver, but it works fine with just the ubuntu
provided evdi-dkms.

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

Title:
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi, I was updating my system, running sudo apt update then sudo apt
  upgrade and there were some errors in the installation. It seems to
  stem from some post-installation script for linux-
  image-6.6.0-14-generic and/or linux-headers-6.6.0-14-generic. After
  the upgrade apt told me that "errors were encountered while
  processing:" linux-generic, linux-headers-generic, linux-
  image-6.6.0-14-generic and linux-headers-6.6.0-14-generic. Running
  dpkg -a --configure does not solve the issue, nor does apt -f install.
  I've tried reconfiguring with the methods suggested in this thread:
  https://askubuntu.com/questions/949760/dpkg-warning-files-list-file-
  for-package-missing and I can manually reconfigure and reinstall
  linux-generic, linux-headers-generic and linux-image-6.6.0-14-generic,
  and I can reconfigure linux-headers-6.6.0-14-generic but then when I
  try to reinstall that package it gives the error "installed linux-
  headers-6.6.0-14-generic package post-installation script subprocess
  returned error exit status 1."

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixgoats   2427 F wireplumber
   /dev/snd/controlC0:  fixgoats   2408 F pipewire
    fixgoats   2427 F wireplumber
   /dev/snd/seq:fixgoats   2408 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 18:06:52 2024
  InstallationDate: Installed on 2023-03-30 (285 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=0fc69223-fb6f-45e4-9873-b76a5b689b0c ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2023-12-30 (10 days ago)
  dmi.bios.date: 03/29/2021
  dmi.bios.release: 2.3
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.03
  dmi.board.name: LY350
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvnRazer:bvr2.03:bd03/29/2021:br2.3:efr1.0:svnRazer:pnBladeStealth13(Late2020)-RZ09-0327:pvr5.04:rvnRazer:rnLY350:rvr4:cvnRazer:ct10:cvr:skuRZ09-03272N12:
  dmi.product.family: 1A581006 Razer Blade Stealth
  dmi.product.name: Blade Stealth 13 (Late 2020) - RZ09-0327
  dmi.product.sku: RZ09-03272N12
  dmi.product.version: 5.04
  dmi.sys.vendor: Razer

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


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

[Kernel-packages] [Bug 2049049] [NEW] Focal update: v5.4.261 upstream stable release

[Manuel Diewald]

Public bug reported:


SRU Justification

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

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

vfs: fix readahead(2) on block devices
genirq/matrix: Exclude managed interrupts in irq_matrix_allocated()
i40e: fix potential memory leaks in i40e_remove()
tcp: call tcp_try_undo_recovery when an RTOd TFO SYNACK is ACKed
wifi: rtw88: debug: Fix the NULL vs IS_ERR() bug for debugfs_create_file()
wifi: mt76: mt7603: rework/fix rx pse hang check
tcp_metrics: add missing barriers on delete
tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics()
tcp_metrics: do not create an entry from tcp_init_metrics()
wifi: rtlwifi: fix EDCA limit set by BT coexistence
can: dev: can_restart(): don't crash kernel if carrier is OK
can: dev: can_restart(): fix race condition between controller restart and 
netif_carrier_on()
thermal: core: prevent potential string overflow
r8169: use tp_to_dev instead of open code
r8169: fix rare issue with broken rx after link-down on RTL8125
chtls: fix tp->rcv_tstamp initialization
tcp: Remove one extra ktime_get_ns() from cookie_init_timestamp
tcp: fix cookie_init_timestamp() overflows
ACPI: sysfs: Fix create_pnp_modalias() and create_of_modalias()
ipv6: avoid atomic fragment on GSO packets
net: add DEV_STATS_READ() helper
ipvlan: properly track tx_errors
regmap: debugfs: Fix a erroneous check after snprintf()
clk: qcom: clk-rcg2: Fix clock rate overflow for high parent frequencies
clk: qcom: gcc-sm8150: use ARRAY_SIZE instead of specifying num_parents
clk: qcom: gcc-sm8150: Fix gcc_sdcc2_apps_clk_src
clk: imx: Select MXC_CLK for CLK_IMX8QXP
clk: keystone: pll: fix a couple NULL vs IS_ERR() checks
clk: npcm7xx: Fix incorrect kfree
clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data
clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data
clk: mediatek: clk-mt7629-eth: Add check for mtk_alloc_clk_data
clk: mediatek: clk-mt7629: Add check for mtk_alloc_clk_data
clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data
platform/x86: wmi: Fix probe failure when failing to register WMI devices
platform/x86: wmi: remove unnecessary initializations
platform/x86: wmi: Fix opening of char device
hwmon: (coretemp) Fix potentially truncated sysfs attribute name
drm/rockchip: vop: Fix reset of state in duplicate state crtc funcs
drm/rockchip: vop: Fix call to crtc reset helper
drm/radeon: possible buffer overflow
drm/rockchip: cdn-dp: Fix some error handling paths in cdn_dp_probe()
arm64: dts: qcom: sdm845-mtp: fix WiFi configuration
ARM: dts: qcom: mdm9615: populate vsdcc fixed regulator
soc: qcom: llcc cleanup to get rid of sdm845 specific driver file
UBUNTU: [Config] remove CONFIG_QCOM_SDM845_LLCC
soc: qcom: Rename llcc-slice to llcc-qcom
soc: qcom: llcc: Handle a second device without data corruption
firmware: ti_sci: Replace HTTP links with HTTPS ones
firmware: ti_sci: Mark driver as non removable
clk: scmi: Free scmi_clk allocated when the clocks with invalid info are skipped
hwrng: geode - fix accessing registers
libnvdimm/of_pmem: Use devm_kstrdup instead of kstrdup and check its return 
value
sched/rt: Provide migrate_disable/enable() inlines
nd_btt: Make BTT lanes preemptible
crypto: caam/qi2 - fix Chacha20 + Poly1305 self test failure
crypto: caam/jr - fix Chacha20 + Poly1305 self test failure
HID: cp2112: Use irqchip template
hid: cp2112: Fix duplicate workqueue initialization
ARM: 9321/1: memset: cast the constant byte to unsigned char
ext4: move 'ix' sanity check to corrent position
scsi: ufs: core: Leave space for '\0' in utf8 desc string
RDMA/hfi1: Workaround truncation compilation error
sh: bios: Revive earlyprintk support
ASoC: Intel: Skylake: Fix mem leak when parsing UUIDs fails
ASoC: ams-delta.c: use component after check
mfd: dln2: Fix double put in dln2_probe
leds: pwm: simplify if condition
leds: pwm: convert to atomic PWM API
leds: pwm: Don't disable the PWM when the LED should be off
ledtrig-cpu: Limit to 8 CPUs
leds: trigger: ledtrig-cpu:: Fix 'output may be truncated' issue for 'cpu'
tty: tty_jobctrl: fix pid memleak in disassociate_ctty()
usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency
dmaengine: ti: edma: handle irq_of_parse_and_map() errors
misc: st_core: Do not call kfree_skb() under spin_lock_irqsave()
tools: iio: privatize globals and functions in iio_generic_buffer.c file
tools: iio: iio_generic_buffer: Fix some integer type and calculation
tools: iio: iio_generic_buffer ensure alignment
USB: usbip: fix stub_dev hub disconnect
dmaengine: pxa_dma: Remove an erroneous BUG_ON() in 

[Kernel-packages] [Bug 2040102] Re: kernel warning when open the lid

[Alfred]

Now ubuntu jammy hwe kernel is 6.5, it does not seem to have this issue
now.

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

Title:
  kernel warning when open the lid

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

Bug description:
  I always put my thinkpad neo 14 to idle, close the lid, but not
  sleep/suspend, when I open the lid and login, I can see below warning
  from kernel in journal. If my memory is correct, when kernel is still
  around 5.15 or previous hwe(might be 6.0), I just see the first
  message about psmouse, no kernel warning.

  Oct 22 19:52:52 kernel: psmouse serio1: TrackPoint at isa0060/serio1/input0 
lost synchronization, throwing 1 bytes away.
  Oct 22 19:52:52 kernel: [ cut here ]
  Oct 22 19:52:52 kernel: WARNING: CPU: 15 PID: 1674 at 
drivers/acpi/platform_profile.c:74 platform_profile_show+0xae/0xf0 
[platform_profile]
  Oct 22 19:52:52 kernel: Modules linked in: btrfs blake2b_generic xor raid6_pq 
ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid tls tcp_diag inet_diag 
pppoe pppox rfcomm veth nft_masq dummy bridge stp llc nvme_fabrics 
nf_conntrack_netbio
  s_ns nf_conntrack_broadcast ccm vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib 
nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat 
nf_nat nf_co
  nntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink 
cmac algif_hash algif_skcipher af_alg overlay bnep binfmt_misc zstd snd_ctl_led 
snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi 
snd_sof_probes sn
  d_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic btusb uvcvideo 
btrtl videobuf2_vmalloc btbcm videobuf2_memops btintel videobuf2_v4l2 btmtk 
videodev bluetooth videobuf2_common ecdh_generic mc ecc snd_soc_dmic 
snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel
  Oct 22 19:52:52 kernel:  soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils 
snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi 
soundwire_bus intel_tcc_cooling snd_soc_core x86_pkg_temp_thermal snd_compress 
intel_powerclamp ac97_bus snd_pcm_dmaengine coretemp snd_hda_intel kvm_intel 
snd_intel_dspcfg zfs(PO) i915 snd_intel_sdw_acpi kvm snd_hda_codec zunicode(PO) 
snd_hda_core snd_hwdep zzst
  d(O) irqbypass thinkpad_acpi iwlmvm drm_buddy snd_pcm crct10dif_pclmul nvram 
zlua(O) ttm polyval_clmulni polyval_generic snd_seq_midi drm_display_helper 
zavl(PO) mac80211 ghash_clmulni_intel snd_seq_midi_event cec sha512_ssse3 
icp(PO) snd_rawmidi nls_iso8859_1 rc_core aesni_intel snd_seq 
processor_thermal_device_pci libarc4 drm_kms_helper crypto_simd zcommon(PO) 
snd_seq_device processor_thermal_device i2c_algo_bit cryptd mei_hdcp iwlwifi 
mei_pxp snd_timer znvpair(PO) proces
  sor_thermal_rfim syscopyarea cmdlinepart pmt_telemetry
  Oct 22 19:52:52 kernel:  rapl spi_nor snd intel_rapl_msr pmt_class input_leds 
processor_thermal_mbox sysfillrect mei_me think_lmi spl(O) cfg80211 
processor_thermal_rapl intel_cstate serio_raw firmware_attributes_class 
wmi_bmof mtd sysimgbl
  t soundcore mei intel_rapl_common igen6_edac intel_vsec ledtrig_audio mac_hid 
int3403_thermal int3400_thermal intel_hid soc_button_array platform_profile 
int340x_thermal_zone acpi_thermal_rel acpi_tad sparse_keymap acpi_pad 
sch_fq_codel ms
  r parport_pc lz4 lz4_compress ppdev lp drm zram parport efi_pstore autofs4 
nvme ucsi_acpi spi_intel_pci i2c_i801 xhci_pci typec_ucsi nvme_core video 
crc32_pclmul psmouse thunderbolt spi_intel i2c_smbus xhci_pci_renesas typec 
nvme_common wm
  i pinctrl_tigerlake
  Oct 22 19:52:52 kernel: CPU: 15 PID: 1674 Comm: power-profiles- Tainted: P
W  O   6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 22 19:52:52 kernel: Hardware name: LENOVO 21DN001ACD/21DN001ACD, BIOS 
R1RET48W(1.20) 03/06/2023
  Oct 22 19:52:52 kernel: RIP: 0010:platform_profile_show+0xae/0xf0 
[platform_profile]
  Oct 22 19:52:52 kernel: Code: e7 e8 f6 bb 80 df 48 98 48 8b 55 e8 65 48 2b 14 
25 28 00 00 00 75 33 48 83 c4 10 5b 41 5c 5d 31 d2 31 f6 31 ff c3 cc cc cc cc 
<0f> 0b 48 c7 c0 fb ff ff ff eb d3 48 c7 c7 60 61 54 c0 e8 6b 0e 36
  Oct 22 19:52:52 kernel: RSP: 0018:a5a5c635bce0 EFLAGS: 00010282
  Oct 22 19:52:52 kernel: RAX: ed0fbddb RBX:  RCX: 

  Oct 22 19:52:52 kernel: RDX:  RSI:  RDI: 

  Oct 22 19:52:52 kernel: RBP: a5a5c635bd00 R08: 8cf841f7a880 R09: 
0001
  Oct 22 19:52:52 kernel: R10:  R11:  R12: 
8cf9ddb43000
  Oct 22 19:52:52 kernel: R13: 0001 R14: 8cf8426d40a0 R15: 
8cf8426d4078
  Oct 22 19:52:52 kernel: FS:  

[Kernel-packages] [Bug 2048735] Re: Disable keyboard wakeup for Framework 13

[Timo Aaltonen]

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

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

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

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

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

Title:
  Disable keyboard wakeup for Framework 13

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  Framework 13" AMD version has an unexpected behavior that EC triggers
  a keyboard wakeup event every time the system exits s0i3. This EC
  keyboard wakeup event is to workaround a different bug.

  Because of this, the following series is sent to mailing list to
  disable wakeup from keyboard when on latest BIOS for Framework 13 AMD.

  
  
https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a

  
  85980669a863 platform/x86/amd/pmc: Move platform defines to header
  2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on 
Cezanne
  b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection 
to pmc-quirks
  a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Soenke]

** Patch added: 
"https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/;
   
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

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

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Alfred]

My Thinkpad T440p with intel 7260 does not have such 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/2047022

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Alfred]

00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi WiFi 
[8086:51f0] (rev 01)
Subsystem: Intel Corporation Device [8086:0090]
Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 9
Memory at 601d1cc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 

Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Alfred]

confirm comment #8,  2nd boot up with 6.5 kernel, wifi now works.

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Alfred]

yes, today my ubuntu jammy upgrade from 6.2 to 6.5, my wifi is gone.

kernel log see attachment

** Attachment added: "journalctl -b -2 -g iwlwifi --no-hostname"
   
https://bugs.launchpad.net/ubuntu/+bug/2047022/+attachment/5738431/+files/iwlwifi.txt

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Launchpad Bug Tracker]

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

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

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Launchpad Bug Tracker]

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

** Changed in: Ubuntu Mantic
   Status: New => Confirmed

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Launchpad Bug Tracker]

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

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic

[Launchpad Bug Tracker]

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

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

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

Title:
  WiFi is not work after upgrade Kernel to 6.5.0-14-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in The Mantic Minotaur:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge

  [Steps to reproduce]
  1. Install Ubuntu 22.04.04 Desktop image to the system
  2. sudo apt-get update
  3. sudo apt-get dist-upgrade
  4. sudo apt install linux-generic-hwe-22.04-edge
  5. Reboot system

  [Expected result]
  WiFi is working after upgrade Kernel

  [Actual result]
  WiFi is not work. Could not find WiFi interface from GUI.

  [Failure rate]
  1/5

  [Additional information]
  CID:202112-29800
  SKU: TRBA-DVT2-C6
  system-manufacturer: Dell Inc.
  system-product-name: XPS 9320
  bios-version: 1.7.1
  CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a6] (rev 08)
  kernel-version: 6.5.0-14-generic

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 2048827] Re: [amdgpu] Mouse cursor theme is grey instead of black

[Chase Clark]

Alright, thanks for looking into this!

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

Title:
  [amdgpu] Mouse cursor theme is grey instead of black

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

Bug description:
  - this is a fresh install of the latest Ubuntu 24.04

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

  - the strange thing is the cursor looks normal when I boot off the USB
  and then looks grey on first boot

  - even more strange is when I went to screenshot the cursor for this
  bug report, it looked normal in the screenshot

  - For graphics I have AMD 6600XT

  
  - I will try in X11 as well to see if this is a Wayland-only issue

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yaru-theme-gtk 22.04.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 21:57:08 2024
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71

[Jeremy Bícha]

ell had an approved MIR but the only thing it was used for was iwd which
is not currently in main. After the MIR is approved, something in main
needs to depend on it (or add it to a main seed) and then the Archive
Admins can promote it to main.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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

[Kernel-packages] [Bug 2049027] [NEW] The display becomes frozen after some time when a HDMI device is connected.

[Sönke Huster]

Public bug reported:

It is exactly this bug:
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

It was fixed with that kernel commit:

commit 648d7be8ecf47b0556e32550145c70db153b16fb
Author: Ville Syrjälä 
Date:   Mon Dec 11 23:37:47 2023 +0200

drm/i915/dmc: Don't enable any pipe DMC events


https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

which was picked for 6.6.9.

I'd like to ask whether it is possible to apply that patch to the
current Ubuntu kernel?

Best
Sönke

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 13:11:59 2024
InstallationDate: Installed on 2023-03-01 (316 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

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

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Roxana Nicolescu]

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

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2049024] [NEW] Focal update: v5.4.260 upstream stable release

[Manuel Diewald]

Public bug reported:


SRU Justification

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

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

mtd: rawnand: marvell: Ensure program page operations are successful
selftests/ftrace: Add new test case which checks non unique symbol
mcb: Return actual parsed size when reading chameleon table
mcb-lpc: Reallocate memory region to avoid memory overlapping
virtio_balloon: Fix endless deflation and inflation on arm64
virtio-mmio: fix memory leak of vm_dev
r8169: fix the KCSAN reported data-race in rtl_tx while reading 
TxDescArray[entry].opts1
r8169: fix the KCSAN reported data race in rtl_rx while reading desc->opts1
treewide: Spelling fix in comment
igb: Fix potential memory leak in igb_add_ethtool_nfc_entry
neighbour: fix various data-races
igc: Fix ambiguity in the ethtool advertising
net: ieee802154: adf7242: Fix some potential buffer overflow in 
adf7242_stats_show()
r8152: Increase USB control msg timeout to 5000ms as per spec
r8152: Run the unload routine if we have errors during probe
r8152: Cancel hw_phy_work if we have an error in probe
tcp: fix wrong RTO timeout when received SACK reneging
gtp: uapi: fix GTPA_MAX
gtp: fix fragmentation needed check with gso
iio: exynos-adc: request second interupt only when touchscreen mode is used
i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node()
i2c: muxes: i2c-mux-gpmux: Use of_get_i2c_adapter_by_node()
i2c: muxes: i2c-demux-pinctrl: Use of_get_i2c_adapter_by_node()
i2c: stm32f7: Fix PEC handling in case of SMBUS transfers
i2c: aspeed: Fix i2c bus hang in slave read
nvmem: imx: correct nregs for i.MX6ULL
nvmem: imx: correct nregs for i.MX6SLL
nvmem: imx: correct nregs for i.MX6UL
perf/core: Fix potential NULL deref
clk: Sanitize possible_parent_show to Handle Return Value of 
of_clk_get_parent_name
i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR
x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility
drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()
arm64: fix a concurrency issue in emulation_proc_handler()
smbdirect: missing rc checks while waiting for rdma events
f2fs: fix to do sanity check on inode type during garbage collection
nfsd: lock_rename() needs both directories to live on the same fs
x86/mm: Simplify RESERVE_BRK()
x86/mm: Fix RESERVE_BRK() for older binutils
ext4: add two helper functions extent_logical_end() and pa_logical_end()
ext4: avoid overlapping preallocations due to overflow
ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow
driver: platform: Add helper for safer setting of driver_override
rpmsg: Constify local variable in field store macro
rpmsg: Fix kfree() of static memory on setting driver_override
rpmsg: Fix calling device_lock() on non-initialized device
rpmsg: glink: Release driver_override
rpmsg: Fix possible refcount leak in rpmsg_register_device_override()
x86: Fix .brk attribute in linker script
Input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table
irqchip/stm32-exti: add missing DT IRQ flag translation
dmaengine: ste_dma40: Fix PM disable depth imbalance in d40_probe
Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport
fbdev: atyfb: only use ioremap_uc() on i386 and ia64
spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
netfilter: nfnetlink_log: silence bogus compiler warning
ASoC: rt5650: fix the wrong result of key button
fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()
scsi: mpt3sas: Fix in error path
platform/x86: asus-wmi: Change ASUS_WMI_BRN_DOWN code from 0x20 to 0x2e
platform/mellanox: mlxbf-tmfifo: Fix a warning message
net: chelsio: cxgb4: add an error code check in t4_load_phy_fw
ata: ahci: fix enum constants for gcc-13
remove the sx8 block driver
UBUNTU: [Config] remove CONFIG_BLK_DEV_SX8
Revert "ARM: dts: Move am33xx and am43xx mmc nodes to sdhci-omap driver"
PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" 
compatibility
tty: 8250: Remove UC-257 and UC-431
tty: 8250: Add support for additional Brainboxes UC cards
tty: 8250: Add support for Brainboxes UP cards
tty: 8250: Add support for Intashield IS-100
Linux 5.4.260
UBUNTU: Upstream stable to v5.4.260

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Manuel Diewald (diewald)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: 

[Kernel-packages] [Bug 2049022] Re: virtualbox-dkms.0.crash VirtualBox DMKS module NOT working

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-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-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049022

Title:
  virtualbox-dkms.0.crash VirtualBox DMKS module NOT working

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  vcarceler@zvezda:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  vcarceler@zvezda:~$

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  vcarceler@zvezda:~$ apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Instalados: 6.5.0.14.14~22.04.7
Candidato:  6.5.0.14.14~22.04.7
Tabla de versión:
   *** 6.5.0.14.14~22.04.7 500
  500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  vcarceler@zvezda:~$

  3) What you expected to happen

  VirtualBox works

  4) What happened instead

  VirtualBox not working

  Building virtualbox module fails. It's not possible to run virtual
  machines with virtualbox.

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


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

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2049022] [NEW] virtualbox-dkms.0.crash VirtualBox DMKS module NOT working

[vcarceler]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

vcarceler@zvezda:~$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
vcarceler@zvezda:~$

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

vcarceler@zvezda:~$ apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
  Instalados: 6.5.0.14.14~22.04.7
  Candidato:  6.5.0.14.14~22.04.7
  Tabla de versión:
 *** 6.5.0.14.14~22.04.7 500
500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 5.15.0.25.27 500
500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
vcarceler@zvezda:~$

3) What you expected to happen

VirtualBox works

4) What happened instead

VirtualBox not working

Building virtualbox module fails. It's not possible to run virtual
machines with virtualbox.

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

** Attachment added: "virtualbox-error.png"
   
https://bugs.launchpad.net/bugs/2049022/+attachment/5738412/+files/virtualbox-error.png

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

Title:
  virtualbox-dkms.0.crash VirtualBox DMKS module NOT working

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  vcarceler@zvezda:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  vcarceler@zvezda:~$

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  vcarceler@zvezda:~$ apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Instalados: 6.5.0.14.14~22.04.7
Candidato:  6.5.0.14.14~22.04.7
Tabla de versión:
   *** 6.5.0.14.14~22.04.7 500
  500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  vcarceler@zvezda:~$

  3) What you expected to happen

  VirtualBox works

  4) What happened instead

  VirtualBox not working

  Building virtualbox module fails. It's not possible to run virtual
  machines with virtualbox.

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


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

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

[bugproxy]

I believe that having a kernel in PPA to unblock you is not very
helpful, since yI think you need that kernel signed with the usual
(prod.) signature/key (and not with a test/dev key coming from the PPA).

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

[Isaac True]

Confirmed fixed in linux/5.15.0-94.104 using the itrue-mqtest-provider
and itrue-mqtest-client snaps.

Test procedure:

sudo snap install itrue-mqtest-provider itrue-mqtest-client
sudo snap connect itrue-mqtest-client:itrue-mqtest-all-perms 
itrue-mqtest-provider:itrue-mqtest-all-perms 
sudo snap connect itrue-mqtest-client:itrue-mqtest-default 
itrue-mqtest-provider:itrue-mqtest-default  
sudo snap connect itrue-mqtest-client:itrue-mqtest-ro 
itrue-mqtest-provider:itrue-mqtest-ro  
sudo snap connect itrue-mqtest-client:itrue-mqtest-rw 
itrue-mqtest-provider:itrue-mqtest-rw  

Before upgrading (on kernel 5.15.0-1048-kvm):

ubuntu@concise-pangolin:~$ sudo itrue-mqtest-provider
MQ "/test-default" failed: File exists
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-client.all
MQ "/test-all-perms" failed: Operation not permitted
Test failed

After upgrading (5.15.0-94-generic):

(in first terminal)
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-provider
MQ "/test-default" created
MQ "/test-ro" created
MQ "/test-rw" created
MQ "/test-all-perms" created
MQ "/test-default": 0xDEADBEEF
MQ "/test-all-perms": 0xDEADBEEF

(in second terminal)
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-client.default
Test succeeded
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-client.all
Test succeeded

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

Title:
  AppArmor patch for mq-posix interface is missing in jammy

Status in linux package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Jammy:
  New

Bug description:
  [ Impact ]

  mq-posix snapd interface does not work on Ubuntu Core 22. It results
  in permission denied even all interfaces are connected.

  Our brandstore customer is using posix message queue for IPC between
  snaps. They added mq-posix interface and connected them properly but
  getting permission denied error.

  The AppArmor patch for posix message queue created for other customer
  did not land in the standard jammy kernel.

  Userspace support for AppArmor message queue handling is already
  present in Ubuntu Core 22, it is just missing from the kernel.

  [ Test Plan ]

   * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or 
Classic 22.04 with the standard kernel.
   * Example snaps for testing: 
https://code.launchpad.net/~itrue/+git/mqtest-provider and 
https://code.launchpad.net/~itrue/+git/mqtest-client

  [ Where problems could occur ]

   * The patches already exist for 5.15 and have been used on other
  private customer kernels and all kernels released after 22.04, so
  there is already a good track record for this patchset and it
  shouldn't create any issues.

  [ Other Info ]
   
   * This is a time-sensitive issue for a paying customer

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


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

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Kleber Sacilotto de Souza]

SRU request submitted: https://lists.ubuntu.com/archives/kernel-
team/2024-January/148033.html

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

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

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2049021] [NEW] package linux-headers-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: el subproceso instalado paquete linux-headers-6.2.0-39-generic script post-i

[Jenaro Gallego]

Public bug reported:

Ubuntu 22.04.3 LTS
Release: 22.04

I've an external usb WIFI. The drivers for Linux have been compiled and
insalled in this system. Up to now I didn't get any issue with the
update of linux headers but I wonder if this is the reason for this
error.

Output of lsusb: (the adapter is the TP-Link Archer T4U ver.3)

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 006: ID 2357:0115 TP-Link Archer T4U ver.3
Bus 001 Device 004: ID 214b:7000 Huasheng Electronics 4-port hub [Maxxter 
ACT-HUB2-4P, HS8836, iSoul ultra-slim]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-headers-6.2.0-39-generic 6.2.0-39.40~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Jan 11 12:21:08 2024
ErrorMessage: el subproceso instalado paquete linux-headers-6.2.0-39-generic 
script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2023-03-29 (288 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
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: linux-hwe-6.2
Title: package linux-headers-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to 
install/upgrade: el subproceso instalado paquete linux-headers-6.2.0-39-generic 
script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-headers-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to
  install/upgrade: el subproceso instalado paquete linux-
  headers-6.2.0-39-generic script post-installation devolvió el código
  de salida de error 1

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

Bug description:
  Ubuntu 22.04.3 LTS
  Release: 22.04

  I've an external usb WIFI. The drivers for Linux have been compiled
  and insalled in this system. Up to now I didn't get any issue with the
  update of linux headers but I wonder if this is the reason for this
  error.

  Output of lsusb: (the adapter is the TP-Link Archer T4U ver.3)

  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
  Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
  Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 007: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
  Bus 001 Device 006: ID 2357:0115 TP-Link Archer T4U ver.3
  Bus 001 Device 004: ID 214b:7000 Huasheng Electronics 4-port hub [Maxxter 
ACT-HUB2-4P, HS8836, iSoul ultra-slim]
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-6.2.0-39-generic 6.2.0-39.40~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jan 11 12:21:08 2024
  ErrorMessage: el subproceso instalado paquete linux-headers-6.2.0-39-generic 
script post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2023-03-29 (288 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  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: linux-hwe-6.2
  Title: package linux-headers-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to 
install/upgrade: el subproceso instalado 

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

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

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

Bug description:
  SRU Justification

  [Impact]

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

  [Fix]

  Please consider enabling the following kconfigs:

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

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

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

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

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

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

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Committed
Status in ivsc-driver source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on 

[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  allow io_uring to be disabled in runtime

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  io_uring has been an important attack vector in the recent years in local 
privilege escalation attacks. Allowing admins that don't use io_uring to 
disable it in their systems allows them to reduce their attack surface.

  [Test case]
  sysctl -w kernel.io_uring_disabled=1
  then try to use io_uring from an unprivileged user, then try it with 
privileges (CAP_SYS_ADMIN)

  Actually also tried setting kernel.io_uring_disabled=2 and checking that
  neither (privileged or unprivileged worked).

  Then testing setting it back to 0.

  Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and
  that it worked for group 1000, then set it to 1001 and verified that it
  didn't work anymore for group 1000.

  
  [Potential regression]
  Uses can be denied from using io_uring.

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


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

[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Infinite systemd loop when power off the machine with multiple MD
  RAIDs

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

Bug description:
  [Impact]
  The system with multiple MD RAIDs sometimes hangs while rebooting, that's 
because of the systemd can't stop and close the MD disk.

  [Fix]
  This commit fixes the issue, and this issue has been introduced by 
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed") 
after v6.0

  https://patchwork.kernel.org/project/linux-
  raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/

  [Test case]
  1. Reboot the system with multiple MD RAIDs at least 10 times.
  2. Make sure the system can reboot successfully every time.
  3. You should not see error messages like below.

  [ 205.360738] systemd-shutdown[1]: Stopping MD devices.
  [ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
  [ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
  [ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
  [ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
  [ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127, 
ignoring: Input/output error
  [ 205.404975] md: md127 stopped.
  [ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
  [ 205.770179] md: md126: resync interrupted.
  [ 205.776258] md126: detected capacity change from 1900396544 to 0
  [ 205.783349] md: md126 stopped.
  [ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
  [ 205.862435] md: md126 stopped.
  [ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125, 
ignoring: Input/output error
  [ 205.872845] block device autoloading is deprecated and will be removed.
  [ 205.880955] md: md125 stopped.
  [ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
  [ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or 
resource busy
  [ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
  [ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or 
resource busy
  [ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
  [ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or 
resource busy
  [ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.

  [Where problems could occur]
  It fixes the data race issue, should not introduce any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+subscriptions


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

[Kernel-packages] [Bug 2036377] Re: Fix RCU warning on AMD laptops

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Fix RCU warning on AMD laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Scary kernel splat about RCU can be observed everytime laptop resumes
  from suspend.

  [Fix]
  Use non-atomic notifier for power supply change to relax the constraint.

  [Test]
  Once the fix is applied, no more RCU warning can be found after several
  suspend/resume cycle.

  [Where problems could occur]
  Essentially no regression potential. Atomic notifier should be used by
  core kernel, and things like power supply doesn't need to be atomic
  anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036377/+subscriptions


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

[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Fix unstable audio at low levels on Thinkpad P1G4

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The audio at low levels is not stable with fluctuating levels.

  [Fix]
  Forcibly assign NID 0x03 to HP while NID 0x02 to SPK.

  [Test]
  Tested on hardware, the audio output is OK at all levels.

  [Where problems could occur]
  It may break audio output on Thinkpad P1G4/5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037077/+subscriptions


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

[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
  multimedia and PCIE peripherals

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

Bug description:
  [SRU Justification]

  [Impact]
  IOMMU related peripherals cannot work.

  [Fix]
  CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency.

  [Test Case]
  build test.
  this is the first step to enable the platform on generic kernel. to fully 
enable the platform, there are some modifications still needed, so only the 
build test is performed at this stage.

  [Where problems could occur]
  to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be 
built-in. the risk would be low because it's not used by default and it needs 
the driver to allocate by demand.

  [Other info]
  the purpose of this is to make ubuntu as an arm systemready ir distribution 
for mediatek platform.

  https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady-
  IR/Test-installation-of-Linux-distributions?lang=en

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


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

[Kernel-packages] [Bug 2037273] Re: Realtek 8852CE WiFi 6E country code udpates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Realtek 8852CE WiFi 6E country code udpates

Status in HWE Next:
  New
Status in linux 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-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing WiFi 6G band for interested countries.

  [Fix]

  Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
  regulatory map to R64-R43").

  [Test Case]

  Use `iw list` to check if 6G bands are then enabled.

  [Where problems could occur]

  This enables corresponding 6G bands for rtw89 driven devices. There
  should be no other side effects.

  [Other Info]

  Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable
  is skipped.

  = original bug report ==

  Proposed fix: 
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
  Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update 
regulatory map to R64-R43") and is in v6.6-rc1 now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037273/+subscriptions


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

[Kernel-packages] [Bug 2038522] Re: disable shiftfs

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  disable shiftfs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Now that all the filesystems that we officially support have the
  idmapped mounts capability we can get rid of shiftfs.

  The benefit of this change is that we don't have to maintain an out-
  of-tree filesystem anymore and we can completely rely on upstream
  features.

  [Test case]

  lxd was the main user of shiftfs to compensate the lack of idmapped
  mounts capability of certain filesystems, such as zfs / ceph, but now
  in mantic also these two filesystem received the support for idmapped
  mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see
  LP: #2032959).

  The lxd team provided a positive feedback, testing the latest 6.5
  Mantic kernel across all the supported filesystems with shiftfs
  disabled.

  [Fix]

  Disable shiftfs in the kernel config and enable unsafe idmapped mounts
  by default (default=on).

  [Regression potential]

  The support for idmapped mounts for the ceph filesystem is not applied
  upstream yet, so we may experience regressions in systems that are
  using this filesystem. Moreover disabling shiftfs may trigger failures
  in our testing (testing shiftfs capabilities will obviously fail) or
  break any other user-space application that is relying on shiftfs
  (however to our knowledge lxd was the only "official" user or shiftfs;
  for this reason we may also see potential regressions in lxd).

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


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

[Kernel-packages] [Bug 2039405] Re: Unable to power off the system with MTL CPU

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Unable to power off the system with MTL CPU

Status in HWE Next:
  New
Status in linux 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-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The commit introduced from v6.4 leads to the power off issue
  45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible

  [Fix]
  The problematic commit has been reverted since v6.6
  fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible"

  [Test case]
  1. Power up the MTL system
  2. Power off the system and make sure it shutdown correctly

  [Where problems could occur]
  From the origin commit log, revert the commit may have a protential security 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039405/+subscriptions


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

[Kernel-packages] [Bug 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  drop all references to is_rust_module.sh in kernels >= 6.5

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

Bug description:
  [Impact]

  The script tools/is_rust_module.sh has been dropped by this commit:

079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
  is_rust_module.sh")

  And upstream as well (in 6.6):

41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")

  But we still have a reference of it in debian.master/reconstruct and
  that generates the following warning during the build:

chmod: cannot access 'scripts/is_rust_module.sh': No such file or
  directory

  [Fix]

  Drop the reference to is_rust_module.sh from reconstruct to prevent
  unnecessary warnings during the build.

  [Test case]

  The following command ran from the kernel source directory is enough
  to trigger the warning:

   $ fakeroot debian/rules clean

  [Regression potential]

  This change is affecting only our packaging. The change is trivial but
  it might affect our kernel build process in case of regressions.

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


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

[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

  
  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 

[Kernel-packages] [Bug 2040192] Re: AppArmor spams kernel log with assert when auditing

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  AppArmor spams kernel log with assert when auditing

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

Bug description:
  A reply to a prompt request that denies all permissions requested will throw 
the following warning, because the auditing code does not expect the request 
field to be empty when generating the audit message.   
   

  Sep 27 22:48:14 ubuntu-mantic snapd[596]: listener.go:189: Sending access 
response back to kernel: {MsgNotification:{MsgHeader:{Length:0 Version:0} 
NotificationType:APPARMOR_NOTIF_RESP Signalled:0 NoCache:1 ID:2 Error:0} 
Error:-13 Allow:0 Deny:4}
  Sep 27 22:48:14 ubuntu-mantic kernel: [ cut here ]
  Sep 27 22:48:14 ubuntu-mantic kernel: AppArmor WARN aa_audit_file: 
((!ad.request)): 
  Sep 27 22:48:14 ubuntu-mantic kernel: WARNING: CPU: 3 PID: 2082 at 
security/apparmor/file.c:268 aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel: Modules linked in: snd_seq_dummy 
snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
snd_timer snd soundcore binfmt_misc nls_iso8859_1 kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel virtio_gpu crypto_simd cryptd 
virtio_dma_buf drm_shmem_helper 9pnet_virtio drm_kms_helper 9pnet 
vmw_vsock_virtio_transport virtio_input vmw_vsock_virtio_transport_common 
input_leds joydev serio_raw vsock msr parport_pc ppdev lp parport drm virtiofs 
efi_pstore ip_tables x_tables autofs4 virtio_net xhci_pci ahci psmouse 
net_failover libahci xhci_pci_renesas failover virtio_rng
  Sep 27 22:48:14 ubuntu-mantic kernel: CPU: 3 PID: 2082 Comm: bash Not tainted 
6.5.0-5-generic #5+aa4.0.0+debug5-Ubuntu
  Sep 27 22:48:14 ubuntu-mantic kernel: Hardware name: QEMU Standard PC (Q35 + 
ICH9, 2009)/LXD, BIOS unknown 2/2/2022
  Sep 27 22:48:14 ubuntu-mantic kernel: RIP: 0010:aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel: Code: 3c ff ff ff e8 80 6f a8 ff 44 8b 
95 3c ff ff ff 5a 59 e9 e3 fe ff ff 48 c7 c6 98 5c 08 84 48 c7 c7 90 1a 60 84 
e8 9f da 9d ff <0f> 0b 8b 85 78 ff ff ff e9 05 ff ff ff 48 89 de 4c 89 f7 e8 b7 
f5
  Sep 27 22:48:14 ubuntu-mantic kernel: RSP: 0018:b66a82b57968 EFLAGS: 
00010246
  Sep 27 22:48:14 ubuntu-mantic kernel: RAX:  RBX: 
b66a82b57b24 RCX: 
  Sep 27 22:48:14 ubuntu-mantic kernel: RDX:  RSI: 
 RDI: 
  Sep 27 22:48:14 ubuntu-mantic kernel: RBP: b66a82b57a30 R08: 
 R09: 
  Sep 27 22:48:14 ubuntu-mantic kernel: R10:  R11: 
 R12: 
  Sep 27 22:48:14 ubuntu-mantic kernel: R13: 8b160239d800 R14: 
b66a82b57970 R15: 0001
  Sep 27 22:48:14 ubuntu-mantic kernel: FS:  7f1f7d3b3380() 
GS:8b17778c() knlGS:
  Sep 27 22:48:14 ubuntu-mantic kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 27 22:48:14 ubuntu-mantic kernel: CR2: 55d4482063f0 CR3: 
000137e64000 CR4: 00750ee0
  Sep 27 22:48:14 ubuntu-mantic kernel: PKRU: 5554
  Sep 27 22:48:14 ubuntu-mantic kernel: Call Trace:
  Sep 27 22:48:14 ubuntu-mantic kernel:  
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? show_regs+0x6d/0x80
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? __warn+0x89/0x160
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? report_bug+0x17e/0x1b0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? handle_bug+0x51/0xa0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? exc_invalid_op+0x18/0x80
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 

[Kernel-packages] [Bug 2040194] Re: apparmor restricts read access of user namespace mediation sysctls to root

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  apparmor restricts read access of user namespace mediation sysctls to
  root

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

Bug description:
  lxc and lxd currently need to determine if the apparmor restriction   
  
  on unprivileged user namespaces are being enforced, so that apparmor  
  
  restrictions won't break lxc/d, and they won't clutter the logs   
  
  by doing something like   
  

  
unshare true
  

  
  to test if the restrictions are being enforced.   
  

  
  Ideally access to this information would be restricted so that any
  
  unknown access would be logged, but lxc/d currently aren't ready for  
  
  this so in order to _not_ force lxc/d to probe whether enforcement is 
  
  enabled, open up read access to the sysctls for unprivileged user 
  
  namespace mediation.  
  
   
  https://github.com/canonical/lxd/issues/11920#issuecomment-1756110109

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


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

[Kernel-packages] [Bug 2040245] Re: apparmor oops when racing to retrieve a notification

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  apparmor oops when racing to retrieve a notification

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

Bug description:
  When there is a race to receive a notification, the failing tasks 
  
  oopes when erroring   
  

  
  [  196.140988] BUG: kernel NULL pointer dereference, address: 
  
  [  196.140995] #PF: supervisor read access in kernel mode 
  
  [  196.140996] #PF: error_code(0x) - not-present page 
  
  [  196.140997] PGD 0 P4D 0
  
  [  196.140999] Oops:  [#1] PREEMPT SMP NOPTI  
  
  [  196.141001] CPU: 0 PID: 2316 Comm: aa-prompt Not tainted 6.5.0-9-generic 
#9-\
  Ubuntu
  
  [  196.141004] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.15.0-\
  1 04/01/2014  
  
  [  196.141005] RIP: 0010:aa_listener_unotif_recv+0x11d/0x260  
  
  [  196.141011] Code: ff ff ff 8b 55 d0 48 8b 75 c8 4c 89 ef e8 6b db ff ff 49 
8\
  9 c2 48 85 c0 0f 88 c0 00 00 00 0f 84 25 ff ff ff 8b 05 3b 1c 1f 03 <49> 8b 
55 \
  00 83 e0 20 83 7a 08 07 74 66 85 c0 0f 85 01 01 00 00 48  
  
  [  196.141012] RSP: 0018:a2674075fdd8 EFLAGS: 00010246
  
  [  196.141014] RAX:  RBX: 974507a08404 RCX: 
000\
  0 
  
  [  196.141017] RDX:  RSI:  RDI: 
000\
  0 
  
  [  196.141017] RBP: a2674075fe10 R08:  R09: 
000\
  0 
  
  [  196.141018] R10: fffe R11:  R12: 
974507a0840\
  0 
  
  [  196.141019] R13:  R14: 974507a08430 R15: 
97451de00a0\
  0 
  
  [  196.141020] FS:  7f4ab6b30740() GS:97486fa0() 
knlGS:\
    
  
  [  196.141022] CS:  0010 DS:  ES:  CR0: 80050033  
  
  [  196.141024] CR2:  CR3: 000104cf2003 CR4: 
00770ef\
  0 
  
  [  196.141026] PKRU: 5554 
  
  [  196.141027] Call Trace:
  
  [  196.141032]  
  
  [  196.141034]  ? show_regs+0x6d/0x80 
  
  [  196.141041]  ? __die+0x24/0x80 
  
  [  196.141043]  ? page_fault_oops+0x99/0x1b0  
  
  [  196.141047]  ? do_user_addr_fault+0x316/0x6b0  
  
  [  196.141048]  ? filemap_map_pages+0x2b3/0x460   
  
  [  196.141056]  ? exc_page_fault+0x83/0x1b0   
  
  [  196.141068]  ? asm_exc_page_fault+0x27/0x30
  
  [  196.141079]  ? aa_listener_unotif_recv+0x11d/0x260 
  
  [  196.141081]  ? aa_listener_unotif_recv+0x184/0x260 
  
  [  196.141083]  listener_ioctl+0x1e1/0x260
  
  

[Kernel-packages] [Bug 2040250] Re: apparmor notification files verification

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  apparmor notification files verification

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

Bug description:
  apparmor notifications on the 6.5 kernel are failing verification
  between the header size and the returned size.

  When strings are appended to the notification the header size should  
  
  be updated to reflect the correct size. While the size is also
  
  directly returned as part of delivering the notification, the header  
  
  should also be update to conform to specification and allow for   
  
  verification. 
  

  
  If verification is enabled and the notification contains appended 
  
  strings then notifications fail verification and won't be delivered.

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


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

[Kernel-packages] [Bug 2042850] Re: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52
  BMC

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

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2042423
  

  Subject: [mantic:linux]  drm/ast: Add BMC virtual connector


  SRU Justification:

  [Impact]
  On systems with Aspeed 2600 revision 52 GPUs, the display fails to progress 
to the login prompt.  With the commit (added in 6.5.0-6.6)

 commit: 916ae609a033cbb55661905d310ba2358b7621ea
 Author:  Jocelyn Falempe 
 Date:Thu Jul 13 15:41:31 2023 +0200
 Subject: drm/ast: report connection status on Display Port.

   the Aspeed 2600 rev 52 GPUs have issues.

  They need the commit:

  This change was dependant on the upstream change
  commit e329cb53b45da475966c4b2e49f6a4a430f307fa
  Author: Jocelyn Falempe 
  Date: Thu Jul 13 15:41:30 2023 +0200
  Subject: drm/ast: Add BMC virtual connector

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

  
  in order to have the display work correctly on the rev52 GPUs.  


  [Fix]
  With cherry-picking this change, the functionality of BMCs using Aspeed 2600 
rev52 GPUs work as expected, as they did prior to the regression in 6.5.0-6.6. 

  [Test Plan]
  I have tested this on multiple versions of Aspeed 2600 GPU enabled BMCs, and 
the revision 52 systems that required the nomodeset option to boot to the 
prompt, now boot fine and display the login prompt, and there is no regression 
on the other systems.  I have tested this on different Aspeed GPUs, and have 
not seen any regressions, or unexpected behaviour. 

  
  [Where problems could occur]
  As this fixes a regression of  functionality for the mantic kernel's Aspeed 
GPU driver on a very specific version of some BMCs to the state it was was in 
the mantic 6.5.0-5.5 kernel, I think there is little room for regressions.

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


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

[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  arm64 atomic issues cause disk corruption

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

Bug description:
  SRU Justification:

  [Impact]
  The mantic kernel introduced a regression in atomic operations on arm64
  which causes all kinds of problems including file system corruptions,
  since commit "locking/atomic: scripts: restructure fallback
  ifdeffery".

  An example report of people encountering this in UTM with a arm64
  generic kernel: https://github.com/utmapp/UTM/issues/4840

  [Fix]
  Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery"
  from linux-stable v6.5.6

  [Test Plan]

  Boot test on an arm64 vm.

  [Where problems could occur]
  Since this is touching atomic operations, this has a wide impact on the
  kernel.

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


-- 
Mailing list: https://launchpad.net/~kernel-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 changed to intel/vsc/

[You-Sheng Yang]

Verified vsc firmware is identical to what we have at this moment, jammy
version 20220329.git681281e4-0ubuntu3.24.

for f in intel/vsc/*; do
  f="${f##*/}";
  if [ -f vsc/soc_a1_prod/$f ]; then
sum_new=$(md5sum intel/vsc/$f | awk '{print $1}');
sum_cur=$(md5sum vsc/soc_a1_prod/$f | awk '{print $1}');
[ "${sum_new}" = "${sum_cur}" ] || echo "Checksum mismatch for $f";
  else
echo "missing $f in vsc/soc_a1_prod/"
  fi;
done

-- 
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 changed to intel/vsc/

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Frank Heimes]

Thanks Steffen for raising this and bringing this to our attention.
That should obviously not have happen, kernel config changes should be 
propagated to all newer Ubuntu kernel version, until explicitly dropped or 
modified for any other reason.
It looks like we hit a kind of a race condition here. While setting this option 
in jammy, the development of mantic just started and it was missed to enable it 
in the 'unstable' tree at that time.
We are looking into it soon-ish.
I believe that having a kernel in PPA to unblock you is not very helpful, since 
I think you need that kernel signed with the usual (prod.) signature/key (and 
not with a test/dev key coming from the PPA).

Since lunar will reach it's eol in less than 2 weeks, we'll ensure that
the option is set in mantic onwards.

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2048986] Re: audio problem: scratching sound. linux-firmware (20220329.git681281e4-0ubuntu3.24) jammy

[Juerg Haefliger]

Can you please run 'apport-collect 2048986'?

** Tags added: kern-8891

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

Title:
  audio problem: scratching sound. linux-firmware
  (20220329.git681281e4-0ubuntu3.24) jammy

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  After an update from 3.23 to 3.24 my audio started to sound scratchy.
  I'm not really sure if the problem was already in 3.23 because I'm not
  sure if I used sound. But anyway, downgrading to 3.14 fixed the
  problem.

  My HW is identified as "Ellesmere HDMI Audio [Radeon RX 470/480/
  570/580/590] Digital Stereo (HDMI 6)" by the GUI sound app. HardInfo
  says "HDA-Intel - HDA ATI HDMI;HDA-Intel - HD-Audio Generic".

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


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

[Kernel-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

[Launchpad Bug Tracker]

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

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

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

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Frank Heimes]

** Changed in: linux (Ubuntu Lunar)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Noble)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Kleber Sacilotto de Souza]

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

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

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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