[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
We have backported the following two patches in Jammy and waiting for review:
18164f66e6c5 x86/fpu: Allow caller to constrain xfeatures when copying
to uabi buffer
8647c52e9504 KVM: x86: Constrain guest-supported xfeatures only at
KVM_GET_XSAVE{2}
The fix will also apply to Focal-HWE kernel.
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => 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/2032164
Title:
A general-proteciton exception during guest migration to unsupported
PKRU machine
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
When a host that supports PKRU initiates a guest that lacks PKRU support, the
flag is enabled on the guest's fpstate.
This information is then passed to userspace through the vcpu ioctl
KVM_GET_XSAVE.
However, a problem arises when the user opts to migrate the mentioned guest
to another machine that does not support PKRU.
In this scenario, the new host attempts to restore the guest's fpu registers.
Nevertheless, due to the absence of PKRU support on the new host, a
general-protection exception takes place, leading to a guest crash.
[Fix]
The problem is resolved by the following upstream commit:
18164f66e6c5 x86/fpu: Allow caller to constrain xfeatures when copying to
uabi buffer
8647c52e9504 KVM: x86: Constrain guest-supported xfeatures only at
KVM_GET_XSAVE{2}
[Test Plan]
Several scenarios need to be conducted to confirm the migration outcome.
Patched kernel with PKRU -> kernel with PKRU
Patched kernel with PKRU -> kernel without PKRU
Patched kernel without PKRU -> kernel with PKRU
Patched kernel without PKRU -> kernel without PKRU
Kernel with PKRU -> patched kernel with PKRU
Kernel with PKRU -> patched kernel without PKRU
Kernel without PKRU -> patched kernel with PKRU
Kernel without PKRU -> patched kernel without PKRU
Patched kernel with PKRU -> patched kernel without PKRU
Each scenarios shall succeed except "Kernel with PKRU -> patched kernel
without PKRU" one.
Addressing this case poses challenges because the most plausible solution is
to clamp the FPU features at the destination during migration.
However, upstream does not support this approach due to concerns about
silently dropping features requested by userspace.
This could potentially lead to other issues and violate KVM's ABI.
[Where problems could occur]
The introduced commits will impact the guest migration process,
potentially leading to failures and preventing the guest from operating
successfully on the migration destination.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+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 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
** Description changed:
[Impact]
When a host that supports PKRU initiates a guest that lacks PKRU support, the
flag is enabled on the guest's fpstate.
This information is then passed to userspace through the vcpu ioctl
KVM_GET_XSAVE.
However, a problem arises when the user opts to migrate the mentioned guest
to another machine that does not support PKRU.
In this scenario, the new host attempts to restore the guest's fpu registers.
Nevertheless, due to the absence of PKRU support on the new host, a
general-protection exception takes place, leading to a guest crash.
[Fix]
The problem is resolved by the following upstream commit:
- ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0
-
- Additionally, a subsequent fix tackles the migration problem stemming from
the earlier commit:
- a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES
+ 18164f66e6c5 x86/fpu: Allow caller to constrain xfeatures when copying to
uabi buffer
+ 8647c52e9504 KVM: x86: Constrain guest-supported xfeatures only at
KVM_GET_XSAVE{2}
[Test Plan]
- 1. Set up two machines: one with PKRU support and the other without.
- 2. Initiate a guest that lacks PKRU support on the machine with PKRU support.
- 3. Utilize libvirt to migrate the aforementioned guest to a different machine
that lacks PKRU support.
- 4. The error emerges on the destination machine:
- KVM: entry failed, hardware error 0x8021
+ Several scenarios need to be conducted to confirm the migration outcome.
+ Patched kernel with PKRU -> kernel with PKRU
+ Patched kernel with PKRU -> kernel without PKRU
+ Patched kernel without PKRU -> kernel with PKRU
+ Patched kernel without PKRU -> kernel without PKRU
+ Kernel with PKRU -> patched kernel with PKRU
+ Kernel with PKRU -> patched kernel without PKRU
+ Kernel without PKRU -> patched kernel with PKRU
+ Kernel without PKRU -> patched kernel without PKRU
+ Patched kernel with PKRU -> patched kernel without PKRU
- If you're running a guest on an Intel machine without unrestricted mode
- support, the failure can be most likely due to the guest entering an invalid
- state for Intel VT. For example, the guest maybe running in big real mode
- which is not supported on less recent Intel processors.
-
- EAX=86cf7970 EBX= ECX=0001 EDX=005b0036
- ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18
- EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
- ES = 9300
- CS =f000 9b00
- SS = 9300
- DS = 9300
- FS = 9300
- GS = 9300
- LDT= 8200
- TR = 8b00
- GDT=
- IDT=
- CR0=6010 CR2= CR3= CR4=
- DR0= DR1= DR2=
DR3=
- DR6=0ff0 DR7=0400
- EFER=
- Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from
pid 4134 (/usr/sbin/libvirtd)
- 2023-07-09 03:03:15.312+: shutting down, reason=destroyed
+ Each scenarios shall succeed except "Kernel with PKRU -> patched kernel
without PKRU" one.
+ Addressing this case poses challenges because the most plausible solution is
to clamp the FPU features at the destination during migration.
+ However, upstream does not support this approach due to concerns about
silently dropping features requested by userspace.
+ This could potentially lead to other issues and violate KVM's ABI.
[Where problems could occur]
The introduced commits will impact the guest migration process,
potentially leading to failures and preventing the guest from operating
successfully on the migration destination.
--
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/2032164
Title:
A general-proteciton exception during guest migration to unsupported
PKRU machine
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Triaged
Bug description:
[Impact]
When a host that supports PKRU initiates a guest that lacks PKRU support, the
flag is enabled on the guest's fpstate.
This information is then passed to userspace through the vcpu ioctl
KVM_GET_XSAVE.
However, a problem arises when the user opts to migrate the mentioned guest
to another machine that does not support PKRU.
In this scenario, the new host attempts to restore the guest's fpu registers.
Nevertheless, due to the absence of PKRU support on the new host, a
general-protection exception takes place,
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.15.0-1055.63)
All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.15.0-1055.63) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049945] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/2049945 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After installing the kernel update to version 6.5, the screen resolution was disrupted. When I try to switch to the open nouveau driver, an error occurs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 19 21:49:11 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-19 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 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/2049945/+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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
Duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038777
--
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/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2055082] Re: IB peer memory feature regressed in 6.5
= Verification = $ cat /proc/version Linux version 6.5.0-27-generic (buildd@lcy02-amd64-059) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41) #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 ubuntu@ubuntu:~/autotest-client-tests/ubuntu_performance_gpudirect_rdma/nvidia-peermem-test$ ./nvidia-peermem-test.sh -m peermem Repository: 'Types: deb URIs: https://ppa.launchpadcontent.net/canonical-nvidia/perftest+cuda/ubuntu/ Suites: mantic Components: main ' Description: Used internal for kernel regression testing More info: https://launchpad.net/~canonical-nvidia/+archive/ubuntu/perftest+cuda Adding repository. Found existing deb entry in /etc/apt/sources.list.d/canonical-nvidia-ubuntu-perftest_cuda-mantic.sources Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu mantic-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:5 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease Hit:6 https://ppa.launchpadcontent.net/canonical-nvidia/perftest+cuda/ubuntu mantic InRelease Hit:7 https://ppa.launchpadcontent.net/dannf/dannf/ubuntu mantic InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done perftest is already the newest version (24.01.0+0.38-1+perftest+cuda.1~ubuntu23.10.1). 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. Reading package lists... Done Building dependency tree... Done Reading state information... Done opensm is already the newest version (3.3.23-2). 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. --use_cuda= Use CUDA specific device for GPUDirect RDMA testing Perftest doesn't supports CUDA tests with inline messages: inline size set to 0 * Waiting for client to connect... * Perftest doesn't supports CUDA tests with inline messages: inline size set to 0 initializing CUDA initializing CUDA Listing all CUDA devices in system: CUDA device 0: PCIe address is 07:00 CUDA device 1: PCIe address is 0F:00 CUDA device 2: PCIe address is 47:00 CUDA device 3: PCIe address is 4E:00 CUDA device 4: PCIe address is 87:00 CUDA device 5: PCIe address is 90:00 CUDA device 6: PCIe address is B7:00 CUDA device 7: PCIe address is BD:00 Picking device No. 1 [pid = 15582, dev = 1] device name = [NVIDIA A100-SXM4-40GB] creating CUDA Ctx Listing all CUDA devices in system: CUDA device 0: PCIe address is 07:00 CUDA device 1: PCIe address is 0F:00 CUDA device 2: PCIe address is 47:00 CUDA device 3: PCIe address is 4E:00 CUDA device 4: PCIe address is 87:00 CUDA device 5: PCIe address is 90:00 CUDA device 6: PCIe address is B7:00 CUDA device 7: PCIe address is BD:00 Picking device No. 0 [pid = 15576, dev = 0] device name = [NVIDIA A100-SXM4-40GB] creating CUDA Ctx making it the current CUDA Ctx cuMemAlloc() of a 16777216 bytes GPU buffer allocated GPU buffer address at 7c014600 pointer=0x7c014600 --- RDMA_Write BW Test Dual-port : OFF Device : mlx5_6 Number of qps : 1Transport type : IB Connection type : RC Using SRQ : OFF PCIe relax order: ON making it the current CUDA Ctx cuMemAlloc() of a 16777216 bytes GPU buffer allocated GPU buffer address at 7a08b400 pointer=0x7a08b400 --- RDMA_Write BW Test Dual-port : OFF Device : mlx5_2 Number of qps : 1Transport type : IB Connection type : RC Using SRQ : OFF PCIe relax order: ON ibv_wr* API : ON TX depth: 128 CQ Moderation : 100 Mtu : 4096[B] Link type : IB Max inline data : 0[B] rdma_cm QPs : OFF Data ex. method : Ethernet --- ibv_wr* API : ON CQ Moderation : 100 Mtu : 4096[B] Link type : IB Max inline data : 0[B] rdma_cm QPs : OFF Data ex. method : Ethernet --- local address: LID 0x01 QPN 0x0029 PSN 0x6763b2 RKey 0x180eef VAddr 0x007a08b480 local address: LID 0x02 QPN 0x36ef PSN 0x149b7b RKey 0x180efd VAddr 0x007c014680 remote address: LID 0x02 QPN 0x36ef PSN 0x149b7b RKey 0x180efd VAddr 0x007c014680 --- #bytes #iterationsBW peak[MB/sec]BW average[MB/sec] MsgRate[Mpps] remote address: LID 0x01 QPN 0x0029 PSN 0x6763b2 RKey 0x180eef VAddr 0x007a08b480
[Kernel-packages] [Bug 2058029] Re: Display crashes on latest kernels
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: 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/2058029 Title: Display crashes on latest kernels Status in linux package in Ubuntu: New Bug description: My display crashes and nothing is displayed when I login to latest kernels. Not sure which kernel version started this issue. I can confirm that kernel version 5.15.0-76 works. System details given below. This is linux mint xfce desktop. - Type: Laptop System: Dell product: Inspiron 3180 v: 1.2.0 - Graphics: Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] vendor: Dell driver: amdgpu v: kernel bus-ID: 00:01.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.1:3 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1366x768~60Hz OpenGL: renderer: STONEY (stoney LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes -- mathew@mathew-Inspiron-3180:~$ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: AuthenticAMD Model name:AMD A6-9220e RADEON R4, 5 COMPUTE CORES 2C+3G CPU family: 21 Model: 112 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping:0 Frequency boost: enabled CPU max MHz: 1600. CPU min MHz: 1200. BogoMIPS:3193.98 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcn t aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_ msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_ save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov Virtualization features: Virtualization:AMD-V Caches (sum of all): L1d: 64 KiB (2 instances) L1i: 128 KiB (2 instances) L2:2 MiB (2 instances) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0,1 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Mitigation; untrained return thunk; SMT disabled Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected Srbds: Not affected Tsx async abort: Not affected -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058029/+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 2058029] [NEW] Display crashes on latest kernels
You have been subscribed to a public bug: My display crashes and nothing is displayed when I login to latest kernels. Not sure which kernel version started this issue. I can confirm that kernel version 5.15.0-76 works. System details given below. This is linux mint xfce desktop. - Type: Laptop System: Dell product: Inspiron 3180 v: 1.2.0 - Graphics: Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] vendor: Dell driver: amdgpu v: kernel bus-ID: 00:01.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.1:3 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1366x768~60Hz OpenGL: renderer: STONEY (stoney LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes -- mathew@mathew-Inspiron-3180:~$ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: AuthenticAMD Model name:AMD A6-9220e RADEON R4, 5 COMPUTE CORES 2C+3G CPU family: 21 Model: 112 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping:0 Frequency boost: enabled CPU max MHz: 1600. CPU min MHz: 1200. BogoMIPS:3193.98 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcn t aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_ msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_ save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov Virtualization features: Virtualization:AMD-V Caches (sum of all): L1d: 64 KiB (2 instances) L1i: 128 KiB (2 instances) L2:2 MiB (2 instances) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0,1 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Mitigation; untrained return thunk; SMT disabled Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected Srbds: Not affected Tsx async abort: Not affected -- ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Display crashes on latest kernels https://bugs.launchpad.net/bugs/2058029 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
** No longer affects: gcc-14 (Ubuntu) ** No longer affects: gcc-14 (Ubuntu Noble) ** Changed in: gcc-8 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: New Status in gcc-11 package in Ubuntu: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: New Status in llvm-toolchain-16 package in Ubuntu: New Status in gcc-10 source package in Noble: New Status in gcc-11 source package in Noble: New Status in gcc-12 source package in Noble: New Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: New Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: New Status in llvm-toolchain-16 source package in Noble: New Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
[Kernel-packages] [Bug 1942133] Re: Nvidia driver packages prevent suspend due to leftover Systemd units
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1942133 Title: Nvidia driver packages prevent suspend due to leftover Systemd units Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: When the nvidia driver packages are uninstalled, they leave some symlinks that prevent suspend. I whink that, when attempting to suspend, the error is logged as this (edited): ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: systemd-logind.service: Failed with result 'exit-code'. systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 7. systemd[1]: Stopped Login Service. systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. systemd[1]: Starting Login Service... I've deleted the problematic symlinks while trying to solving the problem, however, they should be these: /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service I've briefly checked before removing them; at least a couple of them were masked, but they were still causing the problem. I don't see any reason why they should hang around the systemd configuration once the packages are purged. Additionally, this is a problem that is not easy to diagnose. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-470 (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: MATE Date: Mon Aug 30 21:10:52 2021 LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 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-470/+bug/1942133/+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 2055818] Re: Intermittent UI freezes since LTS HWE linux 6.5.0-18
Additional info and observations: - Sometimes there is also flickering in videos (for example zoom calls), without freezing - The flickering and freezes seem to be less (but not entirely removed!) when using a lower refresh rate - While I am using the mouse, no flickering will occur, as soon as I stop moving, it will sometimes flicker - freezing seems to be able to happen while moving the mouse - The used screen is a 144 Hz screen with support for AMD FreeSync, including the AMD Radeon RX 6600 XT GPU in the system. The screen is also connected with Displayport as supposed to be for FreeSync. In a dual-booted Windows, FreeSync is automatically activated and seems to work, and there are no freezes. - I am not sure how to check if FreeSync is enabled/used in Ubuntu. -- 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/2055818 Title: Intermittent UI freezes since LTS HWE linux 6.5.0-18 Status in linux package in Ubuntu: New Bug description: When running the HWE kernel linux-6.5.0-18 and newer in Ubuntu 22.04.4 LTS ( 6.5.0-18.18~22.04.1 ), I get intermittent freezes of about 1-5 seconds of the whole UI (even the mouse pointer stops moving). Sound continues to work. There is absolutely nothing logged in the kernel or any other system logs. I downgraded the kernel in a current up-to-date Ubuntu 22.04.4, and it's running perfectly fine with linux-image-6.5.0-17-generic ( 6.5.0-17.17~22.04.1 ). As intuition I suspect amdgpu or its interaction with firmware, since there is nothing logged in the kernel and its a graphical issue. I couldn't find the patch log of the ubuntu kernel, but vanilla 6.5.17 to 6.5.18 has some amdgpu patches which I guess might be involved, if ubuntu 6.5.0-17 to 6.5.0-18 has anything to do with those vanilla kernel versions. I am attaching the two files (version.log and lspci-vnvn.log called no-freezes_version.log and no-freezes_lspci-vnvn.log) when no freezes happen (kernel 6.5.0-17) and lspci-vnvn.log and version.log when they happen. The generic non-hwe kernel 5.15 is no option - that one freezes the entire system as soon as the screen goes to power-saving mode, see my previous (confirmed) bug: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1987413 1) > lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 2) linux-generic-hwe-22.04: Installed: 6.5.0.21.21~22.04.11 3) No freezes 4) Intermittent UI freezes of 1-5 seconds including mouse pointer when starting multimedia applications, looking at images, etc. But no audio freezes or anything. Nothing logged in system or kernel logs when it happens. The freeze typically happens (but might not be always like that), for instance when starting a new youtube video in firefox or chrome, but subsequent ones work fine for a while. However, it might also happen when looking at a newly received image in any messenger app, it is not exclusive to firefox, or youtube, or videos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055818/+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 1987413] Re: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT
Sorry I overlooked that last message. I actually had a working system from around 6.2.0 to 6.5.0-17. It seems around 6.5.0-18 a new problem was introduced that now causes intermittent freezes. See the new bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055818 -- 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/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 2055818] Re: Intermittent UI freezes since LTS HWE linux 6.5.0-18
** Description changed: When running the HWE kernel linux-6.5.0-18 and newer in Ubuntu 22.04.4 LTS ( 6.5.0-18.18~22.04.1 ), I get intermittent freezes of about 1-5 seconds of the whole UI (even the mouse pointer stops moving). Sound continues to work. There is absolutely nothing logged in the kernel or any other system logs. I downgraded the kernel in a current up-to-date Ubuntu 22.04.4, and it's running perfectly fine with linux-image-6.5.0-17-generic ( 6.5.0-17.17~22.04.1 ). As intuition I suspect amdgpu or its interaction with firmware, since there is nothing logged in the kernel and its a graphical issue. I couldn't find the patch log of the ubuntu kernel, but vanilla 6.5.17 to 6.5.18 has some amdgpu patches which I guess might be involved, if ubuntu 6.5.0-17 to 6.5.0-18 has anything to do with those vanilla kernel versions. I am attaching the two files (version.log and lspci-vnvn.log called no- freezes_version.log and no-freezes_lspci-vnvn.log) when no freezes - happen now (kernel 6.5.0-17). After a reboot I will attach the ones when - freezes happen (rebooted with current HWE LTS kernel), + happen (kernel 6.5.0-17) and lspci-vnvn.log and version.log when they + happen. + + The generic non-hwe kernel 5.15 is no option - that one freezes the + entire system as soon as the screen goes to power-saving mode, see my + previous (confirmed) bug: + https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1987413 1) > lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 2) linux-generic-hwe-22.04: Installed: 6.5.0.21.21~22.04.11 3) No freezes 4) Intermittent UI freezes of 1-5 seconds including mouse pointer when starting multimedia applications, looking at images, etc. But no audio freezes or anything. Nothing logged in system or kernel logs when it happens. The freeze typically happens (but might not be always like that), for instance when starting a new youtube video in firefox or chrome, but subsequent ones work fine for a while. However, it might also happen when looking at a newly received image in any messenger app, it is not exclusive to firefox, or youtube, or videos. -- 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/2055818 Title: Intermittent UI freezes since LTS HWE linux 6.5.0-18 Status in linux package in Ubuntu: New Bug description: When running the HWE kernel linux-6.5.0-18 and newer in Ubuntu 22.04.4 LTS ( 6.5.0-18.18~22.04.1 ), I get intermittent freezes of about 1-5 seconds of the whole UI (even the mouse pointer stops moving). Sound continues to work. There is absolutely nothing logged in the kernel or any other system logs. I downgraded the kernel in a current up-to-date Ubuntu 22.04.4, and it's running perfectly fine with linux-image-6.5.0-17-generic ( 6.5.0-17.17~22.04.1 ). As intuition I suspect amdgpu or its interaction with firmware, since there is nothing logged in the kernel and its a graphical issue. I couldn't find the patch log of the ubuntu kernel, but vanilla 6.5.17 to 6.5.18 has some amdgpu patches which I guess might be involved, if ubuntu 6.5.0-17 to 6.5.0-18 has anything to do with those vanilla kernel versions. I am attaching the two files (version.log and lspci-vnvn.log called no-freezes_version.log and no-freezes_lspci-vnvn.log) when no freezes happen (kernel 6.5.0-17) and lspci-vnvn.log and version.log when they happen. The generic non-hwe kernel 5.15 is no option - that one freezes the entire system as soon as the screen goes to power-saving mode, see my previous (confirmed) bug: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1987413 1) > lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 2) linux-generic-hwe-22.04: Installed: 6.5.0.21.21~22.04.11 3) No freezes 4) Intermittent UI freezes of 1-5 seconds including mouse pointer when starting multimedia applications, looking at images, etc. But no audio freezes or anything. Nothing logged in system or kernel logs when it happens. The freeze typically happens (but might not be always like that), for instance when starting a new youtube video in firefox or chrome, but subsequent ones work fine for a while. However, it might also happen when looking at a newly received image in any messenger app, it is not exclusive to firefox, or youtube, or videos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055818/+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 2048768] Re: Autopkgtest failures on amd64
** Changed in: gcc-13 (Ubuntu Noble) Status: New => Fix Committed -- 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/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: New Status in gcc-11 package in Ubuntu: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-14 package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: New Status in llvm-toolchain-16 package in Ubuntu: New Status in gcc-10 source package in Noble: New Status in gcc-11 source package in Noble: New Status in gcc-12 source package in Noble: New Status in gcc-13 source package in Noble: Fix Committed Status in gcc-14 source package in Noble: New Status in gcc-8 source package in Noble: New Status in gcc-9 source package in Noble: New Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: New Status in llvm-toolchain-16 source package in Noble: New Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Trying to upload the latest file. It's 1.3 G
Uh oh!
Something has gone wrong. We're sorry!
If we are in the middle of an update, Launchpad will be back in a couple
of minutes. Otherwise, we are working to fix the unexpected problems.
Check @launchpadstatus on Twitter or @launchpadstatus@ubuntu.social on
Mastodon for updates.
If the problem persists, let us know in the #launchpad IRC channel on
libera.chat.
Technically, the load balancer took too long to connect to an
application server.
Reload this page or try again in a few minutes
No one on Launchpad chat responds to me.
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2058052] [NEW] Enable Intel IDPF support on ARM64
Public bug reported: [Impact] * Request from Google to enable Intel IDPF driver support on ARM64 [Fix] * Mantic - * Jammy - [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00381197 ** Affects: linux-gcp (Ubuntu) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gke (Ubuntu) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gcp (Ubuntu Jammy) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gke (Ubuntu Jammy) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gcp (Ubuntu Mantic) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gke (Ubuntu Mantic) ** Changed in: linux-gke (Ubuntu) Status: New => In Progress ** Changed in: linux-gke (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/2058052 Title: Enable Intel IDPF support on ARM64 Status in linux-gcp package in Ubuntu: In Progress Status in linux-gke package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: In Progress Status in linux-gke source package in Jammy: In Progress Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Request from Google to enable Intel IDPF driver support on ARM64 [Fix] * Mantic - * Jammy - [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00381197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2058052/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1018.19 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-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] No modems were found sometimtes after reboot/poweroff Got below messages when it fails [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 [Fix] Fibocom provides a fix for this issue which is included in linux-next now https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ 2dac6381c3da net: wwan: t7xx: Add fastboot WWAN port d27553c14f06 net: wwan: t7xx: Infrastructure for early port configuration 409c38d4f156 net: wwan: t7xx: Add sysfs attribute for device state machine e3caf184107a wwan: core: Add WWAN fastboot port type [Test Case] 1. Boot to OS. 2. Insert sim card to the system. 3. Check the gnome-settings with WWAN settings or check with command mmcli -L 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists and works well [Where problems could occur] Hard to tell, but ODM and us did some tests and confirmed the WWAN doesn't keep working during 1900 reboot stress test. = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware
[Kernel-packages] [Bug 2054773] Re: Fix AMD brightness issue on AUO panel
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1018.19 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-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054773 Title: Fix AMD brightness issue on AUO panel Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When change brightness quickly on gnome menu, AUO panel will be stuck in previous brightness. [Fix] The TCON is random hung by PSR-SU. Force enable ffu mode on PSR-SU panel. [Test] Tested on hardware, the brightness is changed as expected. [Where problems could occur] It may break AMD display. The commit is already in v6.8-rc5, the platform is not fully supported in Jammy 5.15, So SRU oem-6.5 and mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054773/+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 2055866] Re: Simplify kcontrol naming on Intel MTL platforms
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1018.19 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-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055866 Title: Simplify kcontrol naming on Intel MTL platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. We may need more MTL machines to make sure the behavior is the aligned. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055866/+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 2056418] Re: Fix headphone mic detection issue on ALC897
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1018.19 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-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+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 2057785] Re: Mute/mic LEDs no function on some HP EliteBook
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1018.19 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-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057785 Title: Mute/mic LEDs no function on some HP EliteBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2057785/+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 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1018.19 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-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
** Attachment added: "Kernel panic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5756269/+files/20240315_090551.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2058047] [NEW] Versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing the Intel Ethernet controller (4) I219-LM [8086:15d7] (rev 21)
Public bug reported: The system hangs with Linux 5.15.0-100 and 6.5.0-25 upon accessing this Ethernet controller: $ lspci -nn ... 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-LM [8086:15d7] (rev 21) Commands that deal with the network hang forever, e.g. "ip link". The machine must be hard-rebooted (magic sysrq) because systemd also hangs during reboot. Previous versions work perfectly fine (5.15.0-97 and 6.5.0-21). The issue is specific to the integrated network controller, because it goes away when the Ethernet controller is disabled in the BIOS. Attached is an extract of the kernel logs under the problematic kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-97-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yl243478 3612 F pulseaudio CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckMismatches: ./boot.catalog CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 15 16:48:19 2024 InstallationDate: Installed on 2022-11-10 (491 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0c45:6717 Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-97-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-97-generic N/A linux-backports-modules-5.15.0-97-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2023 dmi.bios.release: 1.36 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.36.0 dmi.board.name: 0YM3X5 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.36.0:bd12/13/2023:br1.36:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0YM3X5:rvrA01:cvnDellInc.:ct10:cvr:sku081C: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Attachment added: "Kernel logs under the problematic kernel" https://bugs.launchpad.net/bugs/2058047/+attachment/5756248/+files/2024-03-13_network_bug.txt -- 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/2058047 Title: Versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing the Intel Ethernet controller (4) I219-LM [8086:15d7] (rev 21) Status in linux package in Ubuntu: New Bug description: The system hangs with Linux 5.15.0-100 and 6.5.0-25 upon accessing this Ethernet controller: $ lspci -nn ... 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-LM [8086:15d7] (rev 21) Commands that deal with the network hang forever, e.g. "ip link". The machine must be hard-rebooted (magic sysrq) because systemd also hangs during reboot. Previous versions work perfectly fine (5.15.0-97 and 6.5.0-21). The issue is specific to the integrated network controller, because it goes away when the Ethernet controller is disabled in the BIOS. Attached is an extract of the kernel logs under the problematic kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-97-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yl243478 3612
[Kernel-packages] [Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
Follow-up from my previous comment. The build appears to fail if I try to run it twice without running "clean" in between. In other words, to successfully build, I ran: fakeroot debian/rules clean fakeroot debian/rules binary-headers binary-generic binary-perarch The drawback is it rebuilds everything (which is about 45 minutes on my machine). -- 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/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux Status in linux package in Ubuntu: Confirmed Bug description: I've been attempting to build both the hwe-edge and lowlatency-hwe- next kernels from source. Both fail on bpftool not being present, though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is there. ``` make[1]: Leaving directory '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf' mv /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux mv: cannot stat '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:713: /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] Error 1 ``` I've installed the related version of libbpf1 and libbpf-devel, but still seeing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+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 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" Status in linux package in Ubuntu: Confirmed Bug description: After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel that was recently introduced, the test machine started flooding the terminal with following messages: [ 1877.712068] BUG: Bad page state in process swapper/0 pfn:58919 The process name varies and appears to be whatever is currently doing something. I installed a fresh up to date copy to see if this could be replicated elsewhere and the outcome is the same. Both of the machines are VMs running under Xen with XCP-ng, although unsure if it's related. The issue produces a notable amount of syslog entries. If left running, the system will eventually go into a state where processes get stuck and do not react to systemd control, even when there's no notable load, no memory pressure nor is the disk space low. Booted back to 6.6 kernel the issue no longer happens. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 11 00:31 seq crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Mar 11 00:36:24 2024 InstallationDate: Installed on 2024-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240222) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2024 dmi.bios.release: 4.13 dmi.bios.vendor: Xen dmi.bios.version: 4.13 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.13 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+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 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
One of my VM's is affected too, running under Xen with XCP-ng. -- 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/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" Status in linux package in Ubuntu: Confirmed Bug description: After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel that was recently introduced, the test machine started flooding the terminal with following messages: [ 1877.712068] BUG: Bad page state in process swapper/0 pfn:58919 The process name varies and appears to be whatever is currently doing something. I installed a fresh up to date copy to see if this could be replicated elsewhere and the outcome is the same. Both of the machines are VMs running under Xen with XCP-ng, although unsure if it's related. The issue produces a notable amount of syslog entries. If left running, the system will eventually go into a state where processes get stuck and do not react to systemd control, even when there's no notable load, no memory pressure nor is the disk space low. Booted back to 6.6 kernel the issue no longer happens. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 11 00:31 seq crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Mar 11 00:36:24 2024 InstallationDate: Installed on 2024-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240222) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2024 dmi.bios.release: 4.13 dmi.bios.vendor: Xen dmi.bios.version: 4.13 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.13 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Just to inform that Very Kindly, Richardo Ribalda has confirmed the patch to the UVC Quanta 0408:4035 camera, allowing it to join the official source code. Hope that in few releases the uvc driver will be normally recognising the camera. BR PS Seems that it should also apply to UVC Quanta 0408:4033 camera -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor:
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed -- 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/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). * The remaning 6 commits are needed for HVCS, that is essentially broken without them. Overall, issues they fix are race conditions, hotplug remove issues, as well as memory leaks. * Please notice that this is entirely ppc64el architecture-specifc. [Other Info] * All the commits listed above are included in mantic and noble. Hence these are set to Invalid. * Meanwhile these requested commits have been added to other kernels and distros. __ ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
** No longer affects: llvm-toolchain-17 (Ubuntu) ** No longer affects: llvm-toolchain-18 (Ubuntu) ** No longer affects: llvm-toolchain-17 (Ubuntu Noble) ** No longer affects: llvm-toolchain-18 (Ubuntu Noble) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: New Status in gcc-11 package in Ubuntu: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: New Status in gcc-14 package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: New Status in llvm-toolchain-16 package in Ubuntu: New Status in gcc-10 source package in Noble: New Status in gcc-11 source package in Noble: New Status in gcc-12 source package in Noble: New Status in gcc-13 source package in Noble: New Status in gcc-14 source package in Noble: New Status in gcc-8 source package in Noble: New Status in gcc-9 source package in Noble: New Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: New Status in llvm-toolchain-16 source package in Noble: New Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). * The remaning 6 commits are needed for HVCS, that is essentially broken without them. Overall, issues they fix are race conditions, hotplug remove issues, as well as memory leaks. * Please notice that this is entirely ppc64el architecture-specifc. [Other Info] * All the commits listed above are included in mantic and noble. Hence these are set to Invalid. * Meanwhile these requested commits have been added to other kernels and distros. __ ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot,
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Invalid
--
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/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2058034] Re: iwlwifi hangs the computer
** Description changed: I recently discovered that my Wifi hangs the computer when I try to deactivate Wifi. + Actually, most of the programs do work when I try to deactivate Wifi, but, for instance, I cannot sudo anymore. Control-C or Control-Z won't terminate or suspend it. + I may have to press on the power button to power off the computer. + Below, I put a stack trace from syslog. I have found a workaround : rmmod works, so I use it (and modprobe) to kill (and restart) Wifi. - I have updated my BIOS to the latest, it changes noting. + I have updated my BIOS to the latest, it changes nothing. The version of the firmware, if it matters : iwlwifi :3b:00.0: loaded firmware version 46.ff18e32a.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm An example of stack trace : 2024-03-15T09:37:06.483828+01:00 clairetnet kernel: [ 208.124786] iwlwifi :3b:00.0: RF_KILL bit toggled to disable radio. 2024-03-15T09:37:06.483850+01:00 clairetnet kernel: [ 208.124789] iwlwifi :3b:00.0: reporting RF_KILL (radio disabled) 2024-03-15T09:37:06.508745+01:00 clairetnet systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... 2024-03-15T09:37:06.511481+01:00 clairetnet systemd[1]: Started systemd- rfkill.service - Load/Save RF Kill Switch Status. 2024-03-15T09:37:06.520063+01:00 clairetnet kernel: [ 208.159089] wlp59s0: deauthenticating from 90:9a:4a:3e:a2:93 by local choice (Reason: 3=DEAUTH_LEAVING) 2024-03-15T09:37:08.523909+01:00 clairetnet kernel: [ 210.162713] iwlwifi :3b:00.0: fail to flush all tx fifo queues Q 5 2024-03-15T09:37:08.523951+01:00 clairetnet kernel: [ 210.163613] iwlwifi :3b:00.0: Queue 5 is active on fifo 3 and stuck for 1 ms. SW [4, 5] HW [5, 5] FH TRB=0x080305004 2024-03-15T09:37:10.528159+01:00 clairetnet kernel: [ 212.166502] iwlwifi :3b:00.0: fail to flush all tx fifo queues Q 5 2024-03-15T09:37:10.528194+01:00 clairetnet kernel: [ 212.167306] iwlwifi :3b:00.0: Queue 5 is active on fifo 3 and stuck for 1 ms. SW [4, 5] HW [5, 5] FH TRB=0x080305004 2024-03-15T09:37:10.528204+01:00 clairetnet kernel: [ 212.167404] [ cut here ] 2024-03-15T09:37:10.528208+01:00 clairetnet kernel: [ 212.167408] WARNING: CPU: 2 PID: 1256 at net/mac80211/sta_info.c:1442 __sta_info_destroy_part2+0x1c0/0x1f0 [mac80211] 2024-03-15T09:37:10.528225+01:00 clairetnet kernel: [ 212.167659] Modules linked in: ccm cdc_ether usbnet r8152 mii snd_seq_dummy snd_hrtimer snd_hda_codec_hdmi snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) bnep binfmt_misc snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(POE) nvidia_modeset(POE) snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_tcc_cooling snd_hda_intel x86_pkg_temp_thermal intel_powerclamp snd_intel_dspcfg snd_intel_sdw_acpi coretemp snd_hda_codec iwlmvm snd_hda_core kvm_intel snd_hwdep nls_iso8859_1 nvidia(POE) snd_pcm dell_rbtn snd_seq_midi mac80211 kvm snd_seq_midi_event i915 snd_rawmidi irqbypass libarc4 btusb crct10dif_pclmul uvcvideo btrtl dell_laptop polyval_clmulni polyval_generic cmdlinepart videobuf2_vmalloc btbcm uvc 2024-03-15T09:37:10.528230+01:00 clairetnet kernel: [ 212.167814] snd_seq ghash_clmulni_intel btintel drm_buddy videobuf2_memops spi_nor btmtk sha256_ssse3 videobuf2_v4l2 ttm dell_wmi processor_thermal_device_pci_legacy snd_seq_device mei_hdcp mei_pxp mtd intel_rapl_msr dell_smm_hwmon sha1_ssse3 bluetooth aesni_intel processor_thermal_device snd_timer iwlwifi dell_smbios videodev drm_display_helper crypto_simd processor_thermal_rfim cryptd processor_thermal_mbox dcdbas rapl intel_cstate cec dell_wmi_sysman processor_thermal_rapl mei_me videobuf2_common rc_core ledtrig_audio dell_wmi_descriptor firmware_attributes_class intel_wmi_thunderbolt wmi_bmof mxm_wmi snd i2c_i801 intel_rapl_common ecdh_generic spi_intel_pci cfg80211 mc i2c_smbus spi_intel soundcore mei ecc drm_kms_helper i2c_algo_bit intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad joydev input_leds hid_multitouch mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables 2024-03-15T09:37:10.528231+01:00 clairetnet kernel: [ 212.167988] autofs4 usbhid hid_generic rtsx_pci_sdmmc nvme crc32_pclmul psmouse nvme_core video thunderbolt intel_lpss_pci ucsi_acpi nvme_common rtsx_pci i2c_hid_acpi typec_ucsi ahci intel_lpss i2c_hid xhci_pci libahci typec idma64 xhci_pci_renesas
[Kernel-packages] [Bug 2058034] [NEW] iwlwifi hangs the computer
Public bug reported: I recently discovered that my Wifi hangs the computer when I try to deactivate Wifi. Actually, most of the programs do work when I try to deactivate Wifi, but, for instance, I cannot sudo anymore. Control-C or Control-Z won't terminate or suspend it. I may have to press on the power button to power off the computer. Below, I put a stack trace from syslog. I have found a workaround : rmmod works, so I use it (and modprobe) to kill (and restart) Wifi. I have updated my BIOS to the latest, it changes nothing. The version of the firmware, if it matters : iwlwifi :3b:00.0: loaded firmware version 46.ff18e32a.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm An example of stack trace : 2024-03-15T09:37:06.483828+01:00 clairetnet kernel: [ 208.124786] iwlwifi :3b:00.0: RF_KILL bit toggled to disable radio. 2024-03-15T09:37:06.483850+01:00 clairetnet kernel: [ 208.124789] iwlwifi :3b:00.0: reporting RF_KILL (radio disabled) 2024-03-15T09:37:06.508745+01:00 clairetnet systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... 2024-03-15T09:37:06.511481+01:00 clairetnet systemd[1]: Started systemd- rfkill.service - Load/Save RF Kill Switch Status. 2024-03-15T09:37:06.520063+01:00 clairetnet kernel: [ 208.159089] wlp59s0: deauthenticating from 90:9a:4a:3e:a2:93 by local choice (Reason: 3=DEAUTH_LEAVING) 2024-03-15T09:37:08.523909+01:00 clairetnet kernel: [ 210.162713] iwlwifi :3b:00.0: fail to flush all tx fifo queues Q 5 2024-03-15T09:37:08.523951+01:00 clairetnet kernel: [ 210.163613] iwlwifi :3b:00.0: Queue 5 is active on fifo 3 and stuck for 1 ms. SW [4, 5] HW [5, 5] FH TRB=0x080305004 2024-03-15T09:37:10.528159+01:00 clairetnet kernel: [ 212.166502] iwlwifi :3b:00.0: fail to flush all tx fifo queues Q 5 2024-03-15T09:37:10.528194+01:00 clairetnet kernel: [ 212.167306] iwlwifi :3b:00.0: Queue 5 is active on fifo 3 and stuck for 1 ms. SW [4, 5] HW [5, 5] FH TRB=0x080305004 2024-03-15T09:37:10.528204+01:00 clairetnet kernel: [ 212.167404] [ cut here ] 2024-03-15T09:37:10.528208+01:00 clairetnet kernel: [ 212.167408] WARNING: CPU: 2 PID: 1256 at net/mac80211/sta_info.c:1442 __sta_info_destroy_part2+0x1c0/0x1f0 [mac80211] 2024-03-15T09:37:10.528225+01:00 clairetnet kernel: [ 212.167659] Modules linked in: ccm cdc_ether usbnet r8152 mii snd_seq_dummy snd_hrtimer snd_hda_codec_hdmi snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) bnep binfmt_misc snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(POE) nvidia_modeset(POE) snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_tcc_cooling snd_hda_intel x86_pkg_temp_thermal intel_powerclamp snd_intel_dspcfg snd_intel_sdw_acpi coretemp snd_hda_codec iwlmvm snd_hda_core kvm_intel snd_hwdep nls_iso8859_1 nvidia(POE) snd_pcm dell_rbtn snd_seq_midi mac80211 kvm snd_seq_midi_event i915 snd_rawmidi irqbypass libarc4 btusb crct10dif_pclmul uvcvideo btrtl dell_laptop polyval_clmulni polyval_generic cmdlinepart videobuf2_vmalloc btbcm uvc 2024-03-15T09:37:10.528230+01:00 clairetnet kernel: [ 212.167814] snd_seq ghash_clmulni_intel btintel drm_buddy videobuf2_memops spi_nor btmtk sha256_ssse3 videobuf2_v4l2 ttm dell_wmi processor_thermal_device_pci_legacy snd_seq_device mei_hdcp mei_pxp mtd intel_rapl_msr dell_smm_hwmon sha1_ssse3 bluetooth aesni_intel processor_thermal_device snd_timer iwlwifi dell_smbios videodev drm_display_helper crypto_simd processor_thermal_rfim cryptd processor_thermal_mbox dcdbas rapl intel_cstate cec dell_wmi_sysman processor_thermal_rapl mei_me videobuf2_common rc_core ledtrig_audio dell_wmi_descriptor firmware_attributes_class intel_wmi_thunderbolt wmi_bmof mxm_wmi snd i2c_i801 intel_rapl_common ecdh_generic spi_intel_pci cfg80211 mc i2c_smbus spi_intel soundcore mei ecc drm_kms_helper i2c_algo_bit intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad joydev input_leds hid_multitouch mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables 2024-03-15T09:37:10.528231+01:00 clairetnet kernel: [ 212.167988] autofs4 usbhid hid_generic rtsx_pci_sdmmc nvme crc32_pclmul psmouse nvme_core video thunderbolt intel_lpss_pci ucsi_acpi nvme_common rtsx_pci i2c_hid_acpi typec_ucsi ahci intel_lpss i2c_hid xhci_pci libahci typec idma64 xhci_pci_renesas hid wmi pinctrl_cannonlake 2024-03-15T09:37:10.528232+01:00 clairetnet kernel: [ 212.168044] CPU: 2 PID: 1256 Comm: NetworkManager Tainted: P OE 6.5.0-25-generic #25-Ubuntu 2024-03-15T09:37:10.528233+01:00 clairetnet kernel: [
[Kernel-packages] [Bug 2049922] Re: PCI ATS quirk patch needed for IDPF
This bug is awaiting verification that the linux-
gcp-4.15/4.15.0-1160.177 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-bionic-linux-gcp-4.15' to
'verification-done-bionic-linux-gcp-4.15'. If the problem still exists,
change the tag 'verification-needed-bionic-linux-gcp-4.15' to
'verification-failed-bionic-linux-gcp-4.15'.
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-bionic-linux-gcp-4.15-v2
verification-needed-bionic-linux-gcp-4.15
--
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/2049922
Title:
PCI ATS quirk patch needed for IDPF
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp-4.15 package in Ubuntu:
New
Status in linux-gcp source package in Bionic:
In Progress
Status in linux-gcp-4.15 source package in Bionic:
Fix Committed
Status in linux-gcp source package in Focal:
In Progress
Bug description:
[Impact]
* Request from Google to include Intel patches for IDPF support if used from
out-of-tree module to prevent system instability.
[Fixes]
f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")
[Test Case]
* Compile test
* Boot test
* Test on non-IDPF instance
* Tested by Google
[Where things could go wrong]
* Low chance of regression, changes very isolated
[Other Info]
* SF #00376470
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2049569] Re: Enable the mic-mute led on Dell MTL laptops
Accepted into -proposed, but as part of firmware-sof verification,
please also verify audio function on MTL enpowered machines as mentioned
in the regression potential section. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on Dell MTL laptops
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is
working but the LED(on F4) state is not changed accordingly.
[Fix]
There's no problem on the same series on RPL platform. It needs MTL specific
SoF driver and controls to support the registered mixer switch. It requires the
patches in
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
and
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/
[Test Case]
1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
It's only required for new sof-audio-pci-intel-mtl driver. The impact should
be restricting.
== firmware-sof ==
[Impact]
The mic-mute led not working on Intel MTL powered laptops.
[Fix]
For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control
matches with the updated driver.
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
[Where problems could occur]
The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+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 2049569] Re: Enable the mic-mute led on Dell MTL laptops
Hello Chris, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: firmware-sof (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on Dell MTL laptops
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is
working but the LED(on F4) state is not changed accordingly.
[Fix]
There's no problem on the same series on RPL platform. It needs MTL specific
SoF driver and controls to support the registered mixer switch. It requires the
patches in
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
and
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/
[Test Case]
1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
It's only required for new sof-audio-pci-intel-mtl driver. The impact should
be restricting.
== firmware-sof ==
[Impact]
The mic-mute led not working on Intel MTL powered laptops.
[Fix]
For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control
matches with the updated driver.
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
[Where problems could occur]
The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+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 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Turns out we didn't even need to modify the kernel for this. By choosing simplefb and the 'tiny' DRM drivers for initrd, we get simpledrm.ko as it existed in our older kernels... https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+merge/462482 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in linux source package in Mantic: Won't Fix Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer [ Test Plan ] * Ensure that systems currently relying on fbdev (and therefore only allowing Xorg logins) such as some virtual machine types, boot with working Wayland support. [ Where Problems could occur ] * When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen (bug 2039757). * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048077] Re: Migrate oem-6.1 to oem-6.5
** Changed in: linux-meta-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-restricted-modules-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048077 Title: Migrate oem-6.1 to oem-6.5 Status in linux-meta-oem-6.5 package in Ubuntu: Invalid Status in linux-restricted-modules-oem-6.5 package in Ubuntu: Invalid Status in linux-meta-oem-6.5 source package in Jammy: Fix Committed Status in linux-restricted-modules-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] Migrate oem-6.1 to oem-6.5, because some platforms need it instead of hwe-6.5. [Test case] Update a machine with oem-6.1 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.5/+bug/2048077/+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 1970069] Re: Annoying boot messages interfering with splash screen
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+merge/462482 ** Merge proposal unlinked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481 -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2051612] Re: False key press suspend wakeup on AMD Framework 13
that commit is included since -1014.15
** No longer affects: ubuntu
** Package changed: linux-meta-oem-6.5 (Ubuntu) => linux-oem-6.5
(Ubuntu)
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051612
Title:
False key press suspend wakeup on AMD Framework 13
Status in linux-oem-6.5 package in Ubuntu:
Fix Released
Bug description:
Affects: Ubuntu 22.04.3 OEM C kernel.
What is expected: Close the lid to suspend, expecting it to remain in
a suspended state.
What is happening instead: The Laptop 13 (AMD Ryzen 7040Series) BIOS 03.03
has a workaround
included in the EC firmware that will cause the EC to emit a "spurious"
key press during the resume from s0i3 [1].
There is a workaround described as follows:
/etc/udev/rules.d/20-suspend-fixes.rules
with
ACTION=="add", SUBSYSTEM=="serio", DRIVERS=="atkbd",
ATTR{power/wakeup}="disabled"
Provides a workaround.
Mario Limonciello points out this is not backported to the OEM kernel, so the
fix may need to happen here.
https://community.frame.work/t/responded-waking-from-sleep-when-plugged-in-amd-k-ubuntu-22-04/44168/10
Here is the Linux commit itself:
https://github.com/torvalds/linux/commit/a55bdad5dfd1efd4ed9ffe518897a21ca8e4e193
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2051612/+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 1970069] Re: Annoying boot messages interfering with splash screen
** Merge proposal linked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481 ** Merge proposal linked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462482 -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
** Description changed: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: - quiet splash loglevel=2 fastboot - - [ Test Plan ] - - 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. - 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. - 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. - - [ Where problems could occur ] - - Since the fix works by deferring fbcon's takeover of the console, the - main problem encountered during its development was the inability to VT - switch. + quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Seems it's fairly easy to make a working solution in initramfs-tools alone, but there's a compromise. If I only include tiny/simple framebuffer drivers in initrd then i915 starts so late that Plymouth doesn't use it, and bug 2054769 can occur on some machines. If I include all the current drm drivers in initrd then it bloats to 100MB, but at least i915 starts early enough (only just) to avoid bug 2054769. I'm currently leaning toward only including tiny/simple framebuffer drivers and trying to solve bug 2054769 with additional heuristics in Plymouth itself (when the physical monitor dimensions are unknown under simpledrm). If nothing else, fixing this bug is more important than fixing bug 2054769 for all cases. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Plymouth would still need patching in order to optimize the drm modules in debian/local/plymouth.hook ** Changed in: plymouth (Ubuntu) Status: Invalid => 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
I think the delay I'm seeing is a feature of Plymouth, not a bug: "ignoring since we only handle SimpleDRM devices after timeout" As much as I dislike it perpetuating bug 1869655, this feature does prevent bug 2054769 from reoccurring. But this raises the question: is it worth putting i915, amdgpu etc in initrd just to try and solve bug 1869655? Possibly not. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
** Package changed: linux-hwe (Ubuntu) => subiquity (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/2057996
Title:
ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
stas,shim-signed
Status in subiquity package in Ubuntu:
New
Bug description:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64-0222.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on nvme,expected to install succefully.
What happened instead:
Install os on nvme, install always failed.
Before installation, we cleaned up all our nvme disk by dd if=/dev/zero
of=/dev/sda bs=1M count=5
The error log:
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed',
'nvme-cli', 'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages:
FAIL: installing missing packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback
(most recent call last):
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret =
args.func(args)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1998, in curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
builtin_curthooks(cfg, target, state)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1803, in builtin_curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
install_missing_packages(cfg, target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1362, in install_missing_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
distro.install_packages(to_add, target=target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472,
in install_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254,
in run_apt_command
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302,
in apt_install
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
_subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147,
in _subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise
ProcessExecutionError(stdout=out, stderr=err,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
curtin.util.ProcessExecutionError: Unexpected error while running command.
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Command:
['unshare', '--fork', '--pid', '--', 'chroot', '/target',
[Kernel-packages] [Bug 2057996] [NEW] ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Public bug reported:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64-0222.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on nvme,expected to install succefully.
What happened instead:
Install os on nvme, install always failed.
Before installation, we cleaned up all our nvme disk by dd if=/dev/zero
of=/dev/sda bs=1M count=5
The error log:
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed',
'nvme-cli', 'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages:
FAIL: installing missing packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback (most
recent call last):
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret =
args.func(args)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1998, in curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
builtin_curthooks(cfg, target, state)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1803, in builtin_curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
install_missing_packages(cfg, target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1362, in install_missing_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
distro.install_packages(to_add, target=target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472,
in install_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254,
in run_apt_command
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302,
in apt_install
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
_subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147,
in _subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise
ProcessExecutionError(stdout=out, stderr=err,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
curtin.util.ProcessExecutionError: Unexpected error while running command.
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Command:
['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'apt-get', '--quiet',
'--assume-yes', '--option=Dpkg::options::=--force-unsafe-io',
'--option=Dpkg::Options::=--force-confold', 'install', '--download-only',
'efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed', 'nvme-cli',
'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Exit code: 100
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Reason: -
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Stdout: ''
Mar 15 03:03:05
[Kernel-packages] [Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
i add the journal log to attachment, and we also test another ubuntu
version, ubuntu 22.04 can install successfully.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2057996/+attachment/5756122/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/2057996
Title:
ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
stas,shim-signed
Status in linux-hwe package in Ubuntu:
New
Bug description:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64-0222.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on nvme,expected to install succefully.
What happened instead:
Install os on nvme, install always failed.
Before installation, we cleaned up all our nvme disk by dd if=/dev/zero
of=/dev/sda bs=1M count=5
The error log:
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed',
'nvme-cli', 'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages:
FAIL: installing missing packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback
(most recent call last):
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret =
args.func(args)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1998, in curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
builtin_curthooks(cfg, target, state)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1803, in builtin_curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
install_missing_packages(cfg, target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1362, in install_missing_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
distro.install_packages(to_add, target=target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472,
in install_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254,
in run_apt_command
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302,
in apt_install
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
_subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147,
in _subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise
ProcessExecutionError(stdout=out, stderr=err,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
