[Kernel-packages] [Bug 2038743] Re: No sound from ALC236 upon warm boot

2024-01-10 Thread Joseph Sible
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037005 contained
commit 69ea4c9d02b7 ("ALSA: hda/realtek - remove 3k pull low
procedure"), and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039110 contained
commit 46cdff2369cb ("ALSA: hda/realtek - Remodified 3k pull low
procedure").

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

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

Title:
  No sound from ALC236 upon warm boot

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Fix Released

Bug description:
  On an HP 15z-fc000 laptop with Realtek ALC236 audio, on Ubuntu 22.04.3
  with HWE kernel 6.2.0-34-generic, after doing a warm boot (i.e.,
  "Restart" from the menu" or "sudo reboot"), no sound will be able to
  play. Doing a cold boot (i.e., "Power Off" or "sudo poweroff" and then
  pressing the power button to turn it back on) will make it start
  working again.

  This bug is a regression caused by commit 5aec98913095 ("ALSA:
  hda/realtek - ALC236 headset MIC recording issue").

  I've already worked with upstream to get a fix for this bug into the
  mainline kernel, which has since landed as commit 69ea4c9d02b7 ("ALSA:
  hda/realtek - remove 3k pull low procedure"), with commit 46cdff2369cb
  ("ALSA: hda/realtek - Remodified 3k pull low procedure") as a follow-
  up. To fix this bug, those two commits just need to be cherry-picked
  into Ubuntu's kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 21:12:27 2023
  InstallationDate: Installed on 2023-10-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/2038743/+subscriptions


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-94.104)

2024-01-10 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-restricted-modules 
(5.15.0-94.104) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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


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

2024-01-10 Thread You-Sheng Yang
This pulls following commits as well due to dependency:

$ git show d1dc30480fef478b06827a428970ef5d763ed76e
commit d1dc30480fef478b06827a428970ef5d763ed76e
Author: Kalle Valo 
Date:   Wed Apr 5 15:56:21 2023 +0300

ath11k: WCN6855 hw2.0: update board-2.bin

Signed-off-by: Kalle Valo 

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

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

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

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

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

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

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

Bug description:
  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.

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


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


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

2024-01-10 Thread You-Sheng Yang
Public bug reported:

Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:

1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.

In certain caes, the WIFI link training failed while system resumes from
suspend.

This can be reproduced with suspend/resume stress test.

$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated

The proposed fixes are:

* 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
  - This FW include this LP ticket issue fix
* 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
  - The FW is to support new China regulatory support.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-2046433 somerville

** Description changed:

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:
  
  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.
  
  In certain caes, the WIFI link training failed while system resumes from
  suspend.
  
  This can be reproduced with suspend/resume stress test.
  
  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated
+ 
+ The proposed fixes are:
+ 
+ * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
+   - This FW include this LP ticket issue fix
+ * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
+   - The FW is to support new China regulatory support.

** Tags added: oem-priority originate-from-2046433 somerville

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

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.

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


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


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

2024-01-10 Thread Ian May
Public bug reported:

When running an SVA case, the following soft lockup is triggered:

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


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

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

Title:
  Fix soft lockup triggered by arm_smmu_mm_invalidate_range

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

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

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


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


[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

2024-01-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-94.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


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


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


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

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

Title:
  [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

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

Bug description:
  [Impact]
  Description of problem:

  Observed device_dax related probe errors in dmesg when HBM CPU is set
  to flat mode.  Duplicate device_dax ids were created and hence probing
  is failing.

  How reproducible:
  Frequently

  Version-Release
  Release:22.04.2, 22.10

  [Test Case]

  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.

  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.

  Expected results:
  Dummy/duplicate devices should not create.

  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/

  
  [Where problems could occur]

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2

  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].

  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"devdax" ---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    }
  ]
  root@ubuntu:/home/ubuntu# dmesg | grep -i error
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748902] device_dax: probe of dax3.0 failed with error -16

  After reconfig-device devdax to system-ram below are the results:
  ---
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
  {
    "chardev":"dax0.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":2,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
  {
    "chardev":"dax1.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":3,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax4.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  

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

2024-01-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-94.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


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


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


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

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

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

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

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

  [ Where problems could occur ]

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

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

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


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


[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263

2024-01-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-94.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


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


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


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

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

Title:
  Add ODM driver rtc-pcf85263

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

Bug description:
  From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:43:41 +0100
  Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385

  
  [ Impact ]
  rtc-pcf85263 driver needed for ODM partner

  [ Test Plan ]

  Load the driver setting the timestamp level to 0 (default to 1) :
  modprobe rtc-pcf85263 tsl=0

  export the rtc device:
  echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device

  RTC device should act as a standard RTC,
  hwclock -r -f /dev/rtc1 #for reading
  hwclock -w -f /dev/rtc1 #for writing

  This driver has anti-tampering function.
  Get the current tamper timestamp:
  cat /sys/class/rtc/rtc1/device/timestamp1

  unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the 
anti-tampering goes in open state.
  The timestamp should be updated to the current time.

  [ Where problems could occur ]

  Events could occur on the I2C bus communication.

  [ Other Info ]

  X-HWE-Bug: Bug #2046985

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


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


[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can

2024-01-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-94.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


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


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


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

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

Title:
  Add ODM driver f81604 usb-can

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

Bug description:
  From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:46:08 +0100
  Subject: [PATCH 3/3] Add f81604 usb-can kernel driver

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387

  [ Impact ]
  f81604  driver needed for ODM partner

  [ Test Plan ]

  Install can-utils

  apt install can-utils

  insert the driver:
  modprobe f81604

  two socket can interfaces will be created, can0 and can1

  connect the DB9 cable and termination provided.
  Set up the two interfaces:
  ip link set can1 up type can bitrate 50
  ip link set can1 up type can bitrate 50
  candump can0

  In another shell run:
  cansend can1 123#DEADBEEF

  The first shell should report the received frame. Switch the
  interfaces in the last commands to test the frame flow in the other
  way around.

  [ Where problems could occur ]
  USB bus miss-behavior could cause issues to the driver.

  [ Other Info ]

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


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


[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan

2024-01-10 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-94.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


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


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


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

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

Title:
  Add ODM driver gpio-m058ssan

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

Bug description:
  From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:45:07 +0100
  Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386

  [ Impact ]
  gpio-m058ssan driver needed for ODM partner

  [ Test Plan ]

  Connect the loopback GPIO connector to the ReliaCOR-40-13 system and
  connect the power supply of the GPIO connector.

  insert the "m058ssan" module:
  modprobe m058ssan

  create GPIOchip:
  echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device

  get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs ,
  the latter 8 are GPIs.

  Set and reset all of the GPOs one at a time and check that the
  corresponding GPI is set and reset accordingly.

  [ Where problems could occur ]

  Make sure that the power supply of the GPIO connector is correctly connected, 
otherwise the GPI will always report 0.
  Events could occur on the i2c bus communication that may cause miss-behavior 
of the driver.

  [ Other Info ]

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


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


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

2024-01-10 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.15.0.93.90) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

diffoscope/205 (armhf)
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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


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

2024-01-10 Thread Chris Halse Rogers
Additionally: my understanding is that the corruption fix is minimally
invasive and should be easy to backport. Should we quickly do such a
minimal backport to get that fix out quickly, and then have less
pressure to handle the hardware enablement kernel quickly?

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

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 2042075] Re: Black screen at login after updating to this kernel

2024-01-10 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Black screen at login after updating to this kernel

Status in linux package in Ubuntu:
  Expired

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

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

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

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

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

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

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

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

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


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


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

2024-01-10 Thread Daniel van Vugt
Sounds like it was fixed in kernels 6.6 and 6.5.4

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

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

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

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

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

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

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

  - For graphics I have AMD 6600XT

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

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

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


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


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

2024-01-10 Thread Daniel van Vugt
See also:
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
https://gitlab.freedesktop.org/drm/amd/-/issues/1513

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

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

** Tags added: amdgpu

** No longer affects: mutter (Ubuntu)

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

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

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

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

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

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

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

  - For graphics I have AMD 6600XT

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

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

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


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


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

2024-01-10 Thread Daniel van Vugt
Zooming in on the cursor images in GIMP I find they do contain gradients
- both Yaru and DMZ-Black. Therefore some greyness is correct.

I think the remaining bug here is that either the kernel (amdgpu) or
mutter is under-saturating the cursor plane with an alpha component
below 1.0. That's why I asked for drm_info because the blending is
controllable on some drivers, but seemingly not on amdgpu.

** Summary changed:

- yaru mouse cursor theme is grey instead of black
+ [amdgpu] Mouse cursor theme is grey instead of black

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

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

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

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

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

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

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

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

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

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

  - For graphics I have AMD 6600XT

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

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

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


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


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

2024-01-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

- this is a fresh install of the latest Ubuntu 24.04

- I have fully updated the debs and snaps

- my mouse cursor is grey when it should be black

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

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

- For graphics I have AMD 6600XT


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

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

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


** Tags: amd64 apport-bug jammy wayland-session
-- 
[amdgpu] Mouse cursor theme is grey instead of black
https://bugs.launchpad.net/bugs/2048827
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.2 in Ubuntu.

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


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

2024-01-10 Thread Daniel van Vugt
> Force pushing my local commits over, sorry not sorry. :)

Yeah it's fine this time. :)

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
I was able to find one single line that syslog server was able to catch:
[ 353.589347] BUG: kernel NULL pointer dereference, address: 0008

I guess it doesn't give a lot of information...

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


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

2024-01-10 Thread Simon Quigley
> Simon, ell already has a recent approved MIR LP: #1971738

Er, the binary packages in question don't.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


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

2024-01-10 Thread Simon Quigley
> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez

Force pushing my local commits over, sorry not sorry. :)

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


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

2024-01-10 Thread Simon Quigley
I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.

I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.

Something's up with my local setup. I'll figure it out, fix it, and
allow us to move forward here.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


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

2024-01-10 Thread Daniel van Vugt
BTW, having the previous Ubuntu version 5.71-0ubuntu3 on line 415 of the
changelog doesn't feel ideal for people wanting to read the Ubuntu
release history.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71 and merge from Debian

2024-01-10 Thread Daniel van Vugt
Ideally please open a new bug for the merge. This bug should remain Fix
Released because we're already past the point in time when it was
released to Noble.

Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez

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

** Summary changed:

- BlueZ release 5.71 and merge from Debian
+ BlueZ release 5.71

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71 and merge from Debian

2024-01-10 Thread Jeremy Bícha
Simon, ell already has a recent approved MIR LP: #1971738

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738249/+files/dmesg.txt

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
** Attachment added: "lsb_release.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738250/+files/lsb_release.txt

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71 and merge from Debian

2024-01-10 Thread Simon Quigley
At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:

```
$ check-mir
Checking support status of build dependencies...
 * debhelper-compat does not exist (pure virtual?)
 * libell-dev binary and source package is in universe
 * check binary and source package is in universe

Checking support status of binary dependencies...
 * default-dbus-system-bus does not exist (pure virtual?)
  ... alternative dbus-system-bus does not exist (pure virtual?)

Please check https://wiki.ubuntu.com/MainInclusionProcess if this source 
package needs to get into in main/restricted, or reconsider if the package 
really needs above dependencies.
```

I'm going to fix check-mir itself so it ignores debhelper-compat (that
is certainly a false flag since debhelper is in main, and I don't want
to see anyone waste time on this red herring), `libell-dev` and `check`
are valid points. Both of those seem like reasonably small libraries
that could be MIRed, especially ell for embedded devices. That being
said, we did not have these dependencies before, so this is much lower
on my priority list. I would highly encourage someone to beat me to it.

That being said, I've been listening to music with no issue with the
updated bluez, which is what I would expect to be the baseline for a
"working" bluez. The only quirk I noticed is that despite my device
(Beats Flex) being set to autoconnect, I needed to manually connect (to
the already saved device). Connected promptly, no stuttering issues
(from YouTube Music/Firefox Nightly snap), audio is as good/loud as I
would expect it to be, and volume control works smoothly. I'm not
noticing anything particularly different on the blueman configuration
front.

tl;dr: Uploaded Gianfranco's diff to Noble with slight modifications.
This will need to go through binary NEW.

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
** Attachment added: "dmidecode.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738246/+files/dmidecode.txt

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738247/+files/lspci.txt

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738248/+files/lsusb.txt

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


[Kernel-packages] [Bug 2048951] [NEW] NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

2024-01-10 Thread Pavel Malyshev
Public bug reported:

Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
I can't find anything in the journal for the previous boot it just ends without 
any error. Remote syslog server does not receive any error log from this host. 
I've tried running journalctl on the local console and wait for the hang got 
nothing.
On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
 ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
so it is definitely the new kernel.

I don't have enough time to generate report with ubuntu-bug on the new
kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
one.

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

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

Title:
  NUC12WSHi7 hangs few minutes after boot with linux-
  image-6.5.0-14-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

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


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


[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

2024-01-10 Thread Bug Watch Updater
Launchpad has imported 11 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217914.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-09-15T19:33:01+00:00 laktak wrote:

Overview:

Several users report that after upgrading from 6.4.12 to 6.5 the process
scsi_eh_1 will constantly consume >10% CPU resources. This happens most
often in VMs.

Steps to Reproduce:

- Create a VM (e.g. VMware Fusion)
- Create an SCSI disk
- Connect a virtual CD ROM (IDE)
- Boot a 6.4.12 kernel
- Boot a 6.5 kernel

Actual Results:

- no issues for the 6.4.12 kernel
- scsi_eh consumes too much CPU with the 6.5 kernel

Expected Results:

scsi_eh should not consume significant resources.

Build Date & Hardware:

Linux arch 6.5.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 06 Sep 2023 21:01:01 + 
x86_64 GNU/Linux
inside a VMware Fusion VM

Additional Builds and Platforms:

Other users were able to reproduce the error on bare metal hardware.

Additional Information:

More details can be found in this thread:
https://bbs.archlinux.org/viewtopic.php?id=288723

The users loqs and leonshaw helped to narrow it down to this commit:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea

good: 6.4.0-rc1-1-7-g152e52fb6ff1
bad: 6.4.0-rc1-1-8-g624885209f31

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.5/+bug/2048945/comments/0


On 2023-09-15T20:42:23+00:00 bvanassche wrote:

On 9/15/23 12:33, bugzilla-dae...@kernel.org wrote:
> The users loqs and leonshaw helped to narrow it down to this commit:
> 
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea

Damien, can you please take a look?

Thanks,

Bart.

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.5/+bug/2048945/comments/1


On 2023-09-15T20:55:28+00:00 loberman wrote:

On Fri, 2023-09-15 at 13:42 -0700, Bart Van Assche wrote:
> On 9/15/23 12:33, bugzilla-dae...@kernel.org wrote:
> > The users loqs and leonshaw helped to narrow it down to this
> > commit:
> > 
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea
> 
> Damien, can you please take a look?
> 
> Thanks,
> 
> Bart.
> 
I had a quick look at this and its not making sense. The only calls I
see are in the scan when the devices is added and in the re-scan.
It should not be consuming the scsi_eh thread unless some type of udev
events keeps happening.

Would be good to get some
cat /proc//stack of the scsi_eh threads if they are constantly
consuming CPUY

I will try reproduce and try figure out what is going on here.

Thanks
Laurence

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.5/+bug/2048945/comments/2


On 2023-09-15T21:06:07+00:00 loberman wrote:

Not reproducible generically for me

[root@penguin8 ~]# uname -a
Linux penguin8 6.5.0+ #2 SMP PREEMPT_DYNAMIC 

[root@penguin8 ~]# lsscsi
[0:0:0:0]diskATA  Samsung SSD 850  3B6Q  /dev/sdb 
[1:0:0:0]diskATA  Samsung SSD 850  3B6Q  /dev/sda 


USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root1649  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_0]
root1651  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_1]
root1653  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_2]
root1655  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_3]
root1668  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_4]
root1670  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_5]
root1672  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_6]
root1674  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_7]
root1866  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_8]
root1887  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_9]

