[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)

[Jan Kellermann]

We are affected on live machines too.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  [Impact]  

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

   


   
  [Testing] 

   
  This has only been build-tested.  

   


   
  [Potential regression]

   
  Xen guests might not have network access.
  --


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

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

  relevant network config :

  brtctl show :
  br0   8000.XXXno  eno1
     vif1.0

  relevant domU config :

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

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

  No message in dmesg, journal, xen logs..

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


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

[Kernel-packages] [Bug 1996539] Re: Problem linux-tools-common (5.15.0-52.58)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Problem linux-tools-common (5.15.0-52.58)

Status in linux package in Ubuntu:
  Expired

Bug description:
  dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.15.0-52.58_all.deb (--un
  pack):
   trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15
  .0-1017.22
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-tools-common_5.15.0-52.58_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Ubuntu 5.15.0-52.58-generic 5.15.60
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angel  1860 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-11 (156 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 
used by mouse Wireless Desktop 900
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-dq1xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=d93392a1-9ff9-445e-a1bb-e17b947cb8ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/09/2022
  dmi.bios.release: 15.25
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86C8
  dmi.board.vendor: HP
  dmi.board.version: 56.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 56.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd03/09/2022:br15.25:efr56.33:svnHP:pnHPLaptop14-dq1xxx:pvr:rvnHP:rn86C8:rvr56.33:cvnHP:ct10:cvrChassisVersion:sku8AA76UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-dq1xxx
  dmi.product.sku: 8AA76UA#ABA
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angel  1860 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-11 (156 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 
used by mouse Wireless Desktop 900
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-dq1xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=d93392a1-9ff9-445e-a1bb-e17b947cb8ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/09/2022
  dmi.bios.

[Kernel-packages] [Bug 2003031] Re: Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5248
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5248

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5248
   Importance: Unknown
   Status: Unknown

** Tags added: i915

** Summary changed:

- Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not 
allowed without modesets" and crashes in drm_atomic_check_only
+ [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding 
CRTC not allowed without modesets" and crashes in drm_atomic_check_only

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

Title:
  [i915] Using gnome-shell with a USB-C dock causes the kernel to log
  "adding CRTC not allowed without modesets" and crashes in
  drm_atomic_check_only

Status in GNOME Shell:
  Unknown
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   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:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2003031/+subscriptions


-- 
Mailing list: https://launchp

[Kernel-packages] [Bug 2003031] Re: Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only

[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/2003031

Title:
  [i915] Using gnome-shell with a USB-C dock causes the kernel to log
  "adding CRTC not allowed without modesets" and crashes in
  drm_atomic_check_only

Status in GNOME Shell:
  Unknown
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   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:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2003031/+subscriptions


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

[Kernel-packages] [Bug 2003031] Re: Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only

[Launchpad Bug Tracker]

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

** Changed in: mutter (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/2003031

Title:
  [i915] Using gnome-shell with a USB-C dock causes the kernel to log
  "adding CRTC not allowed without modesets" and crashes in
  drm_atomic_check_only

Status in GNOME Shell:
  Unknown
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   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:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2003031/+subscriptions


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

[Kernel-packages] [Bug 2003998] Re: Mouse pointer disappears on the second screen [Failed to post KMS update: drmModeAtomicCommit: Device or resource busy]

[Daniel van Vugt]

*** This bug is a duplicate of bug 2003031 ***
https://bugs.launchpad.net/bugs/2003031

Thanks. The log in comment #3 seems to show this is a duplicate of bug
2003031.

Please also remember to try the workaround in comment #2.


** This bug has been marked a duplicate of bug 2003031
   Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC 
not allowed without modesets" and crashes in drm_atomic_check_only

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

Title:
  Mouse pointer disappears on the second screen [Failed to post KMS
  update: drmModeAtomicCommit: Device or resource busy]

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  On a setup with two screens (primary: laptop screen, secondary:
  external monitor via thunderbolt & docking station), when moving the
  mouse from the primary to the secondary screen, the mouse pointer
  becomes invisible. Waving the mouse and clicking on windows sometimes
  helps.

  Journalctl shows "Failed to post KMS update: drmModeAtomicCommit:
  Device or resource busy" from gnome-shell, which is perfectly timed
  with when I move the mouse pointer to the secondary screen. There's a
  kernel stack trace immediately before that message
  (drm_atomic_nonblocking_commit).

  The issue started occurring 1-2 weeks ago, I suspect immediately after
  installing system updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 27 09:40:39 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-09-01 (512 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (96 days ago)

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


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

[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets"

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel 
says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
+ gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel 
says "adding CRTC not allowed without modesets"

** Summary changed:

- gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel 
says "adding CRTC not allowed without modesets"
+ Using gnome-shell with a USB-C dock crashes the kernel at 
drm_atomic_check_only and logs "adding CRTC not allowed without modesets"

** Summary changed:

- Using gnome-shell with a USB-C dock crashes the kernel at 
drm_atomic_check_only and logs "adding CRTC not allowed without modesets"
+ Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not 
allowed without modesets" and crashes in drm_atomic_check_only

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

Title:
  Using gnome-shell with a USB-C dock causes the kernel to log "adding
  CRTC not allowed without modesets" and crashes in
  drm_atomic_check_only

Status in GNOME Shell:
  Unknown
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   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:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-vi

[Kernel-packages] [Bug 2003728] Re: Enable MGBE ethernet on Orin platforms

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy

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

Title:
  Enable MGBE ethernet on Orin platforms

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
   [Impact]
  Adding these patches enables additional functionality and addresses bugs 
related to the Ubuntu kernel on Orin reference HW.

  Specifically these 3 patches (2 cherry-picks and 1 backport) add
  the MGBE driver.

   [Fix]
  These patches do not constitute a single fix or a set of fixes for bugs 
but instead enable kernel functionality as well as fix kernel bugs related to 
Nvidia HW.

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


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

[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu

[Colin Ian King]

I suspect it was fixed with:

commit b292cafe2dd02d96a07147e4b160927e8399d5cc
Author: Felix Kuehling 
Date:   Wed Sep 21 17:45:59 2022 -0400

drm/amdkfd: Fix UBSAN shift-out-of-bounds warning

This was fixed in initialize_cpsch before, but not in initialize_nocpsch.
Factor sdma bitmap initialization into a helper function to apply the
correct implementation in both cases without duplicating it.

v2: Added a range check

Reported-by: Ellis Michael 
Signed-off-by: Felix Kuehling 
Reviewed-by: Graham Sider 
Signed-off-by: Alex Deucher 


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

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

Title:
  5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  from dmesg

   1.313665] UBSAN: shift-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
  [1.313668] shift exponent 64 is too large for 64-bit type 'long long 
unsigned int'

  there is also a crash but i don't know if it's related.

  1.313671] Call Trace:
  [1.313672]  
  [1.313673]  show_stack+0x52/0x5c
  [1.313676]  dump_stack_lvl+0x4a/0x63
  [1.313678]  dump_stack+0x10/0x16
  [1.313679]  ubsan_epilogue+0x9/0x49
  [1.313680]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [1.313682]  initialize_nocpsch.cold+0x15/0x59 [amdgpu]
  [1.313841]  device_queue_manager_init+0x208/0x3b0 [amdgpu]
  [1.313946]  kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
  [1.314079]  amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
  [1.314178]  amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
  [1.314323]  amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
  [1.314463]  ? do_pci_enable_device+0xdb/0x110
  [1.314466]  amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
  [1.314556]  amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
  [1.314642]  local_pci_probe+0x48/0x90
  [1.314644]  pci_device_probe+0x119/0x1f0
  [1.314645]  really_probe+0x21f/0x420
  [1.314647]  __driver_probe_device+0x119/0x190
  [1.314648]  driver_probe_device+0x23/0xc0
  [1.314650]  __driver_attach+0xbd/0x1f0
  [1.314651]  ? __device_attach_driver+0x120/0x120
  [1.314652]  bus_for_each_dev+0x7c/0xd0
  [1.314654]  driver_attach+0x1e/0x30
  [1.314655]  bus_add_driver+0x148/0x220
  [1.314656]  driver_register+0x95/0x100
  [1.314657]  __pci_register_driver+0x68/0x70
  [1.314659]  amdgpu_init+0x7c/0x1000 [amdgpu]
  [1.314747]  ? 0xc0fc
  [1.314748]  do_one_initcall+0x46/0x1e0
  [1.314750]  ? kmem_cache_alloc_trace+0x19e/0x2e0
  [1.314752]  do_init_module+0x52/0x260
  [1.314753]  load_module+0xb2b/0xbc0
  [1.314754]  __do_sys_finit_module+0xbf/0x120
  [1.314756]  __x64_sys_finit_module+0x18/0x20
  [1.314757]  do_syscall_64+0x59/0xc0
  [1.314758]  ? ksys_lseek+0x85/0xc0
  [1.314759]  ? exit_to_user_mode_prepare+0x37/0xb0
  [1.314761]  ? syscall_exit_to_user_mode+0x27/0x50
  [1.314762]  ? __x64_sys_lseek+0x18/0x20
  [1.314763]  ? do_syscall_64+0x69/0xc0
  [1.314764]  entry_SYSCALL_64_after_hwframe+0x61/0xcb
  [1.314766] RIP: 0033:0x7fef87ab8a3d
  [1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
  [1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX: 
0139
  [1.314770] RAX: ffda RBX: 55d1d00078a0 RCX: 
7fef87ab8a3d
  [1.314771] RDX:  RSI: 7fef87c4f441 RDI: 
0018
  [1.314772] RBP: 0002 R08:  R09: 
0002
  [1.314772] R10: 0018 R11: 0246 R12: 
7fef87c4f441
  [1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15: 
55d1d002eb10
  [1.314774]  
  [1.314778] 


  
  gpu is Amd r 380 tonga 4Gb.
  I was adviced to try 6.0 series of kernel and I dont see the ubsan error 
there but I would like to get the fixes backported 5.15 series.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarkko 1322 F pulseaudio
   /dev/snd/controlC1:  jarkko 1322 F pulseaudio
  CasperMD5json: {
  CurrentDesktop: MATE
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2022-09-19 (71 days ago)
  InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  

[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group

[Stefan Bader]

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

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

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

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

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

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

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  In Progress

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

  [Fix]

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

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

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

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

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


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

[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64

[Stefan Bader]

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

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: Po-Hsu Lin (cypressyew) => Andrea Righi (arighi)

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

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

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

Title:
  cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from
  ubuntu_kernel_selftests hang with non-amd64

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  cmsg_* tests in net tests from ubuntu_kernel_selftests will hang on
  non-amd64 systems and eventually causing "Incomplete" test results on
  RISCV kernels due to the timeout setting.

  This is because of an infinity while loop caused by a char variable
  used here to take the getopt() return value in cmsg_sender.c, it should
  be an int instead.

  [Fix]
  * 1573c68820 ("selftests: net: fix cmsg_so_mark.sh test hang")
  This patch can be cherry-picked into both Kinetic and Lunar, these test
  cases are only available in these newer kernels.

  [Test]
  Compile the patched cmsg_sender.c on a non-amd64 system, and the cmsg_*
  tests will no longer hanging.

  [Where problems could occur ]
  Change limited to testing tools, no actual impact to real functions.

  
  [Original Bug Report]
  Issue found with 5.19.0-1010.11, 5.19.0-1011.12

  This issue does not exist in 5.19.0-1009.10 because the net test can't
  be built by that time.

  Test output:
   Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
    make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
    make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install
    make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
    TAP version 13
    1..1
    # selftests: net: cmsg_so_mark.sh
   Timer expired (5400 sec.), nuking pid 82951

  A manual test shows it will stuck with:
  $ sudo ./cmsg_so_mark.sh
  + NS=ns
  + IP4=172.16.0.1/24
  + TGT4=172.16.0.2
  + IP6=2001:db8:1::1/64
  + TGT6=2001:db8:1::2
  + MARK=1000
  + trap cleanup EXIT
  + ip netns add ns
  + ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647'
  + ip -netns ns link add type dummy
  + ip -netns ns link set dev dummy0 up
  + ip -netns ns addr add 172.16.0.1/24 dev dummy0
  + ip -netns ns addr add 2001:db8:1::1/64 dev dummy0
  + ip -netns ns rule add fwmark 1000 lookup 300
  + ip -6 -netns ns rule add fwmark 1000 lookup 300
  + ip -netns ns route add prohibit any table 300
  + ip -6 -netns ns route add prohibit any table 300
  + BAD=0
  + TOTAL=0
  + for ovr in setsock cmsg both
  + for i in 4 6
  + '[' 4 == 4 ']'
  + TGT=172.16.0.2
  + for p in u i r
  + '[' u == u ']'
  + prot=UDP
  + '[' u == i ']'
  + '[' u == r ']'
  + '[' setsock == setsock ']'
  + m=-M
  + '[' setsock == cmsg ']'
  + '[' setsock == both ']'
  + ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234
  (test stuck here)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+subscriptions


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

[Kernel-packages] [Bug 1999750] Re: Set explicit CC in the headers package

[Stefan Bader]

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

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

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

Title:
  Set explicit CC in the headers package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-5.19 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-hwe-5.19 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-hwe-5.19 source package in Lunar:
  Invalid

Bug description:
  [ Impact ]

   * Currently Ubuntu Linux kernel header packages use stock Makefile as
  shipped by upstream kernel. During linux kernel package build however
  HOSTCC and CC are typically overridden to use explicit complier
  version $(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms module
  build failures as despite all efforts to reuse matching gcc version
  out of .config, various shell scripts / build systems / makefiles do
  not pass the CC variable as a make variable to the end make call that
  is used to build dkms modules. To avoid this, hardcode the correct
  compiler in the linux headers package shipped Makefile. This is
  similar to the Makefile includes that debian ships, albeit with less
  indirections.

  [ Test Plan ]

   * adt-matrix for dkms modules should start to pass correctly

  [ Where problems could occur ]

   * headers package for hwe kernels may demand a newer compiler, for
  which runtime dependency does not exist. dkms package in jammy-updates
  already has explicit dependency on gcc-12 for that reason. Installing
  build-deps of the kernel package will install correct/required
  compilers.

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


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

[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

[Stefan Bader]

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

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

Title:
  powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  When trying to build powerpc tests from ubuntu_kernel_selftests, it 
  will fail with:
  inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3:
  /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may 
be used uninitialized [-Werror=maybe-uninitialized]
     86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
    | ^~~
  cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’:
  cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here
     25 | uint64_t val, expected[2], actual;
    | ^~
  cc1: all warnings being treated as errors

  [Fix]
  * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning"
  This patch can be cherry-picked into Kinetic kernel.

  [Test]
  Apply this patch to the kernel tree and build it with:
  sudo make -C linux/tools/testing/selftests TARGETS=powerpc

  With this error fixed, test compliation can finish without any issue.

  [Where problems could occur]
  Change for test case, no impact to acutal function.

  [Original Bug Report]
  Issue found with K-5.19.0-28-generic on P9 node baltar

  This should not be considered as a regression since
  ubuntu_kernel_selftests will be blocked by the net test crash before
  this powerpc tests can be started. This was found by manually running
  the test.

  Test build failed with:
  gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
  -m64   -no-pie  cycles_with_mmcr2_test.c ../../harness.c ../../utils.c 
../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test
  In file included from /usr/include/stdio.h:906,
   from cycles_with_mmcr2_test.c:6:
  In function ‘printf’,
  inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3:
  /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may 
be used uninitialized [-Werror=maybe-uninitialized]
     86 |   return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
    |  
^~~
  cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’:
  cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here
     25 | uint64_t val, expected[2], actual;
    |^~
  cc1: all warnings being treated as errors
  make[3]: *** [../../../lib.mk:173: 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test]
 Error 1

  Please find attachment for the complete build log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+subscriptions


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

[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress

[Stefan Bader]

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

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

Title:
  Fix W6400 hang after resume of S3 stress

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000299/+subscriptions


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

[Stefan Bader]

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

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in firmware-sof source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions


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

[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

[Ubuntu Foundations Team Bug Bot]

The attachment "zfs-dkms-2.1.4-fix-zero-mac-io-error.patch" seems to be
a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a server that has been running its data volume using ZFS in
  20.04 without any problem. The volume is using ZFS encryption and a
  raidz1-0 configuration. I performed a scrub operations before the
  upgrade and it did not find any problem. After the reboot for the
  upgrade, I was welcomed with the following message:

  status: One or more devices has experienced an error resulting in data
  corruption.  Applications may be affected.
  action: Restore the file in question if possible.  Otherwise restore the
  entire pool from backup.
 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

  The volumes still do not have any checksum error but there are 5 zvols
  that are not accessible. zpool status displays a line similar to the
  below for each of the five:

  errors: Permanent errors have been detected in the following files:   



  tank/data/data:<0x0>

  I run a scrub and it has not identified any problem but the error
  messages are not there and the data is still not available. There are
  10+ other zvols in the zpool that do not have any kind of problem. I
  have been unable to identify any correlation between the zvols that
  are failing.

  I have seen people reporting similar problems in github after the
  20.04 to the 22.04 upgrade (see
  https://github.com/openzfs/zfs/issues/13763). I wonder how widespread
  the problem will be as more people upgrades to 22.04.

  I will try to downgrade the version of zfs in the system and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfsutils-linux 2.1.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Aug 20 22:24:54 2022
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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


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

[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

[Stefan Bader]

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

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

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

Title:
  AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

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

Bug description:
  [Summary]
  No video output on Thunderbolt monitor.
  1. Connect monitor to DUT directly
  2. Connect monitor to DUT via Docking

  System can detect the monitor and able to change display mode but no
  output on the monitor

  [Steps to reproduce]
  1. Boot to OS
  2. Plug an external monitor via thunderbolt port

  [Expected result]
  Display on external monitor normally

  [Actual result]
  No vidoe ouput on external monitor

  [Failure rate]
  3/3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions


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

[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

[Stefan Bader]

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: AceLan Kao (acelankao) => Andrea Righi (arighi)

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

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

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

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

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

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

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

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

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

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

  
  [Test]
  Verified by our QA and ODM.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions


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

[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]

[Stefan Bader]

This is at least staged via stable.

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

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

Title:
  Fix SUT can't displayed after resume from WB/CB with dGFX
  installed(FR:6/10)[RX6300][RX6500]

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

Bug description:
  [Impact]
  SUT can't displayed after resume from WB/CB with dGFX installed.
  Recovery: SUT can display when the DP cable unplug and plug .

  [Fix]
  Use quirk to block the affected SKUes.

  [Test Case]
  1.Install Ubuntu 22.04 on SUT with dGFX card.
  2.Connect the DP cable to the dGFX port.
  3.SUT do power off/restart.
  4.SUT can display.

  [Where problems could occur]
  Add SKU's id to a quirk table, the impact would be small.

  [Other Info]
  * For the pure Jammy, Confronted the error of compilation.
  1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work
  ~~~
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: 
implicit declaration of function 'hpd_rx_irq_create_  workqueue'; did you 
mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration]
  18848  1449 | adev->dm.hpd_rx_offload_wq = 
hpd_rx_irq_create_workqueue(adev->dm.dc);
  18849   |  ^~~
  18850   |  hdcp_create_workqueue
  ~~~
  2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter
  ~~~
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: 
implicit declaration of function 'dm_should_disable_  stutter' 
[-Werror=implicit-function-declaration]
  18838  1505 | if (dm_should_disable_stutter(adev->pdev))
  ~~~

  * hpd_disconnect_quirk_table is placed to the different location on
  J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all.

  * Result from CBD
  ~~~
  Jammy,

  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-820f542767e6-ESq2
  remote: * 192/672 cores busy (2/7 hosts), 0 builds queued
  remote: 2022-12-15 17:09:15  kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK
  remote: 2022-12-15 17:11:13  kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK
  remote: 2022-12-15 17:07:30  kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK
  remote: 2022-12-15 17:10:17  kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK
  remote: 2022-12-15 17:04:55  kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK
  remote: 

  To 54.69.112.110:jammy.git
  ~~~
  Kinetic

  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-kinetic-857358673609-X4Nz
  remote: * 0/672 cores busy (0/7 hosts), 0 builds queued
  remote: 2022-12-15 17:41:37  kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK
  remote: 2022-12-15 17:42:13  kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK
  remote: 2022-12-15 17:35:54  kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK
  remote: 2022-12-15 17:40:54  kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK
  remote: 2022-12-15 17:34:47  kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK
  remote: 

  To 54.69.112.110:kinetic.git
  ~~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions


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

[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

[Walter]

So. I'm affected as well.

Luckily there is a patch already:
https://patch-diff.githubusercontent.com/raw/openzfs/zfs/pull/14161.patch


HOW TO APPLY
-

=== Step 1: get patch ===

(see zfs-dkms-2.1.4-fix-zero-mac-io-error.patch attachment)


=== Step 2: install zfs-dkms and patch it ===

# apt-get install zfs-dkms
(you may get questions about enrolling MOK keys: do as you're told)

# cd /usr/src/zfs-2.1.4

# dkms remove -m zfs -v 2.1.4 -k $(uname -r)

# dkms status
(should yield nothing)

# patch -p1 < /tmp/zfs-dkms-2.1.4-fix-zero-mac-io-error.patch

# dkms install -m zfs -v 2.1.4 -k $(uname -r)
(rebuild the module again, with patch this time)

# update-initramfs -uk $(uname -r)
(if you run zfs on the root fs, you'll probably want this)

# reboot
(and cross fingers)


=== Step 3: confirm that the module is loaded ===

# modinfo zfs | grep ^version:
version:2.1.4-0ubuntu0.1+ossomacfix

(zfs mount should now work again, no "Input/Output error")



CLEANUP/THOUGHTS


- If you have 'zpool status -v' errors, you'll need to clean them with a
'zpool scrub '. If you got to this bug report _before_ trying to
mount, you might be okay.

- I'm not sure yet, but I think you can mount/unmount datasets and that
might correct the MAC everywhere. If it does, you can remove the dkms
module once you've done this. (Needs testing.)

- I haven't tested syncing data from (a patched) 22.04 (zfs-linux-2.1.4)
to a 20.04 (zfs-linux-0.8.3) yet. I try to be a little careful at first
and see how it goes.

- I think this bug needs a HIGH severity label.

Cheers,
Walter Doekes
OSSO B.V.


** Patch added: "zfs-dkms-2.1.4-fix-zero-mac-io-error.patch"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+attachment/5643985/+files/zfs-dkms-2.1.4-fix-zero-mac-io-error.patch

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a server that has been running its data volume using ZFS in
  20.04 without any problem. The volume is using ZFS encryption and a
  raidz1-0 configuration. I performed a scrub operations before the
  upgrade and it did not find any problem. After the reboot for the
  upgrade, I was welcomed with the following message:

  status: One or more devices has experienced an error resulting in data
  corruption.  Applications may be affected.
  action: Restore the file in question if possible.  Otherwise restore the
  entire pool from backup.
 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

  The volumes still do not have any checksum error but there are 5 zvols
  that are not accessible. zpool status displays a line similar to the
  below for each of the five:

  errors: Permanent errors have been detected in the following files:   



  tank/data/data:<0x0>

  I run a scrub and it has not identified any problem but the error
  messages are not there and the data is still not available. There are
  10+ other zvols in the zpool that do not have any kind of problem. I
  have been unable to identify any correlation between the zvols that
  are failing.

  I have seen people reporting similar problems in github after the
  20.04 to the 22.04 upgrade (see
  https://github.com/openzfs/zfs/issues/13763). I wonder how widespread
  the problem will be as more people upgrades to 22.04.

  I will try to downgrade the version of zfs in the system and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfsutils-linux 2.1.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Aug 20 22:24:54 2022
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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


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

[Kernel-packages] [Bug 2004171] [NEW] 2022.08.12 new upstream release

[Dimitri John Ledkov]

*** This bug is a security vulnerability ***

Public security bug reported:

[Impact]

New upstream release. This is a database of wireless regulations, and
should updated in all releases to ensure users have the most up-to-date
regulatory information.

[Test Case]

Following reboot after installing the new database, it should be
possible to query and change the regulatory domain using 'iw reg get'
and 'iw reg set'.

[Where problems could occur]

If crda or the kernel is unable to use the new database, users may be
stuck using the default "world" regulatory domain which is quite
restrictive, therefore they may be unable to use wireless channels that
they were able to use previously. Regulatory rules may have also changed
for the user's region, which could also make some channels unusable, but
this would not be a bug.

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: wireless-regdb (Ubuntu Lunar)
 Importance: Undecided
 Status: New

** Also affects: wireless-regdb (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Information type changed from Public to Public Security

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

Title:
  2022.08.12 new upstream release

Status in wireless-regdb package in Ubuntu:
  New
Status in wireless-regdb source package in Trusty:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in wireless-regdb source package in Bionic:
  New
Status in wireless-regdb source package in Focal:
  New
Status in wireless-regdb source package in Jammy:
  New
Status in wireless-regdb source package in Kinetic:
  New
Status in wireless-regdb source package in Lunar:
  New

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2004171/+subscriptions


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

[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]

[Stefan Bader]

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

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

Title:
  Fix SUT can't displayed after resume from WB/CB with dGFX
  installed(FR:6/10)[RX6300][RX6500]

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

Bug description:
  [Impact]
  SUT can't displayed after resume from WB/CB with dGFX installed.
  Recovery: SUT can display when the DP cable unplug and plug .

  [Fix]
  Use quirk to block the affected SKUes.

  [Test Case]
  1.Install Ubuntu 22.04 on SUT with dGFX card.
  2.Connect the DP cable to the dGFX port.
  3.SUT do power off/restart.
  4.SUT can display.

  [Where problems could occur]
  Add SKU's id to a quirk table, the impact would be small.

  [Other Info]
  * For the pure Jammy, Confronted the error of compilation.
  1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work
  ~~~
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: 
implicit declaration of function 'hpd_rx_irq_create_  workqueue'; did you 
mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration]
  18848  1449 | adev->dm.hpd_rx_offload_wq = 
hpd_rx_irq_create_workqueue(adev->dm.dc);
  18849   |  ^~~
  18850   |  hdcp_create_workqueue
  ~~~
  2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter
  ~~~
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: 
implicit declaration of function 'dm_should_disable_  stutter' 
[-Werror=implicit-function-declaration]
  18838  1505 | if (dm_should_disable_stutter(adev->pdev))
  ~~~

  * hpd_disconnect_quirk_table is placed to the different location on
  J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all.

  * Result from CBD
  ~~~
  Jammy,

  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-820f542767e6-ESq2
  remote: * 192/672 cores busy (2/7 hosts), 0 builds queued
  remote: 2022-12-15 17:09:15  kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK
  remote: 2022-12-15 17:11:13  kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK
  remote: 2022-12-15 17:07:30  kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK
  remote: 2022-12-15 17:10:17  kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK
  remote: 2022-12-15 17:04:55  kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK
  remote: 

  To 54.69.112.110:jammy.git
  ~~~
  Kinetic

  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-kinetic-857358673609-X4Nz
  remote: * 0/672 cores busy (0/7 hosts), 0 builds queued
  remote: 2022-12-15 17:41:37  kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK
  remote: 2022-12-15 17:42:13  kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK
  remote: 2022-12-15 17:35:54  kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK
  remote: 2022-12-15 17:40:54  kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK
  remote: 2022-12-15 17:34:47  kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK
  remote: 

  To 54.69.112.110:kinetic.git
  ~~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions


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

[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]

[Stefan Bader]

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

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

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

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

Title:
  Fix SUT can't displayed after resume from WB/CB with dGFX
  installed(FR:6/10)[RX6300][RX6500]

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

Bug description:
  [Impact]
  SUT can't displayed after resume from WB/CB with dGFX installed.
  Recovery: SUT can display when the DP cable unplug and plug .

  [Fix]
  Use quirk to block the affected SKUes.

  [Test Case]
  1.Install Ubuntu 22.04 on SUT with dGFX card.
  2.Connect the DP cable to the dGFX port.
  3.SUT do power off/restart.
  4.SUT can display.

  [Where problems could occur]
  Add SKU's id to a quirk table, the impact would be small.

  [Other Info]
  * For the pure Jammy, Confronted the error of compilation.
  1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work
  ~~~
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: 
implicit declaration of function 'hpd_rx_irq_create_  workqueue'; did you 
mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration]
  18848  1449 | adev->dm.hpd_rx_offload_wq = 
hpd_rx_irq_create_workqueue(adev->dm.dc);
  18849   |  ^~~
  18850   |  hdcp_create_workqueue
  ~~~
  2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter
  ~~~
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: 
implicit declaration of function 'dm_should_disable_  stutter' 
[-Werror=implicit-function-declaration]
  18838  1505 | if (dm_should_disable_stutter(adev->pdev))
  ~~~

  * hpd_disconnect_quirk_table is placed to the different location on
  J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all.

  * Result from CBD
  ~~~
  Jammy,

  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-820f542767e6-ESq2
  remote: * 192/672 cores busy (2/7 hosts), 0 builds queued
  remote: 2022-12-15 17:09:15  kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK
  remote: 2022-12-15 17:11:13  kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK
  remote: 2022-12-15 17:07:30  kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK
  remote: 2022-12-15 17:10:17  kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK
  remote: 2022-12-15 17:04:55  kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK
  remote: 

  To 54.69.112.110:jammy.git
  ~~~
  Kinetic

  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-kinetic-857358673609-X4Nz
  remote: * 0/672 cores busy (0/7 hosts), 0 builds queued
  remote: 2022-12-15 17:41:37  kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK
  remote: 2022-12-15 17:42:13  kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK
  remote: 2022-12-15 17:35:54  kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK
  remote: 2022-12-15 17:40:54  kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK
  remote: 2022-12-15 17:34:47  kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK
  remote: 

  To 54.69.112.110:kinetic.git
  ~~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions


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

[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian

[Dimitri John Ledkov]

** Also affects: wireless-regdb (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: crda (Ubuntu)
   Status: New => Fix Released

** Changed in: crda (Ubuntu Jammy)
   Status: New => Fix Released

** Description changed:

  Debian has just removed the crda package from the archive, stating that
  it is obsolete with current kernels:
  
-   https://bugs.debian.org/1003903
+   https://bugs.debian.org/1003903
  
  We need someone to determine if this is accurate for Ubuntu as well, and
  if so, update the kernel packaging to not depend on crda anymore so it
  can be removed.
+ 
+ wireless-regdb should stop shipping /lib/crda files which only removed
+ crda package used to use.

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

Title:
  dependency on crda obsolete according to Debian

Status in crda package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-lowlatency package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in wireless-regdb package in Ubuntu:
  New
Status in crda source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-lowlatency source package in Jammy:
  Fix Released
Status in linux-oracle source package in Jammy:
  Fix Released
Status in linux-raspi source package in Jammy:
  Fix Released
Status in wireless-regdb source package in Jammy:
  New
Status in crda package in Debian:
  Fix Released

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

    https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

  wireless-regdb should stop shipping /lib/crda files which only removed
  crda package used to use.

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

This fix will be included in grub2-unsigned/2.06-2ubuntu14.1 for
kinetic, jammy, focal, bionic. Binaries have been built in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
for kinetic.

Signing request: https://answers.launchpad.net/canonical-signing-
jobs/+question/704589

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: grub2-signed (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: grub2-signed (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: grub2-signed (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Also affects: grub2-signed (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools (Ubuntu Kinetic)

** No longer affects: initramfs-tools (Ubuntu Jammy)

** No longer affects: initramfs-tools (Ubuntu Focal)

** No longer affects: initramfs-tools (Ubuntu Bionic)

** No longer affects: linux (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu Jammy)

** No longer affects: linux (Ubuntu Kinetic)

** Description changed:

  [Workaround]
  
  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125
  
  [Impact]
  
   * In some cases, if the users’ initramfs grow bigger, then it’ll likely
  not be able to be loaded by grub2.
  
   * Some real cases from OEM projects:
  
  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts
  the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the
  gfxpayload=auto will remain to use 4K resolution since it’s what EFI
  POST passed.
  
  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:
  
  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```
  
  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:
  
  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 00

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  md: Replace snprintf with scnprintf

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

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  Fix RPL-S support on powercap/intel_rapl

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

Bug description:
  [Impact]
  proc_thermal driver is not loaded

  [Fix]
  Add RPL-S id on device id table of powercap/intel_rapl.

  [Test Case]
  1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal

  [Where problems could occur]
  Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions


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

[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

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

Bug description:
  [Impact]
  turbostat doesn't show the correct fields for RPL-S.
  This's a wrong column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI

  [Fix]
  Add RPL-S support in turbostat

  [Test Case]
  1. run "turbostat --list"
  2. check the output, this is a correct column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_%

  [Where problems could occur]
  Low, just add a devcie id to support RPL-S.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991365/+subscriptions


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

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

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

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-module

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

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

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions


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

[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  TEE Support for CCP driver

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for of AMD Secure Processor device for PCI ID 0x14CA.

  [Fix]

  A patch is being proposed in upstream and CC-ed stable.

  [Test Case]

  Without a proper fix, following error appears in dmesg:

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

  [Where problems could occur]

  This adds a new driver data entry to support ccp device that provides
  both sev and tee feature at the same time.

  [Other Info]

  While this is proposed to stable 5.15+, all kernels >= 5.15 are
  nominated for fix.

  == original bug description ==

  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991608/+subscriptions


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

[Kernel-packages] [Bug 1991974] Re: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking

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

Bug description:
  [SRU Justification]

  [Impact]

  AMD Yellow Carp system hang on HDMI plug in/out over dock station.

  [Fix]

  5 patches from mainline kernel v5.16 to be backported.

  [Test Case]

  Plug and unplug HDMI cable connected external monitor on a docking
  station connected to HP Lockheed platform to try trigger system hang.

  [Where problems could occur]

  This series tries to address null state of MST link encoder, and no know
  fix commits for them ever since till current mainline HEAD.

  [Other Info]

  While this is already available in v5.16 kernel and on, only 5.15 and
  oem-5.14 are nominated for fix.

  == original bug description ==

  In order to resolve system hang during docking scenario with HDMI plug
  in/out, these patches are needed into hwe-5.15.

  v5.16
  43dc2ad5 drm/amd/display: Fix MST link encoder availability check
  e3ab29aa drm/amd/display: Fix for link encoder access for MST
  7fb52632 drm/amd/display: FEC configuration for dpia links
  ed0ffb5d drm/amd/display: FEC configuration for dpia links in MST mode
  c9beecc5 drm/amd/display: Add work around for tunneled MST

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991974/+subscriptions


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

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

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

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

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


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

[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  5.15.0-53-generic no longer boots

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

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

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

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

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

  == Original Bug Report ==

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

  New kernel version: 5.15.0-53.59

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

   enp37s0   no wireless extensions.

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

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-aws-5.15

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

Title:
  Fix ath11k deadlock on WCN6855

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

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

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995041/+subscriptions


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

[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  alsa: soc: the kernel print UBSAN calltrace on the machine with
  cs35l41 codec

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

Bug description:
  The cs35l41 codec driver was backported to Jammy kernel a couple of
  months ago, recently the Jammy kernel was adopted as the hwe kernel
  for OEM machines and with this kernel the UBSAN calltrace was seen,
  need to backport these 2 patches. Kinetic kernel already has the
  patches, so this SRU is only for Jammy kernel.

  [Impact]
  Install the 5.15 hwe kernel on the machines with cs35l41
  codec, after booting and check the dmesg, there is a UBSAN calltrace.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, check the dmesg, there
  is no UBSAN calltrace, and test the audio functions, all input
  and output devices coudl work as well as before.

  
  [Where problems could occur]
  The patch only affects the cirruslogic asoc codec driver, if it
  could introduce the regression, it will be on the machines with
  cs codec, and it will make the audio driver initialization fail
  and make the system lose the audio function. But this possibility
  is very low, we tested the patches on many oem machines, all
  worked well.

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


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

[Kernel-packages] [Bug 2003998] Re: Mouse pointer disappears on the second screen [Failed to post KMS update: drmModeAtomicCommit: Device or resource busy]

[Jerzy Husakowski]

Added journalctl output with kernel stacktrace.

** Attachment added: "drm_atomic_nonblocking_commit.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003998/+attachment/5643974/+files/drm_atomic_nonblocking_commit.log

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

Title:
  Mouse pointer disappears on the second screen [Failed to post KMS
  update: drmModeAtomicCommit: Device or resource busy]

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  On a setup with two screens (primary: laptop screen, secondary:
  external monitor via thunderbolt & docking station), when moving the
  mouse from the primary to the secondary screen, the mouse pointer
  becomes invisible. Waving the mouse and clicking on windows sometimes
  helps.

  Journalctl shows "Failed to post KMS update: drmModeAtomicCommit:
  Device or resource busy" from gnome-shell, which is perfectly timed
  with when I move the mouse pointer to the secondary screen. There's a
  kernel stack trace immediately before that message
  (drm_atomic_nonblocking_commit).

  The issue started occurring 1-2 weeks ago, I suspect immediately after
  installing system updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 27 09:40:39 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-09-01 (512 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (96 days ago)

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


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

[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.3

---
alsa-ucm-conf (1.2.6.3-1ubuntu1.3) jammy; urgency=medium

  * d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
 - Backport patch to fix micmute LED. (LP: #2002373)

  * d/p/sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch
 - Backport patch to fix capture switch default value. (LP: #2001896)

 -- Andy Chi   Tue, 17 Jan 2023 17:36:21 +0800

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions


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

[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.3

---
alsa-ucm-conf (1.2.6.3-1ubuntu1.3) jammy; urgency=medium

  * d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
 - Backport patch to fix micmute LED. (LP: #2002373)

  * d/p/sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch
 - Backport patch to fix capture switch default value. (LP: #2001896)

 -- Andy Chi   Tue, 17 Jan 2023 17:36:21 +0800

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions


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

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

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

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.

[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix RPL-S support on powercap/intel_rapl

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

Bug description:
  [Impact]
  proc_thermal driver is not loaded

  [Fix]
  Add RPL-S id on device id table of powercap/intel_rapl.

  [Test Case]
  1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal

  [Where problems could occur]
  Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions


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

[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

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

Bug description:
  [Impact]
  turbostat doesn't show the correct fields for RPL-S.
  This's a wrong column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI

  [Fix]
  Add RPL-S support in turbostat

  [Test Case]
  1. run "turbostat --list"
  2. check the output, this is a correct column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_%

  [Where problems could occur]
  Low, just add a devcie id to support RPL-S.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991365/+subscriptions


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

[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  TEE Support for CCP driver

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for of AMD Secure Processor device for PCI ID 0x14CA.

  [Fix]

  A patch is being proposed in upstream and CC-ed stable.

  [Test Case]

  Without a proper fix, following error appears in dmesg:

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

  [Where problems could occur]

  This adds a new driver data entry to support ccp device that provides
  both sev and tee feature at the same time.

  [Other Info]

  While this is proposed to stable 5.15+, all kernels >= 5.15 are
  nominated for fix.

  == original bug description ==

  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991608/+subscriptions


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

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

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

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions


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

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  md: Replace snprintf with scnprintf

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

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

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

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix ath11k deadlock on WCN6855

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

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

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995041/+subscriptions


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1991974] Re: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking

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

Bug description:
  [SRU Justification]

  [Impact]

  AMD Yellow Carp system hang on HDMI plug in/out over dock station.

  [Fix]

  5 patches from mainline kernel v5.16 to be backported.

  [Test Case]

  Plug and unplug HDMI cable connected external monitor on a docking
  station connected to HP Lockheed platform to try trigger system hang.

  [Where problems could occur]

  This series tries to address null state of MST link encoder, and no know
  fix commits for them ever since till current mainline HEAD.

  [Other Info]

  While this is already available in v5.16 kernel and on, only 5.15 and
  oem-5.14 are nominated for fix.

  == original bug description ==

  In order to resolve system hang during docking scenario with HDMI plug
  in/out, these patches are needed into hwe-5.15.

  v5.16
  43dc2ad5 drm/amd/display: Fix MST link encoder availability check
  e3ab29aa drm/amd/display: Fix for link encoder access for MST
  7fb52632 drm/amd/display: FEC configuration for dpia links
  ed0ffb5d drm/amd/display: FEC configuration for dpia links in MST mode
  c9beecc5 drm/amd/display: Add work around for tunneled MST

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991974/+subscriptions


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

[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

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


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

[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  alsa: soc: the kernel print UBSAN calltrace on the machine with
  cs35l41 codec

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

Bug description:
  The cs35l41 codec driver was backported to Jammy kernel a couple of
  months ago, recently the Jammy kernel was adopted as the hwe kernel
  for OEM machines and with this kernel the UBSAN calltrace was seen,
  need to backport these 2 patches. Kinetic kernel already has the
  patches, so this SRU is only for Jammy kernel.

  [Impact]
  Install the 5.15 hwe kernel on the machines with cs35l41
  codec, after booting and check the dmesg, there is a UBSAN calltrace.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, check the dmesg, there
  is no UBSAN calltrace, and test the audio functions, all input
  and output devices coudl work as well as before.

  
  [Where problems could occur]
  The patch only affects the cirruslogic asoc codec driver, if it
  could introduce the regression, it will be on the machines with
  cs codec, and it will make the audio driver initialization fail
  and make the system lose the audio function. But this possibility
  is very low, we tested the patches on many oem machines, all
  worked well.

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


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

[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  5.15.0-53-generic no longer boots

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

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

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

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

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

  == Original Bug Report ==

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

  New kernel version: 5.15.0-53.59

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

   enp37s0   no wireless extensions.

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

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


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

[Kernel-packages] [Bug 1998857] Re: tick/rcu: Stop allowing RCU_SOFTIRQ in idle

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  tick/rcu: Stop allowing RCU_SOFTIRQ in idle

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

Bug description:
  * Explain the bug
  RCU_SOFTIRQ used to be special in that it could be raised on purpose
  within the idle path to prevent from stopping the tick. Some code still
  prevents from unnecessary warnings related to this specific behaviour
  while entering in dynticks-idle mode.

  However the nohz layout has changed quite a bit in ten years, and the
  removal of CONFIG_RCU_FAST_NO_HZ has been the final straw to this
  safe-conduct. Now the RCU_SOFTIRQ vector is expected to be raised from
  sane places.

  * Brief explanation of fixes
   
  Stop allowing RCU_SOFTIRQ in idle
   
  * How to test
   
  In boot dmesg, the warning should be gone.
   
  * What it could break.
   
  N/A

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


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

[Kernel-packages] [Bug 1998863] Re: mlxbf-pmc: Fix event string typo

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  mlxbf-pmc: Fix event string typo

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

Bug description:
  SRU Justification:

  [Impact]

  Due to a typo, duplicate events are shown

  [Fix]

  * Fix event name typo.

  [Test Case]

  * cd /sys/class/hwmon/hwmon0/tilenetX ("X" may be 0..7)
  root@localhost:/sys/class/hwmon/hwmon0/tilenet3# cat event_list | grep CRED
  15: CDN_DIAG_N_OUT_OF_CRED
  16: CDN_DIAG_S_OUT_OF_CRED
  17: CDN_DIAG_E_OUT_OF_CRED
  18: CDN_DIAG_W_OUT_OF_CRED
  19: CDN_DIAG_C_OUT_OF_CRED
  25: DDN_DIAG_N_OUT_OF_CRED
  26: DDN_DIAG_S_OUT_OF_CRED
  27: DDN_DIAG_E_OUT_OF_CRED
  28: DDN_DIAG_W_OUT_OF_CRED
  29: DDN_DIAG_C_OUT_OF_CRED
  35: NDN_DIAG_N_OUT_OF_CRED  <== Incorrectly was set to NDN_DIAG_S_OUT_OF_CRED
  36: NDN_DIAG_S_OUT_OF_CRED
  37: NDN_DIAG_E_OUT_OF_CRED
  38: NDN_DIAG_W_OUT_OF_CRED
  39: NDN_DIAG_C_OUT_OF_CRED
   

  [Regression Potential]

  * Duplicate events still get shown

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


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

[Kernel-packages] [Bug 1999309] Re: mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC

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

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to for eMMC host setting on BlueField-3 SoC to be 
consistent with UEFI setting and also for stability reason.

  [Fix]
  The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC.

  [Test Case]
  Same functionality as on BlueField-1/2.

  [Regression Potential]
  Can be considered minimum since similar functionality was already included in 
the focal branch for BlueField-1/2. The driver is different, but functionality 
and eMMC device files will be the same.

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


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

[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu4

---
alsa-ucm-conf (1.2.6.3-1ubuntu4) kinetic; urgency=medium

  * d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
 - Backport patch to fix micmute LED. (LP: #2002373)

  * d/p/sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch
 - Backport patch to fix capture switch default value. (LP: #2001896)

 -- Andy Chi   Tue, 17 Jan 2023 17:46:54 +0800

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions


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

[Kernel-packages] [Bug 2001896] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  sof-hda-dsp internal mic default off after fresh install

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Device with sof-hda-dsp sound card has internal mic off after fresh install

  [Test Plan]
  On the platform with sofhdadsp sound card
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal mic should be on by default

  [Where problems could occur]
  The change takes place on platform with sof-hda-dsp sound card, and it only 
be executed during boot sequence, it won't impact the stored state.
  However, it will change user default expectation after fresh installation.

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/259

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions


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

[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu4

---
alsa-ucm-conf (1.2.6.3-1ubuntu4) kinetic; urgency=medium

  * d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
 - Backport patch to fix micmute LED. (LP: #2002373)

  * d/p/sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch
 - Backport patch to fix capture switch default value. (LP: #2001896)

 -- Andy Chi   Tue, 17 Jan 2023 17:46:54 +0800

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions


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

[Kernel-packages] [Bug 2002373] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Mic Mute LED doesn't work on DMIC laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in alsa-ucm-conf source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  Mic mute LED doesn't work on Intel-based HP laptops.

  [Fix]
  Due to recent change on how kernel creates sound LEDs, there are two captures 
are registered, one from SoF and one from HDA. The SoF one is the "real" 
capture system uses.

  Since physical LED only gets light up when _all_ captures are muted,
  detach the HDA one so micmute LED only need to consider SoF capture's
  mute status.

  [Test]
  The mic mute LED works again on DMIC laptops.

  The legacy HDA systems are unaffected.

  [Where problems could occur]
  Theoretically the system may have more than two internal captures registered, 
then disabling one will not be enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions


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

[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

[Launchpad Bug Tracker]

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

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

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a server that has been running its data volume using ZFS in
  20.04 without any problem. The volume is using ZFS encryption and a
  raidz1-0 configuration. I performed a scrub operations before the
  upgrade and it did not find any problem. After the reboot for the
  upgrade, I was welcomed with the following message:

  status: One or more devices has experienced an error resulting in data
  corruption.  Applications may be affected.
  action: Restore the file in question if possible.  Otherwise restore the
  entire pool from backup.
 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

  The volumes still do not have any checksum error but there are 5 zvols
  that are not accessible. zpool status displays a line similar to the
  below for each of the five:

  errors: Permanent errors have been detected in the following files:   



  tank/data/data:<0x0>

  I run a scrub and it has not identified any problem but the error
  messages are not there and the data is still not available. There are
  10+ other zvols in the zpool that do not have any kind of problem. I
  have been unable to identify any correlation between the zvols that
  are failing.

  I have seen people reporting similar problems in github after the
  20.04 to the 22.04 upgrade (see
  https://github.com/openzfs/zfs/issues/13763). I wonder how widespread
  the problem will be as more people upgrades to 22.04.

  I will try to downgrade the version of zfs in the system and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfsutils-linux 2.1.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Aug 20 22:24:54 2022
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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


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

[Kernel-packages] [Bug 2004146] [NEW] Lunar update: v6.1.7 upstream stable release

[Paolo Pisati]

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:

   v6.1.7 upstream stable release
   from git://git.kernel.org/


Linux 6.1.7
pinctrl: amd: Add dynamic debugging for active GPIOs
Revert "usb: ulpi: defer ulpi_register on ulpi_read_id timeout"
block: handle bio_split_to_limits() NULL return
io_uring/io-wq: only free worker if it was allocated for creation
io_uring/io-wq: free worker if task_work creation is canceled
drm/i915: Fix CFI violations in gt_sysfs
io_uring/poll: attempt request issue after racy poll wakeup
io_uring: lock overflowing for IOPOLL
efi: fix NULL-deref in init error path
ALSA: usb-audio: Fix possible NULL pointer dereference in 
snd_usb_pcm_has_fixed_rate()
platform/x86/amd: Fix refcount leak in amd_pmc_probe
platform/surface: aggregator: Add missing call to ssam_request_sync_free()
bnxt: make sure we return pages to the pool
net: hns3: fix wrong use of rss size during VF rss config
net: lan966x: check for ptp to be enabled in lan966x_ptp_deinit()
igc: Fix PPS delta between two synchronized end-points
perf kmem: Support field "node" in evsel__process_alloc_event() coping with 
recent tracepoint restructuring
perf kmem: Support legacy tracepoints
perf build: Properly guard libbpf includes
octeontx2-pf: Fix resource leakage in VF driver unbind
selftests/net: l2_tos_ttl_inherit.sh: Ensure environment cleanup on failure.
selftests/net: l2_tos_ttl_inherit.sh: Run tests in their own netns.
selftests/net: l2_tos_ttl_inherit.sh: Set IPv6 addresses with "nodad".
net/mlx5e: Fix macsec possible null dereference when updating MAC security 
entity (SecY)
net/mlx5e: Fix macsec ssci attribute handling in offload path
net/mlx5e: Don't support encap rules with gbp option
net/mlx5: Fix ptp max frequency adjustment range
net/mlx5e: IPoIB, Fix child PKEY interface stats on rx path
net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent
net/mlx5e: IPoIB, Block queue count configuration when sub interfaces are 
present
net/mlx5e: Verify dev is present for fix features ndo
net/mlx5: Fix command stats access after free
net/mlx5e: TC, Keep mod hdr actions after mod hdr alloc
net/mlx5: check attr pointer validity before dereferencing it
Revert "r8169: disable detection of chip version 36"
net/sched: act_mpls: Fix warning during failed attribute validation
drm/vmwgfx: Remove rcu locks from user resources
drm/vmwgfx: Remove vmwgfx_hashtab
drm/vmwgfx: Refactor ttm reference object hashtable to use linux/hashtable.
drm/vmwgfx: Refactor resource validation hashtable to use linux/hashtable 
implementation.
drm/vmwgfx: Remove ttm object hashtable
drm/vmwgfx: Refactor resource manager's hashtable to use linux/hashtable 
implementation.
drm/vmwgfx: Write the driver id registers
ice: Add check for kzalloc
ice: Fix potential memory leak in ice_gnss_tty_write()
drm/amdgpu: Fix potential NULL dereference
tools/nolibc: fix the O_* fcntl/open macro definitions for riscv
tools/nolibc: restore mips branch ordering in the _start block
ASoC: qcom: Fix building APQ8016 machine driver without SOUNDWIRE
af_unix: selftest: Fix the size of the parameter to connect()
gro: take care of DODGY packets
gro: avoid checking for a failed search
nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
hvc/xen: lock console list traversal
sched/core: Fix arch_scale_freq_tick() on tickless systems
octeontx2-af: Fix LMAC config in cgx_lmac_rx_tx_enable
nfsd: fix handling of cached open files in nfsd4_open codepath
nfsd: rework refcounting in filecache
NFSD: Add an nfsd_file_fsync tracepoint
nfsd: reorganize filecache.c
nfsd: remove the pages_flushed statistic from filecache
NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection
NFSD: Revert "NFSD: NFSv4 CLOSE should release an nfsd_file immediately"
NFSD: Pass the target nfsd_file to nfsd_commit()
tipc: fix unexpected link reset due to discovery messages
stmmac: dwmac-mediatek: remove the dwmac_fix_mac_speed
ALSA: usb-audio: Relax hw constraints for implicit fb sync
ALSA: usb-audio: Make sure to stop endpoints before closing EPs
mtd: cfi: allow building spi-intel standalone
mtd: parsers: scpart: fix __udivdi3 undefined on mips
ASoC: wm8904: fix wrong outputs volume after power reactivation
drm/msm/dpu: Fix memory leak in msm_mdss_parse_data_bus_icc_path
drm/msm/dpu: Fix some kernel-doc comments
ASoC: Intel: sof-nau8825: fix module alias overflow
ASoC: Intel: sof_nau8825: support rt1015p speaker amplifier
ASoC: Intel: fix sof-nau8825 link failure
scsi: ufs: core: WLUN suspend SSU/enter hibern8 fail recovery
scsi: mpi3mr:

[Kernel-packages] [Bug 2004147] [NEW] Lunar update: v6.1.8 upstream stable release

[Paolo Pisati]

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:

   v6.1.8 upstream stable release
   from git://git.kernel.org/


Linux 6.1.8
soc: qcom: apr: Make qcom,protection-domain optional again
Revert "wifi: mac80211: fix memory leak in ieee80211_if_add()"
block: mq-deadline: Rename deadline_is_seq_writes()
net/mlx5: fix missing mutex_unlock in mlx5_fw_fatal_reporter_err_work()
octeontx2-pf: Fix the use of GFP_KERNEL in atomic context on rt
net/ulp: use consistent error code when blocking ULP
octeontx2-pf: Avoid use of GFP_KERNEL in atomic context
drm/amdgpu: correct MEC number for gfx11 APUs
drm/amdgpu: add tmz support for GC IP v11.0.4
drm/amdgpu: add tmz support for GC 11.0.1
drm/amdgpu: enable GFX Clock Gating control for GC IP v11.0.4
drm/amdgpu: enable GFX Power Gating for GC IP v11.0.4
drm/amdgpu: enable GFX IP v11.0.4 CG support
drm/amdgpu: enable PSP IP v13.0.11 support
drm/amdgpu/discovery: enable nbio support for NBIO v7.7.1
drm/amdgpu/pm: use the specific mailbox registers only for SMU IP v13.0.4
drm/amdgpu/soc21: add mode2 asic reset for SMU IP v13.0.11
drm/amdgpu/pm: add GFXOFF control IP version check for SMU IP v13.0.11
drm/amdgpu: add smu 13 support for smu 13.0.11
drm/amdgpu/pm: enable swsmu for SMU IP v13.0.11
drm/amdgpu/discovery: add PSP IP v13.0.11 support
drm/amdgpu: add gmc v11 support for GC 11.0.4
drm/amdgpu: add gfx support for GC 11.0.4
drm/amdgpu/discovery: set the APU flag for GC 11.0.4
drm/amdgpu: set GC 11.0.4 family
drm/amdgpu/discovery: enable mes support for GC v11.0.4
drm/amdgpu/discovery: enable gfx v11 for GC 11.0.4
drm/amdgpu/discovery: enable gmc v11 for GC 11.0.4
drm/amdgpu/discovery: enable soc21 common for GC 11.0.4
x86/fpu: Use _Alignof to avoid undefined behavior in TYPE_ALIGN
exit: Use READ_ONCE() for all oops/warn limit reads
docs: Fix path paste-o for /sys/kernel/warn_count
panic: Expose "warn_count" to sysfs
panic: Introduce warn_limit
panic: Consolidate open-coded panic_on_warn checks
exit: Allow oops_limit to be disabled
exit: Expose "oops_count" to sysfs
exit: Put an upper limit on how often we can oops
panic: Separate sysctl logic from CONFIG_SMP
efi: rt-wrapper: Add missing include
arm64: efi: Execute runtime services from a dedicated stack
fs/ntfs3: Fix attr_punch_hole() null pointer derenference
cifs: reduce roundtrips on create/qinfo requests
drm/amd/display: disable S/G display on DCN 3.1.4
drm/amd/display: disable S/G display on DCN 3.1.5
drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix
drm/amd/display: Calculate output_color_space after pixel encoding adjustment
drm/amd/display: Fix set scaling doesn's work
drm/i915: Remove unused variable
drm/i915: Allow switching away via vga-switcheroo if uninitialized
drm/i915/display: Check source height is > 0
drm/i915: re-disable RC6p on Sandy Bridge
drm/amdgpu: Correct the power calcultion for Renior/Cezanne.
drm/amdgpu: allow multipipe policy on ASICs with one MEC
drm/amdgpu: fix amdgpu_job_free_resources v2
ARM: omap1: fix !ARCH_OMAP1_ANY link failures
ARM: dts: qcom: apq8084-ifc6540: fix overriding SDHCI
VMCI: Use threaded irqs instead of tasklets
mei: me: add meteor lake point M DID
mei: bus: fix unlink on bus in error path
gsmi: fix null-deref in gsmi_get_variable
serial: exar: Add support for Sealevel 7xxxC serial cards
serial: atmel: fix incorrect baudrate setup
serial: amba-pl011: fix high priority character transmission in rs486 mode
dmaengine: idxd: Do not call DMX TX callbacks during workqueue disable
dmaengine: idxd: Prevent use after free on completion memory
dmaengine: idxd: Let probe fail when workqueue cannot be enabled
dmaengine: tegra210-adma: fix global intr clear
dmaengine: lgm: Move DT parsing after initialization
serial: pch_uart: Pass correct sg to dma_unmap_sg()
dt-bindings: phy: g12a-usb3-pcie-phy: fix compatible string documentation
dt-bindings: phy: g12a-usb2-phy: fix compatible string documentation
arm64: dts: imx8mp: correct usb clocks
usb-storage: apply IGNORE_UAS only for HIKSEMI MD202 on RTL9210
usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate()
USB: gadget: Add ID numbers to configfs-gadget driver names
usb: gadget: g_webcam: Send color matching descriptor per frame
usb: typec: altmodes/displayport: Fix pin assignment calculation
usb: typec: altmodes/displayport: Add pin assignment helper
usb: typec: tcpm: Fix altmode re-registration causes sysfs create fail
usb: musb: fix error return code in omap2430_probe()
usb: host: ehci-fsl: Fix module alias
usb: cdns3: remove fetched trb from cache before dequeuing
USB: serial: cp210x

[Kernel-packages] [Bug 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works

[Hugo Ferreira]

@yk4ever: I am having the same issue. Was it a hardware issue? Does the
modprobe still work? In my case it does not. What kernel are you using
now?

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

Title:
  iwlwifi Not valid error log pointer 0x causes WiFi to not work
  but bluetooth works

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  For some reason, Ubuntu gets glitched where the Bluetooth works but
  WiFi does not even show up. If I reboot into Windows, it is a similar
  issue (wifi does not show up, but device manager shows Code 10. If I
  disable and enable the adaptor Intel Wireless AC 9560, it sometimes
  works and most times does not). After a few days, the issue goes away.

  Relevent info:
  Laptop: Asus ROG Strig-G 531GT
  Using newest bios 308
  WiFi Adaptor: Intel Wireless AC 9560
  As for wifi connection, usually wifi icon does not even show and stays that 
way throughout the whole uptime. If I reboot a couple of times, this may 
change. However, the wifi I connect to usually is WiFi 5 on 5G channel running 
WPA2. If I use my laptop outside my home, it connects to enterprise WiFi
  Here is the Intel firmware version 
  [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 
46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm


  Here is the relevent Dmesg output 
  [code]
  [   10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   10.909348] iwlwifi :00:14.3: IML/ROM dump:
  [   10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   10.909397] iwlwifi :00:14.3: Fseq Registers:
  [   10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   10.909494] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110
  [   14.101296] iwlwifi :00:14.3: retry init count 1
  [   14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x318
  [   14.112168] thermal thermal_zone6: failed to read out thermal zone (-61)
  [   15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   15.390284] iwlwifi :00:14.3: IML/ROM dump:
  [   15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   15.390332] iwlwifi :00:14.3: Fseq Registers:
  [   15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   15.390428] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms)

[Kernel-packages] [Bug 2004110] Re: Wifi keeps failing with: Failed to run INIT ucode: -110

[Hugo Ferreira]

Same issue as reported here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993052

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

Title:
  Wifi keeps failing with:  Failed to run INIT ucode: -110

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Quite a few people are complaining about this issue. For example:
  https://community.frame.work/t/solved-getting-wifi-working-on-
  ubuntu-22-04/25246.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  Something wrong with the iwlwifi firmware and/or driver?
  On boot it fails many (most?) times. 
  When it does work, it seems to work correctly. Does not seem to be hardware 
issue. 
  When it fails, on reboot no wifi option exists.
  When the wifi option does exist, starting and stopping airplane mode can 
sometime help.

  Worked with 20.0X ok.

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


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

[Kernel-packages] [Bug 2004110] Re: Wifi keeps failing with: Failed to run INIT ucode: -110

[Hugo Ferreira]

Not quite the same error as above. But this seems to be the same. Here
is the orginal:

[ 28.357969] iwlwifi :3d:00.0: Could not load the [0] uCode section
[ 28.358001] iwlwifi :3d:00.0: Failed to start INIT ucode: -110

Here is what I have:

sudo dmesg | grep -i wifi
[sudo] password for hmf: 
[   10.325056] Intel(R) Wireless WiFi driver for Linux
[   10.325250] iwlwifi :00:14.3: enabling device ( -> 0002)
[   10.329965] iwlwifi :00:14.3: WRT: Overriding region id 0
[   10.329968] iwlwifi :00:14.3: WRT: Overriding region id 1
[   10.329971] iwlwifi :00:14.3: WRT: Overriding region id 2
[   10.329973] iwlwifi :00:14.3: WRT: Overriding region id 3
[   10.329974] iwlwifi :00:14.3: WRT: Overriding region id 4
[   10.329976] iwlwifi :00:14.3: WRT: Overriding region id 6
[   10.329978] iwlwifi :00:14.3: WRT: Overriding region id 8
[   10.329979] iwlwifi :00:14.3: WRT: Overriding region id 9
[   10.329981] iwlwifi :00:14.3: WRT: Overriding region id 10
[   10.329983] iwlwifi :00:14.3: WRT: Overriding region id 11
[   10.329984] iwlwifi :00:14.3: WRT: Overriding region id 15
[   10.329986] iwlwifi :00:14.3: WRT: Overriding region id 16
[   10.329987] iwlwifi :00:14.3: WRT: Overriding region id 18
[   10.329989] iwlwifi :00:14.3: WRT: Overriding region id 19
[   10.329991] iwlwifi :00:14.3: WRT: Overriding region id 20
[   10.329992] iwlwifi :00:14.3: WRT: Overriding region id 21
[   10.329994] iwlwifi :00:14.3: WRT: Overriding region id 28
[   10.330274] iwlwifi :00:14.3: loaded firmware version 46.fae53a8b.0 
9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[   10.385326] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, 
REV=0x318
[   11.418432] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x0, CPU2 Status: 0x0
[   11.418436] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   11.666372] iwlwifi :00:14.3: Not valid error log pointer 0x for 
Init uCode
[   11.666471] iwlwifi :00:14.3: IML/ROM dump:
[   11.666482] iwlwifi :00:14.3: 0x | IML/ROM error/state
[   11.666527] iwlwifi :00:14.3: 0x | IML/ROM data1
[   11.666552] iwlwifi :00:14.3: Fseq Registers:
[   11.666577] iwlwifi :00:14.3: 0x80587040 | FSEQ_ERROR_CODE
[   11.02] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[   11.27] iwlwifi :00:14.3: 0xE5093394 | FSEQ_CNVIO_INIT_VERSION
[   11.52] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[   11.77] iwlwifi :00:14.3: 0xFE4BB1A7 | FSEQ_TOP_CONTENT_VERSION
[   11.666702] iwlwifi :00:14.3: 0xB5B75B6D | FSEQ_ALIVE_TOKEN
[   11.666727] iwlwifi :00:14.3: 0x99194215 | FSEQ_CNVI_ID
[   11.666752] iwlwifi :00:14.3: 0x5BB3AB7B | FSEQ_CNVR_ID
[   11.666777] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[   11.666835] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[   11.666925] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   11.667015] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   11.667040] iwlwifi :00:14.3: Failed to start INIT ucode: -110
[   11.667054] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   14.816910] iwlwifi :00:14.3: Failed to run INIT ucode: -110
[   14.829566] iwlwifi :00:14.3: retry init count 0
[   14.831451] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, 
REV=0x318
[   15.870686] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x0, CPU2 Status: 0x0
[   15.870704] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   16.118912] iwlwifi :00:14.3: Not valid error log pointer 0x for 
Init uCode
[   16.118955] iwlwifi :00:14.3: IML/ROM dump:
[   16.118959] iwlwifi :00:14.3: 0x | IML/ROM error/state
[   16.118994] iwlwifi :00:14.3: 0x | IML/ROM data1
[   16.119010] iwlwifi :00:14.3: Fseq Registers:
[   16.119021] iwlwifi :00:14.3: 0x80587040 | FSEQ_ERROR_CODE
[   16.119033] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[   16.119045] iwlwifi :00:14.3: 0xE5093394 | FSEQ_CNVIO_INIT_VERSION
[   16.119056] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[   16.119068] iwlwifi :00:14.3: 0xFE4BB1A7 | FSEQ_TOP_CONTENT_VERSION
[   16.119080] iwlwifi :00:14.3: 0xB5B75B6D | FSEQ_ALIVE_TOKEN
[   16.119090] iwlwifi :00:14.3: 0x99194215 | FSEQ_CNVI_ID
[   16.119101] iwlwifi :00:14.3: 0x5BB3AB7B | FSEQ_CNVR_ID
[   16.119113] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[   16.119157] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[   16.119234] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   16.119311] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   16.119323] iwlwifi :00:14.3: Failed to start INIT ucode: -110
[   16.119330] iwlwifi :00:14.3: WRT: Collecting dat

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

[Ubuntu Kernel Bot]

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

apport-collect 2004110

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

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

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

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

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

Title:
  Wifi keeps failing with:  Failed to run INIT ucode: -110

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Quite a few people are complaining about this issue. For example:
  https://community.frame.work/t/solved-getting-wifi-working-on-
  ubuntu-22-04/25246.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  Something wrong with the iwlwifi firmware and/or driver?
  On boot it fails many (most?) times. 
  When it does work, it seems to work correctly. Does not seem to be hardware 
issue. 
  When it fails, on reboot no wifi option exists.
  When the wifi option does exist, starting and stopping airplane mode can 
sometime help.

  Worked with 20.0X ok.

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


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

[Kernel-packages] [Bug 2004110] Re: Wifi keeps failing with: Failed to run INIT ucode: -110

[Hugo Ferreira]

Possibly related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975460

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

Title:
  Wifi keeps failing with:  Failed to run INIT ucode: -110

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Quite a few people are complaining about this issue. For example:
  https://community.frame.work/t/solved-getting-wifi-working-on-
  ubuntu-22-04/25246.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  Something wrong with the iwlwifi firmware and/or driver?
  On boot it fails many (most?) times. 
  When it does work, it seems to work correctly. Does not seem to be hardware 
issue. 
  When it fails, on reboot no wifi option exists.
  When the wifi option does exist, starting and stopping airplane mode can 
sometime help.

  Worked with 20.0X ok.

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


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