date:20240327

--- Comment From boris.m...@de.ibm.com 2024-03-27 16:09 EDT---
Full list of patches:

a54daf459e7504c0f42d3eb028100b7ab07894ff ("pvattest: Fix root-ca parsing")
5e1cb58a21ae0707d1993de3c8fc078c5cffed88 ("libpv: Support `Armonk` in IBM 
signing key subject")
d14e7593cc6380911ca42b09e11c53477ae13d5c ("genprotimg: support `Armonk` in IBM 
signing key subject")
1a3d0b74f7819f5e087e6ecbf3ec879a05a88bbc ("rust/pv: Support `Armonk` in IBM 
signing key subject")

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

Title:
  [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality
  (s390-tools)

Status in linux package in Ubuntu:
  New

Bug description:
  Description: SE-tooling: New IBM host-key subject locality
  Symptom:   
  On April 24 (z15) / March 29 (z16) user will notice that the
  tooling for Secure execution will no longer detect that the provided
  IBM signing key for that generation is a valid IBM signing key. The
  error message will contain "no IBM signing key found" or similar. The
  respective tool will reject creating an encrypted request/image as it
  could not verify the host-key for its validity. This affects
  genprotimg, pvattest, and pvsecret.
  Problem:
  The new IBM signing keys no longer contain 'Poughkeepsie' as 'subject
  locality' and 'Armonk' is used. The SE tooling checks, beside other
  things, for the subject in the IBM signing key. If the subject is not
  the expected one, the certificate is not recognized as a valid IBM
  signing key. With no valid IBM signing key, the host-key verification
  cannot succeed and users cannot build trustable SE images and
  attestation or add-secret requests.
  Solution:   
  Mitigations are available upstream. The fixes allow Armonk as
  additional locality in the subject and allow potential mismatches in
  the locality of revocation list or host-key issuer subject that may
  still contain Poughkeepsie instead of Armonk.
  Reproduction:  Use a new IBM signing key in the unpatched tooling.

  The fix is required due to the circumstances described here:
  
https://www.ibm.com/docs/en/linux-on-systems?topic=systems-whats-new#iplsdkwhatsnew__title__2

  This is required for all Ubuntu releases in service that support secure 
execution. 
  Therefore, Ubuntu 20.04 LTS (focal) and above are affected and need to be 
fixed.

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


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

[Kernel-packages] [Bug 2059237] Comment bridged from LTC Bugzilla

--- Comment From kowshik.j...@in.ibm.com 2024-03-27 15:59 EDT---
>
> So it looks like this happens with a kernel 6.6 (info taken from LP#2052767:
> linux-6.6.0 - is this an upstream kernel build that you did by yourself?
> Since - afair - we never had a kernel 6.6 in noble/24.04, just a 6.7.)
> and with kernel 6.8.0-11 (from the bug description here) - that is the one
> we currently have in the daily IOSs.
>
> There is already an updated kernel available from our "-proposed" pocket.
> $ rmadison --arch=ppc64el --suite=noble,noble-proposed linux-generic
> linux-generic | 6.8.0-11.11+1 | noble  | ppc64el
> linux-generic | 6.8.0-20.20+1 | noble-proposed | ppc64el <==
> Would you mind installing and trying the 6.8.0-20 from proposed, to see if
> that (very latest) kernel still shows this 'UBSAN:
> array-index-out-of-bounds' issue?

Hello Frank,

This issue happened on a P10 Denali LPAR(KVM on PowerVM)

I haven't built any custom kernel. Per my chat discussion records with
my team, https://cdimage.ubuntu.com/ubuntu-server/daily-
live/pending/noble-live-server-ppc64el.iso was the ISO I had used and I
had downloaded it around Feb 7-9 time frame.

Even with the latest ISO available as on today also this issue is
getting recreated.

Sure, I don't mind giving a try with ISO from proposed. Could you please
point me to the ISO path. I did a search but couldn't find it.

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

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
  [0.512032] LR [] 0x0
  [0.512034] --- interrupt: 3000
  [0.512036] ---[ end trace ]---
  [0.518326] systemd[1]: Inserted module 'autofs4'
  [0.521570]

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

2024-03-27 Thread Georgia Garcia

The mqueue patches are present in jammy-linux-gcp-fips: commits
6e7ff802c7b10 and b4ebbcfebd4d3


** Tags removed: verification-needed-jammy-linux-gcp-fips
** Tags added: verification-done-jammy-linux-gcp-fips

-- 
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 Released
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 2059310] [NEW] mlxbf_gige: call request_irq() after NAPI initialized

2024-03-27 Thread David Thompson

Public bug reported:

SRU Justification:

[Impact]
The mlxbf_gige driver encounters a NULL pointer exception in
mlxbf_gige_open() when kdump is enabled.  The exception happens
because there is a pending RX interrupt before the call to
request_irq(RX IRQ) executes.  Then, the RX IRQ handler fires
immediately after this request_irq() completes. The RX IRQ handler
runs "napi_schedule()" before NAPI is fully initialized via
"netif_napi_add()" and "napi_enable()", both which happen later
in the open() logic.

[Fix]
The logic in mlxbf_gige_open() must fully initialize NAPI before
any calls to request_irq() execute.

[Test Case]
* Boot BF platform and bring up "oob_net0" interface
* Enable kdump completely
* Trigger kdump via "echo c > /proc/sysrq-trigger"
* There should be no exceptions from mlxbf_gige driver

[Regression Potential]
There is low potential for regression as this brings in upstream content.

[Other]
None

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

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

Title:
  mlxbf_gige: call request_irq() after NAPI initialized

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_gige driver encounters a NULL pointer exception in
  mlxbf_gige_open() when kdump is enabled.  The exception happens
  because there is a pending RX interrupt before the call to
  request_irq(RX IRQ) executes.  Then, the RX IRQ handler fires
  immediately after this request_irq() completes. The RX IRQ handler
  runs "napi_schedule()" before NAPI is fully initialized via
  "netif_napi_add()" and "napi_enable()", both which happen later
  in the open() logic.

  [Fix]
  The logic in mlxbf_gige_open() must fully initialize NAPI before
  any calls to request_irq() execute.

  [Test Case]
  * Boot BF platform and bring up "oob_net0" interface
  * Enable kdump completely
  * Trigger kdump via "echo c > /proc/sysrq-trigger"
  * There should be no exceptions from mlxbf_gige driver

  [Regression Potential]
  There is low potential for regression as this brings in upstream content.

  [Other]
  None

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


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

[Kernel-packages] [Bug 2059303] [NEW] [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)

Public bug reported:

Description: SE-tooling: New IBM host-key subject locality
Symptom:
On April 24 (z15) / March 29 (z16) user will notice that the
tooling for Secure execution will no longer detect that the provided
IBM signing key for that generation is a valid IBM signing key. The
error message will contain "no IBM signing key found" or similar. The
respective tool will reject creating an encrypted request/image as it
could not verify the host-key for its validity. This affects
genprotimg, pvattest, and pvsecret.
Problem:
The new IBM signing keys no longer contain 'Poughkeepsie' as 'subject
locality' and 'Armonk' is used. The SE tooling checks, beside other
things, for the subject in the IBM signing key. If the subject is not
the expected one, the certificate is not recognized as a valid IBM
signing key. With no valid IBM signing key, the host-key verification
cannot succeed and users cannot build trustable SE images and
attestation or add-secret requests.
Solution:
Mitigations are available upstream. The fixes allow Armonk as
additional locality in the subject and allow potential mismatches in
the locality of revocation list or host-key issuer subject that may
still contain Poughkeepsie instead of Armonk.
Reproduction: Use a new IBM signing key in the unpatched tooling.

The fix is required due to the circumstances described here:
https://www.ibm.com/docs/en/linux-on-systems?topic=systems-whats-new#iplsdkwhatsnew__title__2

This is required for all Ubuntu releases in service that support secure
execution.
Therefore, Ubuntu 20.04 LTS (focal) and above are affected and need to be fixed.

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

** Tags: architecture-s39064 bugnameltc-205928 severity-critical
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-205928 severity-critical
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/2059303

Title:
[UBUNTU 20.04] SE-tooling: New IBM host-key subject locality
(s390-tools)

Status in linux package in Ubuntu:
New

Bug description:
Description: SE-tooling: New IBM host-key subject locality
Symptom:
On April 24 (z15) / March 29 (z16) user will notice that the
tooling for Secure execution will no longer detect that the provided
IBM signing key for that generation is a valid IBM signing key. The
error message will contain "no IBM signing key found" or similar. The
respective tool will reject creating an encrypted request/image as it
could not verify the host-key for its validity. This affects
genprotimg, pvattest, and pvsecret.
Problem:
The new IBM signing keys no longer contain 'Poughkeepsie' as 'subject
locality' and 'Armonk' is used. The SE tooling checks, beside other
things, for the subject in the IBM signing key. If the subject is not
the expected one, the certificate is not recognized as a valid IBM
signing key. With no valid IBM signing key, the host-key verification
cannot succeed and users cannot build trustable SE images and
attestation or add-secret requests.
Solution:
Mitigations are available upstream. The fixes allow Armonk as
additional locality in the subject and allow potential mismatches in
the locality of revocation list or host-key issuer subject that may
still contain Poughkeepsie instead of Armonk.
Reproduction: Use a new IBM signing key in the unpatched tooling.

The fix is required due to the circumstances described here:

https://www.ibm.com/docs/en/linux-on-systems?topic=systems-whats-new#iplsdkwhatsnew__title__2

This is required for all Ubuntu releases in service that support secure
execution.
Therefore, Ubuntu 20.04 LTS (focal) and above are affected and need to be
fixed.

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

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

[Kernel-packages] [Bug 2059303] [NEW] [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)

You have been subscribed to a public bug:

The fix is required due to the circumstances described here:
https://www.ibm.com/docs/en/linux-on-systems?topic=systems-whats-new#iplsdkwhatsnew__title__2

This is required for all Ubuntu releases in service that support secure
execution.
Therefore, Ubuntu 20.04 LTS (focal) and above are affected and need to be fixed.

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

** Tags: architecture-s39064 bugnameltc-205928 severity-critical
targetmilestone-inin---
--
[UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
https://bugs.launchpad.net/bugs/2059303
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

This bug was fixed in the package initramfs-tools - 0.142ubuntu23

---
initramfs-tools (0.142ubuntu23) noble; urgency=medium

  [ Daniel van Vugt ]
  * hooks/framebuffer: Only add simple/tiny framebuffer drivers. This is to
limit the size of initrd when FRAMEBUFFER=y is soon enabled for desktop
installations (LP: #1970069, #1869655).

  [ Benjamin Drung ]
  * autopkgtest: Increase QEMU timeouts on arm64/armhf
  * hooks/framebuffer:
- Move adding framebuffer drivers into auto_add_modules
- Drop looking in $MODULESDIR/initrd/ for kernel modules
- Support MODULES=dep in framebuffer hook

initramfs-tools (0.142ubuntu22) noble; urgency=medium

  * autopkgtest: update systemd-udevd path from /lib to /usr/lib

initramfs-tools (0.142ubuntu21) noble; urgency=medium

  [ Benjamin Drung ]
  * configure_networking:
- Increase minimum timeout to 30 seconds
- Fix configuring BOOTIF when using iSCSI (LP: #2056187)
- Set interface MTU if provided by the DHCP server (LP: #2056194)
- log sleep durations before retries
  * Copy /etc/passwd into the initramfs to allow dhcpcd running as dhcpcd user
  * Replace obsolete pkg-config build-dependency by pkgconf

  [ Dan Bungert ]
  * Restore nvdimm and dax pmem-related modules (LP: #1981385)

 -- Benjamin Drung   Thu, 21 Mar 2024 10:57:54 +0100

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in plymouth package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts

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

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

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

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

Title:
  Remove getabis scripts

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  With ABI checks removed from the tree (#LP2055685), there's no need to
  download the buildinfo from a previous version.

  [Fix]
  This is needed only in the main kernels.
  1. remove the common getabis script
  2. remove per kernel getabis file (this will be done with cranky fix)

  [Test]
  Build test on cbd. No issue found. Also cranked the kernels in advance to see 
if there were issues, but no issue was found.

  [Regression potential]
  In the current cycle, the ABI checks have been removed and this is not used 
anymore. No issues have been found. Now we're just removing an unused feature, 
therefore the regression potential is none.

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


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

[Kernel-packages] [Bug 2059284] Re: Mantic update: upstream stable patchset 2024-03-27

Skipped "jfs: fix uaf in jfs_evict_inode" since it is already applied
(CVE-2023-52600). Adjusted commit message of SAUCE apparmor patch to
match previous series.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52600

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

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

Title:
  Mantic update: upstream stable patchset 2024-03-27

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

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2024-03-27

  Ported from the following upstream stable releases:
  v6.1.77, v6.6.16

 from git://git.kernel.org/

  asm-generic: make sparse happy with odd-sized put_unaligned_*()
  powerpc/mm: Fix null-pointer dereference in pgtable_cache_add
  arm64: irq: set the correct node for VMAP stack
  drivers/perf: pmuv3: don't expose SW_INCR event in sysfs
  powerpc: Fix build error due to is_valid_bugaddr()
  powerpc/mm: Fix build failures due to arch_reserved_kernel_pages()
  powerpc/64s: Fix CONFIG_NUMA=n build due to create_section_mapping()
  x86/boot: Ignore NMIs during very early boot
  powerpc: pmd_move_must_withdraw() is only needed for 
CONFIG_TRANSPARENT_HUGEPAGE
  powerpc/lib: Validate size for vector operations
  x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel
  perf/core: Fix narrow startup race when creating the perf nr_addr_filters 
sysfs file
  debugobjects: Stop accessing objects after releasing hash bucket lock
  regulator: core: Only increment use_count when enable_count changes
  audit: Send netlink ACK before setting connection in auditd_set
  ACPI: video: Add quirk for the Colorful X15 AT 23 Laptop
  PNP: ACPI: fix fortify warning
  ACPI: extlog: fix NULL pointer dereference check
  ACPI: NUMA: Fix the logic of getting the fake_pxm value
  PM / devfreq: Synchronize devfreq_monitor_[start/stop]
  ACPI: APEI: set memory failure flags as MF_ACTION_REQUIRED on synchronous 
events
  FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree
  UBSAN: array-index-out-of-bounds in dtSplitRoot
  jfs: fix slab-out-of-bounds Read in dtSearch
  jfs: fix array-index-out-of-bounds in dbAdjTree
  jfs: fix uaf in jfs_evict_inode
  pstore/ram: Fix crash when setting number of cpus to an odd number
  crypto: octeontx2 - Fix cptvf driver cleanup
  erofs: fix ztailpacking for subpage compressed blocks
  crypto: stm32/crc32 - fix parsing list of devices
  afs: fix the usage of read_seqbegin_or_lock() in afs_lookup_volume_rcu()
  afs: fix the usage of read_seqbegin_or_lock() in afs_find_server*()
  rxrpc_find_service_conn_rcu: fix the usage of read_seqbegin_or_lock()
  jfs: fix array-index-out-of-bounds in diNewExt
  arch: consolidate arch_irq_work_raise prototypes
  s390/vfio-ap: fix sysfs status attribute for AP queue devices
  s390/ptrace: handle setting of fpc register correctly
  KVM: s390: fix setting of fpc register
  SUNRPC: Fix a suspicious RCU usage warning
  ecryptfs: Reject casefold directory inodes
  ext4: fix inconsistent between segment fstrim and full fstrim
  ext4: unify the type of flexbg_size to unsigned int
  ext4: remove unnecessary check from alloc_flex_gd()
  ext4: avoid online resizing failures due to oversized flex bg
  wifi: rt2x00: restart beacon queue when hardware reset
  selftests/bpf: satisfy compiler by having explicit return in btf test
  selftests/bpf: Fix pyperf180 compilation failure with clang18
  wifi: rt2x00: correct wrong BBP register in RxDCOC calibration
  selftests/bpf: Fix issues in setup_classid_environment()
  soc: xilinx: Fix for call trace due to the usage of smp_processor_id()
  soc: xilinx: fix unhandled SGI warning message
  scsi: lpfc: Fix possible file string name overflow when updating firmware
  PCI: Add no PM reset quirk for NVIDIA Spectrum devices
  bonding: return -ENOMEM instead of BUG in alb_upper_dev_walk
  net: usb: ax88179_178a: avoid two consecutive device resets
  scsi: arcmsr: Support new PCI device IDs 1883 and 1886
  ARM: dts: imx7d: Fix coresight funnel ports
  ARM: dts: imx7s: Fix lcdif compatible
  ARM: dts: imx7s: Fix nand-controller #size-cells
  wifi: ath9k: Fix potential array-index-out-of-bounds read in 
ath9k_htc_txstatus()
  wifi: ath11k: fix race due to setting ATH11K_FLAG_EXT_IRQ_ENABLED too early
  bpf: Check

[Kernel-packages] [Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update

2024-03-27 Thread Bug Watch Updater

** Changed in: linux-firmware
   Status: New => Fix Released

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

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

Status in Linux Firmware:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  Current version of amdgpu binaries in linux-firmware shipped with
  ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems
  when decoding VP9 content with the iGPU on modern AMD mobile processor
  (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).

  The issue has been reported and solved upstream:

  https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044

  [EDIT: fixed link]

  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.

  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding

  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9

  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd

  I'm currently running ubuntu 23.10 (mantic) with binaries from
  upstream and the issue is solved.

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


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

[Kernel-packages] [Bug 2059284] [NEW] Mantic update: upstream stable patchset 2024-03-27

2024-03-27 Thread Manuel Diewald

Public bug reported:


SRU Justification

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

   upstream stable patchset 2024-03-27

Ported from the following upstream stable releases:
v6.1.77, v6.6.16

   from git://git.kernel.org/

asm-generic: make sparse happy with odd-sized put_unaligned_*()
powerpc/mm: Fix null-pointer dereference in pgtable_cache_add
arm64: irq: set the correct node for VMAP stack
drivers/perf: pmuv3: don't expose SW_INCR event in sysfs
powerpc: Fix build error due to is_valid_bugaddr()
powerpc/mm: Fix build failures due to arch_reserved_kernel_pages()
powerpc/64s: Fix CONFIG_NUMA=n build due to create_section_mapping()
x86/boot: Ignore NMIs during very early boot
powerpc: pmd_move_must_withdraw() is only needed for CONFIG_TRANSPARENT_HUGEPAGE
powerpc/lib: Validate size for vector operations
x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel
perf/core: Fix narrow startup race when creating the perf nr_addr_filters sysfs 
file
debugobjects: Stop accessing objects after releasing hash bucket lock
regulator: core: Only increment use_count when enable_count changes
audit: Send netlink ACK before setting connection in auditd_set
ACPI: video: Add quirk for the Colorful X15 AT 23 Laptop
PNP: ACPI: fix fortify warning
ACPI: extlog: fix NULL pointer dereference check
ACPI: NUMA: Fix the logic of getting the fake_pxm value
PM / devfreq: Synchronize devfreq_monitor_[start/stop]
ACPI: APEI: set memory failure flags as MF_ACTION_REQUIRED on synchronous events
FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree
UBSAN: array-index-out-of-bounds in dtSplitRoot
jfs: fix slab-out-of-bounds Read in dtSearch
jfs: fix array-index-out-of-bounds in dbAdjTree
jfs: fix uaf in jfs_evict_inode
pstore/ram: Fix crash when setting number of cpus to an odd number
crypto: octeontx2 - Fix cptvf driver cleanup
erofs: fix ztailpacking for subpage compressed blocks
crypto: stm32/crc32 - fix parsing list of devices
afs: fix the usage of read_seqbegin_or_lock() in afs_lookup_volume_rcu()
afs: fix the usage of read_seqbegin_or_lock() in afs_find_server*()
rxrpc_find_service_conn_rcu: fix the usage of read_seqbegin_or_lock()
jfs: fix array-index-out-of-bounds in diNewExt
arch: consolidate arch_irq_work_raise prototypes
s390/vfio-ap: fix sysfs status attribute for AP queue devices
s390/ptrace: handle setting of fpc register correctly
KVM: s390: fix setting of fpc register
SUNRPC: Fix a suspicious RCU usage warning
ecryptfs: Reject casefold directory inodes
ext4: fix inconsistent between segment fstrim and full fstrim
ext4: unify the type of flexbg_size to unsigned int
ext4: remove unnecessary check from alloc_flex_gd()
ext4: avoid online resizing failures due to oversized flex bg
wifi: rt2x00: restart beacon queue when hardware reset
selftests/bpf: satisfy compiler by having explicit return in btf test
selftests/bpf: Fix pyperf180 compilation failure with clang18
wifi: rt2x00: correct wrong BBP register in RxDCOC calibration
selftests/bpf: Fix issues in setup_classid_environment()
soc: xilinx: Fix for call trace due to the usage of smp_processor_id()
soc: xilinx: fix unhandled SGI warning message
scsi: lpfc: Fix possible file string name overflow when updating firmware
PCI: Add no PM reset quirk for NVIDIA Spectrum devices
bonding: return -ENOMEM instead of BUG in alb_upper_dev_walk
net: usb: ax88179_178a: avoid two consecutive device resets
scsi: arcmsr: Support new PCI device IDs 1883 and 1886
ARM: dts: imx7d: Fix coresight funnel ports
ARM: dts: imx7s: Fix lcdif compatible
ARM: dts: imx7s: Fix nand-controller #size-cells
wifi: ath9k: Fix potential array-index-out-of-bounds read in 
ath9k_htc_txstatus()
wifi: ath11k: fix race due to setting ATH11K_FLAG_EXT_IRQ_ENABLED too early
bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
scsi: libfc: Don't schedule abort twice
scsi: libfc: Fix up timeout error in fc_fcp_rec_error()
bpf: Set uattr->batch.count as zero before batched update or deletion
wifi: wfx: fix possible NULL pointer dereference in wfx_set_mfp_ap()
ARM: dts: rockchip: fix rk3036 hdmi ports node
ARM: dts: imx25/27-eukrea: Fix RTC node name
ARM: dts: imx: Use flash@0,0 pattern
ARM: dts: imx27: Fix sram node
ARM: dts: imx1: Fix sram node
net: phy: at803x: fix passing the wrong reference for config_intr
ionic: pass opcode to devcmd_wait
ionic: bypass firmware cmds when stuck in reset
block/rnbd-srv: Check for unlikely string overflow
ARM: dts: imx25: Fix the iim compatible string
ARM: dts: imx25/27: Pass timing0
ARM: dts: imx27-apf27dev: Fix LED name

[Kernel-packages] [Bug 2058485] Re: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter

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

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

Title:
   [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with
  percpu counter

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

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

  Backport: ipc/msg: mitigate the lock contention with percpu counter
  (merged upstream in 6.1) to jammy

  [Impact]

  The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC 
msg queue is in heavy use, causing heavy
  cache bounce and overhead. Change them to percpu_counter greatly improve the 
performance. Since there is one percpu
  struct per namespace, additional memory cost is minimal. Reading of the count 
done in msgctl call, which is infrequent.
  So the need to sum up the counts in each CPU is infrequent.

  [Fix]

  Backport:
72d1e611082e ipc/msg: mitigate the lock contention with percpu counter

  For clean backport/build, those are also required:

  5d0ce3595ab75 percpu: add percpu_counter_add_local and 
percpu_counter_sub_local
  38cd5b12b7854 ipc: Remove extra braces
  0889f44e28103 ipc: Check permissions for checkpoint_restart sysctls at open 
time
  dd141a4955d5e ipc: Remove extra1 field abuse to pass ipc namespace
  def7343ff03bb ipc: Use the same namespace to modify and validate
  1f5c135ee509e ipc: Store ipc sysctls in the ipc namespace
  dc55e35f9e810 ipc: Store mqueue sysctls in the ipc namespace
  0e9beb8a96f21 ipc/ipc_sysctl.c: remove fallback for !CONFIG_PROC_SYSCTL
  5563cabdde7ee ipc: check checkpoint_restore_ns_capable() to modify C/R proc 
files

  
  [Test Plan]

  Test as the original patch, with pts/stress-ng message passing
  and compare performance.

  [Where problems could occur]

  Performance regression in IPC communication/workload.

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


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

[Kernel-packages] [Bug 2059279] [NEW] mlxbf_gige: replace SAUCE patch for pause frame counters

2024-03-27 Thread David Thompson

Public bug reported:

SRU Justification:

[Impact]
The support for mlxbf_gige pause frame counters was added to Jammy
via a SAUCE patch.  After upstream review, a small issue was fixed
that makes the SAUCE patch different from the upstream commit.

[Fix]
The fix is to replace the SAUCE patch in the Jammy repo with
the upstream equivalent.

[Test Case]
* Boot BF platform and bring up "oob_net0" interface
* Execute the command "ethtool -I -a oob_net0" to get baseline stats
* Send heavy traffic into "oob_net0" interface
* Re-run the above ethtool command, noting the pause frame counters

[Regression Potential]
There is low potential for regression as this brings in upstream content.

[Other]
None

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

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

Title:
  mlxbf_gige: replace SAUCE patch for pause frame counters

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  The support for mlxbf_gige pause frame counters was added to Jammy
  via a SAUCE patch.  After upstream review, a small issue was fixed
  that makes the SAUCE patch different from the upstream commit.

  [Fix]
  The fix is to replace the SAUCE patch in the Jammy repo with
  the upstream equivalent.

  [Test Case]
  * Boot BF platform and bring up "oob_net0" interface
  * Execute the command "ethtool -I -a oob_net0" to get baseline stats
  * Send heavy traffic into "oob_net0" interface
  * Re-run the above ethtool command, noting the pause frame counters

  [Regression Potential]
  There is low potential for regression as this brings in upstream content.

  [Other]
  None

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


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

[Kernel-packages] [Bug 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working

2024-03-27 Thread Marc Deslauriers

There's a relevant thread here:

https://lore.kernel.org/all/27131a7fae2794a63f4f285a20e41116ba4198f3.ca...@gmail.com/T/

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

Title:
   [Lenovo 300e 2nd GEN] ELAN Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Used Ubunutu 22.04 with the current 5.15.x Kernel, cross tested with
  Linux Mint and 5.14.x Kernel.

  I have a Lenovo 300e 2nd Gen with an ELAN Touchscreen AND Touchpad
  with AMD processor.

  The Touchscreen is working flawlessly.
  The TouchPAD is dead.

  According to the Windows driver:
  %ELANHIDDeviceDesc%   = ETD_HID_PTP_WIN10_Group2_Inst, 
HID\VEN_ELAN_0660; ClickPad for Capela 14e Windows
  %ELANHIDDeviceDesc%   = ETD_HID_PTP_WIN10_Group1_Inst, 
HID\VEN_ELAN_0661; ClickPad for Windows 100e/300e
  %ELANHIDDeviceDesc%   = ETD_HID_PTP_WIN10_Group3_Inst, 
HID\VEN_ELAN_066C; ClickPad for 100e/300e AMD Pollock
  %ELANHIDDeviceDesc%   = ETD_HID_PTP_WIN10_Group1_Inst, 
HID\VEN_ELAN_066E; ClickPad for 100W&300W Gen3 AMD Pollock
  %ELANHIDDeviceDesc%   = ETD_HID_PTP_WIN10_Group1_Inst, 
HID\VEN_ELAN_066F; ClickPad for 300W Gen3 Intel JasperLake

  it is an ELAN066C

  According to similar solutions i tried to block several built in
  kernel modules, without success.

  
https://askubuntu.com/questions/1248176/ideapad-5-15are05-elan-touchpad-not-working-on-20-04-nor-on-18-04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pingu  1140 F pulseaudio
   /dev/snd/controlC0:  pingu  1140 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-05-30 (17 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220111
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 30c9:001e 8SSC20X63465V1SR135107E EasyCamera 1M
   Bus 001 Device 003: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82GK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=/dev/mapper/vgmint-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 1.187.31
  Tags:  una
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2021
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FRCN21WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K13476WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo 300e 2nd Gen
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrFRCN21WW:bd07/07/2021:br1.21:efr1.15:svnLENOVO:pn82GK:pvrLenovo300e2ndGen:rvnLENOVO:rnLNVNB161216:rvrSDK0K13476WIN:cvnLENOVO:ct31:cvrLenovo300e2ndGen:skuLENOVO_MT_82GK_BU_idea_FM_300e2ndGen:
  dmi.product.family: 300e 2nd Gen
  dmi.product.name: 82GK
  dmi.product.sku: LENOVO_MT_82GK_BU_idea_FM_300e 2nd Gen
  dmi.product.version: Lenovo 300e 2nd Gen
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64

This bug was fixed in the package gcc-13 - 13.2.0-21ubuntu1

---
gcc-13 (13.2.0-21ubuntu1) noble; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-13 (13.2.0-21) unstable; urgency=medium

  * Update to git 20240324 from the gcc-13 branch.
- Fix PR fortran/101135, PR fortran/55978.
  * Update the proposed patch to fix PR ada/114064.
  * Move the _FORTIFY_SOURCE setting from cc1 to the driver.
  * Refresh patches.

gcc-13 (13.2.0-20) unstable; urgency=medium

  * Update to git 20240323 from the gcc-13 branch.
- Fix PR other/109668, PR tree-optimization/114231,
  PR tree-optimization/112793, PR tree-optimization/113670,
  PR middle-end/113622, PR tree-optimization/114203, PR middle-end/114070,
  PR middle-end/114070, PR tree-optimization/114027, PR debug/112718,
  PR tree-optimization/113910, PR tree-optimization/111736,
  PR tree-optimization/114396, PR target/113950 (PPC),
  PR target/111822 (x86), PR target/114160 (RISCV), PR sanitizer/112709,
  PR sanitizer/112709, PR target/114339 (x86), PR middle-end/113907,
  PR target/114310 (AArch64), PR rtl-optimization/110079,
  PR rtl-optimization/114211, PR target/114184 (x86), PR fortran/114001,
  PR fortran/103715, PR fortran/110826, PR fortran/100988,
  PR fortran/104819, PR libstdc++/66146, PR libstdc++/114316,
  PR libstdc++/114147.
  * Make vhdl known to the PPC backend.
  * Use the proposed patch to fix PR ada/114064, 64bit definitions for
time_t_bits type on 32bit archs.
  * libsanitizer: Remove crypt and crypt_r interceptors for releases
with glibc (>= 2.31). Remove the build hacks for crypt.h.
  * libstdc++-dev: Install libstdc++_libbacktrace.a. Note that all Filesystem TS
and std::stacktrace symbols were added to libstdc++exp.a and GCC 14 stops
shipping libstdc++_libbacktrace.a. Closes: #1065359.

 -- Matthias Klose   Sun, 24 Mar 2024 14:57:17 +0100

** Changed in: gcc-13 (Ubuntu Noble)
   Status: Fix Committed => Fix Released

-- 
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 gcc-10 package in Ubuntu:
  Confirmed
Status in gcc-11 package in Ubuntu:
  Confirmed
Status in gcc-12 package in Ubuntu:
  Confirmed
Status in gcc-13 package in Ubuntu:
  Fix Released
Status in gcc-8 package in Ubuntu:
  Invalid
Status in gcc-9 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in Ubuntu:
  Confirmed
Status in llvm-toolchain-16 package in Ubuntu:
  Confirmed
Status in gcc-10 source package in Noble:
  Confirmed
Status in gcc-11 source package in Noble:
  Confirmed
Status in gcc-12 source package in Noble:
  Confirmed
Status in gcc-13 source package in Noble:
  Fix Released
Status in gcc-8 source package in Noble:
  Invalid
Status in gcc-9 source package in Noble:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in llvm-toolchain-14 source package in Noble:
  Confirmed
Status in llvm-toolchain-15 source package in Noble:
  Confirmed
Status in llvm-toolchain-16 source package in Noble:
  Confirmed

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

[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7

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

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

Title:
  iwlwifi disconnect and crash - intel wifi7

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

Bug description:
  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
   xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
   
   ? show_regs+0x6d/0x80
   ? __warn+0x89/0x160
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? report_bug+0x17e/0x1b0
   ? handle_bug+0x46/0x90
   ? exc_invalid_op+0x18/0x80
   ? asm_exc_invalid_op+0x1b/0x20
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? free_unref_page+0x30/0x180
   iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
   ? skb_free_head+0xa8/0xd0
   __napi_poll+0x30/0x1f0
   net_rx_action+0x181/0x2e0
   ? __irq_wake_thread+0x42/0x50
   __do_softirq+0xd9/0x349
   ? __pfx_irq_thread_fn+0x10/0x10
   do_softirq.part.0+0x41/0x80
   
   
   __local_bh_enable_ip+0x72/0x80
   iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
   irq_thread_fn+0x21/0x70
   irq_thread+0xf8/0x1c0
   ? __pfx_irq_thread_dtor+0x10/0x10
   ? __pfx_irq_thread+0x10/0x10
   kthread+0xef/0x120
   ? __pfx_kthread+0x10/0x10
   ret_from_fork+0x44/0x70
   ? __pfx_kthread+0x10/0x10
   ret_from_fork_asm+0x1b/0x30
   
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
  iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi :05:00.0: 0x | data3
  iwlwifi :05:00.0: 0xA0005E44 | beacon time
  iwlwifi :05:00.0: 0x2806818F | tsf low
  iwlwifi :05:00.0: 0x | tsf hi
  iwlwifi :05:00.0: 0x | time gp1
  iwlwifi :05:00.0: 0x0BB840A7 | time gp2
  iwlwifi :05:00.0: 0x0001 | uCode revision type
  iwlwifi :05:00.0: 0x0053 | uCode version major
  iwlwifi :05:00.0: 0xEC13314B | uCode version minor
  iwlwifi :05:00.0: 0x0472 | hw version
  iwlwifi :05:00.0: 0x00C80002 | board version
  iwlwifi :05:00.0: 0x03B7001C | hcmd
  iwlwifi :05:00.0: 0x67F68000

[Kernel-packages] [Bug 2059263] [NEW] Fix acpi_power_meter accessing IPMI region before it's ready

2024-03-27 Thread Kai-Heng Feng

Public bug reported:

[Impact]
ACPI error can be found in kernel message:
[3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) 
[IPMI] (20230628/evregion-130)

[Fix]
On Dell systems that have IPI0001 device, ensure IPMI region is ready
before acpi_power_meter invokes any ACPI method.

[Test]
With the patch applied, no such error can be found in kernel message.
acpi_power_meter sysfs also works correctly.

[Where problems could occur]
If asynchronous probe is disabled, the device drivers that probe after
acpi_power_meter needs to wait until the completion is done, hence the
boot time might be slower.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  Fix acpi_power_meter accessing IPMI region before it's ready

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  ACPI error can be found in kernel message:
  [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) 
[IPMI] (20230628/evregion-130)

  [Fix]
  On Dell systems that have IPI0001 device, ensure IPMI region is ready
  before acpi_power_meter invokes any ACPI method.

  [Test]
  With the patch applied, no such error can be found in kernel message.
  acpi_power_meter sysfs also works correctly.

  [Where problems could occur]
  If asynchronous probe is disabled, the device drivers that probe after
  acpi_power_meter needs to wait until the completion is done, hence the
  boot time might be slower.

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


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

[Kernel-packages] [Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x

Applied for 6.8.0-12.12, so included in -20 (that is atm still in
-proposed).

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

Title:
  Turning COMPAT_32BIT_TIME off on s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This will prevent existing s390 binaries to operate correctly, if they
  are still using 32bit time.

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

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


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

[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

2024-03-27 Thread Andrea Righi

Looking at the code this issue seems to be introduced by `UBUNTU: SAUCE:
modpost: support arbitrary symbol length in modversion` and the UBSAN
warning tells us that accessing vers->name[0] could be an out-of-bounds
access.

The struct modversion_info contains a flexibile array (name), that is
correctly defined as the last member of the struct, and its size is
allocated dynamically at runtime, so I would expect that vars->name[0]
is always allocated, unless vars is not initialized properly or there's
an empty name.

So, my guess is that UBSAN isn't really happy about the flexible array
and this is just a false positive.

However, to be 100% sure that we are not actually doing and out-of-bound
access and prevent the warning, we could apply something like the
following on top of our SAUCE patch:

diff --git a/arch/powerpc/kernel/module_64.c b/arch/powerpc/kernel/module_64.c
index 195714fc6e22..1f5960e25758 100644
--- a/arch/powerpc/kernel/module_64.c
+++ b/arch/powerpc/kernel/module_64.c
@@ -350,6 +350,8 @@ static void dedotify_versions(struct modversion_info *vers,
struct modversion_info *end = (void *)vers + size;
 
for (; vers < end && vers->next; vers = (void *)vers + vers->next) {
+   if (size <= offsetof(struct modversion_info, name))
+   continue;
if (vers->name[0] == '.') {
memmove(vers->name, vers->name+1, strlen(vers->name));
}


In this case even if (for any reason) vars->name[] is an empty string we can 
prevent the out-of-bound access and make UBSAN happy.

Opinions?

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

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP

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

2024-03-27 Thread Boul Chandra Garai

Public bug reported:

$ sudo apt install linux-tools-6.5.0-26-generic 
linux-cloud-tools-6.5.0-26-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-cloud-tools-6.5.0-26-generic is already the newest version 
(6.5.0-26.26~22.04.1).
The following additional packages will be installed:
  linux-hwe-6.5-tools-6.5.0-26 linux-tools-common
The following NEW packages will be installed:
  linux-hwe-6.5-tools-6.5.0-26 linux-tools-6.5.0-26-generic linux-tools-common
0 upgraded, 3 newly installed, 0 to remove and 11 not upgraded.
Need to get 0 B/8,256 kB of archives.
After this operation, 29.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Selecting previously unselected package linux-tools-common.
(Reading database ... 344041 files and directories currently installed.)
Preparing to unpack .../linux-tools-common_5.15.0-101.111_all.deb ...
Unpacking linux-tools-common (5.15.0-101.111) ...
dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0
-101.111_all.deb (--unpack):
 trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-io
tg-tools-common 5.15.0-1050.56
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package linux-hwe-6.5-tools-6.5.0-26.
Preparing to unpack .../linux-hwe-6.5-tools-6.5.0-26_6.5.0-26.26~22.04.1_amd64.d
eb ...
Unpacking linux-hwe-6.5-tools-6.5.0-26 (6.5.0-26.26~22.04.1) ...
Selecting previously unselected package linux-tools-6.5.0-26-generic.
Preparing to unpack .../linux-tools-6.5.0-26-generic_6.5.0-26.26~22.04.1_amd64.d
eb ...
Unpacking linux-tools-6.5.0-26-generic (6.5.0-26.26~22.04.1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-tools-common_5.15.0-101.111_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 linux-tools-common:amd64: Install
 linux-hwe-6.5-tools-6.5.0-26:amd64: Install
 linux-tools-6.5.0-26-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  boul-iisc   2341 F pulseaudio
 /dev/snd/pcmC0D0p:   boul-iisc   2341 F...m pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Wed Mar 27 18:36:09 2024
DpkgTerminalLog:
 Preparing to unpack .../linux-tools-common_5.15.0-101.111_all.deb ...
 Unpacking linux-tools-common (5.15.0-101.111) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/linux-tools-common_5.15.0-101.111_all.deb (--unpack):
  trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15.0-1050.56
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15.0-1050.56
InstallationDate: Installed on 2024-01-11 (76 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Dell Inc. XPS 15 9530
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=bb015bf7-1f70-468a-9510-ceb36baafb05 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.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
SourcePackage: linux
Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15.0-1050.56
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2023
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.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.10.0:bd12/18/2023:br1.10: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.

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

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

Status in linux package in Ubuntu:
  New

Bug

[Kernel-packages] [Bug 2059254] Re: package linux-intel-iotg-tools-common 5.15.0-1049.55 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-b

2024-03-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-intel-iotg-tools-common 5.15.0-1049.55 [modified:
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz
  usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf-
  buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz
  usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-
  daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-
  diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz
  usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf-
  kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz
  usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz
  usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz
  usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz
  usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz
  usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-
  script-python.1.gz usr/share/man/man1/perf-script.1.gz
  usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz
  usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf-
  top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf-
  version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-tools-common 5.15.0-101.111

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

Bug description:
  The following packages will be upgraded:
linux-intel-iotg-tools-common
  1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
  6 not fully installed or removed.
  Need to get 0 B/304 kB of archives.
  After this operation, 23.6 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  (Reading database ... 344169 files and directories currently installed.)
  Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb 
...
  Unpacking linux-intel-iotg-tools-common (5.15.0-1050.56) over 
(5.15.0-1049.55) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.15.0-101.111
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 27 18:18:07 2024
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.15.0-101.111
  InstallationDate: Installed on 2024-01-11 (76 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  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.3
   apt  2.4.11
  SourcePackage: linux-intel-iotg
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2059254] [NEW] package linux-intel-iotg-tools-common 5.15.0-1049.55 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf

2024-03-27 Thread Boul Chandra Garai

Public bug reported:

The following packages will be upgraded:
  linux-intel-iotg-tools-common
1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
6 not fully installed or removed.
Need to get 0 B/304 kB of archives.
After this operation, 23.6 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 344169 files and directories currently installed.)
Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb ...
Unpacking linux-intel-iotg-tools-common (5.15.0-1050.56) over (5.15.0-1049.55) 
...
dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb 
(--unpack):
 trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.15.0-101.111
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 27 18:18:07 2024
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.15.0-101.111
InstallationDate: Installed on 2024-01-11 (76 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
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.3
 apt  2.4.11
SourcePackage: linux-intel-iotg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy package-conflict

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

Title:
  package linux-intel-iotg-tools-common 5.15.0-1049.55 [modified:
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz
  usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf-
  buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz
  usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-
  daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-
  diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz
  usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf-
  kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz
  usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz
  usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz
  usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz
  usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz
  usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-
  script-python.1.gz usr/share/man/man1/perf-script.1.gz
  usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz
  usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf-
  top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf-
  version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-tools-common 5.15.0-101.111

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

Bug description:
  The following packages will be upgraded:
linux-intel-iotg-tools-common
  1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
  6 not fully installed or removed.
  Need to get 0 B/304 kB of archives.
  After this operation, 23.6 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  (Reading database ... 344169 files and directories currently installed.)
  Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb 
...
  Unpacking linux-intel-iotg-tools-common (5.15.0-1050.56) over 
(5.15.0-1049.55) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.15.0-101.111
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1050.56_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

** Tags added: noble

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

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
  [0.512032] LR [] 0x0
  [0.512034] --- interrupt: 3000
  [0.512036] ---[ end trace ]---
  [0.518326] systemd[1]: Inserted module 'autofs4'
  [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode 
(+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL 
+ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP 
+LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
  [0.521583] systemd[1]: Detected virtualization powervm.
  [0.521589] systemd[1]: Detected architecture ppc64-le.
  [0.521593] systemd[1]: Running in initrd.
  [0.521743] systemd[1]: No hostname configured, using default hostname.
  [0.521789] systemd[1]: Hostname set to .
  [0.521847] systemd[1]: Initializing machine ID from random generator.
  [0.600736] systemd[1]: Queued start job for default target initrd.target.

  
   
  Machine Type = P10  LPAR 
   
  Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com 
   
  ---Steps to Reproduce---
  1. reboot the system
  2. Once the system is booted back, look at dmesg
   
  ---uname output---
  Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  Additional Information:
  Same trace messages are seen on L2 guest as well.

  == Comment: - Kowshik Jois B S ==
  Hello Likhitha,

  The ubuntu bug

[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7

2024-03-27 Thread AaronMa

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

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

** Changed in: hwe-next
   Importance: Undecided => High

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

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

Title:
  iwlwifi disconnect and crash - intel wifi7

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

Bug description:
  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
   xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
   
   ? show_regs+0x6d/0x80
   ? __warn+0x89/0x160
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? report_bug+0x17e/0x1b0
   ? handle_bug+0x46/0x90
   ? exc_invalid_op+0x18/0x80
   ? asm_exc_invalid_op+0x1b/0x20
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? free_unref_page+0x30/0x180
   iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
   ? skb_free_head+0xa8/0xd0
   __napi_poll+0x30/0x1f0
   net_rx_action+0x181/0x2e0
   ? __irq_wake_thread+0x42/0x50
   __do_softirq+0xd9/0x349
   ? __pfx_irq_thread_fn+0x10/0x10
   do_softirq.part.0+0x41/0x80
   
   
   __local_bh_enable_ip+0x72/0x80
   iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
   irq_thread_fn+0x21/0x70
   irq_thread+0xf8/0x1c0
   ? __pfx_irq_thread_dtor+0x10/0x10
   ? __pfx_irq_thread+0x10/0x10
   kthread+0xef/0x120
   ? __pfx_kthread+0x10/0x10
   ret_from_fork+0x44/0x70
   ? __pfx_kthread+0x10/0x10
   ret_from_fork_asm+0x1b/0x30
   
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
  iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi :05:00.0: 0x | data3
  iwlwifi :05:00.0: 0xA0005E44 | beacon time
  iwlwifi :05:00.0: 0x2806818F | tsf low
  iwlwifi :05:00.0: 0x | tsf hi
  iwlwifi :05:00.0: 0x | time gp1
  iwlwifi :05:00.0: 0x0BB840A7 | time gp2
  iwlwifi :05:00.0: 0x0001 | uCode revision type
  iwlwifi :05:00.0: 0x0053 | uCode version major
  iwlwifi :05:00.0: 0xEC13314B | uCode

[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7

2024-03-27 Thread AaronMa

** Tags added: oem-priority originate-from-2057871 sutton

** Tags added: originate-from-2059064

** Description changed:

  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.
  
  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
-  xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
+  xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
-  
-  ? show_regs+0x6d/0x80
-  ? __warn+0x89/0x160
-  ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
-  ? report_bug+0x17e/0x1b0
-  ? handle_bug+0x46/0x90
-  ? exc_invalid_op+0x18/0x80
-  ? asm_exc_invalid_op+0x1b/0x20
-  ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
-  ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
-  ? free_unref_page+0x30/0x180
-  iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
-  ? skb_free_head+0xa8/0xd0
-  __napi_poll+0x30/0x1f0
-  net_rx_action+0x181/0x2e0
-  ? __irq_wake_thread+0x42/0x50
-  __do_softirq+0xd9/0x349
-  ? __pfx_irq_thread_fn+0x10/0x10
-  do_softirq.part.0+0x41/0x80
-  
-  
-  __local_bh_enable_ip+0x72/0x80
-  iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
-  irq_thread_fn+0x21/0x70
-  irq_thread+0xf8/0x1c0
-  ? __pfx_irq_thread_dtor+0x10/0x10
-  ? __pfx_irq_thread+0x10/0x10
-  kthread+0xef/0x120
-  ? __pfx_kthread+0x10/0x10
-  ret_from_fork+0x44/0x70
-  ? __pfx_kthread+0x10/0x10
-  ret_from_fork_asm+0x1b/0x30
-  
+  
+  ? show_regs+0x6d/0x80
+  ? __warn+0x89/0x160
+  ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
+  ? report_bug+0x17e/0x1b0
+  ? handle_bug+0x46/0x90
+  ? exc_invalid_op+0x18/0x80
+  ? asm_exc_invalid_op+0x1b/0x20
+  ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
+  ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
+  ? free_unref_page+0x30/0x180
+  iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
+  ? skb_free_head+0xa8/0xd0
+  __napi_poll+0x30/0x1f0
+  net_rx_action+0x181/0x2e0
+  ? __irq_wake_thread+0x42/0x50
+  __do_softirq+0xd9/0x349
+  ? __pfx_irq_thread_fn+0x10/0x10
+  do_softirq.part.0+0x41/0x80
+  
+  
+  __local_bh_enable_ip+0x72/0x80
+  iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
+  irq_thread_fn+0x21/0x70
+  irq_thread+0xf8/0x1c0
+  ? __pfx_irq_thread_dtor+0x10/0x10
+  ? __pfx_irq_thread+0x10/0x10
+  kthread+0xef/0x120
+  ? __pfx_kthread+0x10/0x10
+  ret_from_fork+0x44/0x70
+  ? __pfx_kthread+0x10/0x10
+  ret_from_fork_asm+0x1b/0x30
+  
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
- iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN   
+ iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi :05:00.0: 0x | data3
  iwlwifi :05:00.0: 0xA0005E44 | beacon time
  iwlwifi

[Kernel-packages] [Bug 2059248] Re: noble/linux-intel: 6.8.0-1001.1 -proposed tracker

2024-03-27 Thread Thibf

** Summary changed:

- noble/linux-intel:  -proposed tracker
+ noble/linux-intel: 6.8.0-1001.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thibf (thibf)

** Changed in: kernel-sru-workflow/prepare-package-generate
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-generate
 Assignee: (unassigned) => Thibf (thibf)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thibf (thibf)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thibf (thibf)

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Noble)

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

Title:
  noble/linux-intel: 6.8.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow boot-testing series:
  New
Status in Kernel SRU Workflow new-review series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-generate series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow sru-review series:
  New
Status in linux-intel source package in Noble:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  packages:
generate: linux-generate-intel
main: linux-intel
meta: linux-meta-intel
signed: linux-signed-intel
  phase: Packaging
  phase-changed: Wednesday, 27. March 2024 12:25 UTC
  reason:
:prepare-packages: 'Ongoing -b Being cranked by: thibf'
prepare-package: Pending -- tag not published and package not
  uploaded
prepare-package-generate: Pending -- package not uploaded
prepare-package-meta: Pending -- tag not published and package not
  uploaded
prepare-package-signed: Pending -- tag not published and package not
  uploaded
  variant: debs
  ~~:
announce:
  swm-transition-crankable: 2024-03-27 12:21:41.495196
clamps:
  self: 6.8.0-1001.1
tracker:
  last-message: '2024-03-27 12:18:28.343962+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/2059248/+subscriptions


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

[Kernel-packages] [Bug 2059248] Re: noble/linux-intel: -proposed tracker

2024-03-27 Thread Ubuntu Kernel Bot

** Changed in: kernel-sru-workflow/abi-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/boot-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/new-review
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-generate
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/sru-review
   Importance: Undecided => Medium

** Changed in: linux-intel (Ubuntu Noble)
   Importance: Undecided => Medium

** Tags added: kernel-block-derivatives

** Changed in: kernel-sru-workflow
   Status: Confirmed => Triaged

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ packages:
+   generate: linux-generate-intel
+   main: linux-intel
+   meta: linux-meta-intel
+   signed: linux-signed-intel
+ phase: Ready for Packaging
+ phase-changed: Wednesday, 27. March 2024 12:21 UTC
+ reason:
+   :prepare-packages: Pending -b Debs ready to be cranked
+   prepare-package: Pending -- version not specified
  variant: debs
+ ~~:
+   announce:
+ swm-transition-crankable: 2024-03-27 12:21:41.495196
+   tracker:
+ last-message: '2024-03-27 12:18:28.343962+00:00'

** Changed in: kernel-sru-workflow
   Status: Triaged => In Progress

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

Title:
  noble/linux-intel: 6.8.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow boot-testing series:
  New
Status in Kernel SRU Workflow new-review series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-generate series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow sru-review series:
  New
Status in linux-intel source package in Noble:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  packages:
generate: linux-generate-intel
main: linux-intel
meta: linux-meta-intel
signed: linux-signed-intel
  phase: Packaging
  phase-changed: Wednesday, 27. March 2024 12:25 UTC
  reason:
:prepare-packages: 'Ongoing -b Being cranked by: thibf'
prepare-package: Pending -- tag not published and package

[Kernel-packages] [Bug 2059248] [NEW] noble/linux-intel: 6.8.0-1001.1 -proposed tracker

2024-03-27 Thread Thibf

Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
packages:
  generate: linux-generate-intel
  main: linux-intel
  meta: linux-meta-intel
  signed: linux-signed-intel
phase: Ready for Packaging
phase-changed: Wednesday, 27. March 2024 12:21 UTC
reason:
  :prepare-packages: Pending -b Debs ready to be cranked
  prepare-package: Pending -- version not specified
variant: debs
~~:
  announce:
swm-transition-crankable: 2024-03-27 12:21:41.495196
  tracker:
last-message: '2024-03-27 12:18:28.343962+00:00'

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/abi-testing
 Importance: Medium
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/boot-testing
 Importance: Medium
 Status: New

** Affects: kernel-sru-workflow/new-review
 Importance: Medium
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Thibf (thibf)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-generate
 Importance: Medium
 Assignee: Thibf (thibf)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Thibf (thibf)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Thibf (thibf)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-signing-to-proposed
 Importance: Medium
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/sru-review
 Importance: Medium
 Status: New

** Affects: linux-intel (Ubuntu Noble)
 Importance: Medium
 Status: New


** Tags: kernel-block-derivatives kernel-release-tracking-bug 
kernel-release-tracking-bug-live kernel-sru-cycle-d2024.02.29-1 noble

** Tags added: kernel-release-tracking-bug-live

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ -- swm properties --
+ variant: debs

** Tags added: kernel-sru-cycle-d2024.02.29-1

** Changed in: kernel-sru-workflow
   Status: New => Confirmed

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu)
   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/2059248

Title:
  noble/linux-intel: 6.8.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow boot-testing series:
  New
Status in Kernel SRU Workflow new-review series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-generate series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow sru-review series:
  New
Status in linux-intel source package in Noble:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  packages:
generate: linux-generate-intel
main: linux-intel
meta: linux-meta-intel
signed: linux-signed-intel
  phase: Ready for Packaging

[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

And another quick question:
on which systems does that happen?
P9 (bare-metal or PowerVM) or P10 (PowerVM) or KVM on Power?

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

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
  [0.512032] LR [] 0x0
  [0.512034] --- interrupt: 3000
  [0.512036] ---[ end trace ]---
  [0.518326] systemd[1]: Inserted module 'autofs4'
  [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode 
(+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL 
+ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP 
+LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
  [0.521583] systemd[1]: Detected virtualization powervm.
  [0.521589] systemd[1]: Detected architecture ppc64-le.
  [0.521593] systemd[1]: Running in initrd.
  [0.521743] systemd[1]: No hostname configured, using default hostname.
  [0.521789] systemd[1]: Hostname set to .
  [0.521847] systemd[1]: Initializing machine ID from random generator.
  [0.600736] systemd[1]: Queued start job for default target initrd.target.

  
   
  Machine Type = P10  LPAR 
   
  Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com 
   
  ---Steps to Reproduce---
  1. reboot the system
  2. Once the system is booted back, look at dmesg
   
  ---uname output---
  Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  Additional Information:
  Same trace messages are seen on L2 guest as well.

  == Comment: - Kowshik

[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

Hello Kowshik Jois, thanks for raising our attention on this.

I apologize, but once a Launchpad ticket got closed (for example as Fix 
Released), like with LP#2055126, it is no longer actively monitored anymore (by 
our team), hence we missed your additional comments.
(I just found your comments, after I explicitly opened it again ...)

In addition I personally didn't recognized LP#2052767, since it wasn't
opened via the Bugzilla-to-Launchpad bridge, hence wasn't marked as
affecting the 'The Ubuntu-power-systems project', which is what we
actively monitor.

But anyway, each problem needs it's own Launchpad entry, so it was correct to 
open this one here.
(I'll just mark LP#2052767 as a duplicate of this one, LP#2059237).
___

So it looks like this happens with a kernel 6.6 (info taken from LP#2052767: 
linux-6.6.0 - is this an upstream kernel build that you did by yourself? Since 
- afair - we never had a kernel 6.6 in noble/24.04, just a 6.7.)
and with kernel 6.8.0-11 (from the bug description here) - that is the one we 
currently have in the daily IOSs.

There is already an updated kernel available from our "-proposed" pocket.
$ rmadison --arch=ppc64el --suite=noble,noble-proposed linux-generic
 linux-generic | 6.8.0-11.11+1 | noble  | ppc64el
 linux-generic | 6.8.0-20.20+1 | noble-proposed | ppc64el <==
Would you mind installing and trying the 6.8.0-20 from proposed, to see if that 
(very latest) kernel still shows this 'UBSAN: array-index-out-of-bounds' issue?

** Changed in: ubuntu-power-systems
   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/2059237

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
  [0.512032] LR

[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

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

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
  [0.512032] LR [] 0x0
  [0.512034] --- interrupt: 3000
  [0.512036] ---[ end trace ]---
  [0.518326] systemd[1]: Inserted module 'autofs4'
  [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode 
(+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL 
+ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP 
+LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
  [0.521583] systemd[1]: Detected virtualization powervm.
  [0.521589] systemd[1]: Detected architecture ppc64-le.
  [0.521593] systemd[1]: Running in initrd.
  [0.521743] systemd[1]: No hostname configured, using default hostname.
  [0.521789] systemd[1]: Hostname set to .
  [0.521847] systemd[1]: Initializing machine ID from random generator.
  [0.600736] systemd[1]: Queued start job for default target initrd.target.

  
   
  Machine Type = P10  LPAR 
   
  Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com 
   
  ---Steps to Reproduce---
  1. reboot the system
  2. Once the system is booted back, look at dmesg
   
  ---uname output---
  Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  Additional Information:
  Same trace messages are seen on L2 guest as well.

  == Comment: -

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

2024-03-27 Thread Bug Watch Updater

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

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

Title:
  btmgmt --index broken in Mantic

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  On Mantic:

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

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

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

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

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


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

[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

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

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
(unassigned)

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

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

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

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment:- Kowshik Jois B S ==
  ---Problem Description---
  Below trace messges are observed in dmesg after every reboot.

  
  [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [0.475750] Freeing unused kernel image (initmem) memory: 8832K
  [0.507388] Checked W+X mappings: passed, no W+X pages found
  [0.507400] Run /init as init process
  [0.507403]   with arguments:
  [0.507404] /init
  [0.507405]   with environment:
  [0.507406] HOME=/
  [0.507407] TERM=linux
  [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
  [0.511892] [ cut here ]
  [0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
  [0.511909] index 0 is out of range for type 'char [*]'
  [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
  [0.511921] Call Trace:
  [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
  [0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
  [0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
  [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
  [0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
  [0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
  [0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
  [0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
  [0.511972] --- interrupt: 3000 at 0x7879b903b8a8
  [0.511977] NIP:  7879b903b8a8 LR:  CTR: 

  [0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
  [0.511984] MSR:  8000f033   CR: 
48222428  XER: 
  [0.511993] IRQMASK: 0 
 GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
 GPR04: 7879b8e0c160 0004 0010 
0004 
 GPR08: 0001   
 
 GPR12:  7879b99d3a00 2000 
0002 
 GPR16:   1b5c7d7453e0 
7fffd683ba68 
 GPR20:   1b5c82154ae0 
1b5c82142360 
 GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
 GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
  [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
  [0.512032] LR [] 0x0
  [0.512034] --- interrupt: 3000
  [0.512036] ---[ end trace ]---
  [0.518326] systemd[1]: Inserted module 'autofs4'
  [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode 
(+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL 
+ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP 
+LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
  [0.521583] systemd[1]: Detected virtualization powervm.
  [0.521589] systemd[1]: Detected architecture ppc64-le.
  [0.521593] systemd[1]: Running in initrd.
  [0.521743] systemd[1]: No hostname configured, using default hostname.
  [0.521789] systemd[1]: Hostname set to .
  [0.521847] systemd[1]: Initializing machine ID from random generator.
  [0.600736] systemd[1]: Queued start job for default target initrd.target.

  
   
  Machine Type = P10  LPAR 
   
  Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com 
   
  ---Steps to

[Kernel-packages] [Bug 2058948] Re: Focal update: v5.4.269 upstream stable release

Skipped "jfs: fix uaf in jfs_evict_inode" because it is already applied
as CVE-2023-52600.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52600

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

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

Title:
  Focal update: v5.4.269 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  PCI: mediatek: Clear interrupt status before dispatching handler
  include/linux/units.h: add helpers for kelvin to/from Celsius conversion
  units: Add Watt units
  units: change from 'L' to 'UL'
  units: add the HZ macros
  serial: sc16is7xx: set safe default SPI clock frequency
  spi: introduce SPI_MODE_X_MASK macro
  serial: sc16is7xx: add check for unsupported SPI modes during probe
  ext4: allow for the last group to be marked as trimmed
  crypto: api - Disallow identical driver names
  PM: hibernate: Enforce ordering during image compression/decompression
  hwrng: core - Fix page fault dead lock on mmap-ed hwrng
  rpmsg: virtio: Free driver_override when rpmsg_remove()
  parisc/firmware: Fix F-extend for PDC addresses
  arm64: dts: qcom: sdm845: fix USB wakeup interrupt types
  mmc: core: Use mrq.sbc in close-ended ffu
  nouveau/vmm: don't set addr on the fail path to avoid warning
  ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
  rename(): fix the locking of subdirectories
  block: Remove special-casing of compound pages
  mtd: spinand: macronix: Fix MX35LFxGE4AD page size
  fs: add mode_strip_sgid() helper
  fs: move S_ISGID stripping into the vfs_*() helpers
  powerpc: Use always instead of always-y in for crtsavres.o
  x86/CPU/AMD: Fix disabling XSAVES on AMD family 0x17 due to erratum
  net/smc: fix illegal rmb_desc access in SMC-D connection dump
  vlan: skip nested type that is not IFLA_VLAN_QOS_MAPPING
  llc: make llc_ui_sendmsg() more robust against bonding changes
  llc: Drop support for ETH_P_TR_802_2.
  net/rds: Fix UBSAN: array-index-out-of-bounds in rds_cmsg_recv
  tracing: Ensure visibility when inserting an element into tracing_map
  afs: Hide silly-rename files from userspace
  tcp: Add memory barrier to tcp_push()
  netlink: fix potential sleeping issue in mqueue_flush_file
  net/mlx5: DR, Use the right GVMI number for drop action
  net/mlx5: Use kfree(ft->g) in arfs_create_groups()
  net/mlx5e: fix a double-free in arfs_create_groups
  netfilter: nf_tables: restrict anonymous set and map names to 16 bytes
  netfilter: nf_tables: validate NFPROTO_* family
  fjes: fix memleaks in fjes_hw_setup
  net: fec: fix the unhandled context fault from smmu
  btrfs: ref-verify: free ref cache before clearing mount opt
  btrfs: tree-checker: fix inline ref size in error messages
  btrfs: don't warn if discard range is not aligned to sector
  btrfs: defrag: reject unknown flags of btrfs_ioctl_defrag_range_args
  rbd: don't move requests to the running list on errors
  gpiolib: acpi: Ignore touchpad wakeup on GPD G1619-04
  drm: Don't unref the same fb many times by mistake due to deadlock handling
  drm/bridge: nxp-ptn3460: fix i2c_master_send() error checking
  drm/bridge: nxp-ptn3460: simplify some error checking
  drm/exynos: fix accidental on-stack copy of exynos_drm_plane
  drm/exynos: gsc: minor fix for loop iteration in gsc_runtime_resume
  gpio: eic-sprd: Clear interrupt after set the interrupt type
  spi: bcm-qspi: fix SFDP BFPT read by usig mspi read
  mips: Call lose_fpu(0) before initializing fcr31 in mips_set_personality_nan
  tick/sched: Preserve number of idle sleeps across CPU hotplug events
  x86/entry/ia32: Ensure s32 is sign extended to s64
  powerpc/mm: Fix null-pointer dereference in pgtable_cache_add
  powerpc: Fix build error due to is_valid_bugaddr()
  powerpc/mm: Fix build failures due to arch_reserved_kernel_pages()
  powerpc: pmd_move_must_withdraw() is only needed for 
CONFIG_TRANSPARENT_HUGEPAGE
  powerpc/lib: Validate size for vector operations
  x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel
  perf/core: Fix narrow startup race when creating the perf nr_addr_filters 
sysfs file
  regulator: core: Only increment use_count when enable_count changes
  audit: Send netlink ACK before setting connection in

[Kernel-packages] [Bug 2059014] Re: Jammy update: v5.15.149 upstream stable release

Skipped "jfs: fix uaf in jfs_evict_inode" since this was already applied
as CVE-2023-52600.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52600

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

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

Title:
  Jammy update: v5.15.149 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  ksmbd: free ppace array on error in parse_dacl
  ksmbd: don't allow O_TRUNC open on read-only share
  ksmbd: validate mech token in session setup
  ksmbd: fix UAF issue in ksmbd_tcp_new_connection()
  ksmbd: only v2 leases handle the directory
  iio: adc: ad7091r: Set alert bit in config register
  iio: adc: ad7091r: Allow users to configure device events
  iio: adc: ad7091r: Enable internal vref if external vref is not supplied
  dmaengine: fix NULL pointer in channel unregistration function
  scsi: ufs: core: Simplify power management during async scan
  scsi: ufs: core: Remove the ufshcd_hba_exit() call from ufshcd_async_scan()
  iio:adc:ad7091r: Move exports into IIO_AD7091R namespace.
  ext4: allow for the last group to be marked as trimmed
  btrfs: sysfs: validate scrub_speed_max value
  crypto: api - Disallow identical driver names
  PM: hibernate: Enforce ordering during image compression/decompression
  hwrng: core - Fix page fault dead lock on mmap-ed hwrng
  crypto: s390/aes - Fix buffer overread in CTR mode
  media: imx355: Enable runtime PM before registering async sub-device
  rpmsg: virtio: Free driver_override when rpmsg_remove()
  media: ov9734: Enable runtime PM before registering async sub-device
  mips: Fix max_mapnr being uninitialized on early stages
  bus: mhi: host: Drop chan lock before queuing buffers
  bus: mhi: host: Add spinlock to protect WP access when queueing TREs
  parisc/firmware: Fix F-extend for PDC addresses
  async: Split async_schedule_node_domain()
  async: Introduce async_schedule_dev_nocall()
  arm64: dts: qcom: sc7180: fix USB wakeup interrupt types
  arm64: dts: qcom: sdm845: fix USB wakeup interrupt types
  arm64: dts: qcom: sm8150: fix USB wakeup interrupt types
  arm64: dts: qcom: sdm845: fix USB DP/DM HS PHY interrupts
  lsm: new security_file_ioctl_compat() hook
  scripts/get_abi: fix source path leak
  mmc: core: Use mrq.sbc in close-ended ffu
  mmc: mmc_spi: remove custom DMA mapped buffers
  rtc: Adjust failure return code for cmos_set_alarm()
  nouveau/vmm: don't set addr on the fail path to avoid warning
  ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
  rename(): fix the locking of subdirectories
  ksmbd: set v2 lease version on lease upgrade
  ksmbd: fix potential circular locking issue in smb2_set_ea()
  ksmbd: don't increment epoch if current state and request state are same
  ksmbd: send lease break notification on FILE_RENAME_INFORMATION
  ksmbd: Add missing set_freezable() for freezable kthread
  net/smc: fix illegal rmb_desc access in SMC-D connection dump
  tcp: make sure init the accept_queue's spinlocks once
  bnxt_en: Wait for FLR to complete during probe
  vlan: skip nested type that is not IFLA_VLAN_QOS_MAPPING
  llc: make llc_ui_sendmsg() more robust against bonding changes
  llc: Drop support for ETH_P_TR_802_2.
  net/rds: Fix UBSAN: array-index-out-of-bounds in rds_cmsg_recv
  tracing: Ensure visibility when inserting an element into tracing_map
  afs: Hide silly-rename files from userspace
  tcp: Add memory barrier to tcp_push()
  netlink: fix potential sleeping issue in mqueue_flush_file
  ipv6: init the accept_queue's spinlocks in inet6_create
  net/mlx5: DR, Use the right GVMI number for drop action
  net/mlx5: DR, Align mlx5dv_dr API vport action with FW behavior
  net/mlx5: DR, Can't go to uplink vport on RX rule
  net/mlx5e: fix a double-free in arfs_create_groups
  net/mlx5e: fix a potential double-free in fs_any_create_groups
  overflow: Allow mixed type arguments
  netfilter: nft_limit: reject configurations that cause integer overflow
  netfilter: nf_tables: restrict anonymous set and map names to 16 bytes
  netfilter: nf_tables: validate NFPROTO_* family
  net: stmmac: Wait a bit for the reset to take effect
  net: mvpp2: clear BM pool before initialization
  selftests: netdevsim: fix

[Kernel-packages] [Bug 2059068] Re: Mantic update: upstream stable patchset 2024-03-26

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

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

Title:
  Mantic update: upstream stable patchset 2024-03-26

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

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2024-03-26

  Ported from the following upstream stable releases:
  v6.1.76, v6.6.15

 from git://git.kernel.org/

  iio: adc: ad7091r: Set alert bit in config register
  iio: adc: ad7091r: Allow users to configure device events
  ext4: allow for the last group to be marked as trimmed
  arm64: properly install vmlinuz.efi
  OPP: Pass rounded rate to _set_opp()
  btrfs: sysfs: validate scrub_speed_max value
  crypto: api - Disallow identical driver names
  PM: hibernate: Enforce ordering during image compression/decompression
  hwrng: core - Fix page fault dead lock on mmap-ed hwrng
  crypto: s390/aes - Fix buffer overread in CTR mode
  s390/vfio-ap: unpin pages on gisc registration failure
  PM / devfreq: Fix buffer overflow in trans_stat_show
  media: imx355: Enable runtime PM before registering async sub-device
  rpmsg: virtio: Free driver_override when rpmsg_remove()
  media: ov9734: Enable runtime PM before registering async sub-device
  s390/vfio-ap: always filter entire AP matrix
  s390/vfio-ap: loop over the shadow APCB when filtering guest's AP 
configuration
  s390/vfio-ap: let on_scan_complete() callback filter matrix and update 
guest's APCB
  mips: Fix max_mapnr being uninitialized on early stages
  bus: mhi: host: Add alignment check for event ring read pointer
  bus: mhi: host: Drop chan lock before queuing buffers
  bus: mhi: host: Add spinlock to protect WP access when queueing TREs
  parisc/firmware: Fix F-extend for PDC addresses
  parisc/power: Fix power soft-off button emulation on qemu
  async: Split async_schedule_node_domain()
  async: Introduce async_schedule_dev_nocall()
  iio: adc: ad7091r: Enable internal vref if external vref is not supplied
  dmaengine: fix NULL pointer in channel unregistration function
  scsi: ufs: core: Remove the ufshcd_hba_exit() call from ufshcd_async_scan()
  arm64: dts: qcom: sc7180: fix USB wakeup interrupt types
  arm64: dts: qcom: sdm845: fix USB wakeup interrupt types
  arm64: dts: qcom: sm8150: fix USB wakeup interrupt types
  arm64: dts: qcom: sc7280: fix usb_1 wakeup interrupt types
  arm64: dts: qcom: sdm845: fix USB DP/DM HS PHY interrupts
  arm64: dts: qcom: sm8150: fix USB DP/DM HS PHY interrupts
  lsm: new security_file_ioctl_compat() hook
  docs: kernel_abi.py: fix command injection
  scripts/get_abi: fix source path leak
  media: videobuf2-dma-sg: fix vmap callback
  mmc: core: Use mrq.sbc in close-ended ffu
  mmc: mmc_spi: remove custom DMA mapped buffers
  media: mtk-jpeg: Fix use after free bug due to error path handling in 
mtk_jpeg_dec_device_run
  arm64: Rename ARM64_WORKAROUND_2966298
  rtc: cmos: Use ACPI alarm for non-Intel x86 systems too
  rtc: Adjust failure return code for cmos_set_alarm()
  rtc: mc146818-lib: Adjust failure return code for mc146818_get_time()
  rtc: Add support for configuring the UIP timeout for RTC reads
  rtc: Extend timeout for waiting for UIP to clear to 1s
  nouveau/vmm: don't set addr on the fail path to avoid warning
  ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
  mm/rmap: fix misplaced parenthesis of a likely()
  mm/sparsemem: fix race in accessing memory_section->usage
  rename(): fix the locking of subdirectories
  serial: sc16is7xx: improve regmap debugfs by using one regmap per port
  serial: sc16is7xx: remove wasteful static buffer in sc16is7xx_regmap_name()
  serial: sc16is7xx: remove global regmap from struct sc16is7xx_port
  serial: sc16is7xx: remove unused line structure member
  serial: sc16is7xx: change EFR lock to operate on each channels
  serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO
  serial: sc16is7xx: fix invalid sc16is7xx_lines bitfield in case of probe error
  serial: sc16is7xx: remove obsolete loop in sc16is7xx_port_irq()
  serial: sc16is7xx: improve do/while loop in sc16is7xx_irq()
  LoongArch/smp: Call rcutree_report_cpu_starting() earlier
  mm: page_alloc: unreserve highatomic page blocks before oom
  ksmbd: set v2 lease version on lease upgrade
  ksmbd: fix

[Kernel-packages] [Bug 2059237] [NEW] [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

Public bug reported:

== Comment:- Kowshik Jois B S ==
---Problem Description---
Below trace messges are observed in dmesg after every reboot.


[0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
[0.475750] Freeing unused kernel image (initmem) memory: 8832K
[0.507388] Checked W+X mappings: passed, no W+X pages found
[0.507400] Run /init as init process
[0.507403]   with arguments:
[0.507404] /init
[0.507405]   with environment:
[0.507406] HOME=/
[0.507407] TERM=linux
[0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
[0.511892] [ cut here ]
[0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
[0.511909] index 0 is out of range for type 'char [*]'
[0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
[0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
[0.511921] Call Trace:
[0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
[0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
[0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
[0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
[0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
[0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
[0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
[0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
[0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
[0.511972] --- interrupt: 3000 at 0x7879b903b8a8
[0.511977] NIP:  7879b903b8a8 LR:  CTR: 
[0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
[0.511984] MSR:  8000f033   CR: 
48222428  XER: 
[0.511993] IRQMASK: 0 
   GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
   GPR04: 7879b8e0c160 0004 0010 
0004 
   GPR08: 0001   
 
   GPR12:  7879b99d3a00 2000 
0002 
   GPR16:   1b5c7d7453e0 
7fffd683ba68 
   GPR20:   1b5c82154ae0 
1b5c82142360 
   GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
   GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
[0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
[0.512032] LR [] 0x0
[0.512034] --- interrupt: 3000
[0.512036] ---[ end trace ]---
[0.518326] systemd[1]: Inserted module 'autofs4'
[0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM 
+AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL 
+BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK 
+PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[0.521583] systemd[1]: Detected virtualization powervm.
[0.521589] systemd[1]: Detected architecture ppc64-le.
[0.521593] systemd[1]: Running in initrd.
[0.521743] systemd[1]: No hostname configured, using default hostname.
[0.521789] systemd[1]: Hostname set to .
[0.521847] systemd[1]: Initializing machine ID from random generator.
[0.600736] systemd[1]: Queued start job for default target initrd.target.


 
Machine Type = P10  LPAR 
 
Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com 
 
---Steps to Reproduce---
1. reboot the system
2. Once the system is booted back, look at dmesg
 
---uname output---
Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 
ppc64le ppc64le ppc64le GNU/Linux
 
 
Additional Information:
Same trace messages are seen on L2 guest as well.

== Comment: - Kowshik Jois B S ==
Hello Likhitha,

The ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/2055126 was
created for tracking a different issue which is resolved. I just posted
a question about this issue as well at the end. But its been 20 days and
we haven't heard anything back on that. Also, the bug is already closed.
So I think it makes sense to initiate a new discussion with ubuntu on
this issue.

Earlier I had initiated a discussion through
https://bugs.launchpad.net/ubuntu/+bug/2052767 but no updates on that
one as well till now.


As you mentioned, compiled upstream kernel by disabling the UBSAN in the

[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7

2024-03-27 Thread Timo Aaltonen

** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux (Ubuntu)

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

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

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

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

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

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

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

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

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

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

Title:
  iwlwifi disconnect and crash - intel wifi7

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

Bug description:
  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
   xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
   
   ? show_regs+0x6d/0x80
   ? __warn+0x89/0x160
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? report_bug+0x17e/0x1b0
   ? handle_bug+0x46/0x90
   ? exc_invalid_op+0x18/0x80
   ? asm_exc_invalid_op+0x1b/0x20
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? free_unref_page+0x30/0x180
   iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
   ? skb_free_head+0xa8/0xd0
   __napi_poll+0x30/0x1f0
   net_rx_action+0x181/0x2e0
   ? __irq_wake_thread+0x42/0x50
   __do_softirq+0xd9/0x349
   ? __pfx_irq_thread_fn+0x10/0x10
   do_softirq.part.0+0x41/0x80
   
   
   __local_bh_enable_ip+0x72/0x80
   iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
   irq_thread_fn+0x21/0x70
   irq_thread+0xf8/0x1c0
   ? __pfx_irq_thread_dtor+0x10/0x10
   ? __pfx_irq_thread+0x10/0x10
   kthread+0xef/0x120
   ? __pfx_kthread+0x10/0x10
   ret_from_fork+0x44/0x70
   ? __pfx_kthread+0x10/0x10
   ret_from_fork_asm+0x1b/0x30
   
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
  iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN   
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi

[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7

2024-03-27 Thread AaronMa

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
 Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu)

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
   Status: New => In Progress

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

Title:
  iwlwifi disconnect and crash - intel wifi7

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

Bug description:
  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
   xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
   
   ? show_regs+0x6d/0x80
   ? __warn+0x89/0x160
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? report_bug+0x17e/0x1b0
   ? handle_bug+0x46/0x90
   ? exc_invalid_op+0x18/0x80
   ? asm_exc_invalid_op+0x1b/0x20
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? free_unref_page+0x30/0x180
   iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
   ? skb_free_head+0xa8/0xd0
   __napi_poll+0x30/0x1f0
   net_rx_action+0x181/0x2e0
   ? __irq_wake_thread+0x42/0x50
   __do_softirq+0xd9/0x349
   ? __pfx_irq_thread_fn+0x10/0x10
   do_softirq.part.0+0x41/0x80
   
   
   __local_bh_enable_ip+0x72/0x80
   iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
   irq_thread_fn+0x21/0x70
   irq_thread+0xf8/0x1c0
   ? __pfx_irq_thread_dtor+0x10/0x10
   ? __pfx_irq_thread+0x10/0x10
   kthread+0xef/0x120
   ? __pfx_kthread+0x10/0x10
   ret_from_fork+0x44/0x70
   ? __pfx_kthread+0x10/0x10
   ret_from_fork_asm+0x1b/0x30
   
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
  iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN   
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi :05:00.0: 0x | data3
  iwlwifi :05:00.0: 0xA0005E44 | beacon time
  iwlwifi :05:00.0: 0x2806818F | tsf low
  iwlwifi :05:00.0: 0x | tsf hi
  iwlwifi :05:00.0: 0x | time gp1
  iwlwifi :05:00.0: 0x0BB840A7 | time gp2
  iwlwifi :05:00.0: 0x0001 | uCode revision type
  iwlwifi :05:00.0: 0x0053 | uCode version major
  iwlwifi :05:00.0: 0xEC13314B | uCode version minor
  iwlwifi :05:00.0: 0x0472

[Kernel-packages] [Bug 2059237] [NEW] [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot

You have been subscribed to a public bug:

== Comment:- Kowshik Jois B S ==
---Problem Description---
Below trace messges are observed in dmesg after every reboot.


[0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
[0.475750] Freeing unused kernel image (initmem) memory: 8832K
[0.507388] Checked W+X mappings: passed, no W+X pages found
[0.507400] Run /init as init process
[0.507403]   with arguments:
[0.507404] /init
[0.507405]   with environment:
[0.507406] HOME=/
[0.507407] TERM=linux
[0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic
[0.511892] [ cut here ]
[0.511904] UBSAN: array-index-out-of-bounds in 
/build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17
[0.511909] index 0 is out of range for type 'char [*]'
[0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic 
#11-Ubuntu
[0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries
[0.511921] Call Trace:
[0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
[0.511931] [c6683650] [c0c7bc58] 
__ubsan_handle_out_of_bounds+0xc4/0x12c
[0.511938] [c6683700] [c005d2a8] 
module_frob_arch_sections+0x4ec/0x8d0
[0.511943] [c66837e0] [c02b98cc] 
layout_and_allocate.isra.0+0x38/0x2a8
[0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0
[0.511953] [c6683990] [c02baca8] 
init_module_from_file+0xb4/0x14c
[0.511958] [c6683a70] [c02baf70] 
sys_finit_module+0x230/0x48c
[0.511963] [c6683b80] [c0033248] 
system_call_exception+0xe8/0x240
[0.511967] [c6683e50] [c000d15c] 
system_call_vectored_common+0x15c/0x2ec
[0.511972] --- interrupt: 3000 at 0x7879b903b8a8
[0.511977] NIP:  7879b903b8a8 LR:  CTR: 
[0.511980] REGS: c6683e80 TRAP: 3000   Not tainted  
(6.8.0-11-generic)
[0.511984] MSR:  8000f033   CR: 
48222428  XER: 
[0.511993] IRQMASK: 0 
   GPR00: 0161 7fffd683b580 7879b9166d00 
0004 
   GPR04: 7879b8e0c160 0004 0010 
0004 
   GPR08: 0001   
 
   GPR12:  7879b99d3a00 2000 
0002 
   GPR16:   1b5c7d7453e0 
7fffd683ba68 
   GPR20:   1b5c82154ae0 
1b5c82142360 
   GPR24: 7879b957f7b0 1b5c82154ae0  
1b5c82142160 
   GPR28: 7879b8e0c160 0002 1b5c82154ae0 
1b5c82142380 
[0.512029] NIP [7879b903b8a8] 0x7879b903b8a8
[0.512032] LR [] 0x0
[0.512034] --- interrupt: 3000
[0.512036] ---[ end trace ]---
[0.518326] systemd[1]: Inserted module 'autofs4'
[0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM 
+AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL 
+BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK 
+PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[0.521583] systemd[1]: Detected virtualization powervm.
[0.521589] systemd[1]: Detected architecture ppc64-le.
[0.521593] systemd[1]: Running in initrd.
[0.521743] systemd[1]: No hostname configured, using default hostname.
[0.521789] systemd[1]: Hostname set to .
[0.521847] systemd[1]: Initializing machine ID from random generator.
[0.600736] systemd[1]: Queued start job for default target initrd.target.


 
Machine Type = P10  LPAR 
 
Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com 
 
---Steps to Reproduce---
1. reboot the system
2. Once the system is booted back, look at dmesg
 
---uname output---
Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 
ppc64le ppc64le ppc64le GNU/Linux
 
 
Additional Information:
Same trace messages are seen on L2 guest as well.

== Comment: - Kowshik Jois B S ==
Hello Likhitha,

The ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/2055126 was
created for tracking a different issue which is resolved. I just posted
a question about this issue as well at the end. But its been 20 days and
we haven't heard anything back on that. Also, the bug is already closed.
So I think it makes sense to initiate a new discussion with ubuntu on
this issue.

Earlier I had initiated a discussion through
https://bugs.launchpad.net/ubuntu/+bug/2052767 but no updates on that
one as well till now.


As you mentioned, compiled upstream kernel by

[Kernel-packages] [Bug 2045093] Re: After waking from sleep moving to a different virtual desktop shows a black screen on X11

2024-03-27 Thread Scarlett Gately Moore

I cannot reproduce this with intel graphics. Adding nvidia.

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

** Changed in: plasma-desktop (Ubuntu)
Status: New => Triaged

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

Title:
After waking from sleep moving to a different virtual desktop shows a
black screen on X11

Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in plasma-desktop package in Ubuntu:
Triaged

Bug description:
After enabling Virtual Desktops when I wake up from sleep and switch
desktops I get a black screen.

Steps:

1. Log in with Plasma on X11
2. In System Settings select Workspace Behaviour > Virtual Desktops
3. Create a layout of 2x2 (two rows with two desktops each)
4. Put the system to sleep
5. Wake the system up and enter your credentials
6. Switch to a different desktop to the one you are wither with a key
combination or clicking on it on the taskbar.

Outcome:

A black screen will be shown instead of the desktop. If you try to go
back to the original desktop you will still have a black screen.

Expectation:
For the system to switch virtual desktops without any issues.

Workaround:

1. Change virtual terminals using Control-Alt-F4, for example.
2. Change back to the GUI virtual terminal with Control-Alt-F1
3. The graphical interface is restored and you can switch between virtual
desktops without problems.

Alternatively I imagine that removing virtual desktops would work, but that
reduces functionality.

Things I tried:

1. I purged all the nvidia drivers and installed the last version 535.
It worked briefly but it quickly reverted to the same issue.

2. I have tried login using Plasma on Wayland and I can't reproduce
the problem. Unfortunately I have some applications that aren't
supported yet that require using X11.

Additional information:

$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

$ apt-cache policy plasma-desktop
plasma-desktop:
Installed: 4:5.24.7-0ubuntu0.1
Candidate: 4:5.24.7-0ubuntu0.1
Version table:
*** 4:5.24.7-0ubuntu0.1 500
500
https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu
jammy-updates/universe amd64 Packages
100 /var/lib/dpkg/status
4:5.24.4-0ubuntu1 500
500
https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu
jammy/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: plasma-desktop 4:5.24.7-0ubuntu0.1
ProcVersionSignature: Ubuntu 6.5.0-10008.8-hostname 6.5.3
Uname: Linux 6.5.0-10008-tuxedo x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 29 01:56:19 2023
SourcePackage: plasma-desktop
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2021-08-23T10:06:34.221827

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

[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops

2024-03-27 Thread Bin Li

Installed the 2.0-1ubuntu4.7 version of firmware-sof-signed on the
previously failed ThinkPad platforms. Confirmed that now the LEDs can
toggle accordingly.

** Tags added: originate-from-2047202 sutton

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

Title:
  Enable the mic-mute led on Dell MTL laptops

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

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]
  On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is 
working but the LED(on F4) state is not changed accordingly.

  [Fix]
  There's no problem on the same series on RPL platform. It needs MTL specific 
SoF driver and controls to support the registered mixer switch. It requires the 
patches in 
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
 and 
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only required for new sof-audio-pci-intel-mtl driver. The impact should 
be restricting.

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Intel MTL powered laptops.

  [Fix]
  For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add 
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the 
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control 
matches with the updated driver.

  [Test Case]
  1. enable -proposed pocket and install firmware-sof-signed
  2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.

  [Where problems could occur]
  The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all 
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.

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


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

[Kernel-packages] [Bug 2059159] Re: Mantic update: upstream stable patchset 2024-03-26

2024-03-27 Thread Manuel Diewald

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

** This bug has been marked a duplicate of bug 2059068
   Mantic update: upstream stable patchset 2024-03-26

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

Title:
  Mantic update: upstream stable patchset 2024-03-26

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

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2024-03-26
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2059230] [NEW] enable CONFIG_INTEL_TDX_HOST in linux >= 6.8 for noble

2024-03-27 Thread Thibf

Public bug reported:

[Impact]

Intel Trust Domain Extensions (TDX) protects guest VMs from malicious host and 
certain physical attacks.
Linux 6.7 introduced the TDX support for the host to run confidential VMs (TDX 
guests).

Bug #2046040 enabled TDX_HOST on noble but that was disabled when
updating to 6.8 as this was committed:

cb8eb06d50fcf4 x86/virt/tdx: Disable TDX host support when kexec is
enabled

[Test case]

We should probably define with Intel a proper test case to test this
feature, since it requires special hardware/firmware support.

[Fix]

Enable CONFIG_INTEL_TDX_HOST in our generic kernel.

[Regression potential]

The TDX host support may introduce potential performance regressions, so
we should probably do some performance evaluation with vs without
CONFIG_INTEL_TDX_HOST enabled.

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

Title:
   enable CONFIG_INTEL_TDX_HOST in linux >= 6.8 for noble

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

Bug description:
  [Impact]

  Intel Trust Domain Extensions (TDX) protects guest VMs from malicious host 
and certain physical attacks.
  Linux 6.7 introduced the TDX support for the host to run confidential VMs 
(TDX guests).

  Bug #2046040 enabled TDX_HOST on noble but that was disabled when
  updating to 6.8 as this was committed:

  cb8eb06d50fcf4 x86/virt/tdx: Disable TDX host support when kexec is
  enabled

  [Test case]

  We should probably define with Intel a proper test case to test this
  feature, since it requires special hardware/firmware support.

  [Fix]

  Enable CONFIG_INTEL_TDX_HOST in our generic kernel.

  [Regression potential]

  The TDX host support may introduce potential performance regressions,
  so we should probably do some performance evaluation with vs without
  CONFIG_INTEL_TDX_HOST enabled.

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


-- 
Mailing list: https://launchpad.net/~kernel-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] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

This LP bug was entirely s390x specific, hence not affecting any other platform.
So setting verification again to done, to potentially unblock any further 
processes.

** Tags removed: verification-needed-jammy-linux-nvidia-6.5
** Tags added: verification-done verification-done-jammy-linux-nvidia-6.5

-- 
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 Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

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-z-systems/+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 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough