[Kernel-packages] [Bug 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application

[Juerg Haefliger]

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

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

Title:
  Linux 6.5 breaks Novation Components web MIDI application

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu version: 23.10
  Kernel version: 6.5.0-10

  Steps to recreate:
  1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
  2. Navigate to https://components.novationmusic.com/
  3. Connect a Novation Circuit Tracks via USB

  Expected behaviour (demonstrated by 
linux-image-unsigned-6.4.16-060416-generic):
  - Circuit Tracks shows up in UI with a state of "Connected"

  Observed behaviour:
  - Circuit Tracks shows up in UI with a state of "Connecting" and eventually 
"Connection error"

  Notes:
  - Basic MIDI functions are present (sending notes, clocks etc.)
  - loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N 
makes no difference

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ecoffey2236 F wireplumber
   /dev/snd/controlC1:  ecoffey2236 F wireplumber
   /dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 16:25:39 2023
  InstallationDate: Installed on 2022-12-14 (333 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
  dmi.bios.date: 10/14/2022
  dmi.bios.release: 20.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2014
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z690-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2043686] Re: package linux-image-5.15.0-88-generic (not installed) failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal script subprocess retur

[Juerg Haefliger]

You seem to have aborted the removal of the running kernel that you
triggered manually. What outcome are you expecting?

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

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

Title:
  package linux-image-5.15.0-88-generic (not installed) failed to
  install/upgrade: installed linux-image-5.15.0-88-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux-signed-hwe-5.15 package in Ubuntu:
  Incomplete

Bug description:
  crashed on me

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-88-generic (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-1.0~upboard5-generic 5.4.65
  Uname: Linux 5.4.0-1-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 15 23:21:42 2023
  ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-11-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: linux-signed-hwe-5.15
  Title: package linux-image-5.15.0-88-generic (not installed) failed to 
install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-11-16 (0 days ago)

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


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

[Kernel-packages] [Bug 2043665] Re: Hundreds of errors per second: kernel: pcieport 0000:00:1c.3: PCIe Bus Error

[Juerg Haefliger]

Can you post a log (from the beginning of the boot process) that shows
the errors?


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

Title:
  Hundreds of errors per second: kernel: pcieport :00:1c.3: PCIe Bus
  Error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After a fresh 23.10 install I have noticed that booting up my PC in
  the morning was taking a long time. Checking journalctl there are
  hundreds of warnings generated every  second, and not only at boot
  time (see below). Searching for this problem I found a stopgap
  solution by adding this instruction in GRUB:

  pcie_aspm=off

  However, as a plain Ubuntu user I should be having this problem of
  long boot times and edit GRUB to "fix" it, when the problem captured
  in the log isn't even fixed, I just avoided it with instruction. This
  is why I'm reporting it in case it helps find the original cause.

  Previously I was running 23.04 on the same PC and booting times were
  short, just normal. I believe this is a new problem even when the
  hardware is the same and I haven't done any changes apart from
  upgrading.

  The errors are all the same:

  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: AER: Corrected error 
received: :00:1c.3
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: PCIe Bus Error: 
severity=Corrected, type=Physical Layer, (Receiv>
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:   device [8086:7abb] 
error status/mask=0001/2000
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:[ 0] RxErr
  (First)
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: AER: Corrected error 
received: :00:1c.3
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: PCIe Bus Error: 
severity=Corrected, type=Physical Layer, (Receiv>
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:   device [8086:7abb] 
error status/mask=0001/2000
  Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:[ 0] RxErr
  (First)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:38:28 2023
  InstallationDate: Installed on 2023-11-13 (2 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=fa113624-262e-4625-ba8b-eabf66ab696c ro pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.10
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z690 FORCE WIFI (MS-7D30)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.10:bd12/03/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D30:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690FORCEWIFI(MS-7D30):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D30
  dmi.product.sku: Default string
  dmi.product.version: 2.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/2043665/+subscriptions


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

[Kernel-packages] [Bug 2042716] Re: [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode failed with error -2

[hugh chao]

** Tags added: verification-needed verification-needed-jammy
verification-needed-mantic

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

Title:
  [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode
  failed with error -2

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Wifi is not functional.

  [Fix]

  Cherry-pick relevant FW files.

  [Where Problems Could Occur]

  Only machines with relevant Wifi HW is affected. Potential crashes and
  hangs dues to bad FW.

  [Summary]
  I just upgraded my pc from 23.04 to 23.10,
  and found that my wifi was dead, turn out it's because the firmware load 
failed.

  [Reproduce Steps]
  1. Upgrade 23.04 to 23.10

  [Results]
  Expected: firmware can be loaded
  Actual: firmware load failed

  [Additional Information]
  1. The firmware can be loaded successfully in 23.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 16:58:00 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2023-02-09 (268 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=d2e4673c-e5fe-4a04-8647-bc56a5fa2a08 ro quiet splash 
nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z790-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd01/06/2023:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1979631] Re: Orico Switch5.0 Bluetooth adapter doesn't work

[Choo Ting Feng]

This is not a bug, it is behaving as Intended
The ORICO-BTA-SW01 is not a typical bluetooth adapter
Instead, it is a Bluetooth Audio Transmitter Adapter

It shows itself as a USB Audio device, and any audio sent to it will be
transmitted to a bluetooth device paired to the receiver

As such pairing handled by the device, not the OS
It is also only used for Audio, other Bluetooth devices like Keyboards or Mouse 
cannot be used with it

In essence, it is a USB soundcard and a bluetooth audio transmitter
glued together in 1 dongle

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

Title:
  Orico Switch5.0 Bluetooth adapter doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought Switch5.0 Bluetooth adapter
  (https://www.orico.cc/us/product/detail/7400/BK.html) which identifies
  under lsusb as:

  10d6:dd00 Actions Semiconductor Co., Ltd BT90

  It doesn't work under Ubuntu 22.04. The Bluetooth icon doesn't show up
  and when I try to run blueman-adapters it shows:

  > blueman-adapters
  blueman-adapters 11.38.00 ERRORAdapter:54 __init__  : No adapter(s) found

  
  The weird thing is, that it creates new audio device BT90 in Pulse settings.
  (I think, that the device might share same identification codes as different 
audio device: https://linux-hardware.org/?id=usb:10d6-dd00)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  petr   1703 F pulseaudio
   /dev/snd/pcmC0D0p:   petr   1703 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Thu Jun 23 11:33:41 2022
  InstallationDate: Installed on 2017-05-29 (1850 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Z240 Tower Workstation
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=d1e354f4-cbcc-4f35-b360-8e2f15dca61e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-05-02 (51 days ago)
  dmi.bios.date: 12/15/2020
  dmi.bios.release: 1.81
  dmi.bios.vendor: HP
  dmi.bios.version: N51 Ver. 01.81
  dmi.board.name: 802F
  dmi.board.vendor: HP
  dmi.chassis.asset.tag: CZC710BW19
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 5.56
  dmi.modalias: 
dmi:bvnHP:bvrN51Ver.01.81:bd12/15/2020:br1.81:efr5.56:svnHP:pnHPZ240TowerWorkstation:pvr:rvnHP:rn802F:rvr:cvnHP:ct3:cvr:skuT4L18ES#ARL:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z240 Tower Workstation
  dmi.product.sku: T4L18ES#ARL
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Mario Limonciello]

Try amdgpu.mcbp=0 on your kernel command line.

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in linux package in Ubuntu:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

** Tags added: regression-proposed

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

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 16.0
  dmi.bios.vendor: HP
  dmi.bios.version: S12 Ver. 02.16.00
  dmi.board.name: 8810
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.23
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: HP ProOne 600 G6
  dmi.product.sku: 123456#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2042357] Re: Merge crash 8.0.3+ds1-3 into Noble

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 8.0.3+ds1-3ubuntu1

---
crash (8.0.3+ds1-3ubuntu1) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes: (LP: #2042357)
- d/t/live: If the "live" autopkgtest fails with a recommendation to
  try /proc/kcore instead of the default, attempt that before
  failing the test. LP 1858958.
- d/t/live: Fix logic issue in "live" autopkgtest introduced in the
  last upload.
- d/t/live: Fix test, as if will return 0 when no cases were true.
- d/t/control: Add linux-libc-dev dependency for the autopkg test.
  This package gets usually broken with kernel upgrades, so let it
  already show in the autopkg test.
- d/t/control: Run autopkg test with allow-stderr.
  * Drop changes:
- d/rules: Build without lto. Fails to build gdb on ppc64el. That
  should be fixed, once gdb is updated to a more recent version
  (e.g. 10.x). [This line is already commented out since Mantic.]
  * New changes:
- d/p/0002-Fix-compilation-error-due-to-new-strlcpy-function.patch:
  Fix FTBFS due to strlcpy() introduced in glibc 2.38.
- d/p/0003-Support-module-memory-layout-change-on-Linux-6.4.patch:
  Fix fatal 'crash: invalid structure member offset: module_core_size'

 -- Mauricio Faria de Oliveira   Tue, 07 Nov 2023
15:00:36 -0300

** Changed in: crash (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Merge crash 8.0.3+ds1-3 into Noble

Status in crash package in Ubuntu:
  Fix Released
Status in crash package in Debian:
  Fix Released

Bug description:
  Merge Request / git-ubuntu:

  https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+merge/455353

  Test packages:

  ppa:mfo/noble-crash-v2

  ...

  Versions:

  $ rmadison -a source crash | grep noble
   crash | 8.0.2-1ubuntu1 | noble  | source

  $ rmadison -a source crash -u debian | grep 'unstable '
  crash  | 8.0.2-1   | unstable   | source
  crash  | 8.0.3+ds1-3   | unstable   | source

  ...

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

  ...

  Docs:
  
https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/6.2.0.1018.18)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-lowlatency (6.2.0.1018.18) 
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

linux-lowlatency/6.2.0-1018.18 (amd64, arm64)
systemd/252.5-2ubuntu3.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#linux-meta-lowlatency

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application

[Edward]

Mainline kernel 6.6.1 also exhibits this regression.

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

Title:
  Linux 6.5 breaks Novation Components web MIDI application

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: 23.10
  Kernel version: 6.5.0-10

  Steps to recreate:
  1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
  2. Navigate to https://components.novationmusic.com/
  3. Connect a Novation Circuit Tracks via USB

  Expected behaviour (demonstrated by 
linux-image-unsigned-6.4.16-060416-generic):
  - Circuit Tracks shows up in UI with a state of "Connected"

  Observed behaviour:
  - Circuit Tracks shows up in UI with a state of "Connecting" and eventually 
"Connection error"

  Notes:
  - Basic MIDI functions are present (sending notes, clocks etc.)
  - loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N 
makes no difference

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ecoffey2236 F wireplumber
   /dev/snd/controlC1:  ecoffey2236 F wireplumber
   /dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 12 16:25:39 2023
  InstallationDate: Installed on 2022-12-14 (333 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
  dmi.bios.date: 10/14/2022
  dmi.bios.release: 20.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2014
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z690-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2042867] Re: Changing display resolution leads into black screen

[Aleix]

I installed manually 6.5.7 and the issue has been resolved. The bug was
so frustrating

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

Title:
  Changing display resolution leads into black screen

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Since updating into 23.10, when I change my build-in display from
  2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen
  black and unable to use.

  The only resolution that works is the predefined one.

  This bug wasn't present on the previous release, 23.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 19:37:48 2023
  InstallationDate: Installed on 2023-05-05 (185 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
  dmi.bios.date: 04/18/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UM5401QAB_UM5401QA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UM5401QAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UM5401QAB_UM5401QA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 2042867] Re: Changing display resolution leads into black screen

[zomp]

Is the release expected soon please? (The bug does not affect only those
who proactively modified resolution and so know what got wrong, but also
those who had it modified and upgraded from Lunar to Mantic – these
people have no clue what the issue is. I almost left Ubuntu because the
blank screen was not something I could live with and I could not find a
solution. Early release might help other people.)

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

Title:
  Changing display resolution leads into black screen

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Since updating into 23.10, when I change my build-in display from
  2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen
  black and unable to use.

  The only resolution that works is the predefined one.

  This bug wasn't present on the previous release, 23.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 19:37:48 2023
  InstallationDate: Installed on 2023-05-05 (185 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
  dmi.bios.date: 04/18/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UM5401QAB_UM5401QA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UM5401QAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UM5401QAB_UM5401QA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1937291] Re: no sound on alc294 asus rog laptop

[Launchpad Bug Tracker]

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

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

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

Title:
  no sound on alc294 asus rog laptop

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

Bug description:
  Built-in speakers don't work. Bluetooth work okeyish, but the volume
  is very low.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Regolith:GNOME-Flashback:GNOME
  Date: Thu Jul 22 19:30:07 2021
  InstallationDate: Installed on 2021-06-19 (32 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2043730] [NEW] Update io_uring to 6.6

[Thadeu Lima de Souza Cascardo]

Public bug reported:

[Impact]
io_uring is a fast-developed subsystem in the Linux kernel. In order to keep up 
with the latest changes such that applying further fixes are possible, it 
should be updated to a more recent version.

[Test case]
Given the general update, there are no specific test cases.

[Potential regression]
io_uring users only would be affected given most changes are restricted to it.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Mantic)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  Update io_uring to 6.6

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

Bug description:
  [Impact]
  io_uring is a fast-developed subsystem in the Linux kernel. In order to keep 
up with the latest changes such that applying further fixes are possible, it 
should be updated to a more recent version.

  [Test case]
  Given the general update, there are no specific test cases.

  [Potential regression]
  io_uring users only would be affected given most changes are restricted to it.

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


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

[Kernel-packages] [Bug 2043724] Re: Focal update: v5.4.259 upstream stable release

[Manuel Diewald]

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Manuel Diewald (diewald)

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
- 
-v5.4.259 upstream stable release
-from git://git.kernel.org/
+    v5.4.259 upstream stable release
+    from git://git.kernel.org/
  
  RDMA/cxgb4: Check skb value for failure to allocate
  lib/test_meminit: fix off-by-one error in test_pages()
  pwm: hibvt: Explicitly set .polarity in .get_state()
  HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
  quota: Fix slow quotaoff
  net: prevent address rewrite in kernel_bind()
  drm: etvnaviv: fix bad backport leading to warning
  drm/msm/dsi: skip the wait for video mode done if not applicable
  ravb: Fix up dma_free_coherent() call in ravb_remove()
  ieee802154: ca8210: Fix a potential UAF in ca8210_probe
  mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type
  xen-netback: use default TX queue size for vifs
  drm/vmwgfx: fix typo of sizeof argument
  ixgbe: fix crash with empty VF macvlan list
  net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
  nfc: nci: assert requested protocol is valid
  workqueue: Override implicit ordered attribute in 
workqueue_apply_unbound_cpumask()
  dmaengine: stm32-mdma: abort resume if no ongoing transfer
  usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer
  net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read
  usb: dwc3: Soft reset phy on probe for host
  usb: musb: Get the musb_qh poniter after musb_giveback
  usb: musb: Modify the "HWVers" register address
  iio: pressure: bmp280: Fix NULL pointer exception
  iio: pressure: dps310: Adjust Timeout Settings
  iio: pressure: ms5611: ms5611_prom_is_valid false negative bug
  mcb: remove is_added flag from mcb_device struct
  libceph: use kernel_connect()
  ceph: fix incorrect revoked caps assert in ceph_fill_file_size()
  Input: powermate - fix use-after-free in powermate_config_complete
  Input: psmouse - fix fast_reconnect function for PS/2 mode
  Input: xpad - add PXN V900 support
  cgroup: Remove duplicates in cgroup v1 tasks file
  pinctrl: avoid unsafe code pattern in find_pinctrl()
  usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
  usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call
  x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs
  dmaengine: mediatek: Fix deadlock caused by synchronize_irq()
  powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE
  powerpc/64e: Fix wrong test in __ptep_test_and_clear_young()
  ravb: Fix use-after-free issue in ravb_tx_timeout_work()
  Documentation: sysctl: align cells in second content column
  usb: hub: Guard against accesses to uninitialized BOS descriptors
  Bluetooth: hci_event: Ignore NULL link key
  Bluetooth: Reject connection with the device which has same BD_ADDR
  Bluetooth: Fix a refcnt underflow problem for hci_conn
  Bluetooth: vhci: Fix race when opening vhci device
  Bluetooth: hci_event: Fix coding style
  Bluetooth: avoid memcmp() out of bounds warning
  ice: fix over-shifted variable
  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()
  regmap: fix NULL deref on lookup
  KVM: x86: Mask LVTPC when handling a PMI
  netfilter: nft_payload: fix wrong mac header matching
  qed: fix LL2 RX buffer allocation
  xfrm: fix a data-race in xfrm_gen_index()
  xfrm: interface: use DEV_STATS_INC()
  net: ipv4: fix return value check in esp_remove_trailer
  net: ipv6: fix return value check in esp_remove_trailer
  net: rfkill: gpio: prevent value glitch during probe
  tcp: fix excessive TLP and RACK timeouts from HZ rounding
  tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single skb
  tun: prevent negative ifindex
  ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr
  net: usb: smsc95xx: Fix an error code in 

[Kernel-packages] [Bug 2043724] [NEW] Focal update: v5.4.259 upstream stable release

[Manuel Diewald]

Public bug reported:


SRU Justification

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

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

RDMA/cxgb4: Check skb value for failure to allocate
lib/test_meminit: fix off-by-one error in test_pages()
pwm: hibvt: Explicitly set .polarity in .get_state()
HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
quota: Fix slow quotaoff
net: prevent address rewrite in kernel_bind()
drm: etvnaviv: fix bad backport leading to warning
drm/msm/dsi: skip the wait for video mode done if not applicable
ravb: Fix up dma_free_coherent() call in ravb_remove()
ieee802154: ca8210: Fix a potential UAF in ca8210_probe
mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type
xen-netback: use default TX queue size for vifs
drm/vmwgfx: fix typo of sizeof argument
ixgbe: fix crash with empty VF macvlan list
net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
nfc: nci: assert requested protocol is valid
workqueue: Override implicit ordered attribute in 
workqueue_apply_unbound_cpumask()
dmaengine: stm32-mdma: abort resume if no ongoing transfer
usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer
net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read
usb: dwc3: Soft reset phy on probe for host
usb: musb: Get the musb_qh poniter after musb_giveback
usb: musb: Modify the "HWVers" register address
iio: pressure: bmp280: Fix NULL pointer exception
iio: pressure: dps310: Adjust Timeout Settings
iio: pressure: ms5611: ms5611_prom_is_valid false negative bug
mcb: remove is_added flag from mcb_device struct
libceph: use kernel_connect()
ceph: fix incorrect revoked caps assert in ceph_fill_file_size()
Input: powermate - fix use-after-free in powermate_config_complete
Input: psmouse - fix fast_reconnect function for PS/2 mode
Input: xpad - add PXN V900 support
cgroup: Remove duplicates in cgroup v1 tasks file
pinctrl: avoid unsafe code pattern in find_pinctrl()
usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call
x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs
dmaengine: mediatek: Fix deadlock caused by synchronize_irq()
powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE
powerpc/64e: Fix wrong test in __ptep_test_and_clear_young()
ravb: Fix use-after-free issue in ravb_tx_timeout_work()
Documentation: sysctl: align cells in second content column
usb: hub: Guard against accesses to uninitialized BOS descriptors
Bluetooth: hci_event: Ignore NULL link key
Bluetooth: Reject connection with the device which has same BD_ADDR
Bluetooth: Fix a refcnt underflow problem for hci_conn
Bluetooth: vhci: Fix race when opening vhci device
Bluetooth: hci_event: Fix coding style
Bluetooth: avoid memcmp() out of bounds warning
ice: fix over-shifted variable
nfc: nci: fix possible NULL pointer dereference in send_acknowledge()
regmap: fix NULL deref on lookup
KVM: x86: Mask LVTPC when handling a PMI
netfilter: nft_payload: fix wrong mac header matching
qed: fix LL2 RX buffer allocation
xfrm: fix a data-race in xfrm_gen_index()
xfrm: interface: use DEV_STATS_INC()
net: ipv4: fix return value check in esp_remove_trailer
net: ipv6: fix return value check in esp_remove_trailer
net: rfkill: gpio: prevent value glitch during probe
tcp: fix excessive TLP and RACK timeouts from HZ rounding
tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single skb
tun: prevent negative ifindex
ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr
net: usb: smsc95xx: Fix an error code in smsc95xx_reset()
i40e: prevent crash on probe if hw registers have invalid values
net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve
neighbor: tracing: Move pin6 inside CONFIG_IPV6=y section
netfilter: nft_set_rbtree: .deactivate fails if element has expired
net: pktgen: Fix interface flags printing
resource: Add irqresource_disabled()
ACPI: Drop acpi_dev_irqresource_disabled()
ACPI: resource: Skip IRQ override on Asus Vivobook S5602ZA
ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks
ACPI: resource: Skip IRQ override on Asus Expertbook B2402CBA
ACPI: resource: Skip IRQ override on ASUS ExpertBook B1502CBA
ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CBA
ARM: dts: ti: omap: Fix noisy serial with overrun-throttle-ms for mapphone
btrfs: return -EUCLEAN for delayed tree ref with a ref count not equals to 1
btrfs: initialize start_slot in btrfs_log_prealloc_extents
i2c: mux: Avoid potential false error message in i2c_mux_add_adapter
overlayfs: set ctime when 

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

[Vitaly Protsko]

Bug is still here. 5.15.0-91-generic

Nov 16 21:15:29 mon-host kernel: [  101.739280] 

Nov 16 21:15:29 mon-host kernel: [  101.785597] UBSAN: 
array-index-out-of-bounds in 
/build/linux-90ta4T/linux-5.15.0/drivers/edac/i5000_edac.c:956:20
Nov 16 21:15:29 mon-host kernel: [  101.786940] IPMI message handler: version 
39.2
Nov 16 21:15:29 mon-host kernel: [  101.836146] index 4 is out of range for 
type 'u16 [4]'
Nov 16 21:15:29 mon-host kernel: [  101.836152] CPU: 0 PID: 447 Comm: 
systemd-udevd Not tainted 5.15.0-91-generic #101-Ubuntu
Nov 16 21:15:29 mon-host kernel: [  101.836156] Hardware name: Dell Inc. 
PowerEdge 1950/0D8635, BIOS 2.7.0 10/30/2010
Nov 16 21:15:29 mon-host kernel: [  101.836158] Call Trace:
Nov 16 21:15:29 mon-host kernel: [  101.836162]  
Nov 16 21:15:29 mon-host kernel: [  101.836166]  show_stack+0x52/0x5c
Nov 16 21:15:29 mon-host kernel: [  101.836175]  dump_stack_lvl+0x4a/0x63
Nov 16 21:15:29 mon-host kernel: [  101.836182]  dump_stack+0x10/0x16
Nov 16 21:15:29 mon-host kernel: [  101.836184]  ubsan_epilogue+0x9/0x36
Nov 16 21:15:29 mon-host kernel: [  101.836187]  
__ubsan_handle_out_of_bounds.cold+0x44/0x49
Nov 16 21:15:29 mon-host kernel: [  101.836190]  ? 
i5000_get_mc_regs.isra.0+0x14c/0x1c0 [i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.836197]  i5000_probe1+0x506/0x5c0 
[i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.836201]  ? 
pci_bus_read_config_byte+0x40/0x70
Nov 16 21:15:29 mon-host kernel: [  101.862944]  ? 
do_pci_enable_device+0x54/0x110
Nov 16 21:15:29 mon-host kernel: [  101.862948]  i5000_init_one+0x26/0x30 
[i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.862952]  local_pci_probe+0x4b/0x90
Nov 16 21:15:29 mon-host kernel: [  101.862956]  pci_device_probe+0x119/0x1f0
Nov 16 21:15:29 mon-host kernel: [  101.862960]  really_probe+0x222/0x420
Nov 16 21:15:29 mon-host kernel: [  101.862964]  
__driver_probe_device+0xe8/0x140
Nov 16 21:15:29 mon-host kernel: [  101.862966]  driver_probe_device+0x23/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.862969]  __driver_attach+0xf7/0x1f0
Nov 16 21:15:29 mon-host kernel: [  101.862971]  ? 
__device_attach_driver+0x140/0x140
Nov 16 21:15:29 mon-host kernel: [  101.862974]  bus_for_each_dev+0x7f/0xd0
Nov 16 21:15:29 mon-host kernel: [  101.862978]  driver_attach+0x1e/0x30
Nov 16 21:15:29 mon-host kernel: [  101.862980]  bus_add_driver+0x148/0x220
Nov 16 21:15:29 mon-host kernel: [  101.862982]  ? 
vunmap_range_noflush+0x3d5/0x470
Nov 16 21:15:29 mon-host kernel: [  101.862987]  driver_register+0x95/0x100
Nov 16 21:15:29 mon-host kernel: [  101.862990]  ? 0xc03d8000
Nov 16 21:15:29 mon-host kernel: [  101.862993]  __pci_register_driver+0x68/0x70
Nov 16 21:15:29 mon-host kernel: [  101.862996]  i5000_init+0x36/0x1000 
[i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.863000]  do_one_initcall+0x49/0x1e0
Nov 16 21:15:29 mon-host kernel: [  101.863005]  ? 
kmem_cache_alloc_trace+0x19e/0x2e0
Nov 16 21:15:29 mon-host kernel: [  101.863011]  do_init_module+0x52/0x260
Nov 16 21:15:29 mon-host kernel: [  101.863016]  load_module+0xb2b/0xbc0
Nov 16 21:15:29 mon-host kernel: [  101.863019]  
__do_sys_finit_module+0xbf/0x120
Nov 16 21:15:29 mon-host kernel: [  101.863023]  
__x64_sys_finit_module+0x18/0x20
Nov 16 21:15:29 mon-host kernel: [  101.863025]  do_syscall_64+0x5c/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.863031]  ? 
exit_to_user_mode_prepare+0x37/0xb0
Nov 16 21:15:29 mon-host kernel: [  101.863038]  ? 
syscall_exit_to_user_mode+0x35/0x50
Nov 16 21:15:29 mon-host kernel: [  101.863043]  ? 
__x64_sys_newfstatat+0x1c/0x30
Nov 16 21:15:29 mon-host kernel: [  101.863047]  ? do_syscall_64+0x69/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.863049]  ? do_syscall_64+0x69/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.863051]  ? exc_page_fault+0x89/0x170
Nov 16 21:15:29 mon-host kernel: [  101.863054]  
entry_SYSCALL_64_after_hwframe+0x62/0xcc
Nov 16 21:15:29 mon-host kernel: [  101.863060] RIP: 0033:0x7f5b964c9a7d
Nov 16 21:15:29 mon-host kernel: [  101.863064] 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 83 a3 0f 00 f7 d8 
64 89 01 48
Nov 16 21:15:29 mon-host kernel: [  101.863068] RSP: 002b:7ffe8a418818 
EFLAGS: 0246 ORIG_RAX: 0139
Nov 16 21:15:29 mon-host kernel: [  101.863073] RAX: ffda RBX: 
55fe999a5a00 RCX: 7f5b964c9a7d
Nov 16 21:15:29 mon-host kernel: [  101.863075] RDX:  RSI: 
7f5b96660441 RDI: 000f
Nov 16 21:15:29 mon-host kernel: [  101.863077] RBP: 0002 R08: 
 R09: 7ffe8a418950
Nov 16 21:15:29 mon-host kernel: [  101.863079] R10: 000f R11: 
0246 R12: 7f5b96660441
Nov 16 21:15:29 mon-host kernel: [  101.863080] R13: 55fe99981d40 R14: 
55fe9994eb50 R15: 

[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot

[Vitaly Protsko]

5.15.0-91-generic

Nov 16 21:15:29 mon-host kernel: [  101.739280] 

Nov 16 21:15:29 mon-host kernel: [  101.785597] UBSAN: 
array-index-out-of-bounds in 
/build/linux-90ta4T/linux-5.15.0/drivers/edac/i5000_edac.c:956:20
Nov 16 21:15:29 mon-host kernel: [  101.786940] IPMI message handler: version 
39.2
Nov 16 21:15:29 mon-host kernel: [  101.836146] index 4 is out of range for 
type 'u16 [4]'
Nov 16 21:15:29 mon-host kernel: [  101.836152] CPU: 0 PID: 447 Comm: 
systemd-udevd Not tainted 5.15.0-91-generic #101-Ubuntu
Nov 16 21:15:29 mon-host kernel: [  101.836156] Hardware name: Dell Inc. 
PowerEdge 1950/0D8635, BIOS 2.7.0 10/30/2010
Nov 16 21:15:29 mon-host kernel: [  101.836158] Call Trace:
Nov 16 21:15:29 mon-host kernel: [  101.836162]  
Nov 16 21:15:29 mon-host kernel: [  101.836166]  show_stack+0x52/0x5c
Nov 16 21:15:29 mon-host kernel: [  101.836175]  dump_stack_lvl+0x4a/0x63
Nov 16 21:15:29 mon-host kernel: [  101.836182]  dump_stack+0x10/0x16
Nov 16 21:15:29 mon-host kernel: [  101.836184]  ubsan_epilogue+0x9/0x36
Nov 16 21:15:29 mon-host kernel: [  101.836187]  
__ubsan_handle_out_of_bounds.cold+0x44/0x49
Nov 16 21:15:29 mon-host kernel: [  101.836190]  ? 
i5000_get_mc_regs.isra.0+0x14c/0x1c0 [i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.836197]  i5000_probe1+0x506/0x5c0 
[i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.836201]  ? 
pci_bus_read_config_byte+0x40/0x70
Nov 16 21:15:29 mon-host kernel: [  101.862944]  ? 
do_pci_enable_device+0x54/0x110
Nov 16 21:15:29 mon-host kernel: [  101.862948]  i5000_init_one+0x26/0x30 
[i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.862952]  local_pci_probe+0x4b/0x90
Nov 16 21:15:29 mon-host kernel: [  101.862956]  pci_device_probe+0x119/0x1f0
Nov 16 21:15:29 mon-host kernel: [  101.862960]  really_probe+0x222/0x420
Nov 16 21:15:29 mon-host kernel: [  101.862964]  
__driver_probe_device+0xe8/0x140
Nov 16 21:15:29 mon-host kernel: [  101.862966]  driver_probe_device+0x23/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.862969]  __driver_attach+0xf7/0x1f0
Nov 16 21:15:29 mon-host kernel: [  101.862971]  ? 
__device_attach_driver+0x140/0x140
Nov 16 21:15:29 mon-host kernel: [  101.862974]  bus_for_each_dev+0x7f/0xd0
Nov 16 21:15:29 mon-host kernel: [  101.862978]  driver_attach+0x1e/0x30
Nov 16 21:15:29 mon-host kernel: [  101.862980]  bus_add_driver+0x148/0x220
Nov 16 21:15:29 mon-host kernel: [  101.862982]  ? 
vunmap_range_noflush+0x3d5/0x470
Nov 16 21:15:29 mon-host kernel: [  101.862987]  driver_register+0x95/0x100
Nov 16 21:15:29 mon-host kernel: [  101.862990]  ? 0xc03d8000
Nov 16 21:15:29 mon-host kernel: [  101.862993]  __pci_register_driver+0x68/0x70
Nov 16 21:15:29 mon-host kernel: [  101.862996]  i5000_init+0x36/0x1000 
[i5000_edac]
Nov 16 21:15:29 mon-host kernel: [  101.863000]  do_one_initcall+0x49/0x1e0
Nov 16 21:15:29 mon-host kernel: [  101.863005]  ? 
kmem_cache_alloc_trace+0x19e/0x2e0
Nov 16 21:15:29 mon-host kernel: [  101.863011]  do_init_module+0x52/0x260
Nov 16 21:15:29 mon-host kernel: [  101.863016]  load_module+0xb2b/0xbc0
Nov 16 21:15:29 mon-host kernel: [  101.863019]  
__do_sys_finit_module+0xbf/0x120
Nov 16 21:15:29 mon-host kernel: [  101.863023]  
__x64_sys_finit_module+0x18/0x20
Nov 16 21:15:29 mon-host kernel: [  101.863025]  do_syscall_64+0x5c/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.863031]  ? 
exit_to_user_mode_prepare+0x37/0xb0
Nov 16 21:15:29 mon-host kernel: [  101.863038]  ? 
syscall_exit_to_user_mode+0x35/0x50
Nov 16 21:15:29 mon-host kernel: [  101.863043]  ? 
__x64_sys_newfstatat+0x1c/0x30
Nov 16 21:15:29 mon-host kernel: [  101.863047]  ? do_syscall_64+0x69/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.863049]  ? do_syscall_64+0x69/0xc0
Nov 16 21:15:29 mon-host kernel: [  101.863051]  ? exc_page_fault+0x89/0x170
Nov 16 21:15:29 mon-host kernel: [  101.863054]  
entry_SYSCALL_64_after_hwframe+0x62/0xcc
Nov 16 21:15:29 mon-host kernel: [  101.863060] RIP: 0033:0x7f5b964c9a7d
Nov 16 21:15:29 mon-host kernel: [  101.863064] 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 83 a3 0f 00 f7 d8 
64 89 01 48
Nov 16 21:15:29 mon-host kernel: [  101.863068] RSP: 002b:7ffe8a418818 
EFLAGS: 0246 ORIG_RAX: 0139
Nov 16 21:15:29 mon-host kernel: [  101.863073] RAX: ffda RBX: 
55fe999a5a00 RCX: 7f5b964c9a7d
Nov 16 21:15:29 mon-host kernel: [  101.863075] RDX:  RSI: 
7f5b96660441 RDI: 000f
Nov 16 21:15:29 mon-host kernel: [  101.863077] RBP: 0002 R08: 
 R09: 7ffe8a418950
Nov 16 21:15:29 mon-host kernel: [  101.863079] R10: 000f R11: 
0246 R12: 7f5b96660441
Nov 16 21:15:29 mon-host kernel: [  101.863080] R13: 55fe99981d40 R14: 
55fe9994eb50 R15: 55fe99985200
Nov 16 

[Kernel-packages] [Bug 2040106] Re: firmware broken after upgrade to Ubuntu 23.10

[Launchpad Bug Tracker]

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

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

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

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 
generic hwe kernel (of appropriate version for jammy & mantic)

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]

   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2043640] Re: amdgpu hangs the computer frequently

[nachokb]

This is all the logs for that boot.

** Attachment added: "full logs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043640/+attachment/5720207/+files/lastboot-.txt

** Summary changed:

- amdgpu hangs the computer frequently
+ amdgpu: GPU Recovery fails, frequent hangs

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in linux package in Ubuntu:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2043640] Re: amdgpu hangs the computer frequently

