[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

[You-Sheng Yang]

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

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

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

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

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

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

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

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


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

Please note that #16 has been tested on Jammy GA. The Jammy HWE uses the
same kernel version and package content as Lunar. Refer to Lunar's test
plan for Jammy HWE testing.

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type 

[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

[You-Sheng Yang]

** Description changed:

- TBD.
+ NVME module left unready, therefore not recognized by the installation
+ process, and/or after installation with following error messages:
+ 
+ kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
+ kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
+ kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
+ kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

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

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

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

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


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

[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel

[David Rutherford]

I assume you mean to run this

journalctl -k > journal_good.txt

from the working journal?

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

Title:
  Black screen at login after updating to this kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Inspiron  AMD A10 Laptop
  Linux Mint Mate O/S

  After updating the kernel I restarted the laptop. After entering my
  password and logging in the screen goes black with occasional flashes
  of, I guess i'd call it static.

  The same thing happened with the previous kernel I installed, ending
  .87, when I was running Zorin OS.

  After un-installing the system returns to opening as usual.

  System:
Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working 
correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco
  dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

  Machine:
Type: Portable System: Dell product: Inspiron  v: A12 serial: 
 Chassis:
  type: 8 v: A12 serial: 
Mobo: Dell model: 0CX84K v: A00 serial:  UEFI: Dell v: 
A12
  date: 08/30/2016

  CPU:
Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 
64 type: MT MCP
  arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 
1: 2673 2: 2680
  3: 3053 4: 2700 bogomips: 14374
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu 
v: kernel ports:
  active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 
Mobile]
  vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 
bus-ID: 03:00.0
  chip-ID: 1002:6660
Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 
2-4:3
  chip-ID: 0c45:6712
Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: 
X:
  loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu 
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96
Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9")
OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 
5.15.0-76-generic)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  I don't have a lot of experience with reporting errors so I hope this
  helps!

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


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

[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel

[David Rutherford]

** Attachment added: "journal_good.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716723/+files/journal_good.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/2042075

Title:
  Black screen at login after updating to this kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Inspiron  AMD A10 Laptop
  Linux Mint Mate O/S

  After updating the kernel I restarted the laptop. After entering my
  password and logging in the screen goes black with occasional flashes
  of, I guess i'd call it static.

  The same thing happened with the previous kernel I installed, ending
  .87, when I was running Zorin OS.

  After un-installing the system returns to opening as usual.

  System:
Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working 
correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco
  dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

  Machine:
Type: Portable System: Dell product: Inspiron  v: A12 serial: 
 Chassis:
  type: 8 v: A12 serial: 
Mobo: Dell model: 0CX84K v: A00 serial:  UEFI: Dell v: 
A12
  date: 08/30/2016

  CPU:
Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 
64 type: MT MCP
  arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 
1: 2673 2: 2680
  3: 3053 4: 2700 bogomips: 14374
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu 
v: kernel ports:
  active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 
Mobile]
  vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 
bus-ID: 03:00.0
  chip-ID: 1002:6660
Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 
2-4:3
  chip-ID: 0c45:6712
Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: 
X:
  loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu 
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96
Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9")
OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 
5.15.0-76-generic)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  I don't have a lot of experience with reporting errors so I hope this
  helps!

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


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

[Kernel-packages] [Bug 2042902] [NEW] ucm2: soundwire: add rt713 SDCA device

[Artur Pak]

Public bug reported:

[ Impact ]
Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
Without correct configurations in userspace above codecs cannot be used.

[ Fix ]
Adding rt713 config files in ucm2 will allow to utilize those codecs.

[ Test Plan ]
In progress

** Affects: alsa-ucm-conf (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: pulseaudio (Ubuntu) => alsa-ucm-conf (Ubuntu)

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

Title:
  ucm2: soundwire: add rt713 SDCA device

Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [ Impact ]
  Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
  Without correct configurations in userspace above codecs cannot be used.

  [ Fix ]
  Adding rt713 config files in ucm2 will allow to utilize those codecs.

  [ Test Plan ]
  In progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+subscriptions


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

[Timo Aaltonen]

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

** Changed in: linux-oem-6.5 (Ubuntu Noble)
   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/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:
  New
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 2042902] [NEW] ucm2: soundwire: add rt713 SDCA device

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[ Impact ]
Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
Without correct configurations in userspace above codecs cannot be used.

[ Fix ]
Adding rt713 config files in ucm2 will allow to utilize those codecs.

[ Test Plan ]
In progress

** Affects: alsa-ucm-conf (Ubuntu)
 Importance: Undecided
 Status: New

-- 
ucm2: soundwire: add rt713 SDCA device
https://bugs.launchpad.net/bugs/2042902
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to alsa-ucm-conf in Ubuntu.

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

[Kernel-packages] [Bug 2042897] [NEW] Bump arm64's CONFIG_NR_CPUS to 512

[dann frazier]

Public bug reported:

arm64 server platforms have been announced that will have more cores
than the max of 256 that we currently support. For example, systems w/ 2
NVIDIA Grace chips, each of containing 2 nodes of 72 cores = 288.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  Bump arm64's CONFIG_NR_CPUS to 512

Status in linux package in Ubuntu:
  In Progress

Bug description:
  arm64 server platforms have been announced that will have more cores
  than the max of 256 that we currently support. For example, systems w/
  2 NVIDIA Grace chips, each of containing 2 nodes of 72 cores = 288.

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


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

[Kernel-packages] [Bug 2042894] [NEW] package linux-intel-iotg-5.15-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools

[Prabhat Chand Pandey]

Public bug reported:

crash while install

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-intel-iotg-5.15-tools-common (not installed)
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
AptOrdering:
 linux-intel-iotg-5.15-tools-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Nov  7 11:00:45 2023
DpkgTerminalLog:
 Preparing to unpack 
