date:20231208

https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/noble/cpc/+build/544490 is a log from a build
with a new livecd-rootfs that spits out more debugging info on failure.

+ sgdisk binary/boot/disk-uefi.ext4 --print
Disk binary/boot/disk-uefi.ext4: 9437184 sectors, 4.5 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): CD1DD3AE-E4C8-4C5F-BD64-9236C39B9824
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 9437150
Partitions will be aligned on 2-sector boundaries
Total free space is 0 sectors (0 bytes)

Number  Start (sector)End (sector)  Size   Code  Name
   1  235520 9437150   4.4 GiB 8300  
  12  227328  235519   4.0 MiB 8300  CIDATA
  13  342081   1024.0 KiB    loader1
  142082   10239   4.0 MiB   loader2
  15   10240  227327   106.0 MiB   EF00  
+ mount_image binary/boot/disk-uefi.ext4 1
+ trap clean_loops EXIT
+ backing_img=binary/boot/disk-uefi.ext4
+ local rootpart=1
++ losetup --show -f -P -v binary/boot/disk-uefi.ext4
+ loop_device=/dev/loop5
+ '[' '!' -b /dev/loop5 ']'
+ rootfs_dev_mapper=/dev/loop5p1
+ '[' '!' -b /dev/loop5p1 ']'
+ echo '/dev/loop5p1 is not a block device'
/dev/loop5p1 is not a block device
+ ls -l /dev/loop5p1 /dev/loop5p12
brw--- 1 root root 259, 2 Dec  9 04:16 /dev/loop5p1
brw--- 1 root root 259, 3 Dec  9 04:16 /dev/loop5p12
+ exit 1

This clearly shows that:
- there are 5 partitions on the image being passed to losetup
- after losetup exits, /dev/loop5p1 is not present
- after this check fails, an ls of /dev/loop5p* shows devices present for two 
of the partitions - including /dev/loop5p1 that we were looking for in the 
first place - but not all 5.

So this definitely means we have a race after calling losetup -P.

Is this the expected behavior from the kernel?  How do we make this
race-free?

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

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2033124] Re: Intel AX201 wifi card is hardware blocked/RF_KILL after suspend/resume

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

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

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

Title:
  Intel AX201 wifi card is hardware blocked/RF_KILL after suspend/resume

Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  I have HP 340S G7 laptop where the Intel AX201 REV=0x332 card is stuck
  in RF_KILL after suspend. From googling this it appears I am not the
  only one having problems with this card, but I can't seem to find any
  solution to the problem.

  I have the latest BIOS available (F27 11/21/2022). Before with BIOS
  version F13 the Wifi was not working at all, and by upgrading to the
  latest it at least works until suspend.

  I have tested cloning linux-firmware and copying all the iwlwifi-*
  firmwares into /lib/firmware, which does not seem to do anything. I'm
  not sure why but the laptop continues to want to use 72.daa05125.0
  Qu-c0-hr-b0-72.ucode even if a higher number file is available in the
  folder. I thought the last number was a version but I was guessing.

  There are multiple ACPI errors / BIOS Error (bug) in the log. I will
  upload those logs shortly I just need to get them out of the laptop :)

  I have tested this on the latest Ubuntu 22.04.3 LTS as per now, and
  also 23.04 and latest Alpine Linux.

  Kernel: 6.2.0-27-generic

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


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

[Kernel-packages] [Bug 2038678] Re: 6.2.0-34.34 - Black screen with i915

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

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

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

Title:
  6.2.0-34.34 - Black screen with i915

Status in linux package in Ubuntu:
  Expired

Bug description:
  black screen after grub and after login using i915
  revert back to previous kernel. 6.2.0-33
  unable to run report for logs due to black screen.

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


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

[Kernel-packages] [Bug 2038719] Re: Monitor Issues

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

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

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

Title:
  Monitor Issues

Status in linux package in Ubuntu:
  Expired

Bug description:
  Originally on Kernel 5.13 my GPU is not detected and only one monitor
  out of my three functions. I originally fixed this by moving to the
  latest (6.2) which came with its own issues, of which all were
  resolved.

  Yesterday I updated firmware, and this morning after reboot only one
  monitor works again, and the monitor is all stripey and there are 4 of
  a corner of the screen displayed in strips. The operation is fine but
  the display is broken.

  Hopefully this describes the issue enough, if you need an image just
  tell me how to upload it -  I am on the mint distro, I am a newbie to
  this so I hope this is still the right place.

  CPU: Ryzen 7 3700X
  GPU: Radeon 7900XTX
  Boot: Clean linux only

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


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

[Kernel-packages] [Bug 2045573] Re: AMDGPU: cp queue preemption timeout

2023-12-08 Thread Mario Limonciello

Here's the fix commit ID to backport to fix this issue.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6

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

Title:
  AMDGPU: cp queue preemption timeout

Status in linux package in Ubuntu:
  New

Bug description:
  Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic

  Under load, GPU crashed resulting in a weird behavior. Screen froze,
  blinked a few times and the laptop suspended. After wakeup a normal
  login screen showed up but after logging in, it crashed to black
  screen with a message: " cp queue preemption timeout". Eventually I
  was able to log in to a clean session.

  Log attached

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


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