[nachokb]

I found relevant log entries.

** Attachment added: "excerpt from offending boot's logs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043640/+attachment/5720206/+files/amdgpu-hang.txt

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in linux package in Ubuntu:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2039786] Re: Raspberry Pi 3B+ doesnt boot from USB on 23.10 Mantic

[Juerg Haefliger]

Yes, this is bad
https://lore.kernel.org/all/d04bcc45-3471-4417-b30b-5cf9880d7...@i2se.com/


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

** Also affects: linux-raspi (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Raspberry Pi 3B+ doesnt boot from USB on 23.10 Mantic

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Noble:
  Confirmed

Bug description:
  Hello all,

  I upgraded my Raspberry Pi 3B+ from 22.04 to 23.10.
  The storage device where the OS resides is a USB hdd.
  It is connected to the Pi via a ASMedia Technology Inc. X820.

  After the upgrade to 23.10, Ubuntu crashes during boot.

  To eliminate the X820 as a variable:
  - I created a Ubuntu server 23.10 directly on a USB stick -> The pi doesn't 
boot
  - I created a Ubuntu server 23.04 the same way -> the pi boots

  After investigation, I found that if I copy the /boot/firmware folder
  from an old 22.04 image and replace the content of the Fat32 boot
  partition of the HDD with its content, Ubuntu boots again.

  From the error I get during boot time, it looks like after booting, the USB 
HDD is not found or the root partition is not mounted properly.
  Booting with an SD card and mounting the HDD, I see that no logs in /var/log 
folder are being updated

  What should be my next step to get proper error messages and
  investigate further?

  Thanks in advance,
  Aurélien

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


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

[Kernel-packages] [Bug 500069]

[konoha02]

I am facing this issue with both debian and archlinux.  xfs and ext4
https://forums.debian.net/viewtopic.php?p=778803

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

Title:
  USB file transfer causes system freezes; ops take hours instead of
  minutes

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Fedora:
  Won't Fix

Bug description:
  USB Drive is a MP3 Player 2GB

  sbec@Diamant:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse 
Receiver
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 004: ID 0402:5661 ALi Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  sbec@Diamant:~$

  Linux Diamant 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 
i686 GNU/Linux
  Ubuntu 2.6.31-15.50-generic

  to test, i issued dd command:
  dd if=/dev/zero of=/media/usb-disk/test-file bs=32

  while dd is running i run dstat this is in the log file attached.

  other logs are also in the tar.gz file...

  there is a huge USB performance Bug report #1972262. this Report is
  something simular

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


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

[Kernel-packages] [Bug 500069]

[r.piedfer]

Created attachment 305400
attachment-13101-0.html

Bonjour,

Je suis actuellement absent.
J'aurai d'ici là un accès très limité à mes emails.
Je reviendrai vers vous dès que possible à mon retour.
Pour toute urgence, vous pouvez contacter Vincent Ophele / v.oph...@asmodee.com

Cordialement,

--

Hello,

I am OOO with no access to my emails.
I will get back to you as quickly as possible when I return.
In case of emergency, please contact Vincent Ophele / v.oph...@asmodee.com

Best regards,


Ce courriel provient de la société Financière Amuse BidCo. Le contenu de
ce courriel et les pièces jointes le cas échéant sont confidentiels pour
le destinataire. Ils ne peuvent être ni divulgués, ni utilisés, ni
copiés de quelque manière que ce soit par une personne autre que le
destinataire prévu. Si ce courriel vous a été adressé par erreur, merci
d'en informer son auteur par téléphone et par courriel en intégrant le
message original dans votre réponse, puis supprimez-le. Pour plus
d'informations sur la manière dont nous traitons les données
personnelles, veuillez consulter notre Politique de protection des
données personnelles

. Veuillez noter que Financière Amuse BidCo n'assume aucune
responsabilité vis-à-vis des virus et qu'il vous incombe d'analyser ou
de consulter ce courriel et ses pièces jointes le cas échéant.
Financière Amuse BidCo est une société par actions simplifiée à associé
unique (RCS Versailles 815 143 904). Son siège social est situé 18 rue
Jacqueline Auriol - Quartier Villaroy - 78280 Guyancourt. Pour plus
d'informations, veuillez consulter le site
https://corporate.asmodee.com/.

This email is from Financière Amuse BidCo. The content of this email and
any attachments are confidential to the intended recipient. They may not
be disclosed to or used by or copied in any way by anyone other than the
intended recipient. If this email is received in error, please inform
the author by phone and email, including the original message in your
reply, and then delete it. For more information on how we process
personal data, please see our Privacy policy

. Please note that Financière Amuse BidCo does not accept any
responsibility for viruses and it is your responsibility to scan or
otherwise check this email and any attachments. Financière Amuse BidCo
is a French « Société par actions simplifiée à associé unique »
(Commerce and Companies Register of Versailles 815 143 904) Its
registered office is at 18 rue Jacqueline Auriol - Quartier Villaroy -
78280 Guyancourt. For further information, please refer to
https://corporate.asmodee.com/.

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

Title:
  USB file transfer causes system freezes; ops take hours instead of
  minutes

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Fedora:
  Won't Fix

Bug description:
  USB Drive is a MP3 Player 2GB

  sbec@Diamant:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse 
Receiver
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 004: ID 0402:5661 ALi Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  sbec@Diamant:~$

  Linux Diamant 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 
i686 GNU/Linux
  Ubuntu 2.6.31-15.50-generic

  to test, i issued dd command:
  dd if=/dev/zero of=/media/usb-disk/test-file bs=32

  while dd is running i run dstat this is in the log file attached.

  other logs are also in the tar.gz file...

  there is a huge USB performance Bug report #1972262. this Report is
  something simular

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


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

[Kernel-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/455719

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

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


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

[Kernel-packages] [Bug 2040106] Re: firmware broken after upgrade to Ubuntu 23.10

[Dimitri John Ledkov]

https://lists.ubuntu.com/archives/kernel-team/2023-November/146940.html

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

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 
generic hwe kernel (of appropriate version for jammy & mantic)

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]

   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2036737] Re: Enable dynamic boost control in ccp kernel driver