.../linux-intel-iotg-5.15-tools-common_5.15.0-1043.49~20.04.1_all.deb ...
 Unpacking linux-intel-iotg-5.15-tools-common (5.15.0-1043.49~20.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-5.15-tools-common_5.15.0-1043.49~20.04.1_all.deb
 (--unpack):
  trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.4.0-166.183
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.4.0-166.183
InstallationDate: Installed on 2021-11-06 (730 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: linux-intel-iotg-5.15
Title: package linux-intel-iotg-5.15-tools-common (not installed) failed to 
install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-166.183
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-intel-iotg-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-intel-iotg-5.15-tools-common (not installed) failed to
  install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also
  in package linux-tools-common 5.4.0-166.183

Status in linux-intel-iotg-5.15 package in Ubuntu:
  New

Bug description:
  crash while install

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-intel-iotg-5.15-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  AptOrdering:
   linux-intel-iotg-5.15-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov  7 11:00:45 2023
  DpkgTerminalLog:
   Preparing to unpack 
.../linux-intel-iotg-5.15-tools-common_5.15.0-1043.49~20.04.1_all.deb ...
   Unpacking linux-intel-iotg-5.15-tools-common (5.15.0-1043.49~20.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-5.15-tools-common_5.15.0-1043.49~20.04.1_all.deb
 (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.4.0-166.183
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-166.183
  InstallationDate: Installed on 2021-11-06 (730 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: linux-intel-iotg-5.15
  Title: package linux-intel-iotg-5.15-tools-common (not installed) failed to 
install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-166.183
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg-5.15/+bug/2042894/+subscriptions


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

[Kernel-packages] [Bug 2041782] Re: spi: spi-cadence-quadspi: Fix ospi resume failures conflicts

[Radhey Shyam Pandey]

The conflict resolved in 2023.1_update branch is basically merging
xilinx and upstream resume implementation. In cqspi_resume() I see that
below code sequence[1] is called twice which can be optimized but is
functionally working as reported by the internal regression team.

[1]
cqspi_controller_init(cqspi);
cqspi->current_cs = -1;
cqspi->sclk = 0;

I had also discussed this merge conflict with the driver owner and he
confirmed that the merge commit published to 2023.1_update should
functionally work as we are calling _init with the same values so should
not have any side effects.

Now there are two choices -
a) Continue to use merge resolution published to the 2023.1_update branch.
b) Use the below optimize fix for cqspi_resume.

static int cqspi_resume(struct device *dev)
{
struct cqspi_st *cqspi = dev_get_drvdata(dev);
struct spi_master *master = dev_get_drvdata(dev);
u32 ret;

clk_prepare_enable(cqspi->clk);
cqspi_wait_idle(cqspi);
cqspi_controller_init(cqspi);
cqspi->current_cs = -1;
cqspi->sclk = 0;
cqspi->extra_dummy = false;
cqspi->clk_tuned = false;

ret = cqspi_setup_flash(cqspi);
if (ret) {
dev_err(dev, "failed to setup flash parameters %d\n", ret);
return ret;
}

ret = zynqmp_pm_ospi_mux_select(cqspi->pd_dev_id,
PM_OSPI_MUX_SEL_LINEAR);
if (ret)
return ret;

/* Set the direction as output and enable the output */
gpio_direction_output(cqspi->gpio, 1);
udelay(1);

/* Set value 0 to pin */
gpio_set_value(cqspi->gpio, 0);
udelay(10);
 
/* Set value 1 to pin */
gpio_set_value(cqspi->gpio, 1);
udelay(35);

return spi_master_resume(master);
}

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

Title:
  spi: spi-cadence-quadspi: Fix ospi resume failures conflicts

Status in linux-xilinx-zynqmp package in Ubuntu:
  New
Status in linux-xilinx-zynqmp source package in Jammy:
  New

Bug description:
  jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence-
  quadspi: Fix ospi resume failure" from the Xilinx tree , branch
  xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been
  upstreamed and completely rewrites the function cqspi_resume(). A
  change has landed in the v5.15.111 upstream stable release which
  conflicts with this Xilinx patch in such a way that we don't know how
  to resolve the conflicts and keep the functionality intact.

  We have found where Xlinx resolved the merge on the XIlinx 6.1 branch
  but it doesn't seem correct. In the original commit:

  (https://github.com/Xilinx/linux-
  xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f)

  in the function cqspi_resume() ,  the call to cqspi_controller_enable()   is 
removed and ZynqMP specific controls are added. Upstream fixed an issue with 
suspend-resume 
(https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc).
 The upstream fix replaces the cqspi_controller_enable() with some clock 
initializations and a call to cqspi_controller_init() which does some register 
writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by 
concatenating the two commit's changes to
  cqspi_resume() 
(https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271),
 the end result is that cqspi_resume() consists of ZynqMP specific controls 
followed by a (nested) call to cqspi_controller_enable(), the exact function 
call that was removed in XIlinx's original commit.

  This bug is to track how this merge conflict is resolved.

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


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

[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization

[Ubuntu Kernel Bot]

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


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

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

Title:
  Kernel oops on 32-0bit kernels due to x86_cache_alignment
  initialization

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Triaged
Status in linux-gcp source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from

git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar

  [Fix]

  * Clean cherry pick from linux-next, commit 3e3255265291

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression, isolated fix slightly modifying when value becomes
available.

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


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

[Kernel-packages] [Bug 2036600] Re: Azure: Fix Azure vendor ID

[Ubuntu Kernel Bot]

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


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

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

Title:
  Azure: Fix Azure vendor ID

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The linux-azure 6.2 kernel doesn't report a correct GUEST_ID

  There is a mistake in the commit
  (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
  :

  Before the commit, the good guest_id is 0x81860210.

  With the commit, the generated guest_id is incorrect:
  0x00860210, i.e. the 0x81 from bit 56~63 are dropped.

  See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
  * Bit(s)
  * 63 - Indicates if the OS is Open Source or not; 1 is Open Source

  * 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
  I'll post a patch to LKML to fix this typo.

  * 55:48 - Distro specific identification
  * 47:16 - Linux kernel version number
  * 15:0 - Distro specific identification

  See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
  windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)

  As a result, the host thinks that the VM is not an open-source OS, and
  it's not Linux. Consequently, the "VM Availability" fron Azure portal
  is 0 (unhealthy): some users rely on the info to manage their VMs,
  e.g. if the VM is erroneously reported "unhealthy", the VM may be
  killed and re-created, and the new VM is still "unhealthy", and the VM
  may be killed and re-created again...

  Please consider integrating the below fix ASAP. This affects regular
  VMs, and I think this affects CVMs as well.

  The fix should be:

  diff --git a/include/asm-generic/hyperv-tlfs.h 
b/include/asm-generic/hyperv-tlfs.h
  @@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
  *
  */

  -#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
  +#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  VMs could be misclassified.

  [Other Info]

  SF: #00368936

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


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

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Ubuntu Kernel Bot]

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


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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

[Dan O'Neill]

Description: Ubuntu 22.04.3 LTS
Release: 22.04

uname -a output:
Linux olive 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct  9 
15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux


I modified /etc/default/grub with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2"

and it only made the problem worse.

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-hwe-6.2 source package in Lunar:
  Invalid

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2
  fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
    lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1017.17~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.2' to 'verification-done-jammy-linux-lowlatency-
hwe-6.2'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.2' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.2'.


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


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


** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.2-v2 
verification-needed-jammy-linux-lowlatency-hwe-6.2

-- 
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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

[Launchpad Bug Tracker]

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

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

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-hwe-6.2 source package in Lunar:
  Invalid

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2
  fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
    lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

[Bug Watch Updater]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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

[Mario Limonciello]

This issue is fixed in 6.6-rc3: 2de19022c5d7 ("drm/amd/display: fix the
ability to use lower resolution modes on eDP")

It's backported to stable 6.5.6 as 79aec38ba852 ("drm/amd/display: fix
the ability to use lower resolution modes on eDP").

Canonical needs to pull the fix into their kernel.


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2693
   https://gitlab.freedesktop.org/drm/amd/-/issues/2693

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

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

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

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

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

Title:
  Changing display resolution leads into black screen

Status in Linux:
  Unknown
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 2042888] Re: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic.

[CocoZT_Wang]

** Attachment added: "enable SMT then check dmesg in OS"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2042888/+attachment/5716655/+files/dmesg_smt_enable.txt

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

Title:
  It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system
  dmesg log with kernel version 6.2.0-060200-generic.

Status in linux-hwe package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 22.04.3 LTS
  Release: 22.04
  Kernel: 6.2.0-060200-generic
  CPU: 1x EPYC 9654
  DIMM: 2x Samsung DDR5 16G

  1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also 
tried on kernel 6.5.7-060507)
  2.Reboot system and enable SMT-Control from BIOS.
  3.Boot to system to read lscpu.txt and dmesg.txt,
  lscpu log show Off-line CPU(s) info as below:

  CPU(s):  192
  On-line CPU(s) list: 0-95,97-191
  Off-line CPU(s) list:96
  Vendor ID:   AuthenticAMD
  Model name:  AMD EPYC 9654 96-Core Processor
  CPU family:  25
  Model:   17
  Thread(s) per core:  2
  Core(s) per socket:  96
  Socket(s):   1
  Stepping:1
  Frequency boost: enabled

  dmesg log show CPU fail info as below,

  [0.360560] smp: Bringing up secondary CPUs ...
  [0.360708] x86: Booting SMP configuration:
  [0.360711]  node  #0, CPUs:  #1   #2   #3   #4   #5   #6   #7 
  #8   #9  #10  #11  #12  #13  #14  #15  #16  #17  #18  #19  #20  #21  #22  #23 
 #24  #25  #26  #27  #28  #29  #30  #31  #32  #33  #34  #35  #36  #37  #38  #39 
 #40  #41  #42  #43  #44  #45  #46  #47  #48  #49  #50  #51  #52  #53  #54  #55 
 #56  #57  #58  #59  #60  #61  #62  #63  #64  #65  #66  #67  #68  #69  #70  #71 
 #72  #73  #74  #75  #76  #77  #78  #79  #80  #81  #82  #83  #84  #85  #86  #87 
 #88  #89  #90  #91  #92  #93  #94  #95  #96
  [   10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96
  [   10.631842]   #97

  BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with
  Ubuntu 22.04.3-kernel 6.2.0 and 6.5.7.

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


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

[Kernel-packages] [Bug 2042888] Re: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic.

[CocoZT_Wang]

** Attachment added: "enable SMT then check lscpu in OS"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2042888/+attachment/5716654/+files/dmesg_smt_enable.txt

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

Title:
  It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system
  dmesg log with kernel version 6.2.0-060200-generic.

Status in linux-hwe package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 22.04.3 LTS
  Release: 22.04
  Kernel: 6.2.0-060200-generic
  CPU: 1x EPYC 9654
  DIMM: 2x Samsung DDR5 16G

  1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also 
tried on kernel 6.5.7-060507)
  2.Reboot system and enable SMT-Control from BIOS.
  3.Boot to system to read lscpu.txt and dmesg.txt,
  lscpu log show Off-line CPU(s) info as below:

  CPU(s):  192
  On-line CPU(s) list: 0-95,97-191
  Off-line CPU(s) list:96
  Vendor ID:   AuthenticAMD
  Model name:  AMD EPYC 9654 96-Core Processor
  CPU family:  25
  Model:   17
  Thread(s) per core:  2
  Core(s) per socket:  96
  Socket(s):   1
  Stepping:1
  Frequency boost: enabled

  dmesg log show CPU fail info as below,

  [0.360560] smp: Bringing up secondary CPUs ...
  [0.360708] x86: Booting SMP configuration:
  [0.360711]  node  #0, CPUs:  #1   #2   #3   #4   #5   #6   #7 
  #8   #9  #10  #11  #12  #13  #14  #15  #16  #17  #18  #19  #20  #21  #22  #23 
 #24  #25  #26  #27  #28  #29  #30  #31  #32  #33  #34  #35  #36  #37  #38  #39 
 #40  #41  #42  #43  #44  #45  #46  #47  #48  #49  #50  #51  #52  #53  #54  #55 
 #56  #57  #58  #59  #60  #61  #62  #63  #64  #65  #66  #67  #68  #69  #70  #71 
 #72  #73  #74  #75  #76  #77  #78  #79  #80  #81  #82  #83  #84  #85  #86  #87 
 #88  #89  #90  #91  #92  #93  #94  #95  #96
  [   10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96
  [   10.631842]   #97

  BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with
  Ubuntu 22.04.3-kernel 6.2.0 and 6.5.7.

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


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

[Kernel-packages] [Bug 2042888] [NEW] It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic.

[CocoZT_Wang]

Public bug reported:

OS: Ubuntu 22.04.3 LTS
Release: 22.04
Kernel: 6.2.0-060200-generic
CPU: 1x EPYC 9654
DIMM: 2x Samsung DDR5 16G

1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also 
tried on kernel 6.5.7-060507)
2.Reboot system and enable SMT-Control from BIOS.
3.Boot to system to read lscpu.txt and dmesg.txt,
lscpu log show Off-line CPU(s) info as below:

CPU(s):  192
On-line CPU(s) list: 0-95,97-191
Off-line CPU(s) list:96
Vendor ID:   AuthenticAMD
Model name:  AMD EPYC 9654 96-Core Processor
CPU family:  25
Model:   17
Thread(s) per core:  2
Core(s) per socket:  96
Socket(s):   1
Stepping:1
Frequency boost: enabled

dmesg log show CPU fail info as below,

[0.360560] smp: Bringing up secondary CPUs ...
[0.360708] x86: Booting SMP configuration:
[0.360711]  node  #0, CPUs:  #1   #2   #3   #4   #5   #6   #7   
#8   #9  #10  #11  #12  #13  #14  #15  #16  #17  #18  #19  #20  #21  #22  #23  
#24  #25  #26  #27  #28  #29  #30  #31  #32  #33  #34  #35  #36  #37  #38  #39  
#40  #41  #42  #43  #44  #45  #46  #47  #48  #49  #50  #51  #52  #53  #54  #55  
#56  #57  #58  #59  #60  #61  #62  #63  #64  #65  #66  #67  #68  #69  #70  #71  
#72  #73  #74  #75  #76  #77  #78  #79  #80  #81  #82  #83  #84  #85  #86  #87  
#88  #89  #90  #91  #92  #93  #94  #95  #96
[   10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96
[   10.631842]   #97

BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with Ubuntu
22.04.3-kernel 6.2.0 and 6.5.7.

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

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

Title:
  It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system
  dmesg log with kernel version 6.2.0-060200-generic.

Status in linux-hwe package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 22.04.3 LTS
  Release: 22.04
  Kernel: 6.2.0-060200-generic
  CPU: 1x EPYC 9654
  DIMM: 2x Samsung DDR5 16G

  1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also 
tried on kernel 6.5.7-060507)
  2.Reboot system and enable SMT-Control from BIOS.
  3.Boot to system to read lscpu.txt and dmesg.txt,
  lscpu log show Off-line CPU(s) info as below:

  CPU(s):  192
  On-line CPU(s) list: 0-95,97-191
  Off-line CPU(s) list:96
  Vendor ID:   AuthenticAMD
  Model name:  AMD EPYC 9654 96-Core Processor
  CPU family:  25
  Model:   17
  Thread(s) per core:  2
  Core(s) per socket:  96
  Socket(s):   1
  Stepping:1
  Frequency boost: enabled

  dmesg log show CPU fail info as below,

  [0.360560] smp: Bringing up secondary CPUs ...
  [0.360708] x86: Booting SMP configuration:
  [0.360711]  node  #0, CPUs:  #1   #2   #3   #4   #5   #6   #7 
  #8   #9  #10  #11  #12  #13  #14  #15  #16  #17  #18  #19  #20  #21  #22  #23 
 #24  #25  #26  #27  #28  #29  #30  #31  #32  #33  #34  #35  #36  #37  #38  #39 
 #40  #41  #42  #43  #44  #45  #46  #47  #48  #49  #50  #51  #52  #53  #54  #55 
 #56  #57  #58  #59  #60  #61  #62  #63  #64  #65  #66  #67  #68  #69  #70  #71 
 #72  #73  #74  #75  #76  #77  #78  #79  #80  #81  #82  #83  #84  #85  #86  #87 
 #88  #89  #90  #91  #92  #93  #94  #95  #96
  [   10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96
  [   10.631842]   #97

  BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with
  Ubuntu 22.04.3-kernel 6.2.0 and 6.5.7.

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


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

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

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2023-11-06 19:32 EDT---
--- Comment from Niklas S. ---
This is almost certainly the same problem as described in this upstream issue:
https://github.com/smartmontools/smartmontools/issues/172
"On Big-Endian systems smartctl -a /dev/nvmeXnY may segfault in 
nvme_read_error_log()"

** Bug watch added: github.com/smartmontools/smartmontools/issues #172
   https://github.com/smartmontools/smartmontools/issues/172

-- 
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 linux package in Ubuntu:
  New

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/+source/linux/+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 2042885] [NEW] [UBUNTU 22.04] Running smartctl on NVME hit segmentation fault

[bugproxy]

Public bug reported:

== 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.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-203947 severity-medium 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-203947 severity-medium
targetmilestone-inin---

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

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

-- 
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 linux package in Ubuntu:
  New

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/+source/linux/+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 2042885] [NEW] [UBUNTU 22.04] Running smartctl on NVME hit segmentation fault

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== 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.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-203947 severity-medium 
targetmilestone-inin---
-- 
[UBUNTU 22.04] Running smartctl on NVME hit segmentation fault
https://bugs.launchpad.net/bugs/2042885
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-13.13 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/2042573

Title:
  arm64 atomic issues cause disk corruption

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

Bug description:
  SRU Justification:

  [Impact]
  The mantic kernel introduced a regression in atomic operations on arm64
  which causes all kinds of problems including file system corruptions,
  since commit "locking/atomic: scripts: restructure fallback
  ifdeffery".

  An example report of people encountering this in UTM with a arm64
  generic kernel: https://github.com/utmapp/UTM/issues/4840

  [Fix]
  Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery"
  from linux-stable v6.5.6

  [Test Plan]

  Boot test on an arm64 vm.

  [Where problems could occur]
  Since this is touching atomic operations, this has a wide impact on the
  kernel.

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


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

[Kernel-packages] [Bug 2042877] [NEW] kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

[Imri Paloja]

Public bug reported:

I tried everything. Manually installed the latest kernel, no luck.


Updated the driver, also no luck.

Here is my lshw output:


id: network
description:Ethernet interface
product:RTL8125 2.5GbE Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id:0
bus info:   pci@:0d:00.0
logical name:   enp13s0
version:05
serial: XXX
size:   1Gbit/s
capacity:   1Gbit/s
width:  64 bits
clock:  33MHz
capabilities:   pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration:  
autonegotiation =   on
broadcast   =   yes
driver  =   r8169
driverversion   = 6.2.0-36-generic
duplex  =   full
firmware=   rtl8125b-2_0.0.2 07/13/20
ip  =   192.168.0.228
latency =   0
link=   yes
multicast   =   yes
port=   twisted pair
speed   =   1Gbit/s
resources:  
irq :   34
ioport  :   f000(size=256)
memory  :   fc70-fc70
memory  :   fc71-fc713fff

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Nov  6 22:37:44 2023
InstallationDate: Installed on 2023-06-01 (158 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  kernel: r8169 :0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop:
  42, delay: 100).

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

Bug description:
  I tried everything. Manually installed the latest kernel, no luck.

  
  Updated the driver, also no luck.

  Here is my lshw output:

  
  id:   network
  description:  Ethernet interface
  product:  RTL8125 2.5GbE Controller
  vendor:   Realtek Semiconductor Co., Ltd.
  physical id:  0
  bus info:   pci@:0d:00.0
  logical name: enp13s0
  version:  05
  serial:   XXX
  size: 1Gbit/s
  capacity: 1Gbit/s
  width:64 bits
  clock:33MHz
  capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
  configuration:
  autonegotiation   =   on
  broadcast =   yes
  driver=   r8169
  driverversion = 6.2.0-36-generic
  duplex=   full
  firmware  =   rtl8125b-2_0.0.2 07/13/20
  ip=   192.168.0.228
  latency   =   0
  link  =   yes
  multicast =   yes
  port  =   twisted pair
  speed =   1Gbit/s
  resources:
  irq   :   34
  ioport:   f000(size=256)
  memory:   fc70-fc70
  memory:   fc71-fc713fff

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Nov  6 22:37:44 2023
  InstallationDate: Installed on 2023-06-01 (158 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2041995] Re: pwr-mlxbf: support graceful reboot instead of soft reset

[Feysel Mohammed]

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

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

Title:
  pwr-mlxbf: support graceful reboot instead of soft reset

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

Bug description:
  SRU Justification:

  [Impact]

  There is a new feature request to replace the soft reset with a graceful 
reboot.
  We will use acpi events triggered by the irq in the pwr-mlxbf file to trigger 
the graceful reboot.

  
  [Fix]

  * Change the handling of GPIO7 (BF2) and GPIO6 (BF3). This gpio will trigger 
a graceful reboot instead of 
a forced reboot (soft reset). This is an acpi event.

  [Test Case]

  * trigger the gpio toggling from the BMC: ipmitool raw 0x32 0xA1 0x02
This should trigger a graceful reboot of the DPU.

  [Regression Potential]

  * make sure it works on BF2 and BF3

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


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

[Kernel-packages] [Bug 2042455] Re: Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init

[Feysel Mohammed]

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

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

Title:
  Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init

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

Bug description:
  Summary:
  Machine hangs when loading OFED 2310 mlx5 driver at BlueField

  How to reproduce:
  # load the OFED driver

  Reason:
  BF got stuck and observed call trace "mlx5_sf_hw_table_init+0xf4/0x2d0 
[mlx5_core]

  dmesg from minicom:
  [  726.569928] INFO: task systemd-udevd:297 blocked for more than 604 seconds.
  [  726.576895]   Tainted: G   OE 5.15.0-1029-bluefield 
#31-Ubuntu
  [  726.584101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.591913] task:systemd-udevd   state:D stack:0 pid:  297 ppid:   280 
flags:0x000d
  [  726.600248] Call trace:
  [  726.602680]  __switch_to+0xf8/0x150
  [  726.606159]  __schedule+0x2b8/0x790
  [  726.609634]  schedule+0x64/0x140
  [  726.612850]  schedule_preempt_disabled+0x18/0x24
  [  726.617453]  __mutex_lock.constprop.0+0x1a0/0x680
  [  726.622141]  __mutex_lock_slowpath+0x40/0x90
  [  726.626396]  mutex_lock+0x64/0x70
  [  726.629695]  devlink_resource_register+0x50/0x1a0
  [  726.634386]  mlx5_sf_hw_table_init+0xf4/0x2d0 [mlx5_core]
  [  726.639882]  mlx5_init_one_devl_locked+0x1c8/0x784 [mlx5_core]
  [  726.645791]  probe_one+0x300/0x5f0 [mlx5_core]
  [  726.650307]  local_pci_probe+0x48/0xb4
  [  726.654043]  pci_device_probe+0x18c/0x200
  [  726.658039]  really_probe+0xd0/0x490
  [  726.661600]  __driver_probe_device+0x148/0x190
  [  726.666029]  driver_probe_device+0x48/0x180
  [  726.670198]  __driver_attach+0x104/0x240
  [  726.674106]  bus_for_each_dev+0x78/0xdc
  [  726.677927]  driver_attach+0x2c/0x40
  [  726.681486]  bus_add_driver+0x154/0x270
  [  726.685307]  driver_register+0x80/0x13c
  [  726.689129]  __pci_register_driver+0x4c/0x60
  [  726.693386]  __init_backport+0xf0/0x1000 [mlx5_core]
  [  726.698425]  do_one_initcall+0x4c/0x250
  [  726.702248]  do_init_module+0x50/0x260
  [  726.705983]  load_module+0x9fc/0xbe0
  [  726.709543]  __do_sys_finit_module+0xa8/0x114
  [  726.713885]  __arm64_sys_finit_module+0x28/0x3c
  [  726.718401]  invoke_syscall+0x78/0x100
  [  726.722137]  el0_svc_common.constprop.0+0x54/0x184
  [  726.726913]  do_el0_svc+0x30/0xac
  [  726.730215]  el0_svc+0x48/0x160
  [  726.733341]  el0t_64_sync_handler+0xa4/0x130
  [  726.737597]  el0t_64_sync+0x1a4/0x1a8
  [  847.401924] INFO: task systemd-udevd:297 blocked for more than 724 seconds.
  [  847.408891]   Tainted: G   OE 5.15.0-1029-bluefield 
#31-Ubuntu

  How to fix:
  This is related to
  https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039869
  and we need to backport/cherry-pick more patches from the series

  Patches are below
  Backport: f655dacb59ac net: devlink: remove unused locked functions
  Backport: 012ec02ae441 netdevsim: convert driver to use unlocked devlink API 
during init/fini
  Cherry-pick: eb0e9fa2c635 net: devlink: add unlocked variants of 
devlink_region_create/destroy() functions
  SKIP: 72a4c8c94efa mlxsw: convert driver to use unlocked devlink API during 
init/fini
  Backport: 70a2ff89369d net: devlink: add unlocked variants of 
devlink_dpipe*() functions
  Cherry-pick: 755cfa69c4ec net: devlink: add unlocked variants of 
devlink_sb*() functions
  Cherry-pick: c223d6a4bf6d net: devlink: add unlocked variants of 
devlink_resource*() functions
  Cherry-pick: 852e85a704c2 net: devlink: add unlocked variants of 
devling_trap*() functions
  Cherry-pick: e26fde2f5bef net: devlink: avoid false DEADLOCK warning reported 
by lock

  Thanks!

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


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

[Kernel-packages] [Bug 2039325] Re: mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

[Meriton Tuli]

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

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

Title:
  mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

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

Bug description:
  sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110

  SRU Justification:

  [Impact]
  This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: 
__mmc_blk_ioctl_cmd: data error -110" error under stress test

  [Fix]
  The fix added a quirk for the BF3 sdhci driver to avoid such data error.

  [Test Case]
  1. Same functionality and testing as on BlueField-1/2.
  2. Install OS on NVME, and run the FIO test on EMMC.
  fio --name=mmcblk0_randrw_stress_round_1 \
--ioengine=libaio --direct=1  --time_based=1 \
--end_fsync=1 --ramp_time=5 --norandommap=1 \
--randrepeat=0 --group_reporting=1 --numjobs=8 \
--iodepth=128 --rw=randrw --overwrite=1 \
--runtime=3600 --bs=4K --filename=/dev/mmcblk0 &

  
  [Regression Potential]
  Same behavior from user perspective.

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


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

[Kernel-packages] [Bug 2038868] Re: gpio-mlxbf3: support valid mask

[Feysel Mohammed]

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

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

Title:
  gpio-mlxbf3: support valid mask

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

Bug description:
  SRU Justification:

  [Impact]

  After syncing up the gpio-mlxbf3.c driver with the upstreamed version, we 
dropped the use of the valid_mask variable because kernels greater or equal to 
6.2.0 dont need it.
  This is no longer needed in kernel versions >= 6.2.0 because valid_mask is 
populated by core gpio code.
  5.15 kernel doesnt support that feature so we still need to explicitly define 
valid_mask like we did before. 
  This doesnt impact the functionality of the GPIO driver but it is a security 
breach as it doesnt restrict the access to only gpios defined in the acpi table 
by valid_mask.

  [Fix]

  * define valid_mask and init_valid_mask

  [Test Case]

  * Make sure that the user (libgpiod) cannot access any other gpio
  besides 0->4 (gpiochip0) and 22-23 in gpiochip1.

  [Regression Potential]

  no known regression.

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


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

[Kernel-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)

[Noctis Bennington]

More info: In "Settings - Monitors" it shows like it's not connected to
the second monitor when this happens. It is like it disconnects
automatically from the system for some reason.

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

Title:
  [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
  screen (no screen detected)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I go into "fullscreen" watching a video while browsing in Firefox
  or when playing a game through Steam (fullscreen mode), the screen
  goes black.

  The workaround I have discovered to get back is to enter the gdm from
  "Ctrl + alt + F1" and then return to the session you were in
  (normally, "Ctrl + alt + F2).

  Edit: It happens when I connect a second monitor and use it as the
  primary display while the laptop screen is disabled.

  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  noctis 2095 F wireplumber
   /dev/snd/controlC0:  noctis 2095 F wireplumber
   /dev/snd/seq:noctis 2090 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:00:55 2023
  InstallationDate: Installed on 2023-10-13 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 amdgpudrmfb
   1 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2020
  dmi.bios.release: 1.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17EKAMS.101
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17EK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
  dmi.product.family: Al
  dmi.product.name: Alpha 17 A4DEK
  dmi.product.sku: 17EK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off

[ventsy velev]

Experiencing this on Lunar (23.04) , kernel version  6.2.0-36-generic

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

Title:
  Ubuntu 23.04: Suspend & Power off

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

Bug description:
  Since update to version 23.04 I am facing several problems related to
  system suspend and shutdownon a HP Envy 15 notebook (2016). The system
  refuses to wake up from standby mode, especially if it has run for a
  longer time. Screen is black, no response to keyboard or trackpad
  actions, power button led is on. The only way out of here is a long
  press on the power button.

  Another problem with this and I think it's kind of related. If you
  want to shut down the computer after a long runtime, the machine won't
  power off.  In the logs you can see the steps for shutting down the
  OS, but sometimes the machine stays powered on. The power led is on,
  screen is black, no response to keyboard or trackpad actions. System
  has to be powered off by a long press on the power button.

  Ubuntu 6.2.0-27.28-generic 6.2.15

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-27-generic 6.2.0-27.28
  ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
  Uname: Linux 6.2.0-27-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom2051 F wireplumber
   /dev/snd/seq:tom2037 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 19 16:01:07 2023
  InstallationDate: Installed on 2018-07-01 (1875 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision 
HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic 
root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba 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.2.0-27-generic N/A
   linux-backports-modules-6.2.0-27-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago)
  dmi.bios.date: 11/10/2020
  dmi.bios.release: 15.62
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.62
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81D2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 87.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 87.21
  dmi.modalias: 
dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP ENVY Notebook
  dmi.product.sku: Z6J78EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2030673] Re: Linux 6.2.0-26-generic, network crashes intermittently.

[Garry]

6.2.0.36. A week without problems.

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

Title:
  Linux 6.2.0-26-generic, network crashes intermittently.

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

Bug description:
  After updating the kernel to version 6.2, the network drops once a
  day.

  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Linux MyHomeAssistant 6.2.0-26-generic #26~22.04.1-Ubuntu SMP
  PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64
  GNU/Linux

  
  авг 07 12:32:25 MyHomeAssistant kernel: [ cut here ]
  авг 07 12:32:25 MyHomeAssistant kernel: NETDEV WATCHDOG: enp2s0 (r8169): 
transmit queue 0 timed out
  авг 07 12:32:25 MyHomeAssistant kernel: WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230
  авг 07 12:32:25 MyHomeAssistant kernel: Modules linked in: ntfs3 rfcomm tls 
xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype 
nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc 
snd_hda_codec_hdmi cmac algif_hash algif_skcipher af_alg bnep overlay 
snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation binfmt_misc soundwire_cadence snd_sof_intel_hda 
snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda 
snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus 
nls_iso8859_1 snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
snd_hda_intel x86_pkg_temp_thermal mei_pxp mei_hdcp intel_rapl_msr 
snd_intel_dspcfg intel_powerclamp snd_intel_sdw_acpi i915 snd_hda_codec 
kvm_intel snd_usb_audio iwlmvm snd_hda_core snd_usbmidi_lib kvm mc snd_hwdep 
drm_buddy btusb mac80211 snd_pcm irqbypass ttm snd_seq_midi btrtl 
snd_seq_midi_event libarc4 btbcm
  авг 07 12:32:25 MyHomeAssistant kernel:  crct10dif_pclmul snd_rawmidi 
drm_display_helper btintel polyval_generic snd_seq ghash_clmulni_intel cec 
sha512_ssse3 rc_core iwlwifi snd_seq_device aesni_intel btmtk 
processor_thermal_device_pci_legacy snd_timer drm_kms_helper 
processor_thermal_device crypto_simd processor_thermal_rfim snd i2c_algo_bit 
cryptd processor_thermal_mbox syscopyarea joydev input_leds bluetooth 
intel_cstate cdc_acm sysfillrect processor_thermal_rapl cmdlinepart sysimgblt 
cfg80211 spi_nor soundcore ecdh_generic intel_rapl_common 8250_dw mei_me ee1004 
wmi_bmof ecc mtd int340x_thermal_zone intel_soc_dts_iosf mei acpi_pad mac_hid 
acpi_tad sch_fq_codel coretemp msr parport_pc ppdev lp parport ramoops 
pstore_blk drm reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 
hid_generic usbhid uas hid usb_storage spi_pxa2xx_platform dw_dmac dw_dmac_core 
crc32_pclmul spi_intel_pci i2c_i801 xhci_pci ahci r8169 spi_intel i2c_smbus 
intel_lpss_pci intel_lpss realtek libahci idma64 xhci_pci_renesas video
  авг 07 12:32:25 MyHomeAssistant kernel:  wmi pinctrl_jasperlake
  авг 07 12:32:25 MyHomeAssistant kernel: CPU: 3 PID: 0 Comm: swapper/3 Not 
tainted 6.2.0-26-generic #26~22.04.1-Ubuntu
  авг 07 12:32:25 MyHomeAssistant kernel: Hardware name: AZW U59/U59, BIOS 
JTKT001 05/05/2022
  авг 07 12:32:25 MyHomeAssistant kernel: RIP: 0010:dev_watchdog+0x21f/0x230
  авг 07 12:32:25 MyHomeAssistant kernel: Code: 00 e9 31 ff ff ff 4c 89 e7 c6 
05 f5 a9 78 01 01 e8 c6 ff f7 ff 44 89 f1 4c 89 e6 48 c7 c7 08 30 c4 a7 48 89 
c2 e8 31 0b 2c ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 
90 90
  авг 07 12:32:25 MyHomeAssistant kernel: RSP: 0018:99cf001dce70 EFLAGS: 
00010246
  авг 07 12:32:25 MyHomeAssistant kernel: RAX:  RBX: 
8e93816704c8 RCX: 
  авг 07 12:32:25 MyHomeAssistant kernel: RDX:  RSI: 
 RDI: 
  авг 07 12:32:25 MyHomeAssistant kernel: RBP: 99cf001dce98 R08: 
 R09: 
  авг 07 12:32:25 MyHomeAssistant kernel: R10:  R11: 
 R12: 8e938167
  авг 07 12:32:25 MyHomeAssistant kernel: R13: 8e938167041c R14: 
 R15: 
  авг 07 12:32:25 MyHomeAssistant kernel: FS:  () 
GS:8e96f018() knlGS:
  авг 07 12:32:25 MyHomeAssistant kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  авг 07 12:32:25 MyHomeAssistant kernel: CR2: 564d214f12cc CR3: 
0002c601 CR4: 00350ee0
  авг 07 12:32:25 MyHomeAssistant kernel: Call Trace:
  авг 07 12:32:25 MyHomeAssistant kernel:  
  авг 07 12:32:25 MyHomeAssistant kernel:  ? __pfx_dev_watchdog+0x10/0x10
  авг 07 12:32:25 MyHomeAssistant kernel:  call_timer_fn+0x29/0x160
  авг 07 12:32:25 MyHomeAssistant kernel:  ? __pfx_dev_watchdog+0x10/0x10
  авг 07 12:32:25 MyHomeAssistant kernel:  __run_timers.part.0+0x1fb/0x2b0
  авг 07 12:32:25 

[Kernel-packages] [Bug 2030673] Re: Linux 6.2.0-26-generic, network crashes intermittently.

[Brett D]

According to the link that Garry posted to 2031537, this may be fixed in
kernel 6.2.0-36.37 which was released a week ago.

However it's not clear to me if this bug and that one share a root cause
(ie: are duplicates).

Is anyone here brave enough to try the latest and can report back?

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

Title:
  Linux 6.2.0-26-generic, network crashes intermittently.

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

Bug description:
  After updating the kernel to version 6.2, the network drops once a
  day.

  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Linux MyHomeAssistant 6.2.0-26-generic #26~22.04.1-Ubuntu SMP
  PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64
  GNU/Linux

  
  авг 07 12:32:25 MyHomeAssistant kernel: [ cut here ]
  авг 07 12:32:25 MyHomeAssistant kernel: NETDEV WATCHDOG: enp2s0 (r8169): 
transmit queue 0 timed out
  авг 07 12:32:25 MyHomeAssistant kernel: WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230
  авг 07 12:32:25 MyHomeAssistant kernel: Modules linked in: ntfs3 rfcomm tls 
xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype 
nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc 
snd_hda_codec_hdmi cmac algif_hash algif_skcipher af_alg bnep overlay 
snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation binfmt_misc soundwire_cadence snd_sof_intel_hda 
snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda 
snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus 
nls_iso8859_1 snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
snd_hda_intel x86_pkg_temp_thermal mei_pxp mei_hdcp intel_rapl_msr 
snd_intel_dspcfg intel_powerclamp snd_intel_sdw_acpi i915 snd_hda_codec 
kvm_intel snd_usb_audio iwlmvm snd_hda_core snd_usbmidi_lib kvm mc snd_hwdep 
drm_buddy btusb mac80211 snd_pcm irqbypass ttm snd_seq_midi btrtl 
snd_seq_midi_event libarc4 btbcm
  авг 07 12:32:25 MyHomeAssistant kernel:  crct10dif_pclmul snd_rawmidi 
drm_display_helper btintel polyval_generic snd_seq ghash_clmulni_intel cec 
sha512_ssse3 rc_core iwlwifi snd_seq_device aesni_intel btmtk 
processor_thermal_device_pci_legacy snd_timer drm_kms_helper 
processor_thermal_device crypto_simd processor_thermal_rfim snd i2c_algo_bit 
cryptd processor_thermal_mbox syscopyarea joydev input_leds bluetooth 
intel_cstate cdc_acm sysfillrect processor_thermal_rapl cmdlinepart sysimgblt 
cfg80211 spi_nor soundcore ecdh_generic intel_rapl_common 8250_dw mei_me ee1004 
wmi_bmof ecc mtd int340x_thermal_zone intel_soc_dts_iosf mei acpi_pad mac_hid 
acpi_tad sch_fq_codel coretemp msr parport_pc ppdev lp parport ramoops 
pstore_blk drm reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 
hid_generic usbhid uas hid usb_storage spi_pxa2xx_platform dw_dmac dw_dmac_core 
crc32_pclmul spi_intel_pci i2c_i801 xhci_pci ahci r8169 spi_intel i2c_smbus 
intel_lpss_pci intel_lpss realtek libahci idma64 xhci_pci_renesas video
  авг 07 12:32:25 MyHomeAssistant kernel:  wmi pinctrl_jasperlake
  авг 07 12:32:25 MyHomeAssistant kernel: CPU: 3 PID: 0 Comm: swapper/3 Not 
tainted 6.2.0-26-generic #26~22.04.1-Ubuntu
  авг 07 12:32:25 MyHomeAssistant kernel: Hardware name: AZW U59/U59, BIOS 
JTKT001 05/05/2022
  авг 07 12:32:25 MyHomeAssistant kernel: RIP: 0010:dev_watchdog+0x21f/0x230
  авг 07 12:32:25 MyHomeAssistant kernel: Code: 00 e9 31 ff ff ff 4c 89 e7 c6 
05 f5 a9 78 01 01 e8 c6 ff f7 ff 44 89 f1 4c 89 e6 48 c7 c7 08 30 c4 a7 48 89 
c2 e8 31 0b 2c ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 
90 90
  авг 07 12:32:25 MyHomeAssistant kernel: RSP: 0018:99cf001dce70 EFLAGS: 
00010246
  авг 07 12:32:25 MyHomeAssistant kernel: RAX:  RBX: 
8e93816704c8 RCX: 
  авг 07 12:32:25 MyHomeAssistant kernel: RDX:  RSI: 
 RDI: 
  авг 07 12:32:25 MyHomeAssistant kernel: RBP: 99cf001dce98 R08: 
 R09: 
  авг 07 12:32:25 MyHomeAssistant kernel: R10:  R11: 
 R12: 8e938167
  авг 07 12:32:25 MyHomeAssistant kernel: R13: 8e938167041c R14: 
 R15: 
  авг 07 12:32:25 MyHomeAssistant kernel: FS:  () 
GS:8e96f018() knlGS:
  авг 07 12:32:25 MyHomeAssistant kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  авг 07 12:32:25 MyHomeAssistant kernel: CR2: 564d214f12cc CR3: 
0002c601 CR4: 00350ee0
  авг 07 12:32:25 MyHomeAssistant kernel: Call Trace:
  авг 07 12:32:25 MyHomeAssistant kernel:  
  авг 07 12:32:25 MyHomeAssistant kernel:  ? 

[Kernel-packages] [Bug 2042868] [NEW] Kernel 6.2.0-36 broke RTW88 solution

[Roel van der Plank]

Public bug reported:

On my Linux Mint (derived from Ubuntu) system, I relied on the excellent rtw88 
solution from lwfinger (https://github.com/lwfinger/rtw88) to 'fix' my Realtek 
Wifi Driver whenever a new kernel comes out.
As I understand it, the github repository normally is 'ahead' of any kernels, 
so if and when I do a 'git pull' of his repository before installing the new 
rtw88, it should work.

And this has worked for quite some time, until the 6.2.0-36 kernel came along.
As lwfinger himself (?) states, "Ubuntu often modifies kernel APIs, which can 
cause build issues. You'll need to manually adjust the source code or look for 
solutions specific to your distribution. We cannot support these types of 
issues.", so asking him is not an option. Help?

Result from version:
Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
(Well, this the kernel version in which I have Wifi and thus internet, the 
'does not work' kernel is 6.2.0-36, supported till February 2024)

Result from lscpi-vnvn (also when running the version that still has
internet) as an attachment.

Kind regards,

Roel

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

** Attachment added: "output of lscpi-vnvn"
   
https://bugs.launchpad.net/bugs/2042868/+attachment/5716541/+files/lscpi-vnvn.log

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

Title:
  Kernel 6.2.0-36 broke RTW88 solution

Status in linux package in Ubuntu:
  New

Bug description:
  On my Linux Mint (derived from Ubuntu) system, I relied on the excellent 
rtw88 solution from lwfinger (https://github.com/lwfinger/rtw88) to 'fix' my 
Realtek Wifi Driver whenever a new kernel comes out.
  As I understand it, the github repository normally is 'ahead' of any kernels, 
so if and when I do a 'git pull' of his repository before installing the new 
rtw88, it should work.

  And this has worked for quite some time, until the 6.2.0-36 kernel came along.
  As lwfinger himself (?) states, "Ubuntu often modifies kernel APIs, which can 
cause build issues. You'll need to manually adjust the source code or look for 
solutions specific to your distribution. We cannot support these types of 
issues.", so asking him is not an option. Help?

  Result from version:
  Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  (Well, this the kernel version in which I have Wifi and thus internet, the 
'does not work' kernel is 6.2.0-36, supported till February 2024)

  Result from lscpi-vnvn (also when running the version that still has
  internet) as an attachment.

  Kind regards,

  Roel

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


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

Changing the resolution on the external screen works fine. The problem
is with the build-in display.

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

Title:
  Changing display resolution leads into black screen

Status in linux package in Ubuntu:
  New

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/ubuntu/+source/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] [NEW] Changing display resolution leads into black screen

[Aleix]

Public bug reported:

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.

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


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

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

Title:
  Changing display resolution leads into black screen

Status in linux package in Ubuntu:
  New

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 

[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization

[Ubuntu Kernel Bot]

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


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

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

Title:
  Kernel oops on 32-0bit kernels due to x86_cache_alignment
  initialization

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Triaged
Status in linux-gcp source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from

git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar

  [Fix]

  * Clean cherry pick from linux-next, commit 3e3255265291

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression, isolated fix slightly modifying when value becomes
available.

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


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

[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances

[Ubuntu Kernel Bot]

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


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

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

Title:
  No graphic desktop environment on Google GCP instances

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  Fix Committed
Status in linux-gcp source package in Lunar:
  Fix Committed
Status in linux-gcp source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  * Google reports not being able to display graphic desktop
  environment.

  [Fix]

  * CONFIG_SYSFB_SIMPLEFB was initially enabled in
  https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently
  disabled for amd64 in https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not
  reflected in the GCP kernel config.

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression. Simple config change that was not taken
  from generic.

  [Other Info]

  * SF #00366439

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


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

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Ubuntu Kernel Bot]

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


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

-- 
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 1970957] Re: suspend problem

[cement_head]

Happens rarely on 6.x kernel series.

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  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.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

[Adesayo Adesokan]

apport-bug

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  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.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2042858] [NEW] No newer mainline kernel builds

[Laurent Bonnaud]

Public bug reported:

Hi,

no mainline kernel builds have been published since a while, and
available builds are a few versions old.

Can you do something about this problem ?

Thanks!

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

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

Title:
  No newer mainline kernel builds

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  no mainline kernel builds have been published since a while, and
  available builds are a few versions old.

  Can you do something about this problem ?

  Thanks!

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


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

[Kernel-packages] [Bug 2042533] Re: My system restarts when i shut it down

[Paul White]

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

** Tags added: lunar

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

Title:
  My system restarts when i shut it down

Status in linux package in Ubuntu:
  New

Bug description:
  Hey i have just updated my system. its an HP laptop. and after the update my 
system info is below
  whenever i shutdown my system it boot up again i have tried using shutdown -h 
-now also systemctl poweroff both did the same system just boot up again.Now 
only solution i have is to force power off by holding the power key please fix 
this. i dont have laptop-mode-tool sinstalled

  i have asked the question on ask ubuntu here
  https://askubuntu.com/questions/1491202/my-system-restarts-after-the-
  shutdown-i-cant-shutdown

  System info
  OS: Ubuntu 23.04 x86_64 
  Host: HP Pavilion Laptop 15-eh2xxx 
  Kernel: 6.2.0-36-generic 
  Uptime: 5 mins 
  Packages: 2937 (dpkg), 1 (pkg), 7 (f 
  Shell: bash 5.2.15 
  Resolution: 1920x1080 
  DE: GNOME 44.3 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru-blue-dark [GTK2/3] 
  Icons: Yaru-blue [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: AMD Ryzen 5 5625U with Radeon G 
  GPU: AMD ATI 03:00.0 Barcelo 
  Memory: 2407MiB / 7268MiB

  i have started to get these errors when system boots up
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014
  Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config 
param 0014

  i have uploaded my complete journalctl log in link below
  https://www.swisstransfer.com/d/2865e500-5d04-47a4-8cb7-1c6fe476df7d

  lspci-vnvn output
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Hewlett-Packard Company Renoir/Cezanne Root Complex 
[103c:8a0e]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable- Count=1/4 Maskable- 64bit+
Address:   Data: 
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #5, Speed 8GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 75W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState+
RootCap: CRSVisible+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible+
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- 
LTR+
   

[Kernel-packages] [Bug 2042533] [NEW] My system restarts when i shut it down

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hey i have just updated my system. its an HP laptop. and after the update my 
system info is below
whenever i shutdown my system it boot up again i have tried using shutdown -h 
-now also systemctl poweroff both did the same system just boot up again.Now 
only solution i have is to force power off by holding the power key please fix 
this. i dont have laptop-mode-tool sinstalled

i have asked the question on ask ubuntu here
https://askubuntu.com/questions/1491202/my-system-restarts-after-the-
shutdown-i-cant-shutdown

System info
OS: Ubuntu 23.04 x86_64 
Host: HP Pavilion Laptop 15-eh2xxx 
Kernel: 6.2.0-36-generic 
Uptime: 5 mins 
Packages: 2937 (dpkg), 1 (pkg), 7 (f 
Shell: bash 5.2.15 
Resolution: 1920x1080 
DE: GNOME 44.3 
WM: Mutter 
WM Theme: Adwaita 
Theme: Yaru-blue-dark [GTK2/3] 
Icons: Yaru-blue [GTK2/3] 
Terminal: gnome-terminal 
CPU: AMD Ryzen 5 5625U with Radeon G 
GPU: AMD ATI 03:00.0 Barcelo 
Memory: 2407MiB / 7268MiB

i have started to get these errors when system boots up
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014
Nov 02 10:31:16 hp-pavilion kernel: amd_gpio AMDI0030:00: Invalid config param 
0014

i have uploaded my complete journalctl log in link below
https://www.swisstransfer.com/d/2865e500-5d04-47a4-8cb7-1c6fe476df7d

lspci-vnvn output
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Hewlett-Packard Company Renoir/Cezanne Root Complex 
[103c:8a0e]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable- Count=1/4 Maskable- 64bit+
Address:   Data: 
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #5, Speed 8GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 75W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState+
RootCap: CRSVisible+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible+
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- 
LTR+
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ 
EETLPPrefix+, MaxEETLPPrefixes 1
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS- LN System CLS Not Supported, TPHComp+ ExtTPHComp- 
ARIFwd+
 AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS-
 

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

[Juerg Haefliger]

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  New
Status in linux-firmware source package in Mantic:
  New

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 2042853] [NEW] [UBUNTU 23.04] Kernel config option missing for s390 PCI passthrough

[bugproxy]

Public bug reported:

=== 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?

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-203971 severity-medium 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-203971 severity-medium
targetmilestone-inin---

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

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

-- 
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 linux package in Ubuntu:
  New

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/+source/linux/+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 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)
   Status: Incomplete => New

** Description changed:

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

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

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.
  

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

=== 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?

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-203971 severity-medium 
targetmilestone-inin---
-- 
[UBUNTU 23.04] Kernel config option missing for s390 PCI passthrough
https://bugs.launchpad.net/bugs/2042853
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716489/+files/version.log

** Summary changed:

- kernel crash after wakeup: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
+ kernel crash after suspend: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

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

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] [NEW] kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

Public bug reported:

Laptop may or may not wake up after resume. 2 out of 10 times it will
display an error message and become unresponsive:

nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

Attaching dmesg log file for analysis.


===

At a minimum every hibernate/resume report should contain responses to
each item in this section before being considered Triaged.

1. Is this really a failure?
Yes, as machine hangs and becomes unresponsive.

2. Is it reproducible? If not, how often would it be reproducible?
I'd say it happens 20% of the time.

3. Did it work before on a prior kernel in the same release, or prior release?
Not really sure. I started using the suspend functionality quite recently.

4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
It is the same symptoms each time.

5. Do you end up with a flashing Caps Lock light?
No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

6. Please advise on how the computer hibernated, and resumed specifically.
I suspended it by clicking on the word 'Suspend' in the Gui and then closed the 
lid.
When I opened the lid the computer showed the error.

 
7. Did the machine break while going into hibernation or waking up?
According to the log it broke when suspending.

8. Did you see any error messages leading up to the failure?
Nope.

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

** Attachment added: "output of `sudo journalctl  -k -b -1  --no-tail`"
   https://bugs.launchpad.net/bugs/2042851/+attachment/5716485/+files/dmesg.log

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

** Attachment added: "cmdline"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716487/+files/cmdline

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

** Attachment added: "resume"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716486/+files/resume

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

[gste]

Hi, same error here on multiple VMs with different kernels:

# uname -r
5.15.0-82-generic
5.15.0-60-generic

# lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy


# Tomcat ver
9.0.58


I found it in tomcat9's catalina.out logs:

[crit] java.io.IOException: Duplicate accept detected. This is a known
OS bug. Please consider reporting that you are affected:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

[Philip Cox]

Public bug reported:

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


Starting in 6.5.0-6.6, the BMC output on machines with Aspeed 2600 rev
52 GPUs stopped working.  The machines boot find if "nomodeset" is set,
but without "nomodeset", the machine does not boot to the prompt.

This was introduced by upstream commit:
f81bb0ac7872893241319ea82504956676ef02fd

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?id=f81bb0ac7872893241319ea82504956676ef02fd


Until this has been fixed upstream, we need to revert this change.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: In Progress

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: In Progress

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

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

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

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

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

  Starting in 6.5.0-6.6, the BMC output on machines with Aspeed 2600 rev
  52 GPUs stopped working.  The machines boot find if "nomodeset" is
  set, but without "nomodeset", the machine does not boot to the prompt.

  This was introduced by upstream commit:
  f81bb0ac7872893241319ea82504956676ef02fd

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?id=f81bb0ac7872893241319ea82504956676ef02fd

  
  Until this has been fixed upstream, we need to revert this change.

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 2042549] Re: Xorg crash

[Daniel van Vugt]

Indeed it looks like Xwayland died due to problems in the nouveau kernel
driver. Please consider using an official Nvidia driver instead, via the
Additional Drivers app.

** Tags added: nouveau

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)

** Summary changed:

- Xorg crash
+ [nouveau] Xwayland crash

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

Title:
  [nouveau] Xwayland crash

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

Bug description:
  Have a constant random crashes of Xwayland on almost idle PC. Never had any 
GUI crash issues with 20.04 on the exactly same hardware (same pc).
  As a result all applications are killed and work is not saved...

  [146226.831803] nouveau :01:00.0: gr: TRAP ch 2 [00ffe45000 
Xwayland[3977]]
  [146226.831818] nouveau :01:00.0: gr: GPC0/TPC0/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831825] nouveau :01:00.0: gr: GPC0/TPC0/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b020020 []
  [146226.831833] nouveau :01:00.0: gr: GPC0/TPC1/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831838] nouveau :01:00.0: gr: GPC0/TPC1/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
  [146226.831844] nouveau :01:00.0: gr: GPC0/TPC2/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
  [146226.831849] nouveau :01:00.0: gr: GPC0/TPC2/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b030020 []
  [146226.831857] nouveau :01:00.0: gr: GPC1/TPC0/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
  [146226.831862] nouveau :01:00.0: gr: GPC1/TPC0/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b030020 []
  [146226.831870] nouveau :01:00.0: gr: GPC1/TPC1/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831875] nouveau :01:00.0: gr: GPC1/TPC1/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831880] nouveau :01:00.0: gr: GPC1/TPC2/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
  [146226.831885] nouveau :01:00.0: gr: GPC1/TPC2/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
  [146226.831894] nouveau :01:00.0: gr: GPC2/TPC0/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831899] nouveau :01:00.0: gr: GPC2/TPC0/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b010020 []
  [146226.831906] nouveau :01:00.0: gr: GPC2/TPC1/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
  [146226.831912] nouveau :01:00.0: gr: GPC2/TPC1/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831917] nouveau :01:00.0: gr: GPC2/TPC2/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
  [146226.831922] nouveau :01:00.0: gr: GPC2/TPC2/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
  [146226.831929] nouveau :01:00.0: gr: GPC2/TPC3/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
  [146226.831935] nouveau :01:00.0: gr: GPC2/TPC3/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
  [146226.831967] nouveau :01:00.0: fifo: fault 00 [VIRT_READ] at 