[Kernel-packages] [Bug 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt

2023-12-08 Thread Seth Arnold

There's over 2k instances of errors like this in the terminal log:

dpkg: 경고: files list file for package 'libctf0:amd64' missing; assuming
package has no files currently installed

This is not a happy installation. I recommend a fresh install when
convenient.

As for the prompt, the history log suggests this was run during an
unattended updates run. That'll be invisible to the user. (And, also, I
think it's supposed to skip packages that change configuration files,
but with a few thousand errors for missing file lists, we shouldn't be
surprised that it doesn't work correctly.)

Thanks

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

Title:
  package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I did not recognized the error.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   bluez:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Dec  7 15:44:57 2023
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2021-01-30 (1040 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: bluez
  Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0GY6Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA00:cvnDellInc.:ct6:cvr:sku:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:03  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1332 acl:0 sco:0 events:84 errors:0
TX bytes:3786 acl:0 sco:0 commands:81 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2020-04-03T15:47:01
  mtime.conffile..etc.bluetooth.main.conf: 2020-02-26T18:57:50
  mtime.conffile..etc.bluetooth.network.conf: 2012-12-25T02:46:55
  mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2022-03-24T15:30:38
  mtime.conffile..etc.init.d.bluetooth: 2020-02-26T18:57:50
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


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

[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA

2023-12-08 Thread Austin Domino

I found a patch applied in Linux kernel 5.15.0-91.101 that fixes this
bug

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

Title:
  CPU Lockup related to xhci/DMA

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.19 package in Ubuntu:
  Confirmed
Status in linux-signed-lowlatency package in Ubuntu:
  Confirmed
Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu:
  Confirmed

Bug description:
  CPU lockup problems have been encountered on a number of computers
  running kernel 5.15 or later, but this problem could've been
  introduced in an earlier version. Three of these systems are running a
  light weight version of Ubuntu. The kernels that have been tested are
  4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running
  and causing problems is a program that starts several (4+) distinct
  processes and communicates with different ACM/USB concurrently. This
  problem can be encountered a few minutes after starting this program
  up to about a week later, but it generally happens after ~1-3 days.
  When the lock up occurs, if there are the same number or fewer CPU
  cores than the running number of running processes doing ACM/USB
  device communication, nothing else will execute due to all of the CPU
  cores being locked up until the watchdog frees things up. The longest
  lockup that has been encountered was over 20 minutes! The computers
  that this problem has been tested and verified to be present on are
  the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3.
  Although, this problem appears to be system agnostic; if kernel
  version ~5.15 or later is being used, it'll likely happen if this
  program is setup and run on any system when enough known ACM/USB
  devices are connected to it and communicated with concurrently from
  different processes. The main reason "this program" is being stated in
  a broad sense is because multiple different setups fitting that
  description have been tested trying to get around encountered problems
  in various clever ways and this problem has persisted regardless of
  what's been done.

  Here's a short snippet from the LattePanda Delta 3's syslog:

  Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog 
detected hard LOCKUP on cpu 1
  Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls 
binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda 
mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda 
snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common 
soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core 
nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core 
btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm 
snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 
8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 
goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sch_fq_cod
 el ramoops efi_pstore reed_solomon
  Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone 
ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq 
libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea 
sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca 
crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit 
sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci 
idma64 xhci_pci_renesas wmi video pinctrl_jasperlake
  Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: 
swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu
  Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda 
LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022
  Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 
0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200
  Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 
8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 
0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 
41 5d 41 5e 41
  Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 
EFLAGS: 0002
  Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 
9737c026c2ac RCX: 000

[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA

2023-12-08 Thread Austin Domino

The commit that fixed that bug for that kernel release was
0896f0e476bf58ad0fbc1ede1cb9e19d7eb89da6.

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

Title:
  CPU Lockup related to xhci/DMA

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.19 package in Ubuntu:
  Confirmed
Status in linux-signed-lowlatency package in Ubuntu:
  Confirmed
Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu:
  Confirmed

Bug description:
  CPU lockup problems have been encountered on a number of computers
  running kernel 5.15 or later, but this problem could've been
  introduced in an earlier version. Three of these systems are running a
  light weight version of Ubuntu. The kernels that have been tested are
  4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running
  and causing problems is a program that starts several (4+) distinct
  processes and communicates with different ACM/USB concurrently. This
  problem can be encountered a few minutes after starting this program
  up to about a week later, but it generally happens after ~1-3 days.
  When the lock up occurs, if there are the same number or fewer CPU
  cores than the running number of running processes doing ACM/USB
  device communication, nothing else will execute due to all of the CPU
  cores being locked up until the watchdog frees things up. The longest
  lockup that has been encountered was over 20 minutes! The computers
  that this problem has been tested and verified to be present on are
  the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3.
  Although, this problem appears to be system agnostic; if kernel
  version ~5.15 or later is being used, it'll likely happen if this
  program is setup and run on any system when enough known ACM/USB
  devices are connected to it and communicated with concurrently from
  different processes. The main reason "this program" is being stated in
  a broad sense is because multiple different setups fitting that
  description have been tested trying to get around encountered problems
  in various clever ways and this problem has persisted regardless of
  what's been done.

  Here's a short snippet from the LattePanda Delta 3's syslog:

  Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog 
detected hard LOCKUP on cpu 1
  Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls 
binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda 
mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda 
snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common 
soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core 
nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core 
btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm 
snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 
8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 
goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sch_fq_cod
 el ramoops efi_pstore reed_solomon
  Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone 
ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq 
libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea 
sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca 
crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit 
sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci 
idma64 xhci_pci_renesas wmi video pinctrl_jasperlake
  Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: 
swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu
  Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda 
LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022
  Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 
0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200
  Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 
8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 
0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 
41 5d 41 5e 41
  Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 
EFLAGS: 0002
  Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 
ff

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

Hello You-Sheng, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: firmware-sof (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

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

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (g

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

Hello Chris, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: firmware-sof (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

  [Other info]

  Lunar is skipped, as it'll be EOL soon

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


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

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

Hello You-Sheng, or anyone else affected,

Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-1ubuntu1.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: firmware-sof (Ubuntu Mantic)
   Status: In Progress => Fix Committed

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

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

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

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
als

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

Hello Chris, or anyone else affected,

Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-1ubuntu1.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: firmware-sof (Ubuntu Mantic)
   Status: In Progress => Fix Committed

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

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

  [Other info]

  Lunar is skipped, as it'll be EOL soon

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2023-12-08 Thread Rick S

All good hear, but curious about:
   *apt show zfsutils-linux |grep -e "Breaks"

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>>
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)

Both live nicely here for me:
* apt policy zfsutils-linux zfs-dkms 
zfsutils-linux:
  Installed: 2.2.2-0ubuntu1
  Candidate: 2.2.2-0ubuntu1
  Version table:
 *** 2.2.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
zfs-dkms:
  Installed: 2.2.2-0ubuntu1
  Candidate: 2.2.2-0ubuntu1
  Version table:
 *** 2.2.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages
100 /var/lib/dpkg/status

Seems solid today with multiple boots, reboots and cold boots

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  Incomplete
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium

  * New upstream release. LP: #2044657
- Address potential data corruption

I'm assuming the plan for fixing it on earlier releases does not involve
updating to 2.2.2.

And this does not fall under a hardware enablement exception.  AND there
are packaging changes under debian/.

The diff for this new upstream release is 9kloc.  I would expect a
cherry-picked fix here for mantic, not a full upstream backport - just
as will be required for releases prior to mantic.

** Changed in: zfs-linux (Ubuntu Mantic)
   Status: In Progress => Incomplete

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  Incomplete
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2046011] [NEW] apply nvidia igx patches for Nov 29 - Dec 8 2023

2023-12-08 Thread Brad Griffis

Public bug reported:

Additional patches for IGX kernel.

** Affects: linux-nvidia-tegra-igx (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  apply nvidia igx patches for Nov 29 - Dec 8 2023

Status in linux-nvidia-tegra-igx package in Ubuntu:
  New

Bug description:
  Additional patches for IGX kernel.

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


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

[Kernel-packages] [Bug 2046008] [NEW] Jammy update: v5.15.136 upstream stable release

2023-12-08 Thread Kamal Mostafa

Public bug reported:

SRU Justification

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

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

iommu/vt-d: Avoid memory allocation in iommu_suspend()
scsi: core: Use a structure member to track the SCSI command submitter
scsi: core: Rename scsi_mq_done() into scsi_done() and export it
scsi: ib_srp: Call scsi_done() directly
RDMA/srp: Do not call scsi_done() from srp_abort()
RDMA/cxgb4: Check skb value for failure to allocate
perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7
of: overlay: Reorder struct fragment fields kerneldoc
platform/x86: think-lmi: Fix reference leak
platform/x86: hp-wmi:: Mark driver struct with __refdata to prevent section 
mismatch warning
lib/test_meminit: fix off-by-one error in test_pages()
HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
quota: Fix slow quotaoff
net: prevent address rewrite in kernel_bind()
ALSA: usb-audio: Fix microphone sound on Opencomm2 Headset
KEYS: trusted: allow use of kernel RNG for key material
KEYS: trusted: Remove redundant static calls usage
drm/msm/dp: do not reinitialize phy unless retry during link training
drm/msm/dsi: skip the wait for video mode done if not applicable
drm/msm/dsi: fix irq_of_parse_and_map() error checking
drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid overflow
ravb: Fix up dma_free_coherent() call in ravb_remove()
ravb: Fix use-after-free issue in ravb_tx_timeout_work()
ieee802154: ca8210: Fix a potential UAF in ca8210_probe
mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type
eth: remove copies of the NAPI_POLL_WEIGHT define
xen-netback: use default TX queue size for vifs
riscv, bpf: Factor out emit_call for kernel and bpf context
riscv, bpf: Sign-extend return values
drm/vmwgfx: fix typo of sizeof argument
bpf: Fix verifier log for async callback return values
net: macsec: indicate next pn update when offloading
net: phy: mscc: macsec: reject PN update requests
ixgbe: fix crash with empty VF macvlan list
net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp
net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
pinctrl: renesas: rzn1: Enable missing PINMUX
nfc: nci: assert requested protocol is valid
workqueue: Override implicit ordered attribute in 
workqueue_apply_unbound_cpumask()
net: add sysctl accept_ra_min_rtr_lft
net: change accept_ra_min_rtr_lft to affect all RA lifetimes
net: release reference to inet6_dev pointer
media: mtk-jpeg: Fix use after free bug due to uncanceled work
dmaengine: stm32-mdma: abort resume if no ongoing transfer
xhci: Keep interrupt disabled in initialization until host is running.
usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer
net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read
usb: dwc3: Soft reset phy on probe for host
usb: cdns3: Modify the return value of cdns_set_active () to void when 
CONFIG_PM_SLEEP is disabled
usb: musb: Get the musb_qh poniter after musb_giveback
usb: musb: Modify the "HWVers" register address
iio: pressure: bmp280: Fix NULL pointer exception
iio: pressure: dps310: Adjust Timeout Settings
iio: pressure: ms5611: ms5611_prom_is_valid false negative bug
drm/amdgpu: add missing NULL check
drm/amd/display: Don't set dpms_off for seamless boot
ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CBA
x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs
mcb: remove is_added flag from mcb_device struct
thunderbolt: Workaround an IOMMU fault on certain systems with Intel Maple Ridge
thunderbolt: Check that lane 1 is in CL0 before enabling lane bonding
libceph: use kernel_connect()
ceph: fix incorrect revoked caps assert in ceph_fill_file_size()
ceph: fix type promotion bug on 32bit systems
Input: powermate - fix use-after-free in powermate_config_complete
Input: psmouse - fix fast_reconnect function for PS/2 mode
Input: xpad - add PXN V900 support
Input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table
Input: goodix - ensure int GPIO is in input for gpio_count == 1 && gpio_int_idx 
== 0 case
tee: amdtee: fix use-after-free vulnerability in amdtee_close_session
cgroup: Remove duplicates in cgroup v1 tasks file
counter: microchip-tcb-capture: Fix the use of internal GCLK logic
usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call
usb: cdnsp: Fixes issue with dequeuing not queued requests
x86/alternatives: Disable KASAN in apply_alternatives()
dmaengine: idxd: use spin_lock_irqsave before wait_event_lock_irq
dmaengine: mediatek: Fix deadlock caused by synchron

[Kernel-packages] [Bug 2046003] [NEW] Weirdly behaving CPU power setting on Thinkpad X1 carbon Intel i7-10710U

2023-12-08 Thread Bartosz Woronicz

Public bug reported:

On current kernel 5.15.0-89-generic I change the setting to power, but
when I check /sys nothing happens

root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance powersave
root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference
balance_performance
root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
default performance balance_performance balance_power power 
root@graf:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 
powersave
root@graf:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor 
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-89-generic 5.15.0-89.99
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
Uname: Linux 5.15.0-89-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  8 21:24:31 2023
InstallationDate: Installed on 2021-04-15 (967 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20R10015US
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-89-generic 
root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-89-generic N/A
 linux-backports-modules-5.15.0-89-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.23
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-24 (592 days ago)
dmi.bios.date: 11/08/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2QET54W(1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20R10015US
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:bvrN2QET54W(1.48):bd11/08/2023:br1.48:efr1.19:svnLENOVO:pn20R10015US:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R10015US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20R10015US
dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot from 2023-12-08 21-21-16.png"
   
https://bugs.launchpad.net/bugs/2046003/+attachment/5727581/+files/Screenshot%20from%202023-12-08%2021-21-16.png

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

Title:
  Weirdly behaving CPU power setting on Thinkpad X1 carbon Intel
  i7-10710U

Status in linux package in Ubuntu:
  New

Bug description:
  On current kernel 5.15.0-89-generic I change the setting to power, but
  when I check /sys nothing happens

  root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
  performance powersave
  root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference
  balance_performance
  root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
  default performance balance_performance balance_power power 
  root@graf:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 
  powersave
  root@graf:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor 
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-89-generic 5.15.0-89.99
  ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
  Uname: Linux 5.15.0-89-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  8 21:24:31 2023
  InstallationDate: Installed on 2021-04-15 (967 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20R10015US
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-89-generic 
root=/dev/mapper/ubuntu-root 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.
  RelatedPackageVersi

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

2023-12-08 Thread Andy Gospodarek

Patches that may not be needed or could be a little tricky

1.  Anything with 'Merge' (obviously)
2.  'a9ca9f9ceff3 page_pool: split types and declarations from page_pool.h' 
will add new page pool header files.  There may be some header-file changes 
that do not apply as cleanly.
3.  '2b3082c6ef3b net: flow_dissector: Use 64bits for used_keys' -- skip

These should be all that are needed for 22.04.4.  Thanks, Jeff!

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

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

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

Bug description:
  These patches are needed on top of v6.7 to support Broadcom 5760X
  Adapters.  These patches currently reside in the net-next tree and
  will be included in v6.8.

  Prerequisite commits in net-next today:

  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for 
TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field

  These 13 patches below were submitted on 11/20/23 and accepted on
  11/21/23.  These are the initial patches with 5760X contents.

  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware 
calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free 
bp->ctx

  The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23.
  These are all the basic L2 patches for 5760X including the PCI IDs:

  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware 
interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types 
for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions

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


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

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

2023-12-08 Thread Andy Gospodarek

Here would be the patches if we brought this back to as far back as a
v6.5 kernel:

v6.6 bnxt_en patches
edc0140cc3b7 bnxt_en: Flush XDP for bnxt_poll_nitroa0()'s NAPI
f7e97ce26972 Merge tag 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
e3b3a87967ce bnxt: use the NAPI skb allocation cache
8becd1961c73 bnxt_en: Add tx_resets ring counter
a080b47a04c5 bnxt_en: Display the ring error counters under ethtool -S
4c70dbe3c008 bnxt_en: Save ring error counters across reset
d38c19b13b10 bnxt_en: Increment rx_resets counter in bnxt_disable_napi()
578fcfd26e2a bnxt_en: Let the page pool manage the DMA mapping
86b05508f775 bnxt_en: Use the unified RX page pool buffers for XDP and non-XDP
f1d152eb66a3 rtnetlink: remove redundant checks for nlattr IFLA_BRIDGE_MODE
3d5ecada049f bnxt_en: Fix W=stringop-overflow warning in bnxt_dcb.c
ac1b8c978a7a bnxt_en: Fix W=1 warning in bnxt_dcb.c from fortify memcpy()
a9ca9f9ceff3 page_pool: split types and declarations from page_pool.h
35b1b1fd9638 Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
2b3082c6ef3b net: flow_dissector: Use 64bits for used_keys
9f49db62f58e eth: bnxt: fix warning for define in struct_group
833c4a8105ac eth: bnxt: fix one of the W=1 warnings about fortified memcpy()
61220e098e85 bnxt_en: Share the bar0 address with the RoCE driver
cf1694f09894 bnxt_en: Update HW interface headers
2b56b3d99241 eth: bnxt: handle invalid Tx completions more gracefully
9b1a00fda61e eth: bnxt: take the bit to set as argument of bnxt_queue_sp_work()
fea2993aecd7 eth: bnxt: move and rename reset helpers
47b7acfb016b bnxt_en: use dev_consume_skb_any() in bnxt_tx_int

v6.7 bnxt_en patches
9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters
09d96ee5674a page_pool: remove PP_FLAG_PAGE_FRAG
5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes
64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API
5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic
94c89e73d377 bnxt_en: refactor speed independent ethtool modes
d6263677bb1b bnxt_en: support lane configuration via ethtool
ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode
fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event
55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI
074e1b4221b5 bnxt_en: devlink health: use retained error fmsg API
73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices
c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN"
cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs
e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN
a19b4801457b bnxt_en: Event handler for Thermal event
3d9cf962067b bnxt_en: Use non-standard attribute to expose shutdown temperature
cd13244f19eb bnxt_en: Expose threshold temperatures through hwmon
847da8b1178c bnxt_en: Modify the driver to use hwmon_device_register_with_info
a47f3b3992aa bnxt_en: Move hwmon functions into a dedicated file
6ad71984aa6b bnxt_en: Enhance hwmon temperature reporting
754fbf604ff6 bnxt_en: Update firmware interface to 1.10.2.171
e9cbc89067cc Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net


Merges and other general issues can be skipped.  We will audit this list by CoB 
today to make sure there are none that can be omitted.

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

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

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

Bug description:
  These patches are needed on top of v6.7 to support Broadcom 5760X
  Adapters.  These patches currently reside in the net-next tree and
  will be included in v6.8.

  Prerequisite commits in net-next today:

  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for 
TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field

  These 13 patches below were submitted on 11/20/23 and accepted on
  11/21/23.  These are the initial patches with 5760X contents.

  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

2023-12-08 Thread Andreas Hasenack

This was uploaded, removing sponsors as there is nothing further to
sponsor.

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Committed
Status in ivsc-driver source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come accordi

[Kernel-packages] [Bug 2045443] Re: Ubuntu-5.15.0-89.99 breaks virtio-net spec and doesn't boot

2023-12-08 Thread Daniel Farina

I realize now we had a second issue on arm64 on Ubuntu 20.04 a bit
before that resulted from the same patch, we got around that one without
looking deeply by changing kernels. At the time we declined to
investigate.

So, I have a further question: so, I suspect the reason this slipped
through Ubuntu's QA process is it probably only uses qemu, which must
work at least somewhat well enough. I don't know how the author (Jason)
found he had introduced a defect so quickly upstream, but the issue
existed in upstream linux only briefly, and got magnified by the Ubuntu
release process.

A simple answer would be: I will run proposed kernels and write in if
anything weird happens. But I imagine Ubuntu has a more involved test
suite to qualify kernels. Can an alternative vmm somehow get into the
testing matrix? It's also possible that Firecracker and Crosvm would
have suffered this issue, as they all share Rust crates to do some of
the implementation.

Secondly, are there frequently refreshed upstream packages of kernels
(vanilla, ubuntu modified both) in apt repositories I could add to this
testing matrix, to catch bugs as close to the source and as early as
possible, including in linux upstream? As an administrative matter, I
could somewhat easily test boot and some workload on kernels a, b, c,
etcetera if the packaging is there.

It's no doubt worth our while to check basic functionality working
regularly, but I don't think we can build up Ubuntu's full acceptance
infrastructure, which would be the next level of sophistication.

There may also be some intermediate methods, e.g. if there's some Ubuntu
tests we can run in a VM, even if it is not all of them.

Let me know if this is the place to discuss this. It's obviously not
*exactly* the right place...perhaps a mailing list? But maybe the
answers are simple enough.

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

Title:
  Ubuntu-5.15.0-89.99 breaks virtio-net spec and doesn't boot

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

Bug description:
  I use a non-qemu VMM, cloud-hypervisor. It looks like a patch was
  applied, that introduced a bug, a week later another patch got written
  to fix that bug, and that second patch was not applied in Ubuntu's
  release, but is seen in Greg KH's 5.15 branch.

  The result of the bug is the kernel will not boot.

  Cumulative diff:

  ```
  > git diff  Ubuntu-5.15.0-86.96 Ubuntu-5.15.0-89.99 drivers/net/virtio_net.c
  diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
  index 0351f86494f1..af335f8266c2 100644
  --- a/drivers/net/virtio_net.c
  +++ b/drivers/net/virtio_net.c
  @@ -3319,6 +3319,8 @@ static int virtnet_probe(struct virtio_device *vdev)
  }
  }

  +   _virtnet_set_queues(vi, vi->curr_queue_pairs);
  +
  /* serialize netdev register + virtio_device_ready() with ndo_open() 
*/
  rtnl_lock();

  @@ -3339,8 +3341,6 @@ static int virtnet_probe(struct virtio_device *vdev)
  goto free_unregister_netdev;
  }

  -   virtnet_set_queues(vi, vi->curr_queue_pairs);
  -
  /* Assume link up if device can't report link status,
     otherwise get link status from config. */
  netif_carrier_off(dev);
  ```

  Blamed Commit:

  ```
  commit 5e0545ef5682562ffef072138d9340ea36a2ebc9
  Author: Jason Wang 
  Date:   Tue Jul 25 03:20:49 2023 -0400

  virtio-net: fix race between set queues and probe

  BugLink: https://bugs.launchpad.net/bugs/2035400

  commit 25266128fe16d5632d43ada34c847d7b8daba539 upstream.

  A race were found where set_channels could be called after registering
  but before virtnet_set_queues() in virtnet_probe(). Fixing this by
  moving the virtnet_set_queues() before netdevice registering. While at
  it, use _virtnet_set_queues() to avoid holding rtnl as the device is
  not even registered at that time.

  Cc: sta...@vger.kernel.org
  Fixes: a220871be66f ("virtio-net: correctly enable multiqueue")
  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Reviewed-by: Xuan Zhuo 
  Link: 
https://lore.kernel.org/r/20230725072049.617289-1-jasow...@redhat.com
  Signed-off-by: Jakub Kicinski 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Stefan Bader 
  ```

  Investigation into Greg KH's 5.15 branch shows the (unapplied?)
  followup as:

  ```
  commit 431db3f48c286462ad7453ccdf284f590aafa949
  Author: Jason Wang 
  Date:   Wed Aug 9 23:12:56 2023 -0400

  virtio-net: set queues after driver_ok

  commit 51b813176f098ff61bd2833f627f5319ead098a5 upstream.

  Commit 25266128fe16 ("virtio-net: fix race between set queues and
  probe") tries to fix the race between set queues and probe by calling
  _vi

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] ERROR UVD not responding, trying to reset the VCPU!!!

2023-12-08 Thread Romano Giannetti

I have to confirm that it started to happen to me too,

ii  linux-firmware
20220329.git681281e4-0ubuntu3.23  all  Firmware for
Linux kernel drivers


and 

[romano:~] % inxi -G


Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
driver: i915 v: kernel
  Device-2: AMD Seymour [Radeon HD 6400M/7400M Series] driver: radeon
v: kernel
  Device-3: Silicon Motion WebCam SC-13HDL11431N type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: intel gpu: i915
resolution: 1600x900~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
v: 3.3 Mesa 23.0.4-0ubuntu1~22.04.1

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: in

[Kernel-packages] [Bug 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

2023-12-08 Thread Kai-Heng Feng

** Tags added: oem-priority originate-from-2038400 stella

** Tags added: originate-from-2045249

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

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:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

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


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

[Kernel-packages] [Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel

2023-12-08 Thread Francis Ginther

We are still looking into this issue. While we can reproduce the test
case and see difference in the performance, the delta is not as
significant and our results have not very consistent. I'm taking the
approach of setting up a more comprehensive test environment to run more
tests faster. Hopefully we can then go through an analysis and bisect
process with more meaningful results.

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

Title:
  Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4
  Ubuntu 20.04 kernel

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

Bug description:
  We in the Canonical Public Cloud team have received report from our
  colleagues in Google regarding a potential performance regression with
  the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were
  performed using the linux-gkeop and linux-gkeop-5.15 kernels.

  I have verified with the generic Ubuntu 20.04 5.4 linux-generic and
  the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels.

  The tests were run using `fio`

  fio commands:

  * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`
  * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`

  
  My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the 
results are below:

  Using 5.4 kernel

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.4.0-164-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] 
  fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov  2 09:15:22 2023
write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets
  slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61
  clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38
   lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80
  clat percentiles (usec):
   |  1.00th=[  775],  5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024],
   | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261],
   | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932],
   | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676],
   | 99.99th=[32113]
 bw (  MiB/s): min=  524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, 
samples=4232
 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, 
samples=4232
lat (nsec)   : 500=0.01%, 750=0.01%, 1000=0.01%
lat (usec)   : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01%
lat (usec)   : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93%
lat (msec)   : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07%
lat (msec)   : 100=0.01%
cpu  : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103
IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
   submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.0%
   complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.1%
   issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0
   latency   : target=0, window=0, percentile=100.00%, depth=128

  Run status group 0 (all jobs):
WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), 
io=320GiB (344GB), run=264837-264837msec

  Disk stats (read/write):
sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, 
util=100.00%
  ```

  
  After upgrading to linux-generic-hwe-20.04 kernel and rebooting

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.15.0-88-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s]
  fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov  2 09:46:49 2023
write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets
  slat (nsec): min=660, max=325426k, avg=10351.04, stdev=232438.50
  clat (nsec): min=1100, max=782743k, avg=6595

[Kernel-packages] [Bug 2045979] Re: linux-libc-dev: Missing headers /usr/include/linux/dn.h and /usr/include/linux/netfilter_decnet.h

2023-12-08 Thread velmafia

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

Title:
  linux-libc-dev: Missing headers /usr/include/linux/dn.h and
  /usr/include/linux/netfilter_decnet.h

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  In linux-libc-dev package in focal (5.4.0-167.184), two headers file are 
missing:
  - /usr/include/linux/dn.h
  - /usr/include/linux/netfilter_decnet.h

  In older package version (5.4.0-26.30) available in focal, headers are
  present.

  This files are listed in packages.ubuntu.com:
  https://packages.ubuntu.com/en/focal/amd64/linux-libc-dev/filelist,
  but not exist in deb package. Also "searching by filename" show that
  this file should be part of linux-libc-dev package:
  
https://packages.ubuntu.com/search?searchon=contents&keywords=dn.h&mode=exactfilename&suite=focal&arch=any

  Problem exist also in jammy 5.15.0-89.99, but here the difference between the 
file list and the real package contents is greater: 3 file was added to deb 
package:
  - /usr/include/linux/ipu-isys.h
  - /usr/include/linux/ipu-psys.h
  - /usr/include/scsi/scsi_bsg_mpi3mr.h
  but files are not present in the package file list: 
https://packages.ubuntu.com/en/jammy/amd64/linux-libc-dev/filelist

  I checked two above version for i386 and amd64 arch, but probably
  problem affected more packages.

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


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

[Kernel-packages] [Bug 2045979] [NEW] linux-libc-dev: Missing headers /usr/include/linux/dn.h and /usr/include/linux/netfilter_decnet.h

You have been subscribed to a public bug:

Hi,
In linux-libc-dev package in focal (5.4.0-167.184), two headers file are 
missing:
- /usr/include/linux/dn.h
- /usr/include/linux/netfilter_decnet.h

In older package version (5.4.0-26.30) available in focal, headers are
present.

This files are listed in packages.ubuntu.com:
https://packages.ubuntu.com/en/focal/amd64/linux-libc-dev/filelist, but
not exist in deb package. Also "searching by filename" show that this
file should be part of linux-libc-dev package:
https://packages.ubuntu.com/search?searchon=contents&keywords=dn.h&mode=exactfilename&suite=focal&arch=any

Problem exist also in jammy 5.15.0-89.99, but here the difference between the 
file list and the real package contents is greater: 3 file was added to deb 
package:
- /usr/include/linux/ipu-isys.h
- /usr/include/linux/ipu-psys.h
- /usr/include/scsi/scsi_bsg_mpi3mr.h
but files are not present in the package file list: 
https://packages.ubuntu.com/en/jammy/amd64/linux-libc-dev/filelist

I checked two above version for i386 and amd64 arch, but probably
problem affected more packages.

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


** Tags: bot-comment
-- 
linux-libc-dev: Missing headers /usr/include/linux/dn.h and 
/usr/include/linux/netfilter_decnet.h
https://bugs.launchpad.net/bugs/2045979
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 2032247] Re: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed

2023-12-08 Thread Matthias Klose

ok, so the missing rcrt1.o file looks like another issue. we probably
should revert to the two-staged builds, if that configuration isn't
picked up correctly.

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

Title:
  [UBUNTU 23.04] S390: static-PIE programs segfaults if
  libc6-dev-s390x-cross package is installed

Status in Ubuntu on IBM z Systems:
  New
Status in gcc-12-cross package in Ubuntu:
  New
Status in gcc-13-cross package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == by Stefan  ==
  A simple helloworld program build and linked as static-PIE segfaults while 
startup in __libc_setup_tls:
  $ gcc -c -fPIE -static-pie -o hello.o hello.c
  $ gcc -o hello hello.o -static-pie

  Note:
  If only libc6-dev package is installed, all is fine.
  If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will 
see the mentioned segfault.

  Linking with "-Wl,-v" dumps the used linker command and it shows the used 
startup-files:
  /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev
  /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross
  /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o
  /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o
  /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross

  Linking as static-PIE requires the rcrt1.o file, which is not
  available in libc6-dev-s390x-cross package, but in libc6-dev. Due to
  this mixing of the startup-files, you get the segfault.

  This issue can be fixed by enabling static-PIE also in the 
libc6-dev-s390x-cross package, then all startup-files belong to the same 
package. For s390x static-PIE was introduced in glibc 2.36:
  commit "S390: Enable static PIE" (in glibc 2.36)
  
https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c

  There is a configure check which do a link-test to ensure that a
  suitable binutils(ld) version is used. Afterwards static-PIE is
  automatically enabled. The required binutils-patches are first
  included in binutils 2.39.

  According to the build log of package cross-toolchain-base (see 
https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036),
 the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned 
configure check fails:
  running configure fragment for sysdeps/s390/s390-64
  checking for s390-specific static PIE requirements... no

  In this cross build, glibc is configured in order to first build the
  crt-startup-files, which are needed to complete the cross-gcc build.
  At this time, the sysroot does not contain the crt-files or libc.so
  itself. Thus the "linking" configure check is failing. After building
  the cross-gcc, glibc is build without re-configuring. Thus static-PIE
  is not enabled.

  In glibc-upstream, this configure check is now adjusted and it allows 
checking binutils by version number:
  commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will 
be in glibc 2.39)
  
https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881

  Perhaps you also have to pick the following commits by Sam James which 
adjusted the tests in between (both are in glibc 2.36):
  - commit "s390: use $READELF"
  
https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea
  - commit "s390: use LC_ALL=C for readelf call"
  
https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28


  In addition to the static-PIE configure-checks, there are those other 
s390-specific configure-checks to determine which IFUNC-optimizations can be 
build and used as default. Those also fail for libc6-dev-s390x-cross as linking 
is also involved:
  running configure fragment for sysdeps/s390
  checking for __builtin_tbegin... yes
  checking for S390 vector instruction support... no
  configure: WARNING: Use binutils with vector-support in order to use 
optimized implementations.
  checking for S390 vector support in gcc... no
  checking for S390 arch13 zarch instruction support... no
  checking for S390 z10 zarch instruction support as default... no
  checking for S390 z196 zarch instruction support as default... no
  checking for S390 z13 zarch instruction support as default... no
  checking for S390 arch13 zarch instruction support as default... no

  Those checks were also adjusted in glibc-upstream. Please also pick this 
commits:
  commit "S390: Use compile-only instead of also link-tests in configure." (in 
glibc 2.38)
  
https://sourceware.org/git/?p=glibc.git;a=commit;h=368b7c614b102122b86af3953daea2b30230d0a8

  I've observed this issue on Ubuntu 23.04 with glibc 2.37 and binutils 2.40:
  binutils/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 s390x [installed]
  libc6-dev-s390x-cross/lunar,now 2.37-0ubuntu2cross1 all [installed]

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

2023-12-08 Thread Timo Aaltonen

** Description changed:

  [Impact]
  Old RPL soundwire topology files are found to be muted when doing audio 
capture on left channel.
  
  [Fix]
  
  The commit from https://github.com/thesofproject/sof-bin/ is required.
  * 
https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d
 (Update v2.2.8 topology files for Intel RPL platforms)
  
- 
  [Test Case]
  
  Test audio functions on Dell MayaBay RTL platforms.
  
  [Where problems could occur]
  Most topology files for Intel RPL are updated. Need more confirmation on 
Intel RPL platforms.
+ 
+ [Other info]
+ 
+ Lunar is skipped, as it'll be EOL soon

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

  [Other info]

  Lunar is skipped, as it'll be EOL soon

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


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

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

2023-12-08 Thread You-Sheng Yang

Remove duplicate mark. The required change is being SRUed along with bug
2042090, but not duplicated by 2042090.

** This bug is no longer a duplicate of bug 2042090
   Orchid Bay MLK2/Maya Bay MLK soundwire support

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  
  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

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


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

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

2023-12-08 Thread Jack

Yeah, i have this bug since forever, occurs randomly when opening steam.
It will load the steam window but not all the content inside then
freeze.

Ubuntu 22.04
Kernel: 6.2.0-37-generic 
Amdgpu Mesa 23.3.0 - kisak-mesa PPA (LLVM 15.0.7)

A crash from today

Dec  8 15:31:33 H-Linux steam.desktop[20716]: RegisterForAppOverview 2: 325ms
Dec  8 15:31:34 H-Linux ubuntu-appindicat...@ubuntu.com[2663]: unable to update 
icon for steam
Dec  8 15:32:20 H-Linux kernel: [ 3518.714561] GpuWatchdog[20825]: segfault at 
0 ip 7fb7cbd92bc6 sp 7fb7c09fd370 error 6 in 
libcef.so[7fb7c78ef000+777] likely on CPU 0 (core 0, socket 0)
Dec  8 15:32:20 H-Linux kernel: [ 3518.714585] Code: 89 de e8 4d ee 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 2e 66 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 3a d1 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  https://askubuntu.com/q/1490916/170177
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  https://unix.stackexchange.com/q/658684/45386
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

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

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

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  https://askubuntu.com/q/1490916/170177
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  https://unix.stackexchange.com/q/658684/45386
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

2023-12-08 Thread Michael Gödderz

Update. 
After last "apt upgrade" and kernel 6.2.0-37-generic everything is working fine 
on my notebook.

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

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

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

This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu4

---
firmware-sof (2.2.6-1ubuntu4) noble; urgency=medium

  * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
- Add Intel SOF2.7.2 topology files.
  * Update soundwire topology files for Intel RPL platforms. LP: #2044330
- Update v2.2.8 topology files for Intel RPL platforms

 -- You-Sheng Yang   Wed, 15 Nov 2023
23:32:40 +0800

** Changed in: firmware-sof (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Update soundwire topology files for Intel RPL platforms

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

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

  [Fix]

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

  
  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

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

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


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

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu4

---
firmware-sof (2.2.6-1ubuntu4) noble; urgency=medium

  * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
- Add Intel SOF2.7.2 topology files.
  * Update soundwire topology files for Intel RPL platforms. LP: #2044330
- Update v2.2.8 topology files for Intel RPL platforms

 -- You-Sheng Yang   Wed, 15 Nov 2023
23:32:40 +0800

** Changed in: firmware-sof (Ubuntu Noble)
   Status: In Progress => 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/2042090

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

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

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

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


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

[Kernel-packages] [Bug 2045778] Re: panic due to unhandled page fault via BPF_PROG_RUN syscall

Trying to upload dmesg crashes the site.

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

Title:
  panic due to unhandled page fault via BPF_PROG_RUN syscall

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  Here is a kernel oops triggered from user space by invoking a BPF
  program:

  [ 1191.051531] BUG: unable to handle page fault for address: ea053c70
  [ 1191.053848] #PF: supervisor read access in kernel mode
  [ 1191.055183] #PF: error_code(0x) - not-present page
  [ 1191.056513] PGD 334e15067 P4D 334e15067 PUD 334e17067 PMD 0 
  [ 1191.058016] Oops:  [#1] SMP NOPTI
  [ 1191.058984] CPU: 1 PID: 2557 Comm: ebpf.test Not tainted 6.2.0-1016-azure 
#16~22.04.1-Ubuntu
  [ 1191.061167] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
  [ 1191.063804] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.065064] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
  [ 1191.069766] RSP: 0018:a64e03053c50 EFLAGS: 00010246
  [ 1191.071117] RAX: 0001 RBX: a64e0005a000 RCX: 
a64e03053c3f
  [ 1191.073415] RDX: 0001 RSI: a64e03053c3f RDI: 
8a468580
  [ 1191.075351] RBP: ea053cf0 R08:  R09: 

  [ 1191.077722] R10:  R11:  R12: 
97dc75673c00
  [ 1191.079681] R13: a64e0005a048 R14: a64e03053d34 R15: 
0001
  [ 1191.081636] FS:  7fd4a2ffd640() GS:97df6fc8() 
knlGS:
  [ 1191.083866] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1191.085455] CR2: ea053c70 CR3: 00019ff80001 CR4: 
00370ee0
  [ 1191.087405] Call Trace:
  [ 1191.088121]  
  [ 1191.088745]  ? show_regs+0x6a/0x80
  [ 1191.089710]  ? __die+0x25/0x70
  [ 1191.090591]  ? page_fault_oops+0x79/0x180
  [ 1191.091708]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.093027]  ? search_exception_tables+0x61/0x70
  [ 1191.094421]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.095686]  ? kernelmode_fixup_or_oops+0xa2/0x120
  [ 1191.097014]  ? __bad_area_nosemaphore+0x16f/0x280
  [ 1191.098323]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.099584]  ? apparmor_file_alloc_security+0x1f/0xd0
  [ 1191.100989]  ? bad_area_nosemaphore+0x16/0x20
  [ 1191.102235]  ? do_kern_addr_fault+0x62/0x80
  [ 1191.103393]  ? exc_page_fault+0xd8/0x160
  [ 1191.104505]  ? asm_exc_page_fault+0x27/0x30
  [ 1191.105669]  ? bpf_test_run+0x104/0x2e0
  [ 1191.106745]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.108010]  ? bpf_prog_test_run_skb+0x2e4/0x4f0
  [ 1191.109350]  ? __fdget+0x13/0x20
  [ 1191.110304]  ? __sys_bpf+0x706/0xea0
  [ 1191.111299]  ? __x64_sys_bpf+0x1a/0x30
  [ 1191.112307]  ? do_syscall_64+0x5c/0x90
  [ 1191.113366]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.114634]  ? exit_to_user_mode_loop+0xec/0x160
  [ 1191.115929]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.117466]  ? __set_task_blocked+0x29/0x70
  [ 1191.118904]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.120482]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.122073]  ? sigprocmask+0xb8/0xe0
  [ 1191.123360]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.124868]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.126523]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.128028]  ? syscall_exit_to_user_mode+0x27/0x40
  [ 1191.129599]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.131033]  ? do_syscall_64+0x69/0x90
  [ 1191.132242]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.134199]  ? do_syscall_64+0x69/0x90
  [ 1191.135504]  ? entry_SYSCALL_64_after_hwframe+0x73/0xdd
  [ 1191.137137]  
  [ 1191.137942] Modules linked in: nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp 
