Public bug reported:
Audio via HDMI stops working after upgrading ubuntu-server from noble
(Kernel 6.17.0-19) to resolute (kernel 7.0.0-10)
aplay -L shows the right ALSA device (I use HDMI:0,0) for both noble and resolute.
I cannot get any audio via HDMI in resolute.
To reproduce: "speakertest -c2 -D hdmi:0,0" gives no noise in resolute but in noble.
I can switch back and forth between the two releases and the problem is always reproducible.
I use pure ALSA devices (Ubuntu server) and have no PipeWire or PulseAudio installed.
My graphics card is this:
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev dc)
08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir/Cezanne HDMI/DP Audio Controller
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-modules-7.0.0-10-generic 7.0.0-10.10
ProcVersionSignature: Ubuntu 7.0.0-10.10-generic 7.0.0-rc4
Uname: Linux 7.0.0-10-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
Date: Sat Mar 28 18:18:36 2026
Dependencies: wireless-regdb 2026.02.04-0ubuntu1
InstallationDate: Installed on 2026-03-27 (1 days ago)
InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Daily amd64 (20260325)
MachineType: To Be Filled By O.E.M. B550M Steel Legend
ProcEnviron:
LANG=C.UTF-8
LC_CTYPE=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-10-generic root=UUID=95104315-6283-43c6-9156-c048f7277be2 ro amdgpu.dc=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P2.50
dmi.board.name: B550M Steel Legend
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.50:bd10/19/2022:br5.17:svnToBeFilledByO.E.M.:pnB550MSteelLegend:pvrToBeFilledByO.E.M.:rvnASRock:rnB550MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:pfaToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: B550M Steel Legend
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146642
Title:
No audio via HDMI with kernel 7.0 and AMDGPU
Status in linux package in Ubuntu:
New
Bug description:
Audio via HDMI stops working after upgrading ubuntu-server from noble
(Kernel 6.17.0-19) to resolute (kernel 7.0.0-10)
aplay -L shows the right ALSA device (I use HDMI:0,0) for both noble and resolute.
I cannot get any audio via HDMI in resolute.
To reproduce: "speakertest -c2 -D hdmi:0,0" gives no noise in resolute but in noble.
I can switch back and forth between the two releases and the problem is always reproducible.
I use pure ALSA devices (Ubuntu server) and have no PipeWire or PulseAudio installed.
My graphics card is this:
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev dc)
08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir/Cezanne HDMI/DP Audio Controller
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-modules-7.0.0-10-generic 7.0.0-10.10
ProcVersionSignature: Ubuntu 7.0.0-10.10-generic 7.0.0-rc4
Uname: Linux 7.0.0-10-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
Date: Sat Mar 28 18:18:36 2026
Dependencies: wireless-regdb 2026.02.04-0ubuntu1
InstallationDate: Installed on 2026-03-27 (1 days ago)
InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Daily amd64 (20260325)
MachineType: To Be Filled By O.E.M. B550M Steel Legend
ProcEnviron:
LANG=C.UTF-8
LC_CTYPE=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-10-generic root=UUID=95104315-6283-43c6-9156-c048f7277be2 ro amdgpu.dc=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P2.50
dmi.board.name: B550M Steel Legend
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.50:bd10/19/2022:br5.17:svnToBeFilledByO.E.M.:pnB550MSteelLegend:pvrToBeFilledByO.E.M.:rvnASRock:rnB550MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:pfaToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: B550M Steel Legend
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146642/+subscriptions
суббота
[Bug 2146639] [NEW] Request for CXL DRAM Command Interface Support
Private bug reported:
Compute Express Link (CXL) introduces a new paradigm for memory
expansion and pooling, where DRAM attached to external devices (CXL
Type-3 memory devices) is accessed over the PCIe physical layer using
CXL protocols. In this architecture, the traditional DRAM command
interface (ACT, PRE, RD, WR, REF, MRS, etc.) is abstracted behind the
CXL device controller, and the host interacts with memory using higher-
level load/store semantics via CXL.mem.
In the Linux kernel, CXL support (via the CXL subsystem and drivers such
as cxl_core, cxl_mem) enables discovery, configuration, and management
of CXL-attached memory. However, visibility into underlying DRAM command
behavior (e.g., command retries, media errors, timing constraints) is
limited. Enhancing support would improve observability and reliability
for next-generation memory architectures leveraging CXL.
Feature Request:
Requested details to be enabled on OS:
Enhance CXL subsystem (cxl_core, cxl_mem) to expose DRAM command-related telemetry abstracted by CXL devices.
Integrate CXL memory error reporting with EDAC and RAS frameworks.
Support reporting of internal media events (e.g., command retries, refresh issues, parity/ECC events).
Provide sysfs/debugfs interfaces for monitoring CXL memory device health and command behavior.
Enable firmware-to-OS handoff of CXL memory characteristics and command-related constraints.
Support advanced CXL RAS features (poison handling, error containment, media scrub reporting).
Ensure compatibility with memory pooling and multi-headed CXL configurations.
Enable tracing/logging for performance bottlenecks related to internal DRAM command scheduling.
Document CXL memory device behavior, limitations, and observability mechanisms.
Business Justification:
- Improves observability of CXL-attached memory health and performance.
- Enhances reliability and RAS capabilities for memory expansion and pooling use cases.
- Enables efficient debugging of memory-related issues in disaggregated architectures.
- Supports adoption of CXL-based infrastructure in data centers and hyperscale environments.
- Aligns OS capabilities with emerging CXL memory ecosystem and standards.
References:
– CXL 2.0 / 3.0 Specification (CXL.mem)
Linux Kernel CXL Subsystem Documentation
JEDEC DRAM Standards (DDR5, MRDIMM)
Linux EDAC Subsystem Documentation
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146639
Title:
Request for CXL DRAM Command Interface Support
Status in linux package in Ubuntu:
New
Bug description:
Compute Express Link (CXL) introduces a new paradigm for memory
expansion and pooling, where DRAM attached to external devices (CXL
Type-3 memory devices) is accessed over the PCIe physical layer using
CXL protocols. In this architecture, the traditional DRAM command
interface (ACT, PRE, RD, WR, REF, MRS, etc.) is abstracted behind the
CXL device controller, and the host interacts with memory using
higher-level load/store semantics via CXL.mem.
In the Linux kernel, CXL support (via the CXL subsystem and drivers
such as cxl_core, cxl_mem) enables discovery, configuration, and
management of CXL-attached memory. However, visibility into underlying
DRAM command behavior (e.g., command retries, media errors, timing
constraints) is limited. Enhancing support would improve observability
and reliability for next-generation memory architectures leveraging
CXL.
Feature Request:
Requested details to be enabled on OS:
Enhance CXL subsystem (cxl_core, cxl_mem) to expose DRAM command-related telemetry abstracted by CXL devices.
Integrate CXL memory error reporting with EDAC and RAS frameworks.
Support reporting of internal media events (e.g., command retries, refresh issues, parity/ECC events).
Provide sysfs/debugfs interfaces for monitoring CXL memory device health and command behavior.
Enable firmware-to-OS handoff of CXL memory characteristics and command-related constraints.
Support advanced CXL RAS features (poison handling, error containment, media scrub reporting).
Ensure compatibility with memory pooling and multi-headed CXL configurations.
Enable tracing/logging for performance bottlenecks related to internal DRAM command scheduling.
Document CXL memory device behavior, limitations, and observability mechanisms.
Business Justification:
- Improves observability of CXL-attached memory health and performance.
- Enhances reliability and RAS capabilities for memory expansion and pooling use cases.
- Enables efficient debugging of memory-related issues in disaggregated architectures.
- Supports adoption of CXL-based infrastructure in data centers and hyperscale environments.
- Aligns OS capabilities with emerging CXL memory ecosystem and standards.
References:
– CXL 2.0 / 3.0 Specification (CXL.mem)
Linux Kernel CXL Subsystem Documentation
JEDEC DRAM Standards (DDR5, MRDIMM)
Linux EDAC Subsystem Documentation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146639/+subscriptions
Compute Express Link (CXL) introduces a new paradigm for memory
expansion and pooling, where DRAM attached to external devices (CXL
Type-3 memory devices) is accessed over the PCIe physical layer using
CXL protocols. In this architecture, the traditional DRAM command
interface (ACT, PRE, RD, WR, REF, MRS, etc.) is abstracted behind the
CXL device controller, and the host interacts with memory using higher-
level load/store semantics via CXL.mem.
In the Linux kernel, CXL support (via the CXL subsystem and drivers such
as cxl_core, cxl_mem) enables discovery, configuration, and management
of CXL-attached memory. However, visibility into underlying DRAM command
behavior (e.g., command retries, media errors, timing constraints) is
limited. Enhancing support would improve observability and reliability
for next-generation memory architectures leveraging CXL.
Feature Request:
Requested details to be enabled on OS:
Enhance CXL subsystem (cxl_core, cxl_mem) to expose DRAM command-related telemetry abstracted by CXL devices.
Integrate CXL memory error reporting with EDAC and RAS frameworks.
Support reporting of internal media events (e.g., command retries, refresh issues, parity/ECC events).
Provide sysfs/debugfs interfaces for monitoring CXL memory device health and command behavior.
Enable firmware-to-OS handoff of CXL memory characteristics and command-related constraints.
Support advanced CXL RAS features (poison handling, error containment, media scrub reporting).
Ensure compatibility with memory pooling and multi-headed CXL configurations.
Enable tracing/logging for performance bottlenecks related to internal DRAM command scheduling.
Document CXL memory device behavior, limitations, and observability mechanisms.
Business Justification:
- Improves observability of CXL-attached memory health and performance.
- Enhances reliability and RAS capabilities for memory expansion and pooling use cases.
- Enables efficient debugging of memory-related issues in disaggregated architectures.
- Supports adoption of CXL-based infrastructure in data centers and hyperscale environments.
- Aligns OS capabilities with emerging CXL memory ecosystem and standards.
References:
– CXL 2.0 / 3.0 Specification (CXL.mem)
Linux Kernel CXL Subsystem Documentation
JEDEC DRAM Standards (DDR5, MRDIMM)
Linux EDAC Subsystem Documentation
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146639
Title:
Request for CXL DRAM Command Interface Support
Status in linux package in Ubuntu:
New
Bug description:
Compute Express Link (CXL) introduces a new paradigm for memory
expansion and pooling, where DRAM attached to external devices (CXL
Type-3 memory devices) is accessed over the PCIe physical layer using
CXL protocols. In this architecture, the traditional DRAM command
interface (ACT, PRE, RD, WR, REF, MRS, etc.) is abstracted behind the
CXL device controller, and the host interacts with memory using
higher-level load/store semantics via CXL.mem.
In the Linux kernel, CXL support (via the CXL subsystem and drivers
such as cxl_core, cxl_mem) enables discovery, configuration, and
management of CXL-attached memory. However, visibility into underlying
DRAM command behavior (e.g., command retries, media errors, timing
constraints) is limited. Enhancing support would improve observability
and reliability for next-generation memory architectures leveraging
CXL.
Feature Request:
Requested details to be enabled on OS:
Enhance CXL subsystem (cxl_core, cxl_mem) to expose DRAM command-related telemetry abstracted by CXL devices.
Integrate CXL memory error reporting with EDAC and RAS frameworks.
Support reporting of internal media events (e.g., command retries, refresh issues, parity/ECC events).
Provide sysfs/debugfs interfaces for monitoring CXL memory device health and command behavior.
Enable firmware-to-OS handoff of CXL memory characteristics and command-related constraints.
Support advanced CXL RAS features (poison handling, error containment, media scrub reporting).
Ensure compatibility with memory pooling and multi-headed CXL configurations.
Enable tracing/logging for performance bottlenecks related to internal DRAM command scheduling.
Document CXL memory device behavior, limitations, and observability mechanisms.
Business Justification:
- Improves observability of CXL-attached memory health and performance.
- Enhances reliability and RAS capabilities for memory expansion and pooling use cases.
- Enables efficient debugging of memory-related issues in disaggregated architectures.
- Supports adoption of CXL-based infrastructure in data centers and hyperscale environments.
- Aligns OS capabilities with emerging CXL memory ecosystem and standards.
References:
– CXL 2.0 / 3.0 Specification (CXL.mem)
Linux Kernel CXL Subsystem Documentation
JEDEC DRAM Standards (DDR5, MRDIMM)
Linux EDAC Subsystem Documentation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146639/+subscriptions
[Bug 2146638] [NEW] Request for PCIe Precision Time Measurement (PTM) Support
Private bug reported:
PCIe Precision Time Measurement (PTM) is a capability defined in the PCI
Express specification that enables precise time synchronization between
components in a PCIe hierarchy. PTM allows endpoints and root complexes
to establish a common notion of time by exchanging timing messages and
calculating path delays.
This feature is critical for latency-sensitive and time-synchronized
applications such as high-frequency trading, telecom (5G), real-time
analytics, and distributed systems. PTM operates by designating a PTM
Root (typically the Root Complex) and PTM Responders (endpoints),
enabling accurate timestamping across devices.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe PTM capability detection and enumeration in the PCI subsystem.
Support PTM Root and PTM Responder roles in kernel and platform firmware.
Expose PTM timing information to user space via sysfs or appropriate APIs.
Integrate PTM with existing time synchronization frameworks (e.g., PTP/PHC).
Update device drivers (NICs, accelerators) to utilize PTM timestamps where applicable.
Ensure interoperability with PCIe switches and retimers supporting PTM.
Provide validation and diagnostics tools for PTM accuracy and drift measurement.
Enable PTM support in virtualization environments (KVM/QEMU passthrough scenarios).
Document configuration and usage of PTM across supported platforms.
Business Justification:
- Enables high-precision time synchronization across PCIe devices.
- Improves performance for latency-sensitive and real-time workloads.
- Supports telecom, financial, and distributed computing use cases.
- Aligns with modern hardware capabilities in NICs and accelerators.
- Enhances system-level observability and coordinated operations.
- Provides competitive differentiation for platforms requiring deterministic timing.
References:
PCI-SIG PCIe Base Specification (PTM Capability)
Linux Kernel PCI Subsystem Documentation
IEEE 1588 Precision Time Protocol (PTP)
PCIe PTM Architecture and Implementation Guides
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146638
Title:
Request for PCIe Precision Time Measurement (PTM) Support
Status in linux package in Ubuntu:
New
Bug description:
PCIe Precision Time Measurement (PTM) is a capability defined in the
PCI Express specification that enables precise time synchronization
between components in a PCIe hierarchy. PTM allows endpoints and root
complexes to establish a common notion of time by exchanging timing
messages and calculating path delays.
This feature is critical for latency-sensitive and time-synchronized
applications such as high-frequency trading, telecom (5G), real-time
analytics, and distributed systems. PTM operates by designating a PTM
Root (typically the Root Complex) and PTM Responders (endpoints),
enabling accurate timestamping across devices.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe PTM capability detection and enumeration in the PCI subsystem.
Support PTM Root and PTM Responder roles in kernel and platform firmware.
Expose PTM timing information to user space via sysfs or appropriate APIs.
Integrate PTM with existing time synchronization frameworks (e.g., PTP/PHC).
Update device drivers (NICs, accelerators) to utilize PTM timestamps where applicable.
Ensure interoperability with PCIe switches and retimers supporting PTM.
Provide validation and diagnostics tools for PTM accuracy and drift measurement.
Enable PTM support in virtualization environments (KVM/QEMU passthrough scenarios).
Document configuration and usage of PTM across supported platforms.
Business Justification:
- Enables high-precision time synchronization across PCIe devices.
- Improves performance for latency-sensitive and real-time workloads.
- Supports telecom, financial, and distributed computing use cases.
- Aligns with modern hardware capabilities in NICs and accelerators.
- Enhances system-level observability and coordinated operations.
- Provides competitive differentiation for platforms requiring deterministic timing.
References:
PCI-SIG PCIe Base Specification (PTM Capability)
Linux Kernel PCI Subsystem Documentation
IEEE 1588 Precision Time Protocol (PTP)
PCIe PTM Architecture and Implementation Guides
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146638/+subscriptions
PCIe Precision Time Measurement (PTM) is a capability defined in the PCI
Express specification that enables precise time synchronization between
components in a PCIe hierarchy. PTM allows endpoints and root complexes
to establish a common notion of time by exchanging timing messages and
calculating path delays.
This feature is critical for latency-sensitive and time-synchronized
applications such as high-frequency trading, telecom (5G), real-time
analytics, and distributed systems. PTM operates by designating a PTM
Root (typically the Root Complex) and PTM Responders (endpoints),
enabling accurate timestamping across devices.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe PTM capability detection and enumeration in the PCI subsystem.
Support PTM Root and PTM Responder roles in kernel and platform firmware.
Expose PTM timing information to user space via sysfs or appropriate APIs.
Integrate PTM with existing time synchronization frameworks (e.g., PTP/PHC).
Update device drivers (NICs, accelerators) to utilize PTM timestamps where applicable.
Ensure interoperability with PCIe switches and retimers supporting PTM.
Provide validation and diagnostics tools for PTM accuracy and drift measurement.
Enable PTM support in virtualization environments (KVM/QEMU passthrough scenarios).
Document configuration and usage of PTM across supported platforms.
Business Justification:
- Enables high-precision time synchronization across PCIe devices.
- Improves performance for latency-sensitive and real-time workloads.
- Supports telecom, financial, and distributed computing use cases.
- Aligns with modern hardware capabilities in NICs and accelerators.
- Enhances system-level observability and coordinated operations.
- Provides competitive differentiation for platforms requiring deterministic timing.
References:
PCI-SIG PCIe Base Specification (PTM Capability)
Linux Kernel PCI Subsystem Documentation
IEEE 1588 Precision Time Protocol (PTP)
PCIe PTM Architecture and Implementation Guides
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146638
Title:
Request for PCIe Precision Time Measurement (PTM) Support
Status in linux package in Ubuntu:
New
Bug description:
PCIe Precision Time Measurement (PTM) is a capability defined in the
PCI Express specification that enables precise time synchronization
between components in a PCIe hierarchy. PTM allows endpoints and root
complexes to establish a common notion of time by exchanging timing
messages and calculating path delays.
This feature is critical for latency-sensitive and time-synchronized
applications such as high-frequency trading, telecom (5G), real-time
analytics, and distributed systems. PTM operates by designating a PTM
Root (typically the Root Complex) and PTM Responders (endpoints),
enabling accurate timestamping across devices.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe PTM capability detection and enumeration in the PCI subsystem.
Support PTM Root and PTM Responder roles in kernel and platform firmware.
Expose PTM timing information to user space via sysfs or appropriate APIs.
Integrate PTM with existing time synchronization frameworks (e.g., PTP/PHC).
Update device drivers (NICs, accelerators) to utilize PTM timestamps where applicable.
Ensure interoperability with PCIe switches and retimers supporting PTM.
Provide validation and diagnostics tools for PTM accuracy and drift measurement.
Enable PTM support in virtualization environments (KVM/QEMU passthrough scenarios).
Document configuration and usage of PTM across supported platforms.
Business Justification:
- Enables high-precision time synchronization across PCIe devices.
- Improves performance for latency-sensitive and real-time workloads.
- Supports telecom, financial, and distributed computing use cases.
- Aligns with modern hardware capabilities in NICs and accelerators.
- Enhances system-level observability and coordinated operations.
- Provides competitive differentiation for platforms requiring deterministic timing.
References:
PCI-SIG PCIe Base Specification (PTM Capability)
Linux Kernel PCI Subsystem Documentation
IEEE 1588 Precision Time Protocol (PTP)
PCIe PTM Architecture and Implementation Guides
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146638/+subscriptions
[Bug 2146637] [NEW] Request for PCIe Gen6 (64 GT/s) Support
Private bug reported:
PCIe Gen6 introduces a significant advancement in high-speed
interconnect technology by doubling the data rate to 64 GT/s per lane
and adopting new signaling and encoding mechanisms such as PAM4 (Pulse
Amplitude Modulation-4) and FLIT-based data transfer. These changes are
essential to meet the increasing bandwidth demands of next-generation
workloads including AI/ML, high-performance computing, and high-speed
storage/networking.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe Gen6 (64 GT/s) link support in kernel PCI subsystem.
Add support for FLIT-based encoding/decoding awareness in PCIe stack.
Enhance PCIe Advanced Error Reporting (AER) to handle FEC and CRC events.
Update drivers (NVMe, NIC, GPU/accelerators) for Gen6 compatibility and performance tuning.
Ensure compatibility with PCIe Gen6 retimers/redrivers and link training sequences
Validate backward compatibility with Gen5/Gen4 devices.
Enable firmware (BIOS/UEFI) integration for Gen6 link training and capability exposure.
Provide tools/logging support for debugging Gen6 link health and error conditions.
Document configuration, tuning, and validation workflows for PCIe Gen6 platforms.
Business Justication:
- Enables next-generation high-bandwidth workloads (AI/ML, HPC, hyperscale storage).
- Provides up to 2× bandwidth improvement over PCIe Gen5, improving system performance.
- Enhances platform reliability with FEC and improved error handling mechanisms.
- Ensures competitiveness with emerging server platforms adopting PCIe Gen6.
- Supports future-proof infrastructure for data centers and enterprise deployments.
- Aligns with upcoming hardware from CPU and accelerator vendors.
References:
PCI-SIG PCIe 6.0 Specification
PCIe Gen6 Architecture Overview (PAM4, FLIT, FEC)
Linux Kernel PCI Subsystem Documentation
NVMe and PCIe Gen6 Ecosystem Whitepapers
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146637
Title:
Request for PCIe Gen6 (64 GT/s) Support
Status in linux package in Ubuntu:
New
Bug description:
PCIe Gen6 introduces a significant advancement in high-speed
interconnect technology by doubling the data rate to 64 GT/s per lane
and adopting new signaling and encoding mechanisms such as PAM4 (Pulse
Amplitude Modulation-4) and FLIT-based data transfer. These changes
are essential to meet the increasing bandwidth demands of next-
generation workloads including AI/ML, high-performance computing, and
high-speed storage/networking.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe Gen6 (64 GT/s) link support in kernel PCI subsystem.
Add support for FLIT-based encoding/decoding awareness in PCIe stack.
Enhance PCIe Advanced Error Reporting (AER) to handle FEC and CRC events.
Update drivers (NVMe, NIC, GPU/accelerators) for Gen6 compatibility and performance tuning.
Ensure compatibility with PCIe Gen6 retimers/redrivers and link training sequences
Validate backward compatibility with Gen5/Gen4 devices.
Enable firmware (BIOS/UEFI) integration for Gen6 link training and capability exposure.
Provide tools/logging support for debugging Gen6 link health and error conditions.
Document configuration, tuning, and validation workflows for PCIe Gen6 platforms.
Business Justication:
- Enables next-generation high-bandwidth workloads (AI/ML, HPC, hyperscale storage).
- Provides up to 2× bandwidth improvement over PCIe Gen5, improving system performance.
- Enhances platform reliability with FEC and improved error handling mechanisms.
- Ensures competitiveness with emerging server platforms adopting PCIe Gen6.
- Supports future-proof infrastructure for data centers and enterprise deployments.
- Aligns with upcoming hardware from CPU and accelerator vendors.
References:
PCI-SIG PCIe 6.0 Specification
PCIe Gen6 Architecture Overview (PAM4, FLIT, FEC)
Linux Kernel PCI Subsystem Documentation
NVMe and PCIe Gen6 Ecosystem Whitepapers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146637/+subscriptions
PCIe Gen6 introduces a significant advancement in high-speed
interconnect technology by doubling the data rate to 64 GT/s per lane
and adopting new signaling and encoding mechanisms such as PAM4 (Pulse
Amplitude Modulation-4) and FLIT-based data transfer. These changes are
essential to meet the increasing bandwidth demands of next-generation
workloads including AI/ML, high-performance computing, and high-speed
storage/networking.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe Gen6 (64 GT/s) link support in kernel PCI subsystem.
Add support for FLIT-based encoding/decoding awareness in PCIe stack.
Enhance PCIe Advanced Error Reporting (AER) to handle FEC and CRC events.
Update drivers (NVMe, NIC, GPU/accelerators) for Gen6 compatibility and performance tuning.
Ensure compatibility with PCIe Gen6 retimers/redrivers and link training sequences
Validate backward compatibility with Gen5/Gen4 devices.
Enable firmware (BIOS/UEFI) integration for Gen6 link training and capability exposure.
Provide tools/logging support for debugging Gen6 link health and error conditions.
Document configuration, tuning, and validation workflows for PCIe Gen6 platforms.
Business Justication:
- Enables next-generation high-bandwidth workloads (AI/ML, HPC, hyperscale storage).
- Provides up to 2× bandwidth improvement over PCIe Gen5, improving system performance.
- Enhances platform reliability with FEC and improved error handling mechanisms.
- Ensures competitiveness with emerging server platforms adopting PCIe Gen6.
- Supports future-proof infrastructure for data centers and enterprise deployments.
- Aligns with upcoming hardware from CPU and accelerator vendors.
References:
PCI-SIG PCIe 6.0 Specification
PCIe Gen6 Architecture Overview (PAM4, FLIT, FEC)
Linux Kernel PCI Subsystem Documentation
NVMe and PCIe Gen6 Ecosystem Whitepapers
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146637
Title:
Request for PCIe Gen6 (64 GT/s) Support
Status in linux package in Ubuntu:
New
Bug description:
PCIe Gen6 introduces a significant advancement in high-speed
interconnect technology by doubling the data rate to 64 GT/s per lane
and adopting new signaling and encoding mechanisms such as PAM4 (Pulse
Amplitude Modulation-4) and FLIT-based data transfer. These changes
are essential to meet the increasing bandwidth demands of next-
generation workloads including AI/ML, high-performance computing, and
high-speed storage/networking.
Feature Request:
Requested details to be enabled on OS:
Enable PCIe Gen6 (64 GT/s) link support in kernel PCI subsystem.
Add support for FLIT-based encoding/decoding awareness in PCIe stack.
Enhance PCIe Advanced Error Reporting (AER) to handle FEC and CRC events.
Update drivers (NVMe, NIC, GPU/accelerators) for Gen6 compatibility and performance tuning.
Ensure compatibility with PCIe Gen6 retimers/redrivers and link training sequences
Validate backward compatibility with Gen5/Gen4 devices.
Enable firmware (BIOS/UEFI) integration for Gen6 link training and capability exposure.
Provide tools/logging support for debugging Gen6 link health and error conditions.
Document configuration, tuning, and validation workflows for PCIe Gen6 platforms.
Business Justication:
- Enables next-generation high-bandwidth workloads (AI/ML, HPC, hyperscale storage).
- Provides up to 2× bandwidth improvement over PCIe Gen5, improving system performance.
- Enhances platform reliability with FEC and improved error handling mechanisms.
- Ensures competitiveness with emerging server platforms adopting PCIe Gen6.
- Supports future-proof infrastructure for data centers and enterprise deployments.
- Aligns with upcoming hardware from CPU and accelerator vendors.
References:
PCI-SIG PCIe 6.0 Specification
PCIe Gen6 Architecture Overview (PAM4, FLIT, FEC)
Linux Kernel PCI Subsystem Documentation
NVMe and PCIe Gen6 Ecosystem Whitepapers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146637/+subscriptions
[Bug 2146621] [NEW] [Dell Ubuntu 26.04]: iSCSI LUN is not detected as a boot LUN or a data LUN
Private bug reported:
Description:
When installing Ubuntu Server 26.04 on a remote iSCSI LUN, the installer fails to detect the remote iSCSI LUN. After installing Ubuntu 26.04 on a local disk and booting into the OS, the remote iSCSI disk is still not detected.
Reproduce Steps:
Boot LUN issue:
1. Attach the Ubuntu Server 26.04 installation image to a Dell PowerEdge R750xs system.
2. Boot from the image and proceed with the installation.
3. During installation, the remote iSCSI LUN is not detected and therefore cannot be selected as a boot LUN.
Data LUN issue:
1. Install Ubuntu Server 26.04 on a local disk on the Dell PowerEdge R750xs system.
2. Boot the system into the installed OS.
3. The remote iSCSI LUN is not detected and does not appear in the output of lsblk.
Configuration:
System: Dell PowerEdge R750xs
OS:https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/resolute-live-server-amd64.iso
NIC adapter: Mellanox ConnectX-6 Dx Dual Port 100GbE QSFP56 Adapter
storage：PowerStore
Expected results:
OS is able to recognize and access the remote iscsi disk
Actual results:
OS fails to detect the remote iscsi disk.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146621
Title:
[Dell Ubuntu 26.04]: iSCSI LUN is not detected as a boot LUN or a data
LUN
Status in linux package in Ubuntu:
New
Bug description:
Description:
When installing Ubuntu Server 26.04 on a remote iSCSI LUN, the installer fails to detect the remote iSCSI LUN. After installing Ubuntu 26.04 on a local disk and booting into the OS, the remote iSCSI disk is still not detected.
Reproduce Steps:
Boot LUN issue:
1. Attach the Ubuntu Server 26.04 installation image to a Dell PowerEdge R750xs system.
2. Boot from the image and proceed with the installation.
3. During installation, the remote iSCSI LUN is not detected and therefore cannot be selected as a boot LUN.
Data LUN issue:
1. Install Ubuntu Server 26.04 on a local disk on the Dell PowerEdge R750xs system.
2. Boot the system into the installed OS.
3. The remote iSCSI LUN is not detected and does not appear in the output of lsblk.
Configuration:
System: Dell PowerEdge R750xs
OS:https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/resolute-live-server-amd64.iso
NIC adapter: Mellanox ConnectX-6 Dx Dual Port 100GbE QSFP56 Adapter
storage：PowerStore
Expected results:
OS is able to recognize and access the remote iscsi disk
Actual results:
OS fails to detect the remote iscsi disk.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146621/+subscriptions
Description:
When installing Ubuntu Server 26.04 on a remote iSCSI LUN, the installer fails to detect the remote iSCSI LUN. After installing Ubuntu 26.04 on a local disk and booting into the OS, the remote iSCSI disk is still not detected.
Reproduce Steps:
Boot LUN issue:
1. Attach the Ubuntu Server 26.04 installation image to a Dell PowerEdge R750xs system.
2. Boot from the image and proceed with the installation.
3. During installation, the remote iSCSI LUN is not detected and therefore cannot be selected as a boot LUN.
Data LUN issue:
1. Install Ubuntu Server 26.04 on a local disk on the Dell PowerEdge R750xs system.
2. Boot the system into the installed OS.
3. The remote iSCSI LUN is not detected and does not appear in the output of lsblk.
Configuration:
System: Dell PowerEdge R750xs
OS:https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/resolute-live-server-amd64.iso
NIC adapter: Mellanox ConnectX-6 Dx Dual Port 100GbE QSFP56 Adapter
storage：PowerStore
Expected results:
OS is able to recognize and access the remote iscsi disk
Actual results:
OS fails to detect the remote iscsi disk.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146621
Title:
[Dell Ubuntu 26.04]: iSCSI LUN is not detected as a boot LUN or a data
LUN
Status in linux package in Ubuntu:
New
Bug description:
Description:
When installing Ubuntu Server 26.04 on a remote iSCSI LUN, the installer fails to detect the remote iSCSI LUN. After installing Ubuntu 26.04 on a local disk and booting into the OS, the remote iSCSI disk is still not detected.
Reproduce Steps:
Boot LUN issue:
1. Attach the Ubuntu Server 26.04 installation image to a Dell PowerEdge R750xs system.
2. Boot from the image and proceed with the installation.
3. During installation, the remote iSCSI LUN is not detected and therefore cannot be selected as a boot LUN.
Data LUN issue:
1. Install Ubuntu Server 26.04 on a local disk on the Dell PowerEdge R750xs system.
2. Boot the system into the installed OS.
3. The remote iSCSI LUN is not detected and does not appear in the output of lsblk.
Configuration:
System: Dell PowerEdge R750xs
OS:https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/resolute-live-server-amd64.iso
NIC adapter: Mellanox ConnectX-6 Dx Dual Port 100GbE QSFP56 Adapter
storage：PowerStore
Expected results:
OS is able to recognize and access the remote iscsi disk
Actual results:
OS fails to detect the remote iscsi disk.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146621/+subscriptions
пятница
[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot
Additional data (resume failure analysis)
Hardware:
- GPU: AMD Radeon R9 380 (Tonga, GCN 3)
- CPU: AMD Ryzen 5 5500
- RAM: 16 GB
- Display: HDMI
Software:
- Kernel: 6.8.0-106-generic
- Driver: amdgpu
- Display server: X11 (issue reproducible), Wayland (no hard failure)
---
Summary:
After suspend/resume, HDMI output is not restored and the system may
freeze under X11.
The issue is reproducible and was not present in Linux 6.3.
---
Key observation:
During resume, the driver fails to read EDID:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
This appears to explain why HDMI output is not restored.
---
Relevant DRM / AMDGPU log excerpt:
[drm] Display Core v3.2.266 initialized on DCE 10.0
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
[drm] Initialized amdgpu 3.57.0 20150101 for 0000:01:00.0
---
Analysis:
- The failure occurs during display reinitialization after resume
- EDID read failure prevents proper HDMI modeset
- This aligns with the observed "no signal" condition
Behavior differences:
- deep sleep:
- full GPU/display reinitialization
- leads to EDID failure and system instability
- s2idle:
- partial resume
- avoids full lockup but display may still be inconsistent
This suggests the issue is in the display resume path, possibly
involving:
- DC state restore
- HDMI link training
- DDC/EDID communication
- atomic modeset reconstruction
---
Conclusion:
This is likely a regression in the AMDGPU display resume path, where
EDID read fails after resume, preventing HDMI output from being
restored.
---
Additional notes:
This issue was bisected between Linux 6.3 (good) and 6.4 (bad), with the
transition point identified as a KVM merge commit. While not directly
related to AMDGPU, it may have indirectly exposed this issue via
timing/order changes.
---
If needed, I can provide:
- full journalctl logs
- full bisect log
- additional testing (kernel params, debug options)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
Hardware:
- GPU: AMD Radeon R9 380 (Tonga, GCN 3)
- CPU: AMD Ryzen 5 5500
- RAM: 16 GB
- Display: HDMI
Software:
- Kernel: 6.8.0-106-generic
- Driver: amdgpu
- Display server: X11 (issue reproducible), Wayland (no hard failure)
---
Summary:
After suspend/resume, HDMI output is not restored and the system may
freeze under X11.
The issue is reproducible and was not present in Linux 6.3.
---
Key observation:
During resume, the driver fails to read EDID:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
This appears to explain why HDMI output is not restored.
---
Relevant DRM / AMDGPU log excerpt:
[drm] Display Core v3.2.266 initialized on DCE 10.0
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
[drm] Initialized amdgpu 3.57.0 20150101 for 0000:01:00.0
---
Analysis:
- The failure occurs during display reinitialization after resume
- EDID read failure prevents proper HDMI modeset
- This aligns with the observed "no signal" condition
Behavior differences:
- deep sleep:
- full GPU/display reinitialization
- leads to EDID failure and system instability
- s2idle:
- partial resume
- avoids full lockup but display may still be inconsistent
This suggests the issue is in the display resume path, possibly
involving:
- DC state restore
- HDMI link training
- DDC/EDID communication
- atomic modeset reconstruction
---
Conclusion:
This is likely a regression in the AMDGPU display resume path, where
EDID read fails after resume, preventing HDMI output from being
restored.
---
Additional notes:
This issue was bisected between Linux 6.3 (good) and 6.4 (bad), with the
transition point identified as a KVM merge commit. While not directly
related to AMDGPU, it may have indirectly exposed this issue via
timing/order changes.
---
If needed, I can provide:
- full journalctl logs
- full bisect log
- additional testing (kernel params, debug options)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142389
Title:
amdgpu (R9 380) fails to resume from suspend (deep sleep) – black
screen, requires hard reboot
Status in linux package in Ubuntu:
New
Bug description:
AMDGPU suspend → display black / no video after resume on Radeon R9
380 (No EDID read)
Summary:
After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video.
Steps to reproduce:
Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17).
Suspend system (e.g., via GNOME "Suspend").
Wait short period.
Attempt to resume (mouse/keyboard).
System wakes but display either shows garbled video or no output.
Observed behavior:
System appears not crashed (fans/LEDs/keyboard continue).
Screen stays black or displays remnants but no usable video.
Sometimes resume works, sometimes fails.
Relevant log excerpt:
amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read.
Hardware:
Motherboard: Gigabyte B450 AORUS PRO WIFI
CPU: AMD Ryzen 5 5500
GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver)
Software environment:
Zorin OS 18 Core (Ubuntu 24.10 base)
kernel: 6.17.0-14-generic
X11 session
Workaround currently applied:
Suspend disabled. System remains stable without suspend.
Note: Bug appears related to video resume rather than system freeze;
display subsystem (EDID handshake) may fail after suspend.
Additional info:
Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
[Bug 2146521] Re: [Resolute Mar 26 beta] Boot hang / IOMMU Fault on Ryzen 9800X3D + RX 9070 (Gigabyte B650M DS3H) - Missing IOMMU 0x0 Mapping Fix
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146521
Title:
[Resolute Mar 26 beta] Boot hang / IOMMU Fault on Ryzen 9800X3D + RX
9070 (Gigabyte B650M DS3H) - Missing IOMMU 0x0 Mapping Fix
Status in linux package in Ubuntu:
New
Bug description:
Description:
The Ubuntu 26.04 (Resolute Raccoon) Beta ISO (Kernel 7.0.0-7-generic) fails to boot on my system featuring the Ryzen 7 9800X3D and RX 9070, specifically on the Gigabyte B650M DS3H motherboard. The boot process hangs indefinitely during IOMMU initialization.
Hardware Environment:
CPU: AMD Ryzen 7 9800X3D
GPU: AMD Radeon RX 9070 (RDNA 4)
Motherboard: Gigabyte B650M DS3H (Latest BIOS)
Status: Secure Boot Enabled, IOMMU Enabled in UEFI.
Problem Details:
This is a known regression from 6.19 where the IOMMU fails to correctly handle the 0x0 IOVA mapping, leading to an IO_PAGE_FAULT and a subsequent kernel panic or hard hang.
I have previously tracked and verified this issue in both Fedora and
Arch:
Fedora: I reported in Bugzilla (Kernel 6.19 Test Week). I
coordinated with Justin Forbes and the Fedora QA team during the
Fedora Blocker call to have this patched in 6.19.8-200 build:
https://bugzilla.redhat.com/show_bug.cgi?id=2443049
Arch: I reported and verified there as well.
Other users in Fedora and CachyOS with various AMD hardware had the
issue and the patch fixed it.
The Solution:
The specific fix is is authored by Antheas Kapenekakis:
https://lkml.org/lkml/2026/2/27/464
I believe this might have been merged in 7.0RC5 (after speaking with a
NixOS kernel maintainer who mentioned it), but if not would it be
possible to verify that this was indeed merged and make sure it does
land in Ubuntu as well?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146521/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146521
Title:
[Resolute Mar 26 beta] Boot hang / IOMMU Fault on Ryzen 9800X3D + RX
9070 (Gigabyte B650M DS3H) - Missing IOMMU 0x0 Mapping Fix
Status in linux package in Ubuntu:
New
Bug description:
Description:
The Ubuntu 26.04 (Resolute Raccoon) Beta ISO (Kernel 7.0.0-7-generic) fails to boot on my system featuring the Ryzen 7 9800X3D and RX 9070, specifically on the Gigabyte B650M DS3H motherboard. The boot process hangs indefinitely during IOMMU initialization.
Hardware Environment:
CPU: AMD Ryzen 7 9800X3D
GPU: AMD Radeon RX 9070 (RDNA 4)
Motherboard: Gigabyte B650M DS3H (Latest BIOS)
Status: Secure Boot Enabled, IOMMU Enabled in UEFI.
Problem Details:
This is a known regression from 6.19 where the IOMMU fails to correctly handle the 0x0 IOVA mapping, leading to an IO_PAGE_FAULT and a subsequent kernel panic or hard hang.
I have previously tracked and verified this issue in both Fedora and
Arch:
Fedora: I reported in Bugzilla (Kernel 6.19 Test Week). I
coordinated with Justin Forbes and the Fedora QA team during the
Fedora Blocker call to have this patched in 6.19.8-200 build:
https://bugzilla.redhat.com/show_bug.cgi?id=2443049
Arch: I reported and verified there as well.
Other users in Fedora and CachyOS with various AMD hardware had the
issue and the patch fixed it.
The Solution:
The specific fix is is authored by Antheas Kapenekakis:
https://lkml.org/lkml/2026/2/27/464
I believe this might have been merged in 7.0RC5 (after speaking with a
NixOS kernel maintainer who mentioned it), but if not would it be
possible to verify that this was indeed merged and make sure it does
land in Ubuntu as well?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146521/+subscriptions
[Bug 2146536] Re: [REGRESSION] Intel XMM7360 (Fibocom L850) modem not detected / SIM missing on Ubuntu 25.04+
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146536
Title:
[REGRESSION] Intel XMM7360 (Fibocom L850) modem not detected / SIM
missing on Ubuntu 25.04+
Status in linux package in Ubuntu:
New
Bug description:
Hardware:
Laptop: HP EliteBook 830 G8
Modem: Intel XMM7360 (Fibocom L850 LTE)
PCI ID: 8086:7360
Firmware: HP OEM (whitelisted firmware, not generic, BIOS-restricted)
Summary of the problem:
This appears to be a regression in the in-kernel iosm driver affecting Intel XMM7360-based modems with OEM HP firmware.
The modem worked correctly on Ubuntu 24.10 with the stock kernel and iosm driver.
Starting from Ubuntu 25.04, the SIM is no longer detected.
Starting from Ubuntu 25.10, the modem is not properly initialized and becomes unusable.
The issue is reproducible and persists across reboots.
Regression range:
Last known working: Ubuntu 24.10
First broken (SIM not detected): Ubuntu 25.04
Further regression (modem unusable): Ubuntu 25.10
Detailed description:
On affected systems, the modem is detected on the PCI bus, but fails during initialization when handled by the iosm driver.
ModemManager reports:
state: failed
failed reason: sim-missing
AT command interface is partially functional, but SIM access is
broken:
AT responds correctly
AT+CFUN works
AT+CPIN? returns ERROR
AT+CREG reports not registered (0,0)
Additionally:
No /dev/cdc-wdm device is created
ModemManager cannot fully manage the modem
The device does not transition into an operational state
This suggests that the iosm driver fails to properly initialize the
modem or establish the control channel required for SIM access.
Workaround:
The modem becomes operational when using an out-of-tree driver:
https://github.com/xmm7360/xmm7360-pci
Steps:
make
sudo insmod xmm7360.ko
With this driver:
The modem initializes correctly
AT interface works
The device reports readiness:
[ 4694.634478] xmm7360 0000:55:00.0: modem is ready
This strongly indicates that the hardware and firmware are functional,
and that the regression is specific to the iosm driver or related
kernel components.
Steps to reproduce:
Boot Ubuntu 25.04 or 25.10
Ensure iosm driver is used (default kernel behavior)
Run:
mmcli -L
mmcli -m 0 --enable
Observed result:
Modem enters failed state
SIM is reported as missing
Device remains unusable
Expected result:
Modem should initialize correctly
SIM should be detected
ModemManager should be able to control the modem
Network registration should be possible
ModemManager output:
/org/freedesktop/ModemManager1/Modem/0 [Fibocom] L850 LTE Module
Status | state: failed
| failed reason: sim-missing
Full mmcli output:
/org/freedesktop/ModemManager1/Modem/0 [Fibocom] L850 LTE Module
-----------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 5c8833d8b4341b0bf13dc1c1d4268cb19c62be1f
-----------------------------
Hardware | manufacturer: Fibocom
| model: L850 LTE Module
| firmware revision: 18500.5001.00.05.27.30
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 863989052417938
-----------------------------
System | device: /sys/devices/pci0000:00/0000:00:1c.0/0000:55:00.0
| drivers: xmm7360
| plugin: generic
| primary port: ttyXMM2
| ports: ttyXMM1 (at), ttyXMM2 (at), wwan0 (net)
-----------------------------
Status | state: failed
| failed reason: sim-missing
| power state: on
AT interaction:
AT
OK
AT+CFUN=1
OK
AT+CPIN?
ERROR
AT+CPIN=?
OK
AT+CREG?
+CREG: 0,0
Direct serial access test (picocom):
sudo picocom -b 115200 /dev/ttyXMM1
AT+CFUN=4
OK
AT+CFUN=1
OK
AT+CPIN?
ERROR
dmesg (relevant part):
[ 4694.634478] xmm7360 0000:55:00.0: modem is ready
Also no MBIM control device present:
ls /dev/cdc-wdm*
ls: cannot access '/dev/cdc-wdm*': No such file or directory
PCI device detection:
lspci -nn | grep -i xmm
55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem [8086:7360] (rev 01)
RF state:
rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
System information:
uname -a
Linux elitebook-hp 6.17.0-19-generic #19-Ubuntu SMP x86_64 GNU/Linux
lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 25.10
Release: 25.10
Codename: unknown
Additional notes:
This device uses HP OEM firmware and is BIOS-whitelisted
Replacing firmware or modem is not possible due to platform restrictions
The issue is not hardware-related (confirmed by working alternative driver)
Likely root cause: regression in iosm driver or related subsystem between kernel versions used in Ubuntu 24.10 and 25.04+
Additional testing with alternative driver forks:
An attempt was made to use alternative forks of the xmm7360 out-of-tree driver.
However, they did not provide a complete solution for this platform.
Reason:
HP OEM firmware differs from generic firmware expected by these drivers
The modem does not expose a standard MBIM control interface (/dev/cdc-wdm)
Some forks rely on assumptions about firmware behavior that do not hold for HP-whitelisted devices
As a result:
Partial initialization may occur
SIM access and full modem functionality remain unreliable or broken
Therefore, using out-of-tree drivers is not a viable long-term
solution.
Primary goal:
Restore full functionality using the in-kernel iosm driver.
Request:
Please investigate regression in iosm driver affecting Intel XMM7360 (Fibocom L850) with OEM firmware.
With regards,
Stanislav
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-19-generic 6.17.0-19.19
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 27 12:29:40 2026
InstallationDate: Installed on 2025-09-28 (180 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: HP HP ELITEBOOK 830 G8
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=6a23b845-81bc-47b1-81af-ca4c9a7bd9c8 ro quiet splash resume=/dev/nvme0n1p5 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-10-10 (168 days ago)
dmi.bios.date: 11/06/2025
dmi.bios.release: 23.0
dmi.bios.vendor: HP
dmi.bios.version: T76 Ver. 01.23.00
dmi.board.name: 880D
dmi.board.vendor: HP
dmi.board.version: KBC Version 30.57.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 48.87
dmi.modalias: dmi:bvnHP:bvrT76Ver.01.23.00:bd11/06/2025:br23.0:efr48.87:svnHP:pnHPELITEBOOK830G8:pvrSBKPFV3:rvnHP:rn880D:rvrKBCVersion30.57.00:cvnHP:ct10:cvr:sku2Y2R9EA#ACB:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP ELITEBOOK 830 G8
dmi.product.sku: 2Y2R9EA#ACB
dmi.product.version: SBKPFV3
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146536/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146536
Title:
[REGRESSION] Intel XMM7360 (Fibocom L850) modem not detected / SIM
missing on Ubuntu 25.04+
Status in linux package in Ubuntu:
New
Bug description:
Hardware:
Laptop: HP EliteBook 830 G8
Modem: Intel XMM7360 (Fibocom L850 LTE)
PCI ID: 8086:7360
Firmware: HP OEM (whitelisted firmware, not generic, BIOS-restricted)
Summary of the problem:
This appears to be a regression in the in-kernel iosm driver affecting Intel XMM7360-based modems with OEM HP firmware.
The modem worked correctly on Ubuntu 24.10 with the stock kernel and iosm driver.
Starting from Ubuntu 25.04, the SIM is no longer detected.
Starting from Ubuntu 25.10, the modem is not properly initialized and becomes unusable.
The issue is reproducible and persists across reboots.
Regression range:
Last known working: Ubuntu 24.10
First broken (SIM not detected): Ubuntu 25.04
Further regression (modem unusable): Ubuntu 25.10
Detailed description:
On affected systems, the modem is detected on the PCI bus, but fails during initialization when handled by the iosm driver.
ModemManager reports:
state: failed
failed reason: sim-missing
AT command interface is partially functional, but SIM access is
broken:
AT responds correctly
AT+CFUN works
AT+CPIN? returns ERROR
AT+CREG reports not registered (0,0)
Additionally:
No /dev/cdc-wdm device is created
ModemManager cannot fully manage the modem
The device does not transition into an operational state
This suggests that the iosm driver fails to properly initialize the
modem or establish the control channel required for SIM access.
Workaround:
The modem becomes operational when using an out-of-tree driver:
https://github.com/xmm7360/xmm7360-pci
Steps:
make
sudo insmod xmm7360.ko
With this driver:
The modem initializes correctly
AT interface works
The device reports readiness:
[ 4694.634478] xmm7360 0000:55:00.0: modem is ready
This strongly indicates that the hardware and firmware are functional,
and that the regression is specific to the iosm driver or related
kernel components.
Steps to reproduce:
Boot Ubuntu 25.04 or 25.10
Ensure iosm driver is used (default kernel behavior)
Run:
mmcli -L
mmcli -m 0 --enable
Observed result:
Modem enters failed state
SIM is reported as missing
Device remains unusable
Expected result:
Modem should initialize correctly
SIM should be detected
ModemManager should be able to control the modem
Network registration should be possible
ModemManager output:
/org/freedesktop/ModemManager1/Modem/0 [Fibocom] L850 LTE Module
Status | state: failed
| failed reason: sim-missing
Full mmcli output:
/org/freedesktop/ModemManager1/Modem/0 [Fibocom] L850 LTE Module
-----------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 5c8833d8b4341b0bf13dc1c1d4268cb19c62be1f
-----------------------------
Hardware | manufacturer: Fibocom
| model: L850 LTE Module
| firmware revision: 18500.5001.00.05.27.30
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 863989052417938
-----------------------------
System | device: /sys/devices/pci0000:00/0000:00:1c.0/0000:55:00.0
| drivers: xmm7360
| plugin: generic
| primary port: ttyXMM2
| ports: ttyXMM1 (at), ttyXMM2 (at), wwan0 (net)
-----------------------------
Status | state: failed
| failed reason: sim-missing
| power state: on
AT interaction:
AT
OK
AT+CFUN=1
OK
AT+CPIN?
ERROR
AT+CPIN=?
OK
AT+CREG?
+CREG: 0,0
Direct serial access test (picocom):
sudo picocom -b 115200 /dev/ttyXMM1
AT+CFUN=4
OK
AT+CFUN=1
OK
AT+CPIN?
ERROR
dmesg (relevant part):
[ 4694.634478] xmm7360 0000:55:00.0: modem is ready
Also no MBIM control device present:
ls /dev/cdc-wdm*
ls: cannot access '/dev/cdc-wdm*': No such file or directory
PCI device detection:
lspci -nn | grep -i xmm
55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem [8086:7360] (rev 01)
RF state:
rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
System information:
uname -a
Linux elitebook-hp 6.17.0-19-generic #19-Ubuntu SMP x86_64 GNU/Linux
lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 25.10
Release: 25.10
Codename: unknown
Additional notes:
This device uses HP OEM firmware and is BIOS-whitelisted
Replacing firmware or modem is not possible due to platform restrictions
The issue is not hardware-related (confirmed by working alternative driver)
Likely root cause: regression in iosm driver or related subsystem between kernel versions used in Ubuntu 24.10 and 25.04+
Additional testing with alternative driver forks:
An attempt was made to use alternative forks of the xmm7360 out-of-tree driver.
However, they did not provide a complete solution for this platform.
Reason:
HP OEM firmware differs from generic firmware expected by these drivers
The modem does not expose a standard MBIM control interface (/dev/cdc-wdm)
Some forks rely on assumptions about firmware behavior that do not hold for HP-whitelisted devices
As a result:
Partial initialization may occur
SIM access and full modem functionality remain unreliable or broken
Therefore, using out-of-tree drivers is not a viable long-term
solution.
Primary goal:
Restore full functionality using the in-kernel iosm driver.
Request:
Please investigate regression in iosm driver affecting Intel XMM7360 (Fibocom L850) with OEM firmware.
With regards,
Stanislav
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-19-generic 6.17.0-19.19
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 27 12:29:40 2026
InstallationDate: Installed on 2025-09-28 (180 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: HP HP ELITEBOOK 830 G8
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=6a23b845-81bc-47b1-81af-ca4c9a7bd9c8 ro quiet splash resume=/dev/nvme0n1p5 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-10-10 (168 days ago)
dmi.bios.date: 11/06/2025
dmi.bios.release: 23.0
dmi.bios.vendor: HP
dmi.bios.version: T76 Ver. 01.23.00
dmi.board.name: 880D
dmi.board.vendor: HP
dmi.board.version: KBC Version 30.57.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 48.87
dmi.modalias: dmi:bvnHP:bvrT76Ver.01.23.00:bd11/06/2025:br23.0:efr48.87:svnHP:pnHPELITEBOOK830G8:pvrSBKPFV3:rvnHP:rn880D:rvrKBCVersion30.57.00:cvnHP:ct10:cvr:sku2Y2R9EA#ACB:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP ELITEBOOK 830 G8
dmi.product.sku: 2Y2R9EA#ACB
dmi.product.version: SBKPFV3
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146536/+subscriptions
[Bug 2146538] Re: Kernel image build is not reproducible due to uname
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146538
Title:
Kernel image build is not reproducible due to uname
Status in linux package in Ubuntu:
New
Bug description:
Dear linux package maintainers,
A build of the linux-image-unsigned performed by launchpad/Ubuntu can
currently not be fully reproduced by a local build.
One of the issues is that the kernel build embeds information about
the build system and time in the uname string:
For example:
```
sudo file /boot/vmlinuz-6.19.0-6-generic
/boot/vmlinuz-6.19.0-6-generic: Linux kernel x86 boot executable, bzImage, version 6.19.0-6-generic (buildd@lcy02-amd64-071) #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026, RO-rootFS, Normal VGA, setup size 512*39, syssize 0x104200, jump 0x26c 0x8cd88ec0fc8cd239 instruction, protocol 2.15, from protected-mode code at offset 0x2cc 0x1008b9f bytes ZST compressed, relocatable, handover offset 0x1035640, legacy 64-bit entry point, can be above 4G, 32-bit EFI handoff entry point, 64-bit EFI handoff entry point, EFI kexec boot support, xloadflags bit 5, max cmdline size 2047, init_size 0x44ba000
uname --all
Linux ubuntu 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
```
The `buildd@lcy02-amd64-071` depend on the build machine, and the date `Wed Feb 18 15:48:21 UTC 2026` is **not** set based on the SOURCE_DATE_EPOCH variable but set depending on when the build is performed.
Debian solves this by setting the following variables during the build, it would be nice if the Ubuntu kernels could follow this:
KBUILD_BUILD_USER: for example to `kernel-team`
KBUILD_BUILD_HOST: for example to `lists.ubuntu.com`
KBUILD_BUILD_TIMESTAMP: to a date based on or derived from SOURCE_DATE_EPOCH
On Debian this results in an output of `file` similar to the
following, and allows the package builds to be reproduced:
```
/usr/lib/modules/6.18.5+deb14-amd64/vmlinuz: Linux kernel x86 boot executable, bzImage, version 6.18.5+deb14-amd64 (debian-kernel@lists.debian.org) #1 SMP PREEMPT_DYNAMIC Debian 6.18.5-1 (2026-01-16)
```
<https://sources.debian.org/src/linux/6.19.8-1/debian/rules.real#L43>:
```
SOURCE_DATE_UTC_ISO := $(shell date -u -d '@$(SOURCE_DATE_EPOCH)' +%Y-%m-%d)
...
setup_env += DISTRIBUTION_OFFICIAL_BUILD=1 DISTRIBUTOR="$(DEB_VENDOR)" DISTRIBUTION_VERSION="$(SOURCEVERSION)" KBUILD_BUILD_TIMESTAMP="@$(SOURCE_DATE_EPOCH)" KBUILD_BUILD_VERSION_TIMESTAMP="$(DEB_VENDOR) $(SOURCEVERSION) ($(SOURCE_DATE_UTC_ISO))" KBUILD_BUILD_USER="$(word 1,$(subst @, ,$(MAINTAINER)))" KBUILD_BUILD_HOST="$(word 2,$(subst @, ,$(MAINTAINER)))"
```
It would be nice if these 3 variables could be set similarly to
Debian, allowing the Ubuntu package build to be reproduced locally.
Thank you,
Jonathan Hettwer
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-unsigned-7.0.0-10-generic (not installed)
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 24 18:02 seq
crw-rw---- 1 root audio 116, 33 Mar 24 18:02 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20260221
CloudSubPlatform: config-disk (/dev/sr0)
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Thu Mar 26 16:43:11 2026
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
PciMultimedia:
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, user)
SHELL=/bin/bash
TERM=tmux-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-6-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
firmware-sof N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
acpidump:
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146538/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146538
Title:
Kernel image build is not reproducible due to uname
Status in linux package in Ubuntu:
New
Bug description:
Dear linux package maintainers,
A build of the linux-image-unsigned performed by launchpad/Ubuntu can
currently not be fully reproduced by a local build.
One of the issues is that the kernel build embeds information about
the build system and time in the uname string:
For example:
```
sudo file /boot/vmlinuz-6.19.0-6-generic
/boot/vmlinuz-6.19.0-6-generic: Linux kernel x86 boot executable, bzImage, version 6.19.0-6-generic (buildd@lcy02-amd64-071) #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026, RO-rootFS, Normal VGA, setup size 512*39, syssize 0x104200, jump 0x26c 0x8cd88ec0fc8cd239 instruction, protocol 2.15, from protected-mode code at offset 0x2cc 0x1008b9f bytes ZST compressed, relocatable, handover offset 0x1035640, legacy 64-bit entry point, can be above 4G, 32-bit EFI handoff entry point, 64-bit EFI handoff entry point, EFI kexec boot support, xloadflags bit 5, max cmdline size 2047, init_size 0x44ba000
uname --all
Linux ubuntu 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
```
The `buildd@lcy02-amd64-071` depend on the build machine, and the date `Wed Feb 18 15:48:21 UTC 2026` is **not** set based on the SOURCE_DATE_EPOCH variable but set depending on when the build is performed.
Debian solves this by setting the following variables during the build, it would be nice if the Ubuntu kernels could follow this:
KBUILD_BUILD_USER: for example to `kernel-team`
KBUILD_BUILD_HOST: for example to `lists.ubuntu.com`
KBUILD_BUILD_TIMESTAMP: to a date based on or derived from SOURCE_DATE_EPOCH
On Debian this results in an output of `file` similar to the
following, and allows the package builds to be reproduced:
```
/usr/lib/modules/6.18.5+deb14-amd64/vmlinuz: Linux kernel x86 boot executable, bzImage, version 6.18.5+deb14-amd64 (debian-kernel@lists.debian.org) #1 SMP PREEMPT_DYNAMIC Debian 6.18.5-1 (2026-01-16)
```
<https://sources.debian.org/src/linux/6.19.8-1/debian/rules.real#L43>:
```
SOURCE_DATE_UTC_ISO := $(shell date -u -d '@$(SOURCE_DATE_EPOCH)' +%Y-%m-%d)
...
setup_env += DISTRIBUTION_OFFICIAL_BUILD=1 DISTRIBUTOR="$(DEB_VENDOR)" DISTRIBUTION_VERSION="$(SOURCEVERSION)" KBUILD_BUILD_TIMESTAMP="@$(SOURCE_DATE_EPOCH)" KBUILD_BUILD_VERSION_TIMESTAMP="$(DEB_VENDOR) $(SOURCEVERSION) ($(SOURCE_DATE_UTC_ISO))" KBUILD_BUILD_USER="$(word 1,$(subst @, ,$(MAINTAINER)))" KBUILD_BUILD_HOST="$(word 2,$(subst @, ,$(MAINTAINER)))"
```
It would be nice if these 3 variables could be set similarly to
Debian, allowing the Ubuntu package build to be reproduced locally.
Thank you,
Jonathan Hettwer
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-unsigned-7.0.0-10-generic (not installed)
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 24 18:02 seq
crw-rw---- 1 root audio 116, 33 Mar 24 18:02 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20260221
CloudSubPlatform: config-disk (/dev/sr0)
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Thu Mar 26 16:43:11 2026
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
PciMultimedia:
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, user)
SHELL=/bin/bash
TERM=tmux-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-6-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
firmware-sof N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
acpidump:
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146538/+subscriptions
[Bug 2146586] Re: Resolute 7.0.0-10-generic warnings prevent GUI starting on Framework 13 AMD
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146586
Title:
Resolute 7.0.0-10-generic warnings prevent GUI starting on Framework
13 AMD
Status in linux package in Ubuntu:
New
Bug description:
Framework Laptop 13 (AMD Ryzen 7040 Series) experiences kernel
warnings on boot, which causes the GUI to fail to start. This issue
occurs most of the time, but 1 in 20 (ish) startups do succeed.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-10-generic 7.0.0-10.10
ProcVersionSignature: Ubuntu 7.0.0-10.10-generic 7.0.0-rc4
Uname: Linux 7.0.0-10-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.33.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: henry 4194 F.... wireplumber
/dev/snd/controlC0: henry 4194 F.... wireplumber
/dev/snd/seq: henry 4187 F.... pipewire
CasperMD5CheckResult: unknown
Date: Fri Mar 27 11:50:51 2026
InstallationDate: Installed on 2025-06-14 (286 days ago)
InstallationMedia: Kubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
IwDevWlp1s0Link: Not connected.
MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-10-generic root=UUID=390ed220-e5af-4dea-afa8-2e7eb26e2c1f ro quiet cryptdevice=UUID=a6c53636-e990-4739-ad45-c6b74786713f:luks-a6c53636-e990-4739-ad45-c6b74786713f root=/dev/mapper/luks-a6c53636-e990-4739-ad45-c6b74786713f splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-03-16 (11 days ago)
dmi.bios.date: 01/08/2026
dmi.bios.release: 3.18
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.18
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA751110010
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.18:bd01/08/2026:br3.18:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:pfaLaptop:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146586/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146586
Title:
Resolute 7.0.0-10-generic warnings prevent GUI starting on Framework
13 AMD
Status in linux package in Ubuntu:
New
Bug description:
Framework Laptop 13 (AMD Ryzen 7040 Series) experiences kernel
warnings on boot, which causes the GUI to fail to start. This issue
occurs most of the time, but 1 in 20 (ish) startups do succeed.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-10-generic 7.0.0-10.10
ProcVersionSignature: Ubuntu 7.0.0-10.10-generic 7.0.0-rc4
Uname: Linux 7.0.0-10-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.33.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: henry 4194 F.... wireplumber
/dev/snd/controlC0: henry 4194 F.... wireplumber
/dev/snd/seq: henry 4187 F.... pipewire
CasperMD5CheckResult: unknown
Date: Fri Mar 27 11:50:51 2026
InstallationDate: Installed on 2025-06-14 (286 days ago)
InstallationMedia: Kubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
IwDevWlp1s0Link: Not connected.
MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-10-generic root=UUID=390ed220-e5af-4dea-afa8-2e7eb26e2c1f ro quiet cryptdevice=UUID=a6c53636-e990-4739-ad45-c6b74786713f:luks-a6c53636-e990-4739-ad45-c6b74786713f root=/dev/mapper/luks-a6c53636-e990-4739-ad45-c6b74786713f splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-03-16 (11 days ago)
dmi.bios.date: 01/08/2026
dmi.bios.release: 3.18
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.18
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA751110010
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.18:bd01/08/2026:br3.18:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:pfaLaptop:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146586/+subscriptions
[Bug 2146606] Re: Regression: NVMe "Invalid Field in Command" errors and instability on Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146606
Title:
Regression: NVMe "Invalid Field in Command" errors and instability on
Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17
Status in linux package in Ubuntu:
New
Bug description:
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146606/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146606
Title:
Regression: NVMe "Invalid Field in Command" errors and instability on
Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17
Status in linux package in Ubuntu:
New
Bug description:
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146606/+subscriptions
[Bug 2146517] Re: ov08x40 module mounted upside down on a certain DELL platforms
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146517
Title:
ov08x40 module mounted upside down on a certain DELL platforms
Status in ipu6-drivers package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Noble:
Won't Fix
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Triaged
Status in ipu6-drivers source package in Questing:
Won't Fix
Status in linux source package in Questing:
Won't Fix
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in ipu6-drivers source package in Resolute:
Triaged
Status in linux source package in Resolute:
Triaged
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
Proposed fix in https://github.com/intel/ipu6-drivers/pull/432/, which
requires updates in the dkms and in the in-tree kernel ipu-bridge
driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2146517/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146517
Title:
ov08x40 module mounted upside down on a certain DELL platforms
Status in ipu6-drivers package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in ipu6-drivers source package in Noble:
Won't Fix
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Triaged
Status in ipu6-drivers source package in Questing:
Won't Fix
Status in linux source package in Questing:
Won't Fix
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in ipu6-drivers source package in Resolute:
Triaged
Status in linux source package in Resolute:
Triaged
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
Proposed fix in https://github.com/intel/ipu6-drivers/pull/432/, which
requires updates in the dkms and in the in-tree kernel ipu-bridge
driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2146517/+subscriptions
[Bug 2146606] [NEW] Regression: NVMe "Invalid Field in Command" errors and instability on Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17
Public bug reported:
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Output from smartctl -a /dev/nvme0"
https://bugs.launchpad.net/bugs/2146606/+attachment/5956340/+files/report.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146606
Title:
Regression: NVMe "Invalid Field in Command" errors and instability on
Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17
Status in linux package in Ubuntu:
New
Bug description:
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146606/+subscriptions
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Output from smartctl -a /dev/nvme0"
https://bugs.launchpad.net/bugs/2146606/+attachment/5956340/+files/report.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146606
Title:
Regression: NVMe "Invalid Field in Command" errors and instability on
Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17
Status in linux package in Ubuntu:
New
Bug description:
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146606/+subscriptions
Подписаться на:
Комментарии (Atom)