** Description changed:
[Impact]
On Dell platforms using either Linux 6.11.0-1021-oem or 6.14.0-1005-oem, we observed call traces when unplugging a HDMI/DP/VGA cable from an external monitor.
[Fix]
============= Noble OEM 6.14 ================================================
Apply the following patch from the mailing list amd-gfx@lists.freedesktop.org fixes the issue:
- [PATCH 06/18] drm/amd/display: limit clear_update_flags to dcn32 and
above
While the patch is still under review, an SRU is required out of
urgency.
Link: https://lore.kernel.org/amd-
gfx/20250710212941.630259-7-IVAN.LIPSKI@amd.com/
============== Plucky and Questing ==========================================
- Cherry-pick the following patch from the mainline:
+ 1. Cherry-pick the following patch from the mainline:
f354556e29f4 drm/amd/display: limit clear_update_flags to dcn32 and
above
Here is the reference for the full patchset:
Link: https://lore.kernel.org/amd-
gfx/20250710212941.630259-7-IVAN.LIPSKI@amd.com/
+ 2. Cherry-pick the other patch, which fixes the patch above:
+
+ 2d418e4fd9f1 drm/amd/display: Allow DCN301 to clear update flags
+
+
[Test Plan]
1. Boot into an Ubuntu OS
2. Connect a HDMI/DP/VGA cable into an external monitor
3. Check whether a call trace appears
[Where problems could occur]
This patch changes the behavior of AMD GPUs with DCN version lower than 3.2. It might cause regression on these GPUs.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116908
Title:
[AMDGPU] Call trace occurs when unplugging a HDMI/DP/VGA cable on Dell
platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in The Noble Numbat:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in The Plucky Puffin:
New
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in The Questing Quokka:
New
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
On Dell platforms using either Linux 6.11.0-1021-oem or 6.14.0-1005-oem, we observed call traces when unplugging a HDMI/DP/VGA cable from an external monitor.
[Fix]
============= Noble OEM 6.14 ================================================
Apply the following patch from the mailing list amd-gfx@lists.freedesktop.org fixes the issue:
- [PATCH 06/18] drm/amd/display: limit clear_update_flags to dcn32 and
above
While the patch is still under review, an SRU is required out of
urgency.
Link: https://lore.kernel.org/amd-
gfx/20250710212941.630259-7-IVAN.LIPSKI@amd.com/
============== Plucky and Questing ==========================================
1. Cherry-pick the following patch from the mainline:
f354556e29f4 drm/amd/display: limit clear_update_flags to dcn32 and
above
Here is the reference for the full patchset:
Link: https://lore.kernel.org/amd-
gfx/20250710212941.630259-7-IVAN.LIPSKI@amd.com/
2. Cherry-pick the other patch, which fixes the patch above:
2d418e4fd9f1 drm/amd/display: Allow DCN301 to clear update flags
[Test Plan]
1. Boot into an Ubuntu OS
2. Connect a HDMI/DP/VGA cable into an external monitor
3. Check whether a call trace appears
[Where problems could occur]
This patch changes the behavior of AMD GPUs with DCN version lower than 3.2. It might cause regression on these GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116908/+subscriptions
воскресенье
[Bug 2118407] Re: watchdog: BUG: soft lockup - CPU#6 stuck for 5718s! [wdavdaemon:1134] with 5.15.0-144-generic
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2118407
Title:
watchdog: BUG: soft lockup - CPU#6 stuck for 5718s! [wdavdaemon:1134]
with 5.15.0-144-generic
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Bug description:
linux-image-5.15.0-144-generic
Ubuntu 22.04
Microsoft Defender for Endpoint Linux (mdatp, wdavdaemon)
Docker
After latest kernel patch I see constant freezes on servers with mdatp
and docker running in our environment. Only happens on docker hosts
running 5.15.0-144. We have non-docker hosts running on this kernel
with mdatp without issue.
Jul 24 14:03:21 coa2a-docker kernel: [34356.813909] watchdog: BUG: soft lockup - CPU#6 stuck for 5808s! [wdavdaemon:1134]
Jul 24 14:03:21 coa2a-docker kernel: [34356.814897] Modules linked in: unix_diag(+) tls(+) nf_conntrack_netlink xt_nat xt_tcpudp v
eth xt_conntrack xt_MASQUERADE bridge stp llc xt_set ip_set nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag
_ipv4 xt_addrtype nft_compat nf_tables nfnetlink xfrm_user xfrm_algo cmac cifs cifs_arc4 cifs_md4 fscache netfs overlay binfmt_mis
c nls_iso8859_1 joydev input_leds serio_raw kvm_amd ccp kvm dm_multipath drm scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_codel ef
i_pstore msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash
_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd virtio_net psmouse net_failover virtio_blk virtio_rng failov
er floppy
Jul 24 14:03:21 coa2a-docker kernel: [34356.814950] CPU: 6 PID: 1134 Comm: wdavdaemon Tainted: G L 5.15.0-144-gener
ic #157-Ubuntu
Jul 24 14:03:21 coa2a-docker kernel: [34356.814953] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1 04/01
/2014
Jul 24 14:03:21 coa2a-docker kernel: [34356.814954] RIP: 0010:do_task_stat+0xbff/0xdf0
Jul 24 14:03:21 coa2a-docker kernel: [34356.814961] Code: ff 31 d2 e9 7b fa ff ff 8b 75 98 4c 8b a3 10 02 00 00 4c 8b bb 18 02 00
00 4c 8b ab c8 01 00 00 48 89 d0 4c 03 a0 00 0b 00 00 <4c> 03 b8 08 0b 00 00 4c 03 a8 c0 0a 00 00 48 8b 80 70 0a 00 00 48
Jul 24 14:03:21 coa2a-docker kernel: [34356.814963] RSP: 0018:ffffaf5101317c18 EFLAGS: 00000212
Jul 24 14:03:21 coa2a-docker kernel: [34356.814964] RAX: ffff973b08314c80 RBX: ffff973ceaf03600 RCX: 0000000000000000
Jul 24 14:03:21 coa2a-docker kernel: [34356.814965] RDX: ffff973b0e1d4c80 RSI: 0000000000000000 RDI: 0000000000000001
Jul 24 14:03:21 coa2a-docker kernel: [34356.814966] RBP: ffffaf5101317d28 R08: ffff973b06e29c30 R09: 0000000000000001
Jul 24 14:03:21 coa2a-docker ker
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2118407/+subscriptions
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2118407
Title:
watchdog: BUG: soft lockup - CPU#6 stuck for 5718s! [wdavdaemon:1134]
with 5.15.0-144-generic
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Bug description:
linux-image-5.15.0-144-generic
Ubuntu 22.04
Microsoft Defender for Endpoint Linux (mdatp, wdavdaemon)
Docker
After latest kernel patch I see constant freezes on servers with mdatp
and docker running in our environment. Only happens on docker hosts
running 5.15.0-144. We have non-docker hosts running on this kernel
with mdatp without issue.
Jul 24 14:03:21 coa2a-docker kernel: [34356.813909] watchdog: BUG: soft lockup - CPU#6 stuck for 5808s! [wdavdaemon:1134]
Jul 24 14:03:21 coa2a-docker kernel: [34356.814897] Modules linked in: unix_diag(+) tls(+) nf_conntrack_netlink xt_nat xt_tcpudp v
eth xt_conntrack xt_MASQUERADE bridge stp llc xt_set ip_set nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag
_ipv4 xt_addrtype nft_compat nf_tables nfnetlink xfrm_user xfrm_algo cmac cifs cifs_arc4 cifs_md4 fscache netfs overlay binfmt_mis
c nls_iso8859_1 joydev input_leds serio_raw kvm_amd ccp kvm dm_multipath drm scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_codel ef
i_pstore msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash
_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd virtio_net psmouse net_failover virtio_blk virtio_rng failov
er floppy
Jul 24 14:03:21 coa2a-docker kernel: [34356.814950] CPU: 6 PID: 1134 Comm: wdavdaemon Tainted: G L 5.15.0-144-gener
ic #157-Ubuntu
Jul 24 14:03:21 coa2a-docker kernel: [34356.814953] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1 04/01
/2014
Jul 24 14:03:21 coa2a-docker kernel: [34356.814954] RIP: 0010:do_task_stat+0xbff/0xdf0
Jul 24 14:03:21 coa2a-docker kernel: [34356.814961] Code: ff 31 d2 e9 7b fa ff ff 8b 75 98 4c 8b a3 10 02 00 00 4c 8b bb 18 02 00
00 4c 8b ab c8 01 00 00 48 89 d0 4c 03 a0 00 0b 00 00 <4c> 03 b8 08 0b 00 00 4c 03 a8 c0 0a 00 00 48 8b 80 70 0a 00 00 48
Jul 24 14:03:21 coa2a-docker kernel: [34356.814963] RSP: 0018:ffffaf5101317c18 EFLAGS: 00000212
Jul 24 14:03:21 coa2a-docker kernel: [34356.814964] RAX: ffff973b08314c80 RBX: ffff973ceaf03600 RCX: 0000000000000000
Jul 24 14:03:21 coa2a-docker kernel: [34356.814965] RDX: ffff973b0e1d4c80 RSI: 0000000000000000 RDI: 0000000000000001
Jul 24 14:03:21 coa2a-docker kernel: [34356.814966] RBP: ffffaf5101317d28 R08: ffff973b06e29c30 R09: 0000000000000001
Jul 24 14:03:21 coa2a-docker ker
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2118407/+subscriptions
[Bug 2115447] Re: Ubuntu 24.04.2: NULL pointer dereference with Ceph and selinux
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115447
Title:
Ubuntu 24.04.2: NULL pointer dereference with Ceph and selinux
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
fs/ceph,selinux: fix NULL pointer dereference on CephFS write with
SELinux in permissive mode
A NULL pointer dereference occurs in the Ceph kernel client (CephFS)
when a file is created on a mounted CephFS volume while SELinux is
enabled in permissive mode.
[ 86.678570] BUG: kernel NULL pointer dereference, address: 000000000000001d
[ 86.679238] #PF: supervisor read access in kernel mode
[ 86.679859] #PF: error_code(0x0000) - not-present page
[ 86.680445] PGD 0 P4D 0
[ 86.681021] Oops: 0000 [#1] PREEMPT SMP PTI
[ 86.681558] CPU: 0 PID: 2818 Comm: touch Not tainted 6.8.0-62-generic #65-Ubuntu
[ 86.682095] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[ 86.682716] RIP: 0010:memcpy_orig+0x54/0x130
[ 86.683267] Code: 89 07 4c 89 4f 08 4c 89 57 10 4c 89 5f 18 48 8d 7f 20 73 d4 83 c2 20 eb 44 48 01 d6 48 01 d7 48 83 ea 20 0f 1f 00 48 83 ea 20 <4c> 8b 46 f8 4c 8b 4e f0 4c 8b 56 e8 4c 8b 5e e0 48 8d 76 e0 4c 89
[ 86.684464] RSP: 0018:ffffa79300b2f7e0 EFLAGS: 00010283
[ 86.685060] RAX: ffff9aeb6123a008 RBX: 0000000000000ff8 RCX: 0000000000000000
[ 86.685659] RDX: ffffffffffffffe5 RSI: 0000000000000025 RDI: ffff9aeb6123a02d
[ 86.686265] RBP: ffffa79300b2f810 R08: 0000000000000025 R09: 0000000000000000
[ 86.686843] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000025
[ 86.687366] R13: 0000000000000000 R14: ffff9aeb408d5960 R15: ffffa79300b2f8e4
[ 86.687888] FS: 0000724d07b47740(0000) GS:ffff9aec77c00000(0000) knlGS:0000000000000000
[ 86.688416] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 86.688947] CR2: 000000000000001d CR3: 000000012038a004 CR4: 00000000001706f0
[ 86.689541] Call Trace:
[ 86.690124] <TASK>
[ 86.690704] ? show_regs+0x6d/0x80
[ 86.691256] ? __die+0x24/0x80
[ 86.691807] ? page_fault_oops+0x99/0x1b0
[ 86.692426] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[ 86.692991] ? __bad_area_nosemaphore+0x19e/0x2c0
[ 86.693563] ? find_vma+0x34/0x60
[ 86.694214] ? bad_area_nosemaphore+0x16/0x30
[ 86.694835] ? do_user_addr_fault+0x29d/0x670
[ 86.695439] ? exc_page_fault+0x83/0x1b0
[ 86.696024] ? asm_exc_page_fault+0x27/0x30
[ 86.696614] ? memcpy_orig+0x54/0x130
[ 86.697202] ? ceph_pagelist_append+0x124/0x150 [libceph]
[ 86.697995] ceph_security_init_secctx+0xce/0x1f0 [ceph]
[ 86.698733] ceph_new_inode+0x80/0xe0 [ceph]
[ 86.699484] ceph_atomic_open+0x3b2/0x9d0 [ceph]
[ 86.700239] ? may_create+0x141/0x150
[ 86.700903] lookup_open.isra.0+0x3a9/0x570
[ 86.701534] open_last_lookups+0x14f/0x400
[ 86.702196] path_openat+0x99/0x2d0
[ 86.702815] do_filp_open+0xaf/0x170
[ 86.703475] do_sys_openat2+0xb3/0xe0
[ 86.704098] __x64_sys_openat+0x55/0xa0
[ 86.704804] x64_sys_call+0x1eb1/0x25a0
[ 86.705437] do_syscall_64+0x7f/0x180
[ 86.706120] ? filemap_map_pages+0x2fe/0x4c0
[ 86.706792] ? __lruvec_stat_mod_folio+0x70/0xc0
[ 86.707444] ? do_read_fault+0x112/0x200
[ 86.708157] ? do_fault+0xf0/0x260
[ 86.708850] ? handle_pte_fault+0x114/0x1d0
[ 86.709519] ? __handle_mm_fault+0x654/0x800
[ 86.710216] ? __count_memcg_events+0x6b/0x120
[ 86.710884] ? count_memcg_events.constprop.0+0x2a/0x50
[ 86.711505] ? handle_mm_fault+0xad/0x380
[ 86.712136] ? do_user_addr_fault+0x334/0x670
[ 86.712778] ? irqentry_exit_to_user_mode+0x7b/0x260
[ 86.713433] ? irqentry_exit+0x43/0x50
[ 86.714111] ? clear_bhb_loop+0x15/0x70
[ 86.714777] ? clear_bhb_loop+0x15/0x70
[ 86.715330] ? clear_bhb_loop+0x15/0x70
[ 86.715844] entry_SYSCALL_64_after_hwframe+0x78/0x80
[ 86.716378] RIP: 0033:0x724d0791b175
[ 86.716895] Code: 83 e2 40 75 50 89 f0 f7 d0 a9 00 00 41 00 74 45 80 3d de fe 0e 00 00 74 60 89 da 4c 89 e6 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 7f 00 00 00 48 8b 55 b8 64 48 2b 14 25 28
[ 86.718058] RSP: 002b:00007ffd9c151d40 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[ 86.718648] RAX: ffffffffffffffda RBX: 0000000000000941 RCX: 0000724d0791b175
[ 86.719225] RDX: 0000000000000941 RSI: 00007ffd9c153635 RDI: 00000000ffffff9c
[ 86.719833] RBP: 00007ffd9c151db0 R08: 0000000000000000 R09: 0000000000000000
[ 86.720414] R10: 00000000000001b6 R11: 0000000000000202 R12: 00007ffd9c153635
[ 86.720982] R13: 0000724d07a03248 R14: 0000000000000000 R15: 0000000000000001
[ 86.721596] </TASK>
[ Fix ]
The issue must be solved modifying kernel code as follows:
- In the SELinux hook selinux_dentry_init_security(), remove a faulty cast when
assigning the context pointer is removed, allowing the LSM to populate
the context buffer correctly, avoinding the NULL pointer dereference
- In ceph_security_init_secctx(), add the missing encoding of the xattr name
and it's length to the pagelist
[ Test Plan ]
The issue can be reproduced (before) and the fix tested (after)
following the steps below:
$ sudo snap install microceph
$ sudo microceph cluster bootstrap
$ sudo microceph.ceph osd crush rule rm replicated_rule
$ sudo microceph.ceph osd crush rule create-replicated single default osd
$ sudo microceph disk add /dev/sdb --wipe
$ sudo microceph.ceph config set global osd_pool_default_size 1
$ sudo microceph.ceph osd pool create cephfs_metadata 8
$ sudo microceph.ceph osd pool create cephfs_data 8
$ sudo microceph.ceph fs new cephfs cephfs_metadata cephfs_data
$ sudo apt install selinux-basics selinux-policy-default -y && sudo selinux-activate
$ sudo reboot
$ sudo mkdir -p /mnt/cephfs
$ sudo microceph.ceph auth get-or-create client.admin mon 'allow *' mds 'allow *' osd 'allow *' mgr 'allow *'
$ sudo mount -t ceph $(hostname -I | awk '{print $1}'):6789:/ /mnt/cephfs -o name=admin,secret=
$ sudo touch /mnt/cephfs/test.txt
$ ll /mnt/cephfs/
[ Regression Potential ]
This fix modifies how SELinux provides security context data
to the CephFS client and how that data is encoded for transmission.
A regression could cause incorrect xattr encoding,
resulting in file creation failures (EPERM or EIO) or LSM labeling errors.
If the context pointer is mishandled, memory corruption or crashes may occur.
Additionally, malformed pagelist encoding could cause client-MDS
protocol mismatches.
---
Upgraded ceph cluster running ceph to 24.04.2 from Ubuntu 22. Turning
on selinux (permissive), hit a kernel null reference when mounting
cephfs and trying to touch a file:
1. Update cluster to 24.04
2. Verify ceph is working as intended (able to mount cephFS, write out
a file, unmount, etc.)
3. Installed selinux packages
4. Added following to grub on all 3 cluster members:
"audit=1 audit_backlog_limit=8192 panic=10 security=selinux selinux=1 apparmor=0"
5. Selinux policy is permissive:
root@ceph0:~# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: actual (secure)
Max kernel policy version: 33
root@ceph0:~#
6. Mounted ceph fs:
mount -t ceph admin@.cephfs=/ /var/lib/libvirt/images -o ms_mode=secure
7. attempted to write a file, did not complete and null reference reported:
[ 86.678570] BUG: kernel NULL pointer dereference, address: 000000000000001d
[ 86.679238] #PF: supervisor read access in kernel mode
[ 86.679859] #PF: error_code(0x0000) - not-present page
[ 86.680445] PGD 0 P4D 0
[ 86.681021] Oops: 0000 [#1] PREEMPT SMP PTI
[ 86.681558] CPU: 0 PID: 2818 Comm: touch Not tainted 6.8.0-62-generic #65-Ubuntu
[ 86.682095] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[ 86.682716] RIP: 0010:memcpy_orig+0x54/0x130
[ 86.683267] Code: 89 07 4c 89 4f 08 4c 89 57 10 4c 89 5f 18 48 8d 7f 20 73 d4 83 c2 20 eb 44 48 01 d6 48 01 d7 48 83 ea 20 0f 1f 00 48 83 ea 20 <4c> 8b 46 f8 4c 8b 4e f0 4c 8b 56 e8 4c 8b 5e e0 48 8d 76 e0 4c 89
[ 86.684464] RSP: 0018:ffffa79300b2f7e0 EFLAGS: 00010283
[ 86.685060] RAX: ffff9aeb6123a008 RBX: 0000000000000ff8 RCX: 0000000000000000
[ 86.685659] RDX: ffffffffffffffe5 RSI: 0000000000000025 RDI: ffff9aeb6123a02d
[ 86.686265] RBP: ffffa79300b2f810 R08: 0000000000000025 R09: 0000000000000000
[ 86.686843] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000025
[ 86.687366] R13: 0000000000000000 R14: ffff9aeb408d5960 R15: ffffa79300b2f8e4
[ 86.687888] FS: 0000724d07b47740(0000) GS:ffff9aec77c00000(0000) knlGS:0000000000000000
[ 86.688416] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 86.688947] CR2: 000000000000001d CR3: 000000012038a004 CR4: 00000000001706f0
[ 86.689541] Call Trace:
[ 86.690124] <TASK>
[ 86.690704] ? show_regs+0x6d/0x80
[ 86.691256] ? __die+0x24/0x80
[ 86.691807] ? page_fault_oops+0x99/0x1b0
[ 86.692426] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[ 86.692991] ? __bad_area_nosemaphore+0x19e/0x2c0
[ 86.693563] ? find_vma+0x34/0x60
[ 86.694214] ? bad_area_nosemaphore+0x16/0x30
[ 86.694835] ? do_user_addr_fault+0x29d/0x670
[ 86.695439] ? exc_page_fault+0x83/0x1b0
[ 86.696024] ? asm_exc_page_fault+0x27/0x30
[ 86.696614] ? memcpy_orig+0x54/0x130
[ 86.697202] ? ceph_pagelist_append+0x124/0x150 [libceph]
[ 86.697995] ceph_security_init_secctx+0xce/0x1f0 [ceph]
[ 86.698733] ceph_new_inode+0x80/0xe0 [ceph]
[ 86.699484] ceph_atomic_open+0x3b2/0x9d0 [ceph]
[ 86.700239] ? may_create+0x141/0x150
[ 86.700903] lookup_open.isra.0+0x3a9/0x570
[ 86.701534] open_last_lookups+0x14f/0x400
[ 86.702196] path_openat+0x99/0x2d0
[ 86.702815] do_filp_open+0xaf/0x170
[ 86.703475] do_sys_openat2+0xb3/0xe0
[ 86.704098] __x64_sys_openat+0x55/0xa0
[ 86.704804] x64_sys_call+0x1eb1/0x25a0
[ 86.705437] do_syscall_64+0x7f/0x180
[ 86.706120] ? filemap_map_pages+0x2fe/0x4c0
[ 86.706792] ? __lruvec_stat_mod_folio+0x70/0xc0
[ 86.707444] ? do_read_fault+0x112/0x200
[ 86.708157] ? do_fault+0xf0/0x260
[ 86.708850] ? handle_pte_fault+0x114/0x1d0
[ 86.709519] ? __handle_mm_fault+0x654/0x800
[ 86.710216] ? __count_memcg_events+0x6b/0x120
[ 86.710884] ? count_memcg_events.constprop.0+0x2a/0x50
[ 86.711505] ? handle_mm_fault+0xad/0x380
[ 86.712136] ? do_user_addr_fault+0x334/0x670
[ 86.712778] ? irqentry_exit_to_user_mode+0x7b/0x260
[ 86.713433] ? irqentry_exit+0x43/0x50
[ 86.714111] ? clear_bhb_loop+0x15/0x70
[ 86.714777] ? clear_bhb_loop+0x15/0x70
[ 86.715330] ? clear_bhb_loop+0x15/0x70
[ 86.715844] entry_SYSCALL_64_after_hwframe+0x78/0x80
[ 86.716378] RIP: 0033:0x724d0791b175
[ 86.716895] Code: 83 e2 40 75 50 89 f0 f7 d0 a9 00 00 41 00 74 45 80 3d de fe 0e 00 00 74 60 89 da 4c 89 e6 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 7f 00 00 00 48 8b 55 b8 64 48 2b 14 25 28
[ 86.718058] RSP: 002b:00007ffd9c151d40 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[ 86.718648] RAX: ffffffffffffffda RBX: 0000000000000941 RCX: 0000724d0791b175
[ 86.719225] RDX: 0000000000000941 RSI: 00007ffd9c153635 RDI: 00000000ffffff9c
[ 86.719833] RBP: 00007ffd9c151db0 R08: 0000000000000000 R09: 0000000000000000
[ 86.720414] R10: 00000000000001b6 R11: 0000000000000202 R12: 00007ffd9c153635
[ 86.720982] R13: 0000724d07a03248 R14: 0000000000000000 R15: 0000000000000001
[ 86.721596] </TASK>
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-62-generic 6.8.0-62.65
ProcVersionSignature: Ubuntu 6.8.0-62.65-generic 6.8.12
Uname: Linux 6.8.0-62-generic x86_64
AlsaDevices:
total 0
crw-rw----. 1 root audio 116, 1 Jun 26 19:53 seq
crw-rw----. 1 root audio 116, 33 Jun 26 19:53 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Jun 26 20:01:43 2025
InstallationDate: Installed on 2024-03-19 (464 days ago)
InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 vmwgfxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-62-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ipv6.disable=1 ipv6.disable=1 audit=1 audit_backlog_limit=8192 panic=10 security=selinux selinux=1 apparmor=0
RelatedPackageVersions:
linux-restricted-modules-6.8.0-62-generic N/A
linux-backports-modules-6.8.0-62-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2025-06-26 (0 days ago)
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115447/+subscriptions
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115447
Title:
Ubuntu 24.04.2: NULL pointer dereference with Ceph and selinux
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
fs/ceph,selinux: fix NULL pointer dereference on CephFS write with
SELinux in permissive mode
A NULL pointer dereference occurs in the Ceph kernel client (CephFS)
when a file is created on a mounted CephFS volume while SELinux is
enabled in permissive mode.
[ 86.678570] BUG: kernel NULL pointer dereference, address: 000000000000001d
[ 86.679238] #PF: supervisor read access in kernel mode
[ 86.679859] #PF: error_code(0x0000) - not-present page
[ 86.680445] PGD 0 P4D 0
[ 86.681021] Oops: 0000 [#1] PREEMPT SMP PTI
[ 86.681558] CPU: 0 PID: 2818 Comm: touch Not tainted 6.8.0-62-generic #65-Ubuntu
[ 86.682095] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[ 86.682716] RIP: 0010:memcpy_orig+0x54/0x130
[ 86.683267] Code: 89 07 4c 89 4f 08 4c 89 57 10 4c 89 5f 18 48 8d 7f 20 73 d4 83 c2 20 eb 44 48 01 d6 48 01 d7 48 83 ea 20 0f 1f 00 48 83 ea 20 <4c> 8b 46 f8 4c 8b 4e f0 4c 8b 56 e8 4c 8b 5e e0 48 8d 76 e0 4c 89
[ 86.684464] RSP: 0018:ffffa79300b2f7e0 EFLAGS: 00010283
[ 86.685060] RAX: ffff9aeb6123a008 RBX: 0000000000000ff8 RCX: 0000000000000000
[ 86.685659] RDX: ffffffffffffffe5 RSI: 0000000000000025 RDI: ffff9aeb6123a02d
[ 86.686265] RBP: ffffa79300b2f810 R08: 0000000000000025 R09: 0000000000000000
[ 86.686843] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000025
[ 86.687366] R13: 0000000000000000 R14: ffff9aeb408d5960 R15: ffffa79300b2f8e4
[ 86.687888] FS: 0000724d07b47740(0000) GS:ffff9aec77c00000(0000) knlGS:0000000000000000
[ 86.688416] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 86.688947] CR2: 000000000000001d CR3: 000000012038a004 CR4: 00000000001706f0
[ 86.689541] Call Trace:
[ 86.690124] <TASK>
[ 86.690704] ? show_regs+0x6d/0x80
[ 86.691256] ? __die+0x24/0x80
[ 86.691807] ? page_fault_oops+0x99/0x1b0
[ 86.692426] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[ 86.692991] ? __bad_area_nosemaphore+0x19e/0x2c0
[ 86.693563] ? find_vma+0x34/0x60
[ 86.694214] ? bad_area_nosemaphore+0x16/0x30
[ 86.694835] ? do_user_addr_fault+0x29d/0x670
[ 86.695439] ? exc_page_fault+0x83/0x1b0
[ 86.696024] ? asm_exc_page_fault+0x27/0x30
[ 86.696614] ? memcpy_orig+0x54/0x130
[ 86.697202] ? ceph_pagelist_append+0x124/0x150 [libceph]
[ 86.697995] ceph_security_init_secctx+0xce/0x1f0 [ceph]
[ 86.698733] ceph_new_inode+0x80/0xe0 [ceph]
[ 86.699484] ceph_atomic_open+0x3b2/0x9d0 [ceph]
[ 86.700239] ? may_create+0x141/0x150
[ 86.700903] lookup_open.isra.0+0x3a9/0x570
[ 86.701534] open_last_lookups+0x14f/0x400
[ 86.702196] path_openat+0x99/0x2d0
[ 86.702815] do_filp_open+0xaf/0x170
[ 86.703475] do_sys_openat2+0xb3/0xe0
[ 86.704098] __x64_sys_openat+0x55/0xa0
[ 86.704804] x64_sys_call+0x1eb1/0x25a0
[ 86.705437] do_syscall_64+0x7f/0x180
[ 86.706120] ? filemap_map_pages+0x2fe/0x4c0
[ 86.706792] ? __lruvec_stat_mod_folio+0x70/0xc0
[ 86.707444] ? do_read_fault+0x112/0x200
[ 86.708157] ? do_fault+0xf0/0x260
[ 86.708850] ? handle_pte_fault+0x114/0x1d0
[ 86.709519] ? __handle_mm_fault+0x654/0x800
[ 86.710216] ? __count_memcg_events+0x6b/0x120
[ 86.710884] ? count_memcg_events.constprop.0+0x2a/0x50
[ 86.711505] ? handle_mm_fault+0xad/0x380
[ 86.712136] ? do_user_addr_fault+0x334/0x670
[ 86.712778] ? irqentry_exit_to_user_mode+0x7b/0x260
[ 86.713433] ? irqentry_exit+0x43/0x50
[ 86.714111] ? clear_bhb_loop+0x15/0x70
[ 86.714777] ? clear_bhb_loop+0x15/0x70
[ 86.715330] ? clear_bhb_loop+0x15/0x70
[ 86.715844] entry_SYSCALL_64_after_hwframe+0x78/0x80
[ 86.716378] RIP: 0033:0x724d0791b175
[ 86.716895] Code: 83 e2 40 75 50 89 f0 f7 d0 a9 00 00 41 00 74 45 80 3d de fe 0e 00 00 74 60 89 da 4c 89 e6 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 7f 00 00 00 48 8b 55 b8 64 48 2b 14 25 28
[ 86.718058] RSP: 002b:00007ffd9c151d40 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[ 86.718648] RAX: ffffffffffffffda RBX: 0000000000000941 RCX: 0000724d0791b175
[ 86.719225] RDX: 0000000000000941 RSI: 00007ffd9c153635 RDI: 00000000ffffff9c
[ 86.719833] RBP: 00007ffd9c151db0 R08: 0000000000000000 R09: 0000000000000000
[ 86.720414] R10: 00000000000001b6 R11: 0000000000000202 R12: 00007ffd9c153635
[ 86.720982] R13: 0000724d07a03248 R14: 0000000000000000 R15: 0000000000000001
[ 86.721596] </TASK>
[ Fix ]
The issue must be solved modifying kernel code as follows:
- In the SELinux hook selinux_dentry_init_security(), remove a faulty cast when
assigning the context pointer is removed, allowing the LSM to populate
the context buffer correctly, avoinding the NULL pointer dereference
- In ceph_security_init_secctx(), add the missing encoding of the xattr name
and it's length to the pagelist
[ Test Plan ]
The issue can be reproduced (before) and the fix tested (after)
following the steps below:
$ sudo snap install microceph
$ sudo microceph cluster bootstrap
$ sudo microceph.ceph osd crush rule rm replicated_rule
$ sudo microceph.ceph osd crush rule create-replicated single default osd
$ sudo microceph disk add /dev/sdb --wipe
$ sudo microceph.ceph config set global osd_pool_default_size 1
$ sudo microceph.ceph osd pool create cephfs_metadata 8
$ sudo microceph.ceph osd pool create cephfs_data 8
$ sudo microceph.ceph fs new cephfs cephfs_metadata cephfs_data
$ sudo apt install selinux-basics selinux-policy-default -y && sudo selinux-activate
$ sudo reboot
$ sudo mkdir -p /mnt/cephfs
$ sudo microceph.ceph auth get-or-create client.admin mon 'allow *' mds 'allow *' osd 'allow *' mgr 'allow *'
$ sudo mount -t ceph $(hostname -I | awk '{print $1}'):6789:/ /mnt/cephfs -o name=admin,secret=
$ sudo touch /mnt/cephfs/test.txt
$ ll /mnt/cephfs/
[ Regression Potential ]
This fix modifies how SELinux provides security context data
to the CephFS client and how that data is encoded for transmission.
A regression could cause incorrect xattr encoding,
resulting in file creation failures (EPERM or EIO) or LSM labeling errors.
If the context pointer is mishandled, memory corruption or crashes may occur.
Additionally, malformed pagelist encoding could cause client-MDS
protocol mismatches.
---
Upgraded ceph cluster running ceph to 24.04.2 from Ubuntu 22. Turning
on selinux (permissive), hit a kernel null reference when mounting
cephfs and trying to touch a file:
1. Update cluster to 24.04
2. Verify ceph is working as intended (able to mount cephFS, write out
a file, unmount, etc.)
3. Installed selinux packages
4. Added following to grub on all 3 cluster members:
"audit=1 audit_backlog_limit=8192 panic=10 security=selinux selinux=1 apparmor=0"
5. Selinux policy is permissive:
root@ceph0:~# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: actual (secure)
Max kernel policy version: 33
root@ceph0:~#
6. Mounted ceph fs:
mount -t ceph admin@.cephfs=/ /var/lib/libvirt/images -o ms_mode=secure
7. attempted to write a file, did not complete and null reference reported:
[ 86.678570] BUG: kernel NULL pointer dereference, address: 000000000000001d
[ 86.679238] #PF: supervisor read access in kernel mode
[ 86.679859] #PF: error_code(0x0000) - not-present page
[ 86.680445] PGD 0 P4D 0
[ 86.681021] Oops: 0000 [#1] PREEMPT SMP PTI
[ 86.681558] CPU: 0 PID: 2818 Comm: touch Not tainted 6.8.0-62-generic #65-Ubuntu
[ 86.682095] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[ 86.682716] RIP: 0010:memcpy_orig+0x54/0x130
[ 86.683267] Code: 89 07 4c 89 4f 08 4c 89 57 10 4c 89 5f 18 48 8d 7f 20 73 d4 83 c2 20 eb 44 48 01 d6 48 01 d7 48 83 ea 20 0f 1f 00 48 83 ea 20 <4c> 8b 46 f8 4c 8b 4e f0 4c 8b 56 e8 4c 8b 5e e0 48 8d 76 e0 4c 89
[ 86.684464] RSP: 0018:ffffa79300b2f7e0 EFLAGS: 00010283
[ 86.685060] RAX: ffff9aeb6123a008 RBX: 0000000000000ff8 RCX: 0000000000000000
[ 86.685659] RDX: ffffffffffffffe5 RSI: 0000000000000025 RDI: ffff9aeb6123a02d
[ 86.686265] RBP: ffffa79300b2f810 R08: 0000000000000025 R09: 0000000000000000
[ 86.686843] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000025
[ 86.687366] R13: 0000000000000000 R14: ffff9aeb408d5960 R15: ffffa79300b2f8e4
[ 86.687888] FS: 0000724d07b47740(0000) GS:ffff9aec77c00000(0000) knlGS:0000000000000000
[ 86.688416] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 86.688947] CR2: 000000000000001d CR3: 000000012038a004 CR4: 00000000001706f0
[ 86.689541] Call Trace:
[ 86.690124] <TASK>
[ 86.690704] ? show_regs+0x6d/0x80
[ 86.691256] ? __die+0x24/0x80
[ 86.691807] ? page_fault_oops+0x99/0x1b0
[ 86.692426] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[ 86.692991] ? __bad_area_nosemaphore+0x19e/0x2c0
[ 86.693563] ? find_vma+0x34/0x60
[ 86.694214] ? bad_area_nosemaphore+0x16/0x30
[ 86.694835] ? do_user_addr_fault+0x29d/0x670
[ 86.695439] ? exc_page_fault+0x83/0x1b0
[ 86.696024] ? asm_exc_page_fault+0x27/0x30
[ 86.696614] ? memcpy_orig+0x54/0x130
[ 86.697202] ? ceph_pagelist_append+0x124/0x150 [libceph]
[ 86.697995] ceph_security_init_secctx+0xce/0x1f0 [ceph]
[ 86.698733] ceph_new_inode+0x80/0xe0 [ceph]
[ 86.699484] ceph_atomic_open+0x3b2/0x9d0 [ceph]
[ 86.700239] ? may_create+0x141/0x150
[ 86.700903] lookup_open.isra.0+0x3a9/0x570
[ 86.701534] open_last_lookups+0x14f/0x400
[ 86.702196] path_openat+0x99/0x2d0
[ 86.702815] do_filp_open+0xaf/0x170
[ 86.703475] do_sys_openat2+0xb3/0xe0
[ 86.704098] __x64_sys_openat+0x55/0xa0
[ 86.704804] x64_sys_call+0x1eb1/0x25a0
[ 86.705437] do_syscall_64+0x7f/0x180
[ 86.706120] ? filemap_map_pages+0x2fe/0x4c0
[ 86.706792] ? __lruvec_stat_mod_folio+0x70/0xc0
[ 86.707444] ? do_read_fault+0x112/0x200
[ 86.708157] ? do_fault+0xf0/0x260
[ 86.708850] ? handle_pte_fault+0x114/0x1d0
[ 86.709519] ? __handle_mm_fault+0x654/0x800
[ 86.710216] ? __count_memcg_events+0x6b/0x120
[ 86.710884] ? count_memcg_events.constprop.0+0x2a/0x50
[ 86.711505] ? handle_mm_fault+0xad/0x380
[ 86.712136] ? do_user_addr_fault+0x334/0x670
[ 86.712778] ? irqentry_exit_to_user_mode+0x7b/0x260
[ 86.713433] ? irqentry_exit+0x43/0x50
[ 86.714111] ? clear_bhb_loop+0x15/0x70
[ 86.714777] ? clear_bhb_loop+0x15/0x70
[ 86.715330] ? clear_bhb_loop+0x15/0x70
[ 86.715844] entry_SYSCALL_64_after_hwframe+0x78/0x80
[ 86.716378] RIP: 0033:0x724d0791b175
[ 86.716895] Code: 83 e2 40 75 50 89 f0 f7 d0 a9 00 00 41 00 74 45 80 3d de fe 0e 00 00 74 60 89 da 4c 89 e6 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 7f 00 00 00 48 8b 55 b8 64 48 2b 14 25 28
[ 86.718058] RSP: 002b:00007ffd9c151d40 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[ 86.718648] RAX: ffffffffffffffda RBX: 0000000000000941 RCX: 0000724d0791b175
[ 86.719225] RDX: 0000000000000941 RSI: 00007ffd9c153635 RDI: 00000000ffffff9c
[ 86.719833] RBP: 00007ffd9c151db0 R08: 0000000000000000 R09: 0000000000000000
[ 86.720414] R10: 00000000000001b6 R11: 0000000000000202 R12: 00007ffd9c153635
[ 86.720982] R13: 0000724d07a03248 R14: 0000000000000000 R15: 0000000000000001
[ 86.721596] </TASK>
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-62-generic 6.8.0-62.65
ProcVersionSignature: Ubuntu 6.8.0-62.65-generic 6.8.12
Uname: Linux 6.8.0-62-generic x86_64
AlsaDevices:
total 0
crw-rw----. 1 root audio 116, 1 Jun 26 19:53 seq
crw-rw----. 1 root audio 116, 33 Jun 26 19:53 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Jun 26 20:01:43 2025
InstallationDate: Installed on 2024-03-19 (464 days ago)
InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 vmwgfxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-62-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ipv6.disable=1 ipv6.disable=1 audit=1 audit_backlog_limit=8192 panic=10 security=selinux selinux=1 apparmor=0
RelatedPackageVersions:
linux-restricted-modules-6.8.0-62-generic N/A
linux-backports-modules-6.8.0-62-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2025-06-26 (0 days ago)
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115447/+subscriptions
[Bug 2108954] Re: Fix Mic Mute LED no function on HP G12 laptops with ACP7.0 platform
** Changed in: linux-oem-6.14 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.11 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2108954
Title:
Fix Mic Mute LED no function on HP G12 laptops with ACP7.0 platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
New
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
[Impact]
HP G12 laptops on AMD platform with audio codec RTK ALC3315+CS35L56 amplifier, the MIC-Mute function is working but the LED state is not toggled accordingly.
[Fix]
The HP laptops on AMD platform needs a upstream patch e2cda4617656 ("ASoC: amd: acp: Refactor dmic-codec platform device creation") landed since 6.14-rc6 to correctly create a dmic-codec device instead of a audio card driven by snd_acp_legacy_mach.
[Test Case]
1. Boot and log into the HP G12 laptops powered by AMD.
2. Issue command `alsa-info` and check the generated output file
3. Make sure no card named snd_acp_legacy_mach listed in ALSA modules
4. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon.
5. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
The patch identify the audio device for ACP7.0 correctly. Needs to verify on new AMD platforms which supports ACP7.0 devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2108954/+subscriptions
Status: New => Invalid
** Changed in: linux-oem-6.11 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2108954
Title:
Fix Mic Mute LED no function on HP G12 laptops with ACP7.0 platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
New
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
[Impact]
HP G12 laptops on AMD platform with audio codec RTK ALC3315+CS35L56 amplifier, the MIC-Mute function is working but the LED state is not toggled accordingly.
[Fix]
The HP laptops on AMD platform needs a upstream patch e2cda4617656 ("ASoC: amd: acp: Refactor dmic-codec platform device creation") landed since 6.14-rc6 to correctly create a dmic-codec device instead of a audio card driven by snd_acp_legacy_mach.
[Test Case]
1. Boot and log into the HP G12 laptops powered by AMD.
2. Issue command `alsa-info` and check the generated output file
3. Make sure no card named snd_acp_legacy_mach listed in ALSA modules
4. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon.
5. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
The patch identify the audio device for ACP7.0 correctly. Needs to verify on new AMD platforms which supports ACP7.0 devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2108954/+subscriptions
[Bug 2094986] Re: randomly graphic glitch on some OLED edp panel(amdgpu)
** Changed in: linux-oem-6.14 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2094986
Title:
randomly graphic glitch on some OLED edp panel(amdgpu)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
New
Bug description:
[Impact]
There was randomly graphic glitch on edp with AMDGPU
[Fix]
AMD provides a patch to disable PSR on this panel to fix the issue.
The patch is under AMD internal review and is not submitted to upstream yet.
c31b41f1cb32 drm/amd/display: Disable PSR-SU on some OLED panel
[Test]
1. Boot in OS
2. Idel the machine for a while (~1 min) and move the cursor.
3. There should not have any graphic glitch when using the machine.
[Where problems could occur]
This is a quirk for a specific panel, so should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2094986/+subscriptions
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2094986
Title:
randomly graphic glitch on some OLED edp panel(amdgpu)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
New
Bug description:
[Impact]
There was randomly graphic glitch on edp with AMDGPU
[Fix]
AMD provides a patch to disable PSR on this panel to fix the issue.
The patch is under AMD internal review and is not submitted to upstream yet.
c31b41f1cb32 drm/amd/display: Disable PSR-SU on some OLED panel
[Test]
1. Boot in OS
2. Idel the machine for a while (~1 min) and move the cursor.
3. There should not have any graphic glitch when using the machine.
[Where problems could occur]
This is a quirk for a specific panel, so should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2094986/+subscriptions
[Bug 2091864] Re: Cannot enter luks password at boot after kernel 6.8.0-50 upgrade
I had the same problem on a recently installed Kubuntu 24.04 system on HP ProBook 450 G1 (Haswell i5, with integrated graphics). Kernel is 6.8.0-71.
Cold boot was working fine, but on *reboot* I got a black screen at the LUKS password prompt, so not seeing the HP and Kubuntu boot logos. Please note that, if I typed the password blindly, the boot process was then proceeding successfully, and the system in the end was starting. However, it was quite annoying not to see anything.
Adding i915 to /etc/initramfs-tools/modules and running "update-
initramfs -u" fixed he problem for me too.
It was not easy to find this bug report though, since searching for
"reboot problems" was leading to a lot of other "black screen on boot"
problems, unrelated to this one, including an (already fixed) sddm
problem for Kubuntu.
Never had this problem with Kubuntu 20.04 or on 16.04 and 14.04 bases.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2091864
Title:
Cannot enter luks password at boot after kernel 6.8.0-50 upgrade
Status in linux package in Ubuntu:
Confirmed
Bug description:
Upgraded Ubuntu 24.04 software, including kernel 6.8.0-50, after which
upon booting the luks password couldn't be entered (dialog
unresponsive). Was able to boot 6.8.0-49. Could boot 6.8.0-50 with
quiet splash commented out - with text input.
Added i915 (my video driver) to /etc/initramfs-tools/modules and
updated initrd, after which could boot 6.8.0-50.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091864/+subscriptions
Cold boot was working fine, but on *reboot* I got a black screen at the LUKS password prompt, so not seeing the HP and Kubuntu boot logos. Please note that, if I typed the password blindly, the boot process was then proceeding successfully, and the system in the end was starting. However, it was quite annoying not to see anything.
Adding i915 to /etc/initramfs-tools/modules and running "update-
initramfs -u" fixed he problem for me too.
It was not easy to find this bug report though, since searching for
"reboot problems" was leading to a lot of other "black screen on boot"
problems, unrelated to this one, including an (already fixed) sddm
problem for Kubuntu.
Never had this problem with Kubuntu 20.04 or on 16.04 and 14.04 bases.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2091864
Title:
Cannot enter luks password at boot after kernel 6.8.0-50 upgrade
Status in linux package in Ubuntu:
Confirmed
Bug description:
Upgraded Ubuntu 24.04 software, including kernel 6.8.0-50, after which
upon booting the luks password couldn't be entered (dialog
unresponsive). Was able to boot 6.8.0-49. Could boot 6.8.0-50 with
quiet splash commented out - with text input.
Added i915 (my video driver) to /etc/initramfs-tools/modules and
updated initrd, after which could boot 6.8.0-50.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091864/+subscriptions
[Bug 2092649] Re: Can't enter passphrase for encrypted disk on splash screen after kernel updated to 6.8.0-51-generic
Thank you Nikolaj, I made it pressing "E" when in grub for editing, maybe i's a Linux Mint thing.
But I'm done with Linux so far, having OLED-screens I don't want the login screen to burn-in, Win 10 and 11 go to black after 1 min. Neither the Login-GUI nor the command line login does this.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2092649
Title:
Can't enter passphrase for encrypted disk on splash screen after
kernel updated to 6.8.0-51-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Splash screen is not accepting/allowing passphrase for disk decryption
during boot up. This issue started after kernel is updated to
6.8.0-51-generic. I am able to add passphrase for decryption when I
choose kernel version 6.8.0-49-generic from grub menu under advanced
option.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-51-generic 6.8.0-51.52
ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12
Uname: Linux 6.8.0-49-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_6_8_0_49_49_generic_108
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: navi 3468 F.... pipewire
/dev/snd/controlC0: navi 3468 F.... pipewire
navi 3474 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 29 12:48:16 2024
InstallationDate: Installed on 2024-04-25 (248 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: HP HP Pavilion Plus Laptop 14-eh0xxx
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-49-generic root=UUID=e5bf5ce0-354c-4c6d-9a6d-1743a6e84587 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-49-generic N/A
linux-backports-modules-6.8.0-49-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2023
dmi.bios.release: 15.10
dmi.bios.vendor: Insyde
dmi.bios.version: F.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8A36
dmi.board.vendor: HP
dmi.board.version: 31.36
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 31.36
dmi.modalias: dmi:bvnInsyde:bvrF.10:bd08/16/2023:br15.10:efr31.36:svnHP:pnHPPavilionPlusLaptop14-eh0xxx:pvrType1ProductConfigId:rvnHP:rn8A36:rvr31.36:cvnHP:ct10:cvrChassisVersion:sku6Q158PA#ACJ:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Plus Laptop 14-eh0xxx
dmi.product.sku: 6Q158PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092649/+subscriptions
But I'm done with Linux so far, having OLED-screens I don't want the login screen to burn-in, Win 10 and 11 go to black after 1 min. Neither the Login-GUI nor the command line login does this.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2092649
Title:
Can't enter passphrase for encrypted disk on splash screen after
kernel updated to 6.8.0-51-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Splash screen is not accepting/allowing passphrase for disk decryption
during boot up. This issue started after kernel is updated to
6.8.0-51-generic. I am able to add passphrase for decryption when I
choose kernel version 6.8.0-49-generic from grub menu under advanced
option.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-51-generic 6.8.0-51.52
ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12
Uname: Linux 6.8.0-49-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_6_8_0_49_49_generic_108
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: navi 3468 F.... pipewire
/dev/snd/controlC0: navi 3468 F.... pipewire
navi 3474 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 29 12:48:16 2024
InstallationDate: Installed on 2024-04-25 (248 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: HP HP Pavilion Plus Laptop 14-eh0xxx
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-49-generic root=UUID=e5bf5ce0-354c-4c6d-9a6d-1743a6e84587 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-49-generic N/A
linux-backports-modules-6.8.0-49-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2023
dmi.bios.release: 15.10
dmi.bios.vendor: Insyde
dmi.bios.version: F.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8A36
dmi.board.vendor: HP
dmi.board.version: 31.36
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 31.36
dmi.modalias: dmi:bvnInsyde:bvrF.10:bd08/16/2023:br15.10:efr31.36:svnHP:pnHPPavilionPlusLaptop14-eh0xxx:pvrType1ProductConfigId:rvnHP:rn8A36:rvr31.36:cvnHP:ct10:cvrChassisVersion:sku6Q158PA#ACJ:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Plus Laptop 14-eh0xxx
dmi.product.sku: 6Q158PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092649/+subscriptions
суббота
[Bug 2100565] Re: kernel update broke Logitech G603 mouse over Bluetooth, other Bluetooth devices work fine
Follow up. This bug has been fixed in the kernel with this commit:
https://github.com/torvalds/linux/commit/6ec3185fbc3528f2284c347fb9bd8be6fa672ed4
It's in 6.16-rc7 and later. I haven't had much luck running the release
candidates on my system yet, but based on the long discussion here, I am
sure it will work.
https://github.com/StarLabsLtd/firmware/issues/180
** Bug watch added: github.com/StarLabsLtd/firmware/issues #180
https://github.com/StarLabsLtd/firmware/issues/180
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100565
Title:
kernel update broke Logitech G603 mouse over Bluetooth, other
Bluetooth devices work fine
Status in linux package in Ubuntu:
Confirmed
Bug description:
For the full story, see this Ubuntu Discourse thread:
https://discourse.ubuntu.com/t/recent-kernel-update-broke-
logitech-g603-mouse-over-bluetooth-other-bluetooth-devices-work-
fine/55707/1
Short summary of our findings:
On Ubuntu 24.04 LTS, between kernel 6.10.14 and 6.11-rc1, my Logitech
G603 mouse breaks in that while it is paired and connected, no mouse
clicks nor mouse movements are registered in 6.11-rc1 or later. The
problem exists all the way to the current RC, 6.14-rc4. I discovered
the bug firsthand when running a recent Ubuntu apt update that jumped
me from kernel 6.8.0-51 to 6.11.0-17.
Another user not using Ubuntu reports the same problem with his non-
Logitech Bluetooth keyboard and mouse. What we have in common is the
Intel Bluetooth adapter, which is "ID 8087:0aaa Intel Corp. Bluetooth
9460/9560 Jefferson Peak (JfP)". Other users with other Intel adapters
such as the AX211 do not have the same problem. I also attached a CSR
USB-to-Bluetooth adapter to the affected system, and the mouse works
fine, even on the bad kernel versions 6.11-rc1 and up.
I did diagnostic testing using git bisect and building the LINUX
kernel from source on the affected machine. The sequence I found is
here:
git bisect start
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
git bisect bad 280e36f0d5b997173d014c07484c03a7f7750668
git bisect good 0434dbe32053d07d658165be681505120c6b1abc
git bisect good 80ab5445da623540ea6303740015dd0210a06dc8
git bisect bad e2f710f97f3544df08ebe608c8157536e0ffb494
git bisect bad 586f14a6a182bbdb9404dc66464dcd8d0ac175a3
git bisect bad f6dc9214e526c2f735d93b5330f4dcd42a2b5308
git bisect good 464b99e77b3d024a319db0dabe917d04824039db
git bisect good b1c7cd6caaf6209ed9f7df59b61a2ac885eb79b3
git bisect bad fb5e4713fc185f6283ba0704edccea312253e805
git bisect bad 27489364299a2ddb5c54cd9f29a3f41bd8d151ab
git bisect good d4cc4ee48167b4c25abf49ead19412c29a1ad9f4
git bisect bad 08c22b52262041164990eef4b0e076bce173a3b2
git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
The final result is that this commit is the one that breaks the mouse
for the Intel 9460/9560 adapter:
$ git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
f25b7fd36cc3a850e006aed686f5bbecd200de1b is the first bad commit
commit f25b7fd36cc3a850e006aed686f5bbecd200de1b
Author: Ying Hsu <yinghsu@chromium.org>
Date: Wed May 29 08:00:00 2024 +0000
Bluetooth: Add vendor-specific packet classification for ISO data
When HCI raw sockets are opened, the Bluetooth kernel module doesn't
track CIS/BIS connections. User-space applications have to identify
ISO data by maintaining connection information and look up the mapping
for each ACL data packet received. Besides, btsnoop log captured in
kernel couldn't tell ISO data from ACL data in this case.
To avoid additional lookups, this patch introduces vendor-specific
packet classification for Intel BT controllers to distinguish
ISO data packets from ACL data packets.
Signed-off-by: Ying Hsu <yinghsu@chromium.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
drivers/bluetooth/btintel.c | 25 +++++++++++++++++++++++--
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 16 ++++++++++++++++
3 files changed, 40 insertions(+), 2 deletions(-)
I am pretty sure this commit affects one file in the modules package,
but it might be in another package from the same kernel update. The
whole update from the apt.log is here:
Start-Date: 2025-02-12 12:54:16
Commandline: apt upgrade
Requested-By: me (1000)
Install: linux-hwe-6.11-tools-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-extra-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-image-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-tools-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-hwe-6.11-headers-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-headers-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic)
Upgrade: linux-headers-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-tools-common:amd64 (6.8.0-52.53, 6.8.0-53.55), base-files:amd64 (13ubuntu10.1, 13ubuntu10.2), bpftrace:amd64 (0.20.2-1ubuntu4.2, 0.20.2-1ubuntu4.3), linux-image-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.7, 20240318.git3b128b60-0ubuntu2.9), code:amd64 (1.97.0-1738713410, 1.97.1-1739197498), microsoft-edge-stable:amd64 (132.0.2957.140-1, 133.0.3065.59-1), linux-libc-dev:amd64 (6.8.0-52.53, 6.8.0-53.55)
End-Date: 2025-02-12 12:55:35
Start-Date: 2025-02-12 15:26:04
Commandline: apt autoremove
Requested-By: me (1000)
Remove: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-tools-6.8.0-51:amd64 (6.8.0-51.52), linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51:amd64 (6.8.0-51.52), linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52)
End-Date: 2025-02-12 15:26:12
Currently, I can boot from kernel 6.10.14 and get my mouse working
again, so this is not a show-stopper bug.
I'm willing to help test/diagnose further, if needed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-modules-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 27 14:33:40 2025
Dependencies:
InstallationDate: Installed on 2024-04-29 (304 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dchang 3365 F.... pipewire
/dev/snd/controlC0: dchang 3370 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-29 (309 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Star Labs StarLite
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=40a0d991-e225-4f4b-8cb9-dee8d07c661a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/28/2025
dmi.bios.release: 24.8
dmi.bios.vendor: coreboot
dmi.bios.version: 25.01
dmi.board.name: StarLite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 32
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 25.1
dmi.modalias: dmi:bvncoreboot:bvr25.01:bd01/28/2025:br24.8:efr25.1:svnStarLabs:pnStarLite:pvr1.0:rvnStarLabs:rnStarLite:rvr1.0:cvnStarLabs:ct32:cvr1.0:skuI5:
dmi.product.family: I5
dmi.product.name: StarLite
dmi.product.sku: I5
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565/+subscriptions
https://github.com/torvalds/linux/commit/6ec3185fbc3528f2284c347fb9bd8be6fa672ed4
It's in 6.16-rc7 and later. I haven't had much luck running the release
candidates on my system yet, but based on the long discussion here, I am
sure it will work.
https://github.com/StarLabsLtd/firmware/issues/180
** Bug watch added: github.com/StarLabsLtd/firmware/issues #180
https://github.com/StarLabsLtd/firmware/issues/180
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100565
Title:
kernel update broke Logitech G603 mouse over Bluetooth, other
Bluetooth devices work fine
Status in linux package in Ubuntu:
Confirmed
Bug description:
For the full story, see this Ubuntu Discourse thread:
https://discourse.ubuntu.com/t/recent-kernel-update-broke-
logitech-g603-mouse-over-bluetooth-other-bluetooth-devices-work-
fine/55707/1
Short summary of our findings:
On Ubuntu 24.04 LTS, between kernel 6.10.14 and 6.11-rc1, my Logitech
G603 mouse breaks in that while it is paired and connected, no mouse
clicks nor mouse movements are registered in 6.11-rc1 or later. The
problem exists all the way to the current RC, 6.14-rc4. I discovered
the bug firsthand when running a recent Ubuntu apt update that jumped
me from kernel 6.8.0-51 to 6.11.0-17.
Another user not using Ubuntu reports the same problem with his non-
Logitech Bluetooth keyboard and mouse. What we have in common is the
Intel Bluetooth adapter, which is "ID 8087:0aaa Intel Corp. Bluetooth
9460/9560 Jefferson Peak (JfP)". Other users with other Intel adapters
such as the AX211 do not have the same problem. I also attached a CSR
USB-to-Bluetooth adapter to the affected system, and the mouse works
fine, even on the bad kernel versions 6.11-rc1 and up.
I did diagnostic testing using git bisect and building the LINUX
kernel from source on the affected machine. The sequence I found is
here:
git bisect start
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
git bisect bad 280e36f0d5b997173d014c07484c03a7f7750668
git bisect good 0434dbe32053d07d658165be681505120c6b1abc
git bisect good 80ab5445da623540ea6303740015dd0210a06dc8
git bisect bad e2f710f97f3544df08ebe608c8157536e0ffb494
git bisect bad 586f14a6a182bbdb9404dc66464dcd8d0ac175a3
git bisect bad f6dc9214e526c2f735d93b5330f4dcd42a2b5308
git bisect good 464b99e77b3d024a319db0dabe917d04824039db
git bisect good b1c7cd6caaf6209ed9f7df59b61a2ac885eb79b3
git bisect bad fb5e4713fc185f6283ba0704edccea312253e805
git bisect bad 27489364299a2ddb5c54cd9f29a3f41bd8d151ab
git bisect good d4cc4ee48167b4c25abf49ead19412c29a1ad9f4
git bisect bad 08c22b52262041164990eef4b0e076bce173a3b2
git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
The final result is that this commit is the one that breaks the mouse
for the Intel 9460/9560 adapter:
$ git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
f25b7fd36cc3a850e006aed686f5bbecd200de1b is the first bad commit
commit f25b7fd36cc3a850e006aed686f5bbecd200de1b
Author: Ying Hsu <yinghsu@chromium.org>
Date: Wed May 29 08:00:00 2024 +0000
Bluetooth: Add vendor-specific packet classification for ISO data
When HCI raw sockets are opened, the Bluetooth kernel module doesn't
track CIS/BIS connections. User-space applications have to identify
ISO data by maintaining connection information and look up the mapping
for each ACL data packet received. Besides, btsnoop log captured in
kernel couldn't tell ISO data from ACL data in this case.
To avoid additional lookups, this patch introduces vendor-specific
packet classification for Intel BT controllers to distinguish
ISO data packets from ACL data packets.
Signed-off-by: Ying Hsu <yinghsu@chromium.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
drivers/bluetooth/btintel.c | 25 +++++++++++++++++++++++--
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 16 ++++++++++++++++
3 files changed, 40 insertions(+), 2 deletions(-)
I am pretty sure this commit affects one file in the modules package,
but it might be in another package from the same kernel update. The
whole update from the apt.log is here:
Start-Date: 2025-02-12 12:54:16
Commandline: apt upgrade
Requested-By: me (1000)
Install: linux-hwe-6.11-tools-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-extra-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-image-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-tools-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-hwe-6.11-headers-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-headers-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic)
Upgrade: linux-headers-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-tools-common:amd64 (6.8.0-52.53, 6.8.0-53.55), base-files:amd64 (13ubuntu10.1, 13ubuntu10.2), bpftrace:amd64 (0.20.2-1ubuntu4.2, 0.20.2-1ubuntu4.3), linux-image-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.7, 20240318.git3b128b60-0ubuntu2.9), code:amd64 (1.97.0-1738713410, 1.97.1-1739197498), microsoft-edge-stable:amd64 (132.0.2957.140-1, 133.0.3065.59-1), linux-libc-dev:amd64 (6.8.0-52.53, 6.8.0-53.55)
End-Date: 2025-02-12 12:55:35
Start-Date: 2025-02-12 15:26:04
Commandline: apt autoremove
Requested-By: me (1000)
Remove: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-tools-6.8.0-51:amd64 (6.8.0-51.52), linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51:amd64 (6.8.0-51.52), linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52)
End-Date: 2025-02-12 15:26:12
Currently, I can boot from kernel 6.10.14 and get my mouse working
again, so this is not a show-stopper bug.
I'm willing to help test/diagnose further, if needed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-modules-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 27 14:33:40 2025
Dependencies:
InstallationDate: Installed on 2024-04-29 (304 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dchang 3365 F.... pipewire
/dev/snd/controlC0: dchang 3370 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-29 (309 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Star Labs StarLite
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=40a0d991-e225-4f4b-8cb9-dee8d07c661a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/28/2025
dmi.bios.release: 24.8
dmi.bios.vendor: coreboot
dmi.bios.version: 25.01
dmi.board.name: StarLite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 32
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 25.1
dmi.modalias: dmi:bvncoreboot:bvr25.01:bd01/28/2025:br24.8:efr25.1:svnStarLabs:pnStarLite:pvr1.0:rvnStarLabs:rnStarLite:rvr1.0:cvnStarLabs:ct32:cvr1.0:skuI5:
dmi.product.family: I5
dmi.product.name: StarLite
dmi.product.sku: I5
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565/+subscriptions
[Bug 2119390] Re: My Mic Is Not Working.
Hello Any Updates.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2119390
Title:
My Mic Is Not Working.
Status in linux package in Ubuntu:
Triaged
Bug description:
Note: Link got mangled below and user attached the alsa info script
instead of result. Here is the link - https://alsa-
project.org/db/?f=386a2e1ef74ee1225064d66db94c69da608d9c8e
---
Original report
---
**Title:** Internal Microphone Not Working – HP Victus 16-e1xxx on
Ubuntu 24.04.2 (Realtek ALC245)
**Summary:**
The internal microphone on my HP Victus 16-e1xxx laptop does not work on Ubuntu 24.04.2 LTS, even though it's detected and shows as active. Everything works fine on Windows 11. I've tried all known firmware and configuration fixes.
---
**Laptop:**
* Manufacturer: HP
* Model: Victus by HP Laptop 16-e1xxx
* Audio Chipset: Realtek ALC245
* Kernel: `6.14.0-27-generic`
* Ubuntu Version: `24.04.2 LTS (Noble)`
* Mic works fine on: **Windows 11**
---
### **Commands and Outputs**
<details><summary><code>sudo dmidecode -t system</code></summary>
```
Manufacturer: HP
Product Name: Victus by HP Laptop 16-e1xxx
SKU Number: 374W1UA#ABL
Family: 103C_5335M7 HP VICTUS
```
</details>
<details><summary><code>lspci | grep -i audio</code></summary>
```
01:00.1 Audio device: NVIDIA Corporation Device 2291 (rev a1)
06:00.1 Audio device: AMD Rembrandt Radeon HD Audio Controller
06:00.5 Multimedia controller: AMD ACP/ACP3X/ACP6x Audio Coprocessor (rev 60)
06:00.6 Audio device: AMD Family 17h/19h HD Audio Controller
```
</details>
<details><summary><code>pactl list sources short</code></summary>
```
53 alsa_output.pci-0000_06_00.6.analog-stereo.monitor PipeWire s32le 2ch 48000Hz IDLE
54 alsa_input.pci-0000_06_00.6.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING
```
</details>
<details><summary><code>arecord -l</code></summary>
```
**** List of CAPTURE Hardware Devices ****
card 2: Generic_1 [HD-Audio Generic], device 0: ALC245 Analog [ALC245 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
```
</details>
<details><summary><code>arecord -f cd -D hw:2,0
test.wav</code></summary>
```
No sound is recorded. Playback is silent even though the file is created.
```
</details>
<details><summary><code>alsa-info.sh output</code></summary>
🔗 [https://alsa-
project.org/db/?f=386a2e1ef74ee1225064d66db94c69da608d9c8e](https://alsa-
project.org/db/?f=386a2e1ef74ee1225064d66db94c69da608d9c8e)
</details>
---
### **Troubleshooting Steps Already Tried**
✅ Installed latest firmware:
```bash
sudo apt install linux-firmware alsa-utils alsa-tools alsa-ucm-conf
```
✅ Reloaded ALSA:
```bash
sudo alsa force-reload
```
✅ Installed and ran `alsa-info.sh`
✅ Verified ports with:
```bash
pactl list sources | grep -A20 "Name:"
```
✅ Forced internal mic in WirePlumber:
```lua
-- /etc/wireplumber/main.lua.d/91-force-internal-mic.lua
alsa_monitor.rules = {
{
matches = { { { "node.name", "matches", "alsa_input.*analog-stereo" } }, },
apply_properties = {
["api.alsa.use-acp"] = true,
["api.acp.auto-profile"] = false,
["api.acp.auto-port"] = false,
["device.profile-set"] = "default",
["node.disabled"] = false,
["device.disabled"] = false,
},
},
}
```
✅ Boot options attempted:
```bash
snd-intel-dspcfg.dsp_driver=1
```
✅ Live USB test of Ubuntu 24.04.2 – still no mic input.
---
**Conclusion:**
Microphone is physically working on Windows 11. Detected under Ubuntu, but no sound is captured. Likely a kernel/driver or ACP/ALC245 firmware issue on Ubuntu 24.04 (kernel 6.14). Please assist or escalate upstream for a patch.
---
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC0: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC1: zakhmi-panne 2848 F.... wireplumber
/dev/snd/seq: zakhmi-panne 2836 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-08-02 (3 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: HP Victus by HP Laptop 16-e1xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=8abe9fda-ef3d-41ef-a039-86125efadfa9 ro snd-intel-dspcfg.dsp_driver=3 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-27.27~24.04.1-generic 6.14.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-27-generic N/A
linux-backports-modules-6.14.0-27-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.14
Tags: noble
Uname: Linux 6.14.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2025
dmi.bios.release: 15.26
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A21
dmi.board.vendor: HP
dmi.board.version: 19.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 19.79
dmi.modalias: dmi:bvnAMI:bvrF.26:bd04/22/2025:br15.26:efr19.79:svnHP:pnVictusbyHPLaptop16-e1xxx:pvr:rvnHP:rn8A21:rvr19.79:cvnHP:ct10:cvrChassisVersion:sku374W1UA#ABL:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e1xxx
dmi.product.sku: 374W1UA#ABL
dmi.sys.vendor: HP
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC0: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC1: zakhmi-panne 2848 F.... wireplumber
/dev/snd/seq: zakhmi-panne 2836 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-08-02 (3 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: HP Victus by HP Laptop 16-e1xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=8abe9fda-ef3d-41ef-a039-86125efadfa9 ro snd-intel-dspcfg.dsp_driver=3 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-27.27~24.04.1-generic 6.14.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-27-generic N/A
linux-backports-modules-6.14.0-27-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.14
Tags: noble
Uname: Linux 6.14.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2025
dmi.bios.release: 15.26
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A21
dmi.board.vendor: HP
dmi.board.version: 19.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 19.79
dmi.modalias: dmi:bvnAMI:bvrF.26:bd04/22/2025:br15.26:efr19.79:svnHP:pnVictusbyHPLaptop16-e1xxx:pvr:rvnHP:rn8A21:rvr19.79:cvnHP:ct10:cvrChassisVersion:sku374W1UA#ABL:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e1xxx
dmi.product.sku: 374W1UA#ABL
dmi.sys.vendor: HP
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC0: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC1: zakhmi-panne 2848 F.... wireplumber
/dev/snd/seq: zakhmi-panne 2836 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-08-02 (3 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: HP Victus by HP Laptop 16-e1xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=8abe9fda-ef3d-41ef-a039-86125efadfa9 ro snd-intel-dspcfg.dsp_driver=3 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-27.27~24.04.1-generic 6.14.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-27-generic N/A
linux-backports-modules-6.14.0-27-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.14
Tags: noble
Uname: Linux 6.14.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2025
dmi.bios.release: 15.26
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A21
dmi.board.vendor: HP
dmi.board.version: 19.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 19.79
dmi.modalias: dmi:bvnAMI:bvrF.26:bd04/22/2025:br15.26:efr19.79:svnHP:pnVictusbyHPLaptop16-e1xxx:pvr:rvnHP:rn8A21:rvr19.79:cvnHP:ct10:cvrChassisVersion:sku374W1UA#ABL:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e1xxx
dmi.product.sku: 374W1UA#ABL
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2119390/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2119390
Title:
My Mic Is Not Working.
Status in linux package in Ubuntu:
Triaged
Bug description:
Note: Link got mangled below and user attached the alsa info script
instead of result. Here is the link - https://alsa-
project.org/db/?f=386a2e1ef74ee1225064d66db94c69da608d9c8e
---
Original report
---
**Title:** Internal Microphone Not Working – HP Victus 16-e1xxx on
Ubuntu 24.04.2 (Realtek ALC245)
**Summary:**
The internal microphone on my HP Victus 16-e1xxx laptop does not work on Ubuntu 24.04.2 LTS, even though it's detected and shows as active. Everything works fine on Windows 11. I've tried all known firmware and configuration fixes.
---
**Laptop:**
* Manufacturer: HP
* Model: Victus by HP Laptop 16-e1xxx
* Audio Chipset: Realtek ALC245
* Kernel: `6.14.0-27-generic`
* Ubuntu Version: `24.04.2 LTS (Noble)`
* Mic works fine on: **Windows 11**
---
### **Commands and Outputs**
<details><summary><code>sudo dmidecode -t system</code></summary>
```
Manufacturer: HP
Product Name: Victus by HP Laptop 16-e1xxx
SKU Number: 374W1UA#ABL
Family: 103C_5335M7 HP VICTUS
```
</details>
<details><summary><code>lspci | grep -i audio</code></summary>
```
01:00.1 Audio device: NVIDIA Corporation Device 2291 (rev a1)
06:00.1 Audio device: AMD Rembrandt Radeon HD Audio Controller
06:00.5 Multimedia controller: AMD ACP/ACP3X/ACP6x Audio Coprocessor (rev 60)
06:00.6 Audio device: AMD Family 17h/19h HD Audio Controller
```
</details>
<details><summary><code>pactl list sources short</code></summary>
```
53 alsa_output.pci-0000_06_00.6.analog-stereo.monitor PipeWire s32le 2ch 48000Hz IDLE
54 alsa_input.pci-0000_06_00.6.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING
```
</details>
<details><summary><code>arecord -l</code></summary>
```
**** List of CAPTURE Hardware Devices ****
card 2: Generic_1 [HD-Audio Generic], device 0: ALC245 Analog [ALC245 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
```
</details>
<details><summary><code>arecord -f cd -D hw:2,0
test.wav</code></summary>
```
No sound is recorded. Playback is silent even though the file is created.
```
</details>
<details><summary><code>alsa-info.sh output</code></summary>
🔗 [https://alsa-
project.org/db/?f=386a2e1ef74ee1225064d66db94c69da608d9c8e](https://alsa-
project.org/db/?f=386a2e1ef74ee1225064d66db94c69da608d9c8e)
</details>
---
### **Troubleshooting Steps Already Tried**
✅ Installed latest firmware:
```bash
sudo apt install linux-firmware alsa-utils alsa-tools alsa-ucm-conf
```
✅ Reloaded ALSA:
```bash
sudo alsa force-reload
```
✅ Installed and ran `alsa-info.sh`
✅ Verified ports with:
```bash
pactl list sources | grep -A20 "Name:"
```
✅ Forced internal mic in WirePlumber:
```lua
-- /etc/wireplumber/main.lua.d/91-force-internal-mic.lua
alsa_monitor.rules = {
{
matches = { { { "node.name", "matches", "alsa_input.*analog-stereo" } }, },
apply_properties = {
["api.alsa.use-acp"] = true,
["api.acp.auto-profile"] = false,
["api.acp.auto-port"] = false,
["device.profile-set"] = "default",
["node.disabled"] = false,
["device.disabled"] = false,
},
},
}
```
✅ Boot options attempted:
```bash
snd-intel-dspcfg.dsp_driver=1
```
✅ Live USB test of Ubuntu 24.04.2 – still no mic input.
---
**Conclusion:**
Microphone is physically working on Windows 11. Detected under Ubuntu, but no sound is captured. Likely a kernel/driver or ACP/ALC245 firmware issue on Ubuntu 24.04 (kernel 6.14). Please assist or escalate upstream for a patch.
---
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC0: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC1: zakhmi-panne 2848 F.... wireplumber
/dev/snd/seq: zakhmi-panne 2836 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-08-02 (3 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: HP Victus by HP Laptop 16-e1xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=8abe9fda-ef3d-41ef-a039-86125efadfa9 ro snd-intel-dspcfg.dsp_driver=3 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-27.27~24.04.1-generic 6.14.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-27-generic N/A
linux-backports-modules-6.14.0-27-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.14
Tags: noble
Uname: Linux 6.14.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2025
dmi.bios.release: 15.26
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A21
dmi.board.vendor: HP
dmi.board.version: 19.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 19.79
dmi.modalias: dmi:bvnAMI:bvrF.26:bd04/22/2025:br15.26:efr19.79:svnHP:pnVictusbyHPLaptop16-e1xxx:pvr:rvnHP:rn8A21:rvr19.79:cvnHP:ct10:cvrChassisVersion:sku374W1UA#ABL:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e1xxx
dmi.product.sku: 374W1UA#ABL
dmi.sys.vendor: HP
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC0: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC1: zakhmi-panne 2848 F.... wireplumber
/dev/snd/seq: zakhmi-panne 2836 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-08-02 (3 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: HP Victus by HP Laptop 16-e1xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=8abe9fda-ef3d-41ef-a039-86125efadfa9 ro snd-intel-dspcfg.dsp_driver=3 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-27.27~24.04.1-generic 6.14.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-27-generic N/A
linux-backports-modules-6.14.0-27-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.14
Tags: noble
Uname: Linux 6.14.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2025
dmi.bios.release: 15.26
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A21
dmi.board.vendor: HP
dmi.board.version: 19.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 19.79
dmi.modalias: dmi:bvnAMI:bvrF.26:bd04/22/2025:br15.26:efr19.79:svnHP:pnVictusbyHPLaptop16-e1xxx:pvr:rvnHP:rn8A21:rvr19.79:cvnHP:ct10:cvrChassisVersion:sku374W1UA#ABL:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e1xxx
dmi.product.sku: 374W1UA#ABL
dmi.sys.vendor: HP
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC0: zakhmi-panne 2848 F.... wireplumber
/dev/snd/controlC1: zakhmi-panne 2848 F.... wireplumber
/dev/snd/seq: zakhmi-panne 2836 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-08-02 (3 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: HP Victus by HP Laptop 16-e1xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=8abe9fda-ef3d-41ef-a039-86125efadfa9 ro snd-intel-dspcfg.dsp_driver=3 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-27.27~24.04.1-generic 6.14.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.14.0-27-generic N/A
linux-backports-modules-6.14.0-27-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.14
Tags: noble
Uname: Linux 6.14.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/22/2025
dmi.bios.release: 15.26
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A21
dmi.board.vendor: HP
dmi.board.version: 19.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 19.79
dmi.modalias: dmi:bvnAMI:bvrF.26:bd04/22/2025:br15.26:efr19.79:svnHP:pnVictusbyHPLaptop16-e1xxx:pvr:rvnHP:rn8A21:rvr19.79:cvnHP:ct10:cvrChassisVersion:sku374W1UA#ABL:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e1xxx
dmi.product.sku: 374W1UA#ABL
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2119390/+subscriptions
пятница
[Bug 2110949] Re: No output to USB-C monitor after logging in with the laptop closed
[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 subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2110949
Title:
No output to USB-C monitor after logging in with the laptop closed
Status in linux package in Ubuntu:
Expired
Status in mutter package in Ubuntu:
Expired
Bug description:
1) Description: Ubuntu 24.04.2 LTS
Release: 24.04
2) not sure which package this applies to
3) I have two monitors connected to a laptop in clamshell mode. When I
log out of my profile, I see my background wallpaper blurred, and my
username on the primary monitor that I have setup, as expected.
4) However, when rebooting this layout is ditched for some reason:
- I see a gray background (not the main problem)
- the username/login page is on the secondary monitor
- it is the wrong orientation ( the secondary monitor is setup to be portrait mode) but the login appears horizontally, seeming quite unpolished
- the scale is completely wrong.
Then upon logging in, there is no display output at all, the monitors
detect no USB-C input.
The workaround (which is quite cumbersome) is to disconnect the USB-C
cable from the laptop, remove the laptop from the dock, and open up it
up, log in, connect the usb-c cable so that it recognises the
configuration, and then close the laptop and put it back into the
dock.
The monitor configuration is:
Laptop -> USB-C -> Dell P2224HE (primary, landscape) -> Display Port Daisy Chain -> Dell P2224HE (secondary, portrait).
When booting the same configuration in Windows, it seems to remember
the layout somehow so that the username/login screen is shown on the
primary monitor in the correct orientation with some splash screen.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-60.63-generic 6.8.12
Uname: Linux 6.8.0-60-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.0000.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.144.03 Mon Dec 30 17:44:08 UTC 2024
GCC version:
ApportVersion: 2.28.1-0ubuntu3.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 16 09:58:11 2025
DistUpgraded: 2025-03-29 17:42:36,771 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:86e8]
NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Ti Mobile] [103c:86e8]
InstallationDate: Installed on 2024-02-27 (444 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
MachineType: HP HP Spectre x360 Convertible 15-eb0xxx
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-60-generic root=UUID=73058d45-f5f8-41c9-bac3-b6a3bc48d9b8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2025-03-29 (48 days ago)
dmi.bios.date: 11/02/2022
dmi.bios.release: 15.16
dmi.bios.vendor: AMI
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86E8
dmi.board.vendor: HP
dmi.board.version: 01.77
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.77
dmi.modalias: dmi:bvnAMI:bvrF.16:bd11/02/2022:br15.16:efr1.77:svnHP:pnHPSpectrex360Convertible15-eb0xxx:pvr:rvnHP:rn86E8:rvr01.77:cvnHP:ct31:cvrChassisVersion:sku2T980EA#ABU:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-eb0xxx
dmi.product.sku: 2T980EA#ABU
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.122-1~ubuntu0.24.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.04.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.3
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/linux/+bug/2110949/+subscriptions
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2110949
Title:
No output to USB-C monitor after logging in with the laptop closed
Status in linux package in Ubuntu:
Expired
Status in mutter package in Ubuntu:
Expired
Bug description:
1) Description: Ubuntu 24.04.2 LTS
Release: 24.04
2) not sure which package this applies to
3) I have two monitors connected to a laptop in clamshell mode. When I
log out of my profile, I see my background wallpaper blurred, and my
username on the primary monitor that I have setup, as expected.
4) However, when rebooting this layout is ditched for some reason:
- I see a gray background (not the main problem)
- the username/login page is on the secondary monitor
- it is the wrong orientation ( the secondary monitor is setup to be portrait mode) but the login appears horizontally, seeming quite unpolished
- the scale is completely wrong.
Then upon logging in, there is no display output at all, the monitors
detect no USB-C input.
The workaround (which is quite cumbersome) is to disconnect the USB-C
cable from the laptop, remove the laptop from the dock, and open up it
up, log in, connect the usb-c cable so that it recognises the
configuration, and then close the laptop and put it back into the
dock.
The monitor configuration is:
Laptop -> USB-C -> Dell P2224HE (primary, landscape) -> Display Port Daisy Chain -> Dell P2224HE (secondary, portrait).
When booting the same configuration in Windows, it seems to remember
the layout somehow so that the username/login screen is shown on the
primary monitor in the correct orientation with some splash screen.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-60.63-generic 6.8.12
Uname: Linux 6.8.0-60-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.0000.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.144.03 Mon Dec 30 17:44:08 UTC 2024
GCC version:
ApportVersion: 2.28.1-0ubuntu3.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 16 09:58:11 2025
DistUpgraded: 2025-03-29 17:42:36,771 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:86e8]
NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Ti Mobile] [103c:86e8]
InstallationDate: Installed on 2024-02-27 (444 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
MachineType: HP HP Spectre x360 Convertible 15-eb0xxx
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-60-generic root=UUID=73058d45-f5f8-41c9-bac3-b6a3bc48d9b8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2025-03-29 (48 days ago)
dmi.bios.date: 11/02/2022
dmi.bios.release: 15.16
dmi.bios.vendor: AMI
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86E8
dmi.board.vendor: HP
dmi.board.version: 01.77
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.77
dmi.modalias: dmi:bvnAMI:bvrF.16:bd11/02/2022:br15.16:efr1.77:svnHP:pnHPSpectrex360Convertible15-eb0xxx:pvr:rvnHP:rn86E8:rvr01.77:cvnHP:ct31:cvrChassisVersion:sku2T980EA#ABU:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-eb0xxx
dmi.product.sku: 2T980EA#ABU
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.122-1~ubuntu0.24.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.04.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.3
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/linux/+bug/2110949/+subscriptions
[Bug 2110949] Re: No output to USB-C monitor after logging in with the laptop closed
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2110949
Title:
No output to USB-C monitor after logging in with the laptop closed
Status in linux package in Ubuntu:
Expired
Status in mutter package in Ubuntu:
Expired
Bug description:
1) Description: Ubuntu 24.04.2 LTS
Release: 24.04
2) not sure which package this applies to
3) I have two monitors connected to a laptop in clamshell mode. When I
log out of my profile, I see my background wallpaper blurred, and my
username on the primary monitor that I have setup, as expected.
4) However, when rebooting this layout is ditched for some reason:
- I see a gray background (not the main problem)
- the username/login page is on the secondary monitor
- it is the wrong orientation ( the secondary monitor is setup to be portrait mode) but the login appears horizontally, seeming quite unpolished
- the scale is completely wrong.
Then upon logging in, there is no display output at all, the monitors
detect no USB-C input.
The workaround (which is quite cumbersome) is to disconnect the USB-C
cable from the laptop, remove the laptop from the dock, and open up it
up, log in, connect the usb-c cable so that it recognises the
configuration, and then close the laptop and put it back into the
dock.
The monitor configuration is:
Laptop -> USB-C -> Dell P2224HE (primary, landscape) -> Display Port Daisy Chain -> Dell P2224HE (secondary, portrait).
When booting the same configuration in Windows, it seems to remember
the layout somehow so that the username/login screen is shown on the
primary monitor in the correct orientation with some splash screen.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-60.63-generic 6.8.12
Uname: Linux 6.8.0-60-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.0000.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.144.03 Mon Dec 30 17:44:08 UTC 2024
GCC version:
ApportVersion: 2.28.1-0ubuntu3.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 16 09:58:11 2025
DistUpgraded: 2025-03-29 17:42:36,771 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:86e8]
NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Ti Mobile] [103c:86e8]
InstallationDate: Installed on 2024-02-27 (444 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
MachineType: HP HP Spectre x360 Convertible 15-eb0xxx
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-60-generic root=UUID=73058d45-f5f8-41c9-bac3-b6a3bc48d9b8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2025-03-29 (48 days ago)
dmi.bios.date: 11/02/2022
dmi.bios.release: 15.16
dmi.bios.vendor: AMI
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86E8
dmi.board.vendor: HP
dmi.board.version: 01.77
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.77
dmi.modalias: dmi:bvnAMI:bvrF.16:bd11/02/2022:br15.16:efr1.77:svnHP:pnHPSpectrex360Convertible15-eb0xxx:pvr:rvnHP:rn86E8:rvr01.77:cvnHP:ct31:cvrChassisVersion:sku2T980EA#ABU:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-eb0xxx
dmi.product.sku: 2T980EA#ABU
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.122-1~ubuntu0.24.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.04.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.3
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/linux/+bug/2110949/+subscriptions
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2110949
Title:
No output to USB-C monitor after logging in with the laptop closed
Status in linux package in Ubuntu:
Expired
Status in mutter package in Ubuntu:
Expired
Bug description:
1) Description: Ubuntu 24.04.2 LTS
Release: 24.04
2) not sure which package this applies to
3) I have two monitors connected to a laptop in clamshell mode. When I
log out of my profile, I see my background wallpaper blurred, and my
username on the primary monitor that I have setup, as expected.
4) However, when rebooting this layout is ditched for some reason:
- I see a gray background (not the main problem)
- the username/login page is on the secondary monitor
- it is the wrong orientation ( the secondary monitor is setup to be portrait mode) but the login appears horizontally, seeming quite unpolished
- the scale is completely wrong.
Then upon logging in, there is no display output at all, the monitors
detect no USB-C input.
The workaround (which is quite cumbersome) is to disconnect the USB-C
cable from the laptop, remove the laptop from the dock, and open up it
up, log in, connect the usb-c cable so that it recognises the
configuration, and then close the laptop and put it back into the
dock.
The monitor configuration is:
Laptop -> USB-C -> Dell P2224HE (primary, landscape) -> Display Port Daisy Chain -> Dell P2224HE (secondary, portrait).
When booting the same configuration in Windows, it seems to remember
the layout somehow so that the username/login screen is shown on the
primary monitor in the correct orientation with some splash screen.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-60.63-generic 6.8.12
Uname: Linux 6.8.0-60-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.0000.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.144.03 Mon Dec 30 17:44:08 UTC 2024
GCC version:
ApportVersion: 2.28.1-0ubuntu3.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 16 09:58:11 2025
DistUpgraded: 2025-03-29 17:42:36,771 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:86e8]
NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Ti Mobile] [103c:86e8]
InstallationDate: Installed on 2024-02-27 (444 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
MachineType: HP HP Spectre x360 Convertible 15-eb0xxx
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-60-generic root=UUID=73058d45-f5f8-41c9-bac3-b6a3bc48d9b8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2025-03-29 (48 days ago)
dmi.bios.date: 11/02/2022
dmi.bios.release: 15.16
dmi.bios.vendor: AMI
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86E8
dmi.board.vendor: HP
dmi.board.version: 01.77
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.77
dmi.modalias: dmi:bvnAMI:bvrF.16:bd11/02/2022:br15.16:efr1.77:svnHP:pnHPSpectrex360Convertible15-eb0xxx:pvr:rvnHP:rn86E8:rvr01.77:cvnHP:ct31:cvrChassisVersion:sku2T980EA#ABU:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-eb0xxx
dmi.product.sku: 2T980EA#ABU
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.122-1~ubuntu0.24.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.04.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.3
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/linux/+bug/2110949/+subscriptions
[Bug 2120330] Re: Incorrect backport for CVE-2025-21861 causes kernel hangs
Hi Matthew,
Thanks for getting this fix together so quickly. I've taken it for a spin on some of my machines. I can confirm that the test that were getting stuck in the 1021 kernel now run to completion in 1022.
Thanks again,
-K
** Tags added: verification-done-noble-linux-azure
** Tags removed: verification-done-noble-linux-azure
** Tags added: verification-done-noble-linux-azure-nvidia
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2120330
Title:
Incorrect backport for CVE-2025-21861 causes kernel hangs
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2120330
[Impact]
The patch for CVE-2025-21861 was incorrectly backported to the noble 6.8
kernel, leading to hangs when freeing device memory.
commit 41cddf83d8b00f29fd105e7a0777366edc69a5cf
Author: David Hildenbrand <david@redhat.com>
Date: Mon Feb 10 17:13:17 2025 +0100
Subject: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41cddf83d8b00f29fd105e7a0777366edc69a5cf
ubuntu-noble: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=3858edb1146374f3240d1ec769ba857186531b17
An incorrect backport was performed, causing the old page to be placed
back instead of the new page, e.g.:
src = page_folio(page);
dst = page_folio(newpage);
+ if (!is_zone_device_page(page))
+ putback_lru_page(page);
when in 41cddf83d8b00f29fd105e7a0777366edc69a5cf we have:
+ if (!folio_is_zone_device(dst))
+ folio_add_lru(dst);
in which case, we should really have had the backport as:
+ if (!folio_is_zone_device(newpage))
+ folio_add_lru(newpage);
This keeps references alive to the old memory pages, preventing them from being
released and freed.
Stack traces of stuck processes:
ID: 871438 TASK: ffff007d4d668200 CPU: 95 COMMAND: "nvbandwidth"
#0 [ffff80010e8ef840] __switch_to at ffffc0f22798c550
#1 [ffff80010e8ef8a0] __schedule at ffffc0f22798c89c
#2 [ffff80010e8ef900] schedule at ffffc0f22798cd40
#3 [ffff80010e8ef930] schedule_preempt_disabled at ffffc0f22798d388
#4 [ffff80010e8ef9c0] rwsem_down_write_slowpath at ffffc0f227990dc8
#5 [ffff80010e8efa20] down_write at ffffc0f2279912d0
#6 [ffff80010e8efaa0] uvm_va_space_mm_shutdown at ffffc0f1c2a451ec [nvidia_uvm]
#7 [ffff80010e8efb00] uvm_va_space_mm_unregister at ffffc0f1c2a457a0 [nvidia_uvm]
#8 [ffff80010e8efb30] uvm_release at ffffc0f1c2a226d4 [nvidia_uvm]
#9 [ffff80010e8efc00] uvm_release_entry.part.0 at ffffc0f1c2a227dc [nvidia_uvm]
#10 [ffff80010e8efc20] uvm_release_entry at ffffc0f1c2a22850 [nvidia_uvm]
#11 [ffff80010e8efc30] __fput at ffffc0f2269a5760
#12 [ffff80010e8efc70] ____fput at ffffc0f2269a5a80
#13 [ffff80010e8efc80] task_work_run at ffffc0f2265ceedc
#14 [ffff80010e8efcc0] do_exit at ffffc0f2265a0bc8
#15 [ffff80010e8efcf0] do_group_exit at ffffc0f2265a0fec
#16 [ffff80010e8efd50] get_signal at ffffc0f2265b8750
#17 [ffff80010e8efe10] do_signal at ffffc0f22650166c
#18 [ffff80010e8efe40] do_notify_resume at ffffc0f2265018f0
#19 [ffff80010e8efe70] el0_interrupt at ffffc0f227985564
#20 [ffff80010e8efe90] __el0_irq_handler_common at ffffc0f2279855f0
#21 [ffff80010e8efea0] el0t_64_irq_handler at ffffc0f227986080
#22 [ffff80010e8effe0] el0t_64_irq at ffffc0f2264f17fc
PID: 871467 TASK: ffff007f6aa66000 CPU: 66 COMMAND: "UVM GPU4 BH"
#0 [ffff80015ddef580] __switch_to at ffffc0f22798c550
#1 [ffff80015ddef5e0] __schedule at ffffc0f22798c89c
#2 [ffff80015ddef640] schedule at ffffc0f22798cd40
#3 [ffff80015ddef670] io_schedule at ffffc0f22798cec4
#4 [ffff80015ddef6e0] migration_entry_wait_on_locked at ffffc0f22686e3f0
#5 [ffff80015ddef740] migration_entry_wait at ffffc0f22695a6d4
#6 [ffff80015ddef750] do_swap_page at ffffc0f2268d6378
#7 [ffff80015ddef7d0] handle_pte_fault at ffffc0f2268da688
#8 [ffff80015ddef870] __handle_mm_fault at ffffc0f2268da7f8
#9 [ffff80015ddef8b0] handle_mm_fault at ffffc0f2268dab48
#10 [ffff80015ddef910] handle_fault at ffffc0f1c2aace18 [nvidia_uvm]
#11 [ffff80015ddef950] uvm_populate_pageable_vma at ffffc0f1c2aacf24 [nvidia_uvm]
#12 [ffff80015ddef990] migrate_pageable_vma_populate_mask at ffffc0f1c2aad8c0 [nvidia_uvm]
#13 [ffff80015ddefab0] uvm_migrate_pageable at ffffc0f1c2ab0294 [nvidia_uvm]
#14 [ffff80015ddefb90] service_ats_requests at ffffc0f1c2abf828 [nvidia_uvm]
#15 [ffff80015ddefbb0] uvm_ats_service_faults at ffffc0f1c2ac02f0 [nvidia_uvm]
#16 [ffff80015ddefd40] uvm_parent_gpu_service_non_replayable_fault_buffer at ffffc0f1c2a82e00 [nvidia_uvm]
#17 [ffff80015ddefda0] non_replayable_faults_isr_bottom_half at ffffc0f1c2a3c3e4 [nvidia_uvm]
#18 [ffff80015ddefe00] non_replayable_faults_isr_bottom_half_entry at ffffc0f1c2a3c590 [nvidia_uvm]
#19 [ffff80015ddefe20] _main_loop at ffffc0f1c2a207c8 [nvidia_uvm]
#20 [ffff80015ddefe70] kthread at ffffc0f2265d40dc
There is no workaround.
[Fix]
To make things less confusing, revert the incorrect backport, and backport
"mm: migrate_device: use more folio in migrate_device_finalize()" to use the
new upstream notations, and correctly backport "mm/migrate_device: don't add
folio to be freed to LRU in migrate_device_finalize()". This approach was
suggested and tested by Krister Johansen, and I think it is reasonable.
commit 58bf8c2bf47550bc94fea9cafd2bc7304d97102c
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date: Mon Aug 26 14:58:12 2024 +0800
Subject: mm: migrate_device: use more folio in migrate_device_finalize()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=58bf8c2bf47550bc94fea9cafd2bc7304d97102c
commit 41cddf83d8b00f29fd105e7a0777366edc69a5cf
Author: David Hildenbrand <david@redhat.com>
Date: Mon Feb 10 17:13:17 2025 +0100
Subject: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41cddf83d8b00f29fd105e7a0777366edc69a5cf
The first patch landed in 6.12-rc1 and the second patch in 6.14-rc4. Both are
in plucky.
[Testcase]
There are a few ways to trigger the issue.
You can run the hmm selftests. Note, you need to build a new kernel and set
CONFIG_TEST_HMM=m first.
1) Check out a kernel git tree
2) cd tools/testing/selftests/mm/
3) make
4) sudo ./test_hmm.sh
You can also run nvidia tests like nvbandwidth, if your system has a Nvidia GPU:
https://github.com/NVIDIA/nvbandwidth
$ git clone https://github.com/NVIDIA/nvbandwidth.git
$ cd nvbandwidth
$ sudo ./debian_install.sh
$ sudo ./nvbandwidth
A test package is available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf416039-test
If you install it, and run the hmm selftests, it should no longer
hang.
[Where problems can occur]
This changes some core mm code for device memory from standard pages to using
folios, and carries some additional risk because of this.
If a regression were to occur, it would primarily affect users of devices with
internal memory, such as graphics cards, and quite possibly high end network
cards.
The largest userbase affected by this regression is nvidia users, so it really
would be a bad idea to release with the broken implementation, and instead, to
respin and release with the fixed implementation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2120330/+subscriptions
Thanks for getting this fix together so quickly. I've taken it for a spin on some of my machines. I can confirm that the test that were getting stuck in the 1021 kernel now run to completion in 1022.
Thanks again,
-K
** Tags added: verification-done-noble-linux-azure
** Tags removed: verification-done-noble-linux-azure
** Tags added: verification-done-noble-linux-azure-nvidia
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2120330
Title:
Incorrect backport for CVE-2025-21861 causes kernel hangs
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2120330
[Impact]
The patch for CVE-2025-21861 was incorrectly backported to the noble 6.8
kernel, leading to hangs when freeing device memory.
commit 41cddf83d8b00f29fd105e7a0777366edc69a5cf
Author: David Hildenbrand <david@redhat.com>
Date: Mon Feb 10 17:13:17 2025 +0100
Subject: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41cddf83d8b00f29fd105e7a0777366edc69a5cf
ubuntu-noble: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=3858edb1146374f3240d1ec769ba857186531b17
An incorrect backport was performed, causing the old page to be placed
back instead of the new page, e.g.:
src = page_folio(page);
dst = page_folio(newpage);
+ if (!is_zone_device_page(page))
+ putback_lru_page(page);
when in 41cddf83d8b00f29fd105e7a0777366edc69a5cf we have:
+ if (!folio_is_zone_device(dst))
+ folio_add_lru(dst);
in which case, we should really have had the backport as:
+ if (!folio_is_zone_device(newpage))
+ folio_add_lru(newpage);
This keeps references alive to the old memory pages, preventing them from being
released and freed.
Stack traces of stuck processes:
ID: 871438 TASK: ffff007d4d668200 CPU: 95 COMMAND: "nvbandwidth"
#0 [ffff80010e8ef840] __switch_to at ffffc0f22798c550
#1 [ffff80010e8ef8a0] __schedule at ffffc0f22798c89c
#2 [ffff80010e8ef900] schedule at ffffc0f22798cd40
#3 [ffff80010e8ef930] schedule_preempt_disabled at ffffc0f22798d388
#4 [ffff80010e8ef9c0] rwsem_down_write_slowpath at ffffc0f227990dc8
#5 [ffff80010e8efa20] down_write at ffffc0f2279912d0
#6 [ffff80010e8efaa0] uvm_va_space_mm_shutdown at ffffc0f1c2a451ec [nvidia_uvm]
#7 [ffff80010e8efb00] uvm_va_space_mm_unregister at ffffc0f1c2a457a0 [nvidia_uvm]
#8 [ffff80010e8efb30] uvm_release at ffffc0f1c2a226d4 [nvidia_uvm]
#9 [ffff80010e8efc00] uvm_release_entry.part.0 at ffffc0f1c2a227dc [nvidia_uvm]
#10 [ffff80010e8efc20] uvm_release_entry at ffffc0f1c2a22850 [nvidia_uvm]
#11 [ffff80010e8efc30] __fput at ffffc0f2269a5760
#12 [ffff80010e8efc70] ____fput at ffffc0f2269a5a80
#13 [ffff80010e8efc80] task_work_run at ffffc0f2265ceedc
#14 [ffff80010e8efcc0] do_exit at ffffc0f2265a0bc8
#15 [ffff80010e8efcf0] do_group_exit at ffffc0f2265a0fec
#16 [ffff80010e8efd50] get_signal at ffffc0f2265b8750
#17 [ffff80010e8efe10] do_signal at ffffc0f22650166c
#18 [ffff80010e8efe40] do_notify_resume at ffffc0f2265018f0
#19 [ffff80010e8efe70] el0_interrupt at ffffc0f227985564
#20 [ffff80010e8efe90] __el0_irq_handler_common at ffffc0f2279855f0
#21 [ffff80010e8efea0] el0t_64_irq_handler at ffffc0f227986080
#22 [ffff80010e8effe0] el0t_64_irq at ffffc0f2264f17fc
PID: 871467 TASK: ffff007f6aa66000 CPU: 66 COMMAND: "UVM GPU4 BH"
#0 [ffff80015ddef580] __switch_to at ffffc0f22798c550
#1 [ffff80015ddef5e0] __schedule at ffffc0f22798c89c
#2 [ffff80015ddef640] schedule at ffffc0f22798cd40
#3 [ffff80015ddef670] io_schedule at ffffc0f22798cec4
#4 [ffff80015ddef6e0] migration_entry_wait_on_locked at ffffc0f22686e3f0
#5 [ffff80015ddef740] migration_entry_wait at ffffc0f22695a6d4
#6 [ffff80015ddef750] do_swap_page at ffffc0f2268d6378
#7 [ffff80015ddef7d0] handle_pte_fault at ffffc0f2268da688
#8 [ffff80015ddef870] __handle_mm_fault at ffffc0f2268da7f8
#9 [ffff80015ddef8b0] handle_mm_fault at ffffc0f2268dab48
#10 [ffff80015ddef910] handle_fault at ffffc0f1c2aace18 [nvidia_uvm]
#11 [ffff80015ddef950] uvm_populate_pageable_vma at ffffc0f1c2aacf24 [nvidia_uvm]
#12 [ffff80015ddef990] migrate_pageable_vma_populate_mask at ffffc0f1c2aad8c0 [nvidia_uvm]
#13 [ffff80015ddefab0] uvm_migrate_pageable at ffffc0f1c2ab0294 [nvidia_uvm]
#14 [ffff80015ddefb90] service_ats_requests at ffffc0f1c2abf828 [nvidia_uvm]
#15 [ffff80015ddefbb0] uvm_ats_service_faults at ffffc0f1c2ac02f0 [nvidia_uvm]
#16 [ffff80015ddefd40] uvm_parent_gpu_service_non_replayable_fault_buffer at ffffc0f1c2a82e00 [nvidia_uvm]
#17 [ffff80015ddefda0] non_replayable_faults_isr_bottom_half at ffffc0f1c2a3c3e4 [nvidia_uvm]
#18 [ffff80015ddefe00] non_replayable_faults_isr_bottom_half_entry at ffffc0f1c2a3c590 [nvidia_uvm]
#19 [ffff80015ddefe20] _main_loop at ffffc0f1c2a207c8 [nvidia_uvm]
#20 [ffff80015ddefe70] kthread at ffffc0f2265d40dc
There is no workaround.
[Fix]
To make things less confusing, revert the incorrect backport, and backport
"mm: migrate_device: use more folio in migrate_device_finalize()" to use the
new upstream notations, and correctly backport "mm/migrate_device: don't add
folio to be freed to LRU in migrate_device_finalize()". This approach was
suggested and tested by Krister Johansen, and I think it is reasonable.
commit 58bf8c2bf47550bc94fea9cafd2bc7304d97102c
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date: Mon Aug 26 14:58:12 2024 +0800
Subject: mm: migrate_device: use more folio in migrate_device_finalize()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=58bf8c2bf47550bc94fea9cafd2bc7304d97102c
commit 41cddf83d8b00f29fd105e7a0777366edc69a5cf
Author: David Hildenbrand <david@redhat.com>
Date: Mon Feb 10 17:13:17 2025 +0100
Subject: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41cddf83d8b00f29fd105e7a0777366edc69a5cf
The first patch landed in 6.12-rc1 and the second patch in 6.14-rc4. Both are
in plucky.
[Testcase]
There are a few ways to trigger the issue.
You can run the hmm selftests. Note, you need to build a new kernel and set
CONFIG_TEST_HMM=m first.
1) Check out a kernel git tree
2) cd tools/testing/selftests/mm/
3) make
4) sudo ./test_hmm.sh
You can also run nvidia tests like nvbandwidth, if your system has a Nvidia GPU:
https://github.com/NVIDIA/nvbandwidth
$ git clone https://github.com/NVIDIA/nvbandwidth.git
$ cd nvbandwidth
$ sudo ./debian_install.sh
$ sudo ./nvbandwidth
A test package is available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf416039-test
If you install it, and run the hmm selftests, it should no longer
hang.
[Where problems can occur]
This changes some core mm code for device memory from standard pages to using
folios, and carries some additional risk because of this.
If a regression were to occur, it would primarily affect users of devices with
internal memory, such as graphics cards, and quite possibly high end network
cards.
The largest userbase affected by this regression is nvidia users, so it really
would be a bad idea to release with the broken implementation, and instead, to
respin and release with the fixed implementation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2120330/+subscriptions
[Bug 2120729] Re: package linux-headers-6.14.0-28-generic 6.14.0-28.28 failed to install/upgrade: installed linux-headers-6.14.0-28-generic package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2080624 ***
https://bugs.launchpad.net/bugs/2080624
My apologies. I didn't notice you were running Ubuntu 25.04/plucky. In
that case, the 470 driver is unavailable.
** Package changed: linux (Ubuntu) => ubuntu
** Tags removed: kernel-daily-bug
** Package changed: ubuntu => nvidia-graphics-drivers-470 (Ubuntu)
** This bug has been marked a duplicate of bug 2080624
Remove from oracular, EOL upstream
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2120729
Title:
package linux-headers-6.14.0-28-generic 6.14.0-28.28 failed to
install/upgrade: installed linux-headers-6.14.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Bug description:
Just installed on a clean system, I suspect I have a low end but false
(chineese) NVIDIA adapter. Not good.
ProblemType: Package
DistroRelease: Ubuntu 25.04
Package: linux-headers-6.14.0-28-generic 6.14.0-28.28
ProcVersionSignature: Ubuntu 6.14.0-27.27-generic 6.14.6
Uname: Linux 6.14.0-27-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: ivan 3206 F.... wireplumber
/dev/snd/controlC0: ivan 3206 F.... wireplumber
/dev/snd/seq: ivan 3201 F.... pipewire
CasperMD5CheckResult: pass
Date: Fri Aug 15 20:26:12 2025
ErrorMessage: installed linux-headers-6.14.0-28-generic package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-11-28 (260 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
IwDevWlp3s0Link: Not connected.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP ProDesk 400 G3 SFF
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=67276513-3be0-49fe-86f6-941251270338 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
Python3Details: /usr/bin/python3.13, Python 3.13.3, python3-minimal, 3.13.3-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.14.0-28-generic 6.14.0-28.28 failed to install/upgrade: installed linux-headers-6.14.0-28-generic package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to plucky on 2025-08-09 (6 days ago)
dmi.bios.date: 04/28/2020
dmi.bios.release: 2.47
dmi.bios.vendor: HP
dmi.bios.version: N03 Ver. 02.47
dmi.board.name: 8062
dmi.board.vendor: HP
dmi.board.version: KBC Version 05.39
dmi.chassis.type: 4
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 5.57
dmi.modalias: dmi:bvnHP:bvrN03Ver.02.47:bd04/28/2020:br2.47:efr5.57:svnHP:pnHPProDesk400G3SFF:pvr:rvnHP:rn8062:rvrKBCVersion05.39:cvnHP:ct4:cvr:skuN4P96AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 400 G3 SFF
dmi.product.sku: N4P96AV
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2120729/+subscriptions
https://bugs.launchpad.net/bugs/2080624
My apologies. I didn't notice you were running Ubuntu 25.04/plucky. In
that case, the 470 driver is unavailable.
** Package changed: linux (Ubuntu) => ubuntu
** Tags removed: kernel-daily-bug
** Package changed: ubuntu => nvidia-graphics-drivers-470 (Ubuntu)
** This bug has been marked a duplicate of bug 2080624
Remove from oracular, EOL upstream
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2120729
Title:
package linux-headers-6.14.0-28-generic 6.14.0-28.28 failed to
install/upgrade: installed linux-headers-6.14.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Bug description:
Just installed on a clean system, I suspect I have a low end but false
(chineese) NVIDIA adapter. Not good.
ProblemType: Package
DistroRelease: Ubuntu 25.04
Package: linux-headers-6.14.0-28-generic 6.14.0-28.28
ProcVersionSignature: Ubuntu 6.14.0-27.27-generic 6.14.6
Uname: Linux 6.14.0-27-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: ivan 3206 F.... wireplumber
/dev/snd/controlC0: ivan 3206 F.... wireplumber
/dev/snd/seq: ivan 3201 F.... pipewire
CasperMD5CheckResult: pass
Date: Fri Aug 15 20:26:12 2025
ErrorMessage: installed linux-headers-6.14.0-28-generic package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-11-28 (260 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
IwDevWlp3s0Link: Not connected.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP ProDesk 400 G3 SFF
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-27-generic root=UUID=67276513-3be0-49fe-86f6-941251270338 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
Python3Details: /usr/bin/python3.13, Python 3.13.3, python3-minimal, 3.13.3-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.14.0-28-generic 6.14.0-28.28 failed to install/upgrade: installed linux-headers-6.14.0-28-generic package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to plucky on 2025-08-09 (6 days ago)
dmi.bios.date: 04/28/2020
dmi.bios.release: 2.47
dmi.bios.vendor: HP
dmi.bios.version: N03 Ver. 02.47
dmi.board.name: 8062
dmi.board.vendor: HP
dmi.board.version: KBC Version 05.39
dmi.chassis.type: 4
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 5.57
dmi.modalias: dmi:bvnHP:bvrN03Ver.02.47:bd04/28/2020:br2.47:efr5.57:svnHP:pnHPProDesk400G3SFF:pvr:rvnHP:rn8062:rvrKBCVersion05.39:cvnHP:ct4:cvr:skuN4P96AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 400 G3 SFF
dmi.product.sku: N4P96AV
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2120729/+subscriptions
Подписаться на:
Сообщения (Atom)