llc xt_tcpudp tls xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink overlay nvme_fabrics 
udf crc_itu_t binfmt_misc nls_iso8859_1 kvm_amd ccp joydev kvm hid_generic 
irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd hyperv_drm 
drm_kms_helper syscopyarea sysfillrect serio_raw sysimgblt drm_shmem_helper 
hid_hyperv hv_netvsc hid hyperv_keyboard pata_acpi dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua sch_fq_codel drm efi_pstore i2c_core ip_tables 
x_tables autofs4
  [ 1191.156484] CR2: ea053c70
  [ 1191.158026] ---[ end trace  ]---
  [ 1191.159518] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.160912] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89

[Kernel-packages] [Bug 2045778] Re: panic due to unhandled page fault via BPF_PROG_RUN syscall

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045778/+attachment/5727445/+files/lspci-vvnn.log

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

Title:
  panic due to unhandled page fault via BPF_PROG_RUN syscall

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  Here is a kernel oops triggered from user space by invoking a BPF
  program:

  [ 1191.051531] BUG: unable to handle page fault for address: ea053c70
  [ 1191.053848] #PF: supervisor read access in kernel mode
  [ 1191.055183] #PF: error_code(0x) - not-present page
  [ 1191.056513] PGD 334e15067 P4D 334e15067 PUD 334e17067 PMD 0 
  [ 1191.058016] Oops:  [#1] SMP NOPTI
  [ 1191.058984] CPU: 1 PID: 2557 Comm: ebpf.test Not tainted 6.2.0-1016-azure 
#16~22.04.1-Ubuntu
  [ 1191.061167] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
  [ 1191.063804] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.065064] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
  [ 1191.069766] RSP: 0018:a64e03053c50 EFLAGS: 00010246
  [ 1191.071117] RAX: 0001 RBX: a64e0005a000 RCX: 
