Re: [Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
+ Sumit On Mon, Sep 11, 2023 at 11:40 PM Jeff Lane <2029...@bugs.launchpad.net> wrote: > Why is this being requested? What specific certification blockers or > customer deployments does this affect? > > We don't generally just pull large numbers of patches in like this > without a business justification to backport them, unfortunately, the > aim is to update the driver to resolve issues that are affecting folks > in the field. If someone needs a new driver version the first > suggestion is that they should be running the latest HWE kernel which is > where those updates normally land. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2029905 > > Title: > [Ubuntu] mpi3mr: Include the latest patchset from upstream into > 22.04.1/later LTS > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > This BUG is created to integrate the latest mpi3mr driver available > upstream into the upcoming Ubuntu LTS OS inbox driver. > - The mpi3mr inbox driver version available in the latest LTS (22.04.02) > is 8.0.0.69.0. which is > considerably the base driver + management app support. > - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which > has various important features and > critical bugs. > > > Please include below the latest mpi3mr upstream patset: > > > git online commit id and description: > > f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O > f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O > 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap > 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in > mpi3mr_expander_add() > 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect > chain frame allocation > a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code > (0xF002) > b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const > 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 > e74f2fbd8b06 scsi: mpi3mr: Update copyright year > 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings > e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 > f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when > target is removed > 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds > 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset > 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault > ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() > c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() > d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() > d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in > mpi3mr_remove() > 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak > f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak > 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash > 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails > ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware > init path > 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller > init > 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced > logging is enabled > 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling > interrupt > 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include > e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization > 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes > eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to > alltgt_info->dmi > fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() > ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN > f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile > d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API > 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints > 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS > c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast > f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 > 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug > f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time > 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload > bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code > f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe > HBA > 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels > 47cd930ee6ae scsi: mpi3mr: Support new power management framework > ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files > 5ba207e55e7f scsi: mpi3mr: Fix error code in > mpi3mr_transport_smp_handler() > a113c02f5738 scsi: mpi3mr: Fix error codes in
[Kernel-packages] [Bug 2033267] Re: Nouveau driver crash with 6.2
*** This bug is a duplicate of bug 2031352 *** https://bugs.launchpad.net/bugs/2031352 Hi any news on this bug ? I'm still affected -- 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/2033267 Title: Nouveau driver crash with 6.2 Status in linux package in Ubuntu: Confirmed Bug description: Since 7th of august 2023 after upgrading my system (apt update; apt upgrade) I cannot shutdown my HP Zbook Studio G9 laptop. It hangs forever. The suspend mode is also not working anymore since then, apparently it goes in suspend mode but I can't resume it. The workaround is to hard power it down by pressing 10 seconds on the power button. It works fine until the 7th of august where I update it. Note that we are several people using the same hardware and almost the same installation (using ansible to manage the installation) that have the exact same issue. Here are my HW infos: HW Model: HP HP ZBook Studio 16 inch G9 Mobile Workstation PC Processor: 12th Gen Intel® Core™ i7-12800H × 20 Graphics: Mesa Intel® Graphics (ADL GT2) OS: Ubuntu 22.04.3 LTS 64bits GNOME version: 42.9 Windows System: x11 Description: Ubuntu 22.04.3 LTS Release: 22.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ltshb 3644 F pulseaudio /dev/snd/controlC0: ltshb 3644 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-06 (82 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP ZBook Studio 16 inch G9 Mobile Workstation PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: jammy Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2023 dmi.bios.release: 5.20 dmi.bios.vendor: HP dmi.bios.version: U99 Ver. 01.05.20 dmi.board.name: 89C3 dmi.board.vendor: HP dmi.board.version: KBC Version 10.5E.50 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 16.94 dmi.modalias: dmi:bvnHP:bvrU99Ver.01.05.20:bd02/21/2023:br5.20:efr16.94:svnHP:pnHPZBookStudio16inchG9MobileWorkstationPC:pvr:rvnHP:rn89C3:rvrKBCVersion10.5E.50:cvnHP:ct10:cvr:sku4Z8Q4AV: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 16 inch G9 Mobile Workstation PC dmi.product.sku: 4Z8Q4AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033267/+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 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.1 kernel
This issue does not exist in J-aws-6.2, J-azure-6.2, J-azure-fde-6.2, J-gcp-6.2, J-lowlatency-hwe-6.2 Still visible in J-oem-6.0, J-oem-6.1 -- 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/1995511 Title: net-build failed in ubuntu_kernel_selftests with 6.1 kernel Status in ubuntu-kernel-tests: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: Issue found with J-oem-6.0.0-1007.7 This is not a regression, issue exists before this kernel. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_cpu.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_numa.c -lnuma -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_dualstack.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseaddr_conflict.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include tls.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: tls.c:32:50: error: field ‘sm4gcm’ has incomplete type 32 | struct tls12_crypto_info_sm4_gcm sm4gcm; | ^~ tls.c:33:50: error: field ‘sm4ccm’ has incomplete type 33 | struct tls12_crypto_info_sm4_ccm sm4ccm; | ^~ tls.c: In function ‘tls_crypto_info_init’: tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 56 | case TLS_CIPHER_SM4_GCM: | ^~ | TLS_CIPHER_AES_GCM_256 tls.c:56:14: note: each undeclared identifier is reported only once for each function it appears in tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_gcm’ 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm); | ^~ tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 61 | case TLS_CIPHER_SM4_CCM: | ^~ | TLS_CIPHER_AES_CCM_128 tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_ccm’ 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm); | ^~ tls.c: At top level: tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 268 | .cipher_type = TLS_CIPHER_SM4_GCM, |^~ |TLS_CIPHER_AES_GCM_256 tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 274 | .cipher_type = TLS_CIPHER_SM4_CCM, |^~ |
[Kernel-packages] [Bug 2035166] 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 2035166 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 -- 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indicated by the following commit. d25ceb926436 KVM:
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
Thanks @mloza1 - I see well this looks different from the issue I am investigating, but maybe I can still help. There are 10s of thousands of changes between linux-image-5.15.0-25 and linux-image-5.15.0-67 so it's difficult to know what caused this. I think bisecting the changes is our best bet. Maybe you can try to narrow down which Ubuntu kernel started to fail this use-case? If you can find out which kernel version exactly started to fail that would be helpful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM hangs No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 I'm able to reproduce the issue using the following kernels: linux-image-5.15.0-67-generic_5.15.0-67.74_amd64.deb linux-image-5.15.0-68-generic_5.15.0-68.75_amd64.deb linux-image-5.15.0-69-generic_5.15.0-69.76_amd64.deb linux-image-5.15.0-70-generic_5.15.0-70.77_amd64.deb linux-image-5.15.0-72-generic_5.15.0-72.79_amd64.deb linux-image-5.15.0-73-generic_5.15.0-73.80_amd64.deb linux-image-5.15.0-74-generic_5.15.0-74.81_amd64.deb linux-image-5.15.0-75-generic_5.15.0-75.82_amd64.deb linux-image-5.15.0-77-generic_5.15.0-77.84_amd64.deb --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500/+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 2035166] [NEW] NULL Pointer Dereference During KVM MMU Page Invalidation
Public bug reported: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indicated by the following commit. d25ceb926436 KVM: x86/mmu: Track the number of TDP MMU pages, but not the actual pages While this patch doesn't modify the triggering logic, it replaces the problematic section with a more reliable approach while keeping the original logic unchanged. If the issue persists, it should not result in any memory access problems. We also requested the customer to set up a test environment and simulate a workload similar to the production environment. The patch worked well and did not introduce any adverse effects. [Test Plan] Reproducing the issue has proven to be challenging. Simulating heavy live migration activity in the customer's production environment is the appropriate approach to ensure that applying the patch will not result in any adverse effects. [Where problems could occur] The patch will impact the live migration workflow, but it only modifies the data structure in use, and no functionality will be altered. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Chengen Du (chengendu) Status: New ** Also
[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?)
This bug is awaiting verification that the linux-azure/5.4.0-1117.124 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure -- 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
[Kernel-packages] [Bug 2031022] Re: Fix boot test warning for log_check "CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0"
This bug is awaiting verification that the linux-azure/5.4.0-1117.124 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure -- 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/2031022 Title: Fix boot test warning for log_check "CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Bug description: SRU Justification [Impact] Gather Data Sampling, affecting Intel processors and assigned CVE-2022-40982 introduced this warning.The fix is on microcode, but part of the mitigation on the kernel side is to detect if the microcode update is not there and disable AVX in case it's supported. This needed some reshuffle during initialization so that turning off AVX was possible without it being too late, which also moved the FPU initialization. See commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.252=6e60443668978131a442df485db3deccb31d5651 This causes the following warning during boot: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0 Logs: 154609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.438234] [ cut here ] 154709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.439198] get of unsupported state 154809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.439206] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0 154909:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Modules linked in: 155009:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-158-lowlatency #175-Ubuntu 155109:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 155209:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RIP: 0010:get_xsave_addr+0x98/0xb0 155309:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Code: 7e ff ff ff 48 83 c4 08 5b 5d c3 80 3d ed d8 bc 01 00 75 ae 48 c7 c7 52 76 51 9a 89 75 f4 c6 05 da d8 bc 01 01 e8 1a c8 a7 00 <0f> 0b 8b 75 f4 eb 91 31 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 155409:02:40 INFO | Aug 10 09:01:05 akis systemd-udevd[3200]: enp58s0np0: Process '/usr/bin/killall -SIGHUP irqbalance' failed with exit code 1. 155509:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RSP: :9ac03e80 EFLAGS: 00010282 155609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RAX: RBX: 9ae47180 RCX: 00032109e11a 155709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RDX: 0018 RSI: 9bd8c620 RDI: 0246 155809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RBP: 9ac03e90 R08: 9bd8c620 R09: 74726f707075736e 155909:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] R10: 74726f707075736e R11: 6574617473206465 R12: 9ae47040 156009:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] R13: 0246 R14: 5a1c7469 R15: 5a1d7ee0 156109:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] FS: () GS:a0840040() knlGS: 156209:02:40 INFO | Aug 10 09:01:05 akis systemd[1]: Starting Load Kernel Module pstore_zone... 156309:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CS: 0010 DS: ES: CR0: 80050033 156409:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CR2: a146f000 CR3: 00802c80a001 CR4: 007200b0 156509:02:40 INFO | Aug 10 09:01:05 akis kernel: [
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This bug is awaiting verification that the linux-azure/5.4.0-1117.124 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+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 2033531] Re: Azure: net: mana: Fix MANA VF unload when hardware is unresponsive
This bug is awaiting verification that the linux-azure/5.4.0-1117.124 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-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/2033531 Title: Azure: net: mana: Fix MANA VF unload when hardware is unresponsive Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] MSFT has requested to backport commit a7dfeda6fdeccab4c7c3dce9a72c4262b9530c80 ('net: mana: Fix MANA VF unload when hardware is unresponsive'). When unloading the MANA driver, mana_dealloc_queues() waits for the MANA hardware to complete any inflight packets and set the pending send count to zero. But if the hardware has failed, mana_dealloc_queues() could wait forever. [Test Plan] Microsoft tested. Commit upstream since 6.5 [Regression Potential] The MANA driver may not shut down correctly. [Other Info] SF: #00367140 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2033531/+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 2035163] Re: Avoid address overwrite in kernel_connect
** Description changed: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 + + + Testing: + - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. + + + Regression potenial: + - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. + + More information at: + https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gcp source package in Mantic: New Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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 2035163] [NEW] Avoid address overwrite in kernel_connect
Public bug reported: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gcp source package in Mantic: New Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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
** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-hwe-6.2 (Ubuntu Jammy) Status: New => Invalid ** Changed in: mesa (Ubuntu Mantic) Status: New => Fix Released -- 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 Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-hwe-6.2 source package in Jammy: Invalid Status in mesa source package in Jammy: New Status in linux-hwe-6.2 source package in Lunar: Invalid Status in mesa source package in Lunar: New Status in linux-hwe-6.2 source package in Mantic: Invalid Status in mesa source package in Mantic: Fix Released 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
[Kernel-packages] [Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc won't boot
I am increasingly convinced that the "for waiting the udev" thing is unrelated the things that the mentioned patch set addresses, so please disregard that part, and draw the conclusion that the patches work as advertised. -- 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc won't boot Status in linux package in Ubuntu: In Progress Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' Timed out for waiting the udey queue being empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+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 2035147] 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/2035147 Title: amdgpu hangs Status in linux package in Ubuntu: Confirmed Bug description: With the new mantic kernel the kernel after a while gets into a state where amdgpu hangs when starting any game. My suspicion is that it might happen after waking up from suspend but I am not entirely sure about that yet. After rebooting It will work for a while until it doesn't. The exact symptom is that any game running in full screen mode will hang up and not update the display. It is clear that the game is running because audio works as intended. When opening the gnome window overview it does render correctly in the preview. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7+4 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 23:14:36 2023 InstallationDate: Installed on 2023-01-11 (243 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230815.git0e048b06-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-08-29 (13 days ago) dmi.bios.date: 05/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035147/+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 2035147] [NEW] amdgpu hangs
Public bug reported: With the new mantic kernel the kernel after a while gets into a state where amdgpu hangs when starting any game. My suspicion is that it might happen after waking up from suspend but I am not entirely sure about that yet. After rebooting It will work for a while until it doesn't. The exact symptom is that any game running in full screen mode will hang up and not update the display. It is clear that the game is running because audio works as intended. When opening the gnome window overview it does render correctly in the preview. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7+4 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 23:14:36 2023 InstallationDate: Installed on 2023-01-11 (243 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230815.git0e048b06-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-08-29 (13 days ago) dmi.bios.date: 05/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035147 Title: amdgpu hangs Status in linux package in Ubuntu: New Bug description: With the new mantic kernel the kernel after a while gets into a state where amdgpu hangs when starting any game. My suspicion is that it might happen after waking up from suspend but I am not entirely sure about that yet. After rebooting It will work for a while until it doesn't. The exact symptom is that any game running in full screen mode will hang up and not update the display. It is clear that the game is running because audio works as intended. When opening the gnome window overview it does render correctly in the preview. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7+4 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 23:14:36 2023 InstallationDate: Installed on 2023-01-11 (243 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230815.git0e048b06-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-08-29 (13 days ago) dmi.bios.date: 05/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 2034732] Re: The 50-kdump-tools.rules file needs update for latest kernel 6.6 feature
The 50-kdump-tools.rules file should look like this: # The kernel updates the crash elfcorehdr for CPU and memory changes SUBSYSTEM=="cpu", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end" SUBSYSTEM=="memory", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end" SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/usr/sbin/kdump-config try-reload" SUBSYSTEM=="memory", ACTION=="offline", PROGRAM="/usr/sbin/kdump-config try-reload" SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/usr/sbin/kdump-config try-reload" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/usr/sbin/kdump-config try-reload" SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/usr/sbin/kdump-config try-reload" LABEL="kdump_reload_end" where the first 3 lines and last 1 line are new/added. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2034732 Title: The 50-kdump-tools.rules file needs update for latest kernel 6.6 feature Status in kexec-tools package in Ubuntu: New Bug description: The following series has landed in mainline, and will be present in 6.6. "crash: Kernel handling of CPU and memory hot un/plug" https://lore.kernel.org/lkml/20230814214446.6659-1-eric.devol...@oracle.com/ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d68b4b6f307d155475cce541f2aee938032ed22e To take advantage of the performance benefits of that series, 50-kdump-tools.rules needs an update to optimize the handling of CPU and memory hotplug changes. It is safe to deploy these rule updates now, ahead of distros/kernels enabling the feature, since the crash_hotplug sysfs nodes would not be present and thus the newly introduced rules in 50-kdump-tools would act as a nop-op and fall thru for legacy behavior. But when distros/kernels enable the feature, then 50-kdump-tools rules is ready and can properly take advantage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/2034732/+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 2035135] [NEW] Oracle Cloud systems not getting Jammy kernel updates
Public bug reported: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! ** Affects: linux-meta-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2035135 Title: Oracle Cloud systems not getting Jammy kernel updates Status in linux-meta-oracle package in Ubuntu: New Bug description: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2035135/+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 2035133] [NEW] linux-libc-dev:i386 is not produced anymore
Public bug reported: [Impact] On Bionic, after i386 and other architectures were dropped from building, linux-libc-dev:i386 stopped being produced. That stills needs to be produced for userspace multi-arch support. Otherwise installing newer linux-libc-dev binaries will remove the i386 version of it, as they need to be the same version. [Test case] Install linux-libc-dev and linux-libc-dev:i386 prepared by the same source package. [Potential regression] Packages may fail to build or different config options may be enabled. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/2035133 Title: linux-libc-dev:i386 is not produced anymore Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: [Impact] On Bionic, after i386 and other architectures were dropped from building, linux-libc-dev:i386 stopped being produced. That stills needs to be produced for userspace multi-arch support. Otherwise installing newer linux-libc-dev binaries will remove the i386 version of it, as they need to be the same version. [Test case] Install linux-libc-dev and linux-libc-dev:i386 prepared by the same source package. [Potential regression] Packages may fail to build or different config options may be enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035133/+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 2035116] Re: allow io_uring to be disabled in runtime
** Description changed: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) + Actually also tried setting kernel.io_uring_disabled=2 and checking that + neither (privileged or unprivileged worked). + + Then testing setting it back to 0. + + Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and + that it worked for group 1000, then set it to 1001 and verified that it + didn't work anymore for group 1000. + + [Potential regression] Uses can be denied from using io_uring. -- 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/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
Why is this being requested? What specific certification blockers or customer deployments does this affect? We don't generally just pull large numbers of patches in like this without a business justification to backport them, unfortunately, the aim is to update the driver to resolve issues that are affecting folks in the field. If someone needs a new driver version the first suggestion is that they should be running the latest HWE kernel which is where those updates normally land. -- 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/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Incomplete Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks
[Kernel-packages] [Bug 2035128] [NEW] mlxbf-gige: Enable the OOB port in mlxbf_gige_open
Public bug reported: SRU Justification: [Impact] At the moment, the OOB port is enabled in the mlxbf_gige_probe function. If the mlxbf_gige_open is not executed, this could cause pause frames to increase in the case where there is high backgroud traffic. This results in clogging the BMC port as well. [Fix] * Move enabling the OOB port to mlxbf_gige_open. [Test Case] * Main test for this bug: Check that the BMC is always pingable while pushing a BFB Other tests: * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Do the reboot test and powercycle test and check the oob_net0 interface again * Push BFB multiple times and make sure the OOB is up and running [Regression Potential] Since are moving code that hasn't moved since BF2, it is important to make sure that there is no regression. Make sure that the OOB interface is always up and pingable after the reboot test, the powercycle test and after pushing a BFB. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035128 Title: mlxbf-gige: Enable the OOB port in mlxbf_gige_open Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] At the moment, the OOB port is enabled in the mlxbf_gige_probe function. If the mlxbf_gige_open is not executed, this could cause pause frames to increase in the case where there is high backgroud traffic. This results in clogging the BMC port as well. [Fix] * Move enabling the OOB port to mlxbf_gige_open. [Test Case] * Main test for this bug: Check that the BMC is always pingable while pushing a BFB Other tests: * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Do the reboot test and powercycle test and check the oob_net0 interface again * Push BFB multiple times and make sure the OOB is up and running [Regression Potential] Since are moving code that hasn't moved since BF2, it is important to make sure that there is no regression. Make sure that the OOB interface is always up and pingable after the reboot test, the powercycle test and after pushing a BFB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035128/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints
** Attachment removed: "uaccess clear_user() fix" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013088/+attachment/5660553/+files/s390-uaccess.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2035123] [NEW] scripts/pahole-flags.sh needs upstream fix
Public bug reported: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035123 Title: scripts/pahole-flags.sh needs upstream fix Status in linux-bluefield package in Ubuntu: New Bug description: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035123/+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 2034908] Re: Add support for 3 TDX subfeatures
** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2034908 Title: Add support for 3 TDX subfeatures Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Lunar: New Bug description: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view Testing: Intel has provided code review for the first 2 and has additionally tested the GetQuote feature. GCP has tested all three features and confirmed basic functionality and sanity. More testing will follow when the changes are available in -proposed and before feature release. Regression potential: Most of the code changes are to the following files: arch/x86/coco/tdx drivers/virt/coco/tdx-guest/tdx-guest.c mm/memblock.c mm/memory_hotplug.c mm/page_alloc.c mm/vmstat.c Most of it is new code which is inside #ifdef CONFIG_UNACCEPTED_MEMORY There is 1 tree-wide change "mm, treewide: redefine MAX_ORDER sanely" that affects many files and looks scary, but should be safe as it is basically a refactor. Generally speaking, the code changes here affect early memory initialization on x86 so can impact anything in that area, but realistically should only affect TDX instances (especially ones with >4GB as that is when the unaccepted-memory feature is activated). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2035116] Re: allow io_uring to be disabled in runtime
** Changed in: linux (Ubuntu Mantic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Triaged -- 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/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2035116] 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 2035116 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 Focal) 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/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2035116] Re: allow io_uring to be disabled in runtime
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2028740] Re: Fix AMD gpu hang when screen off/on
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/2028740 Title: Fix AMD gpu hang when screen off/on Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid 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.1 source package in Lunar: Invalid Bug description: [Impact] AMD GPU hang when screen off/on. error log: kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 [Fix] Keep a PHY active when detecting DP signal + DPMS active. [Test] Tested on 3 AMD platforms, GPU works fine. [Where problems could occur] Low risk, the fix is in v6.4-rc1. Generic Jammy kernel doesn't need this commit because of no support of AMD Phoenix GPU. SRU for Lunar/oem-6.1 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028740/+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 2029363] Re: Fix repeated errors of blacklisting during bootup
** Changed in: hwe-next Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) 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.1 in Ubuntu. https://bugs.launchpad.net/bugs/2029363 Title: Fix repeated errors of blacklisting during bootup Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] There are many repeated error of blacklisting during bootup on buggy firmware. log: kernel: blacklist: Problem blacklisting hash (-13) [Fix] Do not create duplicate entries or update existing entries, use a warning instead of spurious error messages. [Test] Tested on hardware with buggy firmware, error message will be shown as warning. No impact on normal hardware. [Where problems could occur] It may break UEFI boot. Because this is only error message, no function changed, SRU for oem-6.1 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029363/+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 2035116] [NEW] allow io_uring to be disabled in runtime
Public bug reported: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) [Potential regression] Uses can be denied from using io_uring. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
** Tags removed: verification-needed-jammy-linux-oem-6.1 verification-needed-lunar-linux ** Tags added: verification-done-jammy-linux-oem-6.1 verification-done-lunar-linux -- 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/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 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 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
I am not sure, because bug 2031537's lspci does not show `!!! Unknown header type 7f` -- 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/2034916 Title: NIC RTL8168 randomly disconnected from pci bus Status in linux-hwe-6.2 package in Ubuntu: New Bug description: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2034916/+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 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
oops, disregard that one, didn't land yet ** Tags removed: verification-needed-jammy-linux-oem-6.1 -- 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/2027816 Title: Interrupt storm on GPIO controller on AMD platforms 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 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: * v6.4: * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+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 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- 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/2027816 Title: Interrupt storm on GPIO controller on AMD platforms 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 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: * v6.4: * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+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 2030680] Re: AMD 6800h internal graphics: flickering white screen
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Fix Released -- 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/2030680 Title: AMD 6800h internal graphics: flickering white screen Status in Linux: 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: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: New 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: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: I am getting a flickering white screen occasionally. I have an Alienware M17 R5 AMD with a Ryzen 6800h CPU and an nvidia RTX 3070 Ti dedicated CPU. I'm getting a constant flickering white screen. According to a web search, this could be fixed in 6.2 with the kernel option amdgpu.sg_display=0. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1017.17 ProcVersionSignature: Ubuntu 6.1.0-1017.17-oem 6.1.34 Uname: Linux 6.1.0-1017-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 7 22:27:51 2023 InstallationDate: Installed on 2017-10-23 (2114 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: Upgraded to jammy on 2022-12-05 (245 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2030680/+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 2033025] Re: Fix numerous AER related issues
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- 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/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed 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 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: Fix Committed 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] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2032704] Re: Fix panel brightness issues on HP laptops
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- 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: Fix Committed 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 2032767] Re: Fix ACPI TAD on some Intel based systems
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- 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/2032767 Title: Fix ACPI TAD on some Intel based systems 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: Fix Committed 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] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+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 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- 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/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 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 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time
please verify 1022 ** Tags added: verification-needed-jammy -- 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/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time 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 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034491/+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 2034701] Re: unexpected system behaviour after kernel update
lspci -vvnn 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01) Subsystem: VMware Virtual Machine Chipset [15ad:1976] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08) Subsystem: VMware Virtual Machine Chipset [15ad:1976] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx 00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Subsystem: VMware PCI bridge [15ad:0790] 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Subsystem: VMware PCI Express Root Port [15ad:07a0] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x32, ASPM L0s, Exit Latency L0s <64ns ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (ok), Width x32 (ok) TrErr- Train- SlotClk- DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Slot #160, PowerLimit 240.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn+ PwrFlt- MRL- PresDet- CmdCplt- HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd- AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
uname Linux myhost 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+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 2034701] Re: unexpected system behaviour after kernel update
/proc/version_signature Ubuntu 5.15.0-83.92-generic 5.15.116 -- 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/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+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 2034701] Re: unexpected system behaviour after kernel update
dmesg [0.00] Linux version 5.15.0-83-generic (buildd@lcy02-amd64-027) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 (Ubuntu 5.15.0-83.92-generic 5.15.116) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=16488428-7c39-44f3-b82c-95b445a58fea ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] Disabled fast string operations [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009f3ff] usable [0.00] BIOS-e820: [mem 0x0009f400-0x0009] reserved [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbfed] usable [0.00] BIOS-e820: [mem 0xbfee-0xbfefefff] ACPI data [0.00] BIOS-e820: [mem 0xbfeff000-0xbfef] ACPI NVS [0.00] BIOS-e820: [mem 0xbff0-0xbfff] usable [0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec0] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xfffe-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00043fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 [0.00] vmware: hypercall mode: 0x02 [0.00] Hypervisor detected: VMware [0.00] vmware: TSC freq read from hypervisor : 2099.999 MHz [0.00] vmware: Host bus clock speed read from hypervisor : 6600 Hz [0.00] vmware: using clock offset of 6397541515 ns [0.16] tsc: Detected 2099.999 MHz processor [0.002306] e820: update [mem 0x-0x0fff] usable ==> reserved [0.002313] e820: remove [mem 0x000a-0x000f] usable [0.002324] last_pfn = 0x44 max_arch_pfn = 0x4 [0.002374] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.002397] total RAM covered: 31744M [0.002629] Found optimal setting for mtrr clean up [0.002631] gran_size: 64K chunk_size: 64K num_reg: 5 lose cover RAM: 0G [0.002709] e820: update [mem 0xc000-0x] usable ==> reserved [0.002720] last_pfn = 0xc max_arch_pfn = 0x4 [0.008571] found SMP MP-table at [mem 0x000f6a70-0x000f6a7f] [0.008609] Using GB pages for direct mapping [0.008902] RAMDISK: [mem 0x2aee3000-0x31768fff] [0.008911] ACPI: Early table checksum verification disabled [0.008915] ACPI: RSDP 0x000F6A00 24 (v02 PTLTD ) [0.008921] ACPI: XSDT 0xBFEEE8FB 5C (v01 INTEL 440BX 0604 VMW 01324272) [0.008929] ACPI: FACP 0xBFEFEE73 F4 (v04 INTEL 440BX 0604 PTL 000F4240) [0.008935] ACPI: DSDT 0xBFEEEBBD 0102B6 (v01 PTLTD Custom 0604 MSFT 0301) [0.008939] ACPI: FACS 0xBFEFFFC0 40 [0.008943] ACPI: FACS 0xBFEFFFC0 40 [0.008946] ACPI: BOOT 0xBFEEEB95 28 (v01 PTLTD $SBFTBL$ 0604 LTP 0001) [0.008950] ACPI: APIC 0xBFEEEB1B 7A (v01 PTLTD ? APIC 0604 LTP ) [0.008954] ACPI: MCFG 0xBFEEEADF 3C (v01 PTLTD $PCITBL$ 0604 LTP 0001) [0.008958] ACPI: SRAT 0xBFEEE9F7 E8 (v02 VMWARE MEMPLUG 0604 VMW 0001) [0.008965] ACPI: HPET 0xBFEEE9BF 38 (v01 VMWARE VMW HPET 0604 VMW 0001) [0.008970] ACPI: WAET 0xBFEEE997 28 (v01 VMWARE VMW WAET 0604 VMW 0001) [0.008973] ACPI: Reserving FACP table memory at [mem 0xbfefee73-0xbfefef66] [0.008975] ACPI: Reserving DSDT table memory at [mem 0xbfeeebbd-0xbfefee72] [0.008977] ACPI: Reserving FACS table memory at [mem 0xbfefffc0-0xbfef] [0.008978] ACPI: Reserving FACS table memory at [mem 0xbfefffc0-0xbfef] [0.008979] ACPI: Reserving BOOT table memory at [mem 0xbfeeeb95-0xbfeeebbc] [0.008980] ACPI: Reserving APIC table memory at [mem 0xbfeeeb1b-0xbfeeeb94] [0.008982] ACPI: Reserving MCFG table memory at [mem 0xbfeeeadf-0xbfeeeb1a] [0.008983] ACPI: Reserving SRAT table memory at [mem 0xbfeee9f7-0xbfeeeade] [0.008984] ACPI: Reserving HPET table memory at [mem 0xbfeee9bf-0xbfeee9f6] [0.008986] ACPI: Reserving WAET table memory at [mem 0xbfeee997-0xbfeee9be] [0.009144] SRAT: PXM 0 -> APIC 0x00 -> Node 0 [0.009148] SRAT: PXM 0 -> APIC 0x02 -> Node 0 [0.009149] SRAT: PXM 0 -> APIC 0x04 ->
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
ON ThinkPad X1 Carbon Gen 11(8086:a75d), the mipi works fine now on 22.04 with generic kernel or 6.1.0-oem kernel, tested in gst-launch-1.0, it works fine. I found it the gst-plugin-scanner crashed after install libcamhal0 , and I met this issue on X1 Carbon Gen 10(8086:465d) too. ** Attachment added: "_usr_lib_x86_64-linux-gnu_gstreamer1.0_gstreamer-1.0_gst-plugin-scanner.1002.crash" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5699882/+files/_usr_lib_x86_64-linux-gnu_gstreamer1.0_gstreamer-1.0_gst-plugin-scanner.1002.crash -- 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
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: New Status in linux source package in Bionic: Fix Released Status in linux-hwe-5.4 source package in Bionic: Confirmed Status in linux-hwe-6.2 source package in Bionic: New Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
Hi all, This bug seems to be present on kernel "6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy Logs: [lun sep 11 12:18:58 2023] BUG: kernel NULL pointer dereference, address: 002b [lun sep 11 12:18:58 2023] #PF: supervisor read access in kernel mode [lun sep 11 12:18:58 2023] #PF: error_code(0x) - not-present page [lun sep 11 12:18:58 2023] PGD 0 P4D 0 [lun sep 11 12:18:58 2023] Oops: [#1] PREEMPT SMP PTI [lun sep 11 12:18:58 2023] CPU: 6 PID: 118 Comm: kswapd0 Tainted: P OE 6.2.0-32-generic #32~22.04.1-Ubuntu [lun sep 11 12:18:58 2023] Hardware name: System manufacturer System Product Name/ROG STRIX Z370-E GAMING, BIOS 3005 09/30/2021 [lun sep 11 12:18:58 2023] RIP: 0010:down_read_trylock+0x16/0x80 [lun sep 11 12:18:58 2023] Code: 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 65 ff 05 5c 69 6b 50 48 b9 07 00 00 00 00 00 00 80 <48> 8b 07 48 85 c8 75 57 48 8d 90 00 01 00 00 f0 48 0f b1 17 75 ed [lun sep 11 12:18:58 2023] RSP: 0018:b6e3405539a8 EFLAGS: 00010282 [lun sep 11 12:18:58 2023] RAX: RBX: f2dbdbbc1080 RCX: 8007 [lun sep 11 12:18:58 2023] RDX: RSI: b6e340553a58 RDI: 002b [lun sep 11 12:18:58 2023] RBP: b6e3405539d8 R08: R09: [lun sep 11 12:18:58 2023] R10: R11: R12: 94f60ffade38 [lun sep 11 12:18:58 2023] R13: 94f60ffade39 R14: b6e340553a58 R15: 002b [lun sep 11 12:18:58 2023] FS: () GS:94fd16b8() knlGS: [lun sep 11 12:18:58 2023] CS: 0010 DS: ES: CR0: 80050033 [lun sep 11 12:18:58 2023] CR2: 002b CR3: 000330e10003 CR4: 003706e0 [lun sep 11 12:18:58 2023] DR0: DR1: DR2: [lun sep 11 12:18:58 2023] DR3: DR6: fffe0ff0 DR7: 0400 [lun sep 11 12:18:58 2023] Call Trace: [lun sep 11 12:18:58 2023] [lun sep 11 12:18:58 2023] ? show_regs+0x72/0x90 [lun sep 11 12:18:58 2023] ? __die+0x25/0x80 [lun sep 11 12:18:58 2023] ? page_fault_oops+0x79/0x190 [lun sep 11 12:18:58 2023] ? blk_mq_get_new_requests+0xf6/0x1a0 [lun sep 11 12:18:58 2023] ? do_user_addr_fault+0x30c/0x640 [lun sep 11 12:18:58 2023] ? exc_page_fault+0x81/0x1b0 [lun sep 11 12:18:58 2023] ? asm_exc_page_fault+0x27/0x30 [lun sep 11 12:18:58 2023] ? down_read_trylock+0x16/0x80 [lun sep 11 12:18:58 2023] ? folio_lock_anon_vma_read+0x76/0x190 [lun sep 11 12:18:58 2023] rmap_walk_anon+0x262/0x350 [lun sep 11 12:18:58 2023] folio_referenced+0x17d/0x240 [lun sep 11 12:18:58 2023] ? __pfx_folio_referenced_one+0x10/0x10 [lun sep 11 12:18:58 2023] ? __pfx_folio_lock_anon_vma_read+0x10/0x10 [lun sep 11 12:18:58 2023] shrink_folio_list+0x7ee/0xc20 [lun sep 11 12:18:58 2023] shrink_inactive_list+0x191/0x600 [lun sep 11 12:18:58 2023] ? shrink_active_list+0x2dd/0x470 [lun sep 11 12:18:58 2023] shrink_lruvec+0x2c4/0x400 [lun sep 11 12:18:58 2023] ? shrink_slab+0x112/0x120 [lun sep 11 12:18:58 2023] ? shrink_slab+0x112/0x120 [lun sep 11 12:18:58 2023] shrink_node_memcgs+0x187/0x1f0 [lun sep 11 12:18:58 2023] shrink_node+0xb9/0x330 [lun sep 11 12:18:58 2023] balance_pgdat+0x375/0x840 [lun sep 11 12:18:58 2023] kswapd+0x11a/0x1f0 [lun sep 11 12:18:58 2023] ? __pfx_kswapd+0x10/0x10 [lun sep 11 12:18:58 2023] kthread+0xeb/0x120 [lun sep 11 12:18:58 2023] ? __pfx_kthread+0x10/0x10 [lun sep 11 12:18:58 2023] ret_from_fork+0x29/0x50 [lun sep 11 12:18:58 2023] ** Also affects: linux-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-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: New Status in linux source package in Bionic: Fix Released Status in linux-hwe-5.4 source package in Bionic: Confirmed Status in linux-hwe-6.2 source package in Bionic: New Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm:
[Kernel-packages] [Bug 1025663] Re: DMIStringIndexOutOfRange on HP Proliant ML110 G5
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1025663 Title: DMIStringIndexOutOfRange on HP Proliant ML110 G5 Status in linux package in Ubuntu: Won't Fix Bug description: We encountered this error when running certification tests in a HP Proliant ML110 G5: FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x09 while accessing entry 'Base Board Information (Type 2)' @ 0x000dc082, field 'Asset Tag', offset 0x08 ADVICE: It may be worth checking against section 7.3 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards/smbios). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-4-generic 3.5.0-4.4 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jul 17 08:52 seq crw-rw---T 1 root audio 116, 33 Jul 17 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.3-0ubuntu4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Jul 17 09:25:00 2012 HibernationDevice: RESUME=UUID=c1530c5c-1763-45eb-b575-4504e0de61f6 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Alpha amd64 (20120717) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant ML110 G5 PciMultimedia: ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US LANGUAGE=en_US: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic root=UUID=90f6a1e1-da49-4ec1-bef7-139784b5a88a ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-4-generic N/A linux-backports-modules-3.5.0-4-generic N/A linux-firmware 1.84 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2007 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.name: A61TT2 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 17 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/08/2007:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnA61TT2:rvrNA:cvnHP:ct17:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025663/+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 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2029138 Title: cifs: fix mid leak during reconnection after timeout threshold Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] A regression in the Ubuntu 5.15 kernel has been causing problems for multiple customers on Azure. This bug has been fixed in the mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc [Test Plan] Microsoft tested [Regression Potential] Reconnections could fail. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+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 2024479] Re: kdump fails on big arm64 systems when offset is not specified
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: Fix Released Status in kexec-tools source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Released Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without
[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2020295 Title: Include the MAC address pass through function on RTL8153DD-CG 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 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed 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.1 source package in Mantic: Invalid Bug description: [Impact] When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it should show pass through MAC address set in BIOS. But the LAN MAC address pass through doesn't function on RTL8153DD-CG sku. [Fix] Commit in v6.3-rc1 fixes the issue. ec51fbd1b8a2 r8152: add USB device driver for config selection [Test] Verified by OEM. [Where problems could occur] It won't affect the old behavior if there is no preferred cfg is configured and will select the preferred one while probing. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020295/+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 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Invalid Bug description: [ Impact ] * Regression in the loop block driver in Jammy kernel between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable), due to a change in the default behavior (value) of kernel parameter `max_loop` (from 0 to 8) in commit: `loop: Fix the max_loop commandline argument treatment when it is set to 0` (comment #6). * Users of loop devices (major 7) with minor >= 8 now fail to `open()` a loop device created with `mknod()`. * This is a corner case, as most people use `losetup` with usual /dev/loopNUMBER (or `--find`) which are not affected as it uses a different code path. (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.) * Workaround: kernel parameter `max_loop=0`. [ Test Steps ] * Run the test cases (losetup and test-loop.c in comment #6): - max_loop not set (default) - max_loop=0 - max_loop=8 * Verify the default behavior (max_loop not set) is restored. * Verify the modified behavior (max_loop is set) is unchanged. [ Regression Potential ] * Regressions would be limited to the loop block driver, more specifically its default behavior (but it's that now) or specific usage of max_loop parameter (tested; looks OK). [ Other Info ] * Patch 1 [1] is not quite a fix, but adds CONFIG guards that Patch 2 [2] depends on. (Alternatively, a Patch 2 backport with that could be done, but Patch 1 seems trivial enough.) * The fix on Jammy is only Patch 2, with a trivial backport (that CONFIG option is not in Jammy/v5.15, only in v5.18). * The fix on Lunar is both patches; clean cherry-picks. * The fix on Mantic is both patches too, now in v6.5-rc3, which should be automatically incorporated as Mantic apparently will release with the 6.5 kernel [3] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a [3] https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release Original Description: --- losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[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?)
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+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 2026028] Re: usbrtl sometimes doesn't reload firmware
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2026028 Title: usbrtl sometimes doesn't reload firmware Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Committed Bug description: [Impact] The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load firmware which results in the BT adapter running potentially old firmware rather than the current version from /lib/firmware provided by the linux-firmware package. This will show in logs like so: Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922 Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp subver d922, hci rev dfc6, hci ver 000a Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware upload needed The driver reads subver from the adapter to determine chip type. But that value is overwritten by a firmware load. In the above case, a firmware was already loaded which returns subver d922 which the driver does not recognize and it therefore won't load new firmware. [Test Case] 1) Boot machine with USB adapter plugged in. 2) Verify firmware is loaded. 3) Reboot a couple of times and verify that firmware is reloaded every time. [Where Problems Could Occur] Limited to Realtek USB bluetooth adapters that use the btrtl driver. Issues could show up as Bluetooth connection/initialization problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+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 2028550] Re: Backport support to tolerate ZSTD compressed firmware files
This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2028550 Title: Backport support to tolerate ZSTD compressed firmware files Status in linux package in Ubuntu: In Progress Bug description: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one (see bug #1942260) * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal-hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028550/+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 2034938] Re: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2034938 Title: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 does not working ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 6.2.0-32-generic Date: Fri Sep 8 17:58:11 2023 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.157-0ubuntu5.23.04.1:/var/lib/dkms/nvidia/390.157/build/nvidia/nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2023-04-29 (131 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageVersion: 390.157-0ubuntu5.23.04.1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2034938/+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 2034938] Re: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2034938 Title: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 does not working ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 6.2.0-32-generic Date: Fri Sep 8 17:58:11 2023 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.157-0ubuntu5.23.04.1:/var/lib/dkms/nvidia/390.157/build/nvidia/nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2023-04-29 (131 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageVersion: 390.157-0ubuntu5.23.04.1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.157-0ubuntu5.23.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2034938/+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 2035019] Re: trackpad is not detected
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2035019 Title: trackpad is not detected Status in linux-signed package in Ubuntu: New Bug description: mouse trackpad not working after update to latest os. wifi also very moody ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-210-generic 4.4.0-210.242 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 10 15:41:08 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-yuanli-precise-amd64-20140320-1 InstallationDate: Installed on 2013-01-01 (3904 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20140320-07:21 SourcePackage: linux-signed UpgradeStatus: Upgraded to xenial on 2023-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2035019/+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 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: In Progress Bug description: [Impact] Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2 resulting in frequent transmit queue timeouts. Related to ASPM. See 'original description' below. [Test Case] Just regular usage for an extended period of time. No transmit queue timeouts with RTL8168h/8111h NICs. [Where Problems Could Occur] Modification are isolated to the r8169 driver so only machine where that driver is loaded are affected. Issues could show up as kernel crashes, stack traces, non-fnuctional wired network. [Original 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 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:
[Kernel-packages] [Bug 2032628] Re: Kernel 6.2.0-26 does not boot
The issue persists after updating to kernel 6.2.0-32. -- 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/2032628 Title: Kernel 6.2.0-26 does not boot Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.3 LTS auto updated from kernel 5.19.0-46-generic to 6.2.0-26-generic. The new kernel does not boot. It stops right after the following warnings: /dev/nvme0n1p7: clean etc. dell_smbios: Unable to run on non-Dell system usb 1-7: 3:3: cannot set freq 24000 to ep 0x82 The PC is a Dell Alienware Aurora R13. If I let it start in recovery mode and then resume boot, it works, but among other it does not recognize two screens. This "ubuntu-bug" was done after booting in this way. The old kernel boots fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 11:17:48 2023 InstallationDate: Installed on 2023-04-04 (139 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/+bug/2032628/+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 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
I have this error in dmesg after trying S3 sleep on an XPS 9700 ( which Dell utterly broke ): [ 161.974794] hid-sensor-hub 001F:8087:0AC2.0003: timeout waiting for response from ISHTP device For me it seems to only affect the touch screen, which in this case stops working after the S3 wake. The S3 wake does not work at all without power cabel, but that is a whole other story, or is it :) ? XPS 9500 does not wake at all by the way, it just hangs wether on power or not. I anyone needs me to investigate further, I have both machines at hand to test at the moment. -- 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/1807406 Title: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, Message after returning from suspension dmesg: [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response from ISHTP device Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 12:02:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 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.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19: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/linux/+bug/1807406/+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 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
** Description changed: + [Impact] + + Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2 + resulting in frequent transmit queue timeouts. Related to ASPM. See + 'original description' below. + + [Test Case] + + No transmit queue timeouts with RTL8168h/8111h NICs. + + [Where Problems Could Occur] + + Modification are isolated to the r8169 driver so only machine where that + driver is loaded are affected. Issues could show up as kernel crashes, + stack traces, non-fnuctional wired network. + + [Original 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 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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
The patch fixing the upstream linked issue is: radeonsi/vcn: fix the incorrect dt_size and it is in mesa main (which will be in 23.3), as well as 23.1.7, which is already in Ubuntu mantic. -- 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 Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa 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
[Kernel-packages] [Bug 2029332] Re: Reboot command powers off the system
That is not a very helpful comment. Can you please provide some more data that makes you believe the problem is not fixed? -- 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/2029332 Title: Reboot command powers off the system 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: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Issue: When a reboot (or init 6) command is issued the server shuts down instead. Expected behaviour: To reboot and NOT shutdown Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core count greater than 16 (like 24,28 or 32) Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15 When the CPU count is 1, issue is not observed. When core count is less than 24 (like 16) issue not observed. [Fix] Problem introduced in v5.18 with commit: 08f253ec3767 x86/cpu: Clear SME feature flag when not in use Fixes for the above:0 9b040453d444 x86/smp: Dont access non-existing CPUID leaf 1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust [Test Case] $ sudo reboot Server should reboot and not power off. [Where Problems Could Occur] The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+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 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
Maybe related: bug 2031537. -- 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/2034916 Title: NIC RTL8168 randomly disconnected from pci bus Status in linux-hwe-6.2 package in Ubuntu: New Bug description: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2034916/+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 2034701] Re: unexpected system behaviour after kernel update
It seems that Ubuntu 22.04 is affected in a critical way. Currently we had freezes only on Ubuntu22, but in Ubuntu 20.04 there are similiar loglines. After some hours of running the ubuntu 22.04 crashes and kernel/systemd are damaged. -- 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/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+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] cpuhotplug related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
ubuntu_ltp/cpuhotplug:cpuhotplug04 can be found failing with system crash on AWS c3.xlarge with 5.15.0-1046.51~20.04.1 as well. -- 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. 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 (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 [
[Kernel-packages] [Bug 2034908] Re: Add support for 3 TDX subfeatures
** Description changed: Support is requested for 3 TDX-specific features: - - Unaccepted memory, aka "lazy memory accept" - - TDX "Get Quote" - is needed for attestation - - Marking the TSC as reliable + - Unaccepted memory, aka "lazy memory accept" + - TDX "Get Quote" - is needed for attestation + - Marking the TSC as reliable + + More information at: + https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view - More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view + Testing: + Intel has provided code review for the first 2 and has additionally tested the GetQuote feature. + GCP has tested all three features and confirmed basic functionality and sanity. More testing will follow when the changes are available in -proposed and before feature release. + + + Regression potential: + Most of the code changes are to the following files: + + arch/x86/coco/tdx + drivers/virt/coco/tdx-guest/tdx-guest.c + mm/memblock.c + mm/memory_hotplug.c + mm/page_alloc.c + mm/vmstat.c + + + Most of it is new code which is inside #ifdef CONFIG_UNACCEPTED_MEMORY + + There is 1 tree-wide change "mm, treewide: redefine MAX_ORDER sanely" + that affects many files and looks scary, but should be safe as it is + basically a refactor. + + Generally speaking, the code changes here affect early memory + initialization on x86 so can impact anything in that area, but + realistically should only affect TDX instances (especially ones with + >4GB as that is when the unaccepted-memory feature is activated). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2034908 Title: Add support for 3 TDX subfeatures Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Lunar: New Bug description: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view Testing: Intel has provided code review for the first 2 and has additionally tested the GetQuote feature. GCP has tested all three features and confirmed basic functionality and sanity. More testing will follow when the changes are available in -proposed and before feature release. Regression potential: Most of the code changes are to the following files: arch/x86/coco/tdx drivers/virt/coco/tdx-guest/tdx-guest.c mm/memblock.c mm/memory_hotplug.c mm/page_alloc.c mm/vmstat.c Most of it is new code which is inside #ifdef CONFIG_UNACCEPTED_MEMORY There is 1 tree-wide change "mm, treewide: redefine MAX_ORDER sanely" that affects many files and looks scary, but should be safe as it is basically a refactor. Generally speaking, the code changes here affect early memory initialization on x86 so can impact anything in that area, but realistically should only affect TDX instances (especially ones with >4GB as that is when the unaccepted-memory feature is activated). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2015372] Re: Add support for intel EMR cpu
** Tags removed: verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy ** Tags added: verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-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/2015372 Title: Add support for intel EMR cpu Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. This support is a nice feature to have in Jammy because it is an LTS release and enabling extra hardware adds to its usability. Usually backporting new features to existing kernels it's not a common practice. But these commits were easy to backport. Most of them were clean cherry picks. Some of them were already picked up from upstream stable releases, and some required manual intervention because Jammy did not have some commits applied but the actual changes were very minimal. More information about each commit is addressed inline. [Commits] 1. 9c252ecf3036: "platform/x86: intel-uncore-freq: add Emerald Rapids support" Adjusted the path to uncore-frequency.c In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to uncore-frequency dir 2. 5a8a05f165fb18d37526062419774d9088c2a9b9 "perf/x86/intel/cstate: Add Emerald Rapids" Small context adjustment in intel_cstates_match array because of missing SPR, RPL and MDL cpu models introduced in 528c9f1daf20d 3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0 "perf/x86/rapl: Add support for Intel Emerald Rapids" Context adjustment due to missing - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL domain" - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N" - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake" - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake" 4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f clean cherry-pick 5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5 clean cherry-pick 6. 93cac4150727dae0ee89f501dd75413b88eedec0 clean cherry-pick 7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb clean cherry-pick 8. e4b2bc6616e21 clean cherry-pick [Testing] Kernel was built on cbd and boot tested on a VM. TODO ask for help from intel. [Regression potential] Very low, these are minimal new features, which actually reuse a lot of the existing cpu structures/functions. The following changes since commit 8feeaa9039a290b978e7855ab82955cd9348fc13 "platform/x86: intel-uncore-freq: add Emerald Rapids support" are available in the Git repository at: git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy lp2015372 for you to fetch changes up to commit 7d88565e6777082265b373733fd93eb3e0914e12 "EDAC/i10nm: Add Intel Emerald Rapids server support" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015372/+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 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
** Tags removed: verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-kinetic verification-needed-lunar ** Tags added: verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-kinetic 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/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+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 2015855] Re: Add split lock detection for EMR
This fix is not specific to azure/aws, and it was verified against generic kernel. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Tags removed: verification-needed-focal-linux-aws-5.15 ** Tags added: verification-done-focal-linux-aws-5.15 -- 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/2015855 Title: Add split lock detection for EMR Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 The remaining feature needed to fully support EMR is the split lock detection mechanism. So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is supported or not, but this is not architectural, meaning that this should be trusted only if it’s confirmed that a specific CPU model implements it. This lead to a mapping between a CPU model and whether it supports split lock detection by default (no need to check IA32_CORE_CAPABILITIES) or they may support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be checked. With more and more CPU models, this becomes hard to maintain. Moreover, the December 2022 edition of the Intel Instruction Set Extensions manual defined that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and retrospectively always has been) architectural. Documentation also mentions “All processors that enumerate support for MSR_IA32_CORE_CAPS and set MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.” Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8: “ x86/split_lock: Enumerate architectural split lock disable bit” from linux-next removes the need of adding a new CPU model in that mapping. This is needed to support split lock detection for the new EMR CPU and future models that don’t suffer architectural changes. [Testing] Kernel was built on cbd and boot tested on a VM. Intel was asked to install and test the new kernel from this ppa https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855 [Regression potential] Very low, it is a small refactor and in essence, it does the exact same thing for existing cpu models: 1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes the mechanism is supported. 2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES without the extra step of checking the map if the CPU supports this (which was always true) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015855/+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 2019131] Re: Add PPIN support for Intel EMR cpu
This fix is not specific to azure/aws, and it was verified against generic kernel. ** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-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/2019131 Title: Add PPIN support for Intel EMR cpu Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+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 2034701] Re: unexpected system behaviour after kernel update
I collected some more loglines, produced by unproductive member of a haproxy failoversystem with usually zero load. over the weekend there are affected several servers. I think this is serious. Sep 8 17:01:06 myhost kernel: [115882.039808] CIFS: Attempting to mount \\host123\folder Sep 8 17:01:06 myhost systemd[1]: mnt-win_share.mount: Deactivated successfully. Sep 8 17:01:06 myhost kernel: [115882.497413] BUG: kernel NULL pointer dereference, address: 0040 Sep 8 17:01:06 myhost kernel: [115882.497460] #PF: supervisor read access in kernel mode Sep 8 17:01:06 myhost kernel: [115882.497485] #PF: error_code(0x) - not-present page Sep 8 17:01:06 myhost kernel: [115882.497502] PGD 0 P4D 0 Sep 8 17:01:06 myhost kernel: [115882.497515] Oops: [#1] SMP PTI Sep 8 17:01:06 myhost kernel: [115882.497530] CPU: 1 PID: 1046703 Comm: kworker/1:2 Not tainted 5.15.0-83-generic #92-Ubuntu Sep 8 17:01:06 myhost kernel: [115882.497560] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Sep 8 17:01:06 myhost kernel: [115882.497598] Workqueue: cifsoplockd cifs_oplock_break [cifs] Sep 8 17:01:06 myhost kernel: [115882.497691] RIP: 0010:cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.497738] Code: 89 45 b8 c0 eb 02 83 e3 01 e8 aa f6 ff ff 84 db 75 34 49 8b 47 48 4c 89 e2 0f b7 4d b8 4d 89 f0 4c 89 ee 4c 89 ff 48 8b 40 48 <48> 8b 40 40 48 8b 80 28 02 00 00 ff d0 0f 1f 00 41 89 c4 f6 05 30 Sep 8 17:01:06 myhost kernel: [115882.497794] RSP: 0018:a74603d87e10 EFLAGS: 00010246 Sep 8 17:01:06 myhost kernel: [115882.497812] RAX: RBX: RCX: Sep 8 17:01:06 myhost kernel: [115882.497834] RDX: 000b RSI: 236fcc211deddb5a RDI: 94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.497856] RBP: a74603d87e70 R08: 9408a1cd6a40 R09: Sep 8 17:01:06 myhost kernel: [115882.497879] R10: 9408a2da3000 R11: ff00 R12: 000b Sep 8 17:01:06 myhost kernel: [115882.497902] R13: 236fcc211deddb5a R14: 9408a1cd6a40 R15: 94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.497925] FS: () GS:940bafc8() knlGS: Sep 8 17:01:06 myhost kernel: [115882.497951] CS: 0010 DS: ES: CR0: 80050033 Sep 8 17:01:06 myhost kernel: [115882.497971] CR2: 0040 CR3: 0001008dc005 CR4: 007706e0 Sep 8 17:01:06 myhost kernel: [115882.498018] PKRU: 5554 Sep 8 17:01:06 myhost kernel: [115882.498029] Call Trace: Sep 8 17:01:06 myhost kernel: [115882.498040] Sep 8 17:01:06 myhost kernel: [115882.498051] ? show_trace_log_lvl+0x1d6/0x2ea Sep 8 17:01:06 myhost kernel: [115882.498071] ? show_trace_log_lvl+0x1d6/0x2ea Sep 8 17:01:06 myhost kernel: [115882.498098] ? process_one_work+0x228/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.498662] ? show_regs.part.0+0x23/0x29 Sep 8 17:01:06 myhost kernel: [115882.499192] ? __die_body.cold+0x8/0xd Sep 8 17:01:06 myhost kernel: [115882.499703] ? __die+0x2b/0x37 Sep 8 17:01:06 myhost kernel: [115882.500219] ? page_fault_oops+0x13b/0x170 Sep 8 17:01:06 myhost kernel: [115882.500699] ? kfree+0x1f7/0x250 Sep 8 17:01:06 myhost kernel: [115882.501195] ? do_user_addr_fault+0x321/0x670 Sep 8 17:01:06 myhost kernel: [115882.501657] ? exc_page_fault+0x77/0x170 Sep 8 17:01:06 myhost kernel: [115882.502125] ? asm_exc_page_fault+0x27/0x30 Sep 8 17:01:06 myhost kernel: [115882.502964] ? cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.503767] process_one_work+0x228/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.504498] worker_thread+0x53/0x420 Sep 8 17:01:06 myhost kernel: [115882.505222] ? process_one_work+0x3d0/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.505959] kthread+0x127/0x150 Sep 8 17:01:06 myhost kernel: [115882.506719] ? set_kthread_struct+0x50/0x50 Sep 8 17:01:06 myhost kernel: [115882.507426] ret_from_fork+0x1f/0x30 Sep 8 17:01:06 myhost kernel: [115882.508112] Sep 8 17:01:06 myhost kernel: [115882.508760] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs tls intel_rapl_msr vmw_balloon intel_rapl_common isst_if_mbox_msr isst_if_common nfit rapl joydev input_leds serio_raw vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock vmw_vmci mac_hid binfmt_misc sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pstore_blk ramoops pstore_zone reed_solomon efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear vmwgfx ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd cryptd syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core ahci mptspi drm i2c_piix4 libahci mptscsih psmouse
[Kernel-packages] [Bug 2034074] Re: 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 insta
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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 Status in nvidia-graphics-drivers-470 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