[Kernel-packages] [Bug 2081678] Re: task txg_sync:696 blocked
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2081678 Title: task txg_sync:696 blocked Status in linux package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in linux source package in Noble: Triaged Status in zfs-linux source package in Noble: New Bug description: SRU Justification [Impact] * Seeing task txg_sync:696 blocked for > 120 seconds in some instances. Logs included below SRU justification [Fix] * Backport 08fd5ccc38c3: "Improve performance for zpool trim on linux" * Backport 370869c56dc8: "vdev_disk: ensure trim errors are returned immediately" [Test Plan] * Compile tested * Run through autopkgtest regression tests [Regression potential] * Changes isolated, minimal regression risk. Changes already in upstream ZFS [43501.152595] INFO: task txg_sync:696 blocked for more than 122 seconds. [43501.152613] Tainted: P IO 6.8.0-45-generic #45-Ubuntu [43501.152616] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [43501.152618] task:txg_syncstate:D stack:0 pid:696 tgid:696 ppid:2 flags:0x4000 [43501.152625] Call Trace: [43501.152628] [43501.152633] __schedule+0x27c/0x6b0 [43501.152644] schedule+0x33/0x110 [43501.152649] schedule_timeout+0x95/0x170 [43501.152653] ? __pfx_process_timeout+0x10/0x10 [43501.152660] io_schedule_timeout+0x51/0x80 [43501.152666] __cv_timedwait_common+0x139/0x180 [spl] [43501.152696] ? __pfx_autoremove_wake_function+0x10/0x10 [43501.152702] __cv_timedwait_io+0x19/0x30 [spl] [43501.152725] zio_wait+0x119/0x230 [zfs] [43501.153184] spa_sync_frees+0x3f/0x90 [zfs] [43501.153635] spa_sync_iterate_to_convergence+0x10b/0x220 [zfs] [43501.154067] spa_sync+0x321/0x620 [zfs] [43501.154502] txg_sync_thread+0x1e7/0x250 [zfs] [43501.154926] ? __pfx_txg_sync_thread+0x10/0x10 [zfs] [43501.155347] ? __pfx_thread_generic_wrapper+0x10/0x10 [spl] [43501.155386] thread_generic_wrapper+0x5f/0x70 [spl] [43501.155415] kthread+0xf2/0x120 [43501.155421] ? __pfx_kthread+0x10/0x10 [43501.155425] ret_from_fork+0x47/0x70 [43501.155429] ? __pfx_kthread+0x10/0x10 [43501.155433] ret_from_fork_asm+0x1b/0x30 [43501.155440] [43501.155443] INFO: task vdev_autotrim:710 blocked for more than 122 seconds. [43501.155447] Tainted: P IO 6.8.0-45-generic #45-Ubuntu [43501.155449] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [43501.155451] task:vdev_autotrim state:D stack:0 pid:710 tgid:710 ppid:2 flags:0x4000 [43501.155456] Call Trace: [43501.155459] [43501.155461] __schedule+0x27c/0x6b0 [43501.155468] schedule+0x33/0x110 [43501.155472] cv_wait_common+0x102/0x140 [spl] [43501.155494] ? __pfx_autoremove_wake_function+0x10/0x10 [43501.155501] __cv_wait+0x15/0x30 [spl] [43501.155522] vdev_autotrim_wait_kick+0x4d/0xb0 [zfs] [43501.155943] vdev_autotrim_thread+0x44e/0x7b0 [zfs] [43501.156373] ? __pfx_vdev_autotrim_thread+0x10/0x10 [zfs] [43501.156793] ? __pfx_thread_generic_wrapper+0x10/0x10 [spl] [43501.156821] thread_generic_wrapper+0x5f/0x70 [spl] [43501.156849] kthread+0xf2/0x120 [43501.156853] ? __pfx_kthread+0x10/0x10 [43501.156857] ret_from_fork+0x47/0x70 [43501.156861] ? __pfx_kthread+0x10/0x10 [43501.156864] ret_from_fork_asm+0x1b/0x30 [43501.156870] [43624.033465] INFO: task txg_sync:696 blocked for more than 245 seconds. [43624.033479] Tainted: P IO 6.8.0-45-generic #45-Ubuntu [43624.033483] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [43624.033486] task:txg_syncstate:D stack:0 pid:696 tgid:696 ppid:2 flags:0x4000 [43624.033494] Call Trace: [43624.033498] [43624.033504] __schedule+0x27c/0x6b0 [43624.033517] schedule+0x33/0x110 [43624.033522] schedule_timeout+0x95/0x170 [43624.033528] ? __pfx_process_timeout+0x10/0x10 [43624.033537] io_schedule_timeout+0x51/0x80 [43624.033545] __cv_timedwait_common+0x139/0x180 [spl] [43624.033583] ? __pfx_autoremove_wake_function+0x10/0x10 [43624.033588] __cv_timedwait_io+0x19/0x30 [spl] [43624.033612] zio_wait+0x119/0x230 [zfs] [43624.034070] spa_sync_frees+0x3f/0x90 [zfs] [43624.034510] spa_sync_iterate_to_convergence+0x10b/0x220 [zfs] [43624.034939] spa_sync+0x321/0x620 [zfs] [43624.035373] txg_sync_thread+0x1e7/0x250 [zfs] [43624.035796] ? __pfx_txg_sync_thread+0x10/0x10 [zfs] [43624.036224] ? __pfx_thread_generic_wrapper+0x10/0x10 [spl] [43624.036255] thread_generic_wrapper+0x5f/0x70 [spl] [43624.036283] kthread+0xf2/0x120 [43624.036289] ? __pfx_kthread+0x10/0x10 [43624.036293] ret_from_fork+0x47/0x70 [43624.036297] ? __pfx_kthread+0x10/0x10 [43624.0
[Kernel-packages] [Bug 2057693] Re: Activating autotrim results in high load average due to uninterruptible threads
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2057693 Title: Activating autotrim results in high load average due to uninterruptible threads Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Noble: New Bug description: SRU Justification [Impact] * High load averages when activating autotrim. Logs included below SRU justification [Fix] * Cherry-pick a0aa7a2ee3b5: "Autotrim High Load Average Fix" [Test Plan] * Compile tested * Run through autopkgtest regression tests [Regression potential] * Changes isolated, minimal regression risk. Changes already in upstream ZFS When activating the autotrim feature on any ZFS version starting from 2.2.0 this will lead to a permanent increase of the load average (as diplayed in top) due to an uninterruptible vdev_autotrim thread for each vdev capable of TRIM. This issue has been reported (https://github.com/openzfs/zfs/issues/15453) as well as fixed (https://github.com/openzfs/zfs/pull/15781) upstream but the fix is not yet backported to Ubuntu. Since this bug was introduced with version 2.2.0 both mantic as well as noble are affected. How to reproduce: 1. Create a pool with at least one TRIM-capable device 2. run "zpool set autotrim=on " 3. watch the output of "top" or "runtime" and see how the load average increases permanently even when the system is idle by one per vdev 4. running "ps aux | grep -w D" will show the broken threads: [root@test ~]# ps aux | grep -w D\< root7193 0.0 0.0 0 0 ?D< 13:07 0:00 [vdev_autotrim] To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2057693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2090852] Re: [SRU] power: intel_pstate: HWP interrupt support for maximum ratio changed
** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Thibf (thibf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2090852 Title: [SRU] power: intel_pstate: HWP interrupt support for maximum ratio changed Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: In Progress Bug description: This is a public version of: https://bugs.launchpad.net/bugs/2078898 [ Impact ] * Performance improvement for intel hardware with dynamic HWP (Hardware P-States) [ Fix ] Upstream commits support dynamic HWP: 7ea81936b853 x86/cpufeatures: Add HWP highest perf change feature flag d845cd901b28 cpufreq: intel_pstate: Support highest performance change interrupt [ Test Plan ] * check on supported hardware that the correct max cpu freq is detected [ Where problems could occur ] * Regression on intel CPU frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2090852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
** Description changed: - I have a server that has been running its data volume using ZFS in 20.04 - without any problem. The volume is using ZFS encryption and a raidz1-0 - configuration. I performed a scrub operations before the upgrade and it - did not find any problem. After the reboot for the upgrade, I was - welcomed with the following message: + [ Impact ] + Upgrading from 20.04 to 22.04 causes encrypted pools to become unmountable. This + is due to broken accounting metadata causing checksum errors on decrypt, which + makes ZFS error out early with ECKSUM. + + [ Test Plan ] + This issue needs specific accounting metadata on the zpool to be broken, and as + such is somewhat tricky to reproduce organically. A regular test plan for an + affected pool should be: + 1. Setup encrypted zpool under 20.04 + 2. Upgrade system to 22.04 (e.g. using do-release-upgrade script) + 3. Verify that zpool fails to mount under 22.04 (zpool status will likely point +to ZFS-8000-8A "Corrupted data" [0]) + + [0] https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A/ + + Thankfully, upstream has included a test scenario for this under the ZFS test + suite, which is ran during build. The + tests/zfs-tests/tests/functional/userquota/13709_reproducer.bz2 file is taken + directly from upstream, and corresponds to an encrypted zpool with the required + (broken) metadata to reproduce this issue. If the ZFS test suite passes, this + should give us a strong signal that this isssue is fixed. + + [ Where problems could occur ] + Although I've backported the upstream test, it'd be great to have confirmation + from affected users that this patch resolves the issue. Additionally, we should + also perform upgrades in non-affected zpools as well as non-encrypted zpools, to + ensure no regressions have been introduced. + + Considering this change affects the encrypt/decrypt code paths, problems could + arise in creating new encrypted zpools, as well as when mounting zpools that + have been previously encrypted. + + [ Other Info ] + This SRU includes a little more changes than the minimal changes mentioned in + the SRU policy, as I've also backported one of upstream's tests for encrypted + pools. This included a new test script (userspace_encrypted_13709.ksh), as well + as a binary zpool dump (13709_reproducer.bz2) that I've added under + d/s/include-binaries. + + Considering this issue causes zpools to become unmountable, I think it's worth + to include these in the standard ZFS test suite (similar to an autopkgtest + scenario for a high-risk regression). These are included in future releases of + zfs-linux, and as such only Jammy is affected by this regression. + -- + + [ Original Description ] + I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data - corruption. Applications may be affected. + corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the - entire pool from backup. -see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A + entire pool from backup. + see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: - errors: Permanent errors have been detected in the following files: - - tank/data/data:<0x0> + errors: Permanent errors have been detected in the following files: + + tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult:
[Kernel-packages] [Bug 2089684] Re: oracular: ubuntu_boot lib/dynamic_queue_limits.c:99!
This triggers a sut-scan in some regression testing cases too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2089684 Title: oracular: ubuntu_boot lib/dynamic_queue_limits.c:99! Status in linux package in Ubuntu: Triaged Status in linux source package in Oracular: Triaged Status in linux source package in Plucky: Triaged Bug description: We observed this in GCP cloud where boot test cases pass but it prints a stack trace afterwards due to an error in virtio_net. [9.326748] cloud-init[617]: Cloud-init v. 24.4~3+really24.3.1-0ubuntu4 running 'init-local' at Tue, 26 Nov 2024 12:47:39 +. Up 9.28 seconds. [ 10.470815] kernel BUG at lib/dynamic_queue_limits.c:99! [ 10.476289] Oops: invalid opcode: [#1] SMP PTI [ 10.481279] CPU: 0 UID: 0 PID: 644 Comm: ip Not tainted 6.11.0-1005-gcp #5-Ubuntu [ 10.47] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 [ 10.498742] RIP: 0010:dql_completed+0x191/0x1b0 [ 10.503629] Code: 63 ce 01 48 89 47 58 e9 03 ff ff ff 45 85 e4 41 0f 95 c3 39 d9 0f 95 c1 41 84 cb 74 05 45 85 ed 78 0a 44 89 d1 e9 e5 fe ff ff <0f> 0b 01 c0 44 89 d1 29 c1 b8 00 00 00 00 0f 48 c8 eb 84 66 66 2e [ 10.522602] RSP: 0018:ab5f3cb0 EFLAGS: 00010297 [ 10.528032] RAX: 0036 RBX: ab5f3d10 RCX: [ 10.535541] RDX: RSI: 0036 RDI: 97d445b28d00 [ 10.542876] RBP: ab5f3d00 R08: R09: [ 10.550384] R10: 97d462c0 R11: bc0060c0 R12: 97d441aec000 [ 10.557875] R13: ab5f3ccc R14: 97d445b28c00 R15: 97d446ac0a00 [ 10.565206] FS: 793839e71800() GS:97d462c0() knlGS: [ 10.573458] CS: 0010 DS: ES: CR0: 80050033 [ 10.579408] CR2: 5fee8b709198 CR3: 03e78006 CR4: 003706f0 [ 10.586663] DR0: DR1: DR2: [ 10.593999] DR3: DR6: fffe0ff0 DR7: 0400 [ 10.601350] Call Trace: [ 10.604094] [ 10.606211] ? show_trace_log_lvl+0x1be/0x310 [ 10.611074] ? show_trace_log_lvl+0x1be/0x310 [ 10.615631] ? free_old_xmit+0x4a/0xa0 [ 10.619633] ? show_regs.part.0+0x22/0x30 [ 10.623774] ? __die_body.cold+0x8/0x10 [ 10.627735] ? __die+0x2a/0x40 [ 10.630904] ? die+0x2f/0x60 [ 10.633898] ? do_trap+0xc8/0x110 [ 10.637675] ? do_error_trap+0x71/0xb0 [ 10.641811] ? dql_completed+0x191/0x1b0 [ 10.645854] ? exc_invalid_op+0x52/0x80 [ 10.649896] ? dql_completed+0x191/0x1b0 [ 10.654011] ? asm_exc_invalid_op+0x1b/0x20 [ 10.658325] ? dql_completed+0x191/0x1b0 [ 10.662456] ? __free_old_xmit+0xe1/0x160 [ 10.666569] free_old_xmit+0x4a/0xa0 [ 10.670339] virtnet_poll_cleantx.isra.0+0xca/0x130 [ 10.675368] virtnet_poll+0x5d/0x610 [ 10.679049] ? __enqueue_entity+0x10b/0x150 [ 10.683438] ? enqueue_entity+0xde/0x530 [ 10.687489] __napi_poll+0x30/0x190 [ 10.691143] net_rx_action+0x212/0x410 [ 10.695002] handle_softirqs+0xe7/0x310 [ 10.699206] __do_softirq+0x10/0x18 [ 10.703163] do_softirq.part.0+0x3f/0x80 [ 10.707211] [ 10.709419] [ 10.711639] __local_bh_enable_ip+0x4e/0x50 [ 10.716069] virtnet_open+0x108/0x360 [ 10.719878] __dev_open+0x109/0x1d0 [ 10.723580] __dev_change_flags+0x1d8/0x230 [ 10.727976] dev_change_flags+0x27/0x80 [ 10.731942] do_setlink+0x39e/0xd90 [ 10.735777] ? rtnetlink_rcv_msg+0x2e8/0x440 [ 10.740156] ? __nla_validate_parse+0x49/0x1b0 [ 10.744717] __rtnl_newlink+0x5c8/0x770 [ 10.748773] rtnl_newlink+0x77/0xa0 [ 10.752378] rtnetlink_rcv_msg+0x2d5/0x440 [ 10.756585] ? __pfx_rtnetlink_rcv_msg+0x10/0x10 [ 10.761479] netlink_rcv_skb+0x52/0x100 [ 10.765484] rtnetlink_rcv+0x15/0x30 [ 10.769180] netlink_unicast+0x226/0x350 [ 10.773253] netlink_sendmsg+0x214/0x460 [ 10.777296] sys_sendmsg+0x3b1/0x3f0 [ 10.781404] ___sys_sendmsg+0x9a/0xf0 [ 10.785279] __sys_sendmsg+0xe5/0x120 [ 10.789111] __x64_sys_sendmsg+0x1d/0x30 [ 10.793339] x64_sys_call+0x7da/0x22b0 [ 10.797375] do_syscall_64+0x7e/0x170 [ 10.801147] ? __count_memcg_events+0x86/0x160 [ 10.805756] ? count_memcg_events.constprop.0+0x2a/0x50 [ 10.811157] ? handle_mm_fault+0x1b1/0x2d0 [ 10.816001] ? do_user_addr_fault+0x5af/0x7b0 [ 10.820939] ? irqentry_exit_to_user_mode+0x43/0x250 [ 10.826117] ? irqentry_exit+0x21/0x40 [ 10.830026] ? clear_bhb_loop+0x15/0x70 [ 10.833979] ? clear_bhb_loop+0x15/0x70 [ 10.838102] ? clear_bhb_loop+0x15/0x70 [ 10.842078] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 10.847339] RIP: 0033:0x793839d35e14 [ 10.8
[Kernel-packages] [Bug 2089780] Re: ip6tables unknown option --set-xmark
** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2089780 Title: ip6tables unknown option --set-xmark Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Triaged Bug description: Summary: ip6tables --set-xmark failed on 1057.59 A degradation Working version: 1053.55 bf-bundle-2.9.1-13_24.11_ubuntu-22.04_prod.bfb has kernel 5.15.0-1053.55.24.g9cc17fe-bluefield root@r-qa-hbn00-host00-00:mgmt:/home/ubuntu# /usr/sbin/ip6tables -t nat -C CNI-HOSTPORT-SETMARK -m comment --comment 'CNI portfwd masquerade mark' -j MARK --set-xmark 0x2000/0x2000 --wait MARK all optin * out * ::/0 -> ::/0 /* CNI portfwd masquerade mark */ MARK or 0x2000 Failed version: 1057.59 === bf-bundle-2.9.1-14_24.11_ubuntu-22.04_prod.bfb has kernel 5.15.0-1057.59.25.g6d91088-bluefield root@r-qa-hbn00-host02-01:mgmt:/home/ubuntu# /usr/sbin/ip6tables -t nat -C CNI-HOSTPORT-SETMARK -m comment --comment 'CNI portfwd masquerade mark' -j MARK --set-xmark 0x2000/0x2000 --wait ip6tables v1.8.7 (nf_tables): unknown option "--set-xmark" Try `ip6tables -h' or 'ip6tables --help' for more information. Fix: need to backport: https://lore.kernel.org/all/20241019-xtables-typos-v2-1-6b8b1735d...@0upti.me/ upstream id 306ed1728e84 netfilter: xtables: fix typo causing some targets not to load on IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2089780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2090810] Re: package linux-image-6.8.0-49-generic 6.8.0-49.49~22.04.1 failed to install/upgrade: installed linux-image-6.8.0-49-generic package pre-removal script subprocess ret
*** This bug is a duplicate of bug 2073399 *** https://bugs.launchpad.net/bugs/2073399 You chose to abort the removal of the running kernel: [?1049l[23;0;0tE: Aborting removal of the running kernel That shouldn't trigger a bug report. ** This bug has been marked a duplicate of bug 2073399 Aborting the removal of the running kernel triggers apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2090810 Title: package linux-image-6.8.0-49-generic 6.8.0-49.49~22.04.1 failed to install/upgrade: installed linux-image-6.8.0-49-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-6.8 package in Ubuntu: New Bug description: bug happen when i am using dual screen. its disable one screen sub and return 1 screen. No problem with my cable HDMI. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-49-generic 6.8.0-49.49~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-49.49~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-49-generic x86_64 NonfreeKernelModules: character_device ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Dec 2 11:56:00 2024 DpkgHistoryLog: Start-Date: 2024-12-02 11:55:24 Commandline: apt purge linux-image-6.8.0-49-generic Requested-By: danglhb (1000) Purge: linux-image-generic-hwe-22.04:amd64 (6.8.0-49.49~22.04.1), linux-image-6.8.0-49-generic:amd64 (6.8.0-49.49~22.04.1), linux-generic-hwe-22.04:amd64 (6.8.0-49.49~22.04.1) ErrorMessage: installed linux-image-6.8.0-49-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-07-29 (125 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04.1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.13 SourcePackage: linux-signed-hwe-6.8 Title: package linux-image-6.8.0-49-generic 6.8.0-49.49~22.04.1 failed to install/upgrade: installed linux-image-6.8.0-49-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2090810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077829] Re: Missing CS35L56 sof firmware for Dell Bolan platform
This bug was fixed in the package firmware-sof - 2024.06-1ubuntu1.1 --- firmware-sof (2024.06-1ubuntu1.1) oracular; urgency=medium * Missing CS35L56 sof firmware for Dell Bolan platform. (LP: #2077829) - Add 2.11 topology2 production binaries - Add SOF v2.11.1 signed Intel binaries for MTL/LNL/ARL -- Chris Chiu Mon, 14 Oct 2024 16:02:39 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2077829 Title: Missing CS35L56 sof firmware for Dell Bolan platform Status in OEM Priority Project: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in firmware-sof source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in firmware-sof source package in Oracular: Fix Released Status in linux-firmware source package in Oracular: Fix Released Status in firmware-sof source package in Plucky: Fix Released Status in linux-firmware source package in Plucky: Fix Released Bug description: [SRU Justifications] == linux-firmware == [Impact] Audio output doesn't work on Dell Bolan platforms with CS35L56 speaker amplifiers [Fix] This requires following firmware blobs: - https://github.com/CirrusLogic/linux-firmware/commit/367fda8e56d7dda4c138438493e2bf6b9b92ce7b which is not landed in linux-firmware mainline yet. [Test Case] 1. Boot up the machine of Dell Bolan platform with CS35L56 speakers 2. Verify the sof-lnl-cs42l43-l0.tplg in in the /lib/firmware/intel/sof-ipc4-tplg/ 3. Verify with checking the output of `aplay -l` command with valid sof output device. Should never be dummy output. [Where problems could occur] It only affects the Dell Bolan platforms with the new CS35L56 amplifier. Should be low low risk of regression == firmware-sof == [Fix] This requires following tplg file in firmware-sof - sof-lnl-cs42l43-l0.tplg upstream firmware-sof 2.11 will have this tplg file included. [Test Case] 1. Boot up the machine of Dell Bolan platform with CS35L56 speakers 2. Verify with the linux-firmware with new CS35L56 amplifier support. 3. Verify with checking the output of `aplay -l` command with valid sof output device. Should never be dummy output. [Other Info] The name of sof-lnl-cs42l43-l0.tplg includes useful information which indicates that the topology is for for the cs42l43 codec connected to soundwire bus 0 w/o other soundwire devices connected on 1/2/3. It only affects the machines which has exactly the same soundwire configuration. The upstream commit of a newer version usually include the topology files for the new platforms or missing configuration on old platforms. It would be better to catch up with upstream to have these configuration which can support more configurations we could be missing in the future. The the addtional 0002-Add-SOF-v2.11.1-signed-Intel-binaries-for-MTL-LNL-AR.patch, it's required for each new Intel Platform and signed by Intel. In the case, the tplg file specify the `lnl`, a signed LunarLake DSP FW will be necessary. It would be better to have the Intel signed DSP FW up-to-date. [Where problems could occur] Although there're lots of new tplg files added, but they are mostly for missing configuration on old platforms or newly added for next-gen Intel platform. And they are specified for particular soundwire configurations which can hardly affect the existing machines. The risk for regression may come from sof-hda-generic-xxx.tplg which is for generic HDA. I'll consider it as low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2077829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2089889] Re: Fix Mic Mute LED no function on HP laptops with Cirrus amplifier
** Summary changed: - Fix Mic Mute LED no function on HP laptops with Cirrus amplifier audio codec + Fix Mic Mute LED no function on HP laptops with Cirrus amplifier ** Description changed: [SRU Justifications] - [Impact] - Audio miu mute function works OK but the LED does not toggle + Audio mic mute function works OK but the LED does not toggle accordingly. [Fix] - This requires the upstream commit https://lore.kernel.org/all/20240829161114.140938-1-sim...@opensource.cirrus.com/ from Cirrus. + This requires the upstream commit https://lore.kernel.org/all/20240829161114.140938-1-sim...@opensource.cirrus.com/ from Cirrus. And additional quirk for specific HP SSIDs are required for working mic-mute led. [Test Case] 1. Boot up the HP ZBook series laptops with Audio codec + Cirrus amplifier 2. Press the Mic Mute function key (F9) and check the mic mute function 3. Check if the LED (on F9) is ON when Mic Mute, and OFF when Mic not muted. [Where problems could occur] - The auto-detection patch is looking for cs35l56 variants in ACPI so we don’t need the quirks anymore to get the amplifier drivers started. Cirrus claims it should cover Machu, Lapaz and Colosseum on HP laptops. + The auto-detection patch is looking for cs35l56 variants in ACPI. Cirrus claims it should cover Machu, Lapaz and Colosseum on HP laptops to get the HDA codec automatically work with the amplifier. The only thing need to be quirked is for mic-mute LED which are restricted on particular HP models and shouldn't introduce regression ** Description changed: [SRU Justifications] [Impact] Audio mic mute function works OK but the LED does not toggle accordingly. [Fix] This requires the upstream commit https://lore.kernel.org/all/20240829161114.140938-1-sim...@opensource.cirrus.com/ from Cirrus. And additional quirk for specific HP SSIDs are required for working mic-mute led. [Test Case] 1. Boot up the HP ZBook series laptops with Audio codec + Cirrus amplifier 2. Press the Mic Mute function key (F9) and check the mic mute function 3. Check if the LED (on F9) is ON when Mic Mute, and OFF when Mic not muted. [Where problems could occur] - The auto-detection patch is looking for cs35l56 variants in ACPI. Cirrus claims it should cover Machu, Lapaz and Colosseum on HP laptops to get the HDA codec automatically work with the amplifier. The only thing need to be quirked is for mic-mute LED which are restricted on particular HP models and shouldn't introduce regression + The auto-detection patch is looking for cs35l56 variants in ACPI. Cirrus claims it should cover Machu, Lapaz and Colosseum on HP laptops to get the HDA codec automatically work with the amplifier. The only thing need to be quirked is for mic-mute LED. It only applies on particular HP models and shouldn't introduce regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2089889 Title: Fix Mic Mute LED no function on HP laptops with Cirrus amplifier Status in linux package in Ubuntu: Triaged Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Triaged Status in linux-oem-6.11 source package in Noble: In Progress Status in linux source package in Oracular: Triaged Status in linux-oem-6.11 source package in Oracular: New Status in linux source package in Plucky: Triaged Status in linux-oem-6.11 source package in Plucky: New Bug description: [SRU Justifications] [Impact] Audio mic mute function works OK but the LED does not toggle accordingly. [Fix] This requires the upstream commit https://lore.kernel.org/all/20240829161114.140938-1-sim...@opensource.cirrus.com/ from Cirrus. And additional quirk for specific HP SSIDs are required for working mic-mute led. [Test Case] 1. Boot up the HP ZBook series laptops with Audio codec + Cirrus amplifier 2. Press the Mic Mute function key (F9) and check the mic mute function 3. Check if the LED (on F9) is ON when Mic Mute, and OFF when Mic not muted. [Where problems could occur] The auto-detection patch is looking for cs35l56 variants in ACPI. Cirrus claims it should cover Machu, Lapaz and Colosseum on HP laptops to get the HDA codec automatically work with the amplifier. The only thing need to be quirked is for mic-mute LED. It only applies on particular HP models and shouldn't introduce regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084059] Re: OVTI08F4:00: number of CSI2 data lanes 2 is not supported
Updated the bug description. ** Description changed: [SRU Justification] [Impact] OVTI08F4 camera sensor is used in a different hardware config that is not currently supported: ``` $ sudo dmesg ... usbio-i2c usbio-i2c.3.auto: hid INTC10B6 uid VIC0 new uid1 ov08x40 i2c-OVTI08F4:00: number of CSI2 data lanes 2 is not supported ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -22 ov08x40 i2c-OVTI08F4:00: probe with driver ov08x40 failed with error -22 ``` [Fix] Proposed fix in: * https://github.com/intel/ipu6-drivers/pull/286 There are two parts. One in the kernel tree that is to be SRU-ed in this pull request. It adds two additional link frequencies so that ipu-bridge may probe this case. The other part is in the camera sensor driver itself that goes to ipu6-drivers. [Test Case] With patch applied, install kernel and intel-ipu6-dkms from -proposed pocket: ``` $ sudo dmesg ... intel_ipu7_psys.psys intel_ipu7.psys.40: psys probe minor: 0 intel_ipu7_isys.isys intel_ipu7.isys.40: bind ov08x40 14-0036 nlanes is 2 port is 0 intel_ipu7_isys.isys intel_ipu7.isys.40: All sensor registration completed. ``` Check if camera actually works: ``` $ sudo gst-launch-1.0 icamerasrc ! autovideosink ``` + Full test plan is done via checkbox camera tests by multiple parties. [Where problems could occur] - This is a new hardware configuration for OVTI08F4. Expect further - issues. + This is a new hardware configuration for OVTI08F4. Verified on both of + the two equipped models being/been enabled. While we don't have much + details about the differences in register contents, expect further + issues if not covered by generic camera tests. [Other Info] So far this configuration is bound to Intel Lunar Lake platform that is only supported by v6.11 kernels and ipu6-drivers/oracular, ipu7/drivers/oracular. Nominate for linux/oracular, linux-oem-6.11/noble and linux-unstable-6.12. == original bug report == $ sudo dmesg|grep ov0 [4.793991] ov08x40 i2c-OVTI08F4:00: number of CSI2 data lanes 2 is not supported [4.793997] ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -22 [4.815076] ov08x40 i2c-OVTI08F4:00: probe with driver ov08x40 failed with error -22 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:gdm1400 F pipewire CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-10-18 (4 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Dell Pro 14 Premium PA14250 Package: linux (not installed) ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1006-oem root=UUID=32c3d524-0a3b-48e2-802c-9cd4ca0503a3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-1006.6-oem 6.11.0 RelatedPackageVersions: linux-restricted-modules-6.11.0-1006-oem N/A linux-backports-modules-6.11.0-1006-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: noble Uname: Linux 6.11.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/06/2024 dmi.bios.release: 89.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.7.31 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AFTPASS dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 137.1 dmi.modalias: dmi:bvnDellInc.:bvr89.7.31:bd09/06/2024:br89.7:efr137.1:svnDellInc.:pnDellPro14PremiumPA14250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CE4: dmi.product.family: Dell Pro Laptops dmi.product.name: Dell Pro 14 Premium PA14250 dmi.product.sku: 0CE4 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:gdm1385 F pipewire CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-10-18 (4 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Dell Pro 14 Premium PA14250 Package: linux (not installed) ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-9006-oem root=UUID=32c3d524-0a3b-48e2-802c-9cd4ca0503a3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-9006.6+exp.21-oem
[Kernel-packages] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
* Installed the firefox snap from --channge=edge, which is core24 * Verified following the test plan that it would reproduce the crash * Added noble-proposed to the mesa-2404 recipe package-repositories: - type: apt url: http://archive.ubuntu.com/ubuntu suites: [noble-proposed] components: [main, universe] architectures: [amd64, i386] key-id: F6ECB3762474EDA9D21B7022871920D1991BC93C key-server: keyserver.ubuntu.com priority: always $ snapcraft --verbosity debug [...] 2024-12-03 10:39:04.936 Downloading package: mesa-va-drivers 2024-12-03 10:39:05.069 Get: 20 mesa-va-drivers_24.0.9-0ubuntu0.3_amd64.deb [4246 kB] [...] 2024-12-03 10:39:14.796 Extracting stage package: mesa-va-drivers $ sudo snap install --dangerous ./mesa-2404_24.0.9_amd64.snap * Verified following the test plan that the crash and green artifacts did not happen. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in Linux: Fix Released Status in Mesa: Fix Released Status in firefox package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Noble: Fix Committed Bug description: [ Impact ] * amdgpu changes in kernel 6.11 make VAAPI video playback crash the GPU and bring down the whole system. * A fix was shipped in mesa 24.2, which is already in Oracular - the only version with kernel 6.11 currently, but snaps bundle their own version of mesa so core22 snaps like Firefox are affected. Firefox has VAAPI disabled by default, but it can be enabled by the user. [ Test Plan ] * Set up a system with an AMD GPU running Ubuntu 24.10 with kernel 6.11 * Open Firefox * Navigate to `about:config` * Search `media.ffmpeg.vaapi.enabled` * Enable the setting by clicking the toggle button * Restart Firefox * Play different videos on x.com or youtube.com (I don't have a reliable reproducer unfortunately) * Ensure that there are no green artifacts on the video playback * Ensure that the system didn't lock up * 10 minutes of scrolling through videos was generally enough to trigger the bug in my testing. Sometimes I could only get the green artifacts, other times I could get the system to lock up. [ Where problems could occur ] * The scope of the change is limited to the VAAPI driver for AMD GPUs ( /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so ) An issue with the change may break video playback. But, as this bug demonstrated, a bug in the video acceleration driver may also bring down the whole system... [ Original Description ] It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Kernel-packages] [Bug 2080489] Re: Network Manager stops functioning on Ubuntu 24.04
Today the system got stuck during shutdown, showing a message of pending update. However it was in fact stuck waiting for the NetworkManager to respond. A few times before I noticed the battery was completely discharged after I had shut the system down. Now it seems the system stays on overnight waiting for the NetworkManager, until power runs out. This is not very healthy for the battery. Any hints on how to deal with this bug are most welcome. Thank you for reading. ** Attachment added: "IMG_20241203_093609848.jpg" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2080489/+attachment/5841746/+files/IMG_20241203_093609848.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2080489 Title: Network Manager stops functioning on Ubuntu 24.04 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I installed Ubuntu 24.04 about a month ago on a Asus Vivobook. Soon after the NetworkManager started misbehaving, with all connections to the internet becoming idle now and then. When this event happens the only way to restore internet access is to reboot the system. If initially these events were occasional, they now take place 3 or 4 times per day, often after signing in from the lock screen. So far I was not able to verify whether NetworkManager is actually crashing, the Settings programme reports "NetworkManager not running" (see attached image). However, in the command line `systemctl` reports an active service: ``` $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled> Active: active (running) since Sun 2024-08-27 18:21:44 WEST; 2h 18min a> Docs: man:NetworkManager(8) Main PID: 1149 (NetworkManager) Tasks: 4 (limit: 18646) Memory: 12.2M (peak: 28.6M) CPU: 836ms CGroup: /system.slice/NetworkManager.service └─1149 /usr/sbin/NetworkManager --no-daemon ago 27 19:34:08 Symbolic NetworkManager[1149]: [1724006048.8961] man> ago 27 19:34:08 Symbolic NetworkManager[1149]: [1724006048.8965] dev> ago 27 19:34:09 Symbolic NetworkManager[1149]: [1724006049.1482] dev> ago 27 19:34:09 Symbolic NetworkManager[1149]: [1724006049.1484] dev> ago 27 19:34:09 Symbolic NetworkManager[1149]: [1724006049.1488] dhc> ago 27 19:34:09 Symbolic NetworkManager[1149]: [1724006049.1488] dhc> ago 27 19:34:09 Symbolic NetworkManager[1149]: [1724006049.1489] dhc> ago 27 19:34:09 Symbolic NetworkManager[1149]: [1724006049.2049] dev> ago 27 20:33:50 Symbolic NetworkManager[1149]: [1724009630.5340] man> ago 27 20:33:50 Symbolic NetworkManager[1149]: [1724009630.5344] dev> ``` But if I try to restart the service, the command line just hangs up: ``` $ ping 1.1.1.1 ping: connect: Network is unreachable $ sudo systemctl restart NetworkManager ``` Also from `ifconfig` there is no response: ``` $ ifconfig -a ``` Please let me know if there is further useful information I can report. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076569] Re: ISST-LTE:KOP:doodlp1g3:L2 guest hung and Call traces seen with Snapshot tests
*** This bug is a duplicate of bug 2076147 *** https://bugs.launchpad.net/bugs/2076147 Hello, yes, that (integrating commit 73bc32875ee9) is what we already did based on LP#2076147: https://bugs.launchpad.net/bugs/2076147 And it's already rolled out. This LP bug here (LP#2076569) got marked as duplicate of LP#2076147. And duplicates are not really updated anymore, but I know that a duplicate is not visible in IBM BZ, so that might be the reason this still seems to be open, but it's not. Let me update the status us this "duplicate" ticket manually, so that the status will hopefully be synched into BZ correctly. ** Changed in: ubuntu-power-systems Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076569 Title: ISST-LTE:KOP:doodlp1g3:L2 guest hung and Call traces seen with Snapshot tests Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - SEETEENA THOUFEEK - 2024-08-12 00:15:56 == +++ This bug was initially created as a clone of Bug #206986 +++ ---Problem Description--- :doodlp1g3:L2 guest hung and Call traces seen with Snapshot test ---Steps to Reproduce--- Problem description : Problem description : Problem on L2 Guest doodlp1g3 is hang and calltraces are seeing [254596.011652] watchdog: BUG: soft lockup - CPU#0 stuck for 805533275s! [systemd-userwor:2849437] [254596.011796] Modules linked in: chacha_generic wp512 streebog_generic rmd160 poly1305_generic nhpoly1305 michael_mic md4 crc32_generic twofish_generic twofish_common serpent_generic fcrypt des_generic libdes cast6_generic cast5_generic cast_common camellia_generic blowfish_generic blowfish_common aegis128 tun rpcsec_gss_krb5 rpcrdma rdma_cm iw_cm nfsv4 ib_cm dns_resolver ib_core nfs netfs nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bonding tls rfkill nf_tables binfmt_misc virtio_net net_failover aes_gcm_p10_crypto failover virtio_balloon crct10dif_vpmsum nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse loop dm_multipath nfnetlink zram xfs vmx_crypto crc32c_vpmsum virtio_scsi pseries_wdt scsi_dh_rdac scsi_dh_emc scsi_dh_alua [254596.012693] CPU: 0 PID: 2849437 Comm: systemd-userwor Tainted: G L [254596.012817] Hardware name: IBM pSeries (emulated by qemu) POWER10 (raw) 0x800200 0xf06 of:SLOF,HEAD hv:linux,kvm pSeries [254596.012947] NIP: c00b9054 LR: c00b9104 CTR: c053c400 [254596.013040] REGS: c001626d6b40 TRAP: 0900 Tainted: G L [254596.013151] MSR: 80009033 CR: 28822824 XER: [254596.013266] CFAR: IRQMASK: 0 [254596.013266] GPR00: 28822824 c001626d6de0 c20ced00 [254596.013266] GPR04: 0a858fa1 00018017 c0077fff [254596.013266] GPR08: c0077fffc400 28822824 [254596.013266] GPR12: c053c400 c3f0 c001626d7238 c3cf5fe8 [254596.013266] GPR16: 00073d64 c3251500 0001 1c8c6203 [254596.013266] GPR20: c3cf5fe8 a28f850a c3251500 [254596.013266] GPR24: 0002 0018 c00740891500 c00740891508 [254596.013266] GPR28: 0003 0001 c3cf6120 c00c00fe4ca8 [254596.014319] NIP [c00b9054] queued_spin_lock_slowpath+0xf20/0x163c [254596.014397] LR [c00b9104] queued_spin_lock_slowpath+0xfd0/0x163c [254596.014474] Call Trace: [254596.014507] [c001626d6de0] [c001626d6e34] 0xc001626d6e34 (unreliable) [254596.014604] [c001626d6f00] [c14f9080] _raw_spin_lock+0x68/0x88 [254596.014681] [c001626d6f20] [c053548c] page_vma_mapped_walk+0x738/0x1220 [254596.014781] [c001626d6fd0] [c053c5b8] try_to_unmap_one+0x1b8/0xe84 [254596.014876] [c001626d7110] [c0539a98] rmap_walk_anon+0x15c/0x324 [254596.014970] [c001626d7170] [c053e950] try_to_unmap+0xc8/0xf0 [254596.015048] [c001626d71d0] [c04c6118] shrink_folio_list+0xa84/0xf8c [254596.015141] [c001626d72f0] [c04c69b8] evict_folios+0x398/0xdd0 [254596.015218] [c001626d74a0] [c04c7640] try_to_shrink_lruvec+0x250/0x5ac [254596.015309] [c001626d7580] [c04c7ae4] shrink_one+0x148/0x2d8 [254596.015388] [c001626d75e0] [c04cd00c] shrink_node+0xe8c/0x11b8 [254596.015463] [c001626d76d0] [c04cea98] do_try_to_free_pages+0x144/0x7ec [254596.01
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
** Description changed: [ Impact ] Upgrading from 20.04 to 22.04 causes encrypted pools to become unmountable. This is due to broken accounting metadata causing checksum errors on decrypt, which makes ZFS error out early with ECKSUM. + + To fix this, we test specifically against this broken metadata condition + (which will cause the objset MAC to be zeroed out) and re-calculate accounting + metadata later when the pool is mounted. [ Test Plan ] This issue needs specific accounting metadata on the zpool to be broken, and as such is somewhat tricky to reproduce organically. A regular test plan for an affected pool should be: 1. Setup encrypted zpool under 20.04 2. Upgrade system to 22.04 (e.g. using do-release-upgrade script) 3. Verify that zpool fails to mount under 22.04 (zpool status will likely point -to ZFS-8000-8A "Corrupted data" [0]) + to ZFS-8000-8A "Corrupted data" [0]) [0] https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A/ Thankfully, upstream has included a test scenario for this under the ZFS test suite, which is ran during build. The tests/zfs-tests/tests/functional/userquota/13709_reproducer.bz2 file is taken directly from upstream, and corresponds to an encrypted zpool with the required (broken) metadata to reproduce this issue. If the ZFS test suite passes, this should give us a strong signal that this isssue is fixed. [ Where problems could occur ] Although I've backported the upstream test, it'd be great to have confirmation from affected users that this patch resolves the issue. Additionally, we should also perform upgrades in non-affected zpools as well as non-encrypted zpools, to ensure no regressions have been introduced. Considering this change affects the encrypt/decrypt code paths, problems could arise in creating new encrypted zpools, as well as when mounting zpools that have been previously encrypted. [ Other Info ] This SRU includes a little more changes than the minimal changes mentioned in the SRU policy, as I've also backported one of upstream's tests for encrypted pools. This included a new test script (userspace_encrypted_13709.ksh), as well as a binary zpool dump (13709_reproducer.bz2) that I've added under d/s/include-binaries. Considering this issue causes zpools to become unmountable, I think it's worth to include these in the standard ZFS test suite (similar to an autopkgtest scenario for a high-risk regression). These are included in future releases of zfs-linux, and as such only Jammy is affected by this regression. -- [ Original Description ] I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubunt
[Kernel-packages] [Bug 2085538] Re: Missing Bluetooth firmware for Intel WiFi 7 AX211/BE200/BE201
Verified:
* linux-firmware/noble-proposed version 20240318.git3b128b60-0ubuntu2.6
* linux-firmware/oracular-proposed version 20240913.gita34e7a5f-0ubuntu2.2
** Tags added: verification-done-noble verification-done-oracular
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2085538
Title:
Missing Bluetooth firmware for Intel WiFi 7 AX211/BE200/BE201
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.11 source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Status in linux-firmware source package in Oracular:
Fix Committed
Status in linux-oem-6.11 source package in Oracular:
Invalid
Status in linux source package in Plucky:
In Progress
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.11 source package in Plucky:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2085538
[Impact]
Missing Bluetooth firmware for Intel(R) Wi-Fi 7 BE201 320MHz:
```
$ lsusb
Bus 003 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
$ sudo dmesg | grep Bluetooth
kernel: Bluetooth: hci0: Device revision is 0
kernel: Bluetooth: hci0: Secure boot is enabled
kernel: Bluetooth: hci0: OTP lock is enabled
kernel: Bluetooth: hci0: API lock is enabled
kernel: Bluetooth: hci0: Debug lock is disabled
kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
kernel: Bluetooth: hci0: Bootloader timestamp 2022.18 buildtype 1 build 16362
kernel: Bluetooth: hci0: DSM reset method type: 0x00
kernel: Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-0093-0041.sfi (-2)
kernel: Bluetooth: hci0: Failed to read MSFT supported features (-56)
```
Where:
* intel/ibt-0093-0041.sfi: BE201 on ARL
- PCIID: 8086:7740 SUBSYS 8086:4090
- USBID: 8087:0033
* intel/ibt-0093-0291.sfi: BE201 on MTL
- PCIID: 8086:7740 SUBSYS 8086:40e0
- USBID: 8087:0037
[Fix]
Upstream commit
[65c4b9b74b00](https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=65c4b9b74b00b70777ca216474f2f7f8affba095)
("linux-firmware: Update firmware file for Intel BlazarU core"), which
has been included in upstream tag 20241110.
This also pulls a few more commits due to updates to
`intel/ibt-0291-0291.sfi` for Gale Peak2 (BE200).
[Test Case]
1. Install linux-firmware from -proposed pocket
2. check dmesg for successful firmware loading messages:
```
Bluetooth: hci0: Device revision is 0
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Bootloader timestamp 2022.18 buildtype 1 build 16362
Bluetooth: hci0: DSM reset method type: 0x00
Bluetooth: hci0: Found device firmware: intel/ibt-0093-0041.sfi
Bluetooth: hci0: Boot Address: 0x100800
Bluetooth: hci0: Firmware Version: 87-38.24
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1748071 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 44999 usecs
Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0093-0041.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware timestamp 2024.38 buildtype 1 build 67159
Bluetooth: hci0: Firmware SHA1: 0x083ad0b2
Bluetooth: hci0: Fseq status: Success (0x00)
Bluetooth: hci0: Fseq executed: 00.00.04.191
Bluetooth: hci0: Fseq BT Top: 00.00.04.191
```
3. check bluetooth interface is up:
```
Index list with 1 item
hci0:Primary controller
addr 98:5F:41:D6:25:0D version 12 manufacturer 2 class 0x6c010c
supported settings: powered connectable fast-connectable
discoverable bondable link-security ssp br/edr le advertising secure-conn
debug-keys privacy configuration static-addr phy-configuration wide-band-speech
cis-central cis-peripheral
current settings: powered ssp br/edr le secure-conn cis-central
cis-peripheral
name localhost
short name
hci0:Configuration options
supported options: public-address
missing options:
```
[Where problems could occur]
New hardware. And we s
[Kernel-packages] [Bug 2081384] Re: bluetooth headphones need reconnect after every reboot
bluez 5.78 appears to resolve this for me (at least symptom wise, haven't checked the first attempt logs since didn't notice any bad behavior). is the fix cherry picked in https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337 the same thing? haven't tried downgrading to that package version since 5.78 is working... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2081384 Title: bluetooth headphones need reconnect after every reboot Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bluez source package in Oracular: Confirmed Status in linux source package in Oracular: Confirmed Bug description: This issue seems to be caused by a recent package update in oracular. Every time I reboot my desktop my bluetooth headset will fail to connect until I manually go through forget device -> new pairing. journalctl says: 23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:00 desktop bluetoothd[3274]: No matching connection for device 23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress 23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:15:46 desktop bluetoothd[3274]: /org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready In dmesg I see lots of: [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085018] Re: Commit "net/mlx5e: Don't offload internal port if filter device is out device" breaks OpenStack/OVN distributed gateway use case
** Also affects: linux-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2085018
Title:
Commit "net/mlx5e: Don't offload internal port if filter device is out
device" breaks OpenStack/OVN distributed gateway use case
Status in linux package in Ubuntu:
Confirmed
Status in linux-hwe-6.8 package in Ubuntu:
New
Bug description:
Consider a topology with two chassis, A and B:
* A acts as a distributed gateway connected to provider network on tagged
VLAN and has GENEVE tunnel configured towards chassis B.
* B hosts the target instance.
* From a third machine connected to the provider network we can observe:
* Only first ICMP ECHO reply from target instance is forwarded.
* Attempt to establish TCP connection fails.
If we revert commit [0] the symptoms disappear.
The issue is also present in the most recent mainline version
available, so there does not appear to exist a fix for the issue.
0: 06b4eac9c4be ("net/mlx5e: Don't offload internal port if filter
device is out device")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085018/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085018] Re: Commit "net/mlx5e: Don't offload internal port if filter device is out device" breaks OpenStack/OVN distributed gateway use case
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.8 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.8 (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux-hwe-6.8 (Ubuntu Noble)
** Changed in: linux (Ubuntu Noble)
Status: New => Confirmed
** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2085018
Title:
Commit "net/mlx5e: Don't offload internal port if filter device is out
device" breaks OpenStack/OVN distributed gateway use case
Status in linux package in Ubuntu:
Invalid
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Confirmed
Status in linux source package in Noble:
Confirmed
Bug description:
Consider a topology with two chassis, A and B:
* A acts as a distributed gateway connected to provider network on tagged
VLAN and has GENEVE tunnel configured towards chassis B.
* B hosts the target instance.
* From a third machine connected to the provider network we can observe:
* Only first ICMP ECHO reply from target instance is forwarded.
* Attempt to establish TCP connection fails.
If we revert commit [0] the symptoms disappear.
The issue is also present in the most recent mainline version
available, so there does not appear to exist a fix for the issue.
0: 06b4eac9c4be ("net/mlx5e: Don't offload internal port if filter
device is out device")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085018/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085018] Re: Commit "net/mlx5e: Don't offload internal port if filter device is out device" breaks OpenStack/OVN distributed gateway use case
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2085018
Title:
Commit "net/mlx5e: Don't offload internal port if filter device is out
device" breaks OpenStack/OVN distributed gateway use case
Status in linux package in Ubuntu:
Invalid
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Consider a topology with two chassis, A and B:
* A acts as a distributed gateway connected to provider network on tagged
VLAN and has GENEVE tunnel configured towards chassis B.
* B hosts the target instance.
* From a third machine connected to the provider network we can observe:
* Only first ICMP ECHO reply from target instance is forwarded.
* Attempt to establish TCP connection fails.
If we revert commit [0] the symptoms disappear.
The issue is also present in the most recent mainline version
available, so there does not appear to exist a fix for the issue.
0: 06b4eac9c4be ("net/mlx5e: Don't offload internal port if filter
device is out device")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085018/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/6.11.0-1006.6)
All autopkgtests for the newly accepted linux-meta-azure (6.11.0-1006.6) for oracular have finished running. The following regressions have been reported in tests triggered by the package: dkms/3.0.11-1ubuntu14 (amd64) systemd/256.5-2ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/oracular/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085904] Re: Enable IOMMU Passthrough by default
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2085904 Title: Enable IOMMU Passthrough by default Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: SRU Justification [Impact] C3 bare metal instances run into a problem on 6.8 kernels due to Intel IOMMU being enabled by default. After performing enough disk-intensive work on the instance, the system becomes unusable and reports I/O errors at the command line until rebooted, losing data in the process. The root issue is being worked on long-term, but in the meantime we will apply a workaround to the issue for affected customers. This fix has a negative impact on security, so it is limited to Jammy kernels for which this issue is a regression. Noble kernels have always had this problem and therefore will be waiting for the long-term fix. [Fix] Change the kernel config to use IOMMU passthrough by default. [Test Plan] Perform up to 50 kernel builds on the instance in sequence. Failures on affected instances are usually detected after only 1 or 2. [Regression potential] Regression potential is especially low for Jammy as we are essentially reverting a breaking change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2085904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085547] Re: Intel(R) Wi-Fi 7 BE201 320MHz: Direct firmware load for iwlwifi-bz-b0-gf-a0-*.ucode failed with error -2
** Description changed:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2085547
[Impact]
Missing wireless firmware for Intel(R) Wi-Fi 7 BE201/BE201 on Intel Arrow
Lake platform.
```
iwlwifi :00:14.3: Detected crf-id 0x401410, cnv-id 0x80930 wfpm id
0x80005b20
iwlwifi :00:14.3: PCI dev 7740/4090, rev=0x461, rfid=0x2010d000
iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 7 BE201 320MHz
iwlwifi :00:14.3: Direct firmware load for iwlwifi-bz-b0-gf-a0-92.ucode
failed with error -2
iwlwifi :00:14.3: Direct firmware load for iwlwifi-bz-b0-gf-a0-91.ucode
failed with error -2
iwlwifi :00:14.3: Direct firmware load for iwlwifi-bz-b0-gf-a0-90.ucode
failed with error -2
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-bz-b0-gf-a0-90
iwlwifi :00:14.3: maximum version supported: iwlwifi-bz-b0-gf-a0-92
```
[Fix]
Upstream commits:
* 99f9c7ed1f4a ("iwlwifi: add gl/Bz FW for core91-69 release"), available
since upstream tag 20241017
* 60cdfe1831e8 ("iwlwifi: add Bz-gf FW for core91-69 release"), available
since upstream tag iwlwifi-fw-2024-11-19
+ * 42b01d49689c("iwlwifi: add Bz-gf FW for core89-91 release"), available
since upstream tag iwlwifi-fw-2024-11-28
Note that by Intel's product firmware release policy and plan, only -94
FW API firmware blobs are included in the new PV updates. While the
v6.11 kernels have FW API 92, v6.12 has 93 and linux-next targeting
v6.13 has 94, we bump into the same problem that we have been dealing
with many times: either to choose backport 100+ commits across v6.11 to
v6.13, or to use backport-iwlwifi dkms instead. The final decision
agreed between multiple parties is the latter one, backport-iwlwifi. It
will then depend on the latest core91 release of backport-iwlwifi, which
is meant to be updated in [bug
2085453](https://bugs.launchpad.net/bugs/2085453)..
[Test Case]
1. Install backport-iwlwifi from [bug
2085453](https://bugs.launchpad.net/bugs/2085453).
2. Install linux-firmware from -proposed pocket
3. Reboot or reload iwlwifi kernel module and check if the firmware is now
being loaded:
-```
-iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 7 BE201 320MHz
-iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.191
-iwlwifi :00:14.3: loaded firmware version 94.62990553.0
bz-b0-gf-a0-94.ucode op_mode iwlmvm
-iwlwifi :00:14.3: loaded PNVM version 35c04ca8
-```
+ ```
+ iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 7 BE201 320MHz
+ iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.191
+ iwlwifi :00:14.3: loaded firmware version 94.62990553.0
bz-b0-gf-a0-94.ucode op_mode iwlmvm
+ iwlwifi :00:14.3: loaded PNVM version 35c04ca8
+ ```
4. check wlan interface:
-```
-$ ip a
-3: wlp0s20f3: mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
-link/ether 2c:7b:a0:c5:43:24 brd ff:ff:ff:ff:ff:ff
-```
+ ```
+ $ ip a
+ 3: wlp0s20f3: mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
+ link/ether 2c:7b:a0:c5:43:24 brd ff:ff:ff:ff:ff:ff
+ ```
[Where problems could occur]
Backport-iwlwifi is never the preferred way to support new wireless
hardware, but that's the only way we can have under current situation
without breaking everyone else.
The new firmware blobs will not be loaded unless the new backport-
iwlwifi-dkms of core91 release is installed/loaded. So it does no harm
to existing setup.
Expect further stable updates for new hardware support.
[Other Info]
The first commit is already in linux-firmware/plucky, and the second one
may also be included in the next update for Plucky. Still nominate for
Noble/Oracular and Plucky.
original bug report
* TRK3-DVT1-C1_202410-35853
- ARL
- Intel(R) Wi-Fi 7 BE201 320MHz [8086:7740] Subsystem [8086:40e0]
- iwlwifi-bz-b0-fm-c0-92.ucode
- intel/ibt-0093-0291.sfi
* TRK3-DVT1-C2-CS-X01_202409-35566
- ARL
- Intel(R) Wi-Fi 7 BE201 320MHz [8086:7740] Subsystem [8086:4090]
- iwlwifi-bz-b0-gf-a0-94.ucode
- intel/ibt-0093-0041.sfi
Oct 17 06:43:58 localhost kernel: iwlwifi :00:14.3: Detected crf-id
0x401410, cnv-id 0x80930 wfpm id 0x80005b20
Oct 17 06:43:58 localhost kernel: iwlwifi :00:14.3: PCI dev 7740/4090,
rev=0x461, rfid=0x2010d000
Oct 17 06:43:58 localhost kernel: iwlwifi :00:14.3: Detected Intel(R)
Wi-Fi 7 BE201 320MHz
Oct 17 06:43:58 localhost kernel: iwlwifi :00:14.3: Direct firmware load
for iwlwifi-bz-b0-gf-a0-92.ucode failed with error -2
Oct 17 06:43:58 localhost kernel: iwlwifi :00:14.3: Direct firmware load
for iwlwifi-bz-b0-gf-a0-91.ucode failed with error -2
Oct 17 06:43:58 localhost kernel: iwlwifi :00:14.3: Direct firmware load
for iwlwifi-bz-b0-gf-a0-90.ucode failed with erro
[Kernel-packages] [Bug 2090811] Re: usb: dwc3: core: Fix system suspend
** Changed in: linux-xilinx-zynqmp (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2090811
Title:
usb: dwc3: core: Fix system suspend
Status in linux-xilinx-zynqmp package in Ubuntu:
New
Status in linux-xilinx-zynqmp source package in Noble:
Fix Committed
Bug description:
Since commit 6d735722063a ("usb: dwc3: core: Prevent phy suspend
during init"), more than one system suspend is broken on Xilinx
platforms.
This issue has been fixed upstream in [1].
There is also a fix for that patch on top of [1] ([2]).
Tested both [1] and [1] + [2] on kv260, confirmed they solve the problem.
[1]:
https://lore.kernel.org/lkml/20241011-am62-lpm-usb-v3-1-562d44562...@kernel.org/
[2]:
https://lore.kernel.org/lkml/20241104-am62-lpm-usb-fix-v1-1-e93df73a4...@kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2090811/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073726] Re: [g700][g510] ltp: cpuhotplug04: cause cpu stuck
this will be fixed in tfa firmware, so all the devices in the lab will need to be upgraded to the latest boot asset. ** Changed in: linux-mtk (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-mtk (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mtk in Ubuntu. https://bugs.launchpad.net/bugs/2073726 Title: [g700][g510] ltp: cpuhotplug04: cause cpu stuck Status in linux-mtk package in Ubuntu: Fix Committed Status in linux-mtk source package in Jammy: Fix Committed Bug description: [Summary] ubuntu_ltp: cpuhotplug04 cause cpu stuck [Steps to reproduce] on the dut: 1. git clone -b sru https://git.launchpad.net/~canonical-kernel-team/+git/ltp 2. sed -i /ntfs/d lib/tst_supported_fs_types.c 3. make autotools 4. ./configure 5. make -j8 6. make install 7. cpuhotplug04.sh [Expected result] should not cause any cpu stuck on the device stdout -- [15836.753391] Detected VIPT I-cache on CPU0 [15836.753486] GICv3: CPU0: found redistributor 0 region 0:0x0c04 [15836.753594] CPU0: Booted secondary processor 0x00 [0x412fd050] [15836.837674] Detected VIPT I-cache on CPU1 [15836.837766] GICv3: CPU1: found redistributor 100 region 0:0x0c06 [15836.837867] CPU1: Booted secondary processor 0x000100 [0x412fd050] [15836.949579] Detected VIPT I-cache on CPU2 [15836.949670] GICv3: CPU2: found redistributor 200 region 0:0x0c08 [15836.949769] CPU2: Booted secondary processor 0x000200 [0x412fd050] [15837.077602] Detected VIPT I-cache on CPU3 [15837.077695] GICv3: CPU3: found redistributor 300 region 0:0x0c0a [15837.077794] CPU3: Booted secondary processor 0x000300 [0x412fd050] [15837.209589] Detected VIPT I-cache on CPU4 [15837.209682] GICv3: CPU4: found redistributor 400 region 0:0x0c0c [15837.209779] CPU4: Booted secondary processor 0x000400 [0x412fd050] [15837.361596] Detected VIPT I-cache on CPU5 [15837.361693] GICv3: CPU5: found redistributor 500 region 0:0x0c0e [15837.361792] CPU5: Booted secondary processor 0x000500 [0x412fd050] [15837.481570] Detected PIPT I-cache on CPU6 [15837.481620] GICv3: CPU6: found redistributor 600 region 0:0x0c10 [15837.481668] CPU6: Booted secondary processor 0x000600 [0x411fd410] [15837.702608] migrate_one_irq: 46 callbacks suppressed [15837.702637] IRQ357: set affinity failed(-22). [15837.702662] IRQ359: set affinity failed(-22). [15837.703122] psci: CPU0 killed (polled 0 ms) [15837.806566] IRQ357: set affinity failed(-22). [15837.806605] IRQ359: set affinity failed(-22). [15837.807839] psci: CPU1 killed (polled 0 ms) [15837.902513] IRQ357: set affinity failed(-22). [15837.902553] IRQ359: set affinity failed(-22). [15837.903546] psci: CPU2 killed (polled 0 ms) [15837.998499] IRQ357: set affinity failed(-22). [15837.998539] IRQ359: set affinity failed(-22). [15837.999630] psci: CPU3 killed (polled 0 ms) [15838.102372] IRQ357: set affinity failed(-22). [15838.102414] IRQ359: set affinity failed(-22). [15838.105003] psci: CPU4 killed (polled 0 ms) [15838.183032] psci: CPU5 killed (polled 0 ms) [15838.242077] psci: CPU6 killed (polled 0 ms) [15838.297405] Detected VIPT I-cache on CPU0 [15838.297495] GICv3: CPU0: found redistributor 0 region 0:0x0c04 [15838.297602] CPU0: Booted secondary processor 0x00 [0x412fd050] [15838.377724] Detected VIPT I-cache on CPU1 [15838.377811] GICv3: CPU1: found redistributor 100 region 0:0x0c06 [15838.377910] CPU1: Booted secondary processor 0x000100 [0x412fd050] [15838.501585] Detected VIPT I-cache on CPU2 [15838.501674] GICv3: CPU2: found redistributor 200 region 0:0x0c08 [15838.501772] CPU2: Booted secondary processor 0x000200 [0x412fd050] [15838.613485] Detected VIPT I-cache on CPU3 [15838.613579] GICv3: CPU3: found redistributor 300 region 0:0x0c0a [15838.613678] CPU3: Booted secondary processor 0x000300 [0x412fd050] [15838.729502] Detected VIPT I-cache on CPU4 [15838.729598] GICv3: CPU4: found redistributor 400 region 0:0x0c0c [15838.729695] CPU4: Booted secondary processor 0x000400 [0x412fd050] [15838.849676] Detected VIPT I-cache on CPU5 [15838.849770] GICv3: CPU5: found redistributor 500 region 0:0x0c0e [15838.849870] CPU5: Booted secondary processor 0x000500 [0x412fd050] [15838.961563] Detected PIPT I-cache on CPU6 [15838.961612] GICv3: CPU6: found redistributor 600 region 0:0x0c10 [15838.961660] CPU6: Booted secondary processor 0x000600 [0x411fd410] [15839.158442] psci: CPU0 killed (polled 0 ms) [15839.242999] psci: CPU1 killed (polled 0 ms) [15839.343828] psci: CPU2 killed (polled 0 ms) [15839.447677] psci
[Kernel-packages] [Bug 2077287] Re: [SRU]Fail to locate the LED of NVME disk behind Intel VMD
the schedule at kernel.ubuntu.com shows that this should release this week unless there's a priority that causes a slip. So unless something bad happens, the update for 24.04 should be released later this week. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077287 Title: [SRU]Fail to locate the LED of NVME disk behind Intel VMD Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Released Bug description: [Impact] Failed to locate the LED of nvme device behing Intel VMD via below command # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only [Test Plan] 1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD 2. Upgrade the kernel to 6.8.0-40 and install ledmon package 3. Locate the LED of nvme device behing Intel VMD via below command # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only [Fix] After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue. [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085018] Re: Commit "net/mlx5e: Don't offload internal port if filter device is out device" breaks OpenStack/OVN distributed gateway use case
I submitted the fix patch to the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2024-December/155739.html.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2085018
Title:
Commit "net/mlx5e: Don't offload internal port if filter device is out
device" breaks OpenStack/OVN distributed gateway use case
Status in linux package in Ubuntu:
Invalid
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Bug description:
Consider a topology with two chassis, A and B:
* A acts as a distributed gateway connected to provider network on tagged
VLAN and has GENEVE tunnel configured towards chassis B.
* B hosts the target instance.
* From a third machine connected to the provider network we can observe:
* Only first ICMP ECHO reply from target instance is forwarded.
* Attempt to establish TCP connection fails.
If we revert commit [0] the symptoms disappear.
The issue is also present in the most recent mainline version
available, so there does not appear to exist a fix for the issue.
0: 06b4eac9c4be ("net/mlx5e: Don't offload internal port if filter
device is out device")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085018/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046572] Re: NFS latency spikes during openat syscalls associated with test_stateid RPC command
We're getting more diagnostics in 24.04 at least: [1734089.971392] NFS call test_stateid 15aeffc7 [1734089.971395] --> nfs41_call_sync_prepare data->seq_server e7ef3825 [1734089.971398] --> nfs4_alloc_slot used_slots= highest_used=4294967295 max_slots=31 [1734089.971401] <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0 [1734089.971405] encode_sequence: sessionid=1732546958:2952628455:4:0 seqid=79117276 slotid=0 max_slotid=0 cache_this=0 [1734089.971525] nfs41_handle_sequence_flag_errors: "redacted" (client ID 8e914467e788fdaf) flags=0x0040 [1734089.971531] --> nfs4_alloc_slot used_slots=0001 highest_used=0 max_slots=31 [1734089.971534] <-- nfs4_alloc_slot used_slots=0003 highest_used=1 slotid=1 [1734089.971537] nfs4_free_slot: slotid 1 highest_used_slotid 0 [1734089.971540] nfs41_sequence_process: Error 0 free the slot [1734089.971543] nfs4_free_slot: slotid 0 highest_used_slotid 4294967295 [1734089.971548] NFS reply test_stateid: succeeded, 0 [1734089.971552] NFS call test_stateid 15aeffc7 [1734089.971556] --> nfs41_call_sync_prepare data->seq_server e7ef3825 [1734089.971559] --> nfs4_alloc_slot used_slots= highest_used=4294967295 max_slots=31 [1734089.971562] <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0 [1734089.971567] encode_sequence: sessionid=1732546958:2952628455:4:0 seqid=79117277 slotid=0 max_slotid=0 cache_this=0 [1734089.971679] nfs41_handle_sequence_flag_errors: "redacted" (client ID 8e914467e788fdaf) flags=0x0040 [1734089.971685] --> nfs4_alloc_slot used_slots=0001 highest_used=0 max_slots=31 [1734089.971689] <-- nfs4_alloc_slot used_slots=0003 highest_used=1 slotid=1 [1734089.971692] nfs4_free_slot: slotid 1 highest_used_slotid 0 [1734089.971695] nfs41_sequence_process: Error 0 free the slot [1734089.971697] nfs4_free_slot: slotid 0 highest_used_slotid 4294967295 [1734089.971703] NFS reply test_stateid: succeeded, 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046572 Title: NFS latency spikes during openat syscalls associated with test_stateid RPC command Status in linux package in Ubuntu: Confirmed Bug description: About once a week the NFS mounts on our eda servers (the nfs clients) slow to a crawl for a large number of workloads. strace reveals that openat system calls for files in the mounts take between 0.1 and 0.3 seconds this can be seen directly by touching any file in the homedir (this normally takes 0.001-0.002 seconds). This causes obvious problems, an IPython instance in a conda environment installed in NFS takes around 2-3 minutes to start for example. I originally thought that this was a manifestation of #2009325, but we are on 5.15.0-89 and have seen this problem across several kernel versions. Additionally we don't see access rpc calls but we do see loads of test_stateid calls: - bursts of 300 or so periodically every couple seconds while idle - 380,452 test_stateid calls when an ipython instance is starting (zero access calls in the same period, when at idle we see 10,267 test_stateid calls over the same ~2:30 time period and again no access calls) We're not using kerberos, just ip based authentication, our mount options are: exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146) We see this on servers with both linux-image-5.15.0-89-generic and linux-headers-5.15.0-83-generic, and have seen it across a few versions (we have the hwe stack installed if that matters). I could upgrade them to 91 but the issue clears after a reboot and we don't have a reliable way to reproduce it so I'm going to keep one online for debugging. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3334 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-04-05 (618 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IwConfig: lono wireless extensions. enp69s0 no wireless extensions. enp68s0 no wireless extensions. MachineType: ASUS System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force fsck.repair=yes ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 PulseList: Error: command ['pacmd', 'list'] failed with exi
[Kernel-packages] [Bug 2084052] Re: RDMA/mana_ib patches
** Tags removed: verification-needed-oracular-linux-azure ** Tags added: verification-done-oracular-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2084052 Title: RDMA/mana_ib patches Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Noble: Fix Released Status in linux-azure source package in Oracular: Fix Committed Bug description: SRU Justification [Impact] * Microsoft requested backport of multiple RDMA/mana patches [Fix] * Clean cherry-pick 4a3b99bc04e5: "RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page" for all releases * Clean cherry-pick 9e517a8e9d9a: "RDMA/mana_ib: use the correct page table index based on hardware page size" for Oracular and Noble, simple backport required for Jammy [Test Plan] * Compile tested * Boot tested * Tested by Microsoft [Regression potential] * Changes isolated, minimal regression risk. Changes already backported as of 6.11 [Other info] * SF #00398680 * SF #00398679 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2084052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086863] Re: Azure: miscellaneous MANA fixes for Oracular/Noble
This bug is awaiting verification that the linux-azure/6.8.0-1019.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-azure-v2
verification-needed-noble-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2086863
Title:
Azure: miscellaneous MANA fixes for Oracular/Noble
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-azure source package in Noble:
Fix Committed
Status in linux-azure source package in Oracular:
Fix Committed
Bug description:
[Impact]
Microsoft has requested backports for the following bugfixes:
58a63729c957 ("net: mana: Fix doorbell out of order violation and avoid
unnecessary doorbell rings")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=58a63729c957
3410d0e14f9a ("net: mana: Implement get_ringparam/set_ringparam for mana")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3410d0e14f9a
1705341485ff ("net: mana: Improve mana_set_channels() in low mem conditions")
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=1705341485ff
[Fix]
58a63729c957 ("net: mana: Fix doorbell out of order violation and avoid
unnecessary doorbell rings")
- jammy, oracular: already in the tree
- noble: cherry-pick
3410d0e14f9a ("net: mana: Implement get_ringparam/set_ringparam for mana")
- oracular, noble: cherry-pick
- jammy: backported
1705341485ff ("net: mana: Improve mana_set_channels() in low mem conditions")
- oracular, noble: cherry-pick
- jammy: backported
[Test plan]
Compile tested only.
[Where problems could occur]
The fixes are relatively small and self-contained, so the regression
risk seems low; however, issues with them would cause degraded network
operation on machines using the MANA ethernet drivers.
[Other info]
SF #00396267
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2086863/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2087886] Re: MGLRU: kswapd uses 100% CPU when MGLRU is enabled and under memory pressure
This bug is awaiting verification that the linux/6.11.0-13.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-oracular-linux' to 'verification-done-oracular- linux'. If the problem still exists, change the tag 'verification- needed-oracular-linux' to 'verification-failed-oracular-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-oracular-linux-v2 verification-needed-oracular-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2087886 Title: MGLRU: kswapd uses 100% CPU when MGLRU is enabled and under memory pressure Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2087886 [Impact] On systems with MGLRU enabled, which it is by default, if the system is under memory pressure, and some pages are then allocated, such that it wakes up kswapd to attempt page reclaim, but the system has enough memory that kswapd doesn't get OOM killed, and then there are no pages to actually reclaim, kswapd can spin at 100% endlessly, causing severe performance issues. What's happening is that lru_gen_shrink_node() unconditionally clears kswapd_failures, which can prevent kswapd from sleeping and cause 100% kswapd cpu usage even when kswapd repeatedly fails to make progress in reclaim. A workaround is to disable MGLRU, and the issue does not occur. [Fix] The fix is to only clear kswap_failures in lru_gen_shrink_node() if reclaim makes some progress, similar to shrink_node(). This was fixed in 6.12-rc4 by the commit: commit b130ba4a6259f6b64d8af15e9e7ab1e912bcb7ad Author: Wei Xu Date: Mon Oct 14 22:12:11 2024 + Subject: mm/mglru: only clear kswapd_failures if reclaimable Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b130ba4a6259f6b64d8af15e9e7ab1e912bcb7ad Both Noble and Oracular need this fix. [Testcase] The systems with this issue are DPDK compute nodes running OpenStack Yoga on Jammy. If you leave them for several days, they will hit this issue and their kswap processes will go to 100% and never drop. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 846 root 20 0 0 0 0 R 100.0 0.0 1915:16 kswapd0 846 root 20 0 0 0 0 R 100.0 0.0 1915:16 kswapd0 846 root 20 0 0 0 0 R 100.0 0.0 1915:17 kswapd0 846 root 20 0 0 0 0 R 99.0 0.0 1915:18 kswapd0 If you disable MGLRU however, they drop to 0% and sleep immediately. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf390959-test If you install the test kernel, the system should remain stable, and kswapd will not go to 100% cpu after some time. [Where problems could occur] We are adding a small requirement to clearing kswapd_failures, that we actually reclaim some memory. If we do actually reclaim some memory, the behaviour is the same as what we have now, we clear kswapd_failures and continue. If we don't manage to reclaim any memory, we leave kswapd_failures as is, and let kswapd sleep, to try again at a later time. If a regression were to occur, it would affect MGLRU users, which is the default. A regression would look like issues with kswapd memory reclaim, or lead to high cpu usage with kswapd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2087886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084513] Re: Navi24 RX6300 light up issue on 6.8 kernel
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084513
Title:
Navi24 RX6300 light up issue on 6.8 kernel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Bug description:
[Impact]
Navi24 (specific customer SKU of RX6300) had problems with lighting up
display on 6.8 kernel.
[Fix]
Mario@AMD looked at issue and it is caused by this commit in 6.8-rc1:
e57cd73f971194e94bc42d57b9fcb184c93a8754 drm/amd/display: Optimize
fast validation cases
It has been fixed by this commit in 6.9-rc1:
f0ec30549a2b ("drm/amd/display: Ensure populate uclk in bb
construction")
[Test]
Boot up the machine with AMD RX6300 gfx, it should display well.
[Where problems could occur]
The patch modifies how optimal DCFCLK (display controller fabric clock) and
UCLK (memory clock) values are calculated and paired. This could potentially
lead to suboptimal clock settings in some scenarios, especially for low
bandwidth cases. The comment mentions this is specifically needed for DCN303
due to low memory bandwidth, but it may have unintended consequences for other
configurations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2084513/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2089889] Re: Fix Mic Mute LED no function on HP laptops with Cirrus amplifier
** Tags added: jira-stella-154 oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2089889 Title: Fix Mic Mute LED no function on HP laptops with Cirrus amplifier Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Triaged Status in linux-oem-6.11 source package in Noble: In Progress Status in linux source package in Oracular: Triaged Status in linux-oem-6.11 source package in Oracular: New Status in linux source package in Plucky: Triaged Status in linux-oem-6.11 source package in Plucky: New Bug description: [SRU Justifications] [Impact] Audio mic mute function works OK but the LED does not toggle accordingly. [Fix] This requires the upstream commit https://lore.kernel.org/all/20240829161114.140938-1-sim...@opensource.cirrus.com/ from Cirrus. And additional quirk for specific HP SSIDs are required for working mic-mute led. [Test Case] 1. Boot up the HP ZBook series laptops with Audio codec + Cirrus amplifier 2. Press the Mic Mute function key (F9) and check the mic mute function 3. Check if the LED (on F9) is ON when Mic Mute, and OFF when Mic not muted. [Where problems could occur] The auto-detection patch is looking for cs35l56 variants in ACPI. Cirrus claims it should cover Machu, Lapaz and Colosseum on HP laptops to get the HDA codec automatically work with the amplifier. The only thing need to be quirked is for mic-mute LED. It only applies on particular HP models and shouldn't introduce regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2089889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2089885] Re: Support for Cirrus codec on Tarako RPL/ARL platform
** Tags added: jira-somerville-1163 oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2089885 Title: Support for Cirrus codec on Tarako RPL/ARL platform Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in firmware-sof source package in Noble: New Status in firmware-sof source package in Oracular: New Status in firmware-sof source package in Plucky: New Bug description: This requires the kernel to be based on 6.11 with following patches * linux - sof driver for Intel ArrowLake platform - Need the following patches from upstream from RPL https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=b27404b2bbf951a11500525dea15681cc970226c https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=d2234596be2192d9c1ae34f8c7534531191bc433 https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=1f3662838a05f1ab6af89a417f6f252d91d0806b https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=9307694f340e518cac0e007f39dd9ff0736e6144 https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=5afc29ba44fdd1bcbad4e07246c395d946301580 https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=af23d38caae5841bd7aa754a7e7205ab719f568d https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=e9db1b551774037ebe39dde4a658d89ba95e260b * firmware-sof - sof-tplg/sof-rpl-cs42l43-l0.tplg and sof-arl.ri are required for RPL/ARL platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2089885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046572] Re: NFS latency spikes during openat syscalls associated with test_stateid RPC command
Yeah we're still hitting this in 24.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046572 Title: NFS latency spikes during openat syscalls associated with test_stateid RPC command Status in linux package in Ubuntu: Confirmed Bug description: About once a week the NFS mounts on our eda servers (the nfs clients) slow to a crawl for a large number of workloads. strace reveals that openat system calls for files in the mounts take between 0.1 and 0.3 seconds this can be seen directly by touching any file in the homedir (this normally takes 0.001-0.002 seconds). This causes obvious problems, an IPython instance in a conda environment installed in NFS takes around 2-3 minutes to start for example. I originally thought that this was a manifestation of #2009325, but we are on 5.15.0-89 and have seen this problem across several kernel versions. Additionally we don't see access rpc calls but we do see loads of test_stateid calls: - bursts of 300 or so periodically every couple seconds while idle - 380,452 test_stateid calls when an ipython instance is starting (zero access calls in the same period, when at idle we see 10,267 test_stateid calls over the same ~2:30 time period and again no access calls) We're not using kerberos, just ip based authentication, our mount options are: exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146) We see this on servers with both linux-image-5.15.0-89-generic and linux-headers-5.15.0-83-generic, and have seen it across a few versions (we have the hwe stack installed if that matters). I could upgrade them to 91 but the issue clears after a reboot and we don't have a reliable way to reproduce it so I'm going to keep one online for debugging. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3334 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-04-05 (618 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IwConfig: lono wireless extensions. enp69s0 no wireless extensions. enp68s0 no wireless extensions. MachineType: ASUS System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force fsck.repair=yes ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-89-generic N/A linux-backports-modules-5.15.0-89-generic N/A linux-firmware 1.187.39 RfKill: Tags: focal Uname: Linux 5.15.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046572] Re: NFS latency spikes during openat syscalls associated with test_stateid RPC command
Yup we're still hitting this in 24.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046572 Title: NFS latency spikes during openat syscalls associated with test_stateid RPC command Status in linux package in Ubuntu: Confirmed Bug description: About once a week the NFS mounts on our eda servers (the nfs clients) slow to a crawl for a large number of workloads. strace reveals that openat system calls for files in the mounts take between 0.1 and 0.3 seconds this can be seen directly by touching any file in the homedir (this normally takes 0.001-0.002 seconds). This causes obvious problems, an IPython instance in a conda environment installed in NFS takes around 2-3 minutes to start for example. I originally thought that this was a manifestation of #2009325, but we are on 5.15.0-89 and have seen this problem across several kernel versions. Additionally we don't see access rpc calls but we do see loads of test_stateid calls: - bursts of 300 or so periodically every couple seconds while idle - 380,452 test_stateid calls when an ipython instance is starting (zero access calls in the same period, when at idle we see 10,267 test_stateid calls over the same ~2:30 time period and again no access calls) We're not using kerberos, just ip based authentication, our mount options are: exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146) We see this on servers with both linux-image-5.15.0-89-generic and linux-headers-5.15.0-83-generic, and have seen it across a few versions (we have the hwe stack installed if that matters). I could upgrade them to 91 but the issue clears after a reboot and we don't have a reliable way to reproduce it so I'm going to keep one online for debugging. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3334 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-04-05 (618 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IwConfig: lono wireless extensions. enp69s0 no wireless extensions. enp68s0 no wireless extensions. MachineType: ASUS System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force fsck.repair=yes ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-89-generic N/A linux-backports-modules-5.15.0-89-generic N/A linux-firmware 1.187.39 RfKill: Tags: focal Uname: Linux 5.15.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/6.8.0-1019.22)
All autopkgtests for the newly accepted linux-meta-azure (6.8.0-1019.22) for noble have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.39-0ubuntu8.3 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/noble/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-6.8/6.8.0-1019.22~22.04.1)
All autopkgtests for the newly accepted linux-meta-azure-6.8 (6.8.0-1019.22~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: fwts/22.03.00-0ubuntu1 (arm64) linux-azure-6.8/6.8.0-1019.22~22.04.1 (arm64) wireguard-linux-compat/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure-6.8 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2090981] [NEW] [g1200-evk] Call trace appeared when reload mtk_mdp3 module
Public bug reported: Test steps: 1. modprobe -r mtk_mdp3 2. modprobe mtk_mdp3 # modprobe mtk_mdp3 [ 4729.890621] kobject_add_internal failed for hdmirxswitch with -EEXIST, don't try to register things with the same n ame in the same directory. [ 4729.892417] kobject_add_internal failed for hdmirxaud with -EEXIST, don't try to register things with the same name in the same directory. [ 4729.894397] kobject_add_internal failed for hdmirx with -EEXIST, don't try to register things with the same name in the same directory. [ 4729.898123] debugfs: File 'hdmirx' in directory '/' already present! [ 4729.908381] mtk-mdp3 14001000.mdp3-rdma0: failed to request channel [ 4729.909295] Unable to handle kernel paging request at virtual address fff0 [ 4729.910302] Mem abort info: [ 4729.910658] ESR = 0x9604 [ 4729.911135] EC = 0x25: DABT (current EL), IL = 32 bits [ 4729.911819] SET = 0, FnV = 0 [ 4729.912208] EA = 0, S1PTW = 0 [ 4729.912606] FSC = 0x04: level 0 translation fault [ 4729.913224] Data abort info: [ 4729.913590] ISV = 0, ISS = 0x0004 [ 4729.914075] CM = 0, WnR = 0 [ 4729.914452] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f16ee000 [ 4729.915301] [fff0] pgd=, p4d= [ 4729.916166] Internal error: Oops: 9604 [#1] PREEMPT SMP [ 4729.916962] Modules linked in: mtk_mdp3(E+) mtk_scp(E) mtk_rpmsg(E) mtk_scp_ipi(E) mtk_hdmirx(E) algif_hash(E) algi f_skcipher(E) af_alg(E) bnep(E) binfmt_misc(E) apusys(E) mtk_jpeg(E) mtk_vcodec_enc_v1_mt8395(E) nls_iso8859_1(E) btus b(E) apu_top(E) btrtl(E) mtk_vcodec_dec_v1_mt8395(E) mtk_vcu_mt8395(E) btbcm(E) mtk_vcodec_common_mt8395(E) btintel(E) joydev(E) btmtk(E) bluetooth(E) ecdh_generic(E) ecc(E) mt7921e(E) mt6360_adc(E) mt7921_common(E) industrialio_trigger ed_buffer(E) kfifo_buf(E) v4l2_mem2mem(E) videobuf2_dma_contig(E) industrialio(E) mt76_connac_lib(E) videobuf2_memops( E) videobuf2_v4l2(E) mt76(E) videobuf2_common(E) tcpci_mt6360(E) tcpci(E) tcpm(E) it5205fn(E) videodev(E) mac80211(E) typec(E) mc(E) cfg80211(E) libarc4(E) usb_conn_gpio(E) mcp251xfd(E) can_dev(E) pwm_mtk_disp(E) optee(E) pwm_mediatek(E ) tee(E) uio_pdrv_genirq(E) uio(E) sch_fq_codel(E) dm_multipath(E) scsi_dh_rdac(E) scsi_dh_emc(E) scsi_dh_alua(E) dma_ buf_test_exporter(E) efi_pstore(E) ip_tables(E) x_tables(E) [ 4729.917018] autofs4(E) [ 4729.917503] mtk-scp 1050.scp: creating channel cros-ec-rpmsg addr 0xd [ 4729.917556] mtk-scp 1050.scp: SCP is ready. FW version cherry_scp_v2.0.21051-de9944a9e [ 4729.917560] remoteproc remoteproc0: remote processor scp is now up [ 4729.928029] btrfs(E) blake2b_generic(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) xor_neon(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) multipath(E) linea r(E) crct10dif_ce(E) ghash_ce(E) sha2_ce(E) sha256_arm64(E) sha1_ce(E) mediatek_drm_hdmi(E) realtek(E) phy_mtk_hdmi_dr v(E) dwmac_mediatek(E) stmmac_platform(E) stmmac(E) pcs_xpcs(E) phylink(E) spidev(E) mtk_rng(E) mtk_pmic_keys(E) gpio_ keys(E) pwm_bl(E) aes_neon_blk(E) crypto_simd(E) cryptd(E) aes_ce_cipher(E) [last unloaded: mtk_rpmsg] [ 4729.937370] CPU: 7 PID: 1588 Comm: modprobe Tainted: G E 5.15.152+ #6 [ 4729.938351] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2022.10 10/01/2022 [ 4729.939407] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4729.940289] pc : mtk_mutex_put+0x1c/0x50 [ 4729.940795] lr : mdp_probe+0x490/0x684 [mtk_mdp3] [ 4729.941403] sp : 8bcf38b0 [ 4729.941823] x29: 8bcf38b0 x28: 81b21598 x27: 81b215b8 [ 4729.942729] x26: 81b215d8 x25: 81b214f8 x24: 0005 [ 4729.943634] x23: c1145410 x22: fff0 x21: 0005 [ 4729.944538] x20: fff0 x19: fff0 x18: [ 4729.945443] x17: 00040044 x16: 8be1f000 x15: c8f0f850 [ 4729.946347] x14: x13: x12: 0001 [ 4729.947252] x11: 0002 x10: 0010 x9 : 81b07850 [ 4729.948156] x8 : 0004 x7 : d7c69010 x6 : 89b84000 [ 4729.949061] x5 : 88b9ad90 x4 : fc00037dc120 x3 : 802f [ 4729.949965] x2 : x1 : 0009 x0 : fff0 [ 4729.950869] Call trace: [ 4729.951181] mtk_mutex_put+0x1c/0x50 [ 4729.951638] mdp_probe+0x490/0x684 [mtk_mdp3] [ 4729.952197] platform_probe+0x70/0x110 [ 4729.952678] really_probe+0xd0/0x490 [ 4729.953134] __driver_probe_device+0x148/0x190 [ 4729.953701] driver_probe_device+0x48/0x180 [ 4729.954234] __driver_attach+0x104/0x240 [ 4729.954735] bus_for_each_dev+0x78/0xd0 [ 4729.955223] driver_attach+0x2c/0x40 [ 4729.955679] bus_add_driver+0x154/0x270 [ 4729.956168] driver_register+0x80/0x13c [ 4729.956657] __platform_driver_register+0x30/0x40 [ 4729.957257] mdp_driver_init+0x2c/0x1000 [mtk
[Kernel-packages] [Bug 2090980] [NEW] [g1200-evk] Call trace appeared when reload mtk_mdp3 module
Public bug reported: Test steps: 1. modprobe -r mtk_mdp3 2. modprobe mtk_mdp3 # modprobe mtk_mdp3 [ 4729.890621] kobject_add_internal failed for hdmirxswitch with -EEXIST, don't try to register things with the same n ame in the same directory. [ 4729.892417] kobject_add_internal failed for hdmirxaud with -EEXIST, don't try to register things with the same name in the same directory. [ 4729.894397] kobject_add_internal failed for hdmirx with -EEXIST, don't try to register things with the same name in the same directory. [ 4729.898123] debugfs: File 'hdmirx' in directory '/' already present! [ 4729.908381] mtk-mdp3 14001000.mdp3-rdma0: failed to request channel [ 4729.909295] Unable to handle kernel paging request at virtual address fff0 [ 4729.910302] Mem abort info: [ 4729.910658] ESR = 0x9604 [ 4729.911135] EC = 0x25: DABT (current EL), IL = 32 bits [ 4729.911819] SET = 0, FnV = 0 [ 4729.912208] EA = 0, S1PTW = 0 [ 4729.912606] FSC = 0x04: level 0 translation fault [ 4729.913224] Data abort info: [ 4729.913590] ISV = 0, ISS = 0x0004 [ 4729.914075] CM = 0, WnR = 0 [ 4729.914452] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f16ee000 [ 4729.915301] [fff0] pgd=, p4d= [ 4729.916166] Internal error: Oops: 9604 [#1] PREEMPT SMP [ 4729.916962] Modules linked in: mtk_mdp3(E+) mtk_scp(E) mtk_rpmsg(E) mtk_scp_ipi(E) mtk_hdmirx(E) algif_hash(E) algi f_skcipher(E) af_alg(E) bnep(E) binfmt_misc(E) apusys(E) mtk_jpeg(E) mtk_vcodec_enc_v1_mt8395(E) nls_iso8859_1(E) btus b(E) apu_top(E) btrtl(E) mtk_vcodec_dec_v1_mt8395(E) mtk_vcu_mt8395(E) btbcm(E) mtk_vcodec_common_mt8395(E) btintel(E) joydev(E) btmtk(E) bluetooth(E) ecdh_generic(E) ecc(E) mt7921e(E) mt6360_adc(E) mt7921_common(E) industrialio_trigger ed_buffer(E) kfifo_buf(E) v4l2_mem2mem(E) videobuf2_dma_contig(E) industrialio(E) mt76_connac_lib(E) videobuf2_memops( E) videobuf2_v4l2(E) mt76(E) videobuf2_common(E) tcpci_mt6360(E) tcpci(E) tcpm(E) it5205fn(E) videodev(E) mac80211(E) typec(E) mc(E) cfg80211(E) libarc4(E) usb_conn_gpio(E) mcp251xfd(E) can_dev(E) pwm_mtk_disp(E) optee(E) pwm_mediatek(E ) tee(E) uio_pdrv_genirq(E) uio(E) sch_fq_codel(E) dm_multipath(E) scsi_dh_rdac(E) scsi_dh_emc(E) scsi_dh_alua(E) dma_ buf_test_exporter(E) efi_pstore(E) ip_tables(E) x_tables(E) [ 4729.917018] autofs4(E) [ 4729.917503] mtk-scp 1050.scp: creating channel cros-ec-rpmsg addr 0xd [ 4729.917556] mtk-scp 1050.scp: SCP is ready. FW version cherry_scp_v2.0.21051-de9944a9e [ 4729.917560] remoteproc remoteproc0: remote processor scp is now up [ 4729.928029] btrfs(E) blake2b_generic(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) xor_neon(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) multipath(E) linea r(E) crct10dif_ce(E) ghash_ce(E) sha2_ce(E) sha256_arm64(E) sha1_ce(E) mediatek_drm_hdmi(E) realtek(E) phy_mtk_hdmi_dr v(E) dwmac_mediatek(E) stmmac_platform(E) stmmac(E) pcs_xpcs(E) phylink(E) spidev(E) mtk_rng(E) mtk_pmic_keys(E) gpio_ keys(E) pwm_bl(E) aes_neon_blk(E) crypto_simd(E) cryptd(E) aes_ce_cipher(E) [last unloaded: mtk_rpmsg] [ 4729.937370] CPU: 7 PID: 1588 Comm: modprobe Tainted: G E 5.15.152+ #6 [ 4729.938351] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2022.10 10/01/2022 [ 4729.939407] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4729.940289] pc : mtk_mutex_put+0x1c/0x50 [ 4729.940795] lr : mdp_probe+0x490/0x684 [mtk_mdp3] [ 4729.941403] sp : 8bcf38b0 [ 4729.941823] x29: 8bcf38b0 x28: 81b21598 x27: 81b215b8 [ 4729.942729] x26: 81b215d8 x25: 81b214f8 x24: 0005 [ 4729.943634] x23: c1145410 x22: fff0 x21: 0005 [ 4729.944538] x20: fff0 x19: fff0 x18: [ 4729.945443] x17: 00040044 x16: 8be1f000 x15: c8f0f850 [ 4729.946347] x14: x13: x12: 0001 [ 4729.947252] x11: 0002 x10: 0010 x9 : 81b07850 [ 4729.948156] x8 : 0004 x7 : d7c69010 x6 : 89b84000 [ 4729.949061] x5 : 88b9ad90 x4 : fc00037dc120 x3 : 802f [ 4729.949965] x2 : x1 : 0009 x0 : fff0 [ 4729.950869] Call trace: [ 4729.951181] mtk_mutex_put+0x1c/0x50 [ 4729.951638] mdp_probe+0x490/0x684 [mtk_mdp3] [ 4729.952197] platform_probe+0x70/0x110 [ 4729.952678] really_probe+0xd0/0x490 [ 4729.953134] __driver_probe_device+0x148/0x190 [ 4729.953701] driver_probe_device+0x48/0x180 [ 4729.954234] __driver_attach+0x104/0x240 [ 4729.954735] bus_for_each_dev+0x78/0xd0 [ 4729.955223] driver_attach+0x2c/0x40 [ 4729.955679] bus_add_driver+0x154/0x270 [ 4729.956168] driver_register+0x80/0x13c [ 4729.956657] __platform_driver_register+0x30/0x40 [ 4729.957257] mdp_driver_init+0x2c/0x1000 [mtk
[Kernel-packages] [Bug 2090979] [NEW] Fail to detect card after unplugging DPoC cable and reboot
Public bug reported: [Summary] Fail to detect card after unplugging DPoC cable and reboot Still can reproduce the issue after upgrading kenrel to 5.15.0-1033-mtk [Steps to reproduce] 1. Flash image 2. Go to U-Boot shell and add display-dsidp.dtbo to list_dtbo 3. Reboot system with DPoC connected 4. Unplug DPoC cable and reboot system 5. Check if the card can be detected $ pactl list cards [Expected result] The card can be detected [Actual result] no card is detected [Failure rate] 100% [Additional information] SKU: G1200-evk P1V2, G510 Image: genio-classic-desktop-2204-20240322-185.tar.xz kernel-version: 5.15.0-1030-mtk --- The issue is gone after changing following values to default values. $ amixer -c 0 cset name='DPTX_OUT_MUX' 0 $ amixer -c 0 cset name='HDMI_OUT_MUX' 1 LP: #2079780 ** Affects: linux-mtk (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mtk in Ubuntu. https://bugs.launchpad.net/bugs/2090979 Title: Fail to detect card after unplugging DPoC cable and reboot Status in linux-mtk package in Ubuntu: New Status in linux-mtk source package in Jammy: New Bug description: [Summary] Fail to detect card after unplugging DPoC cable and reboot Still can reproduce the issue after upgrading kenrel to 5.15.0-1033-mtk [Steps to reproduce] 1. Flash image 2. Go to U-Boot shell and add display-dsidp.dtbo to list_dtbo 3. Reboot system with DPoC connected 4. Unplug DPoC cable and reboot system 5. Check if the card can be detected $ pactl list cards [Expected result] The card can be detected [Actual result] no card is detected [Failure rate] 100% [Additional information] SKU: G1200-evk P1V2, G510 Image: genio-classic-desktop-2204-20240322-185.tar.xz kernel-version: 5.15.0-1030-mtk --- The issue is gone after changing following values to default values. $ amixer -c 0 cset name='DPTX_OUT_MUX' 0 $ amixer -c 0 cset name='HDMI_OUT_MUX' 1 LP: #2079780 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2090979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2090978] [NEW] [g510] mt8188-mdla-devfreq probe failed message found in dmesg
Public bug reported: [Summary] mt8188-mdla-devfreq probe failed message found in dmesg [Steps to reproduce] 1. Install genio-core-22-20240617-112.img 2. Boot into OS and check if there's error message in dmesg or kern.log [Expected result] No error or failed message found in dmesg [Actual result] [ 13.657698] apu_top_3_init register rpmsg driver... [ 13.659594] apu_devfreq_init register mdla_devfreq platform driver... [ 13.659745] mtu3 11201000.usb1: xHCI platform device register success... [ 13.668520] [mt8188_apu_devfreq_cooling_register][238] dev_name(&pdev->dev) = soc:mdla_devfreq, dvfs_dev_id = 1 [ 13.668650] mt8188-mdla-devfreq soc:mdla_devfreq: _opp_is_duplicate: duplicate OPPs detected. Existing: freq: 7, volt: 80, enabled: 1. New: freq: 7, volt: 75, enabled: 1 [ 13.668658] [mt8188_apu_devfreq_cooling_register][296] dvfs_dev_id = 1, register cooling dev NG! [ 13.668662] mt8188-mdla-devfreq: probe of soc:mdla_devfreq failed with error -17 [ 13.674572] mtk-vdec-larb soc:vdec_l23: Adding to iommu group 2 [ 13.674655] [MTK_V4L2] level=0 mtk_vdec_larb_probe(),740: mtk_vdec_larb_probe enable larb 23, hw_id 1 [ 13.675522] mtk-vdec-larb soc:vdec_l21: Adding to iommu group 2 [ 13.685229] [MTK_V4L2] level=0 mtk_vdec_larb_probe(),740: mtk_vdec_larb_probe enable larb 21, hw_id 0 [Failure rate] 100% (1/1) [Additional information] CID: 202405-34023 SKU: G510 Image: genio-core-22-20240617-112.img kernel-version: 5.15.0-1032-mtk [Stage] Issue reported and logs collected right after it happened LP: #2069663 ** Affects: linux-mtk (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mtk in Ubuntu. https://bugs.launchpad.net/bugs/2090978 Title: [g510] mt8188-mdla-devfreq probe failed message found in dmesg Status in linux-mtk package in Ubuntu: New Status in linux-mtk source package in Jammy: New Bug description: [Summary] mt8188-mdla-devfreq probe failed message found in dmesg [Steps to reproduce] 1. Install genio-core-22-20240617-112.img 2. Boot into OS and check if there's error message in dmesg or kern.log [Expected result] No error or failed message found in dmesg [Actual result] [ 13.657698] apu_top_3_init register rpmsg driver... [ 13.659594] apu_devfreq_init register mdla_devfreq platform driver... [ 13.659745] mtu3 11201000.usb1: xHCI platform device register success... [ 13.668520] [mt8188_apu_devfreq_cooling_register][238] dev_name(&pdev->dev) = soc:mdla_devfreq, dvfs_dev_id = 1 [ 13.668650] mt8188-mdla-devfreq soc:mdla_devfreq: _opp_is_duplicate: duplicate OPPs detected. Existing: freq: 7, volt: 80, enabled: 1. New: freq: 7, volt: 75, enabled: 1 [ 13.668658] [mt8188_apu_devfreq_cooling_register][296] dvfs_dev_id = 1, register cooling dev NG! [ 13.668662] mt8188-mdla-devfreq: probe of soc:mdla_devfreq failed with error -17 [ 13.674572] mtk-vdec-larb soc:vdec_l23: Adding to iommu group 2 [ 13.674655] [MTK_V4L2] level=0 mtk_vdec_larb_probe(),740: mtk_vdec_larb_probe enable larb 23, hw_id 1 [ 13.675522] mtk-vdec-larb soc:vdec_l21: Adding to iommu group 2 [ 13.685229] [MTK_V4L2] level=0 mtk_vdec_larb_probe(),740: mtk_vdec_larb_probe enable larb 21, hw_id 0 [Failure rate] 100% (1/1) [Additional information] CID: 202405-34023 SKU: G510 Image: genio-core-22-20240617-112.img kernel-version: 5.15.0-1032-mtk [Stage] Issue reported and logs collected right after it happened LP: #2069663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2090978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085018] Re: Commit "net/mlx5e: Don't offload internal port if filter device is out device" breaks OpenStack/OVN distributed gateway use case
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.8 (Ubuntu Oracular)
Importance: Undecided
Status: New
** No longer affects: linux-hwe-6.8 (Ubuntu Oracular)
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2085018
Title:
Commit "net/mlx5e: Don't offload internal port if filter device is out
device" breaks OpenStack/OVN distributed gateway use case
Status in linux package in Ubuntu:
Invalid
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Bug description:
Consider a topology with two chassis, A and B:
* A acts as a distributed gateway connected to provider network on tagged
VLAN and has GENEVE tunnel configured towards chassis B.
* B hosts the target instance.
* From a third machine connected to the provider network we can observe:
* Only first ICMP ECHO reply from target instance is forwarded.
* Attempt to establish TCP connection fails.
If we revert commit [0] the symptoms disappear.
The issue is also present in the most recent mainline version
available, so there does not appear to exist a fix for the issue.
0: 06b4eac9c4be ("net/mlx5e: Don't offload internal port if filter
device is out device")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085018/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2090966] [NEW] Resume from suspend in unsuccessful (black screen)
Public bug reported: When resuming after suspending the computer, a black screen is present, with only a white cli cursor in the top right. The machine can still be accessed via SSH. 1) The release of Ubuntu you are using: 24.10 2) The version of the package you are using: nvidia 560 drivers 3) What you expected to happen: The computer to resume and get a GUI interface (login screen) 4) What happened instead: Black screen ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: nvidia-driver-560 560.35.03-0ubuntu5 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 4 00:47:52 2024 InstallationDate: Installed on 2024-11-30 (4 days ago) InstallationMedia: Ubuntu-Server 24.10 "Oracular Oriole" - Release amd64 (20241007.1) ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-560 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-560 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-560 in Ubuntu. https://bugs.launchpad.net/bugs/2090966 Title: Resume from suspend in unsuccessful (black screen) Status in nvidia-graphics-drivers-560 package in Ubuntu: New Bug description: When resuming after suspending the computer, a black screen is present, with only a white cli cursor in the top right. The machine can still be accessed via SSH. 1) The release of Ubuntu you are using: 24.10 2) The version of the package you are using: nvidia 560 drivers 3) What you expected to happen: The computer to resume and get a GUI interface (login screen) 4) What happened instead: Black screen ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: nvidia-driver-560 560.35.03-0ubuntu5 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 4 00:47:52 2024 InstallationDate: Installed on 2024-11-30 (4 days ago) InstallationMedia: Ubuntu-Server 24.10 "Oracular Oriole" - Release amd64 (20241007.1) ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-560 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-560/+bug/2090966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084059] Re: OVTI08F4:00: number of CSI2 data lanes 2 is not supported
Hello You-Sheng, or anyone else affected, Accepted ipu6-drivers into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202407190257.9369b88e-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ipu6-drivers (Ubuntu Oracular) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-oracular -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2084059 Title: OVTI08F4:00: number of CSI2 data lanes 2 is not supported Status in ipu6-drivers package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in ipu6-drivers source package in Noble: Won't Fix Status in linux source package in Noble: Won't Fix Status in linux-oem-6.11 source package in Noble: Fix Released Status in ipu6-drivers source package in Oracular: Fix Committed Status in linux source package in Oracular: Fix Committed Status in linux-oem-6.11 source package in Oracular: Invalid Status in ipu6-drivers source package in Plucky: Fix Released Status in linux source package in Plucky: In Progress Status in linux-oem-6.11 source package in Plucky: Invalid Bug description: [SRU Justification] [Impact] OVTI08F4 camera sensor is used in a different hardware config that is not currently supported: ``` $ sudo dmesg ... usbio-i2c usbio-i2c.3.auto: hid INTC10B6 uid VIC0 new uid1 ov08x40 i2c-OVTI08F4:00: number of CSI2 data lanes 2 is not supported ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -22 ov08x40 i2c-OVTI08F4:00: probe with driver ov08x40 failed with error -22 ``` [Fix] Proposed fix in: * https://github.com/intel/ipu6-drivers/pull/286 There are two parts. One in the kernel tree that is to be SRU-ed in this pull request. It adds two additional link frequencies so that ipu-bridge may probe this case. The other part is in the camera sensor driver itself that goes to ipu6-drivers. [Test Case] With patch applied, install kernel and intel-ipu6-dkms from -proposed pocket: ``` $ sudo dmesg ... intel_ipu7_psys.psys intel_ipu7.psys.40: psys probe minor: 0 intel_ipu7_isys.isys intel_ipu7.isys.40: bind ov08x40 14-0036 nlanes is 2 port is 0 intel_ipu7_isys.isys intel_ipu7.isys.40: All sensor registration completed. ``` Check if camera actually works: ``` $ sudo gst-launch-1.0 icamerasrc ! autovideosink ``` Full test plan is done via checkbox camera tests by multiple parties. [Where problems could occur] This is a new hardware configuration for OVTI08F4. Verified on both of the two equipped models being/been enabled. While we don't have much details about the differences in register contents, expect further issues if not covered by generic camera tests. [Other Info] So far this configuration is bound to Intel Lunar Lake platform that is only supported by v6.11 kernels and ipu6-drivers/oracular, ipu7/drivers/oracular. Nominate for linux/oracular, linux- oem-6.11/noble and linux-unstable-6.12. == original bug report == $ sudo dmesg|grep ov0 [4.793991] ov08x40 i2c-OVTI08F4:00: number of CSI2 data lanes 2 is not supported [4.793997] ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -22 [4.815076] ov08x40 i2c-OVTI08F4:00: probe with driver ov08x40 failed with error -22 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:gdm1400 F pipewire CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-10-18 (4 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) I
[Kernel-packages] [Bug 2085904] Re: Enable IOMMU Passthrough by default
** Tags removed: verification-done-jammy verification-needed-jammy-linux-gcp-6.8 ** Tags added: verification-done-jammy-linux-gcp-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2085904 Title: Enable IOMMU Passthrough by default Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: SRU Justification [Impact] C3 bare metal instances run into a problem on 6.8 kernels due to Intel IOMMU being enabled by default. After performing enough disk-intensive work on the instance, the system becomes unusable and reports I/O errors at the command line until rebooted, losing data in the process. The root issue is being worked on long-term, but in the meantime we will apply a workaround to the issue for affected customers. This fix has a negative impact on security, so it is limited to Jammy kernels for which this issue is a regression. Noble kernels have always had this problem and therefore will be waiting for the long-term fix. [Fix] Change the kernel config to use IOMMU passthrough by default. [Test Plan] Perform up to 50 kernel builds on the instance in sequence. Failures on affected instances are usually detected after only 1 or 2. [Regression potential] Regression potential is especially low for Jammy as we are essentially reverting a breaking change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2085904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2089699] Re: kernel:nft "Could not process rule: Device or resource busy" on unreferenced chain
We were able to reproduce this in the generic kernels, working on a potential fix now. ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gke (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2089699 Title: kernel:nft "Could not process rule: Device or resource busy" on unreferenced chain Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Jammy: In Progress Bug description: We see some nftables/netfilter problems after kernel upgrade from 5.15.0-1061-gke to 5.15.0-1067-gke. Correct transaction with nft fails with "Error: Could not process rule: Device or resource busy" which usually means a deleted chain is referenced, but you can see it's not. Full nft table dump + transaction + error is in the attached file. This is logs from kubernetes CI, which started failing immediately after mentioned kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2089699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 472183]
Knowing which software investments your company or business needs is
vital to make smart choices about purchasing such. Find out what can
help your business thrive by identifying which software you need, join
the free cpd course regarding this at the College of Contract
Management. Visit the website of UNICCM to get the full information on
how to join the live one up to two-hour broadcast.
https://www.uniccm.com/course/cpd-talks-unlock-profits-mastering-
software-investments
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/472183
Title:
Boot halts on Toshiba L505
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Won't Fix
Bug description:
Booting from live CD or installed system on Toshiba L505D-S5992 will
fail with message: '/sbin/modprobe -b acpi:lnxvideo:' unexpected exit
with status 0x0009. I can only boot by choosing the "acpi=off" option
for the live cd or by adding "acip=off" to the end of the kernel line
in /boot/grub/grub.cfg. This is with both 9.04 and 9.10.
Laptop has an ATI Radeon 4100/4200 video card (have seen both model
numbers listed in different locations).
lspci reports this for the video: 01:05.0 VGA compatible controller:
ATI Technologies Inc Device 9712
lspci -nn reports: 01:05.0 VGA compatible controller [0300]: ATI
Technologies Inc Device [1002:9712]
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mikep 1563 F knotify4
mikep 1586 F kmix
/dev/snd/controlC1: mikep 1586 F kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xd240 irq 5'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,1179ff12,0011
HDA:11c11040,11790001,00100200'
Controls : 17
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd231 irq 7'
Mixer name : 'ATI RS690/780 HDMI'
Components : 'HDA:1002791a,00791a00,0010'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [off]
Date: Mon Nov 2 19:48:31 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=092105e2-1654-41b1-bed8-4093e5be59da
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: TOSHIBA Satellite L505D
NonfreeKernelModules: fglrx
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic
root=UUID=56762fb6-1081-4c85-9699-604ec732ffd4 ro quiet splash acpi=off
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-14-generic N/A
linux-firmware 1.24
RfKill:
SourcePackage: linux
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(polkit-gnome-authentication-agent-1:1590): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
(npviewer.bin:1832): Gtk-WARNING **:
/usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
dmi.bios.date: 09/07/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.00
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias:
dmi:bvnInsydeCorp.:bvr1.00:bd09/07/2009:svnTOSHIBA:pnSatelliteL505D:pvrPSLV6U-00L001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.name: Satellite L505D
dmi.product.version: PSLV6U-00L001
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/472183/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2090983] [NEW] Phantom "Unknown Display" in Settings due to SimpleDRM dri node appears on *Intel* GPU machine
Public bug reported: I have the same symptom as LP: #2060268. That is, I have a phantom "Unknown Display" appear in Settings application, and there exists a dri node for SimpleDRM. $ ls -lh /dev/dri/by-path/ total 0 lrwxrwxrwx 1 root root 8 ธ.ค. 3 21:09 pci-:00:02.0-card -> ../card1 lrwxrwxrwx 1 root root 13 ธ.ค. 3 21:09 pci-:00:02.0-render -> ../renderD128 lrwxrwxrwx 1 root root 8 ธ.ค. 3 21:09 platform-simple-framebuffer.0-card -> ../card0 However, differently from the mentioned bug, this machine does NOT have an Nvidia card, nor does it have the Nvidia driver installed. This machine (which is a laptop) has an Intel integrated GPU, and seems to be covered by i915 in-tree kernel driver. `71-u-d-c-gpu-detection.rules` says that: # Remove SimpleDRM device when nvidia-drm loads. # This normally happens automatically for DRM devices that also register # a framebuffer device, but that's not the case yet for the nvidia driver. Which seems to imply that if a framebuffer device exist, SimpleDRM device node should go away on its own. And on my machine, framebuffer device do seem to exist (although, 2 of them?) $ ls -lh /dev/fb* crw-rw 1 root video 29, 0 ธ.ค. 3 21:09 /dev/fb0 crw-rw 1 root video 29, 1 ธ.ค. 3 21:09 /dev/fb1 Which is the reason I file this issue against Linux kernel. Currently, I worked around the issue by adapting a rule from `71-u-d-c- gpu-detection.rules` which remove the card0 node, but remove the `DRIVERS=="nvidia"` clause from the rule. This starts happening when I upgraded from Ubuntu 24.04 to 24.10 i.e. this is a regression. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-9-generic 6.11.0-9.9 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:peat 3644 F pipewire /dev/snd/controlC0: peat 3644 F pipewire peat 3653 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 12:15:43 2024 InstallationDate: Installed on 2024-07-23 (133 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Acer Swift SFG14-73 ProcEnviron: LANG=th_TH.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-9-generic root=UUID=5a221c16-5c14-405a-bffc-61598efc4ed7 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-9-generic N/A linux-backports-modules-6.11.0-9-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to oracular on 2024-11-03 (31 days ago) dmi.bios.date: 08/25/2024 dmi.bios.release: 1.14 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Goldfish_MTH dmi.board.vendor: MTL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd08/25/2024:br1.14:efr1.14:svnAcer:pnSwiftSFG14-73:pvrV1.14:rvnMTL:rnGoldfish_MTH:rvrV1.14:cvnAcer:ct10:cvrChassisVersion:sku: dmi.product.family: Swift Go 14 dmi.product.name: Swift SFG14-73 dmi.product.sku: dmi.product.version: V1.14 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2090983 Title: Phantom "Unknown Display" in Settings due to SimpleDRM dri node appears on *Intel* GPU machine Status in linux package in Ubuntu: New Bug description: I have the same symptom as LP: #2060268. That is, I have a phantom "Unknown Display" appear in Settings application, and there exists a dri node for SimpleDRM. $ ls -lh /dev/dri/by-path/ total 0 lrwxrwxrwx 1 root root 8 ธ.ค. 3 21:09 pci-:00:02.0-card -> ../card1 lrwxrwxrwx 1 root root 13 ธ.ค. 3 21:09 pci-:00:02.0-render -> ../renderD128 lrwxrwxrwx 1 root root 8 ธ.ค. 3 21:09 platform-simple-framebuffer.0-card -> ../card0 However, differently from the mentioned bug, this machine does NOT have an Nvidia card, nor does it have the Nvidia driver installed. This machine (which is a laptop) has an Intel integrated GPU, and seems to be covered by i915 in-tree kernel drive
[Kernel-packages] [Bug 2090982] [NEW] Prevent soft lockup on boot up
Public bug reported: [Impact] On system with cores > 200, printk during HMAT parsing can create soft lockup: [ 35.769351] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/0:1] [ 35.769354] Modules linked in: [ 35.769358] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.8.0-1009-nvidia-64k #9~22.04.1-Ubuntu [ 35.769360] Hardware name: NVIDIA PG548-C00/P4975, BIOS 02.02.02 20240729 [ 35.769362] pstate: 81001009 (Nzcv daif -PAN -UAO -TCO +DIT +SSBS BTYPE=--) [ 35.769364] pc : console_flush_all+0x1f0/0x3f0 [ 35.769375] lr : console_flush_all+0x1e8/0x3f0 [ 35.769376] sp : 800081b2f870 [ 35.769377] x29: 800081b2f870 x28: c06104152a10 x27: c06103390008 [ 35.769378] x26: 0001 x25: c06103da8a98 x24: [ 35.769380] x23: x22: 800081b2f990 x21: 800081b2f98f [ 35.769381] x20: c06104307160 x19: 0001 x18: [ 35.769382] x17: x16: x15: 6977646e61422073 [ 35.769384] x14: x13: 732f424d20303a5d x12: 39322d39325b7465 [ 35.769385] x11: 677261542d726f74 x10: 616974696e492020 x9 : c06100bf35c8 [ 35.769386] x8 : x7 : x6 : [ 35.769387] x5 : x4 : x3 : [ 35.769389] x2 : x1 : x0 : [ 35.769391] Call trace: [ 35.769393] console_flush_all+0x1f0/0x3f0 [ 35.769395] console_unlock+0x70/0x1f8 [ 35.769396] vprintk_emit+0x2e4/0x4b8 [ 35.769398] vprintk_default+0x40/0x80 [ 35.769399] vprintk+0x98/0x150 [ 35.769400] _printk+0x64/0xc0 [ 35.769405] hmat_parse_locality.constprop.0+0x1f4/0x740 [ 35.769416] hmat_parse_subtable+0x58/0xf0 [ 35.769418] acpi_parse_entries_array+0x1fc/0x360 [ 35.769426] acpi_table_parse_entries_array+0xa4/0x170 [ 35.769431] acpi_table_parse_entries+0x4c/0xa0 [ 35.769433] hmat_init+0x14c/0x440 [ 35.769434] do_one_initcall+0x4c/0x368 [ 35.769439] do_initcalls+0x134/0x2c0 [ 35.769442] kernel_init_freeable+0x128/0x2b0 [ 35.769443] kernel_init+0x38/0x240 [ 35.769451] ret_from_fork+0x10/0x20 [ 35.959318] acpi/hmat: Initiator-Target[29-30]:0 MB/s [ 35.964658] acpi/hmat: Initiator-Target[29-31]:0 MB/s [ 35.969997] acpi/hmat: Initiator-Target[29-32]:0 MB/s [ 35.975335] acpi/hmat: Initiator-Target[29-33]:0 MB/s [Fix] The information isn't that useful, lower the message level to pr_debug() to avoid the issue. [Test] Boot up the system and check dmesg. With the patch applied, no more HMAT spam can be found in kernel message. [Where problems could occur] There can be some obscure race conditions be exposed by booting the kernel faster. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2090982 Title: Prevent soft lockup on boot up Status in linux package in Ubuntu: Confirmed Bug description: [Impact] On system with cores > 200, printk during HMAT parsing can create soft lockup: [ 35.769351] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/0:1] [ 35.769354] Modules linked in: [ 35.769358] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.8.0-1009-nvidia-64k #9~22.04.1-Ubuntu [ 35.769360] Hardware name: NVIDIA PG548-C00/P4975, BIOS 02.02.02 20240729 [ 35.769362] pstate: 81001009 (Nzcv daif -PAN -UAO -TCO +DIT +SSBS BTYPE=--) [ 35.769364] pc : console_flush_all+0x1f0/0x3f0 [ 35.769375] lr : console_flush_all+0x1e8/0x3f0 [ 35.769376] sp : 800081b2f870 [ 35.769377] x29: 800081b2f870 x28: c06104152a10 x27: c06103390008 [ 35.769378] x26: 0001 x25: c06103da8a98 x24: [ 35.769380] x23: x22: 800081b2f990 x21: 800081b2f98f [ 35.769381] x20: c06104307160 x19: 0001 x18: [ 35.769382] x17: x16: x15: 6977646e61422073 [ 35.769384] x14: x13: 732f424d20303a5d x12: 39322d39325b7465 [ 35.769385] x11: 677261542d726f74 x10: 616974696e492020 x9 : c06100bf35c8 [ 35.769386] x8 : x7 : x6 : [ 35.769387] x5 : x4 : x3 : [ 35.769389] x2 : x1 : x0 : [ 35.769391] Call trace: [ 35.769393] console_flush_all+0x1f0/0x3f0 [ 35.769395] console_unlock+0x70/0x1f8 [ 35.769396] vprintk_emit+0x2e4/0x4b8 [ 35.769398] vprintk_default+0x40/0x80 [ 35.769399] vprintk+0x98/0x150 [ 35.769400] _printk+0x64/0xc0 [ 35.769405] hmat_parse_locality.constprop.0+0x1f4/0x740 [ 35.