a64e03053c3f
  [ 1191.073415] RDX: 0001 RSI: a64e03053c3f RDI: 
8a468580
  [ 1191.075351] RBP: ea053cf0 R08:  R09: 

  [ 1191.077722] R10:  R11:  R12: 
97dc75673c00
  [ 1191.079681] R13: a64e0005a048 R14: a64e03053d34 R15: 
0001
  [ 1191.081636] FS:  7fd4a2ffd640() GS:97df6fc8() 
knlGS:
  [ 1191.083866] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1191.085455] CR2: ea053c70 CR3: 00019ff80001 CR4: 
00370ee0
  [ 1191.087405] Call Trace:
  [ 1191.088121]  
  [ 1191.088745]  ? show_regs+0x6a/0x80
  [ 1191.089710]  ? __die+0x25/0x70
  [ 1191.090591]  ? page_fault_oops+0x79/0x180
  [ 1191.091708]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.093027]  ? search_exception_tables+0x61/0x70
  [ 1191.094421]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.095686]  ? kernelmode_fixup_or_oops+0xa2/0x120
  [ 1191.097014]  ? __bad_area_nosemaphore+0x16f/0x280
  [ 1191.098323]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.099584]  ? apparmor_file_alloc_security+0x1f/0xd0
  [ 1191.100989]  ? bad_area_nosemaphore+0x16/0x20
  [ 1191.102235]  ? do_kern_addr_fault+0x62/0x80
  [ 1191.103393]  ? exc_page_fault+0xd8/0x160
  [ 1191.104505]  ? asm_exc_page_fault+0x27/0x30
  [ 1191.105669]  ? bpf_test_run+0x104/0x2e0
  [ 1191.106745]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.108010]  ? bpf_prog_test_run_skb+0x2e4/0x4f0
  [ 1191.109350]  ? __fdget+0x13/0x20
  [ 1191.110304]  ? __sys_bpf+0x706/0xea0
  [ 1191.111299]  ? __x64_sys_bpf+0x1a/0x30
  [ 1191.112307]  ? do_syscall_64+0x5c/0x90
  [ 1191.113366]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.114634]  ? exit_to_user_mode_loop+0xec/0x160
  [ 1191.115929]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.117466]  ? __set_task_blocked+0x29/0x70
  [ 1191.118904]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.120482]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.122073]  ? sigprocmask+0xb8/0xe0
  [ 1191.123360]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.124868]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.126523]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.128028]  ? syscall_exit_to_user_mode+0x27/0x40
  [ 1191.129599]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.131033]  ? do_syscall_64+0x69/0x90
  [ 1191.132242]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.134199]  ? do_syscall_64+0x69/0x90
  [ 1191.135504]  ? entry_SYSCALL_64_after_hwframe+0x73/0xdd
  [ 1191.137137]  
  [ 1191.137942] Modules linked in: nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp 