[Mario Limonciello]

** Description changed:

  [Impact]
  
  We need to backport dynamic boost control into OEM-6.5 kernel. This
  request is to backport the ccp changes.
  
  Here are the commits necessary to backport to OEM-6.5 kernel from kernel
  6.6:
  
  b58276372182 crypto: ccp - Rename macro for security attributes
  2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
  e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
  b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
  c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost 
control
  d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost 
control
  e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters
  
+ Here are the commits necessary to backport to OEM-6.5 kernel from kernel
+ 6.7:
+ 
+ 53f7f779f45c ("crypto: ccp - Get a free page to use while fetching
+ initial nonce")
+ 
  [Test case]
  
  WIP
  
  [Regression potential]
  
  WIP

** Description changed:

  [Impact]
  
  We need to backport dynamic boost control into OEM-6.5 kernel. This
  request is to backport the ccp changes.
  
  Here are the commits necessary to backport to OEM-6.5 kernel from kernel
  6.6:
  
  b58276372182 crypto: ccp - Rename macro for security attributes
  2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
  e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
  b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
  c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost 
control
  d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost 
control
  e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters
  
  Here are the commits necessary to backport to OEM-6.5 kernel from kernel
  6.7:
  
- 53f7f779f45c ("crypto: ccp - Get a free page to use while fetching
- initial nonce")
+ 53f7f779f45c crypto: ccp - Get a free page to use while fetching initial
+ nonce
  
  [Test case]
  
  WIP
  
  [Regression potential]
  
  WIP

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

Title:
  Enable dynamic boost control in ccp kernel driver

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

Bug description:
  [Impact]

  We need to backport dynamic boost control into OEM-6.5 kernel. This
  request is to backport the ccp changes.

  Here are the commits necessary to backport to OEM-6.5 kernel from
  kernel 6.6:

  b58276372182 crypto: ccp - Rename macro for security attributes
  2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
  e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
  b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
  c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost 
control
  d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost 
control
  e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters

  Here are the commits necessary to backport to OEM-6.5 kernel from
  kernel 6.7:

  53f7f779f45c crypto: ccp - Get a free page to use while fetching
  initial nonce

  [Test case]

  WIP

  [Regression potential]

  WIP

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


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

[Kernel-packages] [Bug 2040106] Re: firmware broken after upgrade to Ubuntu 23.10 (missing transitionals from focal oem kernel installs)

[Dimitri John Ledkov]

** Description changed:

+ [ Impact ]
+ 
+  * Focal preinstalled systems with OEM kernel, if force upgraded to
+ interim releases, before transitional packages have been made available
+ resulted in systems having been stuck on focal oem kernel and not
+ getting any kernel updates.
+ 
+  * Reintroduce all focal oem kernel transitionals to trigger upgrade to
+ hwe kernel in all stable releases for the oem-20.04* kernels
+ 
+ [ Test Plan ]
+ 
+  * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
+  * Force upgrade to mantic
+  * Observe that all oem-20.04 meta packages got upgraded and rolled to 6.5 
generic hwe kernel
+ 
+ [ Where problems could occur ]
+ 
+  * This may trigger dkms package recompilation, and nvidia driver missmatches
+  * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
+  * Users may experience jump from v5.10 kernel to v6.5 kernel
+ 
+ [ Other Info ]
+  
+  * Original bug report
+ 
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59
- 
  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.
  
  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
  
  So my best guess is that something is wrong in the latest firmware
  package.
  
- 
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic
  
- 
  apt-cache policy linux-firmware
  linux-firmware:
-   Installed: 20230919.git3672ccab-0ubuntu2.1
-   Candidate: 20230919.git3672ccab-0ubuntu2.1
-   Version table:
-  *** 20230919.git3672ccab-0ubuntu2.1 500
- 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 20230919.git3672ccab-0ubuntu2.1
+   Candidate: 20230919.git3672ccab-0ubuntu2.1
+   Version table:
+  *** 20230919.git3672ccab-0ubuntu2.1 500
+ 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  joep   2545 F wireplumber
-  /dev/snd/controlC0:  joep   2545 F wireplumber
-  /dev/snd/seq:joep   2537 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  joep   2545 F wireplumber
+  /dev/snd/controlC0:  joep   2545 F wireplumber
+  /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-focal-amd64-20200502-85
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.10.0-1053-oem N/A
-  linux-backports-modules-5.10.0-1053-oem  N/A
-  linux-firmware   20230919.git3672ccab-0ubuntu2.1
+  linux-restricted-modules-5.10.0-1053-oem N/A
+  linux-backports-modules-5.10.0-1053-oem  N/A
+  linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Dimitri John Ledkov]

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

** Summary changed:

- Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
+ Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10 
(missing transitionals from focal oem kernel installs)

** Summary changed:

- Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10 
(missing transitionals from focal oem kernel installs)
+ firmware broken after upgrade to Ubuntu 23.10 (missing transitionals from 
focal oem kernel installs)

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

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 6.5 
generic hwe kernel

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]
   
   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  