root1649  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_0]
root1651  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_1]
root1653  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_2]
root1655  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_3]
root1668  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_4]
root1670  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_5]
root1672  0.0  0.0  0 0 

[Kernel-packages] [Bug 2048945] ProcInterrupts.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738224/+files/ProcInterrupts.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  

[Kernel-packages] [Bug 2048945] acpidump.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738228/+files/acpidump.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  

[Kernel-packages] [Bug 2048945] WifiSyslog.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738227/+files/WifiSyslog.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: 

[Kernel-packages] [Bug 2048945] UdevDb.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2048945/+attachment/5738226/+files/UdevDb.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  

[Kernel-packages] [Bug 2048945] CurrentDmesg.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738219/+files/CurrentDmesg.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  

[Kernel-packages] [Bug 2048945] ProcCpuinfo.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738222/+files/ProcCpuinfo.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: 

[Kernel-packages] [Bug 2048945] ProcCpuinfoMinimal.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738223/+files/ProcCpuinfoMinimal.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
 

[Kernel-packages] [Bug 2048945] ProcModules.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738225/+files/ProcModules.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: 

[Kernel-packages] [Bug 2048945] Lspci-vt.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738221/+files/Lspci-vt.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  

[Kernel-packages] [Bug 2048945] Lspci.txt