llc xt_tcpudp tls xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink overlay nvme_fabrics 
udf crc_itu_t binfmt_misc nls_iso8859_1 kvm_amd ccp joydev kvm hid_generic 
irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd hyperv_drm 
drm_kms_helper syscopyarea sysfillrect serio_raw sysimgblt drm_shmem_helper 
hid_hyperv hv_netvsc hid hyperv_keyboard pata_acpi dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua sch_fq_codel drm efi_pstore i2c_core ip_tables 
x_tables autofs4
  [ 1191.156484] CR2: ea053c70
  [ 1191.158026] ---[ end trace  ]---
  [ 1191.159518] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.160912] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30

[Kernel-packages] [Bug 2045778] Re: panic due to unhandled page fault via BPF_PROG_RUN syscall

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045778/+attachment/5727444/+files/uname-a.log

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

Title:
  panic due to unhandled page fault via BPF_PROG_RUN syscall

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  Here is a kernel oops triggered from user space by invoking a BPF
  program:

  [ 1191.051531] BUG: unable to handle page fault for address: ea053c70
  [ 1191.053848] #PF: supervisor read access in kernel mode
  [ 1191.055183] #PF: error_code(0x) - not-present page
  [ 1191.056513] PGD 334e15067 P4D 334e15067 PUD 334e17067 PMD 0 
  [ 1191.058016] Oops:  [#1] SMP NOPTI
  [ 1191.058984] CPU: 1 PID: 2557 Comm: ebpf.test Not tainted 6.2.0-1016-azure 
#16~22.04.1-Ubuntu
  [ 1191.061167] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
  [ 1191.063804] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.065064] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
  [ 1191.069766] RSP: 0018:a64e03053c50 EFLAGS: 00010246
  [ 1191.071117] RAX: 0001 RBX: a64e0005a000 RCX: 
