[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-kvm / L-kvm
** Summary changed: - ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm + ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-kvm / L-kvm ** Description changed: + (Thibf got this issue fixed for KVM kernels, for PPC please refer to bug + 2026592) + Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' - TAP version 13 - 1..1 - # selftests: ftrace: ftracetest - # === Ftrace unit tests === - # [1] Basic trace file check [PASS] - # [2] Basic test for tracers [PASS] - # [3] Basic trace clock test [PASS] - # [4] Basic event tracing check [PASS] - # [5] Change the ringbuffer size [PASS] - # [6] Snapshot and tracing setting [PASS] - # [7] trace_pipe and trace_marker[PASS] - # [8] Test ftrace direct functions against tracers [UNRESOLVED] - # [9] Test ftrace direct functions against kprobes [UNRESOLVED] - # [10] Generic dynamic event - add/remove eprobe events [PASS] - # [11] Generic dynamic event - add/remove kprobe events [PASS] - # [12] Generic dynamic event - add/remove synthetic events [PASS] - # [13] Generic dynamic event - selective clear (compatibility) [PASS] - # [14] Generic dynamic event - generic clear event [PASS] - # [15] Generic dynamic event - check if duplicate events are caught [FAIL] - # [16] event tracing - enable/disable with event level files [PASS] - # [17] event tracing - restricts events based on pid notrace filtering [PASS] - # [18] event tracing - restricts events based on pid [PASS] - # [19] event tracing - enable/disable with subsystem level files [PASS] - # [20] event tracing - enable/disable with top level files [PASS] - # [21] Test trace_printk from module [PASS] - # [22] ftrace - function graph filters with stack tracer [PASS] - # [23] ftrace - function graph filters [PASS] - # [24] ftrace - function pid notrace filters [PASS] - # [25] ftrace - function pid filters [PASS] - # [26] ftrace - stacktrace filter command[PASS] - # [27] ftrace - function trace with cpumask [PASS] - # [28] ftrace - test for function event triggers [PASS] - # [29] ftrace - function trace on module [PASS] - # [30] ftrace - function profiling [PASS] - # [31] ftrace - function profiler with function tracing [PASS] - # [32] ftrace - test reading of set_ftrace_filter[PASS] - # [33] ftrace - test for function traceon/off triggers [PASS] - # [34] ftrace - test tracing error log support [PASS] - # [35] Test creation and deletion of trace instances while setting an event [PASS] - # [36] Test creation and deletion of trace instances [PASS] - # [37] Kprobe dynamic event - adding and removing[PASS] - # [38] Kprobe dynamic event - busy event check [PASS] - # [39] Kprobe dynamic event with arguments [PASS] - # [40] Kprobe event with comm arguments [PASS] - # [41] Kprobe event string type argument [PASS] - # [42] Kprobe event symbol argument [PASS] - # [43] Kprobe event argument syntax [PASS] - # [44] Kprobes event arguments with types[PASS] - # [45] Kprobe event user-memory access [UNSUPPORTED] - # [46] Kprobe event auto/manual naming [PASS] - # [47] Kprobe dynamic event with function tracer [PASS] - # [48] Create/delete multiprobe on kprobe event [PASS] - # [49] Kprobe event parser error log check [PASS] - # [50] Kretprobe dynamic event with arguments[PASS] - # [51] Kretprobe dynamic event with maxactive[PASS] - # [52] Kretprobe %return suffix test [PASS] - # [53] Register/unregister many kprobe events[PASS] - # [54] Kprobe profile[PASS] - # [55] Uprobe event parser error log check [PASS] - # [56] test for the preemptirqsoff tracer[UNSUPPORTED] - # [57] Meta-selftest: Checkbashisms [PASS] - # [58] Test wakeup tracer[PASS] - # [59] Test wakeup RT tracer [PASS] - # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] - # [61] event trigger - test field variable support [PASS] - # [62] event trigger - test multiple actions on hist trigger [PASS] - # [63] event trigger - test inter-event histogram trigger onchange action [PASS] - # [64] event trigger - test inter-event histogram trigger onmatch action [PASS] - # [65] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] - # [66] event trigger - test inter-event histogram trigger onmax action [PASS] - # [67] event trigger - test inter-event histogram trigger snapshot action [PASS] - # [68] event trigger - test inter-event histogram trigger eprobe on synthetic event
[Kernel-packages] [Bug 2034095] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2034095 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034095 Title: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: Incomplete Status in linux-oem-6.5 source package in Lunar: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: New Bug description: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034095/+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 2034095] [NEW] Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure
Public bug reported: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034095 Title: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: New Bug description: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034095/+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 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
It sounds like the main problem therefore is the Nvidia X driver. It's
refusing to light up HDMI without a custom config explicitly telling it
to use "PCI:193:0:0". But this might be Nvidia's intended behaviour so I
recommend checking the docs for solutions first:
https://us.download.nvidia.com/XFree86/Linux-x86_64/535.86.05/README/index.html
And contacting Nvidia for help second.
P.S. The Nvidia website recommends driver 460 for the A100. Also the
installed driver version sounds like it's from nvidia-graphics-
drivers-535 (desktop), but also there are some nvidia-graphics-
drivers-535-server packages installed? So I wonder if this is just a bad
choice of drivers for the hardware.
** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2033418
Title:
Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
default
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
New
Bug description:
The DGX Station A10 has various display options. The BMC provides an
emulated device (Aspeed controller), a physical BMC controller (NVIDIA
Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.
In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
on the A100 DisplayPort output.
NVIDIA DGX OS - a derivative of Ubuntu - works around this by
installing a service that generates an xorg config file dynamically
based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
I'll attach samples of those files here. Replacing the default Ubuntu
xorg.conf file with the sample xorg-nvidia.conf file on a default
Ubuntu Desktop install is confirmed to enable output.
[*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
started-station-a100.html
(Note: split from bug 2031367)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2033418/+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 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
** Summary changed: - Missing BT IDs for Intel WiFi 7 BE200/BE202 cards + Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 -- 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/2033455 Title: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] [Fix] [Test Case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033455/+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 2033418] [NEW] Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
You have been subscribed to a public bug:
The DGX Station A10 has various display options. The BMC provides an
emulated device (Aspeed controller), a physical BMC controller (NVIDIA
Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort outputs
(A100 SXM4 80GB). See the user guide[*] for a diagram.
In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears on
the A100 DisplayPort output.
NVIDIA DGX OS - a derivative of Ubuntu - works around this by installing
a service that generates an xorg config file dynamically based on the
"OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11"). I'll attach
samples of those files here. Replacing the default Ubuntu xorg.conf file
with the sample xorg-nvidia.conf file on a default Ubuntu Desktop
install is confirmed to enable output.
[*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
started-station-a100.html
(Note: split from bug 2031367)
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment dgx hybrid jammy multigpu nvidia
--
Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
https://bugs.launchpad.net/bugs/2033418
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031407] Re: Missing new hda/cs8409 support for new Dell Dolphin Variants
This has been fixed automatically after oem-6.5 rebased onto v6.5-rc7.
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: hwe-next
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/2031407
Title:
Missing new hda/cs8409 support for new Dell Dolphin Variants
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The audio output device won't be detected for the new Dell Dolphin Variants.
[Fix]
Proposed fix in linux-next commit 7c761166399b ("ALSA: hda/cs8409: Support
new Dell Dolphin Variants") for the unsupported Dolphin Variants.
[Test]
1. Boot into Ubuntn OS .
2. Open Setting-->Sound-->output device
3. Check if the output device shows 'Dummy output' or not.
[Where problems could occur]
The patches are only for new Dell Dolphin variants and enable for specific
SSID. Should be no impact of regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2031407/+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 2034057] Re: function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
And this is affecting 4.15 AWS as well. Here is the output from b-aws-4.15-2099 Test output: + echo blk + echo mmiotrace + echo function_graph (Test interrupted here) dmesg: [ 216.814155] kernel BUG at /build/linux-aws-fips-hcslsq/linux-aws-fips-4.15.0/arch/x86/xen/spinlock.c:69! [ 216.816072] invalid opcode: [#1] SMP PTI [ 216.816991] Modules linked in: nls_iso8859_1 binfmt_misc sb_edac intel_rapl_perf serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops aesni_intel drm aes_x86_64 crypto_simd i2c_piix4 glue_helper cryptd i2c_core ixgbevf pata_acpi [ 216.827515] CPU: 1 PID: 13 Comm: cpuhp/1 Not tainted 4.15.0-2099-aws-fips #105-Ubuntu [ 216.829132] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 216.830471] RIP: 0010:dummy_handler+0x4/0x10 [ 216.831362] RSP: :a0c827a43e38 EFLAGS: 00010046 [ 216.832477] RAX: 8302a9c0 RBX: 003b RCX: 003b [ 216.833951] RDX: 00400e00 RSI: RDI: 003b [ 216.835425] RBP: a0c827a43e38 R08: a0c827000db0 R09: a0c81b14ea00 [ 216.836902] R10: 0040 R11: R12: [ 216.838378] R13: R14: R15: a0c82444f400 [ 216.839854] FS: () GS:a0c827a4() knlGS: [ 216.841533] CS: 0010 DS: ES: CR0: 80050033 [ 216.842708] CR2: CR3: 3b80a001 CR4: 001606e0 [ 216.844141] DR0: DR1: DR2: [ 216.845631] DR3: DR6: fffe0ff0 DR7: 0400 [ 216.847095] Call Trace: [ 216.847640] [ 216.848079] __handle_irq_event_percpu+0x44/0x1a0 [ 216.849070] handle_irq_event_percpu+0x32/0x80 [ 216.850009] handle_percpu_irq+0x3d/0x60 [ 216.850829] generic_handle_irq+0x28/0x40 [ 216.851687] handle_irq_for_port+0x8f/0xe0 [ 216.852556] evtchn_2l_handle_events+0x157/0x270 [ 216.853537] __xen_evtchn_do_upcall+0x76/0xe0 [ 216.854453] xen_evtchn_do_upcall+0x2b/0x50 [ 216.855327] xen_hvm_callback_vector+0x90/0xa0 [ 216.856266] [ 216.856724] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [ 216.857890] RSP: :b95780d37d00 EFLAGS: 0246 ORIG_RAX: ff0c [ 216.859472] RAX: 0001 RBX: a0c82444f400 RCX: 0002cc00 [ 216.860907] RDX: 0001 RSI: 0246 RDI: 0246 [ 216.862353] RBP: b95780d37d00 R08: a0c827000db0 R09: a0c81b14ea00 [ 216.863782] R10: 0040 R11: 0246 R12: 003b [ 216.865233] R13: R14: a0c81b14ea00 R15: a0c81b14eaa4 [ 216.82] __setup_irq+0x424/0x6e0 [ 216.867392] request_threaded_irq+0xf9/0x170 [ 216.868281] bind_ipi_to_irqhandler+0xc6/0x1f0 [ 216.869184] ? xen_qlock_wait+0x90/0x90 [ 216.871428] ? skx_uncore_pci_init+0x40/0x40 [ 216.873772] xen_init_lock_cpu+0x97/0xf0 [ 216.876010] ? skx_uncore_pci_init+0x40/0x40 [ 216.878279] xen_cpu_up_online+0xe/0x20 [ 216.880408] cpuhp_invoke_callback+0x9d/0x570 [ 216.882651] cpuhp_thread_fun+0xc4/0x150 [ 216.884751] smpboot_thread_fn+0xfc/0x170 [ 216.886799] kthread+0x121/0x140 [ 216.888664] ? sort_range+0x30/0x30 [ 216.890525] ? kthread_create_worker_on_cpu+0x70/0x70 [ 216.892663] ret_from_fork+0x35/0x40 [ 216.894462] Code: c0 8b 75 e4 74 d6 44 89 e7 e8 29 3b 57 00 eb d6 44 89 e7 e8 1f 5f 57 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 80 3d 79 e9 3f 01 00 55 48 [ 216.900389] RIP: dummy_handler+0x4/0x10 RSP: a0c827a43e38 [ 216.902668] ---[ end trace af76218ae4efc4a6 ]--- [ 216.904746] Kernel panic - not syncing: Fatal exception in interrupt [ 216.907189] Kernel Offset: 0x200 from 0x8100 (relocation range: 0x8000-0xbfff) ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: 4.15 bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2034057 Title: function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: New Status in linux-aws source package in Jammy: New Status in linux-aws source package in Lunar: New Bug
[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
The similiar patch has been included in v6.4-rc7, so 6.5 kernel should include the fix. 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
hi, would you please help me to try vanilla kernel? check if the issue is still here？ https://drive.google.com/drive/folders/1AFgeX8_USkR9omba8E-D-cJsaDuhzKLW?usp=sharing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Package changed: gdm (Ubuntu Jammy) => gdm3 (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Triaged Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Bug description: The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires config changes: DRM=y DRM_FBDEV_EMULATION=y FB_EFI=n FB_VESA=n (? check this) SYSFB_SIMPLEFB=y fbcon will still require FB to be available, but will use the fbdev emulation layer At the time of filing this bug report, the NVIDIA drivers don't support the fbdev emulation layer, so VT's would be broken on them if this was to be enabled right now. So the drivers need fixing, and this bug report is a placeholder until we are able to move forward. fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965303/+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 2033533] Re: [qxl] installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt
> I can't collect logs because when I do ... the issue is gone
This supports the theory that it's a Plymouth race condition, fixed by
booting more slowly. Plymouth might be wanting to display the password
prompt before graphics support has "booted" in the kernel.
Actually now that I've said that and we know it's DRM it reminds me of
bug 1869655 which might be the same issue. And we might get a permanent
workaround by switching to SimpleDRM in the kernel (bug 1965303).
--
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/2033533
Title:
[qxl] installing with lvm and encryption requires arrow key spam after
reboot to get to encryption passphrase prompt
Status in linux package in Ubuntu:
Confirmed
Status in plymouth package in Ubuntu:
New
Bug description:
This also happens with the canary image and is happening with the
Mantic daily image.
When installing with LVM and encryption, after the "remove
installation medium and press enter to reboot", the user is greeted
with a permanent black screen. After pressing arrow keys, the gui
prompt is then shown to prompt the user to put in the encryption
passphrase.
It is also somehow possible to not get the black screen by changing
the grub prior to installing by removing splash from the grub options.
The user is then greeted with a text-only passphrase prompt after
rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages. If that does not
work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033533/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
@juergh, I want to express my gratitude for your dedication and efforts in investigating the bug. Your involvement has been invaluable, and I truly appreciate it. I've recently updated to the new kernel version, 6.2.0-32-generic, and will be monitoring. Additionally, for clarity, I'd like to mention that I'm utilizing the "NVIDIA proprietary driver" rather than the "Nouveau" driver. ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2034077] [NEW] USB3 controller issues after moving from 18.4 to 22.04
Public bug reported: I just upgrade Ubuntu fro 18.04 to 22.04 with Kernel new kernel 6.2.0.31 VIA USB 3.0 controller fails with ../.. [ 2812.150794] xhci_hcd :02:00.0: WARNING: Host System Error [ 2812.150848] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xbff6 flags=0x] [ 2812.182810] xhci_hcd :02:00.0: Host halt failed, -110 ../.. It is triggered by some USB3 activities (disk file transfer). Already try to set iommu=soft in kernel command line as well enable/disable iommu Bios ... MB: Base Board Information Manufacturer: MSI Product Name: 970 GAMING (MS-7693) Version: 4.0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Sep 4 23:38:32 2023 InstallationDate: Installed on 2023-09-03 (0 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034077 Title: USB3 controller issues after moving from 18.4 to 22.04 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I just upgrade Ubuntu fro 18.04 to 22.04 with Kernel new kernel 6.2.0.31 VIA USB 3.0 controller fails with ../.. [ 2812.150794] xhci_hcd :02:00.0: WARNING: Host System Error [ 2812.150848] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xbff6 flags=0x] [ 2812.182810] xhci_hcd :02:00.0: Host halt failed, -110 ../.. It is triggered by some USB3 activities (disk file transfer). Already try to set iommu=soft in kernel command line as well enable/disable iommu Bios ... MB: Base Board Information Manufacturer: MSI Product Name: 970 GAMING (MS-7693) Version: 4.0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Sep 4 23:38:32 2023 InstallationDate: Installed on 2023-09-03 (0 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034077/+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 2033557] Re: PCM2900 Audio cards based stop working
Fix error on linux-image-6.2.0-1012 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2033557 Title: PCM2900 Audio cards based stop working Status in linux-signed-lowlatency package in Ubuntu: New Bug description: Updating to linux-image-6.2.0-1011-lowlatency, audio cards based on TI PCM2900C stops working and are not detected by the system, has to return to linux-image-6.2.0-1010-lowlatency to keep them working Description:Ubuntu 23.04 Release:23.04 inux-image-lowlatency: Instalados: 6.2.0.1011.11 Candidato: 6.2.0.1011.11 Tabla de versión: *** 6.2.0.1011.11 500 500 http://mx.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://mx.archive.ubuntu.com/ubuntu lunar-security/main amd64 Packages 100 /var/lib/dpkg/status 6.2.0.1003.3 500 500 http://mx.archive.ubuntu.com/ubuntu lunar/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1011-lowlatency 6.2.0-1011.11 ProcVersionSignature: Ubuntu 6.2.0-1010.10-lowlatency 6.2.15 Uname: Linux 6.2.0-1010-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Aug 30 12:57:13 2023 SourcePackage: linux-signed-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2033557/+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 2034074] Status changed to Confirmed
This change was made by a bot. ** 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/2034074 Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux- headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in linux package in Ubuntu: Confirmed Bug description: L'explorateur de fichier a planté, sur une liste de vidéos mis sur un nas. En relançeant l'explorateur ke problème était corrigé ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeanpaul 2055 F wireplumber /dev/snd/controlC1: jeanpaul 2055 F wireplumber /dev/snd/seq:jeanpaul 2049 F pipewire CasperMD5CheckResult: pass Date: Mon Sep 4 22:49:30 2023 ErrorMessage: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2023-04-22 (135 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Precision WorkStation T5500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=111a4c85-d9a3-4cb1-84c0-77ec0b30348f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (130 days ago) dmi.bios.date: 01/21/2011 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0D883F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/21/2011:br0.0:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0D883F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T5500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034074/+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 2034074] [NEW] package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation ins
Public bug reported: L'explorateur de fichier a planté, sur une liste de vidéos mis sur un nas. En relançeant l'explorateur ke problème était corrigé ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeanpaul 2055 F wireplumber /dev/snd/controlC1: jeanpaul 2055 F wireplumber /dev/snd/seq:jeanpaul 2049 F pipewire CasperMD5CheckResult: pass Date: Mon Sep 4 22:49:30 2023 ErrorMessage: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2023-04-22 (135 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Precision WorkStation T5500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=111a4c85-d9a3-4cb1-84c0-77ec0b30348f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (130 days ago) dmi.bios.date: 01/21/2011 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0D883F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/21/2011:br0.0:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0D883F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T5500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package lunar -- 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/2034074 Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux- headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in linux package in Ubuntu: Confirmed Bug description: L'explorateur de fichier a planté, sur une liste de vidéos mis sur un nas. En relançeant l'explorateur ke problème était corrigé ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeanpaul 2055 F wireplumber /dev/snd/controlC1: jeanpaul 2055 F wireplumber /dev/snd/seq:jeanpaul 2049 F pipewire CasperMD5CheckResult: pass Date: Mon Sep 4 22:49:30 2023 ErrorMessage: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2023-04-22 (135 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Precision WorkStation T5500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=111a4c85-d9a3-4cb1-84c0-77ec0b30348f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (130 days ago) dmi.bios.date: 01/21/2011 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0D883F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/21/2011:br0.0:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0D883F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T5500 dmi.sys.vendor: Dell Inc.
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
I should have added that this bug also causes the system to overheat badly even in sleep mode. It seems it causes the system to wake up. I got in the habit of powering it off when traveling because I found it almost too hot to touch a couple of times when I took it out of my backpack. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
linux-oem-22.04d 6.5.0.1003.3 in jammy-updates contains the fix. https://changelogs.ubuntu.com/changelogs/pool/main/l/linux- oem-6.5/linux-oem-6.5_6.5.0-1003.3/changelog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+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 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
This issue is only present for me when a micro-SD card is plugged in, whether it is mounted or not. System is LG-Gram, running fully up to date 22.04.3, running 5.15.0-83-generic kernel as of today. Completely reproducible. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B
[Kernel-packages] [Bug 2033386] Re: 6.2.0-31 SMB1 NAS won't mount
Well, it looks like starting with kernel 6.20-31 we will have to say goodbye to SMB version 1.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/2033386 Title: 6.2.0-31 SMB1 NAS won't mount Status in linux package in Ubuntu: Confirmed Bug description: I can't connect to my old NAS SMB vers=1.0 using cifs via fstab, everything works in kernel 6.2.0-26 and I have to roll back. mount.cifs(8) -22 invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033386/+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 2023585] Re: [nvidia] GPU has fallen off the bus
I decided to disconnect the Nvidia GPU and use a spare AMD GPU and haven't had this occur since. I guess you're probably right that it's a hardware issue but don't know whether the fault was with the GPU or the Motherboard. At the time this was happening I had the Nvidia GPU in the first slot and the AMD GPU in the second PCIe slot but without any power cables running to it from the PSU, so essentially it was off and not being picked up by Ubuntu. I don't know if the motherboard would be at fault or not in the scenario above if the second slot has a device plugged in but not powered? Initially it looks like the fault of the Nvidia GPU but I haven't tested it in other configurations to definitively say it's a fault with the Nvidia GPU. -- 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/2023585 Title: [nvidia] GPU has fallen off the bus Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: When playing Assassins Creed Unity through Steam, the game will run fine for a short period and then pretty quickly in my experience the screen will go blank, lights on the GPU will turn off and GPU fans will spin at max RPM. I checked the dmesg logs from that session and saw at the bottom: ``` Jun 12 19:25:09 pikachu kernel: NVRM: GPU at PCI::0b:00: GPU-f888943b-327b-82af-03dd-7c4213dc4788 Jun 12 19:25:09 pikachu kernel: NVRM: Xid (PCI::0b:00): 79, pid='', name=, GPU has fallen off the bus. Jun 12 19:25:09 pikachu kernel: NVRM: GPU :0b:00.0: GPU has fallen off the bus. Jun 12 19:25:09 pikachu kernel: nvidia-gpu :0b:00.3: Unable to change power state from D3hot to D0, device inaccessible Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power state from D3hot to D0, device inaccessible Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power state from D3cold to D0, device inaccessible Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Controller not ready at resume -19 Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: PCI post-resume error -19! Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: HC died; cleaning up Jun 12 19:25:09 pikachu kernel: audit: type=1400 audit(1686594309.980:429): apparmor="DENIED" operation="open" class="file" profile="snap.keepassxc.keepassxc" name="/sys/devices/pci00> Jun 12 19:25:10 pikachu kernel: nvidia-gpu :0b:00.3: i2c timeout error Jun 12 19:25:10 pikachu kernel: ucsi_ccg 0-0008: i2c_transfer failed -110 ``` Further up in the logs I also see the following (in case it's related): ``` [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0b00] Failed to grab modeset ownership ``` I am using an RTX 2080Ti on driver version 525.105.17. I have attached the full dmesg log ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-525 525.105.17-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 19:35:37 2023 InstallationDate: Installed on 2022-12-06 (187 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-525 UpgradeStatus: Upgraded to lunar on 2023-04-21 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023585/+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 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2024199] Re: Resync CI Runner Configuration
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2028932] Re: ubuntu_bpf failed to build with j-oem-6.1.0-1018.18
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2032174] Re: Got soft lockup CPU if dell_uart_backlight is probed
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2032767] Re: Fix ACPI TAD on some Intel based systems
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
After installing the 6.2.0.26 kernel, there were such messages: "Generic FE-GE Realtek PHY r8169-0-200:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling!" $ sudo journalctl -b 1 --dmesg | grep r8169 The number after -b is the reboot number. -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call
[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
1.416418] platform eisa.0: Probing EISA bus 0 [1.416419] platform eisa.0: EISA: Cannot allocate resource for mainboard [1.416420] platform eisa.0: Cannot allocate resource for EISA slot 1 [1.416420] platform eisa.0: Cannot allocate resource for EISA slot 2 [1.416421] platform eisa.0: Cannot allocate resource for EISA slot 3 [1.416421] platform eisa.0: Cannot allocate resource for EISA slot 4 [1.416422] platform eisa.0: Cannot allocate resource for EISA slot 5 [1.416422] platform eisa.0: Cannot allocate resource for EISA slot 6 [1.416422] platform eisa.0: Cannot allocate resource for EISA slot 7 [1.416423] platform eisa.0: Cannot allocate resource for EISA slot 8 [1.416423] platform eisa.0: EISA: Detected 0 cards Linux Mint, Kernel 5.15.0-83-generic -- 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/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3028 F pulseaudio /dev/snd/pcmC0D0p: caravena 3028 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:16:07 2019 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (230 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
I'm affected: LENOVO THINKPAD 16P, nVidia RTX 3060 Mobile. I can't shutdown the system. Also as @juanma-v82 states no nVidia card is detected and "Software and Updates"->"More Drivers" UI doesn't show the nVidia drivers to install them as if the card is not detected at all; so this could be related to #2034068 I've reported resently. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
After following @juergh updates. I realized the problem was the nouveau drivers, also I saw my fresh installation (Ubuntu 22.04.3) was not detecting my RTX 3070. So I fixed both problems installing the drivers. > sudo apt install nvidia-driver-535 Now, I can shutdown and/or restart my machine without issues. The only problem is this driver is the propertary one. However in my case is not a problem. Regards Juan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
no change 5.15.0-83-generic.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in Ubuntu:
Confirmed
Bug description:
from dmesg
1.313665] UBSAN: shift-out-of-bounds in
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.313668] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
there is also a crash but i don't know if it's related.
1.313671] Call Trace:
[1.313672]
[1.313673] show_stack+0x52/0x5c
[1.313676] dump_stack_lvl+0x4a/0x63
[1.313678] dump_stack+0x10/0x16
[1.313679] ubsan_epilogue+0x9/0x49
[1.313680] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[1.313682] initialize_nocpsch.cold+0x15/0x59 [amdgpu]
[1.313841] device_queue_manager_init+0x208/0x3b0 [amdgpu]
[1.313946] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
[1.314079] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
[1.314178] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
[1.314323] amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
[1.314463] ? do_pci_enable_device+0xdb/0x110
[1.314466] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
[1.314556] amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
[1.314642] local_pci_probe+0x48/0x90
[1.314644] pci_device_probe+0x119/0x1f0
[1.314645] really_probe+0x21f/0x420
[1.314647] __driver_probe_device+0x119/0x190
[1.314648] driver_probe_device+0x23/0xc0
[1.314650] __driver_attach+0xbd/0x1f0
[1.314651] ? __device_attach_driver+0x120/0x120
[1.314652] bus_for_each_dev+0x7c/0xd0
[1.314654] driver_attach+0x1e/0x30
[1.314655] bus_add_driver+0x148/0x220
[1.314656] driver_register+0x95/0x100
[1.314657] __pci_register_driver+0x68/0x70
[1.314659] amdgpu_init+0x7c/0x1000 [amdgpu]
[1.314747] ? 0xc0fc
[1.314748] do_one_initcall+0x46/0x1e0
[1.314750] ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.314752] do_init_module+0x52/0x260
[1.314753] load_module+0xb2b/0xbc0
[1.314754] __do_sys_finit_module+0xbf/0x120
[1.314756] __x64_sys_finit_module+0x18/0x20
[1.314757] do_syscall_64+0x59/0xc0
[1.314758] ? ksys_lseek+0x85/0xc0
[1.314759] ? exit_to_user_mode_prepare+0x37/0xb0
[1.314761] ? syscall_exit_to_user_mode+0x27/0x50
[1.314762] ? __x64_sys_lseek+0x18/0x20
[1.314763] ? do_syscall_64+0x69/0xc0
[1.314764] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[1.314766] RIP: 0033:0x7fef87ab8a3d
[1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX:
0139
[1.314770] RAX: ffda RBX: 55d1d00078a0 RCX:
7fef87ab8a3d
[1.314771] RDX: RSI: 7fef87c4f441 RDI:
0018
[1.314772] RBP: 0002 R08: R09:
0002
[1.314772] R10: 0018 R11: 0246 R12:
7fef87c4f441
[1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15:
55d1d002eb10
[1.314774]
[1.314778]
gpu is Amd r 380 tonga 4Gb.
I was adviced to try 6.0 series of kernel and I dont see the ubsan error
there but I would like to get the fixes backported 5.15 series.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarkko 1322 F pulseaudio
/dev/snd/controlC1: jarkko 1322 F pulseaudio
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-09-19 (71 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1007-oem N/A
linux-backports-modules-6.0.0-1007-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: vanessa
Uname: Linux 6.0.0-1007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
$ sudo journalctl --dmesg | grep r8169 сен 01 19:50:04 MyHomeAssistant kernel: r8169 :02:00.0 eth0: RTL8168h/8111h, 7c:83:34:b6:8a:3b, XID 541, IRQ 127 сен 01 19:50:04 MyHomeAssistant kernel: r8169 :02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] сен 01 19:50:04 MyHomeAssistant kernel: r8169 :03:00.0 eth1: RTL8168h/8111h, 7c:83:34:b6:8a:3c, XID 541, IRQ 128 сен 01 19:50:04 MyHomeAssistant kernel: r8169 :03:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko] сен 01 19:50:04 MyHomeAssistant kernel: r8169 :03:00.0 enp3s0: renamed from eth1 сен 01 19:50:04 MyHomeAssistant kernel: r8169 :02:00.0 enp2s0: renamed from eth0 сен 01 19:50:10 MyHomeAssistant kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC) сен 01 19:50:10 MyHomeAssistant kernel: r8169 :02:00.0 enp2s0: Link is Down сен 01 19:50:10 MyHomeAssistant kernel: Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC) сен 01 19:50:10 MyHomeAssistant kernel: r8169 :03:00.0 enp3s0: Link is Down сен 01 19:50:14 MyHomeAssistant kernel: r8169 :02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control rx/tx -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
Finally made it to Lunar in today's updates! -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this
[Kernel-packages] [Bug 2034061] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2034061
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034061
Title:
Default module signing algo should be accelerated
Status in linux package in Ubuntu:
Incomplete
Bug description:
[ Impact ]
* Slow secureboot due to unoptimized signature verification algo
[ Test Plan ]
* Check config enforcement:
If CONFIG_MODULE_SIG_(ALG)=y, then CONFIG_CRYPTO_(ALG)* should be =y
as well
[ Where problems could occur ]
* Very old hardware incapable of a given optimisation will not gain
from having optimised algo built-in
[ Other Info ]
* Full details
Default module signing algo should be accelerated
Default crypto signing algorithm for kernel modules, all its
accelerated versions, should be built-in. This is to allow secureboot
of accelerated machines to boot as quickly as possible when verifying
each module signature.
For example:
given CONFIG_MODULE_SIG_SHA512=y
All of
CONFIG_CRYPTO_SHA512policy<{'amd64': 'y',
'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
CONFIG_CRYPTO_SHA512note<'module signing'>
CONFIG_CRYPTO_SHA512_ARMpolicy<{'armhf': 'm'}>
CONFIG_CRYPTO_SHA512_ARM64 policy<{'arm64': 'm'}>
CONFIG_CRYPTO_SHA512_ARM64_CE policy<{'arm64': 'm'}>
CONFIG_CRYPTO_SHA512_S390 policy<{'s390x': 'm'}>
CONFIG_CRYPTO_SHA512_SSSE3 policy<{'amd64': 'm'}>
Should be =y on secureboot platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034061/+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 2034061] [NEW] Default module signing algo should be accelerated
Public bug reported:
[ Impact ]
* Slow secureboot due to unoptimized signature verification algo
[ Test Plan ]
* Check config enforcement:
If CONFIG_MODULE_SIG_(ALG)=y, then CONFIG_CRYPTO_(ALG)* should be =y as
well
[ Where problems could occur ]
* Very old hardware incapable of a given optimisation will not gain
from having optimised algo built-in
[ Other Info ]
* Full details
Default module signing algo should be accelerated
Default crypto signing algorithm for kernel modules, all its accelerated
versions, should be built-in. This is to allow secureboot of accelerated
machines to boot as quickly as possible when verifying each module
signature.
For example:
given CONFIG_MODULE_SIG_SHA512=y
All of
CONFIG_CRYPTO_SHA512policy<{'amd64': 'y', 'arm64':
'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
CONFIG_CRYPTO_SHA512note<'module signing'>
CONFIG_CRYPTO_SHA512_ARMpolicy<{'armhf': 'm'}>
CONFIG_CRYPTO_SHA512_ARM64 policy<{'arm64': 'm'}>
CONFIG_CRYPTO_SHA512_ARM64_CE policy<{'arm64': 'm'}>
CONFIG_CRYPTO_SHA512_S390 policy<{'s390x': 'm'}>
CONFIG_CRYPTO_SHA512_SSSE3 policy<{'amd64': 'm'}>
Should be =y on secureboot platforms.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034061
Title:
Default module signing algo should be accelerated
Status in linux package in Ubuntu:
Incomplete
Bug description:
[ Impact ]
* Slow secureboot due to unoptimized signature verification algo
[ Test Plan ]
* Check config enforcement:
If CONFIG_MODULE_SIG_(ALG)=y, then CONFIG_CRYPTO_(ALG)* should be =y
as well
[ Where problems could occur ]
* Very old hardware incapable of a given optimisation will not gain
from having optimised algo built-in
[ Other Info ]
* Full details
Default module signing algo should be accelerated
Default crypto signing algorithm for kernel modules, all its
accelerated versions, should be built-in. This is to allow secureboot
of accelerated machines to boot as quickly as possible when verifying
each module signature.
For example:
given CONFIG_MODULE_SIG_SHA512=y
All of
CONFIG_CRYPTO_SHA512policy<{'amd64': 'y',
'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
CONFIG_CRYPTO_SHA512note<'module signing'>
CONFIG_CRYPTO_SHA512_ARMpolicy<{'armhf': 'm'}>
CONFIG_CRYPTO_SHA512_ARM64 policy<{'arm64': 'm'}>
CONFIG_CRYPTO_SHA512_ARM64_CE policy<{'arm64': 'm'}>
CONFIG_CRYPTO_SHA512_S390 policy<{'s390x': 'm'}>
CONFIG_CRYPTO_SHA512_SSSE3 policy<{'amd64': 'm'}>
Should be =y on secureboot platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034061/+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 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
@paelzer given the above findings and discussion, I would like to mark this as Invalid for cloud-images project and continue the conversation in the context of kernel only. +1 / -1 ? -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+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 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
Ah. I see. KSM_ENABLED=AUTO from /etc/default/qemu-kvm is used through /usr/share/qemu/init/qemu-kvm-init via the qemu-kvm.service systemd service. thanks for the hint! -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+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 2034057] [NEW] function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Public bug reported: Test: * ftrace:test.d--00basic--basic2.tc from ubuntu_kselftests_ftrace * test_enable_all_tracers() and test_enable_all_tracers() from ubuntu_ftrace_smoke_test Will crash AWS instance c3.xlarge when testing the "function_graph" tracer. We have a similar issue filed against Azure (bug 1882669). Filing a new bug report because on AWS this is affecting 5.4 ~ 6.2 AWS kernel. However on Azure this is not affecting newer kernels. Take B-aws-5.4-1108 for example, with the ubuntu_kselftests_ftrace test the system will crash with the following error message and reboot (similar to bug 2029917): [ 211.675624] kernel BUG at /build/linux-aws-5.4-VHOhmt/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62! [ 211.678258] invalid opcode: [#1] SMP PTI [ 211.679596] CPU: 1 PID: 14 Comm: cpuhp/1 Not tainted 5.4.0-1108-aws #116~18.04.1-Ubuntu [ 211.681825] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 211.683728] RIP: 0010:dummy_handler+0x4/0x10 [ 211.685042] Code: 8b 75 e4 74 d6 44 89 e7 e8 f9 88 61 00 eb d6 44 89 e7 e8 6f ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 80 3d 59 d0 9f 01 00 75 02 f3 [ 211.690314] RSP: :aecd4000ee38 EFLAGS: 00010046 [ 211.691934] RAX: b462e3e0 RBX: 003b RCX: [ 211.694036] RDX: 00400e00 RSI: RDI: 003b [ 211.696159] RBP: aecd4000ee38 R08: 8aefa6c036c0 R09: 8aefa6c038c0 [ 211.698232] R10: R11: b6064da8 R12: [ 211.700365] R13: R14: R15: 8aefa34b8700 [ 211.702482] FS: () GS:8aefa804() knlGS: [ 211.704894] CS: 0010 DS: ES: CR0: 80050033 [ 211.706598] CR2: CR3: 0001b400a001 CR4: 001606e0 [ 211.708731] DR0: DR1: DR2: [ 211.710835] DR3: DR6: fffe0ff0 DR7: 0400 [ 211.713448] Call Trace: [ 211.714796] [ 211.715996] __handle_irq_event_percpu+0x44/0x1a0 [ 211.717907] handle_irq_event_percpu+0x32/0x80 [ 211.719759] handle_percpu_irq+0x3d/0x60 [ 211.721474] generic_handle_irq+0x28/0x40 [ 211.723184] handle_irq_for_port+0x8f/0xe0 [ 211.724988] evtchn_2l_handle_events+0x157/0x270 [ 211.726913] __xen_evtchn_do_upcall+0x76/0xe0 [ 211.728749] xen_evtchn_do_upcall+0x2b/0x40 [ 211.730520] xen_hvm_callback_vector+0xf/0x20 [ 211.732271] [ 211.733425] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [ 211.735470] Code: e8 70 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90 90 90 0f 1f 44 00 00 55 48 89 e5 e8 a6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07 [ 211.741920] RSP: :aecd400fbcf8 EFLAGS: 0246 ORIG_RAX: ff0c [ 211.744980] RAX: 0001 RBX: 8aefa34b8700 RCX: 0002cc00 [ 211.747420] RDX: 0001 RSI: 0246 RDI: 0246 [ 211.749882] RBP: aecd400fbcf8 R08: 8aefa6c036c0 R09: 8aefa6c038c0 [ 211.752340] R10: R11: 0246 R12: 003b [ 211.754785] R13: R14: 8aef95bdfa00 R15: 8aef95bdfaa4 [ 211.757249] __setup_irq+0x456/0x760 [ 211.758779] ? kmem_cache_alloc_trace+0x170/0x230 [ 211.760639] request_threaded_irq+0xfb/0x160 [ 211.762358] bind_ipi_to_irqhandler+0xba/0x1c0 [ 211.764124] ? xen_qlock_wait+0x90/0x90 [ 211.765734] ? snr_uncore_mmio_init+0x20/0x20 [ 211.767496] xen_init_lock_cpu+0x78/0xd0 [ 211.769135] ? snr_uncore_mmio_init+0x20/0x20 [ 211.770864] xen_cpu_up_online+0xe/0x20 [ 211.772500] cpuhp_invoke_callback+0x8a/0x580 [ 211.774233] cpuhp_thread_fun+0xb8/0x120 [ 211.775866] smpboot_thread_fn+0xfc/0x170 [ 211.777524] kthread+0x121/0x140 [ 211.778968] ? sort_range+0x30/0x30 [ 211.780508] ? kthread_park+0x90/0x90 [ 211.782073] ret_from_fork+0x35/0x40 [ 211.783622] Modules linked in: nls_iso8859_1 binfmt_misc serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper ixgbevf [ 211.796497] ---[ end trace bb7d4e9bb7f852cb ]--- [ 211.798303] RIP: 0010:dummy_handler+0x4/0x10 [ 211.800022] Code: 8b 75 e4 74 d6 44 89 e7 e8 f9 88 61 00 eb d6 44 89 e7 e8 6f ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 80 3d 59 d0 9f 01 00 75 02 f3 [ 211.806379] RSP: :aecd4000ee38 EFLAGS: 00010046 [ 211.808356] RAX: b462e3e0 RBX: 003b RCX: [ 211.810792] RDX: 00400e00
[Kernel-packages] [Bug 1882669] Re: Focal Azure AMD64 instances crash with ftrace/test.d/00basic/basic2.tc in ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test
For ftrace related issues found with c3.xlarge on AWS cloud, let track it in bug 2034057. -- 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/1882669 Title: Focal Azure AMD64 instances crash with ftrace/test.d/00basic/basic2.tc in ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [ 2236.645769] mmiotrace: enabled CPU26.
[Kernel-packages] [Bug 2033756] Re: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day
Hello Martin, Many thanks for the detailed information. I'm gonna configure amd_pstate=active for the next reboot (I'll wait for few days if I faced no crash to see if this kernel version is intrinsically more stable). Nice to learn that battery will last longer, it was a bit low to me. Regards, JF -- 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/2033756 Title: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day Status in linux package in Ubuntu: Confirmed Bug description: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 I have some technical knowledge, so I can do some tests if that can help solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jf 2338 F pulseaudio /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio /dev/snd/controlC0: jf 2338 F pulseaudio /dev/snd/controlC2: jf 2338 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 10:34:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2023-06-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21J5CTO1WW ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-82-generic root=UUID=ad3cccf2-3072-4b29-84f0-ed7b41dd4de6 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-08-12 (19 days ago) dmi.bios.date: 03/21/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21J5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21J5CTO1WW:pvrThinkPadP14sGen3:rvnLENOVO:rn21J5CTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21J5_BU_Think_FM_ThinkPadP14sGen3: dmi.product.family: ThinkPad P14s Gen 3 dmi.product.name: 21J5CTO1WW dmi.product.sku: LENOVO_MT_21J5_BU_Think_FM_ThinkPad P14s Gen 3 dmi.product.version: ThinkPad P14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756/+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 2033756] Re: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day
Hello JF You can read about amd_pstate here: https://docs.kernel.org/admin-guide/pm/amd-pstate.html and about the T14s gen 3 - which also has GPU-related crashes - here: https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3#GPU I have not been looking at dmesg after each crash but can only conclude that with kernel 6.3 and above and amd_pstate=active, I'm not experiencing any problems. I've read somewhere that amd_pstate will be on by default in kernels >6.5 but until then we have to activate this feature by ourselves. Good luck! edit: as a side note I'm experiencing better battery management and CPU performance with amd_pstate=active. On idle it consume as little as 3.7 W and on performance mode the CPU is boosted to 4.2 GHz. I'm not certain all features are enabled without this boot parameter. BW Martin -- 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/2033756 Title: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day Status in linux package in Ubuntu: Confirmed Bug description: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 I have some technical knowledge, so I can do some tests if that can help solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jf 2338 F pulseaudio /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio /dev/snd/controlC0: jf 2338 F pulseaudio /dev/snd/controlC2: jf 2338 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 10:34:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2023-06-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21J5CTO1WW ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-82-generic root=UUID=ad3cccf2-3072-4b29-84f0-ed7b41dd4de6 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-08-12 (19 days ago) dmi.bios.date: 03/21/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21J5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21J5CTO1WW:pvrThinkPadP14sGen3:rvnLENOVO:rn21J5CTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21J5_BU_Think_FM_ThinkPadP14sGen3: dmi.product.family: ThinkPad P14s Gen 3 dmi.product.name: 21J5CTO1WW dmi.product.sku: LENOVO_MT_21J5_BU_Think_FM_ThinkPad P14s Gen 3 dmi.product.version: ThinkPad P14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756/+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 1988018] Re: [mlx5] Intermittent VF-LAG activation failure
Could this be related to https://bugs.launchpad.net/netplan/+bug/2020409 ? -- 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/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: Triaged Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: Won't Fix Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+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 2025079] Re: [amdgpu] Multiple kernel errors and reboot
I switched back to Wayland today to see if there was any improvement and it was. I have already had few telcos on different platforms today and no crashes yet! -- 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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Incomplete Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+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 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
> it only gets activated when you install ksmtuned (which is not installed by default). No, installing qemu-system-... will also enable it. So Seth gladly filed bug 2033565 to discuss and change this now or at least towards 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+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 2023647] Re: [amdgpu] Screens go into flicker cycle after going blank with external monitor(s)
I switched back to Wayland and 2 external monitors today and the flicker seems to be gone (Ubuntu 23.04 with current updates). -- 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/2023647 Title: [amdgpu] Screens go into flicker cycle after going blank with external monitor(s) Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: This happens whenever screen goes blank after inactivity with external monitors. When there is only one external monitor after few cycles the system recovers from the bug. When there are more than one monitors the system almost never recovers until unplugging extra monitor, as shown in video: https://photos.app.goo.gl/td6coEKFQd3DKe9C7 Happens on desktop and login screen. The same result with Wayland and X11. Does not depend on size of the monitor, cable (HDMI or USB-C) or is it connected via USB-C hub or directly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 13 12:36:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-13 (60 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (52 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (131 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: mutter ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 Tags: lunar Uname: Linux 6.2.0-27-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (122 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2023647/+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 1967166] Re: Azure: not enough RAM under 4GB for CVM
** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- 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/1967166 Title: Azure: not enough RAM under 4GB for CVM Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Can you please include one more patchset for the "no enough RAM under 4GB" issue for the v5.13 kernel (and v5.15 kernel): https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/ https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/ Without the two patches, currently the 5.13 kernel (and 5.15 kernel) can't boot as a CVM guest on Azure. :-( The background is: currently an Azure host only provides about 900 MB memory below the 4GB boundary while the swiotlb code (which is required by the CVM patchset) needs to allocate memory of a size of MIN(1GB, 6% of the total memory). There will be an Azure host update, with which the host will provide about 3GB memory below the 4GB boundary, but we still need to wait a few more weeks to know the ETA. Currently the above two patches can work around the issue from the guest side. [Test Case] Microsoft tested [Where things could go wrong] These patches could affect non-CVM instances. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967166/+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 2026736] Re: Azure: Fix lockup in swiotlb when used as a CVM
** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- 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/2026736 Title: Azure: Fix lockup in swiotlb when used as a CVM Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] Azxure CVM instances can lock up when run under stress. [Test Plan] MSFT tested using the nttcp test. [Regression potential] CVM instances could continue to lock up under stress. [Other info] SF: #00363432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026736/+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 2028286] Re: Case [Azure][TDX] TDX Updated Patch set w/HCL
** Tags removed: verification-needed-lunar-linux-azure ** Tags added: verification-done-lunar-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/2028286 Title: Case [Azure][TDX] TDX Updated Patch set w/HCL Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] Miscrosoft has requested the inclusion of 5 patches in order to implement TDX with HCL. These patches will almost certainly be replaced over time by upstream commits. [Test Plan] Microsoft tested. [Regression Potential] TDX might not work in certain scenarios, e.g., TDX when HCL is present and glibc has not been updated. See SF: #00352899. [Other Info] SF: #00364214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2028286/+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 2034033] [NEW] Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5
Public bug reported: My Xubuntu system this weekend alerted me to a new kernel update being available. The following versions are the existing/working version: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 And the updated/not working version: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 And yes I run my system with: linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8 Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs operation to our Samba NT4 PDC, results in the following output into syslog: Sep 4 08:03:24 jaakob kernel: [ 107.703886] FS-Cache: Loaded Sep 4 08:03:24 jaakob kernel: [ 107.824160] Key type cifs.spnego registered Sep 4 08:03:24 jaakob kernel: [ 107.824169] Key type cifs.idmap registered Sep 4 08:03:24 jaakob kernel: [ 107.824454] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824454] Sep 4 08:03:24 jaakob kernel: [ 107.824457] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824460] CIFS: Attempting to mount \\ldslnx01\data Sep 4 08:03:24 jaakob kernel: [ 107.859554] CIFS: VFS: cifs_mount failed w/return code = -5 And none of the Samba mounts will establish. Booting back to the prior 6.2.0-26 kernel version, Samba mounts work just fine. I use the following switches to the mount.cifs command in order to establish connections to our Samba NT4 PDC: "-o credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0" That last vers= option was the last that needed to be added to continue making use of our Samba NT4 style PDC. Since it is a version upgrade of only the kernel, not Samba package, I would not think that yet another switch to mount.cifs was needed in order to continue connecting successfully. So did the latest Kernel update suddenly break Samba's mount.cifs vers=1.0 support? Nothing gets logged to our Samba server for the failed mount attempt. Booting for not back to the working 6.2.0-26 kernel version. Please kindly advise. ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034033 Title: Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: My Xubuntu system this weekend alerted me to a new kernel update being available. The following versions are the existing/working version: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 And the updated/not working version: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 And yes I run my system with: linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8 Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs operation to our Samba NT4 PDC, results in the following output into syslog: Sep 4 08:03:24 jaakob kernel: [ 107.703886] FS-Cache: Loaded Sep 4 08:03:24 jaakob kernel: [ 107.824160] Key type cifs.spnego registered Sep 4 08:03:24 jaakob kernel: [ 107.824169] Key type cifs.idmap registered Sep 4 08:03:24 jaakob kernel: [ 107.824454] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824454] Sep 4 08:03:24 jaakob kernel: [ 107.824457] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Sep 4 08:03:24 jaakob kernel: [ 107.824460] CIFS: Attempting to mount \\ldslnx01\data Sep 4 08:03:24 jaakob kernel: [ 107.859554] CIFS: VFS: cifs_mount failed w/return code = -5 And none of the Samba mounts will establish. Booting back to the prior 6.2.0-26 kernel version, Samba mounts work just fine. I use the following switches to the mount.cifs command in order to establish connections to our Samba NT4 PDC: "-o credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0" That last vers= option was the last that needed to be added to continue making use of our Samba NT4 style PDC. Since it is a version upgrade of only the kernel, not Samba package, I would not think that yet another switch to mount.cifs was needed in order to continue connecting successfully. So did the latest Kernel update suddenly break Samba's mount.cifs vers=1.0 support? Nothing gets logged to our Samba server for the failed mount attempt. Booting for not back to the working 6.2.0-26 kernel version. Please kindly
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
thanks @Shih-Yuan Lee, I did (more or less) sudo add-apt-repository --remove ppa:oem-solutions-group/intel-ipu6 sudo apt remove libcamhal-ipu6ep0 linux-modules-ipu6-generic-hwe-22.04 linux-modules-ivsc-generic-hwe-22.04 oem-somerville-tentacool-meta libcanberra-gtk0 v4l2-relayd libcamhal-ipu6ep0 libipu6ep libcamhal-ipu6ep-common sudo apt autoremove sudo apt install oem-somerville-tentacool-meta and my webcam is working again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 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.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A
[Kernel-packages] [Bug 2027983] Re: CONFIG_MPTCP_IPV6 is no longer enabled in Raspi Lunar in v6.2.0
This bug was fixed in the package linux-raspi - 6.2.0-1012.14 --- linux-raspi (6.2.0-1012.14) lunar; urgency=medium * lunar/linux-raspi: 6.2.0-1012.14 -proposed tracker (LP: #2030377) * CONFIG_MPTCP_IPV6 is no longer enabled in Raspi Lunar in v6.2.0 (LP: #2027983) - [Config] raspi: Enable MPTCP_IPV6 [ Ubuntu: 6.2.0-32.32 ] * lunar/linux: 6.2.0-32.32 -proposed tracker (LP: #2031134) * libgnutls report "trap invalid opcode" when trying to install packages over https (LP: #2031093) - [Config]: disable CONFIG_GDS_FORCE_MITIGATION [ Ubuntu: 6.2.0-30.30 ] * lunar/linux: 6.2.0-30.30 -proposed tracker (LP: #2030381) * CVE-2022-40982 - init: Provide arch_cpu_finalize_init() - x86/cpu: Switch to arch_cpu_finalize_init() - ARM: cpu: Switch to arch_cpu_finalize_init() - ia64/cpu: Switch to arch_cpu_finalize_init() - m68k/cpu: Switch to arch_cpu_finalize_init() - mips/cpu: Switch to arch_cpu_finalize_init() - sh/cpu: Switch to arch_cpu_finalize_init() - sparc/cpu: Switch to arch_cpu_finalize_init() - um/cpu: Switch to arch_cpu_finalize_init() - init: Remove check_bugs() leftovers - init: Invoke arch_cpu_finalize_init() earlier - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() - x86/init: Initialize signal frame size late - x86/fpu: Remove cpuinfo argument from init functions - x86/fpu: Mark init functions __init - x86/fpu: Move FPU initialization into arch_cpu_finalize_init() - x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build - x86/xen: Fix secondary processors' FPU initialization - x86/speculation: Add Gather Data Sampling mitigation - x86/speculation: Add force option to GDS mitigation - x86/speculation: Add Kconfig option for GDS - KVM: Add GDS_NO support to KVM - Documentation/x86: Fix backwards on/off logic about YMM support - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and CONFIG_GDS_FORCE_MITIGATION * CVE-2023-4015 - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain - netfilter: nf_tables: unbind non-anonymous set if rule construction fails - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR * CVE-2023-3995 - netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID * CVE-2023-3777 - netfilter: nf_tables: skip bound chain on rule flush * CVE-2023-3609 - net/sched: cls_u32: Fix reference counter leak leading to overflow * NULL pointer dereference on CS35L41 HDA AMP (LP: #2029199) - ASoC: cs35l41: Refactor error release code - ALSA: cs35l41: Add shared boost feature - ASoC: dt-bindings: cirrus, cs35l41: Document CS35l41 shared boost - ALSA: hda: cs35l41: Ensure firmware/tuning pairs are always loaded - ALSA: hda: cs35l41: Enable Amp High Pass Filter - ALSA: cs35l41: Use mbox command to enable speaker output for external boost - ALSA: cs35l41: Poll for Power Up/Down rather than waiting a fixed delay - ALSA: hda: cs35l41: Check mailbox status of pause command after firmware load - ALSA: hda: cs35l41: Ensure we correctly re-sync regmap before system suspending. - ALSA: hda: cs35l41: Ensure we pass up any errors during system suspend. - ALSA: hda: cs35l41: Move Play and Pause into separate functions - ALSA: hda: hda_component: Add pre and post playback hooks to hda_component - ALSA: hda: cs35l41: Use pre and post playback hooks - ALSA: hda: cs35l41: Rework System Suspend to ensure correct call separation - ALSA: hda: cs35l41: Add device_link between HDA and cs35l41_hda - ALSA: hda: cs35l41: Ensure amp is only unmuted during playback * Reboot command powers off the system (LP: #2029332) - x86/smp: Make stop_other_cpus() more robust - x86/smp: Dont access non-existing CPUID leaf * losetup with mknod fails on jammy with kernel 5.15.0-69-generic (LP: #2015400) - loop: deprecate autoloading callback loop_probe() - loop: do not enforce max_loop hard limit by (new) default * Fix UBSAN in Intel EDAC driver (LP: #2028746) - EDAC/skx_common: Enable EDAC support for the "near" memory - EDAC/skx_common: Delete duplicated and unreachable code - EDAC/i10nm: Add Intel Emerald Rapids server support - EDAC/i10nm: Make more configurations CPU model specific - EDAC/i10nm: Add Intel Granite Rapids server support - EDAC/i10nm: Skip the absent memory controllers * Make TTY switching possible for NVIDIA when it's boot VGA (LP: #2028749) - drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers - video/aperture: use generic code to figure out the vga default device - drm/aperture: Remove primary argument - video/aperture: Only kick vgacon when the pdev is decoding vga - video/aperture: Move vga handling to pci function - video/aperture: Drop primary argument - video/aperture: Only
[Kernel-packages] [Bug 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
This bug was fixed in the package linux-hwe-6.2 - 6.2.0-32.32~22.04.1 --- linux-hwe-6.2 (6.2.0-32.32~22.04.1) jammy; urgency=medium * jammy/linux-hwe-6.2: 6.2.0-32.32~22.04.1 -proposed tracker (LP: #2030380) [ Ubuntu: 6.2.0-32.32 ] * lunar/linux: 6.2.0-32.32 -proposed tracker (LP: #2031134) * libgnutls report "trap invalid opcode" when trying to install packages over https (LP: #2031093) - [Config]: disable CONFIG_GDS_FORCE_MITIGATION [ Ubuntu: 6.2.0-30.30 ] * lunar/linux: 6.2.0-30.30 -proposed tracker (LP: #2030381) * CVE-2022-40982 - init: Provide arch_cpu_finalize_init() - x86/cpu: Switch to arch_cpu_finalize_init() - ARM: cpu: Switch to arch_cpu_finalize_init() - ia64/cpu: Switch to arch_cpu_finalize_init() - m68k/cpu: Switch to arch_cpu_finalize_init() - mips/cpu: Switch to arch_cpu_finalize_init() - sh/cpu: Switch to arch_cpu_finalize_init() - sparc/cpu: Switch to arch_cpu_finalize_init() - um/cpu: Switch to arch_cpu_finalize_init() - init: Remove check_bugs() leftovers - init: Invoke arch_cpu_finalize_init() earlier - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() - x86/init: Initialize signal frame size late - x86/fpu: Remove cpuinfo argument from init functions - x86/fpu: Mark init functions __init - x86/fpu: Move FPU initialization into arch_cpu_finalize_init() - x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build - x86/xen: Fix secondary processors' FPU initialization - x86/speculation: Add Gather Data Sampling mitigation - x86/speculation: Add force option to GDS mitigation - x86/speculation: Add Kconfig option for GDS - KVM: Add GDS_NO support to KVM - Documentation/x86: Fix backwards on/off logic about YMM support - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and CONFIG_GDS_FORCE_MITIGATION * CVE-2023-4015 - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain - netfilter: nf_tables: unbind non-anonymous set if rule construction fails - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR * CVE-2023-3995 - netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID * CVE-2023-3777 - netfilter: nf_tables: skip bound chain on rule flush * CVE-2023-3609 - net/sched: cls_u32: Fix reference counter leak leading to overflow * NULL pointer dereference on CS35L41 HDA AMP (LP: #2029199) - ASoC: cs35l41: Refactor error release code - ALSA: cs35l41: Add shared boost feature - ASoC: dt-bindings: cirrus, cs35l41: Document CS35l41 shared boost - ALSA: hda: cs35l41: Ensure firmware/tuning pairs are always loaded - ALSA: hda: cs35l41: Enable Amp High Pass Filter - ALSA: cs35l41: Use mbox command to enable speaker output for external boost - ALSA: cs35l41: Poll for Power Up/Down rather than waiting a fixed delay - ALSA: hda: cs35l41: Check mailbox status of pause command after firmware load - ALSA: hda: cs35l41: Ensure we correctly re-sync regmap before system suspending. - ALSA: hda: cs35l41: Ensure we pass up any errors during system suspend. - ALSA: hda: cs35l41: Move Play and Pause into separate functions - ALSA: hda: hda_component: Add pre and post playback hooks to hda_component - ALSA: hda: cs35l41: Use pre and post playback hooks - ALSA: hda: cs35l41: Rework System Suspend to ensure correct call separation - ALSA: hda: cs35l41: Add device_link between HDA and cs35l41_hda - ALSA: hda: cs35l41: Ensure amp is only unmuted during playback * Reboot command powers off the system (LP: #2029332) - x86/smp: Make stop_other_cpus() more robust - x86/smp: Dont access non-existing CPUID leaf * losetup with mknod fails on jammy with kernel 5.15.0-69-generic (LP: #2015400) - loop: deprecate autoloading callback loop_probe() - loop: do not enforce max_loop hard limit by (new) default * Fix UBSAN in Intel EDAC driver (LP: #2028746) - EDAC/skx_common: Enable EDAC support for the "near" memory - EDAC/skx_common: Delete duplicated and unreachable code - EDAC/i10nm: Add Intel Emerald Rapids server support - EDAC/i10nm: Make more configurations CPU model specific - EDAC/i10nm: Add Intel Granite Rapids server support - EDAC/i10nm: Skip the absent memory controllers * Make TTY switching possible for NVIDIA when it's boot VGA (LP: #2028749) - drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers - video/aperture: use generic code to figure out the vga default device - drm/aperture: Remove primary argument - video/aperture: Only kick vgacon when the pdev is decoding vga - video/aperture: Move vga handling to pci function - video/aperture: Drop primary argument - video/aperture: Only remove sysfb on the default vga pci device - fbdev: Simplify fb_is_primary_device for x86 -
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
This bug was fixed in the package linux-hwe-5.15 - 5.15.0-83.92~20.04.1 --- linux-hwe-5.15 (5.15.0-83.92~20.04.1) focal; urgency=medium * focal/linux-hwe-5.15: 5.15.0-83.92~20.04.1 -proposed tracker (LP: #2030420) [ Ubuntu: 5.15.0-83.92 ] * jammy/linux: 5.15.0-83.92 -proposed tracker (LP: #2031132) * libgnutls report "trap invalid opcode" when trying to install packages over https (LP: #2031093) - [Config]: disable CONFIG_GDS_FORCE_MITIGATION [ Ubuntu: 5.15.0-81.90 ] * jammy/linux: 5.15.0-81.90 -proposed tracker (LP: #2030422) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] resync getabis - debian/dkms-versions -- update from kernel-versions (main/2023.08.07) * CVE-2022-40982 - x86/mm: Initialize text poking earlier - x86/mm: fix poking_init() for Xen PV guests - x86/mm: Use mm_alloc() in poking_init() - mm: Move mm_cachep initialization to mm_init() - init: Provide arch_cpu_finalize_init() - x86/cpu: Switch to arch_cpu_finalize_init() - ARM: cpu: Switch to arch_cpu_finalize_init() - sparc/cpu: Switch to arch_cpu_finalize_init() - um/cpu: Switch to arch_cpu_finalize_init() - init: Remove check_bugs() leftovers - init: Invoke arch_cpu_finalize_init() earlier - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() - x86/init: Initialize signal frame size late - x86/fpu: Remove cpuinfo argument from init functions - x86/fpu: Mark init functions __init - x86/fpu: Move FPU initialization into arch_cpu_finalize_init() - x86/xen: Fix secondary processors' FPU initialization - x86/speculation: Add Gather Data Sampling mitigation - x86/speculation: Add force option to GDS mitigation - x86/speculation: Add Kconfig option for GDS - KVM: Add GDS_NO support to KVM - Documentation/x86: Fix backwards on/off logic about YMM support - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and CONFIG_GDS_FORCE_MITIGATION * CVE-2023-3609 - net/sched: cls_u32: Fix reference counter leak leading to overflow * CVE-2023-21400 - io_uring: ensure IOPOLL locks around deferred work * CVE-2023-4015 - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain - netfilter: nf_tables: unbind non-anonymous set if rule construction fails - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR * CVE-2023-3995 - netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID * CVE-2023-3777 - netfilter: nf_tables: skip bound chain on rule flush * losetup with mknod fails on jammy with kernel 5.15.0-69-generic (LP: #2015400) - loop: do not enforce max_loop hard limit by (new) default * Include the MAC address pass through function on RTL8153DD-CG (LP: #2020295) - r8152: add USB device driver for config selection * Jammy update: v5.15.116 upstream stable release (LP: #2029401) - RDMA/bnxt_re: Fix the page_size used during the MR creation - RDMA/efa: Fix unsupported page sizes in device - RDMA/hns: Fix base address table allocation - RDMA/hns: Modify the value of long message loopback slice - dmaengine: at_xdmac: Move the free desc to the tail of the desc list - dmaengine: at_xdmac: fix potential Oops in at_xdmac_prep_interleaved() - RDMA/bnxt_re: Fix a possible memory leak - RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx - iommu/rockchip: Fix unwind goto issue - iommu/amd: Don't block updates to GATag if guest mode is on - dmaengine: pl330: rename _start to prevent build error - riscv: Fix unused variable warning when BUILTIN_DTB is set - net/mlx5: fw_tracer, Fix event handling - net/mlx5e: Don't attach netdev profile while handling internal error - net: mellanox: mlxbf_gige: Fix skb_panic splat under memory pressure - netrom: fix info-leak in nr_write_internal() - af_packet: Fix data-races of pkt_sk(sk)->num. - amd-xgbe: fix the false linkup in xgbe_phy_status - mtd: rawnand: ingenic: fix empty stub helper definitions - RDMA/irdma: Add SW mechanism to generate completions on error - RDMA/irdma: Prevent QP use after free - RDMA/irdma: Fix Local Invalidate fencing - af_packet: do not use READ_ONCE() in packet_bind() - tcp: deny tcp_disconnect() when threads are waiting - tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN state if user_mss set - net/sched: sch_ingress: Only create under TC_H_INGRESS - net/sched: sch_clsact: Only create under TC_H_CLSACT - net/sched: Reserve TC_H_INGRESS (TC_H_CLSACT) for ingress (clsact) Qdiscs - net/sched: Prohibit regrafting ingress or clsact Qdiscs - net: sched: fix NULL pointer dereference in mq_attach - net/netlink: fix NETLINK_LIST_MEMBERSHIPS length report - udp6: Fix race condition in udp6_sendmsg & connect - net/mlx5e: Fix error
[Kernel-packages] [Bug 2029332] Re: Reboot command powers off the system
This bug was fixed in the package linux-hwe-6.2 - 6.2.0-32.32~22.04.1 --- linux-hwe-6.2 (6.2.0-32.32~22.04.1) jammy; urgency=medium * jammy/linux-hwe-6.2: 6.2.0-32.32~22.04.1 -proposed tracker (LP: #2030380) [ Ubuntu: 6.2.0-32.32 ] * lunar/linux: 6.2.0-32.32 -proposed tracker (LP: #2031134) * libgnutls report "trap invalid opcode" when trying to install packages over https (LP: #2031093) - [Config]: disable CONFIG_GDS_FORCE_MITIGATION [ Ubuntu: 6.2.0-30.30 ] * lunar/linux: 6.2.0-30.30 -proposed tracker (LP: #2030381) * CVE-2022-40982 - init: Provide arch_cpu_finalize_init() - x86/cpu: Switch to arch_cpu_finalize_init() - ARM: cpu: Switch to arch_cpu_finalize_init() - ia64/cpu: Switch to arch_cpu_finalize_init() - m68k/cpu: Switch to arch_cpu_finalize_init() - mips/cpu: Switch to arch_cpu_finalize_init() - sh/cpu: Switch to arch_cpu_finalize_init() - sparc/cpu: Switch to arch_cpu_finalize_init() - um/cpu: Switch to arch_cpu_finalize_init() - init: Remove check_bugs() leftovers - init: Invoke arch_cpu_finalize_init() earlier - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() - x86/init: Initialize signal frame size late - x86/fpu: Remove cpuinfo argument from init functions - x86/fpu: Mark init functions __init - x86/fpu: Move FPU initialization into arch_cpu_finalize_init() - x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build - x86/xen: Fix secondary processors' FPU initialization - x86/speculation: Add Gather Data Sampling mitigation - x86/speculation: Add force option to GDS mitigation - x86/speculation: Add Kconfig option for GDS - KVM: Add GDS_NO support to KVM - Documentation/x86: Fix backwards on/off logic about YMM support - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and CONFIG_GDS_FORCE_MITIGATION * CVE-2023-4015 - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain - netfilter: nf_tables: unbind non-anonymous set if rule construction fails - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR * CVE-2023-3995 - netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID * CVE-2023-3777 - netfilter: nf_tables: skip bound chain on rule flush * CVE-2023-3609 - net/sched: cls_u32: Fix reference counter leak leading to overflow * NULL pointer dereference on CS35L41 HDA AMP (LP: #2029199) - ASoC: cs35l41: Refactor error release code - ALSA: cs35l41: Add shared boost feature - ASoC: dt-bindings: cirrus, cs35l41: Document CS35l41 shared boost - ALSA: hda: cs35l41: Ensure firmware/tuning pairs are always loaded - ALSA: hda: cs35l41: Enable Amp High Pass Filter - ALSA: cs35l41: Use mbox command to enable speaker output for external boost - ALSA: cs35l41: Poll for Power Up/Down rather than waiting a fixed delay - ALSA: hda: cs35l41: Check mailbox status of pause command after firmware load - ALSA: hda: cs35l41: Ensure we correctly re-sync regmap before system suspending. - ALSA: hda: cs35l41: Ensure we pass up any errors during system suspend. - ALSA: hda: cs35l41: Move Play and Pause into separate functions - ALSA: hda: hda_component: Add pre and post playback hooks to hda_component - ALSA: hda: cs35l41: Use pre and post playback hooks - ALSA: hda: cs35l41: Rework System Suspend to ensure correct call separation - ALSA: hda: cs35l41: Add device_link between HDA and cs35l41_hda - ALSA: hda: cs35l41: Ensure amp is only unmuted during playback * Reboot command powers off the system (LP: #2029332) - x86/smp: Make stop_other_cpus() more robust - x86/smp: Dont access non-existing CPUID leaf * losetup with mknod fails on jammy with kernel 5.15.0-69-generic (LP: #2015400) - loop: deprecate autoloading callback loop_probe() - loop: do not enforce max_loop hard limit by (new) default * Fix UBSAN in Intel EDAC driver (LP: #2028746) - EDAC/skx_common: Enable EDAC support for the "near" memory - EDAC/skx_common: Delete duplicated and unreachable code - EDAC/i10nm: Add Intel Emerald Rapids server support - EDAC/i10nm: Make more configurations CPU model specific - EDAC/i10nm: Add Intel Granite Rapids server support - EDAC/i10nm: Skip the absent memory controllers * Make TTY switching possible for NVIDIA when it's boot VGA (LP: #2028749) - drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers - video/aperture: use generic code to figure out the vga default device - drm/aperture: Remove primary argument - video/aperture: Only kick vgacon when the pdev is decoding vga - video/aperture: Move vga handling to pci function - video/aperture: Drop primary argument - video/aperture: Only remove sysfb on the default vga pci device - fbdev: Simplify fb_is_primary_device for x86 -
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
Sep 04 14:16:11 ahmed-OptiPlex-3090 kernel: r8169 :03:00.0 eth0: RTL8168h/8111h, c0:25:a5:b6:a9:22, XID 541, IRQ 127 Sep 04 14:16:11 ahmed-OptiPlex-3090 kernel: r8169 :03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] Sep 04 14:16:11 ahmed-OptiPlex-3090 kernel: r8169 :03:00.0 enp3s0: renamed from eth0 Sep 04 14:16:13 ahmed-OptiPlex-3090 kernel: Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC) Sep 04 14:16:13 ahmed-OptiPlex-3090 kernel: r8169 :03:00.0 enp3s0: Link is Down Sep 04 14:16:14 ahmed-OptiPlex-3090 kernel: r8169 :03:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Sep 04 14:16:16 ahmed-OptiPlex-3090 kernel: r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
There seems to be two issues. For those affected, can you please post the output of `sudo journalctl --dmesg | grep r8169`? -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7 12:39:19 2023] call_timer_fn+0x29/0x160 [Mon Aug
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@Stuart Pook (slp110264) Please DON'T use ppa:oem-solutions-group/intel-ipu6 because it is a development PPA that it will often break the MIPI camera during the development. You can use `sudo add-apt-repository --remove ppa:oem-solutions- group/intel-ipu6` to remove it. However there may still be some broken packages in your system that you need to downgrade/remove them manually. The simple way is to reinstall Ubuntu 22.04.3 on your Dell XPS 13 9320 again and upgrade the whole system to the latest. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 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.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
great news thanks, should we upgrade kernel or wait for ubuntu 23.10 ? -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7 12:39:19 2023] call_timer_fn+0x29/0x160 [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
hi all, the webcam on my Dell XPS 9320 was working until this week. I just did the standard required system upgrades and it has stopped working. zbarcam shows an empty black image. cheese pauses before showing "There was an error playing video from the webcam". Chromium https://webcamtests.com/ detects my Intel MIPI Camera but after I click on "Test my cam" I get the error: "The video track is paused." What should I check? :; sudo apt upgrade && sudo apt update && dpkg -l oem-somerville-tentacool-meta Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Get more security updates through Ubuntu Pro with 'esm-apps' enabled: maven libmaven3-core-java libavdevice58 ffmpeg libopenexr25 libpostproc55 libmagickcore-6.q16-6-extra libavcodec58 libmagickwand-6.q16-6 libavutil56 libswscale5 libmagickcore-6.q16-6 libswresample3 imagemagick-6-common libavformat58 libavfilter7 Learn more about Ubuntu Pro at https://ubuntu.com/pro 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Hit:1 http://fr.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://dell.archive.canonical.com jammy InRelease Hit:3 http://fr.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu jammy InRelease Get:5 http://fr.archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB] Hit:6 http://security.ubuntu.com/ubuntu jammy-security InRelease Fetched 109 kB in 1s (216 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---= ii oem-somerville-tentacool-meta 22.04ubuntu6 all hardware support for Dell XPS 13 9320 :; zbarcam :; sudo dmesg | grep ipu6 [ 10.199619] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 10.199821] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x2) [ 10.199845] intel-ipu6 intel-ipu: physical base address 0x603c00 [ 10.199846] intel-ipu6 intel-ipu: mapped as: 0xa28c5f74 [ 10.199908] intel-ipu6 intel-ipu: Unable to set secure mode [ 10.199910] intel-ipu6 intel-ipu: IPU in non-secure mode [ 10.199911] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 10.199913] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 10.199973] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 10.199976] intel-ipu6 intel-ipu: IPC reset done [ 10.199978] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 10.210322] intel-ipu6 intel-ipu: FW version: 20220510 [ 10.212444] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 10.295703] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 10.296695] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 19.578111] intel-ipu6-isys intel-ipu6-isys0: bind ov01a10 17-0036 nlanes is 1 port is 2 [ 19.578339] intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. [ 155.172121] intel-ipu6-isys intel-ipu6-isys0: dma alloc of size 536903680 failed :; sudo dmesg | grep 9320 [0.00] DMI: Dell Inc. XPS 9320/0P9FNW, BIOS 2.2.1 04/17/2023 :; chromium https://webcamtests.com/ Gtk-Message: 12:28:27.557: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. (chrome:31619): Gtk-WARNING **: 12:28:27.599: GTK+ module /snap/chromium/2590/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 12:28:27.599: Failed to load module "canberra-gtk-module" (chrome:31619): Gtk-WARNING **: 12:28:27.600: GTK+ module /snap/chromium/2590/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 12:28:27.600: Failed to load module "canberra-gtk-module" [31619:31619:0904/122827.620588:ERROR:chrome_browser_cloud_management_controller.cc(163)] Cloud management controller initialization aborted as CBCM is not enabled. WARNING: Kernel has no file descriptor comparison support: Operation not permitted [31619:31745:0904/122830.840454:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. ^C :; systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. :; uname -a Linux dataseat 6.2.0-31-generic #31~22.04.1-Ubuntu SMP
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
"Fixed with kernel v6.4.7". If so, what to do with 6.2?.. -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7 12:39:19 2023] call_timer_fn+0x29/0x160 [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7
[Kernel-packages] [Bug 2033756] Re: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day
Hello Martin Many thanks for your reply and the hope your message is bringing. This morning I just decided to give another try to recent kernel versions, funny you suggested this ^^ Previously, I used the tool `mainline`, but I'd not much success (I experienced more crashes). Today, I decided to go for https://github.com/zabbly/ and I'm now running a kernel 6.4.13 with ubuntu 22.04. I was not aware of the parameter `amd_pstate=active` so it's not enabled. I'll try this later. I want to give a chance to the 6.4 and change param one at a time. With earlier kernels I tried `amdgpu.dcdebugmask=0x10` but it was not bullet proof for me... So since a moment I removed this flag. Some questions, on your side did you experienced only system freezes or some other "strange bugs". Here I'm also having: Soft lockup, kernel NULL point dereference, kernel unable to handle page fault... I've found those messages in the lots of log files I have now. From a user perspective I'd say I've noticed them because some firefox tab or some vscode windows were crashing. Regards, JF -- 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/2033756 Title: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day Status in linux package in Ubuntu: Confirmed Bug description: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 I have some technical knowledge, so I can do some tests if that can help solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jf 2338 F pulseaudio /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio /dev/snd/controlC0: jf 2338 F pulseaudio /dev/snd/controlC2: jf 2338 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 10:34:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2023-06-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21J5CTO1WW ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-82-generic root=UUID=ad3cccf2-3072-4b29-84f0-ed7b41dd4de6 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-08-12 (19 days ago) dmi.bios.date: 03/21/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21J5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21J5CTO1WW:pvrThinkPadP14sGen3:rvnLENOVO:rn21J5CTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21J5_BU_Think_FM_ThinkPadP14sGen3: dmi.product.family: ThinkPad P14s Gen 3 dmi.product.name: 21J5CTO1WW dmi.product.sku: LENOVO_MT_21J5_BU_Think_FM_ThinkPad P14s Gen 3 dmi.product.version: ThinkPad P14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756/+subscriptions
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
https://bugzilla.kernel.org/show_bug.cgi?id=217635#c30 -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7 12:39:19 2023] call_timer_fn+0x29/0x160 [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=90ca51e8c654 ** Bug watch added: Linux Kernel Bug Tracker #217635 https://bugzilla.kernel.org/show_bug.cgi?id=217635 -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon Aug 7 12:39:19 2023] ?
[Kernel-packages] [Bug 2029917] Re: [Potential Regression] cpuhotplug related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
This also applies to cpu-hotplug:cpu-on-off-test.sh in
ubuntu_kernel_selftests
It can trigger the same error with AWS 5.4.0-1108-aws on c3.xlarge as well
[ 549.176719] IRQ 75: no longer affine to CPU3
[ 549.176735] IRQ 76: no longer affine to CPU3
[ 549.176750] IRQ 77: no longer affine to CPU3
[ 549.178081] smpboot: CPU 3 is now offline
[ 549.234896] installing Xen timer for CPU 3
[ 549.235323] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 549.236789] [ cut here ]
[ 549.236791] kernel BUG at arch/x86/xen/spinlock.c:62!
[ 549.237807] invalid opcode: [#1] SMP PTI
[ 549.238692] CPU: 3 PID: 24 Comm: cpuhp/3 Not tainted 5.4.0-1108-aws
#116-Ubuntu
Bug title / content updated.
** Description changed:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
+ cpu-hotplug related tests will crash the instance, they are:
+ * cpuset_hotplug in ubuntu_ltp_controllers
+ * cpuhotplug:cpuhotplug02 in ubuntu_ltp (comment #7 in this bug)
+ * cpu-hotplug:cpu-on-off-test.sh in ubuntu_kernel_selftests (comment #8 in
this bug)
+
+ Take cpuset_hotplug in ubuntu_ltp_controllers for example.
+
There is no output from the test itself (looks like it has crashed):
- START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
- Persistent state client._record_indent now set to 2
- Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
- Waiting for pid 925631 for 4500 seconds
- System python is too old, crash handling disabled
+ START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
+ Persistent state client._record_indent now set to 2
+ Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
+ Waiting for pid 925631 for 4500 seconds
+ System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
https://lore.kernel.org/netdev/c3465166-f04d-fcf5-d284-57357abb3...@freenet.de/ https://lore.kernel.org/netdev/ddadceae-19c9-81b8-47b5-a4ff85e25...@gmail.com/ https://lore.kernel.org/netdev/d198a4d6-0c91-7870-9648-5a087fe63...@gmail.com/ -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon
[Kernel-packages] [Bug 2029917] Re: [Potential Regression] cpuhotplug related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
** Summary changed:
- [Potential Regression] ubuntu_ltp_controllers/cpuset_hotplug and
ubuntu_ltp/cpuhotplug:cpuhotplug02 triggers kernel bug
(arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
+ [Potential Regression] cpuhotplug related tests triggers kernel bug
(arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] cpuhotplug related tests triggers kernel bug
(arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.961445] xen_init_lock_cpu+0x78/0xd0
[ 3451.963057] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.964810] xen_cpu_up_online+0xe/0x20
[ 3451.966415] cpuhp_invoke_callback+0x8a/0x580
[ 3451.968144] cpuhp_thread_fun+0xb8/0x120
[Kernel-packages] [Bug 2033533] Re: [qxl] installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt
So I've just double checked, and enabling plymouth debug in the grub
prior to installation means you're not greeted with a black screen, and
don't need to press an arrow key. Could that be a helpful indicator at
all? I can't collect logs because when I do ... the issue is gone
--
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/2033533
Title:
[qxl] installing with lvm and encryption requires arrow key spam after
reboot to get to encryption passphrase prompt
Status in linux package in Ubuntu:
Confirmed
Status in plymouth package in Ubuntu:
New
Bug description:
This also happens with the canary image and is happening with the
Mantic daily image.
When installing with LVM and encryption, after the "remove
installation medium and press enter to reboot", the user is greeted
with a permanent black screen. After pressing arrow keys, the gui
prompt is then shown to prompt the user to put in the encryption
passphrase.
It is also somehow possible to not get the black screen by changing
the grub prior to installing by removing splash from the grub options.
The user is then greeted with a text-only passphrase prompt after
rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages. If that does not
work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033533/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux-hwe-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid xhci_pci_renesas nvme_common realtek wmi hid [44566.731529] CPU: 15 PID: 29333 Comm: kworker/u32:1 Tainted: PW O 6.2.0-31-generic #31~22.04.1-Ubuntu [44566.731531] Hardware name: LENOVO 82MJ/LNVNB161216, BIOS H3CN36WW(V2.06) 09/30/2022 [44566.731533] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [44566.731539] RIP: 0010:amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731702] Code: 31 f6 31 ff c3 cc cc cc cc 44 89 ea 4c 89 e6 4c 89 f7 e8 8f fc ff ff 5b 41 5c 41
[Kernel-packages] [Bug 2033996] Re: ugreen bluetooth 5 usb RTL8761BUV not discovering device
Try `journalctl -b -1` or any other previous boots that runs the 6.2 kernel. -- 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/2033996 Title: ugreen bluetooth 5 usb RTL8761BUV not discovering device Status in linux package in Ubuntu: Incomplete Bug description: MANUFACTURER: UGreen Chipset: RTL8761BUV Device: Bluetooth 5.0 Issue: This kernel(5.15.0-82) detects the usb dongle but the device itself can't detect any bluetooth devices. Resolution: Switched kernel to 6.2.0-31, but the support for the kernel is only up to February 2024, vs 5.15.0-82 which has support until April 2027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033996/+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 2033996] Re: ugreen bluetooth 5 usb RTL8761BUV not discovering device
There's nothing we can do without logs. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033996 Title: ugreen bluetooth 5 usb RTL8761BUV not discovering device Status in linux package in Ubuntu: Incomplete Bug description: MANUFACTURER: UGreen Chipset: RTL8761BUV Device: Bluetooth 5.0 Issue: This kernel(5.15.0-82) detects the usb dongle but the device itself can't detect any bluetooth devices. Resolution: Switched kernel to 6.2.0-31, but the support for the kernel is only up to February 2024, vs 5.15.0-82 which has support until April 2027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033996/+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 2029917] Re: [Potential Regression] ubuntu_ltp_controllers/cpuset_hotplug and ubuntu_ltp/cpuhotplug:cpuhotplug02 triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel pani
** Summary changed:
- [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers
kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
+ [Potential Regression] ubuntu_ltp_controllers/cpuset_hotplug and
ubuntu_ltp/cpuhotplug:cpuhotplug02 triggers kernel bug
(arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] ubuntu_ltp_controllers/cpuset_hotplug and
ubuntu_ltp/cpuhotplug:cpuhotplug02 triggers kernel bug
(arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.961445] xen_init_lock_cpu+0x78/0xd0
[ 3451.963057] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.964810] xen_cpu_up_online+0xe/0x20
[ 3451.966415]
[Kernel-packages] [Bug 2029917] Re: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
The cpuhotplug02 test in ubuntu_ltp can trigger the same error message
with AWS 5.4.0-1108-aws
[ 366.764348] [ cut here ]
[ 366.764350] kernel BUG at arch/x86/xen/spinlock.c:62!
[ 366.765592] invalid opcode: [#1] SMP PTI
(system rebooted here)
The console output is useless in this case because the system got
rebooted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers
triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on
AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.961445] xen_init_lock_cpu+0x78/0xd0
[ 3451.963057] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.964810] xen_cpu_up_online+0xe/0x20
[ 3451.966415] cpuhp_invoke_callback+0x8a/0x580
[ 3451.968144]
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+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 2033756] Re: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day
Hello! I have had the same laptop for some time and have been battling with the same issues. According to my experience, the solution is to find a distro with a >6.3 kernel and set amd_pstate=active as boot parameters. Alternatively, if on an earlier kernel, you can try amdgpu.dcdebugmask=0x10 as boot parameter. I'm currently running Ubuntu 23.10 and it's very stable save for the occasional gnome shell crash which does not freeze or require restart. So far no gpu-related freezes. Only suspend and dim screen don't work in Wayland, but do in xorg, where, on the other hand, the touch pad three-finger swipe doesn't work. BW, Martin -- 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/2033756 Title: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day Status in linux package in Ubuntu: Confirmed Bug description: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 I have some technical knowledge, so I can do some tests if that can help solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jf 2338 F pulseaudio /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio /dev/snd/controlC0: jf 2338 F pulseaudio /dev/snd/controlC2: jf 2338 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 10:34:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2023-06-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21J5CTO1WW ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-82-generic root=UUID=ad3cccf2-3072-4b29-84f0-ed7b41dd4de6 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-08-12 (19 days ago) dmi.bios.date: 03/21/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21J5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21J5CTO1WW:pvrThinkPadP14sGen3:rvnLENOVO:rn21J5CTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21J5_BU_Think_FM_ThinkPadP14sGen3: dmi.product.family: ThinkPad P14s Gen 3 dmi.product.name: 21J5CTO1WW dmi.product.sku: LENOVO_MT_21J5_BU_Think_FM_ThinkPad P14s Gen 3 dmi.product.version: ThinkPad P14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756/+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 2029917] Re: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
I got this hammered again manually this morning by just running the
cpuset_hotplug test with ltp
$ cat /home/ubuntu/short
cpuset_hotplugcpuset_hotplug_test.sh
$ sudo /opt/ltp/runltp -f /home/ubuntu/short ; sudo reboot
* with -1160 the fail rate is 5 out of 25 attempts
* with -1159 deb downloaded from the link you provided, the fail rate is 2 out
of 25 attempts
* with -1158 the fail rate is 4 out of 25 attempts
I am not sure why this seems failing constantly when being tested on our
jenkins. Probably because of other tests started before this
cpuset_hotplug test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers
triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on
AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ?
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2033533] Status changed to Confirmed
This change was made by a bot.
** 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/2033533
Title:
[qxl] installing with lvm and encryption requires arrow key spam after
reboot to get to encryption passphrase prompt
Status in linux package in Ubuntu:
Confirmed
Status in plymouth package in Ubuntu:
New
Bug description:
This also happens with the canary image and is happening with the
Mantic daily image.
When installing with LVM and encryption, after the "remove
installation medium and press enter to reboot", the user is greeted
with a permanent black screen. After pressing arrow keys, the gui
prompt is then shown to prompt the user to put in the encryption
passphrase.
It is also somehow possible to not get the black screen by changing
the grub prior to installing by removing splash from the grub options.
The user is then greeted with a text-only passphrase prompt after
rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages. If that does not
work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033533/+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 2033533] Re: installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt
Sorry it looks like I was completely wrong. qxl *does* support the
preferred "modern" DRM/KMS graphics interface as shown in your log
files. This seems to be some kind of qxl kernel bug or maybe Plymouth
race condition.
I can only suggest collecting more Plymouth debug logs until the bug
happens again.
** Project changed: subiquity => ubuntu
** No longer affects: ubuntu
** Package changed: ubiquity (Ubuntu) => linux (Ubuntu)
** Tags added: qxl
** Summary changed:
- installing with lvm and encryption requires arrow key spam after reboot to
get to encryption passphrase prompt
+ [qxl] installing with lvm and encryption requires arrow key spam after reboot
to get to encryption passphrase prompt
--
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/2033533
Title:
[qxl] installing with lvm and encryption requires arrow key spam after
reboot to get to encryption passphrase prompt
Status in linux package in Ubuntu:
Confirmed
Status in plymouth package in Ubuntu:
New
Bug description:
This also happens with the canary image and is happening with the
Mantic daily image.
When installing with LVM and encryption, after the "remove
installation medium and press enter to reboot", the user is greeted
with a permanent black screen. After pressing arrow keys, the gui
prompt is then shown to prompt the user to put in the encryption
passphrase.
It is also somehow possible to not get the black screen by changing
the grub prior to installing by removing splash from the grub options.
The user is then greeted with a text-only passphrase prompt after
rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages. If that does not
work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
[Kernel-packages] [Bug 2033744] Re: Failed to resume from suspend in linux kernel 6.2.0.31
*** This bug is a duplicate of bug 2031969 *** https://bugs.launchpad.net/bugs/2031969 ** This bug has been marked a duplicate of bug 2031969 Ubuntu 23.04: Suspend & Power off -- 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/2033744 Title: Failed to resume from suspend in linux kernel 6.2.0.31 Status in linux package in Ubuntu: Confirmed Bug description: If system suspended, system can't resume and screen can't display anything, but my computer hardware still running. In some case, screen can show GDM but it content is freeze and can't do anything. I boot to older kernel because this issue This is my system info : $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 $ inxi -Fzxxx System: Kernel: 6.2.0-27-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.3 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM3 v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: LENOVO product: 20KEA062UK v: ThinkPad X280 serial: Chassis: type: 10 serial: Mobo: LENOVO model: 20KEA062UK v: SDK0J40697 WIN serial: UEFI: LENOVO v: N20ET64P (1.49 ) date: 11/21/2022 Battery: ID-1: BAT0 charge: 34.8 Wh (81.3%) condition: 42.8/48.0 Wh (89.2%) volts: 12.2 min: 11.5 model: SMP 01AV471 type: Li-poly serial: status: discharging cycles: 455 CPU: Info: quad core model: Intel Core i5-8350U bits: 64 type: MT MCP smt: enabled arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 1844 high: 2265 min/max: 400/3600 cores: 1: 2265 2: 2092 3: 1900 4: 899 5: 1900 6: 1900 7: 1900 8: 1900 bogomips: 30399 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300 Device-2: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:3 chip-ID: 5986:2113 class-ID: 0e02 Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: 0 Monitor-1: eDP-1 model: AU Optronics 0x106c res: 1366x768 dpi: 126 size: 276x155mm (10.87x6.1") diag: 317mm (12.5") modes: 1366x768 API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~23.04.1 renderer: Mesa Intel UHD Graphics 620 (KBL GT2) direct-render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403 Sound API: ALSA v: k6.2.0-27-generic running: yes Sound Server-1: PulseAudio v: 16.1 running: no Sound Server-2: PipeWire v: 0.3.65 running: yes Network: Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 3b:00.0 chip-ID: 8086:24fd class-ID: 0280 IF: wlp59s0 state: up mac: IF-ID-1: virbr0 state: down mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:2 chip-ID: 8087:0a2b class-ID: e001 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: no address: Drives: Local Storage: total: 238.47 GiB used: 163.05 GiB (68.4%) ID-1: /dev/sda model: M.2 SATA SSD 256GB size: 238.47 GiB speed: 6.0 Gb/s type: SSD serial: rev: 1C0 scheme: GPT Partition: ID-1: / size: 238 GiB used: 163.04 GiB (68.5%) fs: btrfs dev: /dev/sda2 ID-2: /boot/efi size: 486 MiB used: 13.3 MiB (2.7%) fs: vfat dev: /dev/sda1 ID-3: /home size: 238 GiB used: 163.04 GiB (68.5%) fs: btrfs dev: /dev/sda2 Swap: ID-1: swap-1 type: zram size: 7.5 GiB used: 4 MiB (0.1%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 52.0 C mobo: N/A Fan Speeds (RPM): fan-1: 0 Info: Processes: 312 Uptime: 1h 1m wakeups: 7 Memory: 7.5 GiB used: 3.36 GiB (44.9%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.3.0 alt: 12 clang: 15.0.7 Packages: 2439 pm: dpkg pkgs: 2398 pm: flatpak pkgs: 30 pm: snap pkgs: 11 Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.25 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 2033533] [NEW] installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt
You have been subscribed to a public bug:
This also happens with the canary image and is happening with the Mantic
daily image.
When installing with LVM and encryption, after the "remove installation
medium and press enter to reboot", the user is greeted with a permanent
black screen. After pressing arrow keys, the gui prompt is then shown to
prompt the user to put in the encryption passphrase.
It is also somehow possible to not get the black screen by changing the
grub prior to installing by removing splash from the grub options. The
user is then greeted with a text-only passphrase prompt after rebooting.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/vgubuntu-root
ro quiet splash vt.handoff=7
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package. Please
retry after updating the indexes of available packages. If that does not work,
then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug apport-collected mantic third-party-packages
wayland-session
--
installing with lvm and encryption requires arrow key spam after reboot to get
to encryption passphrase prompt
https://bugs.launchpad.net/bugs/2033533
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
** Description changed: + [Impact] + After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. + + [Fix] + + Updated patch from linux-next: + https://patchwork.freedesktop.org/patch/538562/ + + [Test Case] + + Suspend,resume,shutdown,reboot should all work correctly. No nouveau + stack trace in the kernel log. + + [Where Problems Could Occur] + + Limited to nouveau driver that wants to load nonexistent ACR firmware. + Only nvidia GPUs are affected. + + [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
Thanks for the confirmation, will send the patch to our mailing list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. [Fix] Updated patch from linux-next: https://patchwork.freedesktop.org/patch/538562/ [Test Case] Suspend,resume,shutdown,reboot should all work correctly. No nouveau stack trace in the kernel log. [Where Problems Could Occur] Limited to nouveau driver that wants to load nonexistent ACR firmware. Only nvidia GPUs are affected. [Additional information] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
** Tags added: verification-needed-jammy-linux-oem-6.5 -- 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/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Invalid Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2025672 [Impact] Realtek RTL8852CE WiFi 6E/BT Combo takes new firmware to enable 6E features. [Fix] * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) [Test Case] Basic bluetooth, wifi operations. This is verified with all related kernel/series combinations: * linux-hwe5.19/jammy * linux-hwe-6.2/jammy * linux-oem-6.0/jammy * linux-oem-6.1/jammy * linux-oem-6.5/jammy * ilnux/mantic [Where problems could occur] New device firmware blob, even blob format changes. Expect bugs, power consumption issues, etc. [Other Info] Bluetooth V2 firmware support was first landed to v6.4, and the binary rename in linux-next now. To preserve consistency, Unstable, Mantic and OEM-6.5 kernels are nominated for fix. As for linux-firmware, the only target is Jammy. == original bug description == Support Realtek RTL8852CE WiFi 6E/BT Combo * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025672/+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 2028746] Re: Fix UBSAN in Intel EDAC driver
** Tags removed: verification-needed-jammy-linux-oem-6.1 verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028746 Title: Fix UBSAN in Intel EDAC driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [Impact] UBSAN complains shift-out-of-bounds: [ 13.875276] UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:369:16 [ 13.875279] shift exponent -66 is negative [Fix] Skip the absent memory controllers so ~0 won't be used. [Test] Boot system with patch applied, no more UBSAN error in dmesg. [Where problems could occur] The fix itself is trivial, however the dependency patches may bring behavioural changes as new platform support is also added. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028746/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
@juergh, we tested your kernel on one of our notebooks where the problem occurred. Shut down and reboot hasn't shown this behaviour, yet. Looks promising! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+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