0be02000 engine 40 [gr] client 01 [GPC0/T1_1] reason 00 [PDE] on 
channel 2 [00ffe45000 Xwayland[3977]]
  [146226.831971] nouveau :01:00.0: fifo:00:0002:[Xwayland[3977]] rc 
scheduled
  [146226.831972] nouveau :01:00.0: fifo:00: rc scheduled
  [146226.831981] nouveau :01:00.0: fifo:00:0002:0002:[Xwayland[3977]] 
errored - disabling channel
  [146226.831985] nouveau :01:00.0: Xwayland[3977]: channel 2 killed!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  2 12:22:56 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1650 SUPER] [1043:874b]
  InstallationDate: Installed on 2023-01-15 (290 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=81faac01-c5d9-4543-8547-d6a0cbee36fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 2042549] [NEW] Xorg crash

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Have a constant random crashes of Xwayland on almost idle PC. Never had any GUI 
crash issues with 20.04 on the exactly same hardware (same pc).
As a result all applications are killed and work is not saved...

[146226.831803] nouveau :01:00.0: gr: TRAP ch 2 [00ffe45000 Xwayland[3977]]
[146226.831818] nouveau :01:00.0: gr: GPC0/TPC0/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831825] nouveau :01:00.0: gr: GPC0/TPC0/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b020020 []
[146226.831833] nouveau :01:00.0: gr: GPC0/TPC1/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831838] nouveau :01:00.0: gr: GPC0/TPC1/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
[146226.831844] nouveau :01:00.0: gr: GPC0/TPC2/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
[146226.831849] nouveau :01:00.0: gr: GPC0/TPC2/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b030020 []
[146226.831857] nouveau :01:00.0: gr: GPC1/TPC0/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
[146226.831862] nouveau :01:00.0: gr: GPC1/TPC0/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b030020 []
[146226.831870] nouveau :01:00.0: gr: GPC1/TPC1/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831875] nouveau :01:00.0: gr: GPC1/TPC1/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831880] nouveau :01:00.0: gr: GPC1/TPC2/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
[146226.831885] nouveau :01:00.0: gr: GPC1/TPC2/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
[146226.831894] nouveau :01:00.0: gr: GPC2/TPC0/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831899] nouveau :01:00.0: gr: GPC2/TPC0/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b010020 []
[146226.831906] nouveau :01:00.0: gr: GPC2/TPC1/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
[146226.831912] nouveau :01:00.0: gr: GPC2/TPC1/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831917] nouveau :01:00.0: gr: GPC2/TPC2/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b050020 []
[146226.831922] nouveau :01:00.0: gr: GPC2/TPC2/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
[146226.831929] nouveau :01:00.0: gr: GPC2/TPC3/SM0 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b040020 []
[146226.831935] nouveau :01:00.0: gr: GPC2/TPC3/SM1 trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp b060020 []
[146226.831967] nouveau :01:00.0: fifo: fault 00 [VIRT_READ] at 
0be02000 engine 40 [gr] client 01 [GPC0/T1_1] reason 00 [PDE] on 
channel 2 [00ffe45000 Xwayland[3977]]
[146226.831971] nouveau :01:00.0: fifo:00:0002:[Xwayland[3977]] rc 
scheduled
[146226.831972] nouveau :01:00.0: fifo:00: rc scheduled
[146226.831981] nouveau :01:00.0: fifo:00:0002:0002:[Xwayland[3977]] 
errored - disabling channel
[146226.831985] nouveau :01:00.0: Xwayland[3977]: channel 2 killed!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  2 12:22:56 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1650 SUPER] [1043:874b]
InstallationDate: Installed on 2023-01-15 (290 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=81faac01-c5d9-4543-8547-d6a0cbee36fd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2401
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2401:bd07/12/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by 

[Kernel-packages] [Bug 2042772] Re: Display corrupted/freeze

[Daniel van Vugt]

** Tags added: amdgpu

** Summary changed:

- Display corrupted/freeze
+ [amdgpu] Display corrupted/freeze

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

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

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

Title:
  [amdgpu] Display corrupted/freeze

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  After latest updates login display is fine but after entering password
  display changes to black with random full width 1 pixel high white
  lines that move randomly vertically.  Must power off to recover.  Boot
  in recovery mode works OK.

  Send email if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 07:09:04 2023
  DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2018-08-11 (1912 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
  dmi.bios.date: 10/18/2016
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

Re: [Kernel-packages] [Bug 2042760] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-commo

[mrdorl...@gmail.com]

Thank you for your response, will try to install the generic package

Thank you
Dor

On Mon, Nov 6, 2023, 12:56 Juerg Haefliger <2042...@bugs.launchpad.net>
wrote:

> Remove linux-laptop-tools-common, you don't need/want that. Then
> reinstall linux-tools-6.5.0-10-generic.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2042760
>
> Title:
>   package linux-tools-common (not installed) failed to install/upgrade:
>   trying to overwrite '/usr/bin/cpupower', which is also in package
>   linux-laptop-tools-common 6.5.0-1005.8
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   i have tryied to install linux-tools-6.5.0-10-generic
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 23.10
>   Package: linux-tools-common (not installed)
>   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
>   AptOrdering:
>linux-tools-common:amd64: Install
>linux-tools-6.5.0-10:amd64: Install
>linux-tools-6.5.0-10-generic:amd64: Install
>NULL: ConfigurePending
>   Architecture: amd64
>   CRDA: N/A
>   CasperMD5CheckResult: pass
>   Date: Sun Nov  5 10:30:36 2023
>   DpkgTerminalLog:
>Preparing to unpack .../linux-tools-common_6.5.0-10.10_all.deb ...
>Unpacking linux-tools-common (6.5.0-10.10) ...
> [1mdpkg: [0m error processing archive
> /var/cache/apt/archives/linux-tools-common_6.5.0-10.10_all.deb (--unpack):
> trying to overwrite '/usr/bin/cpupower', which is also in package
> linux-laptop-tools-common 6.5.0-1005.8
>   ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in
> package linux-laptop-tools-common 6.5.0-1005.8
>   InstallationDate: Installed on 2023-10-16 (20 days ago)
>   InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
> (20231010)
>   MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
> root=UUID=8c8aff16-b7fe-47fb-9ee7-ee6bc9a3ec1f ro quiet splash vt.handoff=7
>   Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal,
> 3.11.4-5
>   PythonDetails: N/A
>   RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
>   SourcePackage: linux
>   Title: package linux-tools-common (not installed) failed to
> install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in
> package linux-laptop-tools-common 6.5.0-1005.8
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/12/2020
>   dmi.bios.release: 1.49
>   dmi.bios.vendor: HP
>   dmi.bios.version: N91 Ver. 01.49
>   dmi.board.name: 8170
>   dmi.board.vendor: HP
>   dmi.board.version: KBC Version 29.73
>   dmi.chassis.asset.tag: 5CG64830S4
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.ec.firmware.release: 41.115
>   dmi.modalias:
> dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:br1.49:efr41.115:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:skuP2C90AV:
>   dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
>   dmi.product.name: HP EliteBook Folio G1
>   dmi.product.sku: P2C90AV
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042760/+subscriptions
>
>

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/cpupower', which is also in package
  linux-laptop-tools-common 6.5.0-1005.8

Status in linux package in Ubuntu:
  New

Bug description:
  i have tryied to install linux-tools-6.5.0-10-generic

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-tools-common (not installed)
  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
  AptOrdering:
   linux-tools-common:amd64: Install
   linux-tools-6.5.0-10:amd64: Install
   linux-tools-6.5.0-10-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Nov  5 10:30:36 2023
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_6.5.0-10.10_all.deb ...
   Unpacking linux-tools-common (6.5.0-10.10) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_6.5.0-10.10_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package 
linux-laptop-tools-common 6.5.0-1005.8
  ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in 
package linux-laptop-tools-common 6.5.0-1005.8
  InstallationDate: Installed on 2023-10-16 (20 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: 

[Kernel-packages] [Bug 2042772] [NEW] [amdgpu] Display corrupted/freeze

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After latest updates login display is fine but after entering password
display changes to black with random full width 1 pixel high white lines
that move randomly vertically.  Must power off to recover.  Boot in
recovery mode works OK.

Send email if you need more information.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 07:09:04 2023
DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
   Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
   Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
InstallationDate: Installed on 2018-08-11 (1912 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Inspiron 5565
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
dmi.bios.date: 10/18/2016
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.5
dmi.board.name: 0021CT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.0.5
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5565
dmi.product.sku: 0769
dmi.product.version: 1.0.5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 amdgpu apport-bug freeze jammy ubuntu
-- 
[amdgpu] Display corrupted/freeze
https://bugs.launchpad.net/bugs/2042772
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2041496] Re: btmgmt --index broken in Mantic

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

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

Title:
  btmgmt --index broken in Mantic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

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


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

[Kernel-packages] [Bug 2042841] [NEW] Snapshots of encrypted zfs 2.1.5 filesystems sometimes broken

[Walter]

Public bug reported:

As reported in https://github.com/openzfs/zfs/issues/15474 -- I have had
occasional broken snapshots with ZFS 2.1.5 on Jammy on encrypted
filesystems.

This is _not_ the same problem as
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190


**Manifestation**

  # ls -l /var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z
  ls: cannot access 
'/var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z/aria_log.0001': 
Input/output error
  ls: cannot access 
'/var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z/aria_log_control': 
  Input/output error
  total 10129
  -? ? ? ?   ?? aria_log.0001
  -? ? ? ?   ?? aria_log_control
  -rw-rw 1 mysql mysql   0 nov  1 02:55 ddl.log
  -rw-rw 1 mysql mysql   16384 okt 17 10:26 ddl_recovery.log
  -rw-rw 1 mysql mysql 10737419544 nov  1 02:55 galera.cache
  -rw-rw 1 mysql mysql   8 okt 17 10:26 galera.pid
  ...

Creating newer snapshots succeeded just fine, but this snapshot was
unreadable: each and every file in in it was not readable (except for
0-sized files).

Trying to 'zfs send' this snapshot failed as well.


**Workaround**

Deleting the snapshot worked. But at some point a new snapshot would be
broken again.


**Fix**

Upgrading to 2.1.13 -- as described in the Github ticket -- fixed the
problem.

Cheers,
Walter Doekes
OSSO B.V.

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

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

Title:
  Snapshots of encrypted zfs 2.1.5 filesystems sometimes broken

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  As reported in https://github.com/openzfs/zfs/issues/15474 -- I have
  had occasional broken snapshots with ZFS 2.1.5 on Jammy on encrypted
  filesystems.

  This is _not_ the same problem as
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190

  
  **Manifestation**

# ls -l /var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z
ls: cannot access 
'/var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z/aria_log.0001': 
Input/output error
ls: cannot access 
'/var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z/aria_log_control': 
Input/output error
total 10129
-? ? ? ?   ?? aria_log.0001
-? ? ? ?   ?? aria_log_control
-rw-rw 1 mysql mysql   0 nov  1 02:55 ddl.log
-rw-rw 1 mysql mysql   16384 okt 17 10:26 ddl_recovery.log
-rw-rw 1 mysql mysql 10737419544 nov  1 02:55 galera.cache
-rw-rw 1 mysql mysql   8 okt 17 10:26 galera.pid
...

  Creating newer snapshots succeeded just fine, but this snapshot was
  unreadable: each and every file in in it was not readable (except for
  0-sized files).

  Trying to 'zfs send' this snapshot failed as well.

  
  **Workaround**

  Deleting the snapshot worked. But at some point a new snapshot would
  be broken again.

  
  **Fix**

  Upgrading to 2.1.13 -- as described in the Github ticket -- fixed the
  problem.

  Cheers,
  Walter Doekes
  OSSO B.V.

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


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

[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

[DooMMasteR]

And another correction 
sudo apt install mutter/mantic-proposed
and 
sudo apt install -t mantic-proposed mutter
do different things :-)

the mutter fix works :-)

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Kernel-packages] [Bug 2042840] [NEW] External monitor is very slow in 4k with Wayland + Nvidia Prime

[Jorge Sivil]

Public bug reported:

When using Wayland (fractional scaling or not, I use 150% but tried with
100%), the external monitor is very slow / laggy.

In my setup, I only use the external monitor.

Laptop has prime-select set to nvidia, and the Intel one is disabled in
Bios.

I found out that in X11 this issue with the external 4k monitor doesn't happen.
This lag issue doesn't haven in the native laptop monitor also, in either 
Wayland or X11.

In order to get to X11, I have to first Log In, then Log Out, then X11
is automatically selected (on first log in, Wayland is used, and you
only have Gnome or Ubuntu options, after log out, you have more
options).

Please let me know what extra information you need.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-535 535.129.03-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  6 09:55:49 2023
InstallationDate: Installed on 2022-07-02 (492 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  External monitor is very slow in 4k with Wayland + Nvidia Prime

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

Bug description:
  When using Wayland (fractional scaling or not, I use 150% but tried
  with 100%), the external monitor is very slow / laggy.

  In my setup, I only use the external monitor.

  Laptop has prime-select set to nvidia, and the Intel one is disabled
  in Bios.

  I found out that in X11 this issue with the external 4k monitor doesn't 
happen.
  This lag issue doesn't haven in the native laptop monitor also, in either 
Wayland or X11.

  In order to get to X11, I have to first Log In, then Log Out, then X11
  is automatically selected (on first log in, Wayland is used, and you
  only have Gnome or Ubuntu options, after log out, you have more
  options).

  Please let me know what extra information you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-535 535.129.03-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 09:55:49 2023
  InstallationDate: Installed on 2022-07-02 (492 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nvidia-graphics-drivers-535
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

[DooMMasteR]

Ok correction: on a colleagues machine the issue occurs when his laptop is 
detached from the dock (external monitors) on my machine it occurs even when 
docked.
the `MUTTER_DEBUG_KMS_THREAD_TYPE=user` fix/workaround works though.

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Kernel-packages] [Bug 2041496] Re: btmgmt --index broken in Mantic

[Daniel van Vugt]

** Tags added: mantic

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

Title:
  btmgmt --index broken in Mantic

Status in bluez package in Ubuntu:
  New

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

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


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

[Kernel-packages] [Bug 2041267] Re: Laptop not recovering after Lid Close

[Daniel van Vugt]

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

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

Title:
  Laptop not recovering after Lid Close

Status in linux package in Ubuntu:
  New

Bug description:
  Closed laptop lid (10:32) and after about an hour opened it back up
  (11:30). System was responsive and I could hear notifications, but the
  screen was completely dark and the laptop keys were not lit up. I was
  holding down my power button on the keyboard but the system was not
  turning off. I eventually managed to reboot by blindly typing on an
  external USB keyboard.

  System Info:
  alex@ubuntu:~$ inxi -F
  System:
Host: ubuntu Kernel: 6.5.0-10-generic arch: x86_64 bits: 64 Desktop: GNOME
  v: 45.0 Distro: Ubuntu 23.10 (Mantic Minotaur)
  Machine:
Type: Laptop System: Razer product: Blade 15 (2022) - RZ09-0421 v: 8.04
  serial: 
Mobo: Razer model: CH580 v: 4 serial:  UEFI: Razer
  v: 2.02 date: 01/10/2023
  Battery:
ID-1: BAT0 charge: 71.5 Wh (96.9%) condition: 73.8/80.2 Wh (92.0%)
  CPU:
Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12800H bits: 64
  type: MST AMCP cache: L2: 11.5 MiB
Speed (MHz): avg: 445 min/max: 400/4700:4800:3700 cores: 1: 584 2: 400
  3: 458 4: 400 5: 582 6: 458 7: 767 8: 400 9: 470 10: 400 11: 400 12: 400
  13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
  Graphics:
Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel
Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia
  v: 535.113.01
Device-3: IMC Networks Integrated RGB Camera driver: uvcvideo type: USB
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 23.2.0 driver: X:
  loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: 
i915
  resolution: 2560x1440~240Hz
API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3 renderer: Mesa Intel Graphics
  (ADL GT2)
  Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio
  driver: sof-audio-pci-intel-tgl
Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel
API: ALSA v: k6.5.0-10-generic status: kernel-api
Server-1: PipeWire v: 0.3.79 status: active
  Network:
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
IF: wlo1 state: up mac: 4c:44:5b:81:97:dc
  Bluetooth:
Device-1: Intel driver: btusb type: USB
Report: hciconfig ID: hci0 state: up address: 4C:44:5B:81:97:E0 bt-v: 5.3
  Drives:
Local Storage: total: 953.87 GiB used: 289.01 GiB (30.3%)
ID-1: /dev/nvme0n1 model: NVMe CA6-8D1024 size: 953.87 GiB
  Partition:
ID-1: / size: 20 GiB used: 7.27 GiB (36.4%) fs: btrfs dev: /dev/nvme0n1p7
ID-2: /boot size: 974.7 MiB used: 166 MiB (17.0%) fs: ext4
  dev: /dev/nvme0n1p20
ID-3: /boot/efi size: 96 MiB used: 73 MiB (76.1%) fs: vfat
  dev: /dev/nvme0n1p2
ID-4: /home size: 600 GiB used: 273.08 GiB (45.5%) fs: btrfs
  dev: /dev/nvme0n1p8
ID-5: /var size: 20 GiB used: 8.49 GiB (42.4%) fs: btrfs
  dev: /dev/nvme0n1p5
  Swap:
Alert: No swap data was found.
  Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A
Fan Speeds (rpm): N/A
  Info:
Processes: 471 Uptime: 13m Memory: total: 16 GiB note: est.
available: 15.3 GiB used: 3.11 GiB (20.4%) Shell: Bash inxi: 3.3.29

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gdm3 45~beta-1ubuntu1
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 11:46:32 2023
  InstallationDate: Installed on 2023-05-30 (149 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to mantic on 2023-10-26 (0 days ago)

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


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

[Kernel-packages] [Bug 2042835] Re: Kernel update from 6.2.0-35 to 6.2.0-36 lead to unusable display on MacBook Air with NVIDIA GeForce 320m

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 2042835

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected.

You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** Tags added: jammy

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

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

Title:
  Kernel update from 6.2.0-35 to 6.2.0-36 lead to unusable display on
  MacBook Air with NVIDIA GeForce 320m

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

Bug description:
  Hi,

  after updating a (lubuntu) system from 6.2.0-35 to 6.2.0-36 kernel,
  the entire screen turn into a unusable flickering color puzzle. not
  sure what exactly the root cause for this is. possible wrong refresh
  rate/resolution detected by the kernel? doing input like switching
  blindely to a virtual console and doing a login blindely following a
  poweroff works fine. input isnt affacted at all as long as you can
  type virtually blind on a color puzzled console. a picture is
  attached. Kernel 6.2.0-35 works fine. Its a elder MacBook Air with a
  core2duo running nvidia geforce 320m graphics card using the nouveau
  driver. attaching a "nomodeset" to the kernel command line makes the
  screen work again on the 6.2.0-36 kernel, but disables all the power
  stuff of the gfx card including brightness control and related things.
  not a permanent solution. as said, picture attached. system is lubuntu
  based on 22.04.3 lts.

  best regards

  K.

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


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

[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

[DooMMasteR]

For me the new mutter does not fix the issue, gnome-shell does still
crash/get killed when I lock my screen.

2 other people at my office have NO ISSUES at all, despite both being on the 
stable release and also having AMDGPU devices (one is the exact same device I 
have).
Thinkpad P14s G2a

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Kernel-packages] [Bug 2041267] [NEW] Laptop not recovering after Lid Close

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Closed laptop lid (10:32) and after about an hour opened it back up
(11:30). System was responsive and I could hear notifications, but the
screen was completely dark and the laptop keys were not lit up. I was
holding down my power button on the keyboard but the system was not
turning off. I eventually managed to reboot by blindly typing on an
external USB keyboard.

System Info:
alex@ubuntu:~$ inxi -F
System:
  Host: ubuntu Kernel: 6.5.0-10-generic arch: x86_64 bits: 64 Desktop: GNOME
v: 45.0 Distro: Ubuntu 23.10 (Mantic Minotaur)
Machine:
  Type: Laptop System: Razer product: Blade 15 (2022) - RZ09-0421 v: 8.04
serial: 
  Mobo: Razer model: CH580 v: 4 serial:  UEFI: Razer
v: 2.02 date: 01/10/2023
Battery:
  ID-1: BAT0 charge: 71.5 Wh (96.9%) condition: 73.8/80.2 Wh (92.0%)
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12800H bits: 64
type: MST AMCP cache: L2: 11.5 MiB
  Speed (MHz): avg: 445 min/max: 400/4700:4800:3700 cores: 1: 584 2: 400
3: 458 4: 400 5: 582 6: 458 7: 767 8: 400 9: 470 10: 400 11: 400 12: 400
13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel
  Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia
v: 535.113.01
  Device-3: IMC Networks Integrated RGB Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 23.2.0 driver: X:
loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: i915
resolution: 2560x1440~240Hz
  API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3 renderer: Mesa Intel Graphics
(ADL GT2)
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio
driver: sof-audio-pci-intel-tgl
  Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.5.0-10-generic status: kernel-api
  Server-1: PipeWire v: 0.3.79 status: active
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
  IF: wlo1 state: up mac: 4c:44:5b:81:97:dc
Bluetooth:
  Device-1: Intel driver: btusb type: USB
  Report: hciconfig ID: hci0 state: up address: 4C:44:5B:81:97:E0 bt-v: 5.3
Drives:
  Local Storage: total: 953.87 GiB used: 289.01 GiB (30.3%)
  ID-1: /dev/nvme0n1 model: NVMe CA6-8D1024 size: 953.87 GiB
Partition:
  ID-1: / size: 20 GiB used: 7.27 GiB (36.4%) fs: btrfs dev: /dev/nvme0n1p7
  ID-2: /boot size: 974.7 MiB used: 166 MiB (17.0%) fs: ext4
dev: /dev/nvme0n1p20
  ID-3: /boot/efi size: 96 MiB used: 73 MiB (76.1%) fs: vfat
dev: /dev/nvme0n1p2
  ID-4: /home size: 600 GiB used: 273.08 GiB (45.5%) fs: btrfs
dev: /dev/nvme0n1p8
  ID-5: /var size: 20 GiB used: 8.49 GiB (42.4%) fs: btrfs
dev: /dev/nvme0n1p5
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 471 Uptime: 13m Memory: total: 16 GiB note: est.
  available: 15.3 GiB used: 3.11 GiB (20.4%) Shell: Bash inxi: 3.3.29

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gdm3 45~beta-1ubuntu1
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: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 11:46:32 2023
InstallationDate: Installed on 2023-05-30 (149 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: Upgraded to mantic on 2023-10-26 (0 days ago)

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


** Tags: amd64 apport-bug mantic
-- 
Laptop not recovering after Lid Close
https://bugs.launchpad.net/bugs/2041267
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2042835] [NEW] Kernel update from 6.2.0-35 to 6.2.0-36 lead to unusable display on MacBook Air with NVIDIA GeForce 320m

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi,

after updating a (lubuntu) system from 6.2.0-35 to 6.2.0-36 kernel, the
entire screen turn into a unusable flickering color puzzle. not sure
what exactly the root cause for this is. possible wrong refresh
rate/resolution detected by the kernel? doing input like switching
blindely to a virtual console and doing a login blindely following a
poweroff works fine. input isnt affacted at all as long as you can type
virtually blind on a color puzzled console. a picture is attached.
Kernel 6.2.0-35 works fine. Its a elder MacBook Air with a core2duo
running nvidia geforce 320m graphics card using the nouveau driver.
attaching a "nomodeset" to the kernel command line makes the screen work
again on the 6.2.0-36 kernel, but disables all the power stuff of the
gfx card including brightness control and related things. not a
permanent solution. as said, picture attached. system is lubuntu based
on 22.04.3 lts.

best regards

K.

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


** Tags: 320m geforce jammy nvidia
-- 
Kernel update from 6.2.0-35 to 6.2.0-36 lead to unusable display on MacBook Air 
with NVIDIA GeForce 320m
https://bugs.launchpad.net/bugs/2042835
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.2 in Ubuntu.

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

[Kernel-packages] [Bug 2042525] Re: mlxbf-pmc: Support 64-bit counter and counting cycles

[Shravan Kumar Ramani]

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

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

Title:
  mlxbf-pmc: Support 64-bit counter and counting cycles

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

Bug description:
  SRU Justification:

  [Impact]
  Currently, there is no method to keep track of the cycle count when an event 
is being monitored. And since cycle count increments quickly, the 32-bit 
counter values could wrap around and hence support for 64-bit counters is also 
needed for the same.

  [Fix]
  Expose 2 additional sysfs entries: count_clock and use_odd_counter. These 
fields are supported in BlueField-3 PMC hardware and each bit in count_clock 
corresponds to each counter, while each bit in use_odd_counter corresponds to 
an even counter.Exposing these fields will allow the user to program any 
counter of choice to monitor the cycle count for the required duration. 
Similarly, use_odd_counter can be set to couple 2 adjacent odd and even 
counters to form a 64-bit counter.

  [Test Case]
  1. Verify that count_clock and use_odd_counter sysfs entries are created for 
each BlueField-3 HW block. These are not supported by BlueField-1 or 
BlueField-2 HW.
  2. Set any bit in count_clock and check if the corresponding counter values 
increment after enabling.
  3. Set any bit in use_odd_counter and check if the cycle count increments on 
2 counters with the odd counter being the lower 32 bits and the even counter 
being the upper 32 bits.

  [Regression Potential]
  Can be considered minimal.

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


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

[Kernel-packages] [Bug 2042527] Re: mlxbf-pmc: add support for clock_measure counters

[Shravan Kumar Ramani]

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

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

Title:
  mlxbf-pmc: add support for clock_measure counters

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 counters under the clock_measure HW block are not supported by 
the driver and is a new requirement for calculating performance metrics.

  [Fix]
  Add support for "clock_measure" block by passing the block info via ACPI. The 
events monitored by these counters is added to the driver and exposed via a new 
sysfs sub-directory for this block.

  [Test Case]
  Read any of the registers listed under the "clock_measure" sub-directory. 
These fields are read-only and hence all writes will be blocked by the driver.

  [Regression Potential]
  Can be considered minimal.

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


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

[Kernel-packages] [Bug 2042713] Re: Pale Green blank screen after login

[Mario Limonciello]

Please add kernel log from both your old kernel and new 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/2042713

Title:
  Pale Green blank screen after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since linux Kernel 5.15.0-86, when I only get a pale green blank screen after 
login Linux Mint 21.2 Victoria / Cinnamon so I got to use 5.15.0-84.
  N.B. I'm using a Graphic AMD processor with unconventional screens 
resolutions (1280x1025 (5/4) & 1360x768 (16:9))

  inxi :
  CPU: dual core AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G (-MT MCP-)
  speed/min/max: 3594/1400/3500 MHz Kernel: 5.15.0-84-generic x86_64 Up: 12h 9m
  Mem: 1946.1/15413.6 MiB (12.6%) Storage: 7.04 TiB (38.5% used) Procs: 256
  Shell: Bash inxi: 3.3.13

  inxi -S :
  System:
Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64
  Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria

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


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

[Kernel-packages] [Bug 2042831] [NEW] Drop support for modules-extra

[Dimitri John Ledkov]

Public bug reported:

Thanks to the zst module compression, the total install size of
modules+modules-extra is now less than modules alone before.

Continuously all interesting pieces of new support for new hardware and
features lands in modules-extra by default, and then we chase those
forever to include them in the modules.

Also most install types either install everything; or are minimized and
use dpkg filtering (and can exclude large things they don't like).

Thus drop support for split modules/modules-extra.

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

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

Title:
  Drop support for modules-extra

Status in linux package in Ubuntu:
  New

Bug description:
  Thanks to the zst module compression, the total install size of
  modules+modules-extra is now less than modules alone before.

  Continuously all interesting pieces of new support for new hardware
  and features lands in modules-extra by default, and then we chase
  those forever to include them in the modules.

  Also most install types either install everything; or are minimized
  and use dpkg filtering (and can exclude large things they don't like).

  Thus drop support for split modules/modules-extra.

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


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

[Kernel-packages] [Bug 2030978] Re: kernel 6.5 changes cause UBSAN errors (patch included)

[Marietto]

I've upgraded ubuntu 23.04 to 23.10 and I've got the bug that you said
that should have been fixed.

On my Ubuntu 23.10 I'm using kernel 6.5.0-10-generic and I've installed
the nvidia driver version 535.129.03. (my nvidia gpu is the RTX 2080 ti
; my cpu is the intel I9)

Not exactly the same bug because the error in the Ubuntu bug report is
for a different kernel module. But the underlying cause is probably the
same.

Ubuntu is probably at fault here. Possibly the code for the nvidia-uvm
module is designed for kernel versions < 6.5, so when Ubuntu upgraded to
Linux kernel 6.5, it broke some modules because of changes to UBSAN in
Linux 6.5 which causes modules such as nvidia-uvm to need patches to be
compatible with Linux 6.5, but either nvidia has not yet provided a
version of nvidia-uvm that is compatible with Linux 6.5 or Ubuntu
neglected to apply an updated version from nvidia that is compatible
with Linux 6.5.

Whois the guilty ? the nvidia or the ubuntu developers ? I didn't see
this error on ubuntu 23.04,maybe because it does not use the kernel 6.5
by default,but 23.10 does it.

I see a lot of those errors when I issue the command "dmesg" and any
audio-video streamings don't flow.

Log :


[   15.029102] UBSAN: array-index-out-of-bounds in 
/var/lib/dkms/nvidia/535.129.03/build/nvidia-uvm/uvm_pmm_gpu.c:829:45

[   15.031655] index 0 is out of range for type 'uvm_gpu_chunk_t *[*]'
[   15.034248] CPU: 9 PID: 2571 Comm: ffdetect Tainted: P   OE  
6.5.0-10-generic #10-Ubuntu
[   15.034249] Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS PRO/Z390 
AORUS PRO-CF, BIOS F12g GA9 06/08/2020
[   15.034250] Call Trace:
[   15.034251]  
[   15.034251]  dump_stack_lvl+0x48/0x70
[   15.034255]  dump_stack+0x10/0x20
[   15.034257]  __ubsan_handle_out_of_bounds+0xc6/0x110
[   15.034259]  merge_gpu_chunk+0x57/0x1d0 [nvidia_uvm]
[   15.034293]  free_chunk_with_merges+0x13d/0x180 [nvidia_uvm]
[   15.034325]  free_chunk+0xa4/0xd0 [nvidia_uvm]
[   15.034355]  uvm_pmm_gpu_free+0xbf/0xf0 [nvidia_uvm]
[   15.034386]  phys_mem_deallocate+0x33/0xd0 [nvidia_uvm]
[   15.034422]  uvm_page_tree_put_ptes_async+0x4d5/0x580 [nvidia_uvm]
[   15.034459]  uvm_page_table_range_vec_deinit+0x3e/0xd0 [nvidia_uvm]
[   15.034494]  uvm_va_range_destroy+0x14d/0x590 [nvidia_uvm]
[   15.034527]  ? os_release_spinlock+0x1a/0x30 [nvidia]
[   15.034792]  ? uvm_kvfree+0x30/0x70 [nvidia_uvm]
[   15.034826]  destroy_va_ranges.part.0+0x61/0x90 [nvidia_uvm]
[   15.034857]  uvm_user_channel_detach+0x9e/0xe0 [nvidia_uvm]
[   15.034886]  uvm_api_unregister_channel+0xee/0x1a0 [nvidia_uvm]
[   15.034915]  uvm_ioctl+0x1a04/0x1cd0 [nvidia_uvm]
[   15.034939]  ? uvm_api_unregister_channel+0x134/0x1a0 [nvidia_uvm]
[   15.034968]  ? _copy_to_user+0x25/0x70
[   15.034970]  ? uvm_ioctl+0x5cc/0x1cd0 [nvidia_uvm]
[   15.034994]  ? _raw_spin_lock_irqsave+0xe/0x20
[   15.034996]  ? thread_context_non_interrupt_add+0x13a/0x2c0 [nvidia_uvm]
[   15.035031]  uvm_unlocked_ioctl_entry.part.0+0x7b/0xf0 [nvidia_uvm]
[   15.035055]  ? uvm_thread_context_remove+0x39/0x50 [nvidia_uvm]
[   15.035091]  uvm_unlocked_ioctl_entry+0x6b/0x90 [nvidia_uvm]
[   15.035115]  __x64_sys_ioctl+0xa0/0xf0
[   15.035116]  do_syscall_64+0x59/0x90
[   15.035118]  ? __rseq_handle_notify_resume+0x37/0x70
[   15.035119]  ? exit_to_user_mode_loop+0xe0/0x130
[   15.035122]  ? exit_to_user_mode_prepare+0x9b/0xb0
[   15.035123]  ? syscall_exit_to_user_mode+0x37/0x60
[   15.035125]  ? do_syscall_64+0x68/0x90
[   15.035126]  ? syscall_exit_to_user_mode+0x37/0x60
[   15.035128]  ? do_syscall_64+0x68/0x90
[   15.035129]  ? syscall_exit_to_user_mode+0x37/0x60
[   15.035130]  ? do_syscall_64+0x68/0x90
[   15.035131]  ? do_syscall_64+0x68/0x90
[   15.035133]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[   15.035134] RIP: 0033:0x7f9b9e7238ef
[   15.035144] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00
00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[   15.035145] RSP: 002b:7fff0ed9b9a0 EFLAGS: 0246 ORIG_RAX: 
0010
[   15.035147] RAX: ffda RBX: 0239f8b8 RCX: 7f9b9e7238ef
[   15.035147] RDX: 7fff0ed9ba10 RSI: 001c RDI: 0004
[   15.035148] RBP: 7fff0ed9ba50 R08: 242a R09: 0007
[   15.035149] R10: 0242a3c0 R11: 0246 R12: 7fff0ed9ba10
[   15.035150] R13: 0004 R14: 02506600 R15: 0237c138
[   15.035151]  
[   15.035152] 

[   15.037818] 

[   15.040413] UBSAN: array-index-out-of-bounds in 
/var/lib/dkms/nvidia/535.129.03/build/nvidia-uvm/uvm_pmm_gpu.c:857:39

[   15.043033] index 0 is out of range for type 'uvm_gpu_chunk_t *[*]'
[   15.045636] CPU: 9 PID: 2571 Comm: ffdetect Tainted: P

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

[hugh chao]

@juergh

Use the latest firmware,
it can be loaded successfully, and my wifi works,
attached the dmesg log, thank you.

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2042716/+attachment/5716383/+files/dmesg.log

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

Bug description:
  [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 2042765] Re: bluetooth connection do not work

[Juerg Haefliger]

I don't understand. Does it work after you turn it on?

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

Title:
  bluetooth connection do not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  bluetooth connection do not work, in settings says that the bluetooth
  adapter is turned off and needs to be turned on

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-88-generic 5.15.0-88.98
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  evgeniy 976 F pulseaudio
   /dev/snd/controlC0:  evgeniy 976 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 17:56:18 2023
  InstallationDate: Installed on 2023-11-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  MachineType: HONOR BMH-WDX9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=aed664c0-471d-41f5-b341-45cba69d878f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-88-generic N/A
   linux-backports-modules-5.15.0-88-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.21
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-11-03 (1 days ago)
  dmi.bios.date: 04/13/2023
  dmi.bios.release: 1.13
  dmi.bios.vendor: HONOR
  dmi.bios.version: 1.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BMH-WDX9-PCB
  dmi.board.vendor: HONOR
  dmi.board.version: M1100
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HONOR
  dmi.chassis.version: M1100
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnHONOR:bvr1.13:bd04/13/2023:br1.13:efr1.13:svnHONOR:pnBMH-WDX9:pvrM1100:rvnHONOR:rnBMH-WDX9-PCB:rvrM1100:cvnHONOR:ct10:cvrM1100:skuC170:
  dmi.product.family: HONOR MagicBook
  dmi.product.name: BMH-WDX9
  dmi.product.sku: C170
  dmi.product.version: M1100
  dmi.sys.vendor: HONOR

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


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

[Kernel-packages] [Bug 2042760] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-common 6.

[Juerg Haefliger]

Actually, probably better to install linux-tools-generic if you want the
tools installed with new generic kernels.

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/cpupower', which is also in package
  linux-laptop-tools-common 6.5.0-1005.8

Status in linux package in Ubuntu:
  New

Bug description:
  i have tryied to install linux-tools-6.5.0-10-generic

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-tools-common (not installed)
  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
  AptOrdering:
   linux-tools-common:amd64: Install
   linux-tools-6.5.0-10:amd64: Install
   linux-tools-6.5.0-10-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Nov  5 10:30:36 2023
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_6.5.0-10.10_all.deb ...
   Unpacking linux-tools-common (6.5.0-10.10) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_6.5.0-10.10_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package 
linux-laptop-tools-common 6.5.0-1005.8
  ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in 
package linux-laptop-tools-common 6.5.0-1005.8
  InstallationDate: Installed on 2023-10-16 (20 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=8c8aff16-b7fe-47fb-9ee7-ee6bc9a3ec1f ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/cpupower', which is also in package 
linux-laptop-tools-common 6.5.0-1005.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2020
  dmi.bios.release: 1.49
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.49
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.asset.tag: 5CG64830S4
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 41.115
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:br1.49:efr41.115:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:skuP2C90AV:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: P2C90AV
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2042760] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-common 6.

[Juerg Haefliger]

Remove linux-laptop-tools-common, you don't need/want that. Then
reinstall linux-tools-6.5.0-10-generic.

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/cpupower', which is also in package
  linux-laptop-tools-common 6.5.0-1005.8

Status in linux package in Ubuntu:
  New

Bug description:
  i have tryied to install linux-tools-6.5.0-10-generic

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-tools-common (not installed)
  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
  AptOrdering:
   linux-tools-common:amd64: Install
   linux-tools-6.5.0-10:amd64: Install
   linux-tools-6.5.0-10-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Nov  5 10:30:36 2023
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_6.5.0-10.10_all.deb ...
   Unpacking linux-tools-common (6.5.0-10.10) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_6.5.0-10.10_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package 
linux-laptop-tools-common 6.5.0-1005.8
  ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in 
package linux-laptop-tools-common 6.5.0-1005.8
  InstallationDate: Installed on 2023-10-16 (20 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=8c8aff16-b7fe-47fb-9ee7-ee6bc9a3ec1f ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/cpupower', which is also in package 
linux-laptop-tools-common 6.5.0-1005.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2020
  dmi.bios.release: 1.49
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.49
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.asset.tag: 5CG64830S4
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 41.115
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:br1.49:efr41.115:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:skuP2C90AV:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: P2C90AV
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[ElTouco72]

this fix solved my problem
thanks !

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

Title:
  Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot
  screen

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  [Fix]

  Updated patch from linux-next:
  https://patchwork.freedesktop.org/patch/538562/

  [Test Case]

  Suspend,resume,shutdown,reboot should all work correctly. No nouveau
  stack trace in the kernel log.

  [Where Problems Could Occur]

  Limited to nouveau driver that wants to load nonexistent ACR firmware.
  Only nvidia GPUs are affected.

  [Additional information]

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

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


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

[Kernel-packages] [Bug 2030721] Re: no boot after upgrade to Ubuntu 22.04.3 LTS

[ElTouco72]

the fix in https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352 
solves the issue
maybe you could close this ?

** Changed in: linux-hwe-6.2 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  no boot after upgrade  to Ubuntu 22.04.3 LTS

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

Bug description:
  Hi,

  Yersterday, after a routinely update. it seems that Ubuntu kernel was updated 
to 6.2.0-26
  Since then my machine won't boot. i have to choose previous kernel 5.19 on 
grub menu
  My system was Ubuntu 22.04.2 LTS but it seems to have been updated to Ubuntu 
22.04.3 LTS
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  here is my hardware infos

  00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02)
  00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 
Controller #1 (rev 02)
  00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 
Controller #0 (rev 02)
  00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring 
Technology (rev 01)
  00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe 
RAID Controller
  00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
  00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
  00:15.0 Serial bus controller: Intel Corporation Device 7acc (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Device 7acd (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Device 7ace (rev 11)
  00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
  00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Device 7ac8 (rev 11)
  00:1b.0 PCI bridge: Intel Corporation Device 7ac0 (rev 11)
  00:1c.0 PCI bridge: Intel Corporation Device 7ab8 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Device 7ab0 (rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11)
  00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
  00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
  00:1f.5 Serial bus controller: Intel Corporation Device 7aa4 (rev 11)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (17) 
I219-V (rev 11)
  01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [GeForce RTX 3060 
Lite Hash Rate] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1)
  02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller PM9A1/PM9A3/980PRO

  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce 
RTX 3060 Lite Hash Rate] [10de:2504] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd GA106 [GeForce RTX 3060 Lite 
Hash Rate] [1458:4096]

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


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

[Kernel-packages] [Bug 2042730] Re: network broken with r8169 driver on dell G5 15

[Juerg Haefliger]

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

Upgrade our kernel. This is fixed in 6.2.0-36.37~22.04.1.

** This bug has been marked a duplicate of bug 2031537
   Ethernet not stable 23.04 (RTL8168/8169)

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

Title:
  network broken with r8169 driver on dell G5 15

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

Bug description:
  sometimes my network gets broken with these messages in dmesg
  (watchdog traceback - need reboot - module reload does not help):

  [Sa Nov  4 16:05:18 2023] [ cut here ]
  [Sa Nov  4 16:05:18 2023] NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0 
timed out
  [Sa Nov  4 16:05:18 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230
  [Sa Nov  4 16:05:18 2023] Modules linked in: tls rfcomm xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv
  4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink 
br_netfilter bridge stp llc cmac algif_hash algif_skcipher af_alg snd_ctl_led 
snd_hda_codec
  _realtek bnep snd_hda_codec_generic overlay binfmt_misc snd_sof_pci_intel_cnl 
snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation 
soundwire_cadence 
  snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils 
snd_soc_hdac_hda snd_hda_ext_core intel_tcc_cooling snd_soc_acpi_intel_match 
x86_pkg_temp_therm
  al intel_powerclamp snd_soc_acpi coretemp soundwire_bus snd_soc_core 
kvm_intel snd_compress ac97_bus nls_iso8859_1 snd_hda_codec_hdmi 
snd_pcm_dmaengine kvm snd_hda_in
  tel snd_intel_dspcfg snd_intel_sdw_acpi irqbypass crct10dif_pclmul 
polyval_clmulni snd_hda_codec polyval_generic ghash_clmulni_intel sha512_ssse3 
snd_hda_core aesni_i
  ntel crypto_simd
  [Sa Nov  4 16:05:18 2023]  iwlmvm dell_laptop mei_hdcp mei_pxp intel_rapl_msr 
snd_hwdep cryptd dell_smm_hwmon i915 nouveau mac80211 snd_pcm uvcvideo btusb 
btrtl video
  buf2_vmalloc rapl btbcm videobuf2_memops snd_seq_midi drm_ttm_helper 
drm_buddy btintel joydev videobuf2_v4l2 snd_seq_midi_event input_leds 
dell_wmi_sysman btmtk intel
  _cstate libarc4 serio_raw snd_rawmidi ttm dell_wmi videodev bluetooth 
firmware_attributes_class drm_display_helper snd_seq ftdi_sio iwlwifi cec 
cmdlinepart usbserial 
  videobuf2_common dell_smbios ecdh_generic snd_seq_device rc_core snd_timer 
spi_nor mc dcdbas ecc alienware_wmi drm_kms_helper ledtrig_audio mei_me 
dell_wmi_descriptor
   processor_thermal_device_pci_legacy i2c_algo_bit intel_wmi_thunderbolt 
wmi_bmof mxm_wmi mtd ee1004 hid_multitouch cfg80211 snd 
processor_thermal_device syscopyarea m
  ei sysfillrect processor_thermal_rfim processor_thermal_mbox sysimgblt 
soundcore processor_thermal_rapl intel_rapl_common intel_soc_dts_iosf 
intel_pch_thermal mac_hid
   int3403_thermal
  [Sa Nov  4 16:05:18 2023]  int340x_thermal_zone intel_hid int3400_thermal 
acpi_pad acpi_thermal_rel sparse_keymap sch_fq_codel msr parport_pc ppdev lp 
drm parport efi
  _pstore ip_tables x_tables autofs4 hid_generic nvme crc32_pclmul psmouse 
nvme_core i2c_i801 spi_intel_pci r8169 spi_intel ucsi_acpi i2c_smbus 
intel_lpss_pci ahci type
  c_ucsi xhci_pci intel_lpss realtek nvme_common libahci xhci_pci_renesas 
idma64 typec i2c_hid_acpi i2c_hid hid video wmi pinctrl_cannonlake
  [Sa Nov  4 16:05:18 2023] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 
6.2.0-35-generic #35~22.04.1-Ubuntu
  [Sa Nov  4 16:05:18 2023] Hardware name: Dell Inc. G5 5590/0KW84T, BIOS 
1.25.0 06/01/2023
  [Sa Nov  4 16:05:18 2023] RIP: 0010:dev_watchdog+0x21f/0x230
  [Sa Nov  4 16:05:18 2023] Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 36 6d 78 01 
01 e8 26 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 38 5c 84 b1 48 89 c2 e8 a1 d6 2b 
ff <0f> 0b 
  e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
  [Sa Nov  4 16:05:18 2023] RSP: 0018:b4e4c024ce70 EFLAGS: 00010246
  [Sa Nov  4 16:05:18 2023] RAX:  RBX: 8900090804c8 RCX: 

  [Sa Nov  4 16:05:18 2023] RDX:  RSI:  RDI: 

  [Sa Nov  4 16:05:18 2023] RBP: b4e4c024ce98 R08:  R09: 

  [Sa Nov  4 16:05:18 2023] R10:  R11:  R12: 
89000908
  [Sa Nov  4 16:05:18 2023] R13: 89000908041c R14:  R15: 

  [Sa Nov  4 16:05:18 2023] FS:  () 
GS:89036e30() knlGS:
  [Sa Nov  4 16:05:18 2023] CS:  0010 DS:  ES:  CR0: 80050033
  [Sa Nov  4 16:05:18 2023] CR2: 7f72b6e21000 CR3: 000418a10005 CR4: 
003706e0
  [Sa Nov  4 16:05:18 2023] Call Trace:
  [Sa Nov  4 16:05:18 2023]  
  [Sa Nov  4 16:05:18 2023]  ? show_regs+0x72/0x90
  [Sa Nov  4 16:05:18 

[Kernel-packages] [Bug 2042727] Re: BUG ON UPDATE TO UBUNTU 23.10

[Juerg Haefliger]

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  BUG ON UPDATE TO UBUNTU 23.10

Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Dears, good morning.

  I have been trying to upgrade from Ubuntu 23.04 to Ubuntu 23.10,
  however I have been experiencing some issues. When I click "update",
  the updater stops and no longer runs.

  I've restarted, cleaned, updated, among other procedures, but the bug
  persists.

  Can you help me to fix it?

  Thanks a lot.

  
  yours sincerely,

  Filipe Freitas

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fafreitas   3162 F wireplumber
   /dev/snd/controlC0:  fafreitas   3162 F wireplumber
   /dev/snd/seq:fafreitas   3159 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 10:34:52 2023
  InstallationDate: Installed on 2023-09-14 (50 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. Inspiron 3583
  ProcEnviron:
   LANG=pt_BR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-36-generic N/A
   linux-backports-modules-6.2.0-36-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.0
  dmi.board.name: 000W18
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.0:bd07/03/2023:br1.25:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn000W18:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

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


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

[madigal]

systemctl status thermald.service :

#30 is the full load

** Attachment added: "thermal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038288/+attachment/5716361/+files/thermal.txt

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

[Kernel-packages] [Bug 2042706] Re: Kubuntu 23.10 freezes

[Juerg Haefliger]

The fix is in 6.5.6
f8d2e6429139 misc: rtsx: Fix some platforms can not boot and move the l1ss 
judgment to probe
and will be included in Mantic 6.5 eventually.

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

Title:
  Kubuntu 23.10 freezes

Status in linux package in Ubuntu:
  New

Bug description:
  I have upgraded from Kubuntu 23.04 to Kubuntu 23.10.

  After working for 2-7 minutes, everything becomes extremely
  unresponsive and freezes afterwards. The screen goes black (as if
  graphical shell has crashed and I am in the terminal). However, the
  whole system remains unresponsive. I cannot switch between terminals
  too (Ctrl+Alt+F)

  There was one symptom. When I was working in a Konsole window, and it
  went unresponsive. Then I managed to launch another window, and every
  single command returned "Input/output error" e.g.:

  $ ls
  bash: /usr/bin/ls: Input/output error 

  I noticed I can work around the issue by switching from the 6.5.0
  kernel to the older 6.2.0 one which was left from Kubuntu 23.04.

  The exact kernel package versions are:
  * linux-image-6.5.0-10-generic
  * linux-image-6.2.0-36-generic

  How can I debug the issue?
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh 1215 F wireplumber
   /dev/snd/seq:kyrboh 1212 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-11-04 (0 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=db41af68-2c72-4fc6-a654-5b0f2be10d62 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  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.2.0-36-generic N/A
   linux-backports-modules-6.2.0-36-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  Tags: mantic wayland-session
  Uname: Linux 6.2.0-36-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/10/2022
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

That error in itself is not problematic. The kernel walks down until it
finds an (older) FW to load, in our case that's -81. However, there are
lots of kernel traces in the log related to wifi which could be due to
old(er) FW.

Can you download the latest FW from here:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/iwlwifi-so-a0-hr-b0-83.ucode
put it in /lib/firmware, reboot and check that it is loaded and verify if wifi 
is working now? And please attached the kernel log from that boot/run.

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

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

Bug description:
  [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 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

Test plan for Lunar

** Attachment added: "crash_lunar_test_plan.txt"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5716334/+files/crash_lunar_test_plan.txt

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as 

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

Test plan for Mantic

** Attachment added: "crash_mantic_test_plan.txt.txt"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5716336/+files/crash_mantic_test_plan.txt.txt

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as 

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

Test plan for Jammy HWE

** Attachment added: "crash_jammy_test_plan.txt.txt"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5716332/+files/crash_jammy_test_plan.txt.txt

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as 

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

debdiff for Jammy HWE

** Patch added: "lp2038249-crash-jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5716331/+files/lp2038249-crash-jammy.debdiff

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as 

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

debdiff for Lunar

** Patch added: "lp2038249-crash-lunar.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5716333/+files/lp2038249-crash-lunar.debdiff

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as 

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Chengen Du]

debdiff for Mantic

** Patch added: "lp2038249-crash-mantic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5716335/+files/lp2038249-crash-mantic.debdiff

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as 

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

[Juerg Haefliger]

** Tags added: kern-8464

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

Bug description:
  [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 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Chris Chiu]

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

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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


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

[koba]

＠madigal, could you upload the whole thermald lod?

and systemctl status thermald.service

-- 
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 thermald.service - Thermal 

[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Chris Chiu]

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

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

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

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


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