a64e03053c3f
  [ 1191.073415] RDX: 0001 RSI: a64e03053c3f RDI: 
8a468580
  [ 1191.075351] RBP: ea053cf0 R08:  R09: 

  [ 1191.077722] R10:  R11:  R12: 
97dc75673c00
  [ 1191.079681] R13: a64e0005a048 R14: a64e03053d34 R15: 
0001
  [ 1191.081636] FS:  7fd4a2ffd640() GS:97df6fc8() 
knlGS:
  [ 1191.083866] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1191.085455] CR2: ea053c70 CR3: 00019ff80001 CR4: 
00370ee0
  [ 1191.087405] Call Trace:
  [ 1191.088121]  
  [ 1191.088745]  ? show_regs+0x6a/0x80
  [ 1191.089710]  ? __die+0x25/0x70
  [ 1191.090591]  ? page_fault_oops+0x79/0x180
  [ 1191.091708]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.093027]  ? search_exception_tables+0x61/0x70
  [ 1191.094421]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.095686]  ? kernelmode_fixup_or_oops+0xa2/0x120
  [ 1191.097014]  ? __bad_area_nosemaphore+0x16f/0x280
  [ 1191.098323]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.099584]  ? apparmor_file_alloc_security+0x1f/0xd0
  [ 1191.100989]  ? bad_area_nosemaphore+0x16/0x20
  [ 1191.102235]  ? do_kern_addr_fault+0x62/0x80
  [ 1191.103393]  ? exc_page_fault+0xd8/0x160
  [ 1191.104505]  ? asm_exc_page_fault+0x27/0x30
  [ 1191.105669]  ? bpf_test_run+0x104/0x2e0
  [ 1191.106745]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.108010]  ? bpf_prog_test_run_skb+0x2e4/0x4f0
  [ 1191.109350]  ? __fdget+0x13/0x20
  [ 1191.110304]  ? __sys_bpf+0x706/0xea0
  [ 1191.111299]  ? __x64_sys_bpf+0x1a/0x30
  [ 1191.112307]  ? do_syscall_64+0x5c/0x90
  [ 1191.113366]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.114634]  ? exit_to_user_mode_loop+0xec/0x160
  [ 1191.115929]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.117466]  ? __set_task_blocked+0x29/0x70
  [ 1191.118904]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.120482]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.122073]  ? sigprocmask+0xb8/0xe0
  [ 1191.123360]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.124868]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.126523]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.128028]  ? syscall_exit_to_user_mode+0x27/0x40
  [ 1191.129599]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.131033]  ? do_syscall_64+0x69/0x90
  [ 1191.132242]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.134199]  ? do_syscall_64+0x69/0x90
  [ 1191.135504]  ? entry_SYSCALL_64_after_hwframe+0x73/0xdd
  [ 1191.137137]  
  [ 1191.137942] Modules linked in: nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp 
llc xt_tcpudp tls xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink overlay nvme_fabrics 
udf crc_itu_t binfmt_misc nls_iso8859_1 kvm_amd ccp joydev kvm hid_generic 
irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd hyperv_drm 
drm_kms_helper syscopyarea sysfillrect serio_raw sysimgblt drm_shmem_helper 
hid_hyperv hv_netvsc hid hyperv_keyboard pata_acpi dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua sch_fq_codel drm efi_pstore i2c_core ip_tables 
x_tables autofs4
  [ 1191.156484] CR2: ea053c70
  [ 1191.158026] ---[ end trace  ]---
  [ 1191.159518] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.160912] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89

[Kernel-packages] [Bug 2045778] Re: panic due to unhandled page fault via BPF_PROG_RUN syscall

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045778/+attachment/5727443/+files/version.log

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

Title:
  panic due to unhandled page fault via BPF_PROG_RUN syscall

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  Here is a kernel oops triggered from user space by invoking a BPF
  program:

  [ 1191.051531] BUG: unable to handle page fault for address: ea053c70
  [ 1191.053848] #PF: supervisor read access in kernel mode
  [ 1191.055183] #PF: error_code(0x) - not-present page
  [ 1191.056513] PGD 334e15067 P4D 334e15067 PUD 334e17067 PMD 0 
  [ 1191.058016] Oops:  [#1] SMP NOPTI
  [ 1191.058984] CPU: 1 PID: 2557 Comm: ebpf.test Not tainted 6.2.0-1016-azure 
#16~22.04.1-Ubuntu
  [ 1191.061167] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
  [ 1191.063804] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.065064] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
  [ 1191.069766] RSP: 0018:a64e03053c50 EFLAGS: 00010246
  [ 1191.071117] RAX: 0001 RBX: a64e0005a000 RCX: 
a64e03053c3f
  [ 1191.073415] RDX: 0001 RSI: a64e03053c3f RDI: 
8a468580
  [ 1191.075351] RBP: ea053cf0 R08:  R09: 

  [ 1191.077722] R10:  R11:  R12: 
97dc75673c00
  [ 1191.079681] R13: a64e0005a048 R14: a64e03053d34 R15: 
0001
  [ 1191.081636] FS:  7fd4a2ffd640() GS:97df6fc8() 
knlGS:
  [ 1191.083866] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1191.085455] CR2: ea053c70 CR3: 00019ff80001 CR4: 
00370ee0
  [ 1191.087405] Call Trace:
  [ 1191.088121]  
  [ 1191.088745]  ? show_regs+0x6a/0x80
  [ 1191.089710]  ? __die+0x25/0x70
  [ 1191.090591]  ? page_fault_oops+0x79/0x180
  [ 1191.091708]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.093027]  ? search_exception_tables+0x61/0x70
  [ 1191.094421]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.095686]  ? kernelmode_fixup_or_oops+0xa2/0x120
  [ 1191.097014]  ? __bad_area_nosemaphore+0x16f/0x280
  [ 1191.098323]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.099584]  ? apparmor_file_alloc_security+0x1f/0xd0
  [ 1191.100989]  ? bad_area_nosemaphore+0x16/0x20
  [ 1191.102235]  ? do_kern_addr_fault+0x62/0x80
  [ 1191.103393]  ? exc_page_fault+0xd8/0x160
  [ 1191.104505]  ? asm_exc_page_fault+0x27/0x30
  [ 1191.105669]  ? bpf_test_run+0x104/0x2e0
  [ 1191.106745]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.108010]  ? bpf_prog_test_run_skb+0x2e4/0x4f0
  [ 1191.109350]  ? __fdget+0x13/0x20
  [ 1191.110304]  ? __sys_bpf+0x706/0xea0
  [ 1191.111299]  ? __x64_sys_bpf+0x1a/0x30
  [ 1191.112307]  ? do_syscall_64+0x5c/0x90
  [ 1191.113366]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.114634]  ? exit_to_user_mode_loop+0xec/0x160
  [ 1191.115929]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.117466]  ? __set_task_blocked+0x29/0x70
  [ 1191.118904]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.120482]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.122073]  ? sigprocmask+0xb8/0xe0
  [ 1191.123360]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.124868]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.126523]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.128028]  ? syscall_exit_to_user_mode+0x27/0x40
  [ 1191.129599]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.131033]  ? do_syscall_64+0x69/0x90
  [ 1191.132242]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.134199]  ? do_syscall_64+0x69/0x90
  [ 1191.135504]  ? entry_SYSCALL_64_after_hwframe+0x73/0xdd
  [ 1191.137137]  
  [ 1191.137942] Modules linked in: nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp 
llc xt_tcpudp tls xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink overlay nvme_fabrics 
udf crc_itu_t binfmt_misc nls_iso8859_1 kvm_amd ccp joydev kvm hid_generic 
irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd hyperv_drm 
drm_kms_helper syscopyarea sysfillrect serio_raw sysimgblt drm_shmem_helper 
hid_hyperv hv_netvsc hid hyperv_keyboard pata_acpi dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua sch_fq_codel drm efi_pstore i2c_core ip_tables 
x_tables autofs4
  [ 1191.156484] CR2: ea053c70
  [ 1191.158026] ---[ end trace  ]---
  [ 1191.159518] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.160912] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89