[Kernel-packages] [Bug 2042850] Re: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-14.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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-linux'.


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52
  BMC

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2042423
  

  Subject: [mantic:linux]  drm/ast: Add BMC virtual connector


  SRU Justification:

  [Impact]
  On systems with Aspeed 2600 revision 52 GPUs, the display fails to progress 
to the login prompt.  With the commit (added in 6.5.0-6.6)

 commit: 916ae609a033cbb55661905d310ba2358b7621ea
 Author:  Jocelyn Falempe 
 Date:Thu Jul 13 15:41:31 2023 +0200
 Subject: drm/ast: report connection status on Display Port.

   the Aspeed 2600 rev 52 GPUs have issues.

  They need the commit:

  This change was dependant on the upstream change
  commit e329cb53b45da475966c4b2e49f6a4a430f307fa
  Author: Jocelyn Falempe 
  Date: Thu Jul 13 15:41:30 2023 +0200
  Subject: drm/ast: Add BMC virtual connector

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e329cb53b45da475966c4b2e49f6a4a430f307fa

  
  in order to have the display work correctly on the rev52 GPUs.  


  [Fix]
  With cherry-picking this change, the functionality of BMCs using Aspeed 2600 
rev52 GPUs work as expected, as they did prior to the regression in 6.5.0-6.6. 

  [Test Plan]
  I have tested this on multiple versions of Aspeed 2600 GPU enabled BMCs, and 
the revision 52 systems that required the nomodeset option to boot to the 
prompt, now boot fine and display the login prompt, and there is no regression 
on the other systems.  I have tested this on different Aspeed GPUs, and have 
not seen any regressions, or unexpected behaviour. 

  
  [Where problems could occur]
  As this fixes a regression of  functionality for the mantic kernel's Aspeed 
GPU driver on a very specific version of some BMCs to the state it was was in 
the mantic 6.5.0-5.5 kernel, I think there is little room for regressions.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Andrzej Stencel]

Thanks Timo, I updated the kernel and things are still working OK.

$ uname -a
Linux astencel-dell 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 
13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 6.5.0.10.12
  Candidate: 6.5.0.10.12
  Version table:
 *** 6.5.0.10.12 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 6.5.0.9.11 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2043469] Re: Low-latency kernel can't boot to desktop

[icaria36]

** Summary changed:

- Low-latency kernel can't load to desktop
+ Low-latency kernel can't boot to desktop

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

Title:
  Low-latency kernel can't boot to desktop

Status in linux-meta-lowlatency package in Ubuntu:
  New

Bug description:
  23.10 fresh install. Generic kernel boots without problems. lowlatency
  can't boot to desktop, it gets stuck and shows black screen with
  cursor blinking.

  The same PC worked yesterday with 23.04 and low latency without
  problems. I have been running lowlatency kernel in this machine for a
  couple of years, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-lowlatency 6.5.0.10.10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 12:25:24 2023
  InstallationDate: Installed on 2023-11-13 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: linux-meta-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2043469] Re: Low-latency kernel can't load to desktop

[icaria36]

Booting in safe mode the system reaches the point where you can login
and check journalctl. I didn't find any strange errors there, as in
nothing red that isn't appearing on the generic kernel (which continues
to boot without problems). I'm no expert, but it gives the impression
that the system boots up normally and then stops before starting the
graphical interface. I don't know how to debug from this point.

I wonder whether it has something to do with the fact that I am using an
NVidia card (which works fine with the generic kernel boot).

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

Title:
  Low-latency kernel can't load to desktop

Status in linux-meta-lowlatency package in Ubuntu:
  New

Bug description:
  23.10 fresh install. Generic kernel boots without problems. lowlatency
  can't boot to desktop, it gets stuck and shows black screen with
  cursor blinking.

  The same PC worked yesterday with 23.04 and low latency without
  problems. I have been running lowlatency kernel in this machine for a
  couple of years, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-lowlatency 6.5.0.10.10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 12:25:24 2023
  InstallationDate: Installed on 2023-11-13 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: linux-meta-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Timo Aaltonen]

nope, this is a clear process mistake which we'll make sure doesn't
happen again..

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2043551] Re: Fix headset microphone for Dell laptops with audio codec ALC295

[Timo Aaltonen]

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

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

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

Title:
  Fix headset microphone for Dell laptops with audio codec ALC295

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

Bug description:
  [Impact]
  Dell laptops with Realtek audio codec ALC295 can't detect the plug-in of 
