[Kernel-packages] [Bug 2079841] Re: Revert fix for "Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM"

2024-10-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1004.4

---
linux-azure (6.11.0-1004.4) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1004.4 -proposed tracker (LP: #2080828)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from kernel-versions
  (main/d2024.09.16)

  * Revert fix for "Kernel fails to enable XSAVE when running in a “v5” AMD SEV-
SNP VM" (LP: #2079841)
- Revert "UBUNTU: SAUCE: x86/hyperv: temporarily disable CET SS on SEV-SNP 
due
  to a paravisor bug"

  * Miscellaneous Ubuntu changes
- [Packaging] involflt dkms FTBFS on amd64, disable it temporarily
- [Packaging] Don't force bindgen version
- [Config] updateconfigs following Ubuntu-6.11.0-8.8 rebase

  [ Ubuntu: 6.11.0-8.8 ]

  * oracular/linux: 6.11.0-8.8 -proposed tracker (LP: #2080825)
  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.08.12)
  * [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after v6.10
(LP: #2080322)
- [Config] disable CONFIG_TCG_TPM2_HMAC by default
  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
(LP: #2071698)
- Documentation: hid: intel-ish-hid: Add vendor custom firmware loading
- HID: intel-ish-hid: Use CPU generation string in driver_data
- hid: intel-ish-hid: Add support for vendor customized firmware loading
  * Miscellaneous Ubuntu changes
- [Packaging] Purge obsolete upstart files
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64
- [Config] Update toolchain versions
- SAUCE: rust: Fix rustc source path for the new rustc packaging
- [Packaging] Don't force bindgen version
- [Config] Re-enable rust support for amd64

 -- Paolo Pisati   Mon, 30 Sep 2024 11:13:37
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  Revert fix for "Kernel fails to enable XSAVE when running in a “v5”
  AMD SEV-SNP VM"

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Committed
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * LP #2069204 disabled CET Shadow Stack on SEV-SNP due to CPUID emulation bug 
not being fixed in VMs until October 2024.
  * This issue is now fixed, so the patch can be reverted.

  [Fix]

  * Revert "UBUNTU: SAUCE: x86/hyperv: temporarily disable CET SS on
  SEV-SNP due to a paravisor bug"

  [Test Plan]

  * Compile tested
  * Boot tested

  [Regression potential]

  * Reverting back to previous state, so regression very unlikely.
  * Changes isolated, minimal regression risk

  [Other info]

  * SF #00387447

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2079841/+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 2078689] Re: New upstream release 550.90.12 ERD5

2024-10-03 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-550-server -
550.90.12-0ubuntu2

---
nvidia-graphics-drivers-550-server (550.90.12-0ubuntu2) oracular; urgency=medium

  * libnvidia-compute-550-server should provide libcuda1 (LP: #2081723)

 -- Kuba Pawlak   Mon, 23 Sep 2024 16:50:22
+0200

** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Oracular)
   Status: New => Fix Released

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

Title:
  New upstream release 550.90.12 ERD5

Status in fabric-manager-550 package in Ubuntu:
  New
Status in libnvidia-nscq-550 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  Fix Released
Status in nvidia-imex-550 package in Ubuntu:
  New
Status in fabric-manager-550 source package in Focal:
  New
Status in libnvidia-nscq-550 source package in Focal:
  New
Status in nvidia-graphics-drivers-550-server source package in Focal:
  New
Status in nvidia-imex-550 source package in Focal:
  New
Status in fabric-manager-550 source package in Jammy:
  New
Status in libnvidia-nscq-550 source package in Jammy:
  New
Status in nvidia-graphics-drivers-550-server source package in Jammy:
  New
Status in nvidia-imex-550 source package in Jammy:
  New
Status in fabric-manager-550 source package in Noble:
  New
Status in libnvidia-nscq-550 source package in Noble:
  New
Status in nvidia-graphics-drivers-550-server source package in Noble:
  New
Status in nvidia-imex-550 source package in Noble:
  New
Status in fabric-manager-550 source package in Oracular:
  New
Status in libnvidia-nscq-550 source package in Oracular:
  New
Status in nvidia-graphics-drivers-550-server source package in Oracular:
  Fix Released
Status in nvidia-imex-550 source package in Oracular:
  New

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

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

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

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

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

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

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-550/+bug/2078689/+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 2081723] Re: libnvidia-compute-560 should provide libcuda1

2024-10-03 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-550-server -
550.90.12-0ubuntu2

---
nvidia-graphics-drivers-550-server (550.90.12-0ubuntu2) oracular; urgency=medium

  * libnvidia-compute-550-server should provide libcuda1 (LP: #2081723)

 -- Kuba Pawlak   Mon, 23 Sep 2024 16:50:22
+0200

** Changed in: nvidia-graphics-drivers-550-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  libnvidia-compute-560 should provide libcuda1

Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-560 package in Ubuntu:
  Fix Released

Bug description:
  the gpu-burn package is uninstallable, because libnivida-compute
  stopped providing the libcuda1 virtual package. Please re-add that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2081723/+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 2077529] [NEW] DELL EMC UBUNTU24.04.1 BUG]: observed:4xxx 0000:01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2

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

Description: After installing Ubuntu 24.04.1 on a development environment, 
(DELL EMC poweredge system) we observed that dmesg log show below message 
 
   4xxx :0b:00.0: Direct firmware load for qat_402xx_mmp.bin failed with 
error 
   -2
   4xxx :0b:00.0: Failed to load MMP firmware qat_402xx_mmp.bin
   4xxx :0b:00.0: Failed to load acceleration FW
   4xxx: probe of :0b:00.0 failed with error -14
we did the root cause and came to know that Intel firmware was missing as intel 
has not upstream the firmware for QAT 402XX deivce. Request you to please pull 
the fix for the ubuntu 24.04.1 upcoming builds as the Intel has release the 
firmware for the QAT402XX, link below 
 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/

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


** Tags: bot-comment
-- 
DELL EMC UBUNTU24.04.1 BUG]: observed:4xxx :01:00.0: Direct firmware load 
for qat_402xx_mmp.bin failed with error -2
https://bugs.launchpad.net/bugs/2077529
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware in Ubuntu.

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


[Kernel-packages] [Bug 2079887] [NEW] Core dump within gstreamer lib using kernel 6.10.4-061004-generic

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

I am running audio players Sayonara and Clementine on my Mint Linux
system (on a Core I3-6100 system). Recently I tried Mainline Kernel
6.10.4 and 6.10.5. I was running my favorite audio player Sayonara and
immediately it crashed with a core dump when doing a call into a
gstreamer function. This error also happens with Clementine player which
is also based on gstreamer library.

There is no such error using Kernel 6.9.12 to which I returned after the
crash.

Here is the relevant part of the stack trace.

 Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.2.amd64
   Module libzstd.so.1 from deb 
libzstd-1.5.5+dfsg2-2build1.amd64
   Stack trace of thread 10114:
   #0  0x71315923e004 n/a (n/a + 
0x0)
   #1  0x71315b473082 
gst_audio_ring_buffer_acquire (libgstaudio-1.0.so.0 + 0x60082)cat 
/proc/version_signature > version.log
   #2  0x71315b44c18a n/a 
(libgstaudio-1.0.so.0 + 0x3918a)
   #3  0x713166fb9f5c n/a 
(libgstbase-1.0.so.0 + 0x36f5c)
   #4  0x713166fb4a34 n/a 
(libgstbase-1.0.so.0 + 0x31a34)
   #5  0x71316724bfdd n/a 
(libgstreamer-1.0.so.0 + 0x97fdd)
   #6  0x71316724c6bd n/a 
(libgstreamer-1.0.so.0 + 0x986bd)
   #7  0x71316724ce88 n/a 
(libgstreamer-1.0.so.0 + 0x98e88)
   #8  0x713167241535 n/a 
(libgstreamer-1.0.so.0 + 0x8d535)
   #9  0x713167250081 
gst_pad_push_event (libgstreamer-1.0.so.0 + 0x9c081)

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


** Tags: bot-comment
-- 
Core dump within gstreamer lib using  kernel 6.10.4-061004-generic
https://bugs.launchpad.net/bugs/2079887
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-oem-6.10 in Ubuntu.

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


[Kernel-packages] [Bug 2083255] Re: Restore erofs.ko to linux-modules

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

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

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

Title:
  Restore erofs.ko to linux-modules

Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/2081613 and
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809, erofs.ko
  is missing from linux-aws.

  A fix has already been accepted to linux-azure:
  https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  azure/+git/jammy/commit/?id=c7fec922603a7ff52bd037f6ce6791b08f1cfaef

  Can we get this into linux-aws as well? Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2083255/+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 2083077] [NEW] python3 counting 6x slowdown with ubuntu22 on cisco ucs hardware with hyperthreading

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

I suspect this is a kernel bug.

With ubuntu <= 21, I find that this runs in about 13 seconds:

python3 -c "import timeit; print(timeit.Timer('for _ in range(0,1000):
pass').timeit())"

With ubuntu >= 22, I find that it runs in about 83 seconds.

The problem seems to be specific to Cisco UCS hardware and can be mostly
mitigated by disabling hyperthreading.

I also tried counting to a million a thousand times instead of counting
to 1000 a million times (this is how many times timeit runs the
experiment), just in case the time-measuring was the slow part, but it
made no difference.  Even just a straight up loop without using timeit
shows about the same difference.

Originally, I encountered this when upgrading from 18 to 24.  We went
back and isolated the problem to something that changed between 21 and
22.  The version I actually care about is 24.

The only Cisco UCS systems we have are a bunch of Cisco UCS C220 M5SX
rack servers and a bunch of Cisco UCS B200 M5 blades.  All of them show
the regression.  I can confirm that on a variety of similarly-specced
supermicro systems, the regression does not occur.

The problem can be easily reproduced by booting off
https://releases.ubuntu.com/24.04.1/ubuntu-24.04.1-live-server-amd64.iso
(or various other versions) and dropping into a shell.  The installer
kernel behaves the same as the installed kernel across the various
versions.  So it should be possible for anyone with this hardware to
reproduce the issue by using the installer shells.  You may wish to use
an old python3 from a version-pinned docker image to get an apples-to-
apples comparison.

If I run the experiment inside ubuntu18 containers on ubuntu21 and
ubuntu22 I can see that I still get the dramatically different runtimes.
i.e., the kernel version and not the userland or python version is what
seems to matter.

We have tried mitigations=off with no effect.

We have tried reverting various kernel scheduler configuration changes
back to their ubuntu21 settings with no effect.

We have tried disabling hyperthreading in the BIOS.  This had an
enormous effect.  It reduces runtime from 83 seconds to 17 seconds.  17
is still 30% slower than 13, but it is obviously way better than 83.

So just to recap:
13s: ubuntu21 with hyperthreading on
83s: ubuntu22 with hyperthreading on
17s: ubuntu22 with hyperthreading off

This machine has 2 sockets with 20 physical cores each for a total of 80
logical cores once we account for hyperthreading.

Ideally I would prefer not to be forced to disable hyperthreading.  Even
if that is not possible, I am interested in avoiding the remaining 30%
slowdown.

sysbench --test=cpu and sysbench --test=memory also both exhibit a
slowdown, but it is more like a 30% slowdown instead of 800%, even with
hyperthreading turned on.

I have used perf to profile python and found the time was spread out--
did not see any particular smoking gun.  The python process makes < 300
syscalls over its entire lifetime and virtually no context switches.  I
tried running it with realtime priority with affinity for a single core,
which seemed to make little difference.  The python process uses 100% of
a cpu as it runs.

Any ideas?

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


** Tags: bot-comment
-- 
python3 counting 6x slowdown with ubuntu22 on cisco ucs hardware with 
hyperthreading
https://bugs.launchpad.net/bugs/2083077
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2082946] Re: Kernel 6.8.0-45-generic fails to boot on 24.04

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

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

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

Title:
  Kernel 6.8.0-45-generic fails to boot on 24.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system is an ASUS Vivobook laptop with a Intel Core i7 chipset.
  Yesterday the updates brought in a new kernel image: 6.8.0-45-generic.
  Boot has failed since, apparently it is not able to find the root
  volume and drops back to the initramfs prompt. No error messages are
  shown during the failed boot process, however, when I try to quit the
  initramfs prompt a few messages appear (see image attached).

  With the original kernel (6.8.0-44-generic) the system boots fine and
  the HDD is working as expected. The contents of the `fstab` file are
  below.

  ```
  $ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a device; this 
may
  # be used with UUID= as a more robust way to name devices that works even if
  # disks are added and removed. See fstab(5).
  #
  #  
  UUID=F8F9-FF58/boot/efi  vfatdefaults   0 
2
  UUID=e13ff5f9-7a98-4e01-873f-b1a0fd440c77 /  ext4defaults   0 
1
  UUID=5d3a8f7f-d08f-4f65-bcda-55d3fa5f6cbd /home  ext4defaults   0 
2
  /swapfile none   swapsw   0 0
  tmpfs /tmp   tmpfs   
defaults,noatime,mode=1777 0 0
  ```

  Please let me know if I can provide further information. Thank you for
  reading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2082946/+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 2081225] [NEW] 24 LTS upgrade broke my Ubuntu 22 OS - lost data & had to rebuild from scratch; OS locks up ~ 50 % of the time when asking for file actions: like copy to or just

2024-09-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

doing a lot of reset or power cycling to get back to work

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.22
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports:
 640:120:109:5023786:2024-09-18 11:25:46.939001321 -0600:2024-09-18 
17:28:38.780026516 -0600:/var/crash/_usr_bin_gnome-shell.120.crash
 640:1000:109:5350864:2024-09-17 16:40:50.881726264 -0600:2024-09-17 
16:40:51.881726264 -0600:/var/crash/_usr_bin_shotwell.1000.crash
 644:0:109:0:2024-09-18 17:28:38.726026397 -0600:2024-09-18 17:28:38.726026397 
-0600:/var/crash/_usr_bin_gnome-shell.120.upload
 600:107:109:37:2024-09-18 17:28:39.852028899 -0600:2024-09-18 
17:28:39.851028897 -0600:/var/crash/_usr_bin_gnome-shell.120.uploaded
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 19 15:10:15 2024
InstallationDate: Installed on 2024-09-16 (3 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade noble wayland-session
-- 
24 LTS upgrade broke my Ubuntu 22 OS - lost data & had to rebuild from scratch; 
OS locks up ~ 50 % of the time when asking for file actions: like copy to or 
just opening a flash drive
https://bugs.launchpad.net/bugs/2081225
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1753489] Re: kernel BUG at /build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!

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

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

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

Title:
  kernel BUG at /build/linux-hwe-Fuabdm/linux-
  hwe-4.13.0/fs/jbd2/transaction.c:1868!

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Expired