[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final

This bug was fixed in the package zfs-linux - 2.2.0-0ubuntu1~23.10

---
zfs-linux (2.2.0-0ubuntu1~23.10) mantic; urgency=medium

  * New upstream release. LP: #2040181
- drop patches applied upstream
- fix potential data loss
- upgrade to 2.2.0 final
- adjust symbols

 -- Dimitri John Ledkov   Tue, 24 Oct 2023
13:25:21 +0100

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

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

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Mantic:
  Fix Released
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
  32949f2560 Relax error reporting in zpool import and zpool split
  63159e5bda checkstyle: fix action failures
  e99e684b33 zed: update zed.d/statechange-slot_off.sh
  d19304ffee zed: Add zedlet to power off slot when drive is faulted
  92f095a903 copy_file_range: fix fallback when source create on same txg
  895cb689d3 zfs_clone_range should return a descriptive error codes
  6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
  df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
  0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
  bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
  c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux 
<5.3
  12f2b1f65e zdb: include cloned blocks in block statistics

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


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

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

2023-12-08 Thread JS

One independent report
(https://forums.linuxmint.com/viewtopic.php?p=2404622#p2404622) and my
own observation (incl. reverting above mentioned workaround) indicate
that the issue might be resolved in 5.15.0-91.

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 
3: 1000 4: 794
  5: 796 6: 3156 7: 799 8: 758 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 
v: kernel ports:
  active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI 
driver: nvidia
  v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 
10de:1d10
Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 
chip-ID: 0408:a030
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm 
(27")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 
23.0.4-0ubuntu1~22.04.1
  direct render: Yes
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
v: kernel pcie:
  speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
IF: wlp3s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Acer Incorporated ALI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 
04:00.1
  chip-ID: 10ec:8168
IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
Local Storage: total: 1.36 TiB used: 143.29 GiB (10.3%)
ID-1: /dev/sda model: SD Ultra 3D 1TB size: 931.51 GiB speed: 6.0 Gb/s 
serial: 
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB 
speed: 6.0 Gb/s
  serial: 
  Partition:
ID-1: / size: 915.32 GiB used: 143.28 GiB (15.7%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
  Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: 
/swapfile
  Sensors:
System Temperatures: cpu: 48.0 C pch: 37.0 C mobo: N/A
Fan Speeds (RPM): N/A
  Repos:
Packages: 3240 apt: 3217 flatpak: 23
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-jammy.list
  1: deb [signed-by=/etc/apt/keyrings/audio-recorder-ppa-jammy.gpg] https: 
//ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu jammy main
Active apt repos in: 
/etc/apt/sources.list.d/o

[Kernel-packages] [Bug 2045958] [NEW] Avoid using damage rectangle under hardware rotation mode when PSR is enabled

2023-12-08 Thread Kai-Heng Feng

Public bug reported:

[Impact]
When hardware rotation feature is used by compositor, the clip damage on cursor 
plane causes screen glitches on AMD platforms with PSR panel.

[Fix]
Disable clip damage when hardware rotation is used.

[Test]
With the patch applied, the issue can't be observed when the screen is rotated 
180 degree.
90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

[Where problems could occur]
The power consumption in theory will higher for 180 degree rotation because now 
the full screen may need to be redrawn when cursor moves.

** Affects: linux (Ubuntu)
 Importance: Low
 Status: Confirmed

** Affects: linux-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.5 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Low
 Status: Confirmed

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Low
 Status: Confirmed

** Affects: linux (Ubuntu Lunar)
 Importance: Low
 Status: Confirmed

** Affects: linux-oem-6.1 (Ubuntu Lunar)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.5 (Ubuntu Lunar)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Mantic)
 Importance: Low
 Status: Confirmed

** Affects: linux-oem-6.1 (Ubuntu Mantic)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.5 (Ubuntu Mantic)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Noble)
 Importance: Low
 Status: Confirmed

** Affects: linux-oem-6.1 (Ubuntu Noble)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.5 (Ubuntu Noble)
 Importance: Undecided
 Status: Invalid

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Importance: Undecided => Low

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

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

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:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when ha

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

2023-12-08 Thread Timo Aaltonen

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

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

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

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

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


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

[Kernel-packages] [Bug 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

2023-12-08 Thread Hui Wang

** Description changed:

+ [Impact]
+ To support HP stella's latest machine, we need to backport some new PCIIDs 
and corresponding drivers to our OEM kernel, the requirement is here:
+ 
https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508
+ 
+ This pull-request is to unitfy and add some audio controller's ID, but
+ to do so, need to apply some depending patches otherwise it will have
+ conflict to introduce the new ID and new driver to OEM kernel.
+ 
+ unified PCIIDs:
+ PCI_DEVICE_ID_INTEL_HDA_ADL_N
+ PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
+ PCI_DEVICE_ID_INTEL_HDA_ADL_P
+ PCI_DEVICE_ID_INTEL_HDA_RPL_S
+ PCI_DEVICE_ID_INTEL_HDA_MTL
+ 
+ new added PCIID:
+ PCI_DEVICE_ID_INTEL_HDA_ARL_S
+ 
+ [Fix]
+ This add the audio driver for machines with Intel Arrowlake.
+ 
+ [Test case]
+ Boot the patched kernel on a Arrowlake machine, the audio function could 
work. Boot the patches kernel on non-Arrowlake machines, the audio function 
could work as well as before.
+ 
+ [Where problems could occur]
+ Could lose some pciids and make the auido driver not work on those machines, 
and could not play sound or record sound. But this possibility is very low, I 
checked each patch carefully and I verify the patcheset on some lenovo an dell 
machines.
+ 
  From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based 
on it, added new PCIID and audio support for arrowlake-s, need to backport them 
to oem-6.5, this is a preparation for supporting HP latest laptops:
  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL
  
  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

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

Title:
  Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

Status in linux package in Ubuntu:
  New
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:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  To support HP stella's latest machine, we need to backport some new PCIIDs 
and corresponding drivers to our OEM kernel, the requirement is here:
  
https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508

  This pull-request is to unitfy and add some audio controller's ID, but
  to do so, need to apply some depending patches otherwise it will have
  conflict to introduce the new ID and new driver to OEM kernel.

  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

  [Fix]
  This add the audio driver for machines with Intel Arrowlake.

  [Test case]
  Boot the patched kernel on a Arrowlake machine, the audio function could 
work. Boot the patches kernel on non-Arrowlake machines, the audio function 
could work as well as before.

  [Where problems could occur]
  Could lose some pciids and make the auido driver not work on those machines, 
and could not play sound or record sound. But this possibility is very low, I 
checked each patch carefully and I verify the patcheset on some lenovo an dell 
machines.

  From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based 
on it, added new PCIID and audio support for arrowlake-s, need to backport them 
to oem-6.5, this is a preparation for supporting HP latest laptops:
  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

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


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

[Kernel-packages] [Bug 2043136] Re: Bluetooth prpblem

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

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

Title:
  Bluetooth prpblem

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

Bug description:
  It is always disconnected, I tried with Shell and Blueman, but both
  are not good.

  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 22:42:12 2023
  InstallationDate: Installed on 2023-08-10 (90 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/2043136/+subscriptions


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

[Kernel-packages] [Bug 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

2023-12-08 Thread Timo Aaltonen

please update the description with the sru information

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

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

Title:
  Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

Status in linux package in Ubuntu:
  New
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:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based 
on it, added new PCIID and audio support for arrowlake-s, need to backport them 
to oem-6.5, this is a preparation for supporting HP latest laptops:
  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

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


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

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

** Description changed:

The GpuWatchdog can segfault when using apps that use Electron
(https://www.electronjs.org/) which uses the Chromium Embedded Framework
- (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur
- in Chrome and Brave.
+ (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash
+ can occur in Chrome and Brave.

In my specific case this occurs when I have switched off my monitor and
left the computer go idle for a while (I don't know the timings exactly
and I don't know how to force the situation). The computer remains
responsive until I log back in from the Mate lock screen [note: if I
lock my screen I get the light-locker log-in so I do not know what
causes the machine to choose the Mate lock screen].

Upon logging back in the system becomes unresponsive. I can access the
machine over SSH and force a reboot. The segfault in GpuWatchdog appears
immediately on logging back in.

For me, this first appears to have occured on Dec 2.

Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc77192336 sp 7efc6b9fd370 error 6 in
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d
7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41
5d 41 5e

I can find no earlier entry in the syslog. My apt history shows nothing
obvious but I'll attach it anyway.

This GpuWatchdog segfault in libcef.so seems to occur a surprising
amount around the Internet but the trigger seems to vary. Nonetheless
CEF shouldn't be causing systems to become unresponsive. It is possible
(probable) there is a bug in the CEF, but equally it should not be able
to make a system unresponsive unless there is a bug in the kernel or X –
this occurs on all kinds of systems with all kinds of graphics so the
graphics driver seems an unlikely cause. It is not unique to Ubuntu but
I don't know where to start given all the possible components.

The only bug reported kernel bug was closed as not enough information was
supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129

This has been reported for Ubuntu a number of times but I thought it best to
start fresh:

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124

https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399

https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault

https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch
user" and log back in.
xset dpms force off then wake the screen up.

Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm
not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

** Description changed:

The GpuWatchdog can segfault when using apps that use Electron
(https://www.electronjs.org/) which uses the Chromium Embedded Framework
(CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash
can occur in Chrome and Brave.

In my specific case this occurs when I have switched off my monitor and
left the computer go idle for a while (I don't know the timings exactly
and I don't know how to force the

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

To make Electron aware:
https://github.com/electron/electron/issues/40732

** Bug watch added: github.com/electron/electron/issues #40732
   https://github.com/electron/electron/issues/40732

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

** Attachment added: "apt history.log.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+attachment/5727428/+files/history.log.1.gz

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same
  crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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


-- 
Mail

[Kernel-packages] [Bug 2045951] [NEW] GpuWatchdog segfault in libcef.so