headset microphone and also fails to record audio from headset. 

  [Fix]
  Backport the fix from Realtek on linux-next 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=4b21a669ca21ed8f24ef4530b2918be5730114de
 

  [Test Case]
  1. Power on the Dell laptops with Realtek ALC295 HDA.
  2. Plug in the headset microphone
  3. Verify if the jack-detection working and recording function is working or 
not.

  [Where problems could occur]
  Only affect Dell laptops with the Realtek ALC295 HDA. Should be low risk 
since Dell laptops only support MIC2 as external MIC.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Liam Proven]

@xnox:

> I thought 390 is so obsolete, that everyone has migrated to newer ones
if their card supports it.

Sadly I can't. I have 2 Thinkpads with this GPU (Core i7 T420, Core i7
W520) and it is built in -- it can't be replaced.

If upstream has dropped it then there is little that can be done but a
warning when I upgraded to Mantic would have been good! I got nothing, I
just lost PRIME offload.

Secondly, I feel it would be the Ubuntu spirit to automatically _remove_
the no-longer-supported driver and configure Nouveau instead. So far I
have spent hours on this and cannot get it working. It is very
frustrating indeed.

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[crtlbreak]

in the /proc/acpi/wakeup file 
changing XHC from "enabled" to disabled does resolve this.


To disable ‘XHC’, do:

echo 'XHC' > /proc/acpi/wakeup
with superuser privilege.


Documented here >> 
https://ubuntu-mate.community/t/ubuntu-wakes-up-immediately-after-suspend-how-to-fix-it/26848

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

Title:
  Laptop wakes up immediately after suspend or hibernation

Status in linux package in Ubuntu:
  Expired

Bug description:
  After going into suspend (via command line or lid close), the MacBook
  Pro (early 2015) wakes up immediately again. Same for hibernation.
  Running Ubuntu 18.04.

  extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open
  cycle:

  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [ ... ]
  [  778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table 
err:-23
  [  783.011399] PM: suspend entry (deep)
  [  783.011400] PM: Syncing filesystems ... done.
  [  783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  783.030844] OOM killer disabled.
  [  783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  783.032193] Suspending console(s) (use no_console_suspend to debug)
  [  783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache
  [  783.054107] sd 1:0:0:0: [sda] Stopping disk
  [  783.146124] thunderbolt :07:00.0: suspending...
  [  783.146685] thunderbolt :07:00.0: suspend finished
  [  783.146689] thunderbolt :07:00.0: stopping RX ring 0
  [  783.146698] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [  783.146710] thunderbolt :07:00.0: stopping TX ring 0
  [  783.146718] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [  783.146725] thunderbolt :07:00.0: control channel stopped
  [  783.246464] ACPI: Preparing to enter system sleep state S3
  [  783.418015] ACPI: EC: event blocked
  [  783.418016] ACPI: EC: EC stopped
  [  783.418018] PM: Saving platform NVS memory
  [  783.418027] Disabling non-boot CPUs ...
  [  783.434574] IRQ 65: no longer affine to CPU1
  [  783.435629] smpboot: CPU 1 is now offline
  [  783.454574] IRQ 66: no longer affine to CPU2
  [  783.456378] smpboot: CPU 2 is now offline
  [  783.478405] IRQ 21: no longer affine to CPU3
  [  783.478414] IRQ 43: no longer affine to CPU3
  [  783.478435] IRQ 71: no longer affine to CPU3
  [  783.479449] smpboot: CPU 3 is now offline
  [  783.481656] ACPI: Low-level resume complete
  [  783.481733] ACPI: EC: EC started
  [  783.481734] PM: Restoring platform NVS memory
  [  783.482160] Enabling non-boot CPUs ...
  [  783.482240] x86: Booting SMP configuration:
  [  783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  783.558589]  cache: parent cpu1 should not be sleeping
  [  783.687159] CPU1 is up
  [  783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1
  [  783.687812]  cache: parent cpu2 should not be sleeping
  [  783.688001] CPU2 is up
  [  783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  783.783709]  cache: parent cpu3 should not be sleeping
  [  783.978233] CPU3 is up
  [  783.982020] ACPI: Waking up from system sleep state S3
  [  784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.112655] thunderbolt :07:00.0: control channel starting...
  [  784.112660] thunderbolt :07:00.0: starting TX ring 0
  [  784.112673] thunderbolt :07:00.0: enabling interrupt at register 
0x38200 bit 0 (0x0 -> 0x1)
  [  784.112677] thunderbolt :07:00.0: starting RX ring 0
  [  784.112689] thunderbolt :07:00.0: enabling interrupt at register 
0x38200 bit 12 (0x1 -> 0x1001)
  [  784.112696] thunderbolt :07:00.0: resuming...
  [  784.112699] thunderbolt :07:00.0: resetting switch at 0
  [  784.113249] thunderbolt :07:00.0: 0: resuming switch
  [  784.144609] thunderbolt :07:00.0: resume finished
  [  784.213878] thunderbolt :07:00.0: resetting error on 0:b.
  [  784.213897] thunderbolt :07:00.0: 0:b: hotplug: scanning
  [  784.213901] thunderbolt :07:00.0: 0:b: hotplug: no switch found
  [  784.213984] thunderbolt :07:00.0: resetting error on 0:c.
  [  784.213995] thunderbolt :07:00.0: 0:c: hotplug: scanning
  [  784.213999] thunderbolt :07:00.0: 0:c: hotplug: no switch found
  [  785.225640] ACPI: EC: event 

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[joepadmiraal]

Great, I assume we don't need to do the `sudo -E oem-getlogs` that
Andrzej requested anymore?

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on

[Riley Kao]

Verified SENRTY V16

~~~
$ uname -a
Linux test-Vostro-16-5640 6.5.0-1008-oem #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 
10 13:08:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
~~~
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
0
$ sudo rtcwake -m mem -s 5
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
4117866
~~~

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

Title:
  Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle
  screen on

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

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.

  [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814

  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Timo Aaltonen]

ack, so what happenened was likely this:

- you had 20.04 preinstalled with an oem image and -oem-20.04b kernel (5.10)
- upgraded to an interim release or 22.04 *before* 5.10 was EOL'd in focal (and 
moved to hwe-5.15) which happened around March/April '22

-> stuck with oem-5.10 since 22.04 didn't (and still doesn't) come with
transitionals for b/c(5.13)/d(5.14) flavors

So to fix that we need to add the b/c/d transitionals to jammy linux-
meta, and also lunar/mantic/noble

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Timo Aaltonen]

the quick fix for this is to run 'sudo apt install linux-generic', which
would pull the latest generic (= distro) kernel

Your hw is old enough that it shouldn't require the 6.5 oem kernel :)

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2032385] Re: [mlx5] Not able to enable switchdev mode on CX-6 DX with OPN MCX623106AN-CDAT and PSID MT_0000000359

[Moshe Levi]

The Dell servers  comes with SRIOV disabled by default in the BIOS while
our NICs have SRIOV enabled by default on most out-of-the-box
configurations.

Solving this difference solves the issue.
On Dell BIOS under 'Integrated Devices' change 'SR-IOV Global Enable' to 
'Enabled'.

Or you can disable SR-IOV on the NIC FW.

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

Title:
  [mlx5] Not able to enable switchdev mode on CX-6 DX with OPN
  MCX623106AN-CDAT and PSID MT_000359

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This occurs with default firmware configuration on the following kernels:
  5.15.0
  5.19.0
  6.2.0

  Firmware versions tried:
  22.35.3006
  22.38.1002

  
  The operation is successful when attempting to perform the same operation on 
a CX-6 DX card of a different model.

  Steps to reproduce:
  # ip link
  ...
  4: enp65s0f0np0:  mtu 9000 qdisc mq state UP 
mode DEFAULT group default qlen 1000
  link/ether 10:70:fd:0f:84:2a brd ff:ff:ff:ff:ff:ff
  5: enp65s0f1np1:  mtu 9000 qdisc mq state UP 
mode DEFAULT group default qlen 1000
  link/ether 10:70:fd:0f:84:2b brd ff:ff:ff:ff:ff:ff

  # echo 32 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs 
  # echo 32 > /sys/class/net/enp65s0f1np1/device/sriov_numvfs
  # for addr in $(devlink dev show|tail +3|cut -f2 -d/); do echo $addr > 
/sys/bus/pci/drivers/mlx5_core/unbind;done
  # devlink dev eswitch set pci/:41:00.0 mode switchdev
  Error: mlx5_core: Failed setting eswitch to offloads.
  kernel answers: Cannot allocate memory
  # devlink dev eswitch set pci/:41:00.1 mode switchdev
  Error: mlx5_core: Failed setting eswitch to offloads.
  kernel answers: Cannot allocate memory

  Steps to work around:
  # modprobe -r mlx5_ib
  # echo blacklist mlx5_ib > /etc/modprobe.d/blacklist-mlx5-ib.conf
  # devlink dev eswitch set pci/:41:00.0 mode switchdev
  # devlink dev eswitch set pci/:41:00.1 mode switchdev
  # devlink dev eswitch show pci/:41:00.0
  pci/:41:00.0: mode switchdev inline-mode none encap-mode basic
  # devlink dev eswitch show pci/:41:00.1
  pci/:41:00.1: mode switchdev inline-mode none encap-mode basic

  
  Log excerpts:
  # dmesg -T | tail -40
  [Mon Aug 21 14:50:35 2023] mlx5_core :41:08.1 enp65s0f1v31: renamed from 
eth0
  [Mon Aug 21 14:50:36 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 19): 
Error -110 while trying to test write-combining support
  [Mon Aug 21 14:50:36 2023] mlx5_ib.rdma: probe of mlx5_core.rdma.65 failed 
with error -12
  [Mon Aug 21 14:53:32 2023] mlx5_core :41:00.0: E-Switch: Disable: 
mode(LEGACY), nvfs(32), active vports(33)
  [Mon Aug 21 14:53:33 2023] mlx5_core :41:00.0: E-Switch: Supported tc 
chains and prios offload
  [Mon Aug 21 14:53:33 2023] mlx5_core :41:00.0: Supported tc offload range 
- chains: 4294967294, prios: 4294967295
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0 enp65s0f0np0: Link up
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0 enp65s0f0np0: Dropping 
C-tag vlan stripping offload due to S-tag vlan
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0 enp65s0f0np0: Disabling 
HW_VLAN CTAG FILTERING, not supported in switchdev mode
  [Mon Aug 21 14:53:34 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 
102770): Error -110 while trying to test write-combining support
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:34 2023] mlx5_core :41:00.0: Supported tc offload range 
- chains: 4294967294, prios: 4294967295
  [Mon Aug 21 14:53:35 2023] mlx5_core :41:00.0 enp65s0f0np0: Link up
  [Mon Aug 21 14:53:36 2023] infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 
102770): Error -110 while trying to test write-combining support
  [Mon Aug 21 14:53:36 2023] mlx5_ib.rdma: probe of mlx5_core.rdma.0 failed 
with error -12
  [Mon Aug 21 14:53:36 2023] mlx5_core :41:00.0: E-Switch: Enable: 
mode(LEGACY), nvfs(32), active vports(33)
  [Mon Aug 21 14:53:39 2023] mlx5_core :41:00.1: E-Switch: Disable: 
mode(LEGACY), nvfs(32), active vports(33)
  [Mon Aug 21 14:53:39 2023] mlx5_core :41:00.1: E-Switch: Supported tc 
chains and prios offload
  [Mon Aug 21 14:53:39 2023] mlx5_core :41:00.1: Supported tc offload range 
- chains: 4294967294, prios: 4294967295
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1: MLX5E: StrdRq(1) RqSz(64) 
StrdSz(256) RxCqeCmprss(0)
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1 enp65s0f1np1: Link up
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1 enp65s0f1np1: Dropping 
C-tag vlan stripping offload due to S-tag vlan
  [Mon Aug 21 14:53:40 2023] mlx5_core :41:00.1 enp65s0f1np1: Disabling 