Bug description:
  [ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
  [ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
  [ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
  [ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
  [ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
  [ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
  [ 1678.547111] pc : [] lr : [] pstate: 
80400145
  [ 1678.556071] sp : 801f633ffb70
  [ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
  [ 1678.567890] x27:  x26: 801ecd5776e8
  [ 1678.574845] x25:  x24: 01400040
  [ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
  [ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
  [ 1678.595787] x19: 801f4a18ea50 x18: 
  [ 1678.602807] x17:  x16: 
  [ 1678.609844] x15: ddd41681 x14: 3a7accb0
  [ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46
  [ 1678.623964] x11: 801f79729770 x10: 093c8c08
  [ 1678.631058] x9 : 001d x8 : 801ecd577750
  [ 1678.638182] x7 :  x6 : 0001
  [ 1678.645323] x5 :  x4 : 0040
  [ 1678.652468] x3 : 0016 x2 : 801f6d655a28
  [ 1678.659633] x1 :  x0 : 801f6d655a00
  [ 1678.666808] Process jbd2/dm-1-8 (pid: 776, stack limit = 
0x801f633fc000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753489/+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 1753489] Re: kernel BUG at /build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!

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

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

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

Title:
  kernel BUG at /build/linux-hwe-Fuabdm/linux-
  hwe-4.13.0/fs/jbd2/transaction.c:1868!

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Expired

Bug description:
  [ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
  [ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
  [ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
  [ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
  [ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
  [ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
  [ 1678.547111] pc : [] lr : [] pstate: 
80400145
  [ 1678.556071] sp : 801f633ffb70
  [ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
  [ 1678.567890] x27:  x26: 801ecd5776e8
  [ 1678.574845] x25:  x24: 01400040
  [ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
  [ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
  [ 1678.595787] x19: 801f4a18ea50 x18: 
  [ 1678.602807] x17:  x16: 
  [ 1678.609844] x15: ddd41681 x14: 3a7accb0
  [ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46
  [ 1678.623964] x11: 801f79729770 x10: 093c8c08
  [ 1678.631058] x9 : 001d x8 : 801ecd577750
  [ 1678.638182] x7 :  x6 : 0001
  [ 1678.645323] x5 :  x4 : 0040
  [ 1678.652468] x3 : 0016 x2 : 801f6d655a28
  [ 1678.659633] x1 :  x0 : 801f6d655a00
  [ 1678.666808] Process jbd2/dm-1-8 (pid: 776, stack limit = 
0x801f633fc000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753489/+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 2075179] Re: package linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2024-09-29 Thread Launchpad Bug Tracker
[Expired for linux-signed-lts-xenial (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: linux-signed-lts-xenial (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed-lts-xenial package in Ubuntu:
  Expired

Bug description:
  I think this is kernel error because it stopped at the linux-
  image-4.4.0-148-generic

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Tue Jul 30 16:59:23 2024
  DuplicateSignature: 
package:linux-image-4.4.0-148-generic:4.4.0-148.174~14.04.1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2024-07-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 
(20190304.5)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.24
  SourcePackage: linux-signed-lts-xenial
  Title: package linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lts-xenial/+bug/2075179/+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 2083018] [NEW] Intermittent screen flickering observed after upgrading to 24.04 LTS from 22.04 LTS

2024-09-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I am observing screen that my Dell screen flickers once in a while for a
short duration (about 5 secs or so) after upgrading to latest LTS. The
problem is 100 % reproducible on my computer by holding the left mouse
button pressed while dragging the scrollbar. Even otherwise this
flickering is observed automatically about 3-4 times in a span of 20
mins.

Expected Behaviour: The screen does not flicker automatically or while
scrolling a web page.

Package version: 
xorg:
  Installed: 1:7.7+23ubuntu3
  Candidate: 1:7.7+23ubuntu3
  Version table:
 *** 1:7.7+23ubuntu3 500
500 http://in.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status

LSB_Release Information: 
Description:Ubuntu 24.04.1 LTS
Release:24.04

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 15:46:00 2024
DistUpgraded: 2024-09-27 13:45:39,634 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+bolt-l+X51
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08bc]
InstallationDate: Installed on 2019-10-17 (1807 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 413c:301b Dell Computer Corp. Universal Bluetooth 
Receiver
 Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 3400
ProcEnviron:
 LANG=en_IN
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=2fb9395f-2fe4-4c97-ac45-70c28b10ef1d ro mem_sleep_default=deep quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-09-27 (0 days ago)
dmi.bios.date: 08/06/2024
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0GTC5X
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd08/06/2024:br1.33:svnDellInc.:pnLatitude3400:pvr:rvnDellInc.:rn0GTC5X:rvrA00:cvnDellInc.:ct10:cvr:sku08BC:
dmi.product.family: Latitude
dmi.product.name: Latitude 3400
dmi.product.sku: 08BC
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T20:29:07
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu wayland-session
-- 
Intermittent screen flickering observed after upgrading to 24.04 LTS from 22.04 
LTS
https://bugs.launchpad.net/bugs/2083018
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2081244] [NEW] Nvidia driver fails to load with secure boot

2024-09-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When my screen blanks from inactivity timeout the backlight stays on,
for multiple hours and does not turn off ever.

Additional Notes:

* "Everything else" appears to be working fine. I can move my mouse, enter 
password on lock screen, and resume doing whatever I was doing normally, 
nothing else is "stuck"
* This is a dual boot machine, on the Win11 side of things there are no issues.
* Monitor connected over display port.
* This was also a problem in Ubuntu 22 which was installed before the 24 
upgrade.
* This has been consistently happening for a number of months.
* FWIW The monitor in question is a Asus PG32UQR.

Happy to provide any other additional info required or further help
debug.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13
Uname: Linux 6.5.0-44-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 19 18:45:03 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus: nvidia/550.107.02, 6.5.0-44-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. AD102 [GeForce RTX 4090] [1043:88e2]
InstallationDate: Installed on 2024-04-27 (145 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: ASUS System Product Name
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/fish
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-44-generic 
root=UUID=3d5956d7-e387-44fa-8e27-e437aad3feda ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2024
dmi.bios.release: 15.3
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: Default string
dmi.board.name: ROG MAXIMUS Z790 DARK HERO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/07/2024:br15.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ790DARKHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu
-- 
Nvidia driver fails to load with secure boot
https://bugs.launchpad.net/bugs/2081244
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-550 in Ubuntu.

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


[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash

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

** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
   Status: New => Confirmed

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

Title:
  No video after wake from S3 due to Nvidia driver crash

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-09-28 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.7.9

---
ubuntu-drivers-common (1:0.9.7.9) oracular; urgency=medium

  [ Kuba Pawlak ]
  * Sort the output list of matching nvidia drivers (LP: #2081970)
  * NVIDIA 560 release should suggest -open variant first (LP: #2081967)

  [ Alessandro Astone ]
  * Improve SimpleDRM+NVIDIA fix across kernel versions (LP: #2060268)

 -- Kuba Pawlak   Thu, 26 Sep 2024 10:27:26
+0200

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Won't Fix
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still
  controlled by simpledrm, while Nvidia uses /dev/dri/card1.

  This also seems to be triggering bug 2062426 and bug 2066126.

  [ Temporary Workaround ]

  1. sudo rm /dev/dri/card0
  2. Log in again.

  [ Permanent Workaround ]

  Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init
  Beware that this has side-effects: see comment #37

  [ Test Plan - Nvidia case ]

  1. Set up a DESKTOP where the only GPU enabled is an Nvidia one.
  2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
  3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 
'nvidia' and not 'nouveau').
  4. Open Settings and verify the only monitors shown are your real monitors.

  [ Regression Test Plan - Intel/AMD graphics ]

  1. Set up a machine with integrated graphics only.
  2. Reboot.
  3. Verify that you are able to log into the Ubuntu Desktop Wayland session.
  4. Run `apt install nvidia-driver-535`.
  5. Reboot.
  6. Verify that you are able to log into the Ubuntu Desktop Wayland session.

  [ Regression Test Plan - Virtual machines ]

  1. Set up a virtual machine without any graphics acceleration (vmware, 
virtio...)
  2. Reboot.
  3. Verify that you are able to log into the Ubuntu Desktop Wayland session.
  4. Run `sudo apt install nvidia-driver-535`.
  5. Reboot.
  6. Verify that you are able to log into the Ubuntu Desktop Wayland session.
  7. Optionally go back to point 4, and try with nvidia-driver-550.

  [ Regression Test Plan - Nvidia+LUKS ]

  1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted 
disk.
  2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
  3. Reboot
  4. Verify that you see the password prompt for decrypting the disk.

  [ Where problems could occur ]

  Removing the simpledrm card is only safe when it's not being used. If
  somehow a machine wasn't using the installed Nvidia driver then there
  could be a risk of deleting the only working display.

  One case where this could happen is if the Nvidia driver would allow
  being loaded even without any nvidia hardware present: if that is the
  case, "Regression Test Plan - Virtual machines" would fail.

  [ Other Info ]

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble

[Kernel-packages] [Bug 2069148] Re: display black on boot, updated from 23.10 to 24.04

2024-09-27 Thread Launchpad Bug Tracker
[Expired for nvidia-graphics-drivers-470 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  display black on boot, updated from 23.10 to 24.04

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Expired

Bug description:
  card: NVIDIA GF108 GeForce GT730   pci id  10de:0f02

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
  Uname: Linux 6.8.0-35-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jun 12 14:26:09 2024
  DistUpgraded: 2024-06-11 01:29:38,064 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/470.239.06, 6.8.0-35-generic, x86_64: installed
   virtualbox/7.0.16, 6.5.0-41-generic, x86_64: installed
   virtualbox/7.0.16, 6.8.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF108 [GeForce GT 730] [10de:]
  InstallationDate: Installed on 2023-04-17 (422 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Gigabyte Technology Co., Ltd. Z690 AORUS ELITE DDR4
  ProcEnviron:
   LANG=de_DE.UTF-8
   LANGUAGE=
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-35-generic 
root=UUID=e51b9515-bb82-4152-82c2-93dae3c0f1b8 ro quiet
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to noble on 2024-06-10 (2 days ago)
  dmi.bios.date: 03/09/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: Z690 AORUS ELITE DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF23:bd03/09/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690AORUSELITEDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690AORUSELITEDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Z690 MB
  dmi.product.name: Z690 AORUS ELITE DDR4
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2069148/+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 2074301] Re: Kernel 5.15.0-117 has bug similiar to 113 & 116

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

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

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

Title:
  Kernel 5.15.0-117 has bug similiar to 113 & 116

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi, kernel 5.15.0-117 has the same problem as 5.15.0-113 and
  5.15.0-116 with playing video and youtube. I was forced to downgrade
  to most stable 5.15.0-112. Playing youtube it stuttered and repeated
  short fragment 0.5- 1 c endless, all system got frozen. I use Linux
  Mint Cinnamon 21.1

  log impportant:

  wpa_supplicant
  bgscan simple: Failed to enable signal strength monitoring

  pulseaudio
  GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074301/+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 2082946] [NEW] Kernel 6.8.0-45-generic fails to boot on 24.04

2024-09-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The system is an ASUS Vivobook laptop with a Intel Core i7 chipset.
Yesterday the updates brought in a new kernel image: 6.8.0-45-generic.
Boot has failed since, apparently it is not able to find the root volume
and drops back to the initramfs prompt. No error messages are shown
during the failed boot process, however, when I try to quit the
initramfs prompt a few messages appear (see image attached).

With the original kernel (6.8.0-44-generic) the system boots fine and
the HDD is working as expected. The contents of the `fstab` file are
below.

```
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
#  
UUID=F8F9-FF58/boot/efi  vfatdefaults   0 2
UUID=e13ff5f9-7a98-4e01-873f-b1a0fd440c77 /  ext4defaults   0 1
UUID=5d3a8f7f-d08f-4f65-bcda-55d3fa5f6cbd /home  ext4defaults   0 2
/swapfile none   swapsw   0 0
tmpfs /tmp   tmpfs   
defaults,noatime,mode=1777 0 0
```

Please let me know if I can provide further information. Thank you for
reading.

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

-- 
Kernel 6.8.0-45-generic fails to boot on 24.04
https://bugs.launchpad.net/bugs/2082946
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2082946] [NEW] Kernel 6.8.0-45-generic fails to boot on 24.04

2024-09-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The system is an ASUS Vivobook laptop with a Intel Core i7 chipset.
Yesterday the updates brought in a new kernel image: 6.8.0-45-generic.
Boot has failed since, apparently it is not able to find the root volume
and drops back to the initramfs prompt. No error messages are shown
during the failed boot process, however, when I try to quit the
initramfs prompt a few messages appear (see image attached).

With the original kernel (6.8.0-44-generic) the system boots fine and
the HDD is working as expected. The contents of the `fstab` file are
below.

```
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
#  
UUID=F8F9-FF58/boot/efi  vfatdefaults   0 2
UUID=e13ff5f9-7a98-4e01-873f-b1a0fd440c77 /  ext4defaults   0 1
UUID=5d3a8f7f-d08f-4f65-bcda-55d3fa5f6cbd /home  ext4defaults   0 2
/swapfile none   swapsw   0 0
tmpfs /tmp   tmpfs   
defaults,noatime,mode=1777 0 0
```

Please let me know if I can provide further information. Thank you for
reading.

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

-- 
Kernel 6.8.0-45-generic fails to boot on 24.04
https://bugs.launchpad.net/bugs/2082946
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2074262] Re: thinkbook volume buttons don't work

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

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

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

Title:
  thinkbook volume buttons don't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  My laptop is a thinkbook 14 g6 abp and this issue occurs on every
  distro I tried and in different desktop environments. If I quickly tap
  or hold down either volume key; the key will then repeatedly press
  itself forever even after I stop holding the button. The only way to
  stop it by pressing either key for a specific amount of time which
  will make it change the volume normally.

  The distros I tried were:
  Kubuntu 24.04 (plasma)
  Linux Mint 21.3 (cinnamon)
  Fedora 40 (plasma)
  Debian 12.6 (xfce)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074262/+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 2074238] Re: Missing U.2 MVMe drives on Ubuntu 22.04 with disabled SR-IOV in the BIOS

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

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

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

Title:
  Missing U.2 MVMe drives on Ubuntu 22.04 with disabled SR-IOV in the
  BIOS

Status in linux package in Ubuntu:
  Expired

Bug description:
  This is a configuration issue rather than an OS kernel or BIOS
  firmware bug. Although, the symptom manifest only on Ubuntu OS (other
  Linux OSes such as RHEL does NOT have this issue) with a disabled SR-
  IOV at the AMD server's BIOS. Also, only AMD servers with GPU that are
  affected by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074238/+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 2074264] Re: porblem with wifi (usb card)

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

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

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

Title:
  porblem with wifi (usb card)

Status in linux package in Ubuntu:
  Expired

Bug description:
  In this moment i have problem with use mi wi/fi network previus of
  update of 17 of july this was working ok , the problem i can see n the
  network in general , the navigation is very slow , and besides the
  problem persis with ethernet usb card (improve anythings) , the same
  computer with a debian function ok , i am thinking the problem may be
  usb , beacuase the mouse is working bad in ubuntu , thanks for your
  time

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-modules-usbio-generic (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:mauricio   2350 F pipewire
   /dev/snd/controlC1:  mauricio   2353 F wireplumber
   /dev/snd/controlC0:  mauricio   2353 F wireplumber
   /dev/snd/controlC2:  mauricio   2353 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 09:59:52 2024
  InstallationDate: Installed on 2024-07-07 (20 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-39-generic 
root=UUID=26f62941-03a2-441d-b088-2d2c53a83a46 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-39-generic N/A
   linux-backports-modules-6.8.0-39-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/28/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074264/+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 2082448] [NEW] horizontal lines bottom of screen

2024-09-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

roughly 25 lines appear at bottom  of display in uefi, grup, and after boot. (1 
mm apart)
When a window arrive at bottom of of the screen the lines pattern change : they 
become 2 mm apart.
They do not appear in screenshot.

Using additional drivers interface I tried to change from nvidia 535 to
550 idem and also nouveau : the problem persist.

It seems the problem appeared after update of linux-firmware

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.06  Wed Jun 26 
06:46:07 UTC 2024
 GCC version:
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 17:57:08 2024
DistUpgraded: 2024-05-26 12:50:11,629 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Raptor Lake-S UHD Graphics [8086:a788] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Tongfang Hongkong Limited Raptor Lake-S UHD Graphics [1d05:1272]
 NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile] [10de:28e0] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Tongfang Hongkong Limited AD107M [GeForce RTX 4060 Max-Q / 
Mobile] [1d05:1272]
InstallationDate: Installed on 2023-05-04 (511 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: PCSpecialist GM7PX0N
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=25e4cf8c-b384-43d7-9370-094089037d88 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-05-26 (123 days ago)
dmi.bios.date: 02/03/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: N.1.06A00
dmi.board.asset.tag: Standard
dmi.board.name: GM7PX0N
dmi.board.vendor: TongFang
dmi.board.version: Standard
dmi.chassis.asset.tag: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: Standard
dmi.chassis.version: Standard
dmi.ec.firmware.release: 0.29
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.06A00:bd02/03/2023:br5.27:efr0.29:svnPCSpecialist:pnGM7PX0N:pvrStandard:rvnTongFang:rnGM7PX0N:rvrStandard:cvnStandard:ct10:cvrStandard:sku0001:
dmi.product.family: RPL
dmi.product.name: GM7PX0N
dmi.product.sku: 0001
dmi.product.version: Standard
dmi.sys.vendor: PCSpecialist
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption noble ubuntu
-- 
horizontal lines bottom of screen
https://bugs.launchpad.net/bugs/2082448
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2082225] Re: Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then resume from suspend

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

** Changed in: linux (Ubuntu Noble)
   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/2082225

Title:
  Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then
  resume from suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  In Progress
Status in linux source package in Oracular:
  In Progress
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Reproduce Steps]
  1. Clean Install Ubuntu 24.04 image with USB Key
  2. Boot to Ubuntu OS
  3. Plug WD22TB4 with TBT3 HDD.
  4. Let system enter suspend.
  5. Wait 1-min.
  6. Unplug WD22TB4.
  7. Press anykey wake system from suspend. <--Service LED will show 1A8W.

  [Results]
  Expected Result:System will normal resume from suspend.
  Actual Result:Service LED show 1A8W

  [Additional Information]
  This issue will VNP when WD22TB4 without TBT HDD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2082225/+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 2076180] Re: Add new firmwares for 6.8 hwe kernel

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2076180

Title:
  Add new firmwares for 6.8 hwe kernel

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

[Kernel-packages] [Bug 2065829] Re: BTF support missing from kernel

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi - 6.11.0-1003.3

---
linux-raspi (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-raspi: 6.11.0-1003.3 -proposed tracker (LP: #2080020)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.raspi/dkms-versions -- update from kernel-versions
  (main/devel)

  * Miscellaneous Ubuntu changes
- raspi: Update to upstream raspberrypi rpi-6.11.y (2024-09-09)
- [Config] raspi: enable driver for new HiFiBerry ADC only board
- [Config] raspi: updateconfigs after rebase to Ubuntu-6.11.0-7.7

  * Miscellaneous upstream changes
- Bluetooth: hci_sync: Fix crash on NULL parent
- overlays: add overlay for generic I2S clock-master DAC
- ASoC: DACplusADCPro - put ADC control definitions in header file
- configs: Add I2C_HID_OF to Pi defconfigs
- drm: rp1: rp1-dsi: Add DRM_FORMAT_ARGB and DRM_FORMAT_ABGR
- drm: rp1: rp1-dpi: Add DRM_FORMAT_ARGB and DRM_FORMAT_ABGR
- drm: rp1: rp1-vec: Add DRM_FORMAT_ARGB and DRM_FORMAT_ABGR
- drm/vc4: Add a delay after disabling hdmi phy output
- drm/vc4: Implement vc6_hdmi_phy_disable
- drm/vc4: Also power down the PLL core when resetting PHY
- ASoC: add driver for new HiFiBerry ADC only board(s)
- overlays: Add overlay for Hifiberry ADC
- configs: Add Hifiberry ADC to the defconfigs
- drivers: drm: rp1-dsi: Implement more DSI options and flags
- rtc: pcf8523: Fix oscillator stop bit handling reading from Control_1
- drivers: media: pci: Update Hailo accelerator device driver to v4.18.0
- media/rpivid: Make SPS / PPS optional in a request
- configs: Add remaining USB_SERIAL modules
- drivers: media: pci: Fix Hailo compile warnings

  [ Ubuntu: 6.11.0-7.7 ]

  * oracular/linux: 6.11.0-7.7 -proposed tracker (LP: #2079949)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [1/99]: LSM: Infrastructure management of the sock
  security
- SAUCE: apparmor4.0.0 [2/99]: LSM: Add the lsmblob data structure.
- SAUCE: apparmor4.0.0 [3/99]: LSM: Use lsmblob in security_audit_rule_match
- SAUCE: apparmor4.0.0 [4/99]: LSM: Call only one hook for audit rules
- SAUCE: apparmor4.0.0 [5/99]: LSM: Add lsmblob_to_secctx hook
- SAUCE: apparmor4.0.0 [6/99]: Audit: maintain an lsmblob in audit_context
- SAUCE: apparmor4.0.0 [7/99]: LSM: Use lsmblob in security_ipc_getsecid
- SAUCE: apparmor4.0.0 [8/99]: Audit: Update shutdown LSM data
- SAUCE: apparmor4.0.0 [9/99]: LSM: Use lsmblob in security_current_getsecid
- SAUCE: apparmor4.0.0 [10/99]: LSM: Use lsmblob in security_inode_getsecid
- SAUCE: apparmor4.0.0 [11/99]: Audit: use an lsmblob in audit_names
- SAUCE: apparmor4.0.0 [12/99]: LSM: Create new security_cred_getlsmblob LSM
  hook
- SAUCE: apparmor4.0.0 [13/99]: Audit: Change context data from secid to
  lsmblob
- SAUCE: apparmor4.0.0 [14/99]: Netlabel: Use lsmblob for audit data
- SAUCE: apparmor4.0.0 [15/99]: LSM: Ensure the correct LSM context releaser
- SAUCE: apparmor4.0.0 [16/99]: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [17/99]: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [18/99]: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [19/99]: LSM: lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [20/99]: LSM: security_lsmblob_to_secctx module
  selection
- SAUCE: apparmor4.0.0 [21/99]: Audit: Create audit_stamp structure
- SAUCE: apparmor4.0.0 [22/99]: Audit: Allow multiple records in an
  audit_buffer
- SAUCE: apparmor4.0.0 [23/99]: Audit: Add record for multiple task security
  contexts
- SAUCE: apparmor4.0.0 [24/99]: audit: multiple subject lsm values for
  netlabel
- SAUCE: apparmor4.0.0 [25/99]: Audit: Add record for multiple object 
contexts
- SAUCE: apparmor4.0.0 [26/99]: LSM: Remove unused lsmcontext_init()
- SAUCE: apparmor4.0.0 [27/99]: LSM: Improve logic in security_getprocattr
- SAUCE: apparmor4.0.0 [28/99]: LSM: secctx provider check on release
- SAUCE: apparmor4.0.0 [29/99]: LSM: Single calls in socket_getpeersec hooks
- SAUCE: apparmor4.0.0 [30/99]: LSM: Exclusive secmark usage
- SAUCE: apparmor4.0.0 [31/99]: LSM: Identify which LSM handles the context
  string
- SAUCE: apparmor4.0.0 [32/99]: AppArmor: Remove the exclusive flag
- SAUCE: apparmor4.0.0 [33/99]: LSM: Add mount opts blob size tracking
- SAUCE: apparmor4.0.0 [34/99]: LSM: allocate mnt_opts blobs instead of 
module
  specific data
- SAUCE: apparmor4.0.0 [35/99]: LSM: Infrastructure management of the key
  security blob
- SAUCE: apparmor4.0.0 [36/99]: LSM: Infrastructure management of the 
mnt_opts
  security blob
- SAUCE: apparmor4.0.0 [37/99]: LSM: Remove lsmblob scaffolding
- SAUCE: apparmor4.0

[Kernel-packages] [Bug 2060240] Re: Pi DAC+ fails on Pi 5

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi - 6.11.0-1003.3

---
linux-raspi (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-raspi: 6.11.0-1003.3 -proposed tracker (LP: #2080020)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.raspi/dkms-versions -- update from kernel-versions
  (main/devel)

  * Miscellaneous Ubuntu changes
- raspi: Update to upstream raspberrypi rpi-6.11.y (2024-09-09)
- [Config] raspi: enable driver for new HiFiBerry ADC only board
- [Config] raspi: updateconfigs after rebase to Ubuntu-6.11.0-7.7

  * Miscellaneous upstream changes
- Bluetooth: hci_sync: Fix crash on NULL parent
- overlays: add overlay for generic I2S clock-master DAC
- ASoC: DACplusADCPro - put ADC control definitions in header file
- configs: Add I2C_HID_OF to Pi defconfigs
- drm: rp1: rp1-dsi: Add DRM_FORMAT_ARGB and DRM_FORMAT_ABGR
- drm: rp1: rp1-dpi: Add DRM_FORMAT_ARGB and DRM_FORMAT_ABGR
- drm: rp1: rp1-vec: Add DRM_FORMAT_ARGB and DRM_FORMAT_ABGR
- drm/vc4: Add a delay after disabling hdmi phy output
- drm/vc4: Implement vc6_hdmi_phy_disable
- drm/vc4: Also power down the PLL core when resetting PHY
- ASoC: add driver for new HiFiBerry ADC only board(s)
- overlays: Add overlay for Hifiberry ADC
- configs: Add Hifiberry ADC to the defconfigs
- drivers: drm: rp1-dsi: Implement more DSI options and flags
- rtc: pcf8523: Fix oscillator stop bit handling reading from Control_1
- drivers: media: pci: Update Hailo accelerator device driver to v4.18.0
- media/rpivid: Make SPS / PPS optional in a request
- configs: Add remaining USB_SERIAL modules
- drivers: media: pci: Fix Hailo compile warnings

  [ Ubuntu: 6.11.0-7.7 ]

  * oracular/linux: 6.11.0-7.7 -proposed tracker (LP: #2079949)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [1/99]: LSM: Infrastructure management of the sock
  security
- SAUCE: apparmor4.0.0 [2/99]: LSM: Add the lsmblob data structure.
- SAUCE: apparmor4.0.0 [3/99]: LSM: Use lsmblob in security_audit_rule_match
- SAUCE: apparmor4.0.0 [4/99]: LSM: Call only one hook for audit rules
- SAUCE: apparmor4.0.0 [5/99]: LSM: Add lsmblob_to_secctx hook
- SAUCE: apparmor4.0.0 [6/99]: Audit: maintain an lsmblob in audit_context
- SAUCE: apparmor4.0.0 [7/99]: LSM: Use lsmblob in security_ipc_getsecid
- SAUCE: apparmor4.0.0 [8/99]: Audit: Update shutdown LSM data
- SAUCE: apparmor4.0.0 [9/99]: LSM: Use lsmblob in security_current_getsecid
- SAUCE: apparmor4.0.0 [10/99]: LSM: Use lsmblob in security_inode_getsecid
- SAUCE: apparmor4.0.0 [11/99]: Audit: use an lsmblob in audit_names
- SAUCE: apparmor4.0.0 [12/99]: LSM: Create new security_cred_getlsmblob LSM
  hook
- SAUCE: apparmor4.0.0 [13/99]: Audit: Change context data from secid to
  lsmblob
- SAUCE: apparmor4.0.0 [14/99]: Netlabel: Use lsmblob for audit data
- SAUCE: apparmor4.0.0 [15/99]: LSM: Ensure the correct LSM context releaser
- SAUCE: apparmor4.0.0 [16/99]: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [17/99]: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [18/99]: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [19/99]: LSM: lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [20/99]: LSM: security_lsmblob_to_secctx module
  selection
- SAUCE: apparmor4.0.0 [21/99]: Audit: Create audit_stamp structure
- SAUCE: apparmor4.0.0 [22/99]: Audit: Allow multiple records in an
  audit_buffer
- SAUCE: apparmor4.0.0 [23/99]: Audit: Add record for multiple task security
  contexts
- SAUCE: apparmor4.0.0 [24/99]: audit: multiple subject lsm values for
  netlabel
- SAUCE: apparmor4.0.0 [25/99]: Audit: Add record for multiple object 
contexts
- SAUCE: apparmor4.0.0 [26/99]: LSM: Remove unused lsmcontext_init()
- SAUCE: apparmor4.0.0 [27/99]: LSM: Improve logic in security_getprocattr
- SAUCE: apparmor4.0.0 [28/99]: LSM: secctx provider check on release
- SAUCE: apparmor4.0.0 [29/99]: LSM: Single calls in socket_getpeersec hooks
- SAUCE: apparmor4.0.0 [30/99]: LSM: Exclusive secmark usage
- SAUCE: apparmor4.0.0 [31/99]: LSM: Identify which LSM handles the context
  string
- SAUCE: apparmor4.0.0 [32/99]: AppArmor: Remove the exclusive flag
- SAUCE: apparmor4.0.0 [33/99]: LSM: Add mount opts blob size tracking
- SAUCE: apparmor4.0.0 [34/99]: LSM: allocate mnt_opts blobs instead of 
module
  specific data
- SAUCE: apparmor4.0.0 [35/99]: LSM: Infrastructure management of the key
  security blob
- SAUCE: apparmor4.0.0 [36/99]: LSM: Infrastructure management of the 
mnt_opts
  security blob
- SAUCE: apparmor4.0.0 [37/99]: LSM: Remove lsmblob scaffolding
- SAUCE: apparmor4.0

[Kernel-packages] [Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2073525

Title:
  [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite
  rapids

Status in The Kobuk project:

[Kernel-packages] [Bug 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2077490

Title:
  Error: out of memory while booting after installing the linux-firmware
  in proposed

Status in initramfs-t

[Kernel-packages] [Bug 2073047] Re: Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working after a few suspend/resume cycles

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2073047

Title:
  Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops
  working after a few suspend/resume cy

[Kernel-packages] [Bug 2073108] Re: Failed to detect Wireless LAN device

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2073108

Title:
  Failed to detect Wireless LAN device

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

[Kernel-packages] [Bug 2077296] Re: Add more region support of QCOM WiFi WCN7850

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Won't Fix => 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/2077296

Title:
  Add more region support of QCOM WiFi WCN7850

Status in HWE Next:
  Won't Fix
Status in linux-firmware package 

[Kernel-packages] [Bug 2080428] Re: Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2080428

Title:
  Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD

Status in linux-firmware package in Ubuntu:
 

[Kernel-packages] [Bug 2079024] Re: Update mt7925 BT FW to avoid bluetooth_obex_send failed

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.34

---
linux-firmware (20220329.git681281e4-0ubuntu3.34) jammy; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

linux-firmware (20220329.git681281e4-0ubuntu3.33) jammy; urgency=medium

  * Error: out of memory while booting after installing the linux-firmware in 
proposed (LP: #2077490)
- [Packaging] De-dup firmware files
- [Packaging] Add initramfs-hook to de-dup firmware files
  * Add more region support of QCOM WiFi WCN7850 (LP: #2077296)
- ath12k: WCN7850 hw2.0: update board-2.bin
  * [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids 
(LP: #2073525)
- linux-firmware: add firmware for qat_402xx devices

linux-firmware (20220329.git681281e4-0ubuntu3.32) jammy; urgency=medium

  * Failed to detect Wireless LAN device (LP: #2073108)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00288-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00309-
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
  * Add new firmwares for 6.8 hwe kernel (LP: #2076180)
- SAUCE: check_whence.py: Sync to Noble
- SAUCE: check_whence.py: Remove non-existing files from known_files list
- WHENCE: comment out duplicate MediaTek firmware
- WHENCE: remove duplicate File entries
- qcom: add firmware files for Adreno a220
- qcom: add firmware files for Adreno A200
- amdgpu: updated aldebaran firmware for amd-5.4
- amdgpu: update aldebaran firmware for amd.5.5 release
- amdgpu: update aldebaran firmware from 5.7 branch
- amdgpu: update aldebaran firmware
- linux-firmware: add firmware for MT7981
- linux-firmware: add firmware for MT7996
- linux-firmware: Update AMD SEV firmware
- nvidia: add GSP-RM version 535.113.01 firmware images
- powervr: add firmware for Imagination Technologies AXE-1-16M GPU
- cirrus: Add firmware file for cs42l43
- amdgpu: Add GC 9.4.3 firmware
- amdgpu: add PSP 13.0.6 firmware
- amdgpu: add SMU 13.0.6 firmware
- amdgpu: add SDMA 4.4.2 firmware
- amdgpu: add VCN 4.0.3 firmware
- amdgpu: add GC 11.0.1 rlc_1 firmware
- amdgpu: add GC 11.5.0 firmware
- amdgpu: add PSP 14.0.0  firmware
- amdgpu: add SDMA 6.1.0 firmware
- amdgpu: add VCN 4.0.5 firmware
- amdgpu: add VPE 6.1.0 firmware
- amdgpu: add DMCUB 3.5 firmware
- ath12k: add new driver and firmware for WCN7850
- brcm: rename Rock960 NVRAM to AP6356S and link devices to it
- Link some devices that ship with the AW-CM256SM
- WHENCE: Correct dangling symlinks
- WHENCE: Fix the dangling symlinks fix
- brcm: Add nvram for the Asus TF103C tablet
- brcm: Add nvram for the Xiaomi Mi Pad 2 tablet
- brcm: Add nvram for Lenovo Yoga Tablet 2 830F/L and 1050F/L tablets
- brcm: add symlink for Pi Zero 2 W NVRAM file
- brcm: Add nvram for the Lenovo Yoga Book X90F / X90L convertible
- brcm: Add symlinks from Pine64 devices to AW-CM256SM.txt
- WHENCE: add symlink for BananaPi M64
- brcm: Add brcmfmac43430-sdio.xxx.txt nvram for the Chuwi Hi8 (CWI509) 
tablet
- brcm: Add nvram for the Asus Memo Pad 7 ME176C tablet
- brcm: Add nvram for the Acer Iconia One 7 B1-750 tablet
  * Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working 
after a few suspend/resume cycles (LP: #2073047)
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- linux-firmware: Update firmware file for Intel Bluetooth AX200
- Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
  * Miscellaneous Ubuntu changes
- [Packaging]: scripts/create-quilt-series: Correctly handle file renames 
and spaces

 -- Juerg Haefliger   Fri, 13 Sep 2024
11:00:09 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => 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/2079024

Title:
  Update mt7925 BT FW to avoid  bluetooth_obex_send failed

Status in HWE Next:
  New
Status in linux-firmwar

[Kernel-packages] [Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

2024-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package egl-wayland - 1:1.1.9-1.1ubuntu0.1

---
egl-wayland (1:1.1.9-1.1ubuntu0.1) jammy; urgency=high

  * Backport patches to fix GTK apps in hybrid systems (LP: #1965563)
- In order to apply these patches cleanly and avoid rebasing with
  manual conflict resolution, respin
  egl-wayland-retrieve-DRM-device-name-before-acquiring-.patch
  from upstream and have d/p/series match the order of the
  commits upstream.

 -- Alessandro Astone   Fri, 13 Sep
2024 17:52:23 +0200

** Changed in: egl-wayland (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

Status in NVIDIA / egl-wayland:
  Fix Released
Status in GTK+:
  Fix Released
Status in egl-wayland package in Ubuntu:
  Fix Released
Status in egl-wayland source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

   * GTK applications fail to start on a hybrid graphics machine with an
  NVIDIA discrete GPU.

   * The NVIDIA egl-wayland extension 1.1.9 only supports rendering to
  the NVIDIA GPU if it is the primary GPU. On a hybrid system the
  primary GPU would be the integrated graphics, while the NVIDIA GPU
  should only be used for offloading of specific applications. On such a
  setup, the egl-wayland extension still incorrectly advertised the
  driver as compatible and attempted to use the NVIDIA GPU for all EGL
  applications.

   * To fix the issue, backport a commit from a newer version of the
  NVIDIA egl-wayland extension that reports the driver as incompatible
  when the NVIDIA GPU is not the primary GPU. This effectively ensures
  that all EGL applications run on integrated graphics by default.

  [ Test Plan ]

   * Set up a hybrid graphics machine with Jammy 22.04 LTS and the
  proprietary NVIDIA drivers version 535 or 550.

   * Install `libnvidia-egl-wayland1` from the update.

   * Log-in to a Wayland desktop session.

   * Verify that you can start `gnome-text-editor`.

  [ Test Plan - Regression ]

   * Set up a Desktop with a single NVIDIA GPU with Jammy 22.04 LTS and
  the proprietary NVIDIA drivers version 470, 535 or 550.

   * Install `libnvidia-egl-wayland1` from the update.

   * Log-in to GNOME Wayland (in Ubuntu Desktop this implies changing
  the log-in session on the log-in screen)

   * Verify that `eglinfo | grep -A2 "Wayland platform"` reports "EGL
  vendor string: NVIDIA"

   * Also verify that GNOME applications run smoothly as GPU
  accelerated.

  [ Where problems could occur ]

   * The scope of the change is limited to the NVIDIA proprietary
  drivers.

   * A possible regression would be that the driver starts reporting as
  incompatible on NVIDIA single-GPU systems too. One would notice by all
  wayland-native applications suddenly being very slow. Note that such
  systems would not default to Wayland in Jammy.

  [ Original Report ]

  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+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 2081980] [NEW] Position dependent screen flashing

2024-09-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

At a single vertical position near the bottom of the screen, and at
certain locations where there is a high contrast portion of the
wallpaper image, placing the cursor over that site causes the screen to
flash continuously. Change in the video driver does not correct it,
changing the wallpaper image does not correct it, but rebooting into a
different OS corrects the problem. This did not occur prior to the
24.04.1 upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
 DeviceFileMinor: 4323
 DeviceFileMode: 256
 DeviceFileModify: 1
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  550.107.02  Wed Jul 24 
23:53:00 UTC 2024
 GCC version:
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Sep 25 07:20:35 2024
DistUpgraded: 2024-08-30 14:15:30,947 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:07e1]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07e1]
InstallationDate: Installed on 2023-02-18 (585 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Dell Inc. Inspiron 5577
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=fe78af91-ce1d-473c-a261-e8bc74885648 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-08-30 (26 days ago)
dmi.bios.date: 12/02/2018
dmi.bios.release: 1.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 090HMC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:br1.1:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:sku07E1:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5577
dmi.product.sku: 07E1
dmi.product.version: 1.1.3
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.init.d.apport: 2024-07-22T08:59:07
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug kubuntu noble ubuntu
-- 
Position dependent screen flashing
https://bugs.launchpad.net/bugs/2081980
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2081963] [NEW] Acer Nitro 5 does not resume from suspend

2024-09-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Resuming from suspend results in a black screen and keyboard lights turn
on. System does not respond to any commands, including CTRL-ALT-F4.

Need to reboot to recover.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-45-generic 6.8.0-45.45
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:lasse  2361 F pipewire
 /dev/snd/controlC0:  lasse  2365 F wireplumber
 /dev/snd/controlC1:  lasse  2365 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 25 12:32:08 2024
InstallationDate: Installed on 2024-08-14 (42 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Acer Nitro AN515-43
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=2a8f106e-d087-45a9-8985-125718d940f0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-45-generic N/A
 linux-backports-modules-6.8.0-45-generic  N/A
 linux-firmware20240318.git3b128b60-0ubuntu2.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2020
dmi.bios.release: 1.12
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Octavia_PKS
dmi.board.vendor: PK
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd11/05/2020:br1.12:efr1.7:svnAcer:pnNitroAN515-43:pvrV1.12:rvnPK:rnOctavia_PKS:rvrV1.12:cvnAcer:ct10:cvrV1.12:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-43
dmi.product.sku: 
dmi.product.version: V1.12
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug noble wayland-session
-- 
Acer Nitro 5 does not resume from suspend
https://bugs.launchpad.net/bugs/2081963
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2069417] Re: Soundwire support for the Intel LNL Gen platforms

2024-09-25 Thread Launchpad Bug Tracker
This bug was fixed in the package firmware-sof - 2024.06-1ubuntu1

---
firmware-sof (2024.06-1ubuntu1) oracular; urgency=medium

  * Merge from Debian unstable (LP: #2069417, LP: #2069760). Remaining changes:
- compress sof firmware with zstd
- convert the sof-ace-tplg to symbolic link after 2023.12.1-1ubuntu1.1
  * Drop old delta, all upstream.

firmware-sof (2024.06-1) unstable; urgency=medium

  * Improvements to packaging as recommended by Vincent Bernat
  * Update to upstream version 2024-06

 -- Chris Chiu   Wed, 11 Sep 2024 17:54:47
+0800

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

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

Title:
  Soundwire support for the Intel LNL Gen platforms

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Noble:
  In Progress
Status in firmware-sof source package in Oracular:
  Fix Released

Bug description:
  [SRU Justifications]

  [Impact]
  Audio doesn't work on on Intel LNL platforms.

  [Fix]

  For firmware-sof, the following upstream commits are required to support 
Intel LNL platfrom.
  d5e95e4d003f ("Add sof-v2.10 for Intel hardware").
  7e59aa73cadc ("Add SOF v2.10 signed Intel binaries).

  [Test Case]
  1. Install 6.10 kernel or later version which support Intel LNL
  2. Install the -proposed firmware-sof package on the Intel LNL PC with 
soundwire devices
  3. Go to audio setting to make sure the audio input/output device are not 
dummy

  [Where problems could occur]
  New tplg/firmware files signed by Intel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2069417/+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 2069760] Re: Soundwire support for CS42L43 and CS35L56 on Intel MTL

2024-09-25 Thread Launchpad Bug Tracker
This bug was fixed in the package firmware-sof - 2024.06-1ubuntu1

---
firmware-sof (2024.06-1ubuntu1) oracular; urgency=medium

  * Merge from Debian unstable (LP: #2069417, LP: #2069760). Remaining changes:
- compress sof firmware with zstd
- convert the sof-ace-tplg to symbolic link after 2023.12.1-1ubuntu1.1
  * Drop old delta, all upstream.

firmware-sof (2024.06-1) unstable; urgency=medium

  * Improvements to packaging as recommended by Vincent Bernat
  * Update to upstream version 2024-06

 -- Chris Chiu   Wed, 11 Sep 2024 17:54:47
+0800

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

Title:
  Soundwire support for CS42L43 and CS35L56 on Intel MTL

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Noble:
  In Progress
Status in firmware-sof source package in Noble:
  In Progress
Status in alsa-ucm-conf source package in Oracular:
  Fix Released
Status in firmware-sof source package in Oracular:
  Fix Released

Bug description:
  [SRU Justifications]

  == firmware-sof ==
  [Impact]

  Audio doesn't work on Dell new XPS laptops on Intel MTL platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are required. For
  firmware-sof, it's the upstream commit 7d2c7f5ad44d ("Add sof-v2.9 for
  Intel hardware").

  [Test Case]
  1. Install linux-firmware version >= 20240318.git3b128b60-0ubuntu2.1
  2. Install new noble/oracular -proposed alsa UCM conf package
  3. Install 6.10-oem kernel
  4. Go to audio setting to make sure the audio input/output device are not 
dummy

  [Where problems could occur]
  It's simply an additional tplg file which only new kernel driver knows to how 
to load.

  == alsa-ucm-conf ==
  [Impact]

  Audio doesn't work on Dell new XPS laptops on Intel MTL platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are required. For alsa-ucm-conf, 
it requires the following upstream commit
  1. c0a4df603786 ("sof-soundwire: Use one file for speaker codec")
  2. 8e39917518b6 (sof-soundwire: Add basic support for basic cs35l56)
  3. e87dde51d689 (sof-soundwire: Add basic support for cs42l43)

  [Test Case]
  1. Install linux-firmware version >= 20240318.git3b128b60-0ubuntu2.1
  2. Install 6.10-oem kernel
  3. Install new noble/oracular -proposed firmware-sof package
  4. Go to audio setting to make sure the audio input/output device are not 
dummy

  [Where problems could occur]
  The new alsa UCM file only take effect when new cs35l56 driver and 
firmware-sof are loaded. The impact are restricted on cs35l56 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2069760/+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 2069760] Re: Soundwire support for CS42L43 and CS35L56 on Intel MTL

2024-09-25 Thread Launchpad Bug Tracker
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu6

---
alsa-ucm-conf (1.2.10-1ubuntu6) oracular; urgency=medium

  * Added changes:
- d/p/0001-sof-soundwire-Use-one-file-for-speaker-codec-initial.patch
- d/p/0002-sof-soundwire-Add-basic-support-for-basic-cs35l56-co.patch
- d/p/0003-sof-soundwire-Add-basic-support-for-cs42l43.patch
  - Soundwire support for CS42L43 and CS35L56 on Intel MTL
(LP: #2069760)

 -- Chris Chiu   Tue, 02 Jul 2024 22:32:17
+0800

** Changed in: alsa-ucm-conf (Ubuntu Oracular)
   Status: In Progress => Fix Released

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

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

Title:
  Soundwire support for CS42L43 and CS35L56 on Intel MTL

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Noble:
  In Progress
Status in firmware-sof source package in Noble:
  In Progress
Status in alsa-ucm-conf source package in Oracular:
  Fix Released
Status in firmware-sof source package in Oracular:
  Fix Released

Bug description:
  [SRU Justifications]

  == firmware-sof ==
  [Impact]

  Audio doesn't work on Dell new XPS laptops on Intel MTL platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are required. For
  firmware-sof, it's the upstream commit 7d2c7f5ad44d ("Add sof-v2.9 for
  Intel hardware").

  [Test Case]
  1. Install linux-firmware version >= 20240318.git3b128b60-0ubuntu2.1
  2. Install new noble/oracular -proposed alsa UCM conf package
  3. Install 6.10-oem kernel
  4. Go to audio setting to make sure the audio input/output device are not 
dummy

  [Where problems could occur]
  It's simply an additional tplg file which only new kernel driver knows to how 
to load.

  == alsa-ucm-conf ==
  [Impact]

  Audio doesn't work on Dell new XPS laptops on Intel MTL platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are required. For alsa-ucm-conf, 
it requires the following upstream commit
  1. c0a4df603786 ("sof-soundwire: Use one file for speaker codec")
  2. 8e39917518b6 (sof-soundwire: Add basic support for basic cs35l56)
  3. e87dde51d689 (sof-soundwire: Add basic support for cs42l43)

  [Test Case]
  1. Install linux-firmware version >= 20240318.git3b128b60-0ubuntu2.1
  2. Install 6.10-oem kernel
  3. Install new noble/oracular -proposed firmware-sof package
  4. Go to audio setting to make sure the audio input/output device are not 
dummy

  [Where problems could occur]
  The new alsa UCM file only take effect when new cs35l56 driver and 
firmware-sof are loaded. The impact are restricted on cs35l56 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2069760/+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 2081723] Re: libnvidia-compute-560 should provide libcuda1

2024-09-25 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.183.06-0ubuntu6

---
nvidia-graphics-drivers-535-server (535.183.06-0ubuntu6) oracular; 
urgency=medium

  * libnvidia-compute-535-server should provide libcuda1 (LP: #2081723)

 -- Kuba Pawlak   Mon, 23 Sep 2024 17:20:44
+0200

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

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

Title:
  libnvidia-compute-560 should provide libcuda1

Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-560 package in Ubuntu:
  Fix Released

Bug description:
  the gpu-burn package is uninstallable, because libnivida-compute
  stopped providing the libcuda1 virtual package. Please re-add that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2081723/+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 1861057] Re: CONFIG_IOMMU_DEBUGFS should not be on by default

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

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

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

Title:
  CONFIG_IOMMU_DEBUGFS should not be on by default

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  This config option causes the following message to be displayed in the
  kernel log:

  [0.568713] *
  [0.570549] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE**
  [0.570640] ** **
  [0.572478] **  IOMMU DebugFS SUPPORT HAS BEEN ENABLED IN THIS KERNEL  **
  [0.574313] ** **
  [0.574640] ** This means that this kernel is built to expose internal **
  [0.576481] ** IOMMU data structures, which may compromise security on **
  [0.578307] ** your system.**
  [0.578642] ** **
  [0.580486] ** If you see this message and you are not debugging the   **
  [0.582327] ** kernel, report this immediately to your vendor! **
  [0.582641] ** **
  [0.584469] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE**
  [0.586296] *

  This was pointed out by a cloud vendor, but it should probably be
  disabled in all kernel configs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861057/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

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

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

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

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  Invalid
Status in linux package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

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

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

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

Title:
  Ubuntu 18.04 guest hangs during diskio stress

Status in dellserver:
  Invalid
Status in linux package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1933274] Re: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"

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

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

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

Title:
  TGL-H skl_dram_get_dimm_info crashes with "Missing case (val ==
  65535)"

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  Tracing this back, I found the current Ubuntu 5.11 kernel has
  incorrect offsets for some platforms (TGL-H and ADL). I created an
  upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662
  and was directed to a commit, 5d0c938ec9cc, that ought to fix this
  issue. See the attached patch file for this commit applied to the
  current Ubuntu 5.11 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933274/+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 2081685] [NEW] [Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System, ThinkSystem SR950 V3.

2024-09-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

There is CPU hard Lockup detected under Ubuntu 24.04 LTS (kernel
6.8.0-38). see attachment"dmesg0723-Lockup-Ubuntu24.04.log"

ubuntu@SR950V3:~$ cat /var/log/dmesg | grep -i  lockup

[   15.241164] kernel: watchdog: Watchdog detected hard LOCKUP on cpu
124

[   15.241164] kernel:  ? watchdog_hardlockup_check+0x1cb/0x3b0


Besides, the issue does not occur on upstream kernel 6.8,6.9, 6.10, 6.11-rc*, 
then only ubuntu kernel issue. see  attachment "dmesg0923-No-Lockup-Kernel 
6-10.log". 
According to the dmesg log, the "hard lockup" is not a real lockup, 
Because many CPU try to get cache_disable_lock spin lock at the same time when 
kernel boot. And competition has occurred here. 
Every CPU's TLB will be flushed in the critical zone, the flushing TLB is a 
time-consuming operation, and there are so many CPUs,
so the false "hard lockup" was detected by kernel. To avoid customer confuse, 
when Canonical do the fix?


HW Config:
ThinkSystem SR950 V3

CPU: 8*  Intel(R) Xeon(R) Platinum 8490H 60 Core 3.5GHz

MEM:  2TB = SK Hynix 356GB DDR5 4800MHz 3DS (2015.1GB)

Raid: ThinkSystem RAID 940-8i 4GB Flash PCIe Gen4 12Gb Adapter

Storage: Micron_7450_MTFDKBA960TFR *1

Samsung 30.7TB 24Gbps SAS 2.5" SSD

NIC: ThinkSystem Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter

OS: ubuntu 24.04 LTS( kernel 6.8.0-38-generic)

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

-- 
[Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System, ThinkSystem 
SR950 V3.
https://bugs.launchpad.net/bugs/2081685
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2069207] [NEW] rcu_tasks detected stalls on tasks

2024-09-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The following is observed when running heavier I/O to our NVMe/TCP
target:

2024-06-11T23:16:42.773199+00:00 blr-r19-s33u kernel: INFO: rcu_tasks detected 
stalls on tasks:
2024-06-11T23:16:42.773232+00:00 blr-r19-s33u kernel: 3db97b04: .. 
nvcsw: 34791011/34791011 holdout: 1 idle_cpu: -1/1
2024-06-11T23:16:42.773236+00:00 blr-r19-s33u kernel: task:kworker/1:1H
state:R  running task stack:0 pid:881   tgid:881   ppid:2  
flags:0x4000
2024-06-11T23:16:42.773239+00:00 blr-r19-s33u kernel: Workqueue: nvme_tcp_wq 
nvme_tcp_io_work [nvme_tcp]
2024-06-11T23:16:42.773243+00:00 blr-r19-s33u kernel: Call Trace:
2024-06-11T23:16:42.773245+00:00 blr-r19-s33u kernel:  
2024-06-11T23:16:42.773247+00:00 blr-r19-s33u kernel:  ? release_sock+0x8d/0xb0
2024-06-11T23:16:42.773249+00:00 blr-r19-s33u kernel:  ? 
nvme_tcp_io_work+0x7f/0xe0 [nvme_tcp]
2024-06-11T23:16:42.773254+00:00 blr-r19-s33u kernel:  ? 
process_one_work+0x16c/0x350
2024-06-11T23:16:42.773257+00:00 blr-r19-s33u kernel:  ? 
worker_thread+0x306/0x440
2024-06-11T23:16:42.773259+00:00 blr-r19-s33u kernel:  ? 
_raw_spin_lock_irqsave+0xe/0x20
2024-06-11T23:16:42.773262+00:00 blr-r19-s33u kernel:  ? 
__pfx_worker_thread+0x10/0x10
2024-06-11T23:16:42.773265+00:00 blr-r19-s33u kernel:  ? kthread+0xef/0x120
2024-06-11T23:16:42.773267+00:00 blr-r19-s33u kernel:  ? __pfx_kthread+0x10/0x10
2024-06-11T23:16:42.773270+00:00 blr-r19-s33u kernel:  ? ret_from_fork+0x44/0x70
2024-06-11T23:16:42.773273+00:00 blr-r19-s33u kernel:  ? __pfx_kthread+0x10/0x10
2024-06-11T23:16:42.773276+00:00 blr-r19-s33u kernel:  ? 
ret_from_fork_asm+0x1b/0x30


root@blr-r19-s33u:~# uname -a
Linux blr-r19-s33u 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr  
   20 
00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
root@blr-r19-s33u:~# uname -r
6.8.0-31-generic
root@blr-r19-s33u:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy 
   
-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
root@blr-r19-s33u:~#

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


** Tags: bot-comment
-- 
rcu_tasks detected stalls on tasks
https://bugs.launchpad.net/bugs/2069207
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2081270] [NEW] bug ACPI

2024-09-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

ACPI bug restart computer

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 20 09:45:09 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] 
[103c:880d]
InstallationDate: Installed on 2024-08-31 (20 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
MachineType: HP HP EliteBook 830 G8 Notebook PC
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=1a9567bd-a11d-4844-95cc-c44bb39c7e48 ro loglevel=3 quiet splash 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/03/2024
dmi.bios.release: 17.1
dmi.bios.vendor: HP
dmi.bios.version: T76 Ver. 01.17.01
dmi.board.name: 880D
dmi.board.vendor: HP
dmi.board.version: KBC Version 30.53.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 48.83
dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.17.01:bd05/03/2024:br17.1:efr48.83:svnHP:pnHPEliteBook830G8NotebookPC:pvrSBKPF:rvnHP:rn880D:rvrKBCVersion30.53.00:cvnHP:ct10:cvr:sku26D48AV:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 830 G8 Notebook PC
dmi.product.sku: 26D48AV
dmi.product.version: SBKPF
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption noble ubuntu wayland-session
-- 
bug ACPI
https://bugs.launchpad.net/bugs/2081270
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2081250] [NEW] Dual Monitor - Builtin Screen shake

2024-09-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a Dell monitor connected to my Lenovo X1 Carbon Yoga (Gen 6).
There is an invisible line where, if I hold my mouse 'on' this line, the
Lenovo screen shakes. It does not shale all the time and it seems to be
linked to the website I am displaying on the Lenovo screen. For example
speedtest.net will shake but https://help.ubuntu.com/stable/ubuntu-
help/report-ubuntu-bug.html.en and Launchpad URLs do not shake.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 20 09:08:28 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
InstallationDate: Installed on 2024-08-05 (45 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: LENOVO 20XY003AUK
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-44-generic 
root=UUID=33975dba-a276-44b3-9613-f7a7776a6148 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2024
dmi.bios.release: 1.69
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET93W (1.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XY003AUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.36
dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET93W(1.69):bd07/01/2024:br1.69:efr1.36:svnLENOVO:pn20XY003AUK:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY003AUK:rvrSDK0K17763WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
dmi.product.family: ThinkPad X1 Yoga Gen 6
dmi.product.name: 20XY003AUK
dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
dmi.product.version: ThinkPad X1 Yoga Gen 6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu wayland-session
-- 
Dual Monitor - Builtin Screen shake
https://bugs.launchpad.net/bugs/2081250
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2071698] Re: Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform

2024-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.4

---
linux-firmware (20240318.git3b128b60-0ubuntu2.4) noble; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Missing DMC firmware for Xe driver for Intel BattleMage (LP: #2080214)
- i915: Add BMG DMC v2.06
  * Add firmware for Cirrus CS35L54 (LP: #2080371)
- cirrus: cs35l56: Add firmware for Cirrus CS35L54 for some HP laptops
  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform (LP: 
#2071698)
- linux-firmware: Add ISH firmware file for Intel Lunar Lake platform
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

 -- Juerg Haefliger   Fri, 13 Sep 2024
10:49:04 +0200

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

Title:
  Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Won't Fix
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.11 source package in Noble:
  In Progress
Status in linux source package in Oracular:
  Fix Released
Status in linux-firmware source package in Oracular:
  Fix Released
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Starting from Intel Lunar Lake, the ISH firmware will reside in system
  root as separated blobs, and the kernel driver is responsible for
  loading a preferred one based on DMI info.

  [Fix]

  Kernel fixes in linux-next:
  * aa4674c525e1e hid: intel-ish-hid: Add support for vendor customized 
firmware loading
  * 641361538b68d HID: intel-ish-hid: Use CPU generation string in driver_data
  * 87de1615194ee Documentation: hid: intel-ish-hid: Add vendor custom firmware 
loading

  linux-firmware in upstream tag 20240709:
  * 33a8b2a7f604 linux-firmware: Add ISH firmware file for Intel Lunar Lake 
platform

  [Test Case]

  dmesg dumps:
  ```
  intel_ish_ipc :00:12.0: ISH loader: firmware loaded. size:748032
  ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done 
OK, num_hid_devices=2
  hid-generic 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on 
  hid-generic 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on 
  hid-sensor-hub 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on 
  hid-sensor-hub 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on
  ```

  [Where problems could occur]

  This is to include generic blob provided by Intel for all Lunar Lake
  platforms. It may not be stable, may not be functional, and may have
  various problems until the hardware vendor submit their own.

  [Other Info]

  Nominated for linux/oracular, linux-oem-6.11/noble, linux-
  firmware/oracular and linux-firmware/noble.

  == original bug report ==

  * kernel
    - 
https://patchwork.kernel.org/project/linux-input/cover/20240813034736.812475-1-lixu.zh...@intel.com/
  * linux-firmware
    - generic
  * commit 33a8b2a7f604 ("linux-firmware: Add ISH firmware file for Intel 
Lunar Lake platform")

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2071698/+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 2079024] Re: Update mt7925 BT FW to avoid bluetooth_obex_send failed

2024-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.4

---
linux-firmware (20240318.git3b128b60-0ubuntu2.4) noble; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Missing DMC firmware for Xe driver for Intel BattleMage (LP: #2080214)
- i915: Add BMG DMC v2.06
  * Add firmware for Cirrus CS35L54 (LP: #2080371)
- cirrus: cs35l56: Add firmware for Cirrus CS35L54 for some HP laptops
  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform (LP: 
#2071698)
- linux-firmware: Add ISH firmware file for Intel Lunar Lake platform
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

 -- Juerg Haefliger   Fri, 13 Sep 2024
10:49:04 +0200

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

Title:
  Update mt7925 BT FW to avoid  bluetooth_obex_send failed

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

Bug description:
  [Impact]
  In OEM project, we found that the Mediatek mtk7925 bluetooth device will fail 
on transmitting files with the peer device by OBEX.

  The bluetooth mouse, keyboard and headset are working while this
  happen.

  [Fix]
  Cherry-pick the mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin from the 
linux-firmware:Oracular:

  https://kernel.ubuntu.com/gitea/kernel/linux-
  firmware/commit/79c19bb0cda0abc97fdca49d3165f3b419aa2ac6

  [Test Plan]
  1. Boot into OS
  2. checkbox-cli run com.canonical.certification::bluetooth/bluetooth_obex_send

  [Where problems could occur]
  May cause regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2079024/+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 2080371] Re: Add firmware for Cirrus CS35L54

2024-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.4

---
linux-firmware (20240318.git3b128b60-0ubuntu2.4) noble; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Missing DMC firmware for Xe driver for Intel BattleMage (LP: #2080214)
- i915: Add BMG DMC v2.06
  * Add firmware for Cirrus CS35L54 (LP: #2080371)
- cirrus: cs35l56: Add firmware for Cirrus CS35L54 for some HP laptops
  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform (LP: 
#2071698)
- linux-firmware: Add ISH firmware file for Intel Lunar Lake platform
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

 -- Juerg Haefliger   Fri, 13 Sep 2024
10:49:04 +0200

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

Title:
  Add firmware for Cirrus CS35L54

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-firmware source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  Without the FWs loaded, the audio output missing

  [ 7.103847] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.0: .bin file required but 
not found
  [ 7.103852] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.1: .bin file required but 
not found
  [ 7.103853] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.2: .bin file required but 
not found
  [ 7.103855] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.3: .bin file required but 
not found

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=a9c9dbf495fd3aa6e880b2ba32af576f83e7f7fa

  [Test Case]

  With the FWs loaded, the audio output properly

  [  715.179244] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.2: DSP1: Firmware: 
1a00d6 vendor: 0x2 v3.11.18, 41 algorithms
  [  715.553139] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.0: DSP1: Firmware: 
1a00d6 vendor: 0x2 v3.11.18, 41 algorithms
  [  715.554366] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.1: DSP1: Firmware: 
1a00d6 vendor: 0x2 v3.11.18, 41 algorithms
  [  715.555907] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.3: DSP1: Firmware: 
1a00d6 vendor: 0x2 v3.11.18, 41 algorithms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2080371/+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 2080214] Re: Missing DMC firmware for Xe driver for Intel BattleMage

2024-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.4

---
linux-firmware (20240318.git3b128b60-0ubuntu2.4) noble; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Missing DMC firmware for Xe driver for Intel BattleMage (LP: #2080214)
- i915: Add BMG DMC v2.06
  * Add firmware for Cirrus CS35L54 (LP: #2080371)
- cirrus: cs35l56: Add firmware for Cirrus CS35L54 for some HP laptops
  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform (LP: 
#2071698)
- linux-firmware: Add ISH firmware file for Intel Lunar Lake platform
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

 -- Juerg Haefliger   Fri, 13 Sep 2024
10:49:04 +0200

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

Title:
  Missing DMC firmware for Xe driver for Intel BattleMage

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-firmware source package in Oracular:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Missing DMC firmware for Xe driver for Intel BattleMage.
  ```
  xe :04:00.0: Direct firmware load for i915/bmg_dmc.bin failed with error 
-2
  xe :04:00.0: [drm] Failed to load DMC firmware i915/bmg_dmc.bin 
(-ENOENT). Disabling runtime power management.
  ```

  [Fix]

  linux-firmware commit fa86949f1 ("i915: Add BMG DMC v2.06") included
  in upstream tag 20240513.

  [Test Case]

  Expect following messages in dmesg output:
  ```
  $ sudo dmesg | grep xe
  xe :04:00.0: [drm] Finished loading DMC firmware i915/bmg_dmc.bin (v2.6)
  ```

  [Where problems could occur]

  New hardware. May need further updates.

  [Other Info]

  Targets v6.11+ kernels, so nominating only for Noble and Oracular.

  = original bug description ==

  [5.146422] xe :04:00.0: Direct firmware load for i915/bmg_dmc.bin 
failed with error -2
  [5.146424] xe :04:00.0: [drm] Failed to load DMC firmware 
i915/bmg_dmc.bin (-ENOENT). Disabling runtime power management.
  [5.146426] xe :04:00.0: [drm] DMC firmware homepage: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Need linux-firmware commit fa86949f1 ("i915: Add BMG DMC v2.06")
  included in upstream tag 20240513.

  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:u  2277 F pipewire
   /dev/snd/controlC0:  u  2280 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-05-03 (131 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240314)
  MachineType: Intel Corporation Arrow Lake Client Platform
  Package: linux-firmware
  PackageArchitecture: amd64
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1004-oem 
root=UUID=cf746c14-f32e-47c6-aafb-6f133166eacc ro i915.force_probe=!* 
xe.force_probe=* quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.11.0-1004.4-oem 6.11.0-rc6
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-1004-oem N/A
   linux-backports-modules-6.11.0-1004-oem  N/A
   linux-firmware   20240318.git3b128b60-0ubuntu2.2
  Tags: noble
  Uname: Linux 6.11.0-1004-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/31/2024
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: MTLSFWI1.R00.4052.D81.2401311921
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: MTL-S UDIMM 1DPC EVCRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 3
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 2.19
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrMTLSFWI1.R00.4052.D81.2401311921:bd01/31/2024:efr2.19:svnIntelCorporation:pnArrowLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-SUDIMM1DPCEVCRB:rvr3:cvnIntelCorporation:ct3:cvr0.1:sku010010210200:
  dmi.product.family: Arrow Lake Client System
  dmi.product.name: Arrow Lake Client Platform
  dmi.product.sku: 010010210200
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


-- 
Mailing list

[Kernel-packages] [Bug 2080428] Re: Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD

2024-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.4

---
linux-firmware (20240318.git3b128b60-0ubuntu2.4) noble; urgency=medium

  * Update mt7925 BT FW to avoid  bluetooth_obex_send failed  (LP: #2079024)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7925)
  * Missing DMC firmware for Xe driver for Intel BattleMage (LP: #2080214)
- i915: Add BMG DMC v2.06
  * Add firmware for Cirrus CS35L54 (LP: #2080371)
- cirrus: cs35l56: Add firmware for Cirrus CS35L54 for some HP laptops
  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform (LP: 
#2071698)
- linux-firmware: Add ISH firmware file for Intel Lunar Lake platform
  * Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD (LP: #2080428)
- SAUCE: Revert "ath12k: WCN7850 hw2.0: update board-2.bin"

 -- Juerg Haefliger   Fri, 13 Sep 2024
10:49:04 +0200

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

Title:
  Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-firmware source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  After installing new package updates as suggested by ubuntu, my WiFi
  Card (Qualcomm WCN785x Wi-Fi 7(802.11be) as far as lshw -C network is
  concerned) did not connect to the network again after waking the
  laptop from idle.

  After some research I found this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2077296

  It seems that after updating the firmware package after the bugfix for
  the mentioned bug got released, the updated file board-2.bin is now
  broken for at least T14 Gen5 AMD. In the mentioned bugfix thread, a
  person already posted this issue yesterday. However, I am reposting it
  here as suggested by Timo in
  https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/2077296/comments/5.

  Running sudo dmesg | grep ath12k reveals that the board data could not
  be fetched from the updated file:

  [2.381547] ath12k_pci :02:00.0: BAR 0 [mem 0x9060-0x907f 
64bit]: assigned
  [2.381567] ath12k_pci :02:00.0: enabling device ( -> 0002)
  [2.382640] ath12k_pci :02:00.0: MSI vectors: 16
  [2.382647] ath12k_pci :02:00.0: Hardware name: wcn7850 hw2.0
  [3.479946] ath12k_pci :02:00.0: chip_id 0x2 chip_family 0x4 board_id 
0xff soc_id 0x40170200
  [3.479950] ath12k_pci :02:00.0: fw_version 0x100301e1 
fw_build_timestamp 2023-12-06 04:05 fw_build_id 
QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
  [3.492086] ath12k_pci :02:00.0: failed to fetch board data for 
bus=pci,vendor=17cb,device=1107,subsystem-vendor=17aa,subsystem-device=e0e6,qmi-chip-id=2,qmi-board-id=255
 from ath12k/WCN7850/hw2.0/board-2.bin
  [3.492101] ath12k_pci :02:00.0: failed to fetch board.bin from 
WCN7850/hw2.0
  [3.492103] ath12k_pci :02:00.0: qmi failed to load bdf:
  [3.492105] ath12k_pci :02:00.0: qmi failed to load board data file:-2

  Any help is greatly appreciated.

  [Fix]

  Revert offending commit.

  [Where Problems Could Occur]

  Limited to ath12k wifi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2080428/+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 2081723] Re: libnvidia-compute-560 should provide libcuda1

2024-09-23 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-560 -
560.35.03-0ubuntu5

---
nvidia-graphics-drivers-560 (560.35.03-0ubuntu5) oracular; urgency=medium

  * libnvidia-compute-560 should provide libcuda1 (LP: #2081723)

 -- Kuba Pawlak   Mon, 23 Sep 2024 15:06:03
+0200

** Changed in: nvidia-graphics-drivers-560 (Ubuntu)
   Status: New => Fix Released

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

Title:
  libnvidia-compute-560 should provide libcuda1

Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-560 package in Ubuntu:
  Fix Released

Bug description:
  the gpu-burn package is uninstallable, because libnivida-compute
  stopped providing the libcuda1 virtual package. Please re-add that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2081723/+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 2081204] Re: Jammy 6.8 kernel metas recommend non-existent ubuntu-kernel-accessories

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

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

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

Title:
  Jammy 6.8 kernel metas recommend non-existent ubuntu-kernel-
  accessories

Status in linux-gcp package in Ubuntu:
  Confirmed

Bug description:
  Noticed while attempting to upgrade jammy linux-gcp 6.5 -> 6.8.

  Typical upgrade flow for most users is to just use `apt upgrade` these
  days, but this does not currently work due to a recommends on ubuntu-
  kernel-accessories from linux-gcp. This seems to be the case for all
  cloud-tuned kernels and linux-generic-hwe-22.04 as well.

  There is no ubuntu-kernel-accessories in the jammy repo, so `apt
  upgrade` will hold the kernel packages back. `apt full-upgrade` still
  works.


  --- Example. Top is evidence it works by excluding recommends (which
  is only ubuntu-kernel-accessories), bottom is standard behavior ---

  kyler_hornor@kyler-network:/etc/apt/apt.conf.d$ sudo apt -o 
Debug::pkgDepCache::Marker=1 --no-install-recommends upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
MarkInstall linux-image-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU Ib > FU=0
  MarkInstall linux-image-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN Ib > FU=0
MarkInstall linux-modules-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN > FU=0
MarkInstall linux-headers-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU Ib > FU=0
  MarkInstall linux-headers-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN Ib > FU=0
MarkInstall linux-gcp-6.8-headers-6.8.0-1015:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN > FU=0
  Calculating upgrade... Done
  The following NEW packages will be installed:
linux-gcp-6.8-headers-6.8.0-1015 linux-headers-6.8.0-1015-gcp 
linux-image-6.8.0-1015-gcp linux-modules-6.8.0-1015-gcp
  The following packages will be upgraded:
linux-gcp linux-headers-gcp linux-image-gcp
  3 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
  3 standard LTS security updates
  Need to get 56.9 MB of archives.
  After this operation, 266 MB of additional disk space will be used.
  Do you want to continue? [Y/n] ^C
  kyler_hornor@kyler-network:/etc/apt/apt.conf.d$ sudo apt -o 
Debug::pkgDepCache::Marker=1 upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
MarkInstall linux-image-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU Ib > FU=0
  MarkInstall linux-image-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN Ib > FU=0
MarkInstall linux-modules-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN > FU=0
MarkInstall linux-headers-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU Ib > FU=0
  MarkInstall linux-headers-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN Ib > FU=0
MarkInstall linux-gcp-6.8-headers-6.8.0-1015:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN > FU=0
MarkInstall linux-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU IPb > FU=0
  MarkInstall linux-tools-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN Ib > FU=0
MarkInstall linux-gcp-6.8-tools-6.8.0-1015:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un uN Ib > FU=0
  MarkInstall libnuma1:amd64 < none -> 2.0.14-3ubuntu2 @un uN > FU=0
  linux-gcp:amd64 Recommends on ubuntu-kernel-accessories:amd64 < none @un 
H > can't be satisfied! (dep)
MarkKeep linux-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 6.8.0-1015.17~22.04.1 
@ii umU IPb > FU=0
MarkKeep linux-image-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU > FU=0
MarkKeep linux-headers-gcp:amd64 < 6.5.0.1025.27~22.04.1 -> 
6.8.0-1015.17~22.04.1 @ii umU > FU=0
  Calculating upgrade... Done
MarkDelete libnuma1:amd64 < none -> 2.0.14-3ubuntu2 @un ugN > FU=0
MarkDelete linux-gcp-6.8-headers-6.8.0-1015:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un ugN > FU=0
MarkDelete linux-gcp-6.8-tools-6.8.0-1015:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un ugN Ib > FU=0
MarkDelete linux-headers-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un ugN Ib > FU=0
MarkDelete linux-image-6.8.0-1015-gcp:amd64 < none -> 6.8.0-1015.17~22.04.1 
@un ugN > FU=0
MarkDelete linux-modules-6.8.0-1015-gcp:amd64 < none -> 
6.8.0-1015.17~22.04.1 @un ugN > FU=0
MarkDelete linux-tools-6.8.0-1015-gcp:amd64 < none -> 6.8.0-1015.17~22.04.1 
@un ugN Ib > FU=0
  The following packages have been kept back:
linux-gcp linux-headers-gcp linux-image-gcp
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

To manage notifications about thi

[Kernel-packages] [Bug 2071698] Re: Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform

2024-09-23 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.11.0-8.8

---
linux (6.11.0-8.8) oracular; urgency=medium

  * oracular/linux: 6.11.0-8.8 -proposed tracker (LP: #2080825)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.08.12)

  * [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after v6.10
(LP: #2080322)
- [Config] disable CONFIG_TCG_TPM2_HMAC by default

  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
(LP: #2071698)
- Documentation: hid: intel-ish-hid: Add vendor custom firmware loading
- HID: intel-ish-hid: Use CPU generation string in driver_data
- hid: intel-ish-hid: Add support for vendor customized firmware loading

  * Miscellaneous Ubuntu changes
- [Packaging] Purge obsolete upstart files
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64
- [Config] Update toolchain versions
- SAUCE: rust: Fix rustc source path for the new rustc packaging
- [Packaging] Don't force bindgen version
- [Config] Re-enable rust support for amd64

 -- Timo Aaltonen   Mon, 16 Sep 2024
15:04:18 +0300

** Changed in: linux (Ubuntu Oracular)
   Status: Fix Committed => 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/2071698

Title:
  Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Won't Fix
Status in linux-firmware source package in Noble:
  Fix Committed
Status in linux-oem-6.11 source package in Noble:
  In Progress
Status in linux source package in Oracular:
  Fix Released
Status in linux-firmware source package in Oracular:
  Fix Released
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Starting from Intel Lunar Lake, the ISH firmware will reside in system
  root as separated blobs, and the kernel driver is responsible for
  loading a preferred one based on DMI info.

  [Fix]

  Kernel fixes in linux-next:
  * aa4674c525e1e hid: intel-ish-hid: Add support for vendor customized 
firmware loading
  * 641361538b68d HID: intel-ish-hid: Use CPU generation string in driver_data
  * 87de1615194ee Documentation: hid: intel-ish-hid: Add vendor custom firmware 
loading

  linux-firmware in upstream tag 20240709:
  * 33a8b2a7f604 linux-firmware: Add ISH firmware file for Intel Lunar Lake 
platform

  [Test Case]

  dmesg dumps:
  ```
  intel_ish_ipc :00:12.0: ISH loader: firmware loaded. size:748032
  ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done 
OK, num_hid_devices=2
  hid-generic 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on 
  hid-generic 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on 
  hid-sensor-hub 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on 
  hid-sensor-hub 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device 
[hid-ishtp 8087:0AC2] on
  ```

  [Where problems could occur]

  This is to include generic blob provided by Intel for all Lunar Lake
  platforms. It may not be stable, may not be functional, and may have
  various problems until the hardware vendor submit their own.

  [Other Info]

  Nominated for linux/oracular, linux-oem-6.11/noble, linux-
  firmware/oracular and linux-firmware/noble.

  == original bug report ==

  * kernel
    - 
https://patchwork.kernel.org/project/linux-input/cover/20240813034736.812475-1-lixu.zh...@intel.com/
  * linux-firmware
    - generic
  * commit 33a8b2a7f604 ("linux-firmware: Add ISH firmware file for Intel 
Lunar Lake platform")

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2071698/+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 2080322] Re: [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after v6.10

2024-09-23 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.11.0-8.8

---
linux (6.11.0-8.8) oracular; urgency=medium

  * oracular/linux: 6.11.0-8.8 -proposed tracker (LP: #2080825)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.08.12)

  * [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after v6.10
(LP: #2080322)
- [Config] disable CONFIG_TCG_TPM2_HMAC by default

  * Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
(LP: #2071698)
- Documentation: hid: intel-ish-hid: Add vendor custom firmware loading
- HID: intel-ish-hid: Use CPU generation string in driver_data
- hid: intel-ish-hid: Add support for vendor customized firmware loading

  * Miscellaneous Ubuntu changes
- [Packaging] Purge obsolete upstart files
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64
- [Config] Update toolchain versions
- SAUCE: rust: Fix rustc source path for the new rustc packaging
- [Packaging] Don't force bindgen version
- [Config] Re-enable rust support for amd64

 -- Timo Aaltonen   Mon, 16 Sep 2024
15:04:18 +0300

** Changed in: linux (Ubuntu Oracular)
   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/2080322

Title:
  [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after
  v6.10

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  In Progress
Status in linux source package in Oracular:
  Fix Released
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  significant delays at bootup, the bootup time is 7 sec when this feature is 
disabled,
  but 20 sec when it's enabled.

  [Fix]
  v6.10-rc1 introduce encryption overhead to all kernel to TPM transactions,
  Disable it by default until there is a real fix.

  [Test]
  Tested on hardware, bootup is 7 sec as 6.8 noble kernel.

  [Where problems could occur]
  It may less security or break TPM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080322/+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 2066407] Re: Waking from suspend takes over 20 seconds each time

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

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

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

Title:
  Waking from suspend takes over 20 seconds each time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 9315. I just upgraded from 23.10 to 24.04.

  I have an issue with waking up from suspend. When I try to resume from
  suspend (e.g., opening the laptop lid or pressing a key on the
  keyboard), it takes 10+ seconds for it to wake up (to the lock
  screen).

  I attached the output of sudo journalctl  --since="-1 minutes"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066407/+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 2033553] Re: SD Card not detected, rtsx_pci_sdmmc reload required

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

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

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

Title:
  SD Card not detected, rtsx_pci_sdmmc reload required

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

Bug description:
  The SD card reader (Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card 
Reader) does not detect a SD card when it is inserted. 
  Only when the card was inserted during boot, or when called

  sudo rmmod rtsx_pci_sdmmc && sudo modprobe rtsx_pci_sdmmc

  the SD card is detected and can be used as usual. Running the modprobe 
without a card and inserting it then doesn't (temporarily) fix the issue. Also 
a change of card doesn't work.
  => The work around is always to insert the card and then remove and reload 
the module.

  Loading the module shows this message in dmesg:
  **
  [  651.937165] mmc0: cannot verify signal voltage switch
  [  652.053032] mmc0: new ultra high speed SDR104 SDHC card at address 59b4
  [  652.053708] mmcblk0: mmc0:59b4 SDU1  29.8 GiB (ro)
  [  652.055090]  mmcblk0: p1
  **

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

  $ uname -a
  Linux gandalf 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 
16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  
  Note:
  This bug reports seem to show a very similar behavior: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Aug 30 21:36:45 2023
  InstallationDate: Installed on 2023-08-26 (4 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2033553/+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 2077575] Re: standby broken on ThinkPad 260 Yoga with 6.8

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

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

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

Title:
  standby broken on ThinkPad 260 Yoga with 6.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 22.04 with HWE, so I recently got the upgrade from 6.5
  to 6.8 and since then, standby doesn't work anymore. The screen goes
  black, the keyboard backlight goes off and the status LED goes from on
  to fading, but the fan and the LEDs on the keyboard stay on.

  The laptop also doesn't wake up anymore.

  The logs end here:

  Aug 21 20:57:20 systemd[1]: Starting System Suspend...
  Aug 21 20:57:20 wpa_supplicant[1259]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 20:57:20 wpa_supplicant[1259]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 20:57:20 wpa_supplicant[1259]: nl80211: deinit ifname=wlp4s0 
disabled_11b_rates=0
  Aug 21 20:57:20 systemd[1]: grub-common.service: Deactivated successfully.
  Aug 21 20:57:20 systemd[1]: Finished Record successful boot for GRUB.
  Aug 21 20:57:20 systemd-sleep[2204]: Entering sleep state 'suspend'...
  Aug 21 20:57:20 kernel: PM: suspend entry (deep)

  whereas they continue on 6.5:

  Aug 21 21:03:03 wpa_supplicant[1213]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 21:03:03 wpa_supplicant[1213]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 21:03:03 wpa_supplicant[1213]: nl80211: deinit ifname=wlp4s0 
disabled_11b_rates=0
  Aug 21 21:03:03 systemd-sleep[2158]: Entering sleep state 'suspend'...
  Aug 21 21:03:03 kernel: PM: suspend entry (deep)
  Aug 21 21:03:04 kernel: Filesystems sync: 0.392 seconds
  Aug 21 21:03:15 kernel: Freezing user space processes
  Aug 21 21:03:15 kernel: Freezing user space processes completed (elapsed 
0.001 seconds)
  Aug 21 21:03:15 kernel: OOM killer disabled.
  Aug 21 21:03:15 kernel: Freezing remaining freezable tasks
  Aug 21 21:03:15 kernel: Freezing remaining freezable tasks completed (elapsed 
0.001 seconds)
  Aug 21 21:03:15 kernel: printk: Suspending console(s) (use no_console_suspend 
to debug)
  Aug 21 21:03:15 kernel: e1000e: EEE TX LPI TIMER: 0011
  Aug 21 21:03:15 kernel: ACPI: EC: interrupt blocked
  Aug 21 21:03:15 kernel: ACPI: PM: Preparing to enter system sleep state S3
  Aug 21 21:03:15 kernel: ACPI: EC: event blocked
  Aug 21 21:03:15 kernel: ACPI: EC: EC stopped
  Aug 21 21:03:15 kernel: ACPI: PM: Saving platform NVS memory
  Aug 21 21:03:15 kernel: Disabling non-boot CPUs ...
  Aug 21 21:03:15 kernel: smpboot: CPU 1 is now offline
  Aug 21 21:03:15 kernel: smpboot: CPU 2 is now offline
  Aug 21 21:03:15 kernel: smpboot: CPU 3 is now offline
  Aug 21 21:03:15 kernel: ACPI: PM: Low-level resume complete
  Aug 21 21:03:15 kernel: ACPI: EC: EC started
  Aug 21 21:03:15 kernel: ACPI: PM: Restoring platform NVS memory
  Aug 21 21:03:15 kernel: Enabling non-boot CPUs ...
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
  Aug 21 21:03:15 kernel: CPU1 is up
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
  Aug 21 21:03:15 kernel: CPU2 is up
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
  Aug 21 21:03:15 kernel: CPU3 is up
  Aug 21 21:03:15 kernel: ACPI: PM: Waking up from system sleep state S3
  Aug 21 21:03:15 kernel: ACPI: EC: interrupt unblocked
  Aug 21 21:03:15 kernel: ACPI: EC: event unblocked
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is 
disabled/in DSI mode with an ungated>
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is 
disabled/in DSI mode with an ungate>
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is 
disabled/in DSI mode with an ungate>
  Aug 21 21:03:15 kernel: nvme nvme0: Shutdown timeout set to 8 seconds
  Aug 21 21:03:15 kernel: nvme nvme0: 4/0/0 default/read/poll queues
  Aug 21 21:03:15 kernel: thinkpad_acpi: Unknown/reserved multi mode value 
0x for type 4, please report this to ibm-acpi-de...@lists.sourceforge.net
  Aug 21 21:03:15 kernel: usb 1-8: reset high-speed USB device number 3 using 
xhci_hcd
  Aug 21 21:03:15 kernel: usb 1-9: reset full-speed USB device number 4 using 
xhci_hcd
  Aug 21 21:03:15 kernel: OOM killer enabled.
  Aug 21 21:03:15 kernel: Restarting tasks ... done.
  Aug 21 21:03:15 kernel: random: crng reseeded on system resumption
  Aug 21 21:03:15 kernel: kauditd_printk_skb: 14405 callbacks suppressed
  Aug 21 21:03:15 systemd-resolved[708]: Clock change detected. Flushing caches.
  Aug 21 21:03:15 systemd-sleep[2158]: System returned from sleep state.
  Aug 21 21:03:15 kernel: PM: suspend exit
  Aug 21 21:03:15 systemd[1]: systemd-suspend.service: Deactivated successfully.
  Aug 21 21:03:15 systemd[1]: Finished System Suspend.
  Aug 21 21:03:15 systemd[1]: Sto

[Kernel-packages] [Bug 2073892] Re: i am continouly gettig this bug related to wifi and my screen also get blinking indefinitly when using libra office or chrome for much more time

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

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

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

Title:
  i am continouly gettig this bug related to wifi and my screen also get
  blinking indefinitly when using libra office or chrome for much more
  time

Status in linux package in Ubuntu:
  Expired

Bug description:
  501] iwlwifi :00:14.3: Unhandled alg: 0x703
  [  878.792743] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe 
A (start=53653 end=53654) time 262 us, min 1073, max 1079, scanline start 1071, 
end 1088
  [  893.917673] audit: type=1400 audit(1721743533.693:166): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=5080 
comm="snap-confine" capability=12  capname="net_admin"
  [  893.917679] audit: type=1400 audit(1721743533.693:167): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=5080 
comm="snap-confine" capability=38  capname="perfmon"
  [  893.994841] audit: type=1400 audit(1721743533.770:168): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" 
name="/usr/local/share/" pid=5094 comm="5" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [  894.037655] audit: type=1400 audit(1721743533.813:169): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" 
name="/proc/5107/maps" pid=5107 comm="5" requested_mask="r" denied_mask="r" 
fsuid=1000 ouid=0
  [  895.629353] audit: type=1107 audit(1721743535.405:170): pid=872 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.120" pid=5080 label="snap.firefox.firefox" peer_pid=5253 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? 
terminal=?'
  [  895.631813] audit: type=1107 audit(1721743535.407:171): pid=872 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.120" pid=5080 label="snap.firefox.firefox" peer_pid=5253 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? 
terminal=?'
  [  898.947932] iwlwifi :00:14.3: Unhandled alg: 0x703
  [  898.948972] iwlwifi :00:14.3: Unhandled alg: 0x703
  [  898.950533] iwlwifi :00:14.3: Unhandled alg: 0x703
  [  898.953941] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1031.274882] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1031.340347] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.559980] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.563289] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.564746] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.567359] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.571541] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.573115] iwlwifi :00:14.3: Unhandled alg: 0x703
  [ 1097.574902] iwlwifi :00:14.3: Unhandled alg: 0x703

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-38-generic 6.8.0-38.38
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gurditta   1806 F pipewire
   /dev/snd/controlC0:  gurditta   1810 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 23 19:34:19 2024
  InstallationDate: Installed on 2024-05-19 (65 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 5986:211c Bison Electronics Inc. HD Webcam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Micro-Star International Co., Ltd. Modern 14 B10MW
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=f5cecc53-fdaa-4f8d-8dbc-51670f3a2183 ro quiet splash i915.modeset=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-38-generic N/A
   linux-backports-modules-6.8.0-38-generic  N/A
   linux-firmware20240318.g

[Kernel-packages] [Bug 2073651] Re: Wifi does not work after wake-up, wifi driver crashes

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

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

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

Title:
  Wifi does not work after wake-up, wifi driver crashes

Status in linux package in Ubuntu:
  Expired

Bug description:
  After waking up from sleep, wifi does not work anymore. It looks like
  the machine is connected to wifi though. If I disable and re-enable
  the wifi connection, the driver crashes.

  The crash is shown is dmesg. I have attached a file that shows what is
  going on.

  I have installed the latest 6.9.9 mainline and the issue does not
  happen with it. 6.8.0.35 causes issues for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-38-generic 6.8.0-38.38
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 20 08:36:30 2024
  InstallationDate: Installed on 2023-07-10 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: LENOVO 82L7
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=a2361136-2f7a-4575-beb1-43fa8a461249 ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-38-generic N/A
   linux-backports-modules-6.8.0-38-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-05-22 (59 days ago)
  dmi.bios.date: 04/02/2024
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GECN38WW(V1.22)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 Pro 14ACN6
  dmi.ec.firmware.release: 1.38
  dmi.modalias: 
dmi:bvnLENOVO:bvrGECN38WW(V1.22):bd04/02/2024:br1.38:efr1.38:svnLENOVO:pn82L7:pvrIdeaPad5Pro14ACN6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad5Pro14ACN6:skuLENOVO_MT_82L7_BU_idea_FM_IdeaPad5Pro14ACN6:
  dmi.product.family: IdeaPad 5 Pro 14ACN6
  dmi.product.name: 82L7
  dmi.product.sku: LENOVO_MT_82L7_BU_idea_FM_IdeaPad 5 Pro 14ACN6
  dmi.product.version: IdeaPad 5 Pro 14ACN6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073651/+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 2073711] Re: unchecked MSR access error: RDMSR from 0xc00102f1

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

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

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

Title:
  unchecked MSR access error: RDMSR from 0xc00102f1

Status in linux package in Ubuntu:
  Expired

Bug description:
  [0.368219] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
  [0.368757] smp: Bringing up secondary CPUs ...
  [0.368820] x86: Booting SMP configuration:
  [0.368821]  node  #0, CPUs:  #1
  [0.004512] unchecked MSR access error: RDMSR from 0xc00102f1 at rIP: 
0xb7b8b7a3 (mce_setup+0x153/0x190)
  [0.004512] Call Trace:
  [0.004512]  
  [0.004512]  ? show_stack_regs+0x23/0x29
  [0.004512]  ? ex_handler_msr.cold+0x74/0x9a
  [0.004512]  ? fixup_exception+0x108/0x300
  [0.004512]  ? exc_general_protection+0xe3/0x3f0
  [0.004512]  ? asm_exc_general_protection+0x27/0x30
  [0.004512]  ? mce_setup+0x153/0x190
  [0.004512]  ? mce_setup+0x8b/0x190
  [0.004512]  machine_check_poll+0x56/0x280
  [0.004512]  __mcheck_cpu_init_generic+0x3d/0xb0
  [0.004512]  mcheck_cpu_init+0x151/0x480
  [0.004512]  identify_cpu+0x513/0x780
  [0.004512]  identify_secondary_cpu+0x1c/0xc0
  [0.004512]  smp_store_cpu_info+0x5a/0x80
  [0.004512]  start_secondary+0x53/0x180
  [0.004512]  secondary_startup_64_no_verify+0xc2/0xcb
  [0.004512]  
  [0.369056]#2   #3   #4   #5   #6   #7   #8   #9  #10  #11  #12  #13  
#14  #15  #16  #17  #18  #19  #20  #21  #22  #23
  [0.377486] smp: Brought up 1 node, 24 CPUs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.189.187
  ProcVersionSignature: Ubuntu 5.15.0-116.126~20.04.1-generic 5.15.158
  Uname: Linux 5.15.0-116-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  hbucher3912 F pulseaudio
   /dev/snd/pcmC3D0p:   hbucher3912 F...m pulseaudio
   /dev/snd/controlC2:  hbucher3912 F pulseaudio
   /dev/snd/controlC0:  hbucher3912 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jul 21 15:30:02 2024
  InstallationDate: Installed on 2021-06-16 (1131 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-116-generic 
root=UUID=6406e681-0601-4b8a-beb6-ed804b63cb71 ro quiet splash nosmt 
mitigations=off isolcpus=18-23 nohz_full=18-23 clocksource=tsc tsc=reliable 
iommu=off intel_iommu=off default_hugepagesz=2MB hugepagesz=1G hugepages=2 
hugepagesz=2M hugepages=128 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-116-generic N/A
   linux-backports-modules-5.15.0-116-generic  N/A
   linux-firmware  1.187.39
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2024-01-13 (190 days ago)
  dmi.bios.date: 09/07/2022
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FD
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFD:bd09/07/2022:br5.15:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073711/+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 2077260] Re: freeze after updating to newest kernel on log in sreen or just after log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

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

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

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

Title:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to rester to 6.5.0-45

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-45-generic 6.5.0-45.45~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 15:53:56 2024
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michal 2670 F wireplumber
   /dev/snd/seq:michal 2665 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  MachineType: Hewlett-Packard HP G62 Notebook PC
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=62689215-60a8-4e0a-8e4e-fb3115fd7b88 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-45-generic N/A
   linux-backports-modules-6.5.0-45-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  Tags: noble wayland-session
  Uname: Linux 6.5.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/29/2010
  dmi.bios.release: 15.37
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1439
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 60.3F
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 60.63
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd10/29/2010:br15.37:efr60.63:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn1439:rvr60.3F:cvnHewlett-Packard:ct10:cvrChassisVersion:skuLD667EA#AKD:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP G62 Notebook PC
  dmi.product.sku: LD667EA#AKD
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.init.d.apport: 2024-07-22T14:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077260/+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 2081231] Re: kernel 6.8.0-40: ext4 online resize on thin-provisioned storage gives 'invalid opcode'

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

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

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

Title:
  kernel 6.8.0-40: ext4 online resize on thin-provisioned storage gives
  'invalid opcode'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  We're seeing failures of an ext4 resize on LVM and Ceph block devices
  in the LXD CI; the following call trace happens during resize2fs of an
  ext4 FS on an LVM lv. I'll also upload an apport report. Let me know
  if there's anything else I can provide!

  ---

  [   54.268802] EXT4-fs (dm-8): mounted filesystem 
210714a1-4375-4524-ab2e-019d0859cf5f r/w with ordered data mode. Quota mode: 
none.
  [   54.273065] EXT4-fs (dm-8): resizing filesystem from 7168 to 786432 blocks
  [   54.274006] [ cut here ]
  [   54.274012] kernel BUG at fs/ext4/resize.c:324!
  [   54.274773] invalid opcode:  [#1] PREEMPT SMP NOPTI
  [   54.275841] CPU: 10 PID: 1397 Comm: resize2fs Tainted: P   O   
6.8.0-40-generic #40~22.04.3-Ubuntu
  [   54.282782] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 
unknown 2/2/2022
  [   54.285284] RIP: 0010:ext4_alloc_group_tables+0x532/0x540
  [   54.286769] Code: c2 f7 da 44 01 e0 8d 48 ff 89 4d c8 44 31 e1 85 d1 75 17 
b9 fd ff ff ff 66 89 4d cc e9 32 fb ff ff 44 8b 45 a0 e9 a8 fe ff ff <0f> 0b 66 
66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90
  [   54.291216] RSP: 0018:b691c3c53b78 EFLAGS: 00010202
  [   54.292109] RAX: 0018 RBX: 9bce87f5b000 RCX: 
0016
  [   54.293312] RDX: fff0 RSI: 9bce8186d560 RDI: 
9bce822a7800
  [   54.294433] RBP: b691c3c53bd8 R08: 0010 R09: 

  [   54.295551] R10:  R11:  R12: 
0001
  [   54.296515] R13: 9bce822a7800 R14: 9bce8186d560 R15: 
fffc3fe7
  [   54.297393] FS:  75726aea3b80() GS:9bcf79d0() 
knlGS:
  [   54.298382] CS:  0010 DS:  ES:  CR0: 80050033
  [   54.299197] CR2: 75726ac5a230 CR3: 0001192b4000 CR4: 
00750ef0
  [   54.300157] PKRU: 5554
  [   54.300520] Call Trace:
  [   54.300734]  
  [   54.300910]  ? show_regs+0x6d/0x80
  [   54.301191]  ? die+0x37/0xa0
  [   54.301674]  ? do_trap+0xd4/0xf0
  [   54.302163]  ? do_error_trap+0x71/0xb0
  [   54.302675]  ? ext4_alloc_group_tables+0x532/0x540
  [   54.303151]  ? exc_invalid_op+0x52/0x80
  [   54.303728]  ? ext4_alloc_group_tables+0x532/0x540
  [   54.304445]  ? asm_exc_invalid_op+0x1b/0x20
  [   54.305092]  ? ext4_alloc_group_tables+0x532/0x540
  [   54.305833]  ext4_resize_fs+0x378/0x6d0
  [   54.306434]  __ext4_ioctl+0x34e/0x1160
  [   54.307028]  ? filename_lookup+0xe4/0x200
  [   54.307625]  ? xa_load+0x87/0xf0
  [   54.308168]  ext4_ioctl+0xe/0x20
  [   54.308697]  __x64_sys_ioctl+0xa0/0xf0
  [   54.309328]  x64_sys_call+0xa68/0x24b0
  [   54.30]  do_syscall_64+0x81/0x170
  [   54.310715]  ? mntput+0x24/0x50
  [   54.311339]  ? path_put+0x1e/0x30
  [   54.311982]  ? do_faccessat+0x1c2/0x2f0
  [   54.312720]  ? syscall_exit_to_user_mode+0x89/0x260
  [   54.313640]  ? do_syscall_64+0x8d/0x170
  [   54.314424]  ? handle_mm_fault+0xad/0x380
  [   54.315080]  ? do_user_addr_fault+0x337/0x670
  [   54.315484]  ? irqentry_exit_to_user_mode+0x7e/0x260
  [   54.315875]  ? irqentry_exit+0x43/0x50
  [   54.316172]  ? clear_bhb_loop+0x15/0x70
  [   54.316483]  ? clear_bhb_loop+0x15/0x70
  [   54.317223]  ? clear_bhb_loop+0x15/0x70
  [   54.317869]  entry_SYSCALL_64_after_hwframe+0x78/0x80
  [   54.318699] RIP: 0033:0x75726ad1a94f
  [   54.319434] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 
3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00
  [   54.323404] RSP: 002b:7ffd784e7a80 EFLAGS: 0246 ORIG_RAX: 
0010
  [   54.324609] RAX: ffda RBX: 0001 RCX: 
75726ad1a94f
  [   54.325304] RDX: 7ffd784e7b80 RSI: 40086610 RDI: 
0004
  [   54.325933] RBP: 5b0d59a2c990 R08:  R09: 
7ffd784e79b7
  [   54.326570] R10:  R11: 0246 R12: 
0004
  [   54.327122] R13: 5b0d59a2ca40 R14: 5b0d59a2eb00 R15: 

  [   54.327672]  
  [   54.327974] Modules linked in: dm_snapshot vhost_vsock vhost vhost_iotlb 
nft_masq ipmi_devintf ipmi_msghandler nft_chain_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 bridge stp llc nf_tables nfnetlink binfmt_misc 
nls_iso8859_1 zfs(PO) spl(O) intel_rapl_msr intel_rapl_common 
intel_uncore_frequency_common intel_pmc_core intel_vsec pmt_telemetry pmt_class 
kvm_intel kvm irqbypass crct10dif_p

[Kernel-packages] [Bug 2063532] Re: missing uic

2024-09-19 Thread Launchpad Bug Tracker
[Expired for pyqt6 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  missing uic

Status in linux package in Ubuntu:
  Invalid
Status in pyqt6 package in Ubuntu:
  Expired

Bug description:
  Package python3-pyqt6 does not provide uic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063532/+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 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4

2024-09-19 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-hwe-6.8 - 6.8.0-45.45~22.04.1

---
linux-hwe-6.8 (6.8.0-45.45~22.04.1) jammy; urgency=medium

  * jammy/linux-hwe-6.8: 6.8.0-45.45~22.04.1 -proposed tracker (LP:
#2078099)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.hwe-6.8/dkms-versions -- update from kernel-versions
  (main/s2024.08.05)

  [ Ubuntu: 6.8.0-45.45 ]

  * noble/linux: 6.8.0-45.45 -proposed tracker (LP: #2078100)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/s2024.08.05)
  * Noble update: upstream stable patchset 2024-08-09 (LP: #2076435) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf
  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub
  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42224
- net: dsa: mv88e6xxx: Correct check for empty list
  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42154
- tcp_metrics: validate source addr length
  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc
  * CVE-2024-42159
- scsi: mpi3mr: Sanitise num_phys

 -- Stefan Bader   Wed, 11 Sep 2024 15:33:32
+0200

** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  Virtualbox Guru meditation on VM start caused by kernel commit in
  v6.9-rc4

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-6.8 source package in Jammy:
  Fix Released
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid
Status in virtualbox source package in Jammy:
  Confirmed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2073267

  SRU Justification:

  [Impact]

  Commit "randomize_kstack: Improve entropy diffusion" changed the
  kernel stack for entropy to 1KiB, limiting the thread kernel stack to
  15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer
  maintained upstream. The issue does not persist on version 7.0.20 due to a
  code refactoring that probably resulted in less stack usage. Fixing it on
  the jammy virtualbox package side is not straightfoward because the fix is
  not easy to backport to 6.x and upgrading the jammy package to 7.x breaks
  current users machines that run Windows, but not only.
  Users need to uninstall the Guest additions drivers, migrate the
  virtualbox package to 7.x, boot each VMs and install the Guest additions
  drivers in each VM.

  This impacts:
  1. jammy:linux
  2. jammy:linux-hwe-6.8
  3. focal:linux-hwe-5.15

  [Fix]

  Revert commit "randomize_kstack: Improve entropy diffusion"

  [Test Plan]

  Without this fix, a VM would crash, showing with "VCPU0: Guru
  Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)".
  After the kernel upgrade, all VMs should run with no problem.

  [Where problems could occur]
  This may have an impact on security. The commit is a fix to improve the
  stack entropy.

  Original description:

  It worked yesterday, but today I get a Guru Meditation trying to start
  some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru
  Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this
  may have started due to a Linux kernel upgrade I installed this
  morning.

  A fresh VM with no disk shows the issue. Sometimes turning off the I/O
  APIC makes the issue go away, sometimes not. Turning off nested paging
  sometimes lets VirtualBox make a little bit of progress w.r.t. booting
  VMs, but that usually still crashes before the VM finishes starting.

  This may be related to this bug reported on the VirtualBox forums:
  
https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538

  https://forums.virtualbox.org/viewtopic.php?t=111918

  Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is
  6.1.50-dfsg-1~ubuntu1.22.04.1.

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


--

[Kernel-packages] [Bug 2062568] Re: nfsd gets unresponsive after some hours of operation

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

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

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

Title:
  nfsd gets unresponsive after some hours of operation

Status in linux package in Ubuntu:
  Confirmed
Status in nfs-utils package in Ubuntu:
  Confirmed

Bug description:
  I installed the 24.04 Beta on two test machines that were running
  22.04 without issues before. One of them exports two volumes that are
  mounted by the other machine, which primarily uses them as a secondary
  storage for ccache.

  After being up for a couple of hours (happened twice since yesterday
  evening) it seems that nfsd on the machine exporting the volumes hangs
  on something.

  From dmesg on the server (repeated a few times):

  [11183.290548] INFO: task nfsd:1419 blocked for more than 1228 seconds.
  [11183.290558]   Not tainted 6.8.0-22-generic #22-Ubuntu
  [11183.290563] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [11183.290582] task:nfsdstate:D stack:0 pid:1419  tgid:1419  
ppid:2  flags:0x4000
  [11183.290587] Call Trace:
  [11183.290602]  
  [11183.290606]  __schedule+0x27c/0x6b0
  [11183.290612]  schedule+0x33/0x110
  [11183.290615]  schedule_timeout+0x157/0x170
  [11183.290619]  wait_for_completion+0x88/0x150
  [11183.290623]  __flush_workqueue+0x140/0x3e0
  [11183.290629]  nfsd4_probe_callback_sync+0x1a/0x30 [nfsd]
  [11183.290689]  nfsd4_destroy_session+0x186/0x260 [nfsd]
  [11183.290744]  nfsd4_proc_compound+0x3af/0x770 [nfsd]
  [11183.290798]  nfsd_dispatch+0xd4/0x220 [nfsd]
  [11183.290851]  svc_process_common+0x44d/0x710 [sunrpc]
  [11183.290924]  ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd]
  [11183.290976]  svc_process+0x132/0x1b0 [sunrpc]
  [11183.291041]  svc_handle_xprt+0x4d3/0x5d0 [sunrpc]
  [11183.291105]  svc_recv+0x18b/0x2e0 [sunrpc]
  [11183.291168]  ? __pfx_nfsd+0x10/0x10 [nfsd]
  [11183.291220]  nfsd+0x8b/0xe0 [nfsd]
  [11183.291270]  kthread+0xef/0x120
  [11183.291274]  ? __pfx_kthread+0x10/0x10
  [11183.291276]  ret_from_fork+0x44/0x70
  [11183.291279]  ? __pfx_kthread+0x10/0x10
  [11183.291281]  ret_from_fork_asm+0x1b/0x30
  [11183.291286]  

  From dmesg on the client (repeated a number of times):
  [ 6596.911785] RPC: Could not send backchannel reply error: -110
  [ 6596.972490] RPC: Could not send backchannel reply error: -110
  [ 6837.281307] RPC: Could not send backchannel reply error: -110

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nfs-kernel-server 1:2.6.4-3ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  .etc.request-key.d.id_resolver.conf: create   id_resolver *   *   
/usr/sbin/nfsidmap -t 600 %k %d
  ApportVersion: 2.28.1-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr 19 14:10:25 2024
  InstallationDate: Installed on 2024-04-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 
(20240410.1)
  NFSMounts:

  NFSv4Mounts:

  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062568/+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 1318951] Re: kernel update fails with /boot on FAT32

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

** Changed in: linux-base (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/1318951

Title:
  kernel update fails with /boot on FAT32

Status in dpkg package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed
Status in dpkg package in Debian:
  New
Status in linux-base package in Debian:
  New

Bug description:
  My latest system upgrade failed because it can't upgrade the kernel:

    $sudo env LANGUAGE=en_US apt-get upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    You might want to run 'apt-get -f install' to correct these.
    The following packages have unmet dependencies:
     linux-signed-image-3.13.0-24-generic : Depends: 
linux-image-3.13.0-24-generic (= 3.13.0-24.47) but 3.13.0-24.46 is installed
    E: Unmet dependencies. Try using -f.

  When trying to install linux-image-3.13.0-24-generic manually it fails
  because it can't create a backup link for the old kernel. This really
  doesn't surprise me, because /boot is on a fat32 filesystem ( EFI
  System Partition ) so it shouldn't be possible to create any links at
  all.

  My fstab entries for boot are as follows:
    UUID=0E1E-3E58/mnt/efi  vfatdefaults 0  2
    /mnt/efi/ubuntu /boot   none  bind0 0

  Here is the output of me trying to install the kernel manually:

    $sudo env LANGUAGE=en_US apt-get install linux-image-3.13.0-24-generic
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer 
required:
  efibootmgr secureboot-db shim
    Use 'apt-get autoremove' to remove them.
    Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
    Recommended packages:
  grub-pc grub-efi-amd64 grub-efi-ia32 grub lilo
    The following packages will be upgraded:
  linux-image-3.13.0-24-generic
    1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    114 not fully installed or removed.
    Need to get 0 B/15,0 MB of archives.
    After this operation, 1.024 B disk space will be freed.
    (Reading database ... 205799 files and directories currently installed.)
    Preparing to unpack 
.../linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb ...
    Done.
    Unpacking linux-image-3.13.0-24-generic (3.13.0-24.47) over (3.13.0-24.46) 
...
    dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb 
(--unpack):
    unable to make backup link of `./boot/vmlinuz-3.13.0-24-generic' before 
installing new version: Operation not permitted
    dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
    Examining /etc/kernel/postrm.d .
    run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic 
/boot/vmlinuz-3.13.0-24-generic
    run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic 
/boot/vmlinuz-3.13.0-24-generic
    Errors were encountered while processing:
     
/var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb
    E  : Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1318951/+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 1318951] Re: kernel update fails with /boot on FAT32

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

** Changed in: dpkg (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/1318951

Title:
  kernel update fails with /boot on FAT32

Status in dpkg package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed
Status in dpkg package in Debian:
  New
Status in linux-base package in Debian:
  New

Bug description:
  My latest system upgrade failed because it can't upgrade the kernel:

    $sudo env LANGUAGE=en_US apt-get upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    You might want to run 'apt-get -f install' to correct these.
    The following packages have unmet dependencies:
     linux-signed-image-3.13.0-24-generic : Depends: 
linux-image-3.13.0-24-generic (= 3.13.0-24.47) but 3.13.0-24.46 is installed
    E: Unmet dependencies. Try using -f.

  When trying to install linux-image-3.13.0-24-generic manually it fails
  because it can't create a backup link for the old kernel. This really
  doesn't surprise me, because /boot is on a fat32 filesystem ( EFI
  System Partition ) so it shouldn't be possible to create any links at
  all.

  My fstab entries for boot are as follows:
    UUID=0E1E-3E58/mnt/efi  vfatdefaults 0  2
    /mnt/efi/ubuntu /boot   none  bind0 0

  Here is the output of me trying to install the kernel manually:

    $sudo env LANGUAGE=en_US apt-get install linux-image-3.13.0-24-generic
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer 
required:
  efibootmgr secureboot-db shim
    Use 'apt-get autoremove' to remove them.
    Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
    Recommended packages:
  grub-pc grub-efi-amd64 grub-efi-ia32 grub lilo
    The following packages will be upgraded:
  linux-image-3.13.0-24-generic
    1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    114 not fully installed or removed.
    Need to get 0 B/15,0 MB of archives.
    After this operation, 1.024 B disk space will be freed.
    (Reading database ... 205799 files and directories currently installed.)
    Preparing to unpack 
.../linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb ...
    Done.
    Unpacking linux-image-3.13.0-24-generic (3.13.0-24.47) over (3.13.0-24.46) 
...
    dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb 
(--unpack):
    unable to make backup link of `./boot/vmlinuz-3.13.0-24-generic' before 
installing new version: Operation not permitted
    dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
    Examining /etc/kernel/postrm.d .
    run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic 
/boot/vmlinuz-3.13.0-24-generic
    run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic 
/boot/vmlinuz-3.13.0-24-generic
    Errors were encountered while processing:
     
/var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb
    E  : Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1318951/+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 2081092] [NEW] black screen after amdgpu crash (ring gfx timeout)

2024-09-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since the last week 6.8 kernel update, the amdgpu driver regularly
crashes after a while, at least in screen saver.

No recovery, so black screen afterward and mandatory reboot.

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.5 LTS
Release:22.04
Codename:   jammy

# uname -a
Linux server 6.8.0-40-generic #40~22.04.3-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 30 
17:30:19 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

# lshw -class video
  *-display 
   description: VGA compatible controller
   product: Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:06:00.0
   logical name: /dev/fb0
   version: c7
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
   configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
   resources: irq:57 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fcf0-fcf3 memory:c-d

# lshw -class processor
  *-cpu 
   description: CPU
   product: AMD Ryzen 7 3700X 8-Core Processor
   vendor: Advanced Micro Devices [AMD]
   physical id: 11
   bus info: cpu@0
   version: 23.113.0
   serial: Unknown
   slot: AM4
   size: 4332MHz
   capacity: 4426MHz
   width: 64 bits
   clock: 100MHz
   capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx 
mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc 
cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 
sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 
hw_pstate ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a 
rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc 
cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru 
wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid 
decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl 
umip rdpid overflow_recov succor smca sev sev_es cpufreq
   configuration: cores=8 enabledcores=8 microcode=141561889 threads=16

Relevant part of the journal:
Sep 18 06:55:28 server kernel: [309106.875597] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=689970, emitted seq=689972
Sep 18 06:55:28 server kernel: [309106.876158] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xwayland pid 4403 thread 
Xwayland:cs0 pid 4408
Sep 18 06:55:28 server kernel: [309106.876702] amdgpu :06:00.0: amdgpu: GPU 
reset begin!
Sep 18 06:55:28 server kernel: [309106.876795] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876795] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876803] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876803] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876810] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876810] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876817] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876817] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876824] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876824] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876831] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876831] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876837] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876837] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876845] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876845] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876852] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876852] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876859] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876859] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876866] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876866] last message was failed ret is 
65535
Sep 18 06:55:28 server kernel: [309106.876872] amdgpu :06:00.0: amdgpu: 
Sep 18 06:55:28 server kernel: [309106.876872] last message was failed ret is 
65535
Sep 18 0

[Kernel-packages] [Bug 2069198] Re: OpenZFS High Load Average

2024-09-17 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 2057693 ***
https://bugs.launchpad.net/bugs/2057693

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

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

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

Title:
  OpenZFS High Load Average

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Currently Ubuntu 24.04 is using OpenZFS 2.2.2 which as a bug that
  raises the system load average to 2.00 when idle.

  Bug and fix documented here: https://github.com/openzfs/zfs/pull/15781

  Should be very simple to backport as it's a single line change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2069198/+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 2078573] Re: I can no longer boot from my Thunderbolt disk

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

** Changed in: initramfs-tools (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/2078573

Title:
  I can no longer boot from my Thunderbolt disk

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu 24.04.1 LTS
  Release:  24.04

  Package:linux-image-6.8.0-41-generic

  
  Since the kernel 6.8.0-36 has been updated to a newer version, I can no 
longer boot from my Thunderbolt disk. Even with the current kernel 6.8.0-41 it 
does not work.

  If I boot with the old kernel 6.8.0-36 it still works, but I don't
  want to work with it forever.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:roman  2357 F pipewire
   /dev/snd/controlC0:  roman  2361 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 31 18:34:27 2024
  InstallationDate: Installed on 2024-07-07 (55 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Dell Inc. Latitude 5550
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-36-generic 
root=/dev/mapper/cryptvg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-36-generic N/A
   linux-backports-modules-6.8.0-36-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2024
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0314H2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd07/18/2024:br1.6:efr1.5:svnDellInc.:pnLatitude5550:pvr:rvnDellInc.:rn0314H2:rvrA00:cvnDellInc.:ct10:cvr:sku0CB9:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5550
  dmi.product.sku: 0CB9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2078573/+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 2077945] Re: Error On Automatic suspend after sleep

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

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

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

Title:
  Error On Automatic suspend after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When the system goes to sleep and automatic suspend , i cant wake the
  system instead it goes to a black screen. and also the fan speen
  raises . i dont know wheather the problem is with the kernal version
  or with my graphic driver.I had checked if the issue persist on
  downgrading the kernal version but the issue still persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:prayag 2179 F pipewire
   /dev/snd/controlC0:  prayag 2183 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 13:13:36 2024
  InstallationDate: Installed on 2024-08-23 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 25a7:fa70 Areson Technology Corp Hydra 10
   Bus 001 Device 003: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge 
Mini Keyboard]
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Micro-Star International Co., Ltd. GF63 Thin 9SCSR
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=56a0ebbe-0013-4945-917b-97c6d1ab0c73 ro quiet splash acpi_sleep=deep 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2020
  dmi.bios.release: 5.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16R4IMS.505
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16R4
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16R4IMS.505:bd11/05/2020:br5.5:svnMicro-StarInternationalCo.,Ltd.:pnGF63Thin9SCSR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16R4:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16R4.5:
  dmi.product.family: GF
  dmi.product.name: GF63 Thin 9SCSR
  dmi.product.sku: 16R4.5
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077945/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)

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

** Changed in: linux (Ubuntu Noble)
   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/2077487

Title:
  Broken atime in 2.2.2-0ubuntu9 (noble's version)

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Confirmed
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  * 2.2.2-0ubuntu9 has the 6.7 compat series, including 
https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, 
but does not include the fix for that commit (affects both pre-6.7 and 
post-6.7),
  
https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. 
This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as 
writes to a file resetting atime back to 0 (reads still seem to work as 
expected though given that state), which of course breaks real-world things (in 
my case, I can no longer successfully run LLVM's test suite).

  Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like
  this isn't a kernel memory disclosure and is instead a deterministic
  use of 0, so I don't believe this to be a blatant security
  vulnerability. This also explains the behaviour observed above.

  This needs fixing in noble, and then propagating back through whatever
  kernels are pulling in this version, since linux-modules vendors
  copies of the pre-built DKMS modules, with the current 6.8 HWE kernel
  using 2.2.2-0ubuntu9 explicitly.

  [Fix]

  * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix
  atime update" from upstream ZFS as quilt patch.

  [Test Case]

  * Build tested against Noble generic
  * Ran autopkgktests for regressions, none encountered

  [Where things could go wrong]

  * Low chance of regression, isolated instantiation and logic fix.
  * Addition of time delta check could cause issues during unexpected delay > 2 
seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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 2055237] Re: Backport ps uart RS485 driver

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-xilinx-zynqmp - 5.15.0-1035.39

---
linux-xilinx-zynqmp (5.15.0-1035.39) jammy; urgency=medium

  * jammy/linux-xilinx-zynqmp: 5.15.0-1035.39 -proposed tracker (LP:
#2077835)

  * Backport ps uart  RS485  driver  (LP: #2055237)
- dt-bindings: serial: cdsn,uart: add power-domains
- dt-bindings: Add reference to rs485.yaml
- serial: Store character timing information to uart_port
- serial: take termios_rwsem for ->rs485_config() & pass termios as param
- tty: serial: uartps: Relocate cdns_uart_tx_empty to facilitate rs485
- tty: serial: uartps: Add rs485 support to uartps driver
- dt-bindings: serial: cdns,uart: Add optional reset property
- arm64: zynqmp: Add resets property for UART nodes
- tty: serial: uartps: Add support for uartps controller reset
- SAUCE: dts: zynqmp-sck-kd-g-revA: Enable uart0 for KD240
- SAUCE: arm64: zynqmp: dts: Add required properties for rs485 support for
  KD240
- SAUCE: arm64: zynqmp: dts: Add rts delay property for rs485 mode on KD240
- serial: 8250: Document termios parameter of serial8250_em485_config()
- serial: fix TIOCSRS485 locking

 -- Portia Stephens   Mon, 26 Aug 2024
09:21:51 +1000

** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Backport ps uart  RS485  driver

Status in linux-xilinx-zynqmp package in Ubuntu:
  Confirmed
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Released
Status in linux-xilinx-zynqmp source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  * Backports support for rs485 to the uartps driver from mainline.
  * One device tree patch is taken from the vendor's tree .

  [ Test Plan ]
  * Testing is needed to ensure this doesn't break the serial console on 
current platforms. QA will develop a new automated test to be integrated into 
cert testing
  * Testing of the RS485 port will be integrated into the cert testing for the 
KD240

  [ Where problems could occur ]

  * Three patch is not in mainline and only exists on the vendor tree ,
  it is a device tree change.

  [ Other info ]
  * The following 3 patches are required from the tty-dev tree. All other 
patches were pulled in to support the backport.
  1. 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=32152467ffac3b79eae7313959c310946b0e6072
  2. 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=74231ab6cc2d02303ddf1fabd878756c52f788a5
  3. 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=fccc9d9233f918ee50cf2955ae7134a7f3418351
  4. 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=cc3236cd758b07c1f36cabd55ea1740f0881faa0
  5. 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=b4337685010990385901405cc317a5a46b147b5a
  6. 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=e3896be240780ccade65cc6cc8925c6f12e7f6c6
  7. 
https://github.com/Xilinx/linux-xlnx/commit/6472141dd7401ff43fc0fbb3dbc253454c5be2ee

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055237/+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 2072456] Re: boot failure on kv260

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-xilinx-zynqmp - 5.15.0-1035.39

---
linux-xilinx-zynqmp (5.15.0-1035.39) jammy; urgency=medium

  * jammy/linux-xilinx-zynqmp: 5.15.0-1035.39 -proposed tracker (LP:
#2077835)

  * Backport ps uart  RS485  driver  (LP: #2055237)
- dt-bindings: serial: cdsn,uart: add power-domains
- dt-bindings: Add reference to rs485.yaml
- serial: Store character timing information to uart_port
- serial: take termios_rwsem for ->rs485_config() & pass termios as param
- tty: serial: uartps: Relocate cdns_uart_tx_empty to facilitate rs485
- tty: serial: uartps: Add rs485 support to uartps driver
- dt-bindings: serial: cdns,uart: Add optional reset property
- arm64: zynqmp: Add resets property for UART nodes
- tty: serial: uartps: Add support for uartps controller reset
- SAUCE: dts: zynqmp-sck-kd-g-revA: Enable uart0 for KD240
- SAUCE: arm64: zynqmp: dts: Add required properties for rs485 support for
  KD240
- SAUCE: arm64: zynqmp: dts: Add rts delay property for rs485 mode on KD240
- serial: 8250: Document termios parameter of serial8250_em485_config()
- serial: fix TIOCSRS485 locking

 -- Portia Stephens   Mon, 26 Aug 2024
09:21:51 +1000

** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  boot failure on kv260

Status in linux-xilinx-zynqmp package in Ubuntu:
  New
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Released
Status in linux-xilinx-zynqmp source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]
  * The KV260 is currently unable to boot, this will allow the board to boot.
  * Kernel boot testing of 5.15.0-1032.36 failed on the KV260. The new kernel 
is installed but the system does not come back up after a reboot. Console logs 
show that there is a soft lockup.

  [ Test Plan ]
  * Normal certification and kernel regression testing will be run on all GM'd
  platforms. The failure was catestrophic and was easily caught.

  [ Where problems could occur ]
  * Xilinx has changes to the dmaengine driver that have not been upstreamed,:
  specifically adding support for cyclic dma mode.  There is a risk that these
  non-upstreamed changes have not been tested with this change.

  [ Other Info ]
  * BugLink: https://bugs.launchpad.net/bugs/2072456
  * Upstream state in original commit was incorrect.
  * Upstream commit "dma: xilinx_dpdma: Fix locking"


  [2.028650] mtdoops: mtd device (mtddev=name/number) must be supplied^M
  [4.762858] OF: graph: no port node found in /axi/display@fd4a^M
  [   15.326703] [drm:drm_crtc_commit_wait] *ERROR* flip_done timed out^M
  [   15.326713] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* 
[CRTC:41:crtc-0] commit wait timed out^M
  [   20.462842] xhci-hcd xhci-hcd.0.auto: xHCI host controller not responding, 
assume dead^M
  [   20.462874] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up^M
  [   25.566706] [drm:drm_crtc_commit_wait] *ERROR* flip_done timed out^M
  [   25.566718] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* 
[CONNECTOR:43:DP-1] commit wait timed out^M
  [   35.806698] [drm:drm_crtc_commit_wait] *ERROR* flip_done timed out^M
  [   35.806707] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* 
[PLANE:40:plane-1] commit wait timed out^M
  [   44.006688] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[kworker/3:3:307]^M
  [   64.946689] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
  [   64.952639] rcu: >~~~0-...0: (1 GPs behind) idle=ca3/1/0x4002 
softirq=2317/2325 fqs=3000 ^M
  [   68.006688] watchdog: BUG: soft lockup - CPU#3 stuck for 45s! 
[kworker/3:3:307]^M
  [   92.006688] watchdog: BUG: soft lockup - CPU#3 stuck for 67s! 
[kworker/3:3:307]^M
  [  116.006688] watchdog: BUG: soft lockup - CPU#3 stuck for 90s! 
[kworker/3:3:307]^M 

  [  140.006689] watchdog: BUG: 
soft lockup - CPU#3 stuck for 112s! [kworker/3:3:307]^M 


 [  164.006689] watchdog: BUG: soft lockup - CPU#3 stuck for 134s! 
[kworker/3:3:307]^M 

 [  188.006689] watchdog: BUG: 
soft lockup - CPU#3 stuck for 157s! [kworker/3:3:307]^M 
 

[Kernel-packages] [Bug 2076108] Re: Update IMX547 out-of-tree driver code

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-xilinx-zynqmp - 5.15.0-1035.39

---
linux-xilinx-zynqmp (5.15.0-1035.39) jammy; urgency=medium

  * jammy/linux-xilinx-zynqmp: 5.15.0-1035.39 -proposed tracker (LP:
#2077835)

  * Backport ps uart  RS485  driver  (LP: #2055237)
- dt-bindings: serial: cdsn,uart: add power-domains
- dt-bindings: Add reference to rs485.yaml
- serial: Store character timing information to uart_port
- serial: take termios_rwsem for ->rs485_config() & pass termios as param
- tty: serial: uartps: Relocate cdns_uart_tx_empty to facilitate rs485
- tty: serial: uartps: Add rs485 support to uartps driver
- dt-bindings: serial: cdns,uart: Add optional reset property
- arm64: zynqmp: Add resets property for UART nodes
- tty: serial: uartps: Add support for uartps controller reset
- SAUCE: dts: zynqmp-sck-kd-g-revA: Enable uart0 for KD240
- SAUCE: arm64: zynqmp: dts: Add required properties for rs485 support for
  KD240
- SAUCE: arm64: zynqmp: dts: Add rts delay property for rs485 mode on KD240
- serial: 8250: Document termios parameter of serial8250_em485_config()
- serial: fix TIOCSRS485 locking

 -- Portia Stephens   Mon, 26 Aug 2024
09:21:51 +1000

** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update IMX547 out-of-tree driver code

Status in linux-xilinx-zynqmp package in Ubuntu:
  Confirmed
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  * With current use of non-devm functions the user is responsible for
  freeing the resources and since this is not handled currently the
  driver does not probe the sensor on the second load, since resources
  are not freed.

  * Here is a dmesg snippet:

  On first load
  ubuntu@kria:~$ sudo dmesg | grep imx547
  [ 72.621037] imx547: module is from the staging directory, the quality is 
unknown, you have been
  warned.
  [ 72.628992] imx547 7-001a: imx547 : imx547 probe success !
  On second load:
  ubuntu@kria:~$ sudo dmesg | grep imx547
  [ 312.319586] imx547 7-001a: GT TRX Reset GPIO not setup in DT
  [ 312.325487] imx547: probe of 7-001a failed with error -16

  * New implementation of using device managed ie devm_* functions ensures that 
resource is
  automatically removed when driver is unloaded.

  [ Test Plan ]

  * Xilinx will verify the functionality when testing kernel is
  provided.

  [ Where problems could occur ]

  * Since freeing of the GPIO resource is not explicitly handled in current 
implementation
  the driver fails to probe the sensor and fails to add it to media subsystem.

  [ Other Info ]

  * Patch/Tag to be included : https://github.com/Xilinx/mv-camera-
  sensor-module/releases/tag/v0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2076108/+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 2077571] Re: GVE stuck TX queues

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-gcp - 5.15.0-1069.77

---
linux-gcp (5.15.0-1069.77) jammy; urgency=medium

  * jammy/linux-gcp: 5.15.0-1069.77 -proposed tracker (LP: #2078120)

  * GVE stuck TX queues (LP: #2077571)
- gve: ignore nonrelevant GSO type bits when processing TSO headers
- gve: Fix an edge case for TSO skb validity check

  [ Ubuntu: 5.15.0-122.132 ]

  * jammy/linux: 5.15.0-122.132 -proposed tracker (LP: #2078154)
  * isolcpus are ignored when using cgroups V2, causing processes to have wrong
affinity (LP: #2076957)
- cgroup/cpuset: Optimize cpuset_attach() on v2
  * Jammy update: v5.15.164 upstream stable release (LP: #2076100) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf
  * CVE-2024-39494
- ima: Fix use-after-free on a dentry's dname.name
  * CVE-2024-39496
- btrfs: zoned: fix use-after-free due to race with dev replace
  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub
  * CVE-2024-38570
- gfs2: Rename sd_{ glock => kill }_wait
- gfs2: Fix potential glock use-after-free on unmount
  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc
  * CVE-2024-27012
- netfilter: nf_tables: restore set elements when delete set fails
  * CVE-2024-26677
- rxrpc: Fix delayed ACKs to not set the reference serial number

 -- Manuel Diewald   Fri, 30 Aug 2024
19:03:36 +0200

** Changed in: linux-gcp (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

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

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

Title:
  GVE stuck TX queues

Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gke package in Ubuntu:
  New
Status in linux-gkeop package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gke source package in Jammy:
  Fix Committed
Status in linux-gkeop source package in Jammy:
  Fix Committed
Status in linux-gcp source package in Noble:
  Fix Released
Status in linux-gke source package in Noble:
  Fix Committed
Status in linux-gkeop source package in Noble:
  Invalid

Bug description:
  [Impact]
  Request from Google to backport a set of patches to address issues in the GVE 
driver.

  [Fix]
  36e3b949e35964e22b9a57f960660fc599038dd4 (gve: Fix an edge case for TSO skb 
validity check)
  1b9f756344416e02b41439bf2324b26aa25e141c (gve: ignore nonrelevant GSO type 
bits when processing TSO headers)

  [Test]
  Compile and boot tested.

  [Where problems could occur]
  Changes are limited to the GVE driver.

  [Other info]
  #SF 00389911

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2077571/+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 2076361] Re: Lenovo X12 Detachable Gen 2 unresponsive under light load

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1013.13

---
linux-oem-6.8 (6.8.0-1013.13) noble; urgency=medium

  * noble/linux-oem-6.8: 6.8.0-1013.13 -proposed tracker (LP: #2078087)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.oem/dkms-versions -- update from kernel-versions
  (main/s2024.08.05)

  * Lenovo X12 Detachable Gen 2 unresponsive under light load (LP: #2076361)
- drm/i915: Enable Wa_16019325821
- drm/i915/guc: Add support for w/a KLVs
- drm/i915/guc: Enable Wa_14019159160

  [ Ubuntu: 6.8.0-45.45 ]

  * noble/linux: 6.8.0-45.45 -proposed tracker (LP: #2078100)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/s2024.08.05)
  * Noble update: upstream stable patchset 2024-08-09 (LP: #2076435) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf
  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub
  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42224
- net: dsa: mv88e6xxx: Correct check for empty list
  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42154
- tcp_metrics: validate source addr length
  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc
  * CVE-2024-42159
- scsi: mpi3mr: Sanitise num_phys

 -- Kuan-Ying Lee   Fri, 06 Sep 2024
10:32:46 +0800

** Changed in: linux-oem-6.8 (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  Lenovo X12 Detachable Gen 2 unresponsive under light load

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.8 package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Invalid
Status in linux-signed-lowlatency package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-oem-6.8 source package in Noble:
  Fix Released
Status in linux-signed source package in Noble:
  Invalid
Status in linux-signed-lowlatency source package in Noble:
  Invalid

Bug description:
  SRU Justification:
  ==

  [Impact]
  To encode some video files with ffmpeg, and the system becomes completely
  unresponsive for as long as the process executes.

  [Fix]
  Enable Wa_14019159160 and  Wa_16019325821 for MTL.

  [Test]
  Tested on hardware, the system works fine when run the same script to
  encode.

  [Where problems could occur]
  It may break intel i915 driver.
  =

  I've been using a Lenovo X12 Detachable Gen 2 model from 2024 [1] to
  encode some video files with ffmpeg, and the system becomes completely
  unresponsive for as long as the process executes. Although small, this
  is a pretty good device hardware wise, and while executing the system
  has plenty of RAM (32GB total, 10GB+ left), almost all CPUs are idle,
  no IO wait.

  [1] Intel Core Ultra 164U variant at:
  
https://psref.lenovo.com/syspool/Sys/PDF/Think_Tablets/ThinkPad_X12_Detachable_Gen_2/ThinkPad_X12_Detachable_Gen_2_Spec.pdf

  Things I've tried:

  1) Lowering the priority of ffmpeg with renice
  2) Lowering the priority of ffmpeg with ionice
  3) Using a single thread in ffmpeg
  4) Switching to the lowlatency kernel, with all recommended fiddling
  5) Switching to the OEM kernel (6.8.0-1010-oem)

  Nothing even touches the complete lack of responsiveness. The system
  becomes so unresponsive that when typing nothing shows up, and then
  characters show repeated as long sequences all at once.

  In addition to the attached information, some details about the moment
  the problem happens:

  top - 16:27:49 up  3:26,  1 user,  load average: 1.13, 0.70, 0.68
  Tasks: 397 total,   1 running, 396 sleeping,   0 stopped,   0 zombie
  %Cpu0  :  2.7 us,  0.0 sy,  0.0 ni, 56.3 id, 41.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu1  :  3.3 us,  0.3 sy,  0.0 ni, 96.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu2  :  3.0 us,  0.0 sy,  0.0 ni, 97.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu3  :  0.7 us,  1.0 sy,  6.3 ni,  2.7 id, 89.3 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu4  :  3.7 us,  0.0 sy,  0.0 ni, 96.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu5  :  4.0 us,  0.3 sy,  0.0 ni, 95.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st
  %Cpu6  :  3.3 us,  0.0

[Kernel-packages] [Bug 2076957] Re: isolcpus are ignored when using cgroups V2, causing processes to have wrong affinity

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-122.132

---
linux (5.15.0-122.132) jammy; urgency=medium

  * jammy/linux: 5.15.0-122.132 -proposed tracker (LP: #2078154)

  * isolcpus are ignored when using cgroups V2, causing processes to have wrong
affinity (LP: #2076957)
- cgroup/cpuset: Optimize cpuset_attach() on v2

  * Jammy update: v5.15.164 upstream stable release (LP: #2076100) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf

  * CVE-2024-39494
- ima: Fix use-after-free on a dentry's dname.name

  * CVE-2024-39496
- btrfs: zoned: fix use-after-free due to race with dev replace

  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub

  * CVE-2024-38570
- gfs2: Rename sd_{ glock => kill }_wait
- gfs2: Fix potential glock use-after-free on unmount

  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc

  * CVE-2024-27012
- netfilter: nf_tables: restore set elements when delete set fails

  * CVE-2024-26677
- rxrpc: Fix delayed ACKs to not set the reference serial number

 -- Manuel Diewald   Thu, 29 Aug 2024
14:23:02 +0200

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

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

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

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

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

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

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

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

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

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

Title:
  isolcpus are ignored when using cgroups V2, causing processes to have
  wrong affinity

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2076957

  [Impact]

  In latency sensitive environments, it is very common to use isolcpus
  to reserve a set of cpus that no other processes are to be placed on,
  and run just dpdk in poll mode.

  There is a bug in the jammy kernel, where if cgroups V2 are enabled,
  after several minutes the kernel will place other processes onto these
  reserved isolcpus at random. This disturbs dpdk and introduces
  latency.

  The issue does not occur with cgroups V1, so a workaround is to use
  cgroups V1 instead of V2 for the moment.

  [Fix]

  I arrived at this commit after a full git bisect, which fixes the
  issue. It landed in 6.2-rc1:

  commit 7fd4da9c1584be97ffbc40e600a19cb469fd4e78
  Author: Waiman Long 
  Date:   Sat Nov 12 17:19:39 2022 -0500
  Subject: cgroup/cpuset: Optimize cpuset_attach() on v2
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fd4da9c1584be97ffbc40e600a19cb469fd4e78

  Only the 5.15 Jammy kernel needs this fix. Focal works correctly as
  is.

  The commit skips calls to cpuset_attach() if the underlying cpusets or
  memory have not changed in a cgroup, and it seems to fix the issue.

  [Testcase]

  Deploy a bare metal server, ideally with a number of cores, 56 should be 
plenty.
  Use Jammy, with the 5.15 GA kernel.

  1) Edit /etc/default/grub and set GRUB_CMDLINE_LINUX_DEFAULT to have
  "isolcpus=4-7,32-35 rcu_nocb_poll rcu_nocbs=4-7,32-35 
systemd.unified_cgroup_hierarchy=1"
  2) sudo reboot
  3) sudo cat /sys/devices/system/cpu/isolated
  4-7,32-35
  4) sudo apt install s-tui stress
  5) sudo s-tui
  6) htop
  7) $ while true; do sudo ps -eLF | head -n 1; sudo ps -eLF | grep stress | 
awk -v a="4" '$9 == a {print;}'; sudo ps -eLF | grep stress | awk -v a="5" '$9 
== a {print;}'; sudo ps -eLF | grep stress | awk -v a="6" '$9 == a {print;}'; 
sudo ps -eLF | grep stress | awk -v a="7" '$9 == a {print;}'; sudo ps -eLF | 
grep stress | awk -v a="32" '$9 == a {print;}'; sudo ps -eLF | grep stress | 
awk -v a="33" '$9 == a {print;}'; sudo ps -eLF | grep stress | awk -v a="34" 
'$9 == a {print;}'; sudo ps -eLF | grep stress | awk -v a="35" '$9 == a 
{print;}'; sleep 5; done

  Setup isolcpus to separate off 4-7 and 32-35, so each NUMA node has a
  set of isolated CPUs.

  s-tui is a great frontend for stress, and it starts stress processes.
  All stress processes should initially be on non-isolated CPUs, confirm
  this with htop, that 4-7 and 32-25 are at 0% while every other cpu is
  at 100%.

  After 3 minutes, but sometimes it takes up to 10 minutes, a stress
  process, or the s-tui process will be incorrectly placed onto an
  isolated c

[Kernel-packages] [Bug 2076435] Re: Noble update: upstream stable patchset 2024-08-09

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.8.0-45.45

---
linux (6.8.0-45.45) noble; urgency=medium

  * noble/linux: 6.8.0-45.45 -proposed tracker (LP: #2078100)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/s2024.08.05)

  * Noble update: upstream stable patchset 2024-08-09 (LP: #2076435) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf

  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub

  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42224
- net: dsa: mv88e6xxx: Correct check for empty list

  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42154
- tcp_metrics: validate source addr length

  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc

  * CVE-2024-42159
- scsi: mpi3mr: Sanitise num_phys

 -- Manuel Diewald   Fri, 30 Aug 2024
10:32:37 +0200

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

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

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

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

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

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

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

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

Title:
  Noble update: upstream stable patchset 2024-08-09

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Fix Released

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

  Ported from the following upstream stable releases:
  v6.6.37, v6.9.8

 from git://git.kernel.org/

  usb: typec: ucsi: Never send a lone connector change ack
  usb: typec: ucsi: Ack also failed Get Error commands
  Input: ili210x - fix ili251x_read_touch_data() return value
  pinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER
  pinctrl: rockchip: fix pinmux bits for RK3328 GPIO2-B pins
  pinctrl: rockchip: fix pinmux bits for RK3328 GPIO3-B pins
  pinctrl: rockchip: use dedicated pinctrl type for RK3328
  pinctrl: rockchip: fix pinmux reset in rockchip_pmx_set
  MIPS: pci: lantiq: restore reset gpio polarity
  ASoC: rockchip: i2s-tdm: Fix trcm mode by setting clock on right mclk
  ASoC: mediatek: mt8183-da7219-max98357: Fix kcontrol name collision
  ASoC: atmel: atmel-classd: Re-add dai_link->platform to fix card init
  workqueue: Increase worker desc's length to 32
  ASoC: q6apm-lpass-dai: close graph on prepare errors
  bpf: Add missed var_off setting in set_sext32_default_val()
  bpf: Add missed var_off setting in coerce_subreg_to_size_sx()
  s390/pci: Add missing virt_to_phys() for directed DIBV
  ASoC: amd: acp: add a null check for chip_pdev structure
  ASoC: amd: acp: remove i2s configuration check in acp_i2s_probe()
  ASoC: fsl-asoc-card: set priv->pdev before using it
  net: dsa: microchip: fix initial port flush problem
  openvswitch: get related ct labels from its master if it is not confirmed
  mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems
  bpf: Fix overrunning reservations in ringbuf
  ibmvnic: Free any outstanding tx skbs during scrq reset
  net: phy: micrel: add Microchip KSZ 9477 to the device table
  net: dsa: microchip: use collision based back pressure mode
  ice: Rebuild TC queues on VSI queue reconfiguration
  xdp: Remove WARN() from __xdp_reg_mem_model()
  netfilter: fix undefined reference to 'netfilter_lwtunnel_*' when 
CONFIG_SYSCTL=n
  btrfs: use NOFS context when getting inodes during logging and log replay
  Fix race for duplicate reqsk on identical SYN
  ALSA: seq: Fix missing channel at encoding RPN/NRPN MIDI2 messages
  net: dsa: microchip: fix wrong register write when masking interrupt
  sparc: fix old compat_sys_select()
  sparc: fix compat recv/recvfrom syscalls
  parisc: use correct compat recv/recvfrom syscalls
  powerpc: restore some missing spu syscalls
  tcp: fix tcp_rcv_fastopen_synack() to enter TCP_CA_Loss for failed TFO
  ALSA: se

[Kernel-packages] [Bug 2077600] Re: Noble update: upstream stable patchset 2024-08-22

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.8.0-45.45

---
linux (6.8.0-45.45) noble; urgency=medium

  * noble/linux: 6.8.0-45.45 -proposed tracker (LP: #2078100)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/s2024.08.05)

  * Noble update: upstream stable patchset 2024-08-09 (LP: #2076435) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf

  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub

  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42224
- net: dsa: mv88e6xxx: Correct check for empty list

  * Noble update: upstream stable patchset 2024-08-22 (LP: #2077600) //
CVE-2024-42154
- tcp_metrics: validate source addr length

  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc

  * CVE-2024-42159
- scsi: mpi3mr: Sanitise num_phys

 -- Manuel Diewald   Fri, 30 Aug 2024
10:32:37 +0200

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

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

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

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

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

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

Title:
  Noble update: upstream stable patchset 2024-08-22

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Fix Released

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

  Ported from the following upstream stable releases:
  v6.6.38, v6.6.39, v6.9.9

 from git://git.kernel.org/

  locking/mutex: Introduce devm_mutex_init()
  leds: an30259a: Use devm_mutex_init() for mutex initialization
  crypto: hisilicon/debugfs - Fix debugfs uninit process issue
  drm/lima: fix shared irq handling on driver remove
  powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt.
  media: dvb: as102-fe: Fix as10x_register_addr packing
  media: dvb-usb: dib0700_devices: Add missing release_firmware()
  IB/core: Implement a limit on UMAD receive List
  scsi: qedf: Make qedf_execute_tmf() non-preemptible
  selftests/bpf: adjust dummy_st_ops_success to detect additional error
  selftests/bpf: do not pass NULL for non-nullable params in dummy_st_ops
  selftests/bpf: dummy_st_ops should reject 0 for non-nullable params
  RISC-V: KVM: Fix the initial sample period value
  crypto: aead,cipher - zeroize key buffer after use
  media: mediatek: vcodec: Only free buffer VA that is not NULL
  drm/amdgpu: Fix uninitialized variable warnings
  drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc
  drm/amdgpu: Initialize timestamp for some legacy SOCs
  drm/amd/display: Check index msg_id before read or write
  drm/amd/display: Check pipe offset before setting vblank
  drm/amd/display: Skip finding free audio for unknown engine_id
  drm/amd/display: Fix uninitialized variables in DM
  drm/amdgpu: fix uninitialized scalar variable warning
  drm/amdgpu: fix the warning about the expression (int)size - len
  media: dw2102: Don't translate i2c read into write
  riscv: Apply SiFive CIP-1200 workaround to single-ASID sfence.vma
  sctp: prefer struct_size over open coded arithmetic
  firmware: dmi: Stop decoding on broken entry
  Input: ff-core - prefer struct_size over open coded arithmetic
  wifi: mt76: replace skb_put with skb_put_zero
  wifi: mt76: mt7996: add sanity checks for background radar trigger
  thermal/drivers/mediatek/lvts_thermal: Check NULL ptr on lvts_data
  net: dsa: mv88e6xxx: Correct check for empty list
  media: dvb-frontends: tda18271c2dd: Remove casting during div
  media: s2255: Use refcount_t instead of atomic_t for num_channels
  media: dvb-frontends: tda10048: Fix integer overflow
  i2c: i801: Annotate apanel_addr as __ro_after_init
  powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n
  orangefs: fix out-of-bounds fsid access
  kunit: Fix timeout message
  powerpc/xmon: Check cpu id in commands "c#", "dp#" and "dx#"
  selftests/net: fix uninitialized variables
  igc: fix a log entry using uninitializ

[Kernel-packages] [Bug 2076100] Re: Jammy update: v5.15.164 upstream stable release

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-122.132

---
linux (5.15.0-122.132) jammy; urgency=medium

  * jammy/linux: 5.15.0-122.132 -proposed tracker (LP: #2078154)

  * isolcpus are ignored when using cgroups V2, causing processes to have wrong
affinity (LP: #2076957)
- cgroup/cpuset: Optimize cpuset_attach() on v2

  * Jammy update: v5.15.164 upstream stable release (LP: #2076100) //
CVE-2024-41009
- bpf: Fix overrunning reservations in ringbuf

  * CVE-2024-39494
- ima: Fix use-after-free on a dentry's dname.name

  * CVE-2024-39496
- btrfs: zoned: fix use-after-free due to race with dev replace

  * CVE-2024-42160
- f2fs: check validation of fault attrs in f2fs_build_fault_attr()
- f2fs: Add inline to f2fs_build_fault_attr() stub

  * CVE-2024-38570
- gfs2: Rename sd_{ glock => kill }_wait
- gfs2: Fix potential glock use-after-free on unmount

  * CVE-2024-42228
- drm/amdgpu: Using uninitialized value *size when calling 
amdgpu_vce_cs_reloc

  * CVE-2024-27012
- netfilter: nf_tables: restore set elements when delete set fails

  * CVE-2024-26677
- rxrpc: Fix delayed ACKs to not set the reference serial number

 -- Manuel Diewald   Thu, 29 Aug 2024
14:23:02 +0200

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

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

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

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

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

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

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

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

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

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

Title:
  Jammy update: v5.15.164 upstream stable release

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

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.164 upstream stable release
 from git://git.kernel.org/

  gcc-plugins: Rename last_stmt() for GCC 14+
  filelock: Remove locks reliably when fcntl/close race is detected
  ARM: 9324/1: fix get_user() broken with veneer
  ACPI: processor_idle: Fix invalid comparison with insertion sort for latency
  bpf: Fix overrunning reservations in ringbuf
  scsi: core: Fix a use-after-free
  scsi: core: alua: I/O errors for ALUA state transitions
  scsi: qedf: Don't process stag work during unload and recovery
  scsi: qedf: Wait for stag work during unload
  scsi: qedf: Set qed_slowpath_params to zero before use
  ACPI: EC: Abort address space access upon error
  ACPI: EC: Avoid returning AE_OK on errors in address space handler
  tools/power/cpupower: Fix Pstate frequency reporting on AMD Family 1Ah CPUs
  wifi: mac80211: mesh: init nonpeer_pm to active by default in mesh sdata
  wifi: mac80211: handle tasklet frames before stopping
  wifi: iwlwifi: mvm: d3: fix WoWLAN command version lookup
  wifi: iwlwifi: mvm: Handle BIGTK cipher in kek_kck cmd
  wifi: iwlwifi: mvm: properly set 6 GHz channel direct probe option
  wifi: mac80211: fix UBSAN noise in ieee80211_prep_hw_scan()
  selftests/openat2: Fix build warnings on ppc64
  Input: silead - Always support 10 fingers
  net: ipv6: rpl_iptunnel: block BH in rpl_output() and rpl_input()
  ila: block BH in ila_output()
  arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process
  null_blk: fix validation of block size
  kconfig: gconf: give a proper initial state to the Save button
  kconfig: remove wrong expr_trans_bool()
  fs/file: fix the check in find_next_fd()
  mei: demote client disconnect warning on suspend to debug
  nvme: avoid double free special payload
  wifi: cfg80211: wext: add extra SIOCSIWSCAN data check
  KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group()
  drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency
  ALSA: hda/realtek: Add more codec ID to no shutup pins list
  mips: fix compat_sys_lseek syscall
  Input: elantech - fix touchpad state on resume for Lenovo N24
  Input: i8042 - add Ayaneo Kun to i8042 quirk table
  bytcr_rt5640 : inverse jack detect for Archos 101 cesium
  ALSA: dmaengine: Synchronize dma chan

[Kernel-packages] [Bug 2048183] Re: Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-lowlatency - 6.11.0-1002.2

---
linux-lowlatency (6.11.0-1002.2) oracular; urgency=medium

  * oracular/linux-lowlatency: 6.11.0-1002.2 -proposed tracker (LP:
#2080028)

  * Miscellaneous Ubuntu changes
- [packaging] sync Build-Depends and Build-Depends-Indep wrt debian.master

 -- Paolo Pisati   Tue, 10 Sep 2024 08:38:45
+0200

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

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

Title:
  Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
  linux-*-tools-host binary packages

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  New
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-intel-iotg package in Ubuntu:
  New
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Confirmed
Status in linux-iot package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  Fix Released
Status in linux-lowlatency-hwe-5.15 package in Ubuntu:
  New
Status in linux-nvidia package in Ubuntu:
  New
Status in linux-nvidia-6.8 package in Ubuntu:
  New
Status in linux-xilinx-zynqmp package in Ubuntu:
  New
Status in linux-hwe-5.15 source package in Focal:
  New
Status in linux-ibm source package in Focal:
  New
Status in linux-intel-iotg-5.15 source package in Focal:
  New
Status in linux-iot source package in Focal:
  New
Status in linux-lowlatency-hwe-5.15 source package in Focal:
  New
Status in linux-hwe-6.5 source package in Jammy:
  New
Status in linux-ibm source package in Jammy:
  New
Status in linux-intel-iotg source package in Jammy:
  New
Status in linux-lowlatency source package in Jammy:
  New
Status in linux-nvidia source package in Jammy:
  New
Status in linux-nvidia-6.5 source package in Jammy:
  New
Status in linux-nvidia-6.8 source package in Jammy:
  Fix Released
Status in linux-realtime source package in Jammy:
  New
Status in linux-xilinx-zynqmp source package in Jammy:
  New
Status in linux-ibm source package in Noble:
  New
Status in linux-lowlatency source package in Noble:
  New
Status in linux-nvidia source package in Noble:
  New
Status in linux-nvidia-lowlatency source package in Noble:
  New

Bug description:
  [Impact]

  Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common
  and/or linux-*-tools-host binary deb packages. That is all wrong, only
  the primary/main linux source package should produce these. These
  packages result in install failures of the regular linux-cloud-tools-
  common, linux-tools-common and linux-tools-host packages.

  [Test Case]

  Check list of built binary packages in LP and verify the packages are
  not built.

  [Where Problems Could Occur]

  Already installed packages won't upgrade and become stale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048183/+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 2066982] Re: Azure: net: mana: Enable MANA driver on ARM64 with 4K page size

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  Azure: net: mana: Enable MANA driver on ARM64 with 4K page size

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Mantic:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Request to enable MANA driver on arm64 arch using 4k page size

  [Fix]

  * Clean cherry-pick, commit 40a1d11fc670ac03c5dc2e5a9724b330e74f38b0
  net: mana: Enable MANA driver on ARM64 with 4K page size

  [Test Plan]

  * Compile tested
  * Ensured mana modules built for arm64 arch
  * Boot tested
  * Loaded and unloaded mana_ib successfully
  * Microsoft to test

  [Regression potential]

  * Limited to configuration options, no regression potential

  [Other Info]

  * SF: #00385931

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2066982/+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 2069362] Re: Request to enable VDPA kernel config

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  Request to enable VDPA kernel config

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Request from MSFT to set the following config options:

  CONFIG_VDPA=m
  CONFIG_VDPA_SIM=m
  CONFIG_VDPA_SIM_NET=m
  CONFIG_VDPA_SIM_BLOCK=m
  CONFIG_VHOST_RING=m
  CONFIG_VHOST_VDPA=m

  [Fix]

  * SAUCE patch to enable config options

  [Test Plan]

  * Compile tested
  * Boot tested
  * Microsoft tested

  [Regression potential]

  * Changes isolated, minimal regression risk
  * Configs enabled in Generic, but missing from Azure

  [Other info]

  * SF #00386379

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2069362/+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 2071445] Re: Ubuntu 24.04 for Azure unable to run 32bit binaries

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 24.04 for Azure unable to run 32bit binaries

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-signed-azure package in Ubuntu:
  Invalid
Status in linux-signed-azure-6.8 package in Ubuntu:
  Invalid
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released
Status in linux-signed-azure source package in Oracular:
  Invalid
Status in linux-signed-azure-6.8 source package in Oracular:
  Invalid

Bug description:
  [Impact]

  ## Issue details

  The configuration of the kernel in linux-image-6.8.0-1008-azure is 
incompatible with the way libc6:i386 is built.
  This leads to the error "The futex facility returned an unexpected error 
code." and application crash when trying to execute many 32bit applications in 
x86-64 machines.

  In very short the issue is the following:
  This kernel image is compiled with CONFIG_COMPAT_32BIT_TIME=n, unlike the 
vanilla Ubuntu 24.04 kernel images.
  But, the glibc / libc6:i386 distributed with Ubuntu24.04 is compiled needing 
the syscalls enabled with that option.
  i.e. **This kernel configuration is just incompatible with the provided 
glibc**

  In detail:
  glibc when built for 32bit, if not told which kernel is built for, will 
decide if the time_t value fits or not in a 32bit time_t, and do either the 32 
or 64bit syscall:
  
https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/futex-internal.c;h=0bb1dd51f66802521afd71b9246222ed0ea0d862;hb=refs/heads/release/2.39/master#l90
  calls with no deadline fit in the 32bit version, but as the kernel does not 
provide this syscall, glibc will just get  a ENOSYS, and glibc will error out 
aborting the program
  ```
  abort (abort.c:79)
  __libc_message_impl.cold (libc_fatal.c:132)
  __libc_fatal (libc_fatal.c:141)
  futex_fatal_error (futex-internal.h:87)
  __futex_abstimed_wait_common (futex-internal.c:119)
  ```
  after printing "The futex facility returned an unexpected error code.\n":
  
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/nptl/futex-internal.h;h=0e87e92d15ab92f5069463719a494e97d9800431;hb=refs/heads/release/2.39/master#l87

  ## Expected behavior:

  * No crashes for 32bit applications with this kernel
  * This kernel image built with CONFIG_COMPAT_32BIT_TIME=y

  ## Aditional info:

  For reference, this is the current vanilla Ubuntu 24.04 kernel for x86_64 and 
this config:
  ```
  $ uname -a
  Linux  6.8.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Mon May 20 
15:51:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_COMPAT_32BIT_TIME /boot/config-$(uname -r)
  CONFIG_COMPAT_32BIT_TIME=y
  ```

  On the other hand this is the kernel config for this kernel image:
  ```
  Linux <> 6.8.0-1008-azure #8-Ubuntu SMP Fri May 17 10:44:55 UTC 2024 x86_64 
x86_64 x86_64 GNU/Linux
  # CONFIG_COMPAT_32BIT_TIME is not set
  ```

  Related github issue (the issue was found in github ubuntu 24.04 runners)
  https://github.com/actions/runner-images/issues/9977

  [Fix]

  Reenable COMPAT_32BIT_TIME

  [Test Case]

  See above.

  [Where Problems Could Occur]

  Disabling COMPAT_32BIT_TIME in Noble azure introduced a regression
  when running x86 binaries, so the fix is not expected to break
  anything (new).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2071445/+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 2069204] Re: Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Request from MSFT to include patch to disable CET Shadow Stack on
  SEV-SNP. Due to CPUID emulation bug not being fixed in VMs until
  October 2024, this feature is being disabled in the interim.

  [Fix]

  * Clean cherry-pick SAUCE patch from MSFT tree, https://github.com/dcui/linux
  * cdf5cdd: "x86/hyperv: temporarily disable CET SS on SEV-SNP due to a 
paravisor bug"

  [Test Plan]

  * Compile tested
  * Boot tested
  * Microsoft tested

  [Regression potential]

  * Changes isolated, minimal regression risk

  [Other info]

  * SF #00387447

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2069204/+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 2066992] Re: Azure: net: mana: Fix Rx DMA datasize and skb_over_panic

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  Azure: net: mana: Fix Rx DMA datasize and skb_over_panic

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Mantic:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Request to remove multiple of 64 alignment on mana Rx DMA datasize

  [Fix]

  * Clean cherry-pick, commit c0de6ab920aafb56feab56058e46b688e694a246
  net: mana: Fix Rx DMA datasize and skb_over_panic

  [Test Plan]

  * Compile tested
  * Boot tested
  * Microsoft to test

  [Regression potential]

  * Changes isolated
  * Could cause more dropped packets when truncated

  [Other Info]

  * SF: #00385930

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2066992/+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 2070402] Re: net: mana: Add support for page sizes other than 4KB on ARM64

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  net: mana: Add support for page sizes other than 4KB on ARM64

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Request from MSFT to add MANA support for page sizes other than 4KB

  [Fix]

  * Clean cherry pick from linux-next, 382d1741b5b2: "net: mana: Add support 
for page sizes other than 4KB on ARM64"
  * Uses MANA_PAGE_SIZE, which defaults to 4KB, rather than PAGE_SIZE which is 
tied to platform page size

  [Test Plan]

  * Compile tested
  * Boot tested
  * Module loaded

  [Regression potential]

  * Changes isolated, minimal regression risk
  * Functionally equivalent, simply changing the origin of defines

  [Other info]

  * SF #00388152

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2070402/+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 2076291] Re: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.11.0-1003.3

---
linux-azure (6.11.0-1003.3) oracular; urgency=medium

  * oracular/linux-azure: 6.11.0-1003.3 -proposed tracker (LP: #2080360)

  * Miscellaneous Ubuntu changes
- [Packaging] tools/hv: don't build/install hv_fcopy_uio_daemon on arm64

 -- Paolo Pisati   Wed, 11 Sep 2024 13:49:32
+0200

** Changed in: linux-azure (Ubuntu Oracular)
   Status: Fix Committed => Fix Released

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

Title:
  kernel panic was caused by a fatal exception due to a null pointer
  dereference in the iptable_nat module

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  * Microsoft has requested a patch to address a kernel panic issue
  similar to the upstream issue here -
  
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/

  [Fix]

  * Clean cherry-pick upstream commit 5830aa863981: "netfilter:
  iptables: Fix null-ptr-deref in iptable_nat_table_init()"

  [Test Plan]

  * Build and boot tested

  [Where problems could occur]

  * Low regression risk, mostly shifting logic
  * Change to order of register_pernet_subsys() and xt_register_template() 
could expose some other logic being held together under race condition

  [Other info]

  * SF #00391736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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 2077571] Re: GVE stuck TX queues

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-gcp - 6.11.0-1001.1

---
linux-gcp (6.11.0-1001.1) oracular; urgency=medium

  * oracular/linux-gcp: 6.11.0-1001.1 -proposed tracker (LP: #2079971)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- [Packaging] debian.gcp/dkms-versions -- update from kernel-versions
  (main/d2024.08.12)

  * Miscellaneous Ubuntu changes
- [packaging] move to 6.11 and oracular
- [Config] updateconfigs following Ubuntu-6.11.0-7.7 rebase
- [packaging] sync Build-Depends and Build-Depends-Indep wrt debian.master

  [ Ubuntu: 6.11.0-7.7 ]

  * oracular/linux: 6.11.0-7.7 -proposed tracker (LP: #2079949)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [1/99]: LSM: Infrastructure management of the sock
  security
- SAUCE: apparmor4.0.0 [2/99]: LSM: Add the lsmblob data structure.
- SAUCE: apparmor4.0.0 [3/99]: LSM: Use lsmblob in security_audit_rule_match
- SAUCE: apparmor4.0.0 [4/99]: LSM: Call only one hook for audit rules
- SAUCE: apparmor4.0.0 [5/99]: LSM: Add lsmblob_to_secctx hook
- SAUCE: apparmor4.0.0 [6/99]: Audit: maintain an lsmblob in audit_context
- SAUCE: apparmor4.0.0 [7/99]: LSM: Use lsmblob in security_ipc_getsecid
- SAUCE: apparmor4.0.0 [8/99]: Audit: Update shutdown LSM data
- SAUCE: apparmor4.0.0 [9/99]: LSM: Use lsmblob in security_current_getsecid
- SAUCE: apparmor4.0.0 [10/99]: LSM: Use lsmblob in security_inode_getsecid
- SAUCE: apparmor4.0.0 [11/99]: Audit: use an lsmblob in audit_names
- SAUCE: apparmor4.0.0 [12/99]: LSM: Create new security_cred_getlsmblob LSM
  hook
- SAUCE: apparmor4.0.0 [13/99]: Audit: Change context data from secid to
  lsmblob
- SAUCE: apparmor4.0.0 [14/99]: Netlabel: Use lsmblob for audit data
- SAUCE: apparmor4.0.0 [15/99]: LSM: Ensure the correct LSM context releaser
- SAUCE: apparmor4.0.0 [16/99]: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [17/99]: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [18/99]: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [19/99]: LSM: lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [20/99]: LSM: security_lsmblob_to_secctx module
  selection
- SAUCE: apparmor4.0.0 [21/99]: Audit: Create audit_stamp structure
- SAUCE: apparmor4.0.0 [22/99]: Audit: Allow multiple records in an
  audit_buffer
- SAUCE: apparmor4.0.0 [23/99]: Audit: Add record for multiple task security
  contexts
- SAUCE: apparmor4.0.0 [24/99]: audit: multiple subject lsm values for
  netlabel
- SAUCE: apparmor4.0.0 [25/99]: Audit: Add record for multiple object 
contexts
- SAUCE: apparmor4.0.0 [26/99]: LSM: Remove unused lsmcontext_init()
- SAUCE: apparmor4.0.0 [27/99]: LSM: Improve logic in security_getprocattr
- SAUCE: apparmor4.0.0 [28/99]: LSM: secctx provider check on release
- SAUCE: apparmor4.0.0 [29/99]: LSM: Single calls in socket_getpeersec hooks
- SAUCE: apparmor4.0.0 [30/99]: LSM: Exclusive secmark usage
- SAUCE: apparmor4.0.0 [31/99]: LSM: Identify which LSM handles the context
  string
- SAUCE: apparmor4.0.0 [32/99]: AppArmor: Remove the exclusive flag
- SAUCE: apparmor4.0.0 [33/99]: LSM: Add mount opts blob size tracking
- SAUCE: apparmor4.0.0 [34/99]: LSM: allocate mnt_opts blobs instead of 
module
  specific data
- SAUCE: apparmor4.0.0 [35/99]: LSM: Infrastructure management of the key
  security blob
- SAUCE: apparmor4.0.0 [36/99]: LSM: Infrastructure management of the 
mnt_opts
  security blob
- SAUCE: apparmor4.0.0 [37/99]: LSM: Remove lsmblob scaffolding
- SAUCE: apparmor4.0.0 [38/99]: LSM: Allow reservation of netlabel
- SAUCE: apparmor4.0.0 [39/99]: LSM: restrict security_cred_getsecid() to a
  single LSM
- SAUCE: apparmor4.0.0 [40/99]: Smack: Remove LSM_FLAG_EXCLUSIVE
- SAUCE: apparmor4.0.0 [41/99]: LSM stacking v39: UBUNTU: SAUCE: 
apparmor4.0.0
  [41/99]: add/use fns to print hash string hex value
- SAUCE: apparmor4.0.0 [42/99]: patch to provide compatibility with v2.x net
  rules
- SAUCE: apparmor4.0.0 [43/99]: add unpriviled user ns mediation
- SAUCE: apparmor4.0.0 [44/99]: Add sysctls for additional controls of 
unpriv
  userns restrictions
- SAUCE: apparmor4.0.0 [45/99]: af_unix mediation
- SAUCE: apparmor4.0.0 [46/99]: Add fine grained mediation of posix mqueues
- SAUCE: apparmor4.0.0 [47/99] fixup inode_set_attr
- SAUCE: apparmor4.0.0 [48/99]: setup slab cache for audit data
- SAUCE: apparmor4.0.0 [49/99]: Improve debug print infrastructure
- SAUCE: apparmor4.0.0 [50/99]: add the ability for profiles to have a
  learning cache
- SAUCE: apparmor4.0.0 [51/99]: enable userspace upcall for mediation
- SAUCE: apparmor4.0.0 [52/99]: prompt - loc

[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.11.0-7.7

---
linux (6.11.0-7.7) oracular; urgency=medium

  * oracular/linux: 6.11.0-7.7 -proposed tracker (LP: #2079949)

  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [1/99]: LSM: Infrastructure management of the sock
  security
- SAUCE: apparmor4.0.0 [2/99]: LSM: Add the lsmblob data structure.
- SAUCE: apparmor4.0.0 [3/99]: LSM: Use lsmblob in security_audit_rule_match
- SAUCE: apparmor4.0.0 [4/99]: LSM: Call only one hook for audit rules
- SAUCE: apparmor4.0.0 [5/99]: LSM: Add lsmblob_to_secctx hook
- SAUCE: apparmor4.0.0 [6/99]: Audit: maintain an lsmblob in audit_context
- SAUCE: apparmor4.0.0 [7/99]: LSM: Use lsmblob in security_ipc_getsecid
- SAUCE: apparmor4.0.0 [8/99]: Audit: Update shutdown LSM data
- SAUCE: apparmor4.0.0 [9/99]: LSM: Use lsmblob in security_current_getsecid
- SAUCE: apparmor4.0.0 [10/99]: LSM: Use lsmblob in security_inode_getsecid
- SAUCE: apparmor4.0.0 [11/99]: Audit: use an lsmblob in audit_names
- SAUCE: apparmor4.0.0 [12/99]: LSM: Create new security_cred_getlsmblob LSM
  hook
- SAUCE: apparmor4.0.0 [13/99]: Audit: Change context data from secid to
  lsmblob
- SAUCE: apparmor4.0.0 [14/99]: Netlabel: Use lsmblob for audit data
- SAUCE: apparmor4.0.0 [15/99]: LSM: Ensure the correct LSM context releaser
- SAUCE: apparmor4.0.0 [16/99]: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [17/99]: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [18/99]: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [19/99]: LSM: lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [20/99]: LSM: security_lsmblob_to_secctx module
  selection
- SAUCE: apparmor4.0.0 [21/99]: Audit: Create audit_stamp structure
- SAUCE: apparmor4.0.0 [22/99]: Audit: Allow multiple records in an
  audit_buffer
- SAUCE: apparmor4.0.0 [23/99]: Audit: Add record for multiple task security
  contexts
- SAUCE: apparmor4.0.0 [24/99]: audit: multiple subject lsm values for
  netlabel
- SAUCE: apparmor4.0.0 [25/99]: Audit: Add record for multiple object 
contexts
- SAUCE: apparmor4.0.0 [26/99]: LSM: Remove unused lsmcontext_init()
- SAUCE: apparmor4.0.0 [27/99]: LSM: Improve logic in security_getprocattr
- SAUCE: apparmor4.0.0 [28/99]: LSM: secctx provider check on release
- SAUCE: apparmor4.0.0 [29/99]: LSM: Single calls in socket_getpeersec hooks
- SAUCE: apparmor4.0.0 [30/99]: LSM: Exclusive secmark usage
- SAUCE: apparmor4.0.0 [31/99]: LSM: Identify which LSM handles the context
  string
- SAUCE: apparmor4.0.0 [32/99]: AppArmor: Remove the exclusive flag
- SAUCE: apparmor4.0.0 [33/99]: LSM: Add mount opts blob size tracking
- SAUCE: apparmor4.0.0 [34/99]: LSM: allocate mnt_opts blobs instead of 
module
  specific data
- SAUCE: apparmor4.0.0 [35/99]: LSM: Infrastructure management of the key
  security blob
- SAUCE: apparmor4.0.0 [36/99]: LSM: Infrastructure management of the 
mnt_opts
  security blob
- SAUCE: apparmor4.0.0 [37/99]: LSM: Remove lsmblob scaffolding
- SAUCE: apparmor4.0.0 [38/99]: LSM: Allow reservation of netlabel
- SAUCE: apparmor4.0.0 [39/99]: LSM: restrict security_cred_getsecid() to a
  single LSM
- SAUCE: apparmor4.0.0 [40/99]: Smack: Remove LSM_FLAG_EXCLUSIVE
- SAUCE: apparmor4.0.0 [41/99]: LSM stacking v39: UBUNTU: SAUCE: 
apparmor4.0.0
  [41/99]: add/use fns to print hash string hex value
- SAUCE: apparmor4.0.0 [42/99]: patch to provide compatibility with v2.x net
  rules
- SAUCE: apparmor4.0.0 [43/99]: add unpriviled user ns mediation
- SAUCE: apparmor4.0.0 [44/99]: Add sysctls for additional controls of 
unpriv
  userns restrictions
- SAUCE: apparmor4.0.0 [45/99]: af_unix mediation
- SAUCE: apparmor4.0.0 [46/99]: Add fine grained mediation of posix mqueues
- SAUCE: apparmor4.0.0 [47/99] fixup inode_set_attr
- SAUCE: apparmor4.0.0 [48/99]: setup slab cache for audit data
- SAUCE: apparmor4.0.0 [49/99]: Improve debug print infrastructure
- SAUCE: apparmor4.0.0 [50/99]: add the ability for profiles to have a
  learning cache
- SAUCE: apparmor4.0.0 [51/99]: enable userspace upcall for mediation
- SAUCE: apparmor4.0.0 [52/99]: prompt - lock down prompt interface
- SAUCE: apparmor4.0.0 [53/99]: prompt - allow controlling of caching of a
  prompt response
- SAUCE: apparmor4.0.0 [54/99]: prompt - add refcount to audit_node in prep 
or
  reuse and delete
- SAUCE: apparmor4.0.0 [55/99]: prompt - refactor to moving caching to
  uresponse
- SAUCE: apparmor4.0.0 [56/99]: prompt - Improve debug statements
- SAUCE: apparmor4.0.0 [57/99]: prompt - fix caching
- SAUCE: apparmor4.0.0 [58/99]: prompt - rework bui

[Kernel-packages] [Bug 2067597] Re: New upstream release 535.183.01

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-535 -
535.183.01-0ubuntu2

---
nvidia-graphics-drivers-535 (535.183.01-0ubuntu2) oracular; urgency=medium

  [ Paolo Pisati ]
  * Fix gcc-14 FTBFS (LP: #2075340)

 -- Eduard de Vidal Flores   Thu,
01 Aug 2024 15:23:10 +0200

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Oracular)
   Status: In Progress => Fix Released

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

Title:
  New upstream release 535.183.01

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Oracular:
  Fix Released

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

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

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

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

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

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

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2067597/+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 2070042] Re: noble:linux: ADT ubuntu-regression-suite misses fakeroot dependency

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.11.0-7.7

---
linux (6.11.0-7.7) oracular; urgency=medium

  * oracular/linux: 6.11.0-7.7 -proposed tracker (LP: #2079949)

  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [1/99]: LSM: Infrastructure management of the sock
  security
- SAUCE: apparmor4.0.0 [2/99]: LSM: Add the lsmblob data structure.
- SAUCE: apparmor4.0.0 [3/99]: LSM: Use lsmblob in security_audit_rule_match
- SAUCE: apparmor4.0.0 [4/99]: LSM: Call only one hook for audit rules
- SAUCE: apparmor4.0.0 [5/99]: LSM: Add lsmblob_to_secctx hook
- SAUCE: apparmor4.0.0 [6/99]: Audit: maintain an lsmblob in audit_context
- SAUCE: apparmor4.0.0 [7/99]: LSM: Use lsmblob in security_ipc_getsecid
- SAUCE: apparmor4.0.0 [8/99]: Audit: Update shutdown LSM data
- SAUCE: apparmor4.0.0 [9/99]: LSM: Use lsmblob in security_current_getsecid
- SAUCE: apparmor4.0.0 [10/99]: LSM: Use lsmblob in security_inode_getsecid
- SAUCE: apparmor4.0.0 [11/99]: Audit: use an lsmblob in audit_names
- SAUCE: apparmor4.0.0 [12/99]: LSM: Create new security_cred_getlsmblob LSM
  hook
- SAUCE: apparmor4.0.0 [13/99]: Audit: Change context data from secid to
  lsmblob
- SAUCE: apparmor4.0.0 [14/99]: Netlabel: Use lsmblob for audit data
- SAUCE: apparmor4.0.0 [15/99]: LSM: Ensure the correct LSM context releaser
- SAUCE: apparmor4.0.0 [16/99]: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [17/99]: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [18/99]: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [19/99]: LSM: lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [20/99]: LSM: security_lsmblob_to_secctx module
  selection
- SAUCE: apparmor4.0.0 [21/99]: Audit: Create audit_stamp structure
- SAUCE: apparmor4.0.0 [22/99]: Audit: Allow multiple records in an
  audit_buffer
- SAUCE: apparmor4.0.0 [23/99]: Audit: Add record for multiple task security
  contexts
- SAUCE: apparmor4.0.0 [24/99]: audit: multiple subject lsm values for
  netlabel
- SAUCE: apparmor4.0.0 [25/99]: Audit: Add record for multiple object 
contexts
- SAUCE: apparmor4.0.0 [26/99]: LSM: Remove unused lsmcontext_init()
- SAUCE: apparmor4.0.0 [27/99]: LSM: Improve logic in security_getprocattr
- SAUCE: apparmor4.0.0 [28/99]: LSM: secctx provider check on release
- SAUCE: apparmor4.0.0 [29/99]: LSM: Single calls in socket_getpeersec hooks
- SAUCE: apparmor4.0.0 [30/99]: LSM: Exclusive secmark usage
- SAUCE: apparmor4.0.0 [31/99]: LSM: Identify which LSM handles the context
  string
- SAUCE: apparmor4.0.0 [32/99]: AppArmor: Remove the exclusive flag
- SAUCE: apparmor4.0.0 [33/99]: LSM: Add mount opts blob size tracking
- SAUCE: apparmor4.0.0 [34/99]: LSM: allocate mnt_opts blobs instead of 
module
  specific data
- SAUCE: apparmor4.0.0 [35/99]: LSM: Infrastructure management of the key
  security blob
- SAUCE: apparmor4.0.0 [36/99]: LSM: Infrastructure management of the 
mnt_opts
  security blob
- SAUCE: apparmor4.0.0 [37/99]: LSM: Remove lsmblob scaffolding
- SAUCE: apparmor4.0.0 [38/99]: LSM: Allow reservation of netlabel
- SAUCE: apparmor4.0.0 [39/99]: LSM: restrict security_cred_getsecid() to a
  single LSM
- SAUCE: apparmor4.0.0 [40/99]: Smack: Remove LSM_FLAG_EXCLUSIVE
- SAUCE: apparmor4.0.0 [41/99]: LSM stacking v39: UBUNTU: SAUCE: 
apparmor4.0.0
  [41/99]: add/use fns to print hash string hex value
- SAUCE: apparmor4.0.0 [42/99]: patch to provide compatibility with v2.x net
  rules
- SAUCE: apparmor4.0.0 [43/99]: add unpriviled user ns mediation
- SAUCE: apparmor4.0.0 [44/99]: Add sysctls for additional controls of 
unpriv
  userns restrictions
- SAUCE: apparmor4.0.0 [45/99]: af_unix mediation
- SAUCE: apparmor4.0.0 [46/99]: Add fine grained mediation of posix mqueues
- SAUCE: apparmor4.0.0 [47/99] fixup inode_set_attr
- SAUCE: apparmor4.0.0 [48/99]: setup slab cache for audit data
- SAUCE: apparmor4.0.0 [49/99]: Improve debug print infrastructure
- SAUCE: apparmor4.0.0 [50/99]: add the ability for profiles to have a
  learning cache
- SAUCE: apparmor4.0.0 [51/99]: enable userspace upcall for mediation
- SAUCE: apparmor4.0.0 [52/99]: prompt - lock down prompt interface
- SAUCE: apparmor4.0.0 [53/99]: prompt - allow controlling of caching of a
  prompt response
- SAUCE: apparmor4.0.0 [54/99]: prompt - add refcount to audit_node in prep 
or
  reuse and delete
- SAUCE: apparmor4.0.0 [55/99]: prompt - refactor to moving caching to
  uresponse
- SAUCE: apparmor4.0.0 [56/99]: prompt - Improve debug statements
- SAUCE: apparmor4.0.0 [57/99]: prompt - fix caching
- SAUCE: apparmor4.0.0 [58/99]: prompt - rework bui

[Kernel-packages] [Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.11.0-7.7

---
linux (6.11.0-7.7) oracular; urgency=medium

  * oracular/linux: 6.11.0-7.7 -proposed tracker (LP: #2079949)

  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [1/99]: LSM: Infrastructure management of the sock
  security
- SAUCE: apparmor4.0.0 [2/99]: LSM: Add the lsmblob data structure.
- SAUCE: apparmor4.0.0 [3/99]: LSM: Use lsmblob in security_audit_rule_match
- SAUCE: apparmor4.0.0 [4/99]: LSM: Call only one hook for audit rules
- SAUCE: apparmor4.0.0 [5/99]: LSM: Add lsmblob_to_secctx hook
- SAUCE: apparmor4.0.0 [6/99]: Audit: maintain an lsmblob in audit_context
- SAUCE: apparmor4.0.0 [7/99]: LSM: Use lsmblob in security_ipc_getsecid
- SAUCE: apparmor4.0.0 [8/99]: Audit: Update shutdown LSM data
- SAUCE: apparmor4.0.0 [9/99]: LSM: Use lsmblob in security_current_getsecid
- SAUCE: apparmor4.0.0 [10/99]: LSM: Use lsmblob in security_inode_getsecid
- SAUCE: apparmor4.0.0 [11/99]: Audit: use an lsmblob in audit_names
- SAUCE: apparmor4.0.0 [12/99]: LSM: Create new security_cred_getlsmblob LSM
  hook
- SAUCE: apparmor4.0.0 [13/99]: Audit: Change context data from secid to
  lsmblob
- SAUCE: apparmor4.0.0 [14/99]: Netlabel: Use lsmblob for audit data
- SAUCE: apparmor4.0.0 [15/99]: LSM: Ensure the correct LSM context releaser
- SAUCE: apparmor4.0.0 [16/99]: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [17/99]: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [18/99]: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [19/99]: LSM: lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [20/99]: LSM: security_lsmblob_to_secctx module
  selection
- SAUCE: apparmor4.0.0 [21/99]: Audit: Create audit_stamp structure
- SAUCE: apparmor4.0.0 [22/99]: Audit: Allow multiple records in an
  audit_buffer
- SAUCE: apparmor4.0.0 [23/99]: Audit: Add record for multiple task security
  contexts
- SAUCE: apparmor4.0.0 [24/99]: audit: multiple subject lsm values for
  netlabel
- SAUCE: apparmor4.0.0 [25/99]: Audit: Add record for multiple object 
contexts
- SAUCE: apparmor4.0.0 [26/99]: LSM: Remove unused lsmcontext_init()
- SAUCE: apparmor4.0.0 [27/99]: LSM: Improve logic in security_getprocattr
- SAUCE: apparmor4.0.0 [28/99]: LSM: secctx provider check on release
- SAUCE: apparmor4.0.0 [29/99]: LSM: Single calls in socket_getpeersec hooks
- SAUCE: apparmor4.0.0 [30/99]: LSM: Exclusive secmark usage
- SAUCE: apparmor4.0.0 [31/99]: LSM: Identify which LSM handles the context
  string
- SAUCE: apparmor4.0.0 [32/99]: AppArmor: Remove the exclusive flag
- SAUCE: apparmor4.0.0 [33/99]: LSM: Add mount opts blob size tracking
- SAUCE: apparmor4.0.0 [34/99]: LSM: allocate mnt_opts blobs instead of 
module
  specific data
- SAUCE: apparmor4.0.0 [35/99]: LSM: Infrastructure management of the key
  security blob
- SAUCE: apparmor4.0.0 [36/99]: LSM: Infrastructure management of the 
mnt_opts
  security blob
- SAUCE: apparmor4.0.0 [37/99]: LSM: Remove lsmblob scaffolding
- SAUCE: apparmor4.0.0 [38/99]: LSM: Allow reservation of netlabel
- SAUCE: apparmor4.0.0 [39/99]: LSM: restrict security_cred_getsecid() to a
  single LSM
- SAUCE: apparmor4.0.0 [40/99]: Smack: Remove LSM_FLAG_EXCLUSIVE
- SAUCE: apparmor4.0.0 [41/99]: LSM stacking v39: UBUNTU: SAUCE: 
apparmor4.0.0
  [41/99]: add/use fns to print hash string hex value
- SAUCE: apparmor4.0.0 [42/99]: patch to provide compatibility with v2.x net
  rules
- SAUCE: apparmor4.0.0 [43/99]: add unpriviled user ns mediation
- SAUCE: apparmor4.0.0 [44/99]: Add sysctls for additional controls of 
unpriv
  userns restrictions
- SAUCE: apparmor4.0.0 [45/99]: af_unix mediation
- SAUCE: apparmor4.0.0 [46/99]: Add fine grained mediation of posix mqueues
- SAUCE: apparmor4.0.0 [47/99] fixup inode_set_attr
- SAUCE: apparmor4.0.0 [48/99]: setup slab cache for audit data
- SAUCE: apparmor4.0.0 [49/99]: Improve debug print infrastructure
- SAUCE: apparmor4.0.0 [50/99]: add the ability for profiles to have a
  learning cache
- SAUCE: apparmor4.0.0 [51/99]: enable userspace upcall for mediation
- SAUCE: apparmor4.0.0 [52/99]: prompt - lock down prompt interface
- SAUCE: apparmor4.0.0 [53/99]: prompt - allow controlling of caching of a
  prompt response
- SAUCE: apparmor4.0.0 [54/99]: prompt - add refcount to audit_node in prep 
or
  reuse and delete
- SAUCE: apparmor4.0.0 [55/99]: prompt - refactor to moving caching to
  uresponse
- SAUCE: apparmor4.0.0 [56/99]: prompt - Improve debug statements
- SAUCE: apparmor4.0.0 [57/99]: prompt - fix caching
- SAUCE: apparmor4.0.0 [58/99]: prompt - rework bui

[Kernel-packages] [Bug 2067881] Re: New upstream release 550.90.07

2024-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-550 -
550.107.02-0ubuntu1

---
nvidia-graphics-drivers-550 (550.107.02-0ubuntu1) oracular; urgency=medium

  * New upstream release (LP: #2075327)

 -- Eduard de Vidal Flores   Mon,
05 Aug 2024 10:49:10 +0200

** Changed in: nvidia-graphics-drivers-550 (Ubuntu Oracular)
   Status: In Progress => Fix Released

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

Title:
  New upstream release 550.90.07

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Oracular:
  Fix Released

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

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

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

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

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

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

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2067881/+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


  1   2   3   4   5   6   7   8   9   10   >