2024-01-10 Thread Andrew Reis
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2048945/+attachment/5738220/+files/Lspci.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  

[Kernel-packages] [Bug 2048945] ProcCpuinfoMinimal.txt

2024-01-10 Thread Andrew Reis
** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738218/+files/ProcCpuinfoMinimal.txt

** Description changed:

  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/
  
  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:
  
  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94
  
  root@server:~# top -d 1
  
  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem
  
  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1
  
  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  
  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
+  crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
+ IwConfig:
+  lono wireless extensions.
+  
+  eth0  no wireless extensions.
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 vmwgfxdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
+ ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
+ RelatedPackageVersions:
+  linux-restricted-modules-6.5.0-14-generic N/A
+  linux-backports-modules-6.5.0-14-generic  N/A
+  linux-firmware20220329.git681281e4-0ubuntu3.23
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  jammy
+ Uname: Linux 6.5.0-14-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 11/12/2020
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX Desktop Reference Platform
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: None
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: No Enclosure
+ dmi.chassis.version: N/A
+ dmi.ec.firmware.release: 0.0
+ dmi.modalias: 

[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

2024-01-10 Thread Andrew Reis
** Also affects: linux-aws-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Tags added: apport-collected third-party-packages

** Description changed:

  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/
  
  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:
  
  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94
  
  root@server:~# top -d 1
  
  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem
  
  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1
  
  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  
  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
+ Tags: jammy third-party-packages
+ Uname: Linux 6.5.0-14-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5738217/+files/Dependencies.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Unknown
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 

[Kernel-packages] [Bug 2048945] [NEW] scsi_eh_* process using idle CPU after upgrade to kernel 6.5

2024-01-10 Thread Andrew Reis
Public bug reported:

Possibly related to https://lkml.kernel.org/linux-
scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

Getting alerts from monitoring tools about high average CPU usage.
Machine reporting the following:

root@server:~# uptime
 17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

root@server:~# top -d 1

top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
 88 root  20   0   0  0  0 D  55.4   0.0  11275:46 scsi_eh_1

root@server:~# lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
linux-image-virtual-hwe-22.04-edge:
  Installed: 6.5.0.14.14~22.04.6
  Candidate: 6.5.0.14.14~22.04.7
  Version table:
 6.5.0.14.14~22.04.7 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 *** 6.5.0.14.14~22.04.6 100
100 /var/lib/dpkg/status
 5.15.0.25.27 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Jan 10 17:02:50 2024
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)

** Affects: kernel
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug jammy kernel-bug patch-accepted-upstream

** Bug watch added: Linux Kernel Bug Tracker #217914
   https://bugzilla.kernel.org/show_bug.cgi?id=217914

** Also affects: kernel via
   https://bugzilla.kernel.org/show_bug.cgi?id=217914
   Importance: Unknown
   Status: Unknown

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

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

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)

To manage notifications 

[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

2024-01-10 Thread Frank H
Few hours after posting I got the 6.5.0-14-generic update.
So I'll test it out for a while and see if the issue persists or if it's fixed.

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 2048942] [NEW] Openvswitch matching broken for nat packets in the related state

2024-01-10 Thread Brad Cowie
Public bug reported:

Linux kernel commit ebddb1404900 ("net: move the nat function to
nf_nat_ovs for ovs and tc") introduced a regression into the kernel
openvswitch datapath which prevented the match key from being updated
when nat was undone for packets in the related conntrack state. This
issue caused these packets (usually ICMP/ICMPv6 error packets) to
match the wrong openflow rule when processed by openvswitch.
This commit is present in Ubuntu kernel versions v6.2 and v6.5.

This issue was fixed in upstream linux kernel commit e6345d2824a3 ("netfilter:
nf_nat: fix action not being set for all ct states"). Which is included
in upstream linux kernel versions v6.7 and v6.6.11. This commit can be found
in the kernel stable tree:

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

Discussion for this patch can be found on this netdev mailing list
thread:

https://lore.kernel.org/netdev/20231221224311.130319-1-b...@faucet.nz/T/

Test cases to reproduce the bug with both the openvswitch test suite
and linux kernel self-tests can be found on the ovs-dev mailing list:

https://mail.openvswitch.org/pipermail/ovs-dev/2024-January/410476.html

Can commit e6345d2824a3 be considered for SRU in jammy-hwe, lunar and
mantic?

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

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

Title:
  Openvswitch matching broken for nat packets in the related state

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernel commit ebddb1404900 ("net: move the nat function to
  nf_nat_ovs for ovs and tc") introduced a regression into the kernel
  openvswitch datapath which prevented the match key from being updated
  when nat was undone for packets in the related conntrack state. This
  issue caused these packets (usually ICMP/ICMPv6 error packets) to
  match the wrong openflow rule when processed by openvswitch.
  This commit is present in Ubuntu kernel versions v6.2 and v6.5.

  This issue was fixed in upstream linux kernel commit e6345d2824a3 ("netfilter:
  nf_nat: fix action not being set for all ct states"). Which is included
  in upstream linux kernel versions v6.7 and v6.6.11. This commit can be found
  in the kernel stable tree:

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

  Discussion for this patch can be found on this netdev mailing list
  thread:

  https://lore.kernel.org/netdev/20231221224311.130319-1-b...@faucet.nz/T/

  Test cases to reproduce the bug with both the openvswitch test suite
  and linux kernel self-tests can be found on the ovs-dev mailing list:

  https://mail.openvswitch.org/pipermail/ovs-
  dev/2024-January/410476.html

  Can commit e6345d2824a3 be considered for SRU in jammy-hwe, lunar and
  mantic?

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


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


[Kernel-packages] [Bug 2048935] [NEW] Right speaker broken on Dell XPS 13 Plus 9320

2024-01-10 Thread Andreas Hoornstra
Public bug reported:

After upgrading from the previous HWE kernel 6.2.0-39-generic to the new
HWE kernel 6.5.0-14-generic, the right speaker no longer works. When
booting back into the old HWE kernel, the right speaker functions again.
The left speaker works in both cases.

Hardware info:
Dell XPS 13 Plus 9320 with Intel i7 1260P

Software info:
Description:Ubuntu 22.04.3 LTS
Release:22.04

Package info:
apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
  Installed: 6.5.0.14.14~22.04.7
  Candidate: 6.5.0.14.14~22.04.7
  Version table:
 *** 6.5.0.14.14~22.04.7 500
500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 5.15.0.25.27 500
500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


lspci output on kernel 6.5.0-14-generic:
```
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
Subsystem: Dell Device 0af3
Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15
Memory at 603e1d (64-bit, non-prefetchable) [size=16K]
Memory at 603e00 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: sof-audio-pci-intel-tgl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
Subsystem: Dell Device 0af3
Flags: medium devsel, IRQ 16, IOMMU group 15
Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256]
I/O ports at efa0 [size=32]
```

aplay -l output on kernel 6.5.0-14-generic:
```
 List of PLAYBACK Hardware Devices 
card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
```

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 10 21:40:02 2024
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2022-06-25 (563 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
SourcePackage: linux-meta-hwe-6.5
UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago)

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


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

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

Title:
  Right speaker broken on Dell XPS 13 Plus 9320

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

Bug description:
  After upgrading from the previous HWE kernel 6.2.0-39-generic to the
  new HWE kernel 6.5.0-14-generic, the right speaker no longer works.
  When booting back into the old HWE kernel, the right speaker functions
  again. The left speaker works in both cases.

  Hardware info:
  Dell XPS 13 Plus 9320 with Intel i7 1260P

  Software info:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package info:
  apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Installed: 6.5.0.14.14~22.04.7
Candidate: 6.5.0.14.14~22.04.7
Version table:
   *** 6.5.0.14.14~22.04.7 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  lspci output on kernel 6.5.0-14-generic:
  ```
  00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
Subsystem: Dell Device 0af3
Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15
Memory at 603e1d (64-bit, non-prefetchable) [size=16K]
Memory at 603e00 (64-bit, non-prefetchable) [size=1M]
  

[Kernel-packages] [Bug 1909005] Re: [Dell Inspiron 3593] Ubuntu does not resume (wake up) from suspend

2024-01-10 Thread Jonathan C
3 years is a long time not to fix a basic sleep problem...

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

Title:
  [Dell Inspiron 3593] Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-
  image-5.0.0-1070-oem-osp1". But with this old kernel I run into
  different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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


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


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

2024-01-10 Thread Simon Quigley
** Changed in: bluez (Ubuntu)
   Status: Fix Released => In Progress

** Summary changed:

- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian

** Changed in: bluez (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

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


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


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

2024-01-10 Thread Bilbija
Public bug reported:

driver bug while update

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

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


** Tags: amd64 apport-package jammy

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

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

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

Bug description:
  driver bug while update

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

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


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


[Kernel-packages] [Bug 2048915] Re: initrd is bloated

2024-01-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  initrd is bloated

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

Bug description:
  With the modules-extra package removed, a ton of additional modules
  are installed and lots of them end up in the initrd, blowing it up in
  size. We need to shrink it.

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


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


[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-01-10 Thread b
This issue persists on 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/2016388

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

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


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


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

2024-01-10 Thread Gianfranco Costamagna
two patches are now with Debian bugs
 Opened #1060393 in bluez 5.67-1 by Gianfranco Costamagna (locutusofborg) 
«please update patch 
work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch». 
https://bugs.debian.org/1060393
 Opened #1060395 in bluez by Gianfranco Costamagna (locutusofborg) «please 
add simple testsuite from Ubuntu». https://bugs.debian.org/1060395

** Bug watch added: Debian Bug tracker #1060393
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060393

** Bug watch added: Debian Bug tracker #1060395
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060395

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


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

2024-01-10 Thread Gianfranco Costamagna
and ell-dev needs a i386 whitelist, not sure

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2048504] Re: package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: installed linux-headers-6.2.0-39-generic package post-installation script subprocess r

2024-01-10 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to
  install/upgrade: installed linux-headers-6.2.0-39-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
   fv

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-39-generic 6.2.0-39.40
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdcir  2337 F pipewire
mdcir  2340 F wireplumber
   /dev/snd/seq:mdcir  2337 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Jan  8 09:25:27 2024
  DpkgHistoryLog:
   Start-Date: 2024-01-08  09:25:26
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.23.04.1, 
1:115.6.0+build2-0ubuntu0.23.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.23.04.1, 1:115.6.0+build2-0ubuntu0.23.04.1), 
thunderbird-locale-zh-hant:amd64 (1:115.5.0+build1-0ubuntu0.23.04.1, 
1:115.6.0+build2-0ubuntu0.23.04.1), thunderbird-locale-en-gb:amd64 
(1:115.5.0+build1-0ubuntu0.23.04.1, 1:115.6.0+build2-0ubuntu0.23.04.1), 
thunderbird-locale-en-us:amd64 (1:115.5.0+build1-0ubuntu0.23.04.1, 
1:115.6.0+build2-0ubuntu0.23.04.1), thunderbird-gnome-support:amd64 
(1:115.5.0+build1-0ubuntu0.23.04.1, 1:115.6.0+build2-0ubuntu0.23.04.1)
  ErrorMessage: installed linux-headers-6.2.0-39-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-06 (93 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. XPS 15 9530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=0a8a6779-7f01-4cb5-aa7b-2ba2d0ad4a06 ro quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to 
install/upgrade: installed linux-headers-6.2.0-39-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 01WV13
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd09/19/2023:br1.8:efr1.4:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn01WV13:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9530
  dmi.product.sku: 0BEB
  dmi.sys.vendor: Dell Inc.

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


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


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

2024-01-10 Thread bugproxy
Public bug reported:

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

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

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

that's the expected state for Ubuntu.

# current/ non expected behavior

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

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

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

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


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


# Proposed Solution:

change the kernel config to

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

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

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


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

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

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

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

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

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

Status in linux package in Ubuntu:
  New

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

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

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

  that's the expected state for Ubuntu.

  # current/ non expected behavior

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

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

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

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

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

  
  # Proposed Solution:

  change the kernel config to

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

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

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


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


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

2024-01-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

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

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

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

that's the expected state for Ubuntu.

# current/ non expected behavior

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

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

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

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


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


# Proposed Solution:

change the kernel config to

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

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

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


** Tags: architecture-s39064 bugnameltc-204559 severity-medium 
targetmilestone-inin---
-- 
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
https://bugs.launchpad.net/bugs/2048919
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 2047780] Re: BlueZ release 5.71

2024-01-10 Thread Gianfranco Costamagna
Hello, I did the merge from Debian, now the packaging is really simpler,
please have a look and upload if possible.

** Attachment added: "bluez_5.71-1ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5738106/+files/bluez_5.71-1ubuntu1.debian.tar.xz

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Kernel-packages] [Bug 2048915] Re: initrd is bloated

2024-01-10 Thread Juerg Haefliger
Yikes.

With old linux-modules:
-rw-r--r--  1 root root 29622096 Oct 11 22:55 initrd.img-6.5.0-1005-raspi

With new linux-modules:
-rw-r--r--  1 root root 61907522 Jan 10 16:54 initrd.img-6.5.0-1008-raspi

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

Title:
  initrd is bloated

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

Bug description:
  With the modules-extra package removed, a ton of additional modules
  are installed and lots of them end up in the initrd, blowing it up in
  size. We need to shrink it.

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


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


[Kernel-packages] [Bug 2048915] [NEW] initrd is bloated

2024-01-10 Thread Juerg Haefliger
Public bug reported:

With the modules-extra package removed, a ton of additional modules are
installed and lots of them end up in the initrd, blowing it up in size.
We need to shrink it.

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

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

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

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

Title:
  initrd is bloated

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

Bug description:
  With the modules-extra package removed, a ton of additional modules
  are installed and lots of them end up in the initrd, blowing it up in
  size. We need to shrink it.

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


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


[Kernel-packages] [Bug 2047590] Re: 6.5.0-14 kernel will not boot

2024-01-10 Thread Juerg Haefliger
Can you remove 'quiet' and 'splash' from the kernel commandline and
reboot into the broken kernel? That should give some console messages.

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

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

Title:
  6.5.0-14 kernel will not boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The computer hangs during boot with kernel 6.5.0-14-generic.  However,
  kernel 6.2.0-39-generic works fine.  This was a recent upgrade from an
  earlier Ubuntu version.

  I see on the screen:
  Loading Linux 6.5.014-generic...
  Loading initial ramdisk ...

  I waited several minutes before pushing the reset button.

  Other system information should be attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gsking 1759 F wireplumber
   /dev/snd/controlC1:  gsking 1759 F wireplumber
   /dev/snd/seq:gsking 1745 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 16:45:06 2023
  InstallationDate: Installed on 2023-07-03 (177 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=5a06426c-3de2-4755-be67-fdc02ccff00d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-12-05 (22 days ago)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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


[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers

2024-01-10 Thread Timo Aaltonen
uploaded, thanks

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

Title:
  [needs-packaging] usbio-drivers

Status in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in The Jammy Jellyfish:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice 
AIC
   This package provides kernel drivers for MIPI cameras through the Intel IPU6
   on Intel MeteoLake platform with Lattice AIC.

  Upstream URL: https://github.com/intel/usbio-drivers
  Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms 
(to request usd-import after created)
  License: GPL v2

  PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800.

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


-- 
Mailing list: https://launchpad.net/~kernel-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: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters

2024-01-10 Thread Andy Gospodarek
Testing looks good from our side.  When we have fixes how should we
request they are integrated?  A new launchpad bug with a list of
upstream fixes that should be backported?

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

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

Title:
  Update bnxt_en with bug fixes and support for Broadcom 5760X network
  adapters

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [IMPACT]

  This is requested by one of our larger server hardware partners and
  Broadcom to to update the bnxt_en network driver code to add some bug
  fixes and support for the newer 5760X adapters into Mantic.  The goal
  is to have these land in 22.04.4 HWE and the installer environment via
  the HWE kernel.

  Missing these patches will mean customers running this hardware will
  not be able to use it with Ubuntu Server 22.04 LTS until the much
  later 22.04.5 point release, setting up a months-long gap in support
  for these adapters.

  [FIXES]

  These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and
  pick cleanly with the exception of the two noted at the end of this
  section.  For Mantic all are picked. For Noble, only the subset
  currently in linux-next will be picked, depending on what happens in
  our Noble tree during the cycle.

  d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc
  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
  8243345bfaec bnxt_en: Refactor RSS capability fields
  d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism
  on P7 chips
  d3c16475dc06 bnxt_en: Consolidate DB offset calculation
  a432a45bdba4 bnxt_en: Define basic P7 macros
  397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15
  08b386b132c6 bnxt_en: Fix backing store V2 logic
  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
  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
  9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters
  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() 

[Kernel-packages] [Bug 2042426] Re: Introduce the new NVIDIA 545 driver series

2024-01-10 Thread Dimitri John Ledkov
** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Focal)

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

Title:
  Introduce the new NVIDIA 545 driver series

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Lunar:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Mantic:
  In Progress

Bug description:
  Introduce the new NVIDIA 545 driver series.

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


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


[Kernel-packages] [Bug 2048904] [NEW] package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to install/upgrade: »installiertes nvidia-dkms-535-Skript des Paketes post-installation«-Unterprozess g

2024-01-10 Thread Jürgen Wiesemann
Public bug reported:

it crashes after kernel update

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jan 10 15:20:57 2024
ErrorMessage: »installiertes nvidia-dkms-535-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
InstallationDate: Installed on 2022-09-25 (471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
SourcePackage: nvidia-graphics-drivers-535
Title: package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to 
install/upgrade: »installiertes nvidia-dkms-535-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

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

Bug description:
  it crashes after kernel update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 10 15:20:57 2024
  ErrorMessage: »installiertes nvidia-dkms-535-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2022-09-25 (471 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: nvidia-graphics-drivers-535
  Title: package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to 
install/upgrade: »installiertes nvidia-dkms-535-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 2028125] Re: Update the NVIDIA 535 series to 535.86.05

2024-01-10 Thread Dimitri John Ledkov
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
   Status: Triaged => Invalid

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
   Status: New => Invalid

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

Title:
  Update the NVIDIA 535 series to 535.86.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Invalid
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Invalid
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Invalid
Status in fabric-manager-535 source package in Kinetic:
  Won't Fix
Status in libnvidia-nscq-535 source package in Kinetic:
  Won't Fix
Status in nvidia-graphics-drivers-535 source package in Kinetic:
  Won't Fix
Status in nvidia-graphics-drivers-535-server source package in Kinetic:
  Won't Fix
Status in fabric-manager-535 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  Invalid

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2028125/+subscriptions


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


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

2024-01-10 Thread Valtýr Kári Daníelsson
** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048796/+attachment/5738071/+files/make.log

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

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

Status in linux package in Ubuntu:
  Triaged

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

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

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


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


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

2024-01-10 Thread Valtýr Kári Daníelsson
The previous kernel version was 6.5.0-14-generic. The full output, after
I remove all the mentioned packages and try to reinstall them, is
attached in updateoutput. I do have a dkms module installed, dkms status
outputs evdi/1.14.1, 6.5.0-14-generic, x86_64. The output from apt also
says to check /var/lib/dkms/evdi/1.14.1/build/make.log for more
information. I can't figure out how to attach more than one attachment
to a comment so I'll attach make.log in another comment

** Attachment added: "updateoutput.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048796/+attachment/5738070/+files/updateoutput.txt

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

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

Status in linux package in Ubuntu:
  Triaged

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

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

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


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


[Kernel-packages] [Bug 2048887] Re: thermald assert failure: *** stack smashing detected ***: terminated

2024-01-10 Thread Apport retracing service
*** This bug is a duplicate of bug 2036135 ***
https://bugs.launchpad.net/bugs/2036135

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2036135, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738041/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738043/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738046/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738047/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738048/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738049/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2048887/+attachment/5738050/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 2036135

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  thermald assert failure: *** stack smashing detected ***: terminated

Status in thermald package in Ubuntu:
  New

Bug description:
  installing ubuntu 24.04, I can not go past the white Installing
  screen. Nothing shows up on it.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: thermald 2.5.4-3
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** stack smashing detected ***: terminated
  CasperMD5CheckResult: unknown
  CasperVersion: 1.490
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Wed Jan 10 12:16:40 2024
  ExecutablePath: /usr/sbin/thermald
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240108)
  ProcCmdline: /usr/sbin/thermald --systemd --dbus-enable --adaptive
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: thermald
  StacktraceTop:
   __libc_message (fmt=fmt@entry=0x7b3c4a0d18d3 "*** %s ***: terminated\n") at 
../sysdeps/posix/libc_fatal.c:150
   __GI___fortify_fail (msg=msg@entry=0x7b3c4a0d18eb "stack smashing detected") 
at ./debug/fortify_fail.c:24
   __stack_chk_fail () at ./debug/stack_chk_fail.c:24
   cthd_acpi_rel::read_psvt() ()
   ?? ()
  Title: thermald assert failure: *** stack smashing detected ***: terminated
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  modified.conffile..etc.init.thermald.conf: [deleted]
  mtime.conffile..etc.thermald.thermal-cpu-cdev-order.xml: 2024-01-08T05:59:53
  separator:

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


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


[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

2024-01-10 Thread Frank H
I'm on 6.2.0-39-generic (Ubuntu 22.04) and have started to get touchpad 
problems(I believe around September 2023).
Touchpad often stops responding after having the laptop(Lenovo Yoga slim 
14ARE05) on for a while.

A full shutdown + waiting for a while and starting the laptop again
makes the touchpad work again but just a reboot doesn't fix it.

Don't think it will help but here are my journalctl logs from yesterday:

jan 09 23:18:33 codingthing kernel: i2c_designware AMDI0010:00: controller 
timed out
jan 09 23:18:32 codingthing kernel: i2c_designware AMDI0010:00: 
i2c_dw_handle_tx_abort: lost arbitration

I didn't have this in the first 2 years of usage though.


I'm unsure how to safely try other kernel versions myself so I'm really hoping 
this fix finds its way to Ubuntu 22.04 or 24.04 releases.

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2024-01-10 Thread Robert Malz
Hey @Christian,
1a) No need, AQ 0x000A returns NVM capabilities regardless of configuration 
applied (it's done during driver init)
1b) That's the point, I noticed you upgraded to 4.3 which I currently don't 
have access to and I wanted to verify capabilities on 4.3. NVM caps should be 
similar on the same NVM version in single head of family so values I had access 
to would be the same you had on 4.2 (meaning there is no point of collecting 
these)
1c) No, any "recent" kernel/driver version will support enabling debug logs by 
adding dyndbg=+p param to module. We only care for logs which are retrieved 
from NVM and printed with debug flags.

2) The issue based on recent patches from Intel is caused by performing LAG 
related operations without proper support from NVM. Release notes does not 
always tell every feature change so there is a possibility that 4.4 introduced 
sriov_lag capability but I cannot verify it.
Worst case scenario is that NVM 4.4 will introduce sriov_lag capability, 
meaning patches added recently to upstream kernel will have no effect, and also 
issue will still reproduce. In this scenario currently there will be no 
'workaround' for it.
Best case scenario is that NVM 4.4 will introduce sriov_lag capability and 
issue will no longer reproduce.
In this scenario no additional patches to the driver will be required.

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything 

[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64

2024-01-10 Thread Danilo Egea Gondolfo
Hi Dimitri, I just tried it here. The same problem is happening with
kernel 6.7 and the same workaround (disabling ASLR) works.

Example of failure:


clang++-$VERSION -O1 -g -fsanitize=address -fno-omit-frame-pointer foo.cpp
ASAN_OPTIONS=verbosity=1 ./a.out &> foo.log || true
./debian/qualify-clang.sh: line 634:  4281 Segmentation fault  (core 
dumped) ASAN_OPTIONS=verbosity=1 ./a.out &> foo.log
if ! grep -q "Init done" foo.log; then
echo "asan verbose mode failed"
cat foo.log
exit 42
fi
asan verbose mode failed
==4281==Registered root region at 0x736c74f00b70 of size 48
==4281==Registered root region at 0x736c74b007a0 of size 32
==4281==Unregistered root region at 0x736c74f00b70 of size 48
==4281==Unregistered root region at 0x736c74b007a0 of size 32
==4281==AddressSanitizer: failed to intercept '__isoc99_printf'
==4281==Registered root region at 0x736c74f00b70 of size 48
==4281==Registered root region at 0x736c74b007a0 of size 32
==4281==Unregistered root region at 0x736c74f00b70 of size 48
==4281==Unregistered root region at 0x736c74b007a0 of size 32
==4281==AddressSanitizer: failed to intercept '__isoc99_sprintf'
==4281==Registered root region at 0x736c74f00b70 of size 48
==4281==Registered root region at 0x736c74b007a0 of size 32
==4281==Unregistered root region at 0x736c74f00b70 of size 48
==4281==Unregistered root region at 0x736c74b007a0 of size 32
==4281==AddressSanitizer: failed to intercept '__isoc99_snprintf'
==4281==Registered root region at 0x736c74f00b70 of size 48
==4281==Registered root region at 0x736c74b007a0 of size 32
==4281==Unregistered root region at 0x736c74f00b70 of size 48
==4281==Unregistered root region at 0x736c74b007a0 of size 32
==4281==AddressSanitizer: failed to intercept '__isoc99_fprintf'

==4281==Unregistered root region at 0x736c74b00780 of size 32
==4281==AddressSanitizer: failed to intercept 'crypt'
==4281==Registered root region at 0x736c74f00b70 of size 48
==4281==Registered root region at 0x736c74b00780 of size 32
==4281==Unregistered root region at 0x736c74f00b70 of size 48
==4281==Unregistered root region at 0x736c74b00780 of size 32
==4281==AddressSanitizer: failed to intercept 'crypt_r'
==4281==Registered root region at 0x736c74900f40 of size 64
==4281==Registered root region at 0x736c74b00780 of size 32
==4281==Unregistered root region at 0x736c74900f40 of size 64
==4281==Unregistered root region at 0x736c74b00780 of size 32
==4281==AddressSanitizer: failed to intercept '__cxa_rethrow_primary_exception'
==4281==AddressSanitizer: libc interceptors initialized
|| `[0x10007fff8000, 0x7fff]` || HighMem||
|| `[0x02008fff7000, 0x10007fff7fff]` || HighShadow ||
|| `[0x8fff7000, 0x02008fff6fff]` || ShadowGap  ||
|| `[0x7fff8000, 0x8fff6fff]` || LowShadow  ||
|| `[0x, 0x7fff7fff]` || LowMem ||
MemToShadow(shadow): 0x8fff7000 0x91ff6dff 0x004091ff6e00 0x02008fff6fff
redzone=16
max_redzone=2048
quarantine_size_mb=256M
thread_local_quarantine_size_kb=1024K
malloc_context_size=30
SHADOW_SCALE: 3
SHADOW_GRANULARITY: 8
SHADOW_OFFSET: 0x7fff8000
==4281==Installed the sigaction for signal 11
==4281==Installed the sigaction for signal 7
==4281==Installed the sigaction for signal 8
autopkgtest [11:22:53]: test command1: ---]

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

Title:
  Autopkgtest failures on amd64

Status in linux package in Ubuntu:
  New
Status in llvm-toolchain-14 package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in llvm-toolchain-14 source package in Noble:
  New

Bug description:
  Some tests related to the address sanitizer are occasionally failing
  on amd64 (also for llvm-toolchain-15 and 16):

  --
  FAIL: LLVM regression suite :: test_leaksan.c (38 of 45)
  746s  TEST 'LLVM regression suite :: test_leaksan.c' 
FAILED 
  746s Script:
  746s --
  746s : 'RUN: at line 4';   /usr/bin/clang-14 -o 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
-fsanitize=address -g 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c
  746s : 'RUN: at line 5';   env ASAN_OPTIONS="log_path=stdout:exitcode=0"  
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s : 'RUN: at line 6';   grep -q "detected memory leaks" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s --
  746s Exit Code: 139
  746s
  746s Command Output (stderr):
  746s --
  746s 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script:
 line 3:  3335 Segmentation fault  (core dumped) env 
ASAN_OPTIONS="log_path=stdout:exitcode=0" 

[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64

2024-01-10 Thread Dimitri John Ledkov
we area bout to move to v6.7 kernel as v6.6 is sort of dead to us
already.

Are you able to test with linux-generic-wip (linux-unstable source) from
this ppa https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable?field.series_filter=noble ?

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

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

Title:
  Autopkgtest failures on amd64

Status in linux package in Ubuntu:
  New
Status in llvm-toolchain-14 package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in llvm-toolchain-14 source package in Noble:
  New

Bug description:
  Some tests related to the address sanitizer are occasionally failing
  on amd64 (also for llvm-toolchain-15 and 16):

  --
  FAIL: LLVM regression suite :: test_leaksan.c (38 of 45)
  746s  TEST 'LLVM regression suite :: test_leaksan.c' 
FAILED 
  746s Script:
  746s --
  746s : 'RUN: at line 4';   /usr/bin/clang-14 -o 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
-fsanitize=address -g 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c
  746s : 'RUN: at line 5';   env ASAN_OPTIONS="log_path=stdout:exitcode=0"  
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s : 'RUN: at line 6';   grep -q "detected memory leaks" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s --
  746s Exit Code: 139
  746s
  746s Command Output (stderr):
  746s --
  746s 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script:
 line 3:  3335 Segmentation fault  (core dumped) env 
ASAN_OPTIONS="log_path=stdout:exitcode=0" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  --

  If you run the test manually you'll notice that it works but
  eventually crashes:

  
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8631==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5e9c3441ed12 in __interceptor_malloc 
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
 (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
  #1 0x5e9c3445acb8 in main 
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
  #2 0x7e84e1e280cf  (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: 
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)

  SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8634==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5f19be5f6d12 in __interceptor_malloc 
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
 (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
  #1 0x5f19be632cb8 in main 
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
  #2 0x77c7d3c280cf  (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: 
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)

  SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).

  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp
  Segmentation fault (core dumped)
  

  After some investigation I found that it will not fail with ASLR
  disabled:

  sudo sysctl kernel.randomize_va_space=0

  while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
  ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ;
  fi done

  If you enable ASLR it will start to crash:

  $ sudo sysctl kernel.randomize_va_space=2

  $ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" 
./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed

  If you enable ASLR again and run it with "setarch -R" (to disable ASLR
  for this binary), it will also not crash.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt

2024-01-10 Thread Daniel van Vugt
** Description changed:

+ [ Workaround ]
+ 
+ 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
+ 2. Run: systemctl restart bluetooth # or reboot
+ 
+ [ Original Description ]
+ 
  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to enter
  a PIN in the device (not possible to enter a pin in the gamepad).
  
  Source pacakge (from "apt list -a bluez"):
  
  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64
  
  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.
  
  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  
  Package version:
  bluez:
-   Installed: 5.64-0ubuntu1.1
+   Installed: 5.64-0ubuntu1.1
  
  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code
  
  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

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

Title:
  ps3 sixasis controller request pin to connect to bt

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  [ Workaround ]

  1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
  2. Run: systemctl restart bluetooth # or reboot

  [ Original Description ]

  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to
  enter a PIN in the device (not possible to enter a pin in the
  gamepad).

  Source pacakge (from "apt list -a bluez"):

  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.

  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package version:
  bluez:
    Installed: 5.64-0ubuntu1.1

  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code

  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

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


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


[Kernel-packages] [Bug 2048862] [NEW] Remove linux-modules-extra

2024-01-10 Thread Juerg Haefliger
Public bug reported:

Kernel modules are zstd-compressed nowadays so there's no real reason
anymore to split the modules package. In fact that used to cause issues
and required frequent moving of modules from one package to the other.

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

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

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

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

Title:
  Remove linux-modules-extra

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

Bug description:
  Kernel modules are zstd-compressed nowadays so there's no real reason
  anymore to split the modules package. In fact that used to cause
  issues and required frequent moving of modules from one package to the
  other.

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


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


[Kernel-packages] [Bug 2048864] [NEW] Remove armhf support

2024-01-10 Thread Juerg Haefliger
Public bug reported:

Noble and newer doesn't support armhf for Pi anymore.

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

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

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

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

Title:
  Remove armhf support

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

Bug description:
  Noble and newer doesn't support armhf for Pi anymore.

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


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


[Kernel-packages] [Bug 2048861] [NEW] Make dwc2 the default

2024-01-10 Thread Juerg Haefliger
Public bug reported:

dwc_otg is really only used for armv6 Pis, which Ubuntu doesn't support,
so make dwc2 the default.

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

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

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

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

Title:
  Make dwc2 the default

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

Bug description:
  dwc_otg is really only used for armv6 Pis, which Ubuntu doesn't
  support, so make dwc2 the default.

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


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


[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B PC

2024-01-10 Thread Ivan Hu
Test B PC device withlinux/5.15.0-93.103 kernel on several displays, display 
fine. 
 

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

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

Title:
  Add quirk to disable i915 fastboot on B PC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Some displays connect to the B PC device got the garbled display

  [Fix]
  The issue will disappear after commit 
5ac860cc52540df8bca27e0bb25b6744df67e8f0,
  but these patches cannot be backported from 5.19 to 5.15. So add quirk
  to force disable the i915 fastboot on the device to fix the abnormal display

  [Test Case]
  1. Connect the display and power on the B PC device
  2. Check the display for boot up

  [Where problems could occur]
  Quirk only on the B PCs. Risk of regression is low.

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


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


[Kernel-packages] [Bug 2043542] Re: Add MT7925 WiFi/BT support

2024-01-10 Thread You-Sheng Yang
** Also affects: linux-firmware (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

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

Title:
  Add MT7925 WiFi/BT support

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

Bug description:
  * WiFi
    - kernel: 
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
  * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
  * 3c1199134874 wifi: mt76: connac: add more unified command IDs
  * 473f26fb167e wifi: mt76: connac: add data field in struct tlv
  * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
  * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
  * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
  * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
  * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
  * Bluetooth
    - kernel: 
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2

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


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


[Kernel-packages] [Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110

2024-01-10 Thread You-Sheng Yang
Commit 318c64abf touches PNVM as well:

$ git log --oneline --stat 318c64abf
318c64abf (tag: iwlwifi-fw-2023-12-21, korg-iwlwifi/for-upstream) iwlwifi: 
update gl FW for core80-165 release
 WHENCE   |   2 +-
 iwlwifi-gl-c0-fm-c0-83.ucode | Bin 1799504 -> 1797996 bytes
 iwlwifi-gl-c0-fm-c0.pnvm | Bin 226668 -> 246228 bytes
 3 files changed, 1 insertion(+), 1 deletion(-)

Which then pulls two more commits due the the modification chain of the
PNVM file:

$ git log --oneline --stat f27dec616
f27dec616 (tag: iwlwifi-fw-2023-11-16-fixed) iwlwifi: fix for the new FWs from 
core83-55 release
 iwlwifi-gl-c0-fm-c0-86.ucode  | Bin 1840116 -> 1840116 bytes
 iwlwifi-gl-c0-fm-c0.pnvm  | Bin 226668 -> 226668 bytes
 iwlwifi-ma-b0-gf-a0-86.ucode  | Bin 1695788 -> 1695788 bytes
 iwlwifi-ma-b0-gf-a0.pnvm  | Bin 55092 -> 55092 bytes
 iwlwifi-ma-b0-gf4-a0-86.ucode | Bin 1670940 -> 1670940 bytes
 iwlwifi-ma-b0-gf4-a0.pnvm | Bin 27820 -> 27820 bytes
 iwlwifi-ma-b0-hr-b0-86.ucode  | Bin 1520636 -> 1520636 bytes
 iwlwifi-so-a0-gf-a0-86.ucode  | Bin 1679788 -> 1679788 bytes
 iwlwifi-so-a0-gf-a0.pnvm  | Bin 55172 -> 55172 bytes
 iwlwifi-so-a0-gf4-a0-86.ucode | Bin 1653836 -> 1653836 bytes
 iwlwifi-so-a0-gf4-a0.pnvm | Bin 27860 -> 27860 bytes
 iwlwifi-so-a0-hr-b0-86.ucode  | Bin 1507388 -> 1507388 bytes
 iwlwifi-ty-a0-gf-a0-86.ucode  | Bin 1632464 -> 1632464 bytes
 iwlwifi-ty-a0-gf-a0.pnvm  | Bin 55020 -> 55020 bytes
 14 files changed, 0 insertions(+), 0 deletions(-)

$ git log --oneline --stat a07fd0b96
a07fd0b96 (tag: iwlwifi-fw-2023-11-15) iwlwifi: add new FWs from core83-55 
release
 WHENCE|  24 
 iwlwifi-gl-c0-fm-c0-86.ucode  | Bin 0 -> 1840116 bytes
 iwlwifi-gl-c0-fm-c0.pnvm  | Bin 246228 -> 226668 bytes
 iwlwifi-ma-b0-gf-a0-86.ucode  | Bin 0 -> 1695788 bytes
 iwlwifi-ma-b0-gf-a0.pnvm  | Bin 55500 -> 55092 bytes
 iwlwifi-ma-b0-gf4-a0-86.ucode | Bin 0 -> 1670940 bytes
 iwlwifi-ma-b0-gf4-a0.pnvm | Bin 28024 -> 27820 bytes
 iwlwifi-ma-b0-hr-b0-86.ucode  | Bin 0 -> 1520636 bytes
 iwlwifi-so-a0-gf-a0-86.ucode  | Bin 0 -> 1679788 bytes
 iwlwifi-so-a0-gf-a0.pnvm  | Bin 55580 -> 55172 bytes
 iwlwifi-so-a0-gf4-a0-86.ucode | Bin 0 -> 1653836 bytes
 iwlwifi-so-a0-gf4-a0.pnvm | Bin 28064 -> 27860 bytes
 iwlwifi-so-a0-hr-b0-86.ucode  | Bin 0 -> 1507388 bytes
 iwlwifi-ty-a0-gf-a0-86.ucode  | Bin 0 -> 1632464 bytes
 iwlwifi-ty-a0-gf-a0.pnvm  | Bin 55484 -> 55020 bytes
 15 files changed, 24 insertions(+)

While the two commits are for ucode 86 releases that is currently not
supported by all available kernels in Jammy, there is not hard/effect
that may be introduced by pulling both of them.

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

Title:
  occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
  start RT ucode: -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  Within stress reboot tests, iwlwifi may fail to load firmware and
  triggers retry, and finally makes wifi operative.

  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | 
trm_hw_status0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x | 
trm_hw_status1
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE | 
interruptlink1
  ..
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC: 
0x8026934e
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1: 
0x8026934c
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode: 
-110
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).

  Test steps:

  $ checkbox-cli run com.canonical.certification::stress/reboot

  Proposed fix:

  * 

[Kernel-packages] [Bug 2048853] [NEW] occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110

2024-01-10 Thread You-Sheng Yang
Public bug reported:

Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.

Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x | trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1: 
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode: 
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).

Test steps:

$ checkbox-cli run com.canonical.certification::stress/reboot

Proposed fix:

* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux-firmware (Ubuntu Jammy)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux-firmware (Ubuntu Mantic)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux-firmware (Ubuntu Noble)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress


** Tags: oem-priority originate-from-2039134 somerville

** Tags added: oem-priority originate-from-2039134 somerville

** Description changed:

  Within stress reboot tests, iwlwifi may fail to load firmware and
  triggers retry, and finally makes wifi operative.
  
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | 
trm_hw_status0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x | 
trm_hw_status1
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE | 
interruptlink1
  ..
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC: 
0x8026934e
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1: 
0x8026934c
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode: 
-110
  Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).
  
  Test steps:
  
  $ checkbox-cli run com.canonical.certification::stress/reboot
+ 
+ Proposed fix:
+ 
+ * https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
+ firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b

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

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

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

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

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

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

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

** Changed in: linux-firmware (Ubuntu Mantic)
   

[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers

2024-01-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [needs-packaging] usbio-drivers

Status in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in The Jammy Jellyfish:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice 
AIC
   This package provides kernel drivers for MIPI cameras through the Intel IPU6
   on Intel MeteoLake platform with Lattice AIC.

  Upstream URL: https://github.com/intel/usbio-drivers
  Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms 
(to request usd-import after created)
  License: GPL v2

  PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800.

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


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


[Kernel-packages] [Bug 2047382] Re: Hotplugging SCSI disk in QEMU VM fails

2024-01-10 Thread Chengen Du
Both Lunar (6.2.0-41.42) and Mantic (6.5.0-16.16) successfully verified by the 
test plan.
root@ubuntu:~# dmesg -wT
[Wed Jan 10 08:28:27 2024] pci :08:00.0: [1af4:1042] type 00 class 0x01
[Wed Jan 10 08:28:27 2024] pci :08:00.0: reg 0x14: [mem 
0x-0x0fff]
[Wed Jan 10 08:28:27 2024] pci :08:00.0: reg 0x20: [mem 
0x-0x3fff 64bit pref]
[Wed Jan 10 08:28:27 2024] pci :08:00.0: BAR 4: assigned [mem 
0x80080-0x800803fff 64bit pref]
[Wed Jan 10 08:28:27 2024] pci :08:00.0: BAR 1: assigned [mem 
0xc0c0-0xc0c00fff]
[Wed Jan 10 08:28:27 2024] virtio-pci :08:00.0: enabling device ( -> 
0002)
[Wed Jan 10 08:28:27 2024] virtio_blk virtio6: 4/0/0 default/read/poll queues
[Wed Jan 10 08:28:27 2024] virtio_blk virtio6: [vdc] 10485760 512-byte logical 
blocks (5.37 GB/5.00 GiB)
[Wed Jan 10 08:28:32 2024] pci :09:00.0: [1af4:1042] type 00 class 0x01
[Wed Jan 10 08:28:32 2024] pci :09:00.0: reg 0x14: [mem 
0x-0x0fff]
[Wed Jan 10 08:28:32 2024] pci :09:00.0: reg 0x20: [mem 
0x-0x3fff 64bit pref]
[Wed Jan 10 08:28:32 2024] pci :09:00.0: BAR 4: assigned [mem 
0x800a0-0x800a03fff 64bit pref]
[Wed Jan 10 08:28:32 2024] pci :09:00.0: BAR 1: assigned [mem 
0xc0a0-0xc0a00fff]
[Wed Jan 10 08:28:32 2024] virtio-pci :09:00.0: enabling device ( -> 
0002)
[Wed Jan 10 08:28:32 2024] virtio_blk virtio7: 4/0/0 default/read/poll queues
[Wed Jan 10 08:28:32 2024] virtio_blk virtio7: [vdd] 10485760 512-byte logical 
blocks (5.37 GB/5.00 GiB)

root@ubuntu:~# lsblk 
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0 7:00  74.1M  1 loop /snap/core22/1033
loop1 7:10 152.1M  1 loop /snap/lxd/26200
loop2 7:20  40.4M  1 loop /snap/snapd/20671
vda 253:0080G  0 disk 
├─vda1  253:1079G  0 part /
├─vda14 253:14   0 4M  0 part 
├─vda15 253:15   0   106M  0 part /boot/efi
└─vda16 259:00   913M  0 part /boot
vdb 253:16   0   366K  0 disk 
vdc 253:32   0 5G  0 disk 
vdd 253:48   0 5G  0 disk

** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  Hotplugging SCSI disk in QEMU VM fails

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
  Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest 
kernels >= 6.5 might be broken.
  The inconsistency suggests a potential race condition.

  [Fix]
  Reverting the two specified commits appears to restore reliability.
  ==
  cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only 
for non-root bus
  40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  Upstream has resolved the issue by reverting both commits through a commit 
placed below.
  ==
  5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  [Test Plan]
  1. Create a VM
  virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk 
path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio
  -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0
  2. Prepare two XMLs for adding two disk devices
  # cat disk_X.xml
  
    
    
    
  
  3. Hotplug disks and check for success
  virsh attach-device scsi_test disk_X.xml

  [Where problems could occur]
  The patch reverts two commits that previously addressed long-standing issues 
related to hotplugging devices with large BARs.
  While this reversion may reintroduce legacy issues, it does not introduce new 
problems.
  The associated risks are deemed low, making it worthwhile to address timing 
issues during the hotplugging of SCSI disks in QEMU VM.

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


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


[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers

2024-01-10 Thread You-Sheng Yang
Pushed new revision of usbio-drivers source package to
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800. It's based on
a new upstream release version and therefore source tarball & everything
else needed are in the PPA.

Changes since previous attempt:
* New upstream WW50'23-USBIO-PV release
* drop patches that have been upstreamed
* correct license body as mentioned by Steve in comment #13.

Need 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/2041800

Title:
  [needs-packaging] usbio-drivers

Status in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in The Jammy Jellyfish:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice 
AIC
   This package provides kernel drivers for MIPI cameras through the Intel IPU6
   on Intel MeteoLake platform with Lattice AIC.

  Upstream URL: https://github.com/intel/usbio-drivers
  Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms 
(to request usd-import after created)
  License: GPL v2

  PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800.

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


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


[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers

2024-01-10 Thread You-Sheng Yang
** Changed in: Ubuntu Noble
   Status: Fix Committed => In Progress

** Description changed:

  Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice 
AIC
-  This package provides kernel drivers for MIPI cameras through the Intel IPU6
-  on Intel MeteoLake platform with Lattice AIC.
+  This package provides kernel drivers for MIPI cameras through the Intel IPU6
+  on Intel MeteoLake platform with Lattice AIC.
  
  Upstream URL: https://github.com/intel/usbio-drivers
  Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms 
(to request usd-import after created)
  License: GPL v2
  
- PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412.
+ PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800.

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

Title:
  [needs-packaging] usbio-drivers

Status in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in The Jammy Jellyfish:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice 
AIC
   This package provides kernel drivers for MIPI cameras through the Intel IPU6
   on Intel MeteoLake platform with Lattice AIC.

  Upstream URL: https://github.com/intel/usbio-drivers
  Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms 
(to request usd-import after created)
  License: GPL v2

  PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800.

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


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