HW_VLAN CTAG FILTERING, not supported in switchdev mode
  [Mon Aug 21 

[Kernel-packages] [Bug 2042885] Re: [UBUNTU 22.04] Running smartctl on NVME hit segmentation fault

[Frank Heimes]

** Package changed: linux (Ubuntu) => smartmontools (Ubuntu)

** Changed in: smartmontools (Ubuntu)
   Status: New => Triaged

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

** Changed in: smartmontools (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Zhaoxuan Zhai 
(kxuan)

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

Title:
  [UBUNTU 22.04] Running smartctl on NVME hit segmentation fault

Status in Ubuntu on IBM z Systems:
  Triaged
Status in smartmontools package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - SCHAYNE BELLROSE  - 2023-10-31 
10:08:10 ==
  ---Problem Description---
  Ran sudo smartctl -i -a /dev/nvme0 against NVME drive to get SMART data but 
hit Segmentation fault
   
  Contact Information = Schayne Bellrose/schayne.bellro...@ibm.com 
   
  ---Additional Hardware Info---
  DPM system and added Storage group contains a NVME drive set for data.  

   
  ---uname output---
  Linux t249sb2 5.15.0-87-generic #97-Ubuntu SMP Mon Oct 2 21:11:23 UTC 2023 
s390x s390x s390x GNU/Linux
   
  Machine Type = 3932 
   
  ---Steps to Reproduce---
   Run the following command 
  smartctl -i -a /dev/nvme0 
   
  *Additional Instructions for Schayne Bellrose/schayne.bellro...@ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

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


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

[Kernel-packages] [Bug 2036697] Re: i915: Update DMC, GuC, HuC fw for Meteor Lake

[Timo Aaltonen]

Hello Timo, or anyone else affected,

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

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

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

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

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

** Description changed:

  [Impact]
  There are new firmware versions available for MTL, which contain undisclosed 
fixes.
  
  lunar is omitted as it doesn't have support for MTL, while jammy does
  via oem-6.5
  
  [Test case]
- Install the update, test on MTL that things keep working at least the same as 
before.
+ Install the update, test on MTL that things keep working at least the same as 
before and that also GuC/HuC gets loaded.
  
  [Regression potential]
  MTL is a new platform being enabled, these do not affect any shipping hardware

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

Title:
  i915: Update DMC, GuC, HuC fw for Meteor Lake

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

Bug description:
  [Impact]
  There are new firmware versions available for MTL, which contain undisclosed 
fixes.

  lunar is omitted as it doesn't have support for MTL, while jammy does
  via oem-6.5

  [Test case]
  Install the update, test on MTL that things keep working at least the same as 
before and that also GuC/HuC gets loaded.

  [Regression potential]
  MTL is a new platform being enabled, these do not affect any shipping hardware

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

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

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

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

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

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

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

Title:
  missing mei_vsc firmware for HM2172 and OV02E sensor

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  Missing mei_vsc firmware for HM2172 and OV02E sensor.

mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
mei_vsc spi-INTC10D0:00: reset failed ret = -19
mei_vsc spi-INTC10D0:00: link layer initialization failed.
mei_vsc spi-INTC10D0:00: init hw failure.

  [Fix]

  Upstream (https://github.com/intel/ivsc-firmware) commit 4f15196c0dcb
  ("firmware: add HM2172 and OV02E sensor").

  Note that a surfix "_a1_prod" is added to the requested fw filename, so a
  symbolic link is created for each of the VSC fw blobs.

  [Test Case]

  Boot with firmware blobs installed, and mei_vsc should probe successfully
  without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort. While there is no
  Noble branch yet, Noble is not nominated.

  == original bug report ==

  [ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
  [ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
  [ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
  [ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
  [ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
  [ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

  Upstream commit in https://github.com/intel/ivsc-
  firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

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

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

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

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

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

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

Title:
  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY.

  [Fix]

  Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
  from 
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

  [Test Case]

  Run suspend/resume stress test with fwts:
  ```
  $ checkbox-cli run 
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
  ```

  [Where problems could occur]

  The proposed firmware is opaque to us, expect every possible
  regression.

  [Other Info]

  At the time writing this pull request, this firmware blob is public released
  in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, 
nominate
  for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now.

  == original bug report ==

  [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1
  [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb 
board_id 0xff soc_id 0x400c1211
  [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e 
fw_build_timestamp 2022-12-22 12:54 fw_build_id 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23

  Upstream firwmware
  WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from
  
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

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

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

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

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

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

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

Title:
  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY.

  [Fix]

  Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
  from 
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

  [Test Case]

  Run suspend/resume stress test with fwts:
  ```
  $ checkbox-cli run 
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
  ```

  [Where problems could occur]

  The proposed firmware is opaque to us, expect every possible
  regression.

  [Other Info]

  At the time writing this pull request, this firmware blob is public released
  in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, 
nominate
  for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now.

  == original bug report ==

  [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1
  [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb 
board_id 0xff soc_id 0x400c1211
  [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e 
fw_build_timestamp 2022-12-22 12:54 fw_build_id 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23

  Upstream firwmware
  WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from
  
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.4 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  missing mei_vsc firmware for HM2172 and OV02E sensor

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  Missing mei_vsc firmware for HM2172 and OV02E sensor.

mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
mei_vsc spi-INTC10D0:00: reset failed ret = -19
mei_vsc spi-INTC10D0:00: link layer initialization failed.
mei_vsc spi-INTC10D0:00: init hw failure.

  [Fix]

  Upstream (https://github.com/intel/ivsc-firmware) commit 4f15196c0dcb
  ("firmware: add HM2172 and OV02E sensor").

  Note that a surfix "_a1_prod" is added to the requested fw filename, so a
  symbolic link is created for each of the VSC fw blobs.

  [Test Case]

  Boot with firmware blobs installed, and mei_vsc should probe successfully
  without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort. While there is no
  Noble branch yet, Noble is not nominated.

  == original bug report ==

  [ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
  [ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
  [ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
  [ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
  [ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
  [ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

  Upstream commit in https://github.com/intel/ivsc-
  firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

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


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

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

[Timo Aaltonen]

Hello hugh, or anyone else affected,

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

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

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

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

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

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

Title:
  [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode
  failed with error -2

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Wifi is not functional.

  [Fix]

  Cherry-pick relevant FW files.

  [Where Problems Could Occur]

  Only machines with relevant Wifi HW is affected. Potential crashes and
  hangs dues to bad FW.

  [Summary]
  I just upgraded my pc from 23.04 to 23.10,
  and found that my wifi was dead, turn out it's because the firmware load 
failed.

  [Reproduce Steps]
  1. Upgrade 23.04 to 23.10

  [Results]
  Expected: firmware can be loaded
  Actual: firmware load failed

  [Additional Information]
  1. The firmware can be loaded successfully in 23.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 16:58:00 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2023-02-09 (268 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=d2e4673c-e5fe-4a04-8647-bc56a5fa2a08 ro quiet splash 
nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z790-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd01/06/2023:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.4 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY.

  [Fix]

  Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
  from 
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

  [Test Case]

  Run suspend/resume stress test with fwts:
  ```
  $ checkbox-cli run 
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
  ```

  [Where problems could occur]

  The proposed firmware is opaque to us, expect every possible
  regression.

  [Other Info]

  At the time writing this pull request, this firmware blob is public released
  in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, 
nominate
  for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now.

  == original bug report ==

  [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1
  [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb 
board_id 0xff soc_id 0x400c1211
  [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e 
fw_build_timestamp 2022-12-22 12:54 fw_build_id 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23

  Upstream firwmware
  WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from
  
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

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


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

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

[Timo Aaltonen]

Hello hugh, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.4 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode
  failed with error -2

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Wifi is not functional.

  [Fix]

  Cherry-pick relevant FW files.

  [Where Problems Could Occur]

  Only machines with relevant Wifi HW is affected. Potential crashes and
  hangs dues to bad FW.

  [Summary]
  I just upgraded my pc from 23.04 to 23.10,
  and found that my wifi was dead, turn out it's because the firmware load 
failed.

  [Reproduce Steps]
  1. Upgrade 23.04 to 23.10

  [Results]
  Expected: firmware can be loaded
  Actual: firmware load failed

  [Additional Information]
  1. The firmware can be loaded successfully in 23.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 16:58:00 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2023-02-09 (268 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=d2e4673c-e5fe-4a04-8647-bc56a5fa2a08 ro quiet splash 
nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z790-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd01/06/2023:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

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

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

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

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

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

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

Title:
  BT/WiFi coex stability issue on RTL8851BE/RTL8852BE

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

Bug description:
  [SRU Justifcation]

  [Impact]

  On platforms with RTL8851BE/RTL8852BE, bluetooth mouse/keyboard may not work
  smoothly with WiFi connection activated.

  [Fix]

  Proposed firmware upstreamed as:
  * 2afd1423e476 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 7a916315fb28 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 02df6e4f03c0 ("rtw89: 8851b: update fw to v0.29.41.3")

  [Test Case]

  1. Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2. Connected BT KB/MS, and then connected WIFI, select an AP to connect
  3. Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
 smoothly.

  [Where problems could occur]

  This updates opaque firmware blobs, so anything could happen. With 
verifications
  from multiparties, it improves the stability and no other problem found so 
far.

  [Other Info]

  On Lunar, we don't have RTL8851BE enabled, so the related commits are omitted.
  On Mantic and oem-6.5/jammy, we have both.

  == original bug report ==

  1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
  3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond 
smoothly.

  Proposed firmware upstreamed as:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7a916315fb2889aa4b89a71b4eb0b18e5d6153a9
 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
 ("rtw89: 8851b: update fw to v0.29.41.3")

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


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

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

[Frank Heimes]

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

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

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

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

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

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

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

Bug description:
  === Description by mjros...@us.ibm.com  ===

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

  For lunar and mantic, the kernel code did not require backporting due
  to the base kernel version already containing it, but the kernel
  config option still needs to be enabled.  Comparison from
  git.launchpad.net:

  Jammy:
  cat debian.master/config/annotations | grep CONFIG_VFIO_PCI_ZDEV_KVM
  CONFIG_VFIO_PCI_ZDEV_KVMpolicy<{'s390x': 'y'}>
  CONFIG_VFIO_PCI_ZDEV_KVMnote<'LP#1853306 Enable VFIO 
zPCI pass-through for s390x'>

  Lunar:
  cat debian.master/config/annotations | grep CONFIG_VFIO_PCI_ZDEV_KVM
  CONFIG_VFIO_PCI_ZDEV_KVMpolicy<{'s390x': 'n'}>

  Mantic:
  cat debian.master/config/annotations | grep CONFIG_VFIO_PCI_ZDEV_KVM
  CONFIG_VFIO_PCI_ZDEV_KVMpolicy<{'s390x': 'n'}>

  This setting is supposed to default y when S390 && KVM via Kconfig.
  Can this be enabled for lunar, mantic, and future releases?

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

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

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

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

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

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

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2042999

Title:
  BT/WiFi coex stability issue on RTL8851BE/RTL8852BE

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

Bug description:
  [SRU Justifcation]

  [Impact]

  On platforms with RTL8851BE/RTL8852BE, bluetooth mouse/keyboard may not work
  smoothly with WiFi connection activated.

  [Fix]

  Proposed firmware upstreamed as:
  * 2afd1423e476 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 7a916315fb28 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 02df6e4f03c0 ("rtw89: 8851b: update fw to v0.29.41.3")

  [Test Case]

  1. Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2. Connected BT KB/MS, and then connected WIFI, select an AP to connect
  3. Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
 smoothly.

  [Where problems could occur]

  This updates opaque firmware blobs, so anything could happen. With 
verifications
  from multiparties, it improves the stability and no other problem found so 
far.

  [Other Info]

  On Lunar, we don't have RTL8851BE enabled, so the related commits are omitted.
  On Mantic and oem-6.5/jammy, we have both.

  == original bug report ==

  1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
  3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond 
smoothly.

  Proposed firmware upstreamed as:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7a916315fb2889aa4b89a71b4eb0b18e5d6153a9
 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
 ("rtw89: 8851b: update fw to v0.29.41.3")

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

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

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

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

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

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

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

Title:
  New Intel MIPI IPU6 firmware available for MTL-P platform

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Intel IPU6 camera drivers may not load with MTL QS stepping CPUs.

  [Fix]

  New upstream firmware release in
  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87.

  [Test Case]

  1. Install firmware into /lib/firmware/intel/ipu6epmtl_fw.bin and reboot
  2. Try access camera via webcamtest.com
  3. The camera should be working as verified with ES CPUs.

  [Where problems could occur]

  Opaque firmware, and there is no IPU6/MTL platform shipped yet.

  [Other Info]

  Intel MIPI IPU6 on Intel Meteor Lake platform is only supported on 6.5 kernels
  or newer. Nominate Jammy for oem-6.5, Noble as the next LTS, and best effort
  support for Mantic.

  == original bug report ==

  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87
  Intel released a new firmware blob for MIPI IPU6 on Intel Meteor Lake 
platform.

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.4 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  BT/WiFi coex stability issue on RTL8851BE/RTL8852BE

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

Bug description:
  [SRU Justifcation]

  [Impact]

  On platforms with RTL8851BE/RTL8852BE, bluetooth mouse/keyboard may not work
  smoothly with WiFi connection activated.

  [Fix]

  Proposed firmware upstreamed as:
  * 2afd1423e476 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 7a916315fb28 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 02df6e4f03c0 ("rtw89: 8851b: update fw to v0.29.41.3")

  [Test Case]

  1. Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2. Connected BT KB/MS, and then connected WIFI, select an AP to connect
  3. Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
 smoothly.

  [Where problems could occur]

  This updates opaque firmware blobs, so anything could happen. With 
verifications
  from multiparties, it improves the stability and no other problem found so 
far.

  [Other Info]

  On Lunar, we don't have RTL8851BE enabled, so the related commits are omitted.
  On Mantic and oem-6.5/jammy, we have both.

  == original bug report ==

  1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
  3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond 
smoothly.

  Proposed firmware upstreamed as:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7a916315fb2889aa4b89a71b4eb0b18e5d6153a9
 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
 ("rtw89: 8851b: update fw to v0.29.41.3")

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


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

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

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.4 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  New Intel MIPI IPU6 firmware available for MTL-P platform

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Intel IPU6 camera drivers may not load with MTL QS stepping CPUs.

  [Fix]

  New upstream firmware release in
  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87.

  [Test Case]

  1. Install firmware into /lib/firmware/intel/ipu6epmtl_fw.bin and reboot
  2. Try access camera via webcamtest.com
  3. The camera should be working as verified with ES CPUs.

  [Where problems could occur]

  Opaque firmware, and there is no IPU6/MTL platform shipped yet.

  [Other Info]

  Intel MIPI IPU6 on Intel Meteor Lake platform is only supported on 6.5 kernels
  or newer. Nominate Jammy for oem-6.5, Noble as the next LTS, and best effort
  support for Mantic.

  == original bug report ==

  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87
  Intel released a new firmware blob for MIPI IPU6 on Intel Meteor Lake 
platform.

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


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

[Kernel-packages] [Bug 2043686] [NEW] package linux-image-5.15.0-88-generic (not installed) failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal script subprocess ret

[Kostyantyn Halanets]

Public bug reported:

crashed on me

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-88-generic (not installed)
ProcVersionSignature: Ubuntu 5.4.0-1.0~upboard5-generic 5.4.65
Uname: Linux 5.4.0-1-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Nov 15 23:21:42 2023
ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
InstallationDate: Installed on 2023-11-16 (0 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.10
SourcePackage: linux-signed-hwe-5.15
Title: package linux-image-5.15.0-88-generic (not installed) failed to 
install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2023-11-16 (0 days ago)

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


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

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

Title:
  package linux-image-5.15.0-88-generic (not installed) failed to
  install/upgrade: installed linux-image-5.15.0-88-generic package pre-
  removal script subprocess returned error exit status 1

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

Bug description:
  crashed on me

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-88-generic (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-1.0~upboard5-generic 5.4.65
  Uname: Linux 5.4.0-1-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 15 23:21:42 2023
  ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-11-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: linux-signed-hwe-5.15
  Title: package linux-image-5.15.0-88-generic (not installed) failed to 
install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-11-16 (0 days ago)

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


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

[Kernel-packages] [Bug 2036841] Re: [mantic] usb ethernet not working

[Juerg Haefliger]

Not a kernel issue, fixed in ubuntu-raspi-settings.

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

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

Title:
  [mantic] usb ethernet not working

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  Tested with the 20230919.1 arm64 image on rpi-zero2
  This device does not have built-in ethernet, so it relies on USB ethernet to 
connect. I noticed on the initial boot that I was unable to login as 
ubuntu/ubuntu, and I suspect this might be loosely related to this because I 
also noticed that there were no lights on my ethernet dongle. If I unplugged it 
and replugged it, it would light up for a minute then stop. After reboot, I was 
able to login but still no ethernet.  The dongle is detected, but it gets 
renamed from eth0 to something else, which I think is what's causing it to fail 
to be setup properly.

  ubuntu@ubuntu:~$ uname -a
  Linux ubuntu 6.5.0-1002-raspi #2-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep  8 
15:39:40 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

  [6.990858] ax88179_178a 1-1.3.4.3:1.0 eth0: register 'ax88179_178a' at 
usb-3f98.usb-1.3.4.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 
00:0e:c6:c4:1f:57
  ...
  [7.026290] ax88179_178a 1-1.3.4.3:1.0 enx000ec6c41f57: renamed from eth0

  ubuntu@ubuntu:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enx000ec6c41f57:  mtu 1500 qdisc noop state DOWN 
group default qlen 1000
  link/ether 00:0e:c6:c4:1f:57 brd ff:ff:ff:ff:ff:ff
  3: wlan0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether e4:5f:01:10:82:e1 brd ff:ff:ff:ff:ff:ff

  I am able to manually configure ethernet though, so the device itself
  is working with this kernel.

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


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

[Kernel-packages] [Bug 2043005] Re: mlxbf-pmc: Fix crspace event offsets

[Bartlomiej Zolnierkiewicz]

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

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

Title:
  mlxbf-pmc: Fix crspace event offsets

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

Bug description:
  SRU Justification:

  [Impact]
  Currently, the offsets calculated for programming crspace type events on 
BlueField-3 are incorrect and this leads to a mismatch of counter numbers 
between the driver and actual HW where, for example, event2 in the driver is 
actually event4 in HW.

  [Fix]
  Fix the offset calculation for programming crspace events.

  [Test Case]
  On a BlueField-3 platform, program any valid event number to the event sysfs 
and check that the corresponding counter value increments.

  [Regression Potential]
  This is a bug fix and the regression potential can be considered minimal.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Andrzej Stencel]

$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: (none)
  Candidate: 6.5.0.10.12
  Version table:
 6.5.0.10.12 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
 6.5.0.9.11 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Timo Aaltonen]

please run 'apt-cache policy linux-image-generic'

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2042716] Re: [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode failed with error -2

[Juerg Haefliger]

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

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

Title:
  [Intel AX201] Direct firmware load for iwlwifi-so-a0-hr-b0-83.ucode
  failed with error -2

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Wifi is not functional.

  [Fix]

  Cherry-pick relevant FW files.

  [Where Problems Could Occur]

  Only machines with relevant Wifi HW is affected. Potential crashes and
  hangs dues to bad FW.

  [Summary]
  I just upgraded my pc from 23.04 to 23.10,
  and found that my wifi was dead, turn out it's because the firmware load 
failed.

  [Reproduce Steps]
  1. Upgrade 23.04 to 23.10

  [Results]
  Expected: firmware can be loaded
  Actual: firmware load failed

  [Additional Information]
  1. The firmware can be loaded successfully in 23.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 16:58:00 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2023-02-09 (268 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=d2e4673c-e5fe-4a04-8647-bc56a5fa2a08 ro quiet splash 
nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z790-P WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd01/06/2023:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2043005] Re: mlxbf-pmc: Fix crspace event offsets

[Bartlomiej Zolnierkiewicz]

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

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

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

Title:
  mlxbf-pmc: Fix crspace event offsets

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  SRU Justification:

  [Impact]
  Currently, the offsets calculated for programming crspace type events on 
BlueField-3 are incorrect and this leads to a mismatch of counter numbers 
between the driver and actual HW where, for example, event2 in the driver is 
actually event4 in HW.

  [Fix]
  Fix the offset calculation for programming crspace events.

  [Test Case]
  On a BlueField-3 platform, program any valid event number to the event sysfs 
and check that the corresponding counter value increments.

  [Regression Potential]
  This is a bug fix and the regression potential can be considered minimal.

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


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

[Kernel-packages] [Bug 2036697] Re: i915: Update DMC, GuC, HuC fw for Meteor Lake

[Juerg Haefliger]

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

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

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

Title:
  i915: Update DMC, GuC, HuC fw for Meteor Lake

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

Bug description:
  [Impact]
  There are new firmware versions available for MTL, which contain undisclosed 
fixes.

  lunar is omitted as it doesn't have support for MTL, while jammy does
  via oem-6.5

  [Test case]
  Install the update, test on MTL that things keep working at least the same as 
before.

  [Regression potential]
  MTL is a new platform being enabled, these do not affect any shipping hardware

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Andrzej Stencel]

Trying to attach the output of `sudo -E oem-getlogs`, but getting an
error when trying to post the comment.

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Andrzej Stencel]

> I have no idea why I'm at that kernel version.
> I have a Dell precision that came with Ubuntu preinstalled and just did 
> Ubuntu updates on that.

Same story here. Got the Dell Precision 5560 with Ubuntu 20.04, then I think I 
updated to:
- 22.04
- 22.10 (or perhaps skipped this one)
- 23.04
- 23.10

$ uname -a
Linux astencel-dell 5.14.0-1054-oem #61-Ubuntu SMP Fri Oct 14 13:05:50 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2043580] Re: New Intel MIPI IPU6 firmware available for MTL-P platform

[Juerg Haefliger]

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2043580

Title:
  New Intel MIPI IPU6 firmware available for MTL-P platform

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Intel IPU6 camera drivers may not load with MTL QS stepping CPUs.

  [Fix]

  New upstream firmware release in
  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87.

  [Test Case]

  1. Install firmware into /lib/firmware/intel/ipu6epmtl_fw.bin and reboot
  2. Try access camera via webcamtest.com
  3. The camera should be working as verified with ES CPUs.

  [Where problems could occur]

  Opaque firmware, and there is no IPU6/MTL platform shipped yet.

  [Other Info]

  Intel MIPI IPU6 on Intel Meteor Lake platform is only supported on 6.5 kernels
  or newer. Nominate Jammy for oem-6.5, Noble as the next LTS, and best effort
  support for Mantic.

  == original bug report ==

  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87
  Intel released a new firmware blob for MIPI IPU6 on Intel Meteor Lake 
platform.

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


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

[Kernel-packages] [Bug 2042074] Re: missing mei_vsc firmware for HM2172 and OV02E sensor

[Juerg Haefliger]

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2042074

Title:
  missing mei_vsc firmware for HM2172 and OV02E sensor

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  Missing mei_vsc firmware for HM2172 and OV02E sensor.

mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
mei_vsc spi-INTC10D0:00: reset failed ret = -19
mei_vsc spi-INTC10D0:00: link layer initialization failed.
mei_vsc spi-INTC10D0:00: init hw failure.

  [Fix]

  Upstream (https://github.com/intel/ivsc-firmware) commit 4f15196c0dcb
  ("firmware: add HM2172 and OV02E sensor").

  Note that a surfix "_a1_prod" is added to the requested fw filename, so a
  symbolic link is created for each of the VSC fw blobs.

  [Test Case]

  Boot with firmware blobs installed, and mei_vsc should probe successfully
  without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort. While there is no
  Noble branch yet, Noble is not nominated.

  == original bug report ==

  [ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
  [ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
  [ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
  [ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
  [ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
  [ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

  Upstream commit in https://github.com/intel/ivsc-
  firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

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


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

[Kernel-packages] [Bug 2042534] Re: System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY

[Juerg Haefliger]

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2042534

Title:
  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Incomplete

Bug description:
  [SRU Justification]

  [Impact]

  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY.

  [Fix]

  Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
  from 
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

  [Test Case]

  Run suspend/resume stress test with fwts:
  ```
  $ checkbox-cli run 
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
  ```

  [Where problems could occur]

  The proposed firmware is opaque to us, expect every possible
  regression.

  [Other Info]

  At the time writing this pull request, this firmware blob is public released
  in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, 
nominate
  for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now.

  == original bug report ==

  [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1
  [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb 
board_id 0xff soc_id 0x400c1211
  [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e 
fw_build_timestamp 2022-12-22 12:54 fw_build_id 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23

  Upstream firwmware
  WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from
  
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Kai-Chuan Hsieh]

The platform is shipped with focal preinstalled. May I know how did you
upgrade to the current codename you are using?

Could you attach $ sudo -E oem-getlogs to let me know your current
configuration?

Thanks,

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2042534] Re: System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY

[Juerg Haefliger]

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

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

Title:
  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY

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

Bug description:
  [SRU Justification]

  [Impact]

  System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm -
  2R8DY.

  [Fix]

  Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
  from 
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

  [Test Case]

  Run suspend/resume stress test with fwts:
  ```
  $ checkbox-cli run 
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
  ```

  [Where problems could occur]

  The proposed firmware is opaque to us, expect every possible
  regression.

  [Other Info]

  At the time writing this pull request, this firmware blob is public released
  in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, 
nominate
  for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now.

  == original bug report ==

  [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1
  [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb 
board_id 0xff soc_id 0x400c1211
  [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e 
fw_build_timestamp 2022-12-22 12:54 fw_build_id 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23

  Upstream firwmware
  WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from
  
https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9
  should be used.

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


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

[Kernel-packages] [Bug 2042999] Re: BT/WiFi coex stability issue on RTL8851BE/RTL8852BE

[Juerg Haefliger]

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

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

Title:
  BT/WiFi coex stability issue on RTL8851BE/RTL8852BE

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justifcation]

  [Impact]

  On platforms with RTL8851BE/RTL8852BE, bluetooth mouse/keyboard may not work
  smoothly with WiFi connection activated.

  [Fix]

  Proposed firmware upstreamed as:
  * 2afd1423e476 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 7a916315fb28 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 02df6e4f03c0 ("rtw89: 8851b: update fw to v0.29.41.3")

  [Test Case]

  1. Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2. Connected BT KB/MS, and then connected WIFI, select an AP to connect
  3. Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
 smoothly.

  [Where problems could occur]

  This updates opaque firmware blobs, so anything could happen. With 
verifications
  from multiparties, it improves the stability and no other problem found so 
far.

  [Other Info]

  On Lunar, we don't have RTL8851BE enabled, so the related commits are omitted.
  On Mantic and oem-6.5/jammy, we have both.

  == original bug report ==

  1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
  2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
  3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond 
smoothly.

  Proposed firmware upstreamed as:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
 ("rtw89: 8852b: update fw to v0.29.29.5")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7a916315fb2889aa4b89a71b4eb0b18e5d6153a9
 ("rtw89: 8852b: update fw to v0.29.29.4")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
 ("rtw89: 8851b: update fw to v0.29.41.3")

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[joepadmiraal]

I installed the latest oem kernel with: `sudo apt install linux-oem-22.04`.
It installed the 6.5 kernel and I can confirm it solved the issue.

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2043580] Re: New Intel MIPI IPU6 firmware available for MTL-P platform

[Juerg Haefliger]

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

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

Title:
  New Intel MIPI IPU6 firmware available for MTL-P platform

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Intel IPU6 camera drivers may not load with MTL QS stepping CPUs.

  [Fix]

  New upstream firmware release in
  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87.

  [Test Case]

  1. Install firmware into /lib/firmware/intel/ipu6epmtl_fw.bin and reboot
  2. Try access camera via webcamtest.com
  3. The camera should be working as verified with ES CPUs.

  [Where problems could occur]

  Opaque firmware, and there is no IPU6/MTL platform shipped yet.

  [Other Info]

  Intel MIPI IPU6 on Intel Meteor Lake platform is only supported on 6.5 kernels
  or newer. Nominate Jammy for oem-6.5, Noble as the next LTS, and best effort
  support for Mantic.

  == original bug report ==

  
https://github.com/intel/ipu6-camera-bins/commit/0dad591f1b5dc7bcd6891a36dca64219eb6dbe87
  Intel released a new firmware blob for MIPI IPU6 on Intel Meteor Lake 
platform.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers

[Launchpad Bug Tracker]

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

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

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

Title:
  RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
  unmaintained upstream drivers

Status in bumblebee package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  This legacy driver had the last update on 2022.11.22, and is EOL
  upstream. We should remove it from the archive before the next LTS,
  maybe even before Mantic is released.

  We're planning on migrating the kernel from fbdev drivers to using
  simpledrm, but this old driver doesn't support the fbdev emulation
  layer, meaning that VT's would remain blank when the driver is used.

  Similarly 418-server and 450-server are also EOL and unsupported.

  Also we shomehow have remains of 440-server published in the archive,
  with many superseeded (hostile takeover) of binary packages by
  450-server.

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


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

[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on

[koba]

Verified with CID:202309-32128, 
~~~
$ uname -a
Linux 6.5.0-1008-oem #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 10 13:08:33 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
~~~
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
0
$ sudo rtcwake -m mem -s 5
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
4017704
~~~

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

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

Title:
  Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle
  screen on

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

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.

  [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814

  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

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


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

[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card

[Stefan Bader]

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

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

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

Title:
  System hang after unplug/plug DP monitor with AMD W7500 card

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System hangs and no external output after unplug/plug DP monitor. (AMD Radeon 
Pro W7500)
  Observed a bunch of [Hardware Error] messages and finally amdgpu crashed.

  [Fix]
  AMD provides a patch to fix the issue
  https://www.spinics.net/lists/amd-gfx/msg99737.html

  which is included in v6.7-rc1
  7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code

  [Testcase]
  1. Connect the DUT to an external DP monitor via one of the ports on the AMD 
graphics card
  2. Boot into Ubuntu
  3. Unplug the DP cable from the DUT
  4. Wait for 30 seconds
  5. Replug in the DP cable
  6. Make sure the system doesn't hang and the external DP monitor works

  [Where probles could occur]
  The patch make sure MACO is supported only if BACO is supported. It creates a 
stricter rule for MACO to avoid MACO is enabled with BACO supports. It should 
be safe to apply stricter rules to enable features.

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


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

[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[joepadmiraal]

I have no idea why I'm at that kernel version.
I'll try to update it.
I have a Dell precision that came with Ubuntu preinstalled and just did Ubuntu 
updates on that. 
So maybe something in the Dell configuration makes it stick at this kernel 
version.
And it seems more people are having this issue.
At least people with this issue can now find the cause via google.

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2043665] [NEW] Hundreds of errors per second: kernel: pcieport 0000:00:1c.3: PCIe Bus Error

[icaria36]

Public bug reported:

After a fresh 23.10 install I have noticed that booting up my PC in the
morning was taking a long time. Checking journalctl there are hundreds
of warnings generated every  second, and not only at boot time (see
below). Searching for this problem I found a stopgap solution by adding
this instruction in GRUB:

pcie_aspm=off

However, as a plain Ubuntu user I should be having this problem of long
boot times and edit GRUB to "fix" it, when the problem captured in the
log isn't even fixed, I just avoided it with instruction. This is why
I'm reporting it in case it helps find the original cause.

Previously I was running 23.04 on the same PC and booting times were
short, just normal. I believe this is a new problem even when the
hardware is the same and I haven't done any changes apart from
upgrading.

The errors are all the same:

Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: AER: Corrected error 
received: :00:1c.3
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: PCIe Bus Error: 
severity=Corrected, type=Physical Layer, (Receiv>
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:   device [8086:7abb] error 
status/mask=0001/2000
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:[ 0] RxErr  
(First)
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: AER: Corrected error 
received: :00:1c.3
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: PCIe Bus Error: 
severity=Corrected, type=Physical Layer, (Receiv>
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:   device [8086:7abb] error 
status/mask=0001/2000
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:[ 0] RxErr  
(First)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 16 09:38:28 2023
InstallationDate: Installed on 2023-11-13 (2 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=fa113624-262e-4625-ba8b-eabf66ab696c ro pcie_aspm=off
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-10-generic N/A
 linux-backports-modules-6.5.0-10-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2021
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.10
dmi.board.asset.tag: Default string
dmi.board.name: MPG Z690 FORCE WIFI (MS-7D30)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.10:bd12/03/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D30:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690FORCEWIFI(MS-7D30):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D30
dmi.product.sku: Default string
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug mantic

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

Title:
  Hundreds of errors per second: kernel: pcieport :00:1c.3: PCIe Bus
  Error

Status in linux package in Ubuntu:
  New

Bug description:
  After a fresh 23.10 install I have noticed that booting up my PC in
  the morning was taking a long time. Checking journalctl there are
  hundreds of warnings generated every  second, and not only at boot
  time (see below). Searching for this problem I found a stopgap
  solution by adding this instruction in GRUB:

  pcie_aspm=off

  However, as a plain Ubuntu user I should be having this problem of
  long boot times and edit GRUB to "fix" it, when the problem captured
  in the log isn't even fixed, I just avoided it with instruction. This
  is why I'm reporting it in case it helps find the original cause.

  Previously I was running 23.04 on the same PC and booting times were
  short, just normal. I believe this is a new problem even when the
  hardware is the same and I haven't done any changes apart from
  upgrading.

  The errors are all the same:

  Nov 16 

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Roxana Nicolescu]

@eitsop It is part of the 2023.10.30 cycle and it will be released on
the week of 4th of December as described here https://kernel.ubuntu.com.

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

Title:
  Include cifs.ko in linux-modules package

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

Bug description:
  SRU Justification:

  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

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


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

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

[Hervé Fache]

When booting on Linux 6.2 the bug disappears (and other bugs too BTW:
broken suspend, missing kernel logs)

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: Failed to start 

[Kernel-packages] [Bug 2043561] Re: rtl8761bu bluetooth dongle bails out or looses device connection

[Juerg Haefliger]

Is this a regression? If so, what was the last known good kernel?

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

Title:
  rtl8761bu bluetooth dongle bails out or looses device connection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Environment:
  Bluetooth dongle connected to integrated Hub -> bluetooth mouse

  After a fresh boot into (K)ubuntu, the dongle/mouse works.
  Then, after some minutes, the mouse stops working.

  Errors:
  A) Some times, the bluetooth dongle is gone and I have to re-plug it to make 
it work again.
  B) Some times, it is enough, to deactivate and activate bluetooth in the 
settings.

  What is strange is, that I can't find any crash or similar entries in
  the logs for A).

  Following the "dmesg|grep -i  bluetooth" and the "journalctl" of that moment:
  
  ─$ sudo dmesg|grep -i bluetooth
  [2.017029] usb 1-8.1: Product: Bluetooth Radio
  [   16.482420] Bluetooth: Core ver 2.22
  [   16.482513] NET: Registered PF_BLUETOOTH protocol family
  [   16.482515] Bluetooth: HCI device and connection manager initialized
  [   16.482548] Bluetooth: HCI socket layer initialized
  [   16.482549] Bluetooth: L2CAP socket layer initialized
  [   16.482553] Bluetooth: SCO socket layer initialized
  [   16.639986] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b 
lmp_ver=0a lmp_subver=8761
  [   16.640993] Bluetooth: hci0: RTL: rom_version status=0 version=1
  [   16.640996] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
  [   16.643667] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
  [   16.643720] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
  [   16.796044] Bluetooth: hci0: RTL: fw version 0xdfc6d922
  [   17.340032] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   17.340034] Bluetooth: BNEP filters: protocol multicast
  [   17.340036] Bluetooth: BNEP socket layer initialized
  [   17.340857] Bluetooth: MGMT ver 1.22
  [   25.315698] Bluetooth: RFCOMM TTY layer initialized
  [   25.315714] Bluetooth: RFCOMM socket layer initialized
  [   25.315721] Bluetooth: RFCOMM ver 1.11
  [  173.107927] hid-generic 0005:046D:B031.0003: input,hidraw2: BLUETOOTH HID 
v0.10 Mouse [LIFT] on a0:9f:10:be:79:e4
  [ 1698.769225] usb 1-8.4: Product: Bluetooth Radio
  [ 1698.782108] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b 
lmp_ver=0a lmp_subver=8761
  [ 1698.783105] Bluetooth: hci0: RTL: rom_version status=0 version=1
  [ 1698.783119] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
  [ 1698.784771] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
  [ 1698.784945] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
  [ 1698.943074] Bluetooth: hci0: RTL: fw version 0xdfc6d922
  [ 1699.011186] Bluetooth: MGMT ver 1.22
  [ 1711.453643] hid-generic 0005:046D:B031.0004: input,hidraw2: BLUETOOTH HID 
v0.10 Mouse [LIFT] on a0:9f:10:be:79:e4
  [ 1926.008318] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1926.008337] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1926.008345] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1926.008352] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1926.008358] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1926.008364] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1926.008370] Bluetooth: hci0: ACL packet for unknown connection handle 16
  [ 1930.221737] hid-generic 0005:046D:B031.0005: input,hidraw2: BLUETOOTH HID 
v0.10 Mouse [LIFT] on a0:9f:10:be:79:e4
  


  
  
  Nov 15 10:12:39 media-pc-lx dbus-daemon[1094]: [system] Rejected send 
message, 0 matched rules; type="error", sender=":1.57" (uid=1000 pid=4460 
comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" 
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" 
requested_reply="0" destination=":1.3" (uid=0 pid=1093 
comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")
  Nov 15 10:12:39 media-pc-lx dbus-daemon[1094]: [system] Rejected send 
message, 0 matched rules; type="error", sender=":1.57" (uid=1000 pid=4460 
comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" 
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" 
requested_reply="0" destination=":1.3" (uid=0 pid=1093 
comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")
  Nov 15 10:12:39 media-pc-lx dbus-daemon[1094]: [system] Rejected send 
message, 0 matched rules; type="error", sender=":1.57" (uid=1000 pid=4460 
comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" 
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" 
requested_reply="0" destination=":1.3" (uid=0 pid=1093 

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

[madigal]

Maybe related to: https://github.com/intel/thermal_daemon/pull/422/files
or: https://github.com/intel/thermal_daemon/issues/416

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: Failed to