Consult /var/lib/dkms/nvidia/590.48.01/build/make.log
---------------------------------
Please attach that file. If it contains a lot of errors that say "naked
return found in MITIGATION_RETHUNK build", then it's a duplicate of bug
2141316
"After purging all the nvidia-related packages with sudo apt remove --purge '^nvidia-.*', no configuration errors remain, but the 6.19 kernel still crashes on load."
Did you reinstall the linux-image-6.19.0-3-generic package after removing the nvidia ones?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141475
Title:
6.19 kernel fails to load, possibly because of nvidia configuration
issue
Status in linux package in Ubuntu:
Incomplete
Bug description:
On ubuntu 26.04, I upgraded to kernel 6.19 with nvidia-driver-590-open installed. I got configuration errors, and the 6.19 kernel failed to load.
After purging all the nvidia-related packages with sudo apt remove --purge '^nvidia-.*', no configuration errors remain, but the 6.19 kernel still crashes on load.
This issue appears with the nvidia-driver-580-open driver as well, so I think this is a kernel issue and not an nvidia issue.
Kernel 6.18 works fine with nvidia drivers.
This is what I get with each initramfs attempt when the nvidia driver
is installed:
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)… done.
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-modeset.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-drm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-uvm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod… done.
Building initial module nvidia/590.48.01 for 6.19.0-3-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
dpkg: error processing package nvidia-dkms-590-open (–configure):
installed nvidia-dkms-590-open package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-590-open:
nvidia-driver-590-open depends on nvidia-dkms-590-open (<= 590.48.01-1); however:
Package nvidia-dkms-590-open is not configured yet.
nvidia-driver-590-open depends on nvidia-dkms-590-open (>= 590.48.01); however:
Package nvidia-dkms-590-open is not configured yet.
dpkg: error processing package nvidia-driver-590-open (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for linu
x-image-6.19.0-3-generic (6.19.0-3.3+1) …
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-3-generic (x86_64)
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
Autoinstall on 6.19.0-3-generic failed for module(s) nvidia(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.19.0-3-generic (–configure):
installed linux-image-6.19.0-3-generic package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.150ubuntu7) …
update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic
Errors were encountered while processing:
nvidia-dkms-590-open
nvidia-driver-590-open
linux-image-6.19.0-3-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-3-generic 6.19.0-3.3+1
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 10 22:28:57 2026
InstallationDate: Installed on 2022-01-31 (1471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
MachineType: ASUS System Product Name
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.18.0-9-generic root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-07 (3 days ago)
dmi.bios.date: 12/03/2024
dmi.bios.release: 41.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4101
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd12/03/2024:br41.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141475/+subscriptions
вторник
[Bug 2141222] Re: Displayport not proper working with linux kernel 6.17.0-14
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141222
Title:
Displayport not proper working with linux kernel 6.17.0-14
Status in linux package in Ubuntu:
New
Bug description:
After upgrading to linux kernel 6.17.0-14 the Displayport of my ATI Ellesmere-GPU is not working anylonger. During the boot process the Linux Mint symbol is visible and afterwards my 2 monitors doesn't get a signal and are going to sleep (they are connected by one Displayport cable and the 2nd monitor is connected to the 1st). Looks like rest of the system works normal since short press of the power button shutsdown the system like expected.
By going back to kernel 6.14.0-37 everything works like expected again.
Output of "cat /proc/version_signature > version.log" - but this is not the affected kernel, this is the version which I'm currently using since it's working:
Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Output of "sudo lspci -vnvn > lspci-vnvn.log" see attached.
'lsb_release -rd':
Description: Linux Mint 22.3
Release: 22.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141222/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141222
Title:
Displayport not proper working with linux kernel 6.17.0-14
Status in linux package in Ubuntu:
New
Bug description:
After upgrading to linux kernel 6.17.0-14 the Displayport of my ATI Ellesmere-GPU is not working anylonger. During the boot process the Linux Mint symbol is visible and afterwards my 2 monitors doesn't get a signal and are going to sleep (they are connected by one Displayport cable and the 2nd monitor is connected to the 1st). Looks like rest of the system works normal since short press of the power button shutsdown the system like expected.
By going back to kernel 6.14.0-37 everything works like expected again.
Output of "cat /proc/version_signature > version.log" - but this is not the affected kernel, this is the version which I'm currently using since it's working:
Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Output of "sudo lspci -vnvn > lspci-vnvn.log" see attached.
'lsb_release -rd':
Description: Linux Mint 22.3
Release: 22.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141222/+subscriptions
[Bug 2141222] [NEW] Displayport not proper working with linux kernel 6.17.0-14
You have been subscribed to a public bug:
After upgrading to linux kernel 6.17.0-14 the Displayport of my ATI Ellesmere-GPU is not working anylonger. During the boot process the Linux Mint symbol is visible and afterwards my 2 monitors doesn't get a signal and are going to sleep (they are connected by one Displayport cable and the 2nd monitor is connected to the 1st). Looks like rest of the system works normal since short press of the power button shutsdown the system like expected.
By going back to kernel 6.14.0-37 everything works like expected again.
Output of "cat /proc/version_signature > version.log" - but this is not the affected kernel, this is the version which I'm currently using since it's working:
Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Output of "sudo lspci -vnvn > lspci-vnvn.log" see attached.
'lsb_release -rd':
Description: Linux Mint 22.3
Release: 22.3
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
Displayport not proper working with linux kernel 6.17.0-14
https://bugs.launchpad.net/bugs/2141222
You received this bug notification because you are subscribed to linux in Ubuntu.
After upgrading to linux kernel 6.17.0-14 the Displayport of my ATI Ellesmere-GPU is not working anylonger. During the boot process the Linux Mint symbol is visible and afterwards my 2 monitors doesn't get a signal and are going to sleep (they are connected by one Displayport cable and the 2nd monitor is connected to the 1st). Looks like rest of the system works normal since short press of the power button shutsdown the system like expected.
By going back to kernel 6.14.0-37 everything works like expected again.
Output of "cat /proc/version_signature > version.log" - but this is not the affected kernel, this is the version which I'm currently using since it's working:
Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Output of "sudo lspci -vnvn > lspci-vnvn.log" see attached.
'lsb_release -rd':
Description: Linux Mint 22.3
Release: 22.3
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
Displayport not proper working with linux kernel 6.17.0-14
https://bugs.launchpad.net/bugs/2141222
You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2141475] [NEW] 6.19 kernel fails to load, possibly because of nvidia configuration issue
Public bug reported:
On ubuntu 26.04, I upgraded to kernel 6.19 with nvidia-driver-590-open installed. I got configuration errors, and the 6.19 kernel failed to load.
After purging all the nvidia-related packages with sudo apt remove --purge '^nvidia-.*', no configuration errors remain, but the 6.19 kernel still crashes on load.
This issue appears with the nvidia-driver-580-open driver as well, so I think this is a kernel issue and not an nvidia issue.
Kernel 6.18 works fine with nvidia drivers.
This is what I get with each initramfs attempt when the nvidia driver is
installed:
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)… done.
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-modeset.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-drm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-uvm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod… done.
Building initial module nvidia/590.48.01 for 6.19.0-3-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
dpkg: error processing package nvidia-dkms-590-open (–configure):
installed nvidia-dkms-590-open package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-590-open:
nvidia-driver-590-open depends on nvidia-dkms-590-open (<= 590.48.01-1); however:
Package nvidia-dkms-590-open is not configured yet.
nvidia-driver-590-open depends on nvidia-dkms-590-open (>= 590.48.01); however:
Package nvidia-dkms-590-open is not configured yet.
dpkg: error processing package nvidia-driver-590-open (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for linu
x-image-6.19.0-3-generic (6.19.0-3.3+1) …
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-3-generic (x86_64)
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
Autoinstall on 6.19.0-3-generic failed for module(s) nvidia(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.19.0-3-generic (–configure):
installed linux-image-6.19.0-3-generic package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.150ubuntu7) …
update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic
Errors were encountered while processing:
nvidia-dkms-590-open
nvidia-driver-590-open
linux-image-6.19.0-3-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-3-generic 6.19.0-3.3+1
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 10 22:28:57 2026
InstallationDate: Installed on 2022-01-31 (1471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
MachineType: ASUS System Product Name
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.18.0-9-generic root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-07 (3 days ago)
dmi.bios.date: 12/03/2024
dmi.bios.release: 41.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4101
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd12/03/2024:br41.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute third-party-packages
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141475
Title:
6.19 kernel fails to load, possibly because of nvidia configuration
issue
Status in linux package in Ubuntu:
New
Bug description:
On ubuntu 26.04, I upgraded to kernel 6.19 with nvidia-driver-590-open installed. I got configuration errors, and the 6.19 kernel failed to load.
After purging all the nvidia-related packages with sudo apt remove --purge '^nvidia-.*', no configuration errors remain, but the 6.19 kernel still crashes on load.
This issue appears with the nvidia-driver-580-open driver as well, so I think this is a kernel issue and not an nvidia issue.
Kernel 6.18 works fine with nvidia drivers.
This is what I get with each initramfs attempt when the nvidia driver
is installed:
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)… done.
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-modeset.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-drm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-uvm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod… done.
Building initial module nvidia/590.48.01 for 6.19.0-3-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
dpkg: error processing package nvidia-dkms-590-open (–configure):
installed nvidia-dkms-590-open package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-590-open:
nvidia-driver-590-open depends on nvidia-dkms-590-open (<= 590.48.01-1); however:
Package nvidia-dkms-590-open is not configured yet.
nvidia-driver-590-open depends on nvidia-dkms-590-open (>= 590.48.01); however:
Package nvidia-dkms-590-open is not configured yet.
dpkg: error processing package nvidia-driver-590-open (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for linu
x-image-6.19.0-3-generic (6.19.0-3.3+1) …
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-3-generic (x86_64)
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
Autoinstall on 6.19.0-3-generic failed for module(s) nvidia(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.19.0-3-generic (–configure):
installed linux-image-6.19.0-3-generic package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.150ubuntu7) …
update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic
Errors were encountered while processing:
nvidia-dkms-590-open
nvidia-driver-590-open
linux-image-6.19.0-3-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-3-generic 6.19.0-3.3+1
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 10 22:28:57 2026
InstallationDate: Installed on 2022-01-31 (1471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
MachineType: ASUS System Product Name
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.18.0-9-generic root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-07 (3 days ago)
dmi.bios.date: 12/03/2024
dmi.bios.release: 41.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4101
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd12/03/2024:br41.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141475/+subscriptions
On ubuntu 26.04, I upgraded to kernel 6.19 with nvidia-driver-590-open installed. I got configuration errors, and the 6.19 kernel failed to load.
After purging all the nvidia-related packages with sudo apt remove --purge '^nvidia-.*', no configuration errors remain, but the 6.19 kernel still crashes on load.
This issue appears with the nvidia-driver-580-open driver as well, so I think this is a kernel issue and not an nvidia issue.
Kernel 6.18 works fine with nvidia drivers.
This is what I get with each initramfs attempt when the nvidia driver is
installed:
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)… done.
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-modeset.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-drm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-uvm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod… done.
Building initial module nvidia/590.48.01 for 6.19.0-3-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
dpkg: error processing package nvidia-dkms-590-open (–configure):
installed nvidia-dkms-590-open package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-590-open:
nvidia-driver-590-open depends on nvidia-dkms-590-open (<= 590.48.01-1); however:
Package nvidia-dkms-590-open is not configured yet.
nvidia-driver-590-open depends on nvidia-dkms-590-open (>= 590.48.01); however:
Package nvidia-dkms-590-open is not configured yet.
dpkg: error processing package nvidia-driver-590-open (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for linu
x-image-6.19.0-3-generic (6.19.0-3.3+1) …
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-3-generic (x86_64)
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
Autoinstall on 6.19.0-3-generic failed for module(s) nvidia(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.19.0-3-generic (–configure):
installed linux-image-6.19.0-3-generic package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.150ubuntu7) …
update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic
Errors were encountered while processing:
nvidia-dkms-590-open
nvidia-driver-590-open
linux-image-6.19.0-3-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-3-generic 6.19.0-3.3+1
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 10 22:28:57 2026
InstallationDate: Installed on 2022-01-31 (1471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
MachineType: ASUS System Product Name
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.18.0-9-generic root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-07 (3 days ago)
dmi.bios.date: 12/03/2024
dmi.bios.release: 41.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4101
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd12/03/2024:br41.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute third-party-packages
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141475
Title:
6.19 kernel fails to load, possibly because of nvidia configuration
issue
Status in linux package in Ubuntu:
New
Bug description:
On ubuntu 26.04, I upgraded to kernel 6.19 with nvidia-driver-590-open installed. I got configuration errors, and the 6.19 kernel failed to load.
After purging all the nvidia-related packages with sudo apt remove --purge '^nvidia-.*', no configuration errors remain, but the 6.19 kernel still crashes on load.
This issue appears with the nvidia-driver-580-open driver as well, so I think this is a kernel issue and not an nvidia issue.
Kernel 6.18 works fine with nvidia drivers.
This is what I get with each initramfs attempt when the nvidia driver
is installed:
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)… done.
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-modeset.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-drm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-uvm.ko.zst
Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-peermem.ko.zst
Running depmod… done.
Building initial module nvidia/590.48.01 for 6.19.0-3-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
dpkg: error processing package nvidia-dkms-590-open (–configure):
installed nvidia-dkms-590-open package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-590-open:
nvidia-driver-590-open depends on nvidia-dkms-590-open (<= 590.48.01-1); however:
Package nvidia-dkms-590-open is not configured yet.
nvidia-driver-590-open depends on nvidia-dkms-590-open (>= 590.48.01); however:
Package nvidia-dkms-590-open is not configured yet.
dpkg: error processing package nvidia-driver-590-open (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for linu
x-image-6.19.0-3-generic (6.19.0-3.3+1) …
/etc/kernel/postinst.d/dkms:
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-3-generic (x86_64)
Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch… done.
Building module(s)…(bad exit status: 2)
Failed command:
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19
.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNE
L_IBT= modules
/usr/share/apport/package-hooks/dkms_packages.py:101: DeprecationWarning: apport.fatal() is deprecated. Please use apport.logging.fata
l() directly instead.
apport.fatal('Cannot create report: ' + str(e))
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-590-open.0.crash'
Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64)
Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information.
Autoinstall on 6.19.0-3-generic failed for module(s) nvidia(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.19.0-3-generic (–configure):
installed linux-image-6.19.0-3-generic package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.150ubuntu7) …
update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic
Errors were encountered while processing:
nvidia-dkms-590-open
nvidia-driver-590-open
linux-image-6.19.0-3-generic
Error: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-3-generic 6.19.0-3.3+1
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 10 22:28:57 2026
InstallationDate: Installed on 2022-01-31 (1471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
MachineType: ASUS System Product Name
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.18.0-9-generic root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-07 (3 days ago)
dmi.bios.date: 12/03/2024
dmi.bios.release: 41.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4101
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd12/03/2024:br41.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141475/+subscriptions
[Bug 2129972] Re: Ubuntu 25.10 can't boot with 6.17.0-6-generic kernel on encrypted fs
I run into this with every kernel update now (recently 6.17.0-14).
Having to disable and re-enable my network shares to get back up and
running. I suppose I'll have to take this kdump-tools workaround for a
spin...
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2129972
Title:
Ubuntu 25.10 can't boot with 6.17.0-6-generic kernel on encrypted fs
Status in kdump-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi guys.
Just got updated kernel 6.17.0-6 for 25.10, decided to reboot and
found out, that I can't boot anymore.
This laptop uses an ext4 on top of encrypted LVM setup (LUKS
encryption v2).
I'm able to provide encryption password, system continues to boot, but
it looks like that can't mount root partition, so I don't have logs,
just a screenshot of what kernel reports on screen that I've added to
attachment.
Previous kernel 6.17.0-5 boots without problems.
That's my /etc/fstab just in case it's needed:
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-aoOM30ZlY6QyCItp6GcyhkVzOBoTPNfQX0UH24zvqx7or2HTnBZW2Y5PquPhVoXq / ext4 defaults 0 1
# /boot was on /dev/nvme0n1p2 during curtin installation
/dev/disk/by-uuid/5ee5a33e-ec14-4619-84a2-ae11385c546e /boot ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/3B99-B952 /boot/efi vfat defaults 0 1
/swapfile none swap sw 0 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2129972/+subscriptions
Having to disable and re-enable my network shares to get back up and
running. I suppose I'll have to take this kdump-tools workaround for a
spin...
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2129972
Title:
Ubuntu 25.10 can't boot with 6.17.0-6-generic kernel on encrypted fs
Status in kdump-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi guys.
Just got updated kernel 6.17.0-6 for 25.10, decided to reboot and
found out, that I can't boot anymore.
This laptop uses an ext4 on top of encrypted LVM setup (LUKS
encryption v2).
I'm able to provide encryption password, system continues to boot, but
it looks like that can't mount root partition, so I don't have logs,
just a screenshot of what kernel reports on screen that I've added to
attachment.
Previous kernel 6.17.0-5 boots without problems.
That's my /etc/fstab just in case it's needed:
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-aoOM30ZlY6QyCItp6GcyhkVzOBoTPNfQX0UH24zvqx7or2HTnBZW2Y5PquPhVoXq / ext4 defaults 0 1
# /boot was on /dev/nvme0n1p2 during curtin installation
/dev/disk/by-uuid/5ee5a33e-ec14-4619-84a2-ae11385c546e /boot ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/3B99-B952 /boot/efi vfat defaults 0 1
/swapfile none swap sw 0 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2129972/+subscriptions
[Bug 2141198] Re: Suspend failure with mt7925e after kernel upgrade
The log actually shows 2 errors on suspend (I/O error (-5) from the
NVidia GPU and the timeout (-110) from mt7925*). But only 1 out of the 9
logged attempts. So the wifi one is clearly the more problematic.
Without much knowledge in that area this would be the list of changes
related to the driver between -94 and -100:
caebf21cb95a wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan
d7df895ddc78 wifi: mt76: mt7925: fix the wrong config for tx interrupt
46538accc007 wifi: mt76: mt7925: introduce thermal protection
b18036b7dfbd wifi: mt76: mt7925: fix host interrupt register initialization
6f06c674da53 wifi: mt76: mt7925: ensure all MCU commands wait for response
b8661e81e6ff wifi: mt76: mt7925: refine the sniffer commnad
70f32333522f wifi: mt76: mt7925: prevent multiple scan commands
09e5c8afe92f wifi: mt76: mt7925: fix fails to enter low power mode in suspend state
3116845d21ab wifi: mt76: mt7925: load the appropriate CLC data based on hardware type
d2c93401aecf wifi: mt76: mt7925: fix country count limitation for CLC
8adfc20eaf99 wifi: mt76: mt7925: ensure wow pattern command align fw format
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141198
Title:
Suspend failure with mt7925e after kernel upgrade
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
Last night, I updated to kernel 6.8.0-100.100 from kernel 6.8.0-94.96
and immediately shut down the computer. Today I booted the computer,
read some things for a few minutes and tried to suspend, which failed
repeatedly. I had no such problem in the previous kernel.
journalctl reported the following lines as the source of the problem:
Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: Message 00020007 (seq 5) timeout Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend+0x0/0x2e0 [mt7925e] returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: failed to suspend async: error -110 Feb 07 12:02:24 pm-cpp kernel: PM: Some devices failed to suspend, or early wake event detected
I am able to suspend by shutting down wifi and removing the mt7925e
and related kernel modules:
sudo nano /usr/lib/systemd/system-sleep/mt7925e-sleep
#!/bin/sh
case "$1/$2" in
pre/*)
/usr/bin/nmcli radio wifi off >/dev/null 2>&1 || true
/usr/sbin/modprobe -r mt7925e mt76_connac_lib mt76 >/dev/null 2>&1 || true
;;
post/*)
/usr/sbin/modprobe mt7925e >/dev/null 2>&1 || true
/usr/bin/nmcli radio wifi on >/dev/null 2>&1 || true
;;
esac
exit 0
The above, however, may give me problems resuming remote connections.
An alternative is to return to my older kernel, but that loses
security updates, I presume.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: pm 3631 F.... wireplumber
/dev/snd/pcmC1D0p: pm 3629 F...m pipewire
/dev/snd/controlC0: pm 3631 F.... wireplumber
/dev/snd/seq: pm 3629 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Feb 7 12:59:42 2026
HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354
InstallationDate: Installed on 2024-12-22 (413 days ago)
InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
MachineType: CyberPowerPC GamingPC
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro quiet cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot splash resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=1 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2025
dmi.bios.release: 22.7
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2207
dmi.board.asset.tag: Default string
dmi.board.name: Z890 MAX GAMING WIFI7
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2207:bd07/18/2025:br22.7:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US:
dmi.product.family: C Series
dmi.product.name: GamingPC
dmi.product.sku: CPPC-SYSTEM-US
dmi.product.version: System Version
dmi.sys.vendor: CyberPowerPC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141198/+subscriptions
NVidia GPU and the timeout (-110) from mt7925*). But only 1 out of the 9
logged attempts. So the wifi one is clearly the more problematic.
Without much knowledge in that area this would be the list of changes
related to the driver between -94 and -100:
caebf21cb95a wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan
d7df895ddc78 wifi: mt76: mt7925: fix the wrong config for tx interrupt
46538accc007 wifi: mt76: mt7925: introduce thermal protection
b18036b7dfbd wifi: mt76: mt7925: fix host interrupt register initialization
6f06c674da53 wifi: mt76: mt7925: ensure all MCU commands wait for response
b8661e81e6ff wifi: mt76: mt7925: refine the sniffer commnad
70f32333522f wifi: mt76: mt7925: prevent multiple scan commands
09e5c8afe92f wifi: mt76: mt7925: fix fails to enter low power mode in suspend state
3116845d21ab wifi: mt76: mt7925: load the appropriate CLC data based on hardware type
d2c93401aecf wifi: mt76: mt7925: fix country count limitation for CLC
8adfc20eaf99 wifi: mt76: mt7925: ensure wow pattern command align fw format
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141198
Title:
Suspend failure with mt7925e after kernel upgrade
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
Last night, I updated to kernel 6.8.0-100.100 from kernel 6.8.0-94.96
and immediately shut down the computer. Today I booted the computer,
read some things for a few minutes and tried to suspend, which failed
repeatedly. I had no such problem in the previous kernel.
journalctl reported the following lines as the source of the problem:
Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: Message 00020007 (seq 5) timeout Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend+0x0/0x2e0 [mt7925e] returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: failed to suspend async: error -110 Feb 07 12:02:24 pm-cpp kernel: PM: Some devices failed to suspend, or early wake event detected
I am able to suspend by shutting down wifi and removing the mt7925e
and related kernel modules:
sudo nano /usr/lib/systemd/system-sleep/mt7925e-sleep
#!/bin/sh
case "$1/$2" in
pre/*)
/usr/bin/nmcli radio wifi off >/dev/null 2>&1 || true
/usr/sbin/modprobe -r mt7925e mt76_connac_lib mt76 >/dev/null 2>&1 || true
;;
post/*)
/usr/sbin/modprobe mt7925e >/dev/null 2>&1 || true
/usr/bin/nmcli radio wifi on >/dev/null 2>&1 || true
;;
esac
exit 0
The above, however, may give me problems resuming remote connections.
An alternative is to return to my older kernel, but that loses
security updates, I presume.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: pm 3631 F.... wireplumber
/dev/snd/pcmC1D0p: pm 3629 F...m pipewire
/dev/snd/controlC0: pm 3631 F.... wireplumber
/dev/snd/seq: pm 3629 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Feb 7 12:59:42 2026
HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354
InstallationDate: Installed on 2024-12-22 (413 days ago)
InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
MachineType: CyberPowerPC GamingPC
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro quiet cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot splash resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=1 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2025
dmi.bios.release: 22.7
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2207
dmi.board.asset.tag: Default string
dmi.board.name: Z890 MAX GAMING WIFI7
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2207:bd07/18/2025:br22.7:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US:
dmi.product.family: C Series
dmi.product.name: GamingPC
dmi.product.sku: CPPC-SYSTEM-US
dmi.product.version: System Version
dmi.sys.vendor: CyberPowerPC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141198/+subscriptions
[Bug 2141203] Re: kernel panic after upgrade to linux kernel 6.17.0-14-generic
Just want to still add - I fou nd a workaround, for now:
- Boot from old kernel
- sudo update-initramfs -u -k 6.17.0-14-generic
- sudo update-grub
- reboot to 6.17.0-14 and it works
So it looks like the initramfs was not generated or not correctly for
kernel 6.17.0-14
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141203
Title:
kernel panic after upgrade to linux kernel 6.17.0-14-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel
panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor
fs on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141203/+subscriptions
- Boot from old kernel
- sudo update-initramfs -u -k 6.17.0-14-generic
- sudo update-grub
- reboot to 6.17.0-14 and it works
So it looks like the initramfs was not generated or not correctly for
kernel 6.17.0-14
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141203
Title:
kernel panic after upgrade to linux kernel 6.17.0-14-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel
panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor
fs on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141203/+subscriptions
[Bug 2139276] Re: [usrmerge] evaluate kernel owned packages for DEP17 compliance
** Changed in: alsa-driver (Ubuntu)
Status: New => Triaged
** Changed in: alsa-driver (Ubuntu)
Importance: Undecided => Low
** Tags added: dcr-incoming
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139276
Title:
[usrmerge] evaluate kernel owned packages for DEP17 compliance
Status in alsa-driver package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware-xilinx-ap1302 package in Ubuntu:
New
Status in linux-firmware-xilinx-vcu package in Ubuntu:
New
Status in nouveau-firmware package in Ubuntu:
New
Bug description:
The following packages have been identified as having a possible issue
related to usr-merge. DEP-17 describes the issue and problems at
length[0]. The check done was not perfect, and may lead to false
positives. The following was the run to identify possible packages,
further refined with slight pruning of obvious false positives
apt-file search --package-only --regexp
'^/(sbin|bin|lib|lib32|lib64|libx32)/*'
Lintian, when run on a suitably new system (such as within a resolute
build environment), will provide some errors related to usr-merge. an
example of a Lintian error from busybox
E: busybox-static: aliased-location [bin/]
E: busybox-static: aliased-location [bin/static-sh]
Please evaluate the follow packages for any issues dictated in dep17.
If any package below is not a part of the Kernel set, please let me
know and I'll file separate bugs for those packages (a bunch are
nvidia based, and I'm not sure who is owning them)
[0] https://dep-team.pages.debian.net/deps/dep17/
alsa-driver
fabric-manager-570
fabric-manager-580
fabric-manager-590
linux
linux-firmware-xilinx-ap1302
linux-firmware-xilinx-vcu
linux-realtime
linux-restricted-modules
linux-restricted-modules-aws
linux-restricted-modules-azure
linux-restricted-modules-gcp
linux-restricted-modules-oracle
linux-restricted-signatures
linux-riscv
nouveau-firmware
nvidia-graphics-drivers-580
nvidia-graphics-drivers-580-server
nvidia-graphics-drivers-590
nvidia-graphics-drivers-590-server
nvidia-imex-570
nvidia-imex-580
nvidia-imex-590
nvidia-prime
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2139276/+subscriptions
Status: New => Triaged
** Changed in: alsa-driver (Ubuntu)
Importance: Undecided => Low
** Tags added: dcr-incoming
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139276
Title:
[usrmerge] evaluate kernel owned packages for DEP17 compliance
Status in alsa-driver package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware-xilinx-ap1302 package in Ubuntu:
New
Status in linux-firmware-xilinx-vcu package in Ubuntu:
New
Status in nouveau-firmware package in Ubuntu:
New
Bug description:
The following packages have been identified as having a possible issue
related to usr-merge. DEP-17 describes the issue and problems at
length[0]. The check done was not perfect, and may lead to false
positives. The following was the run to identify possible packages,
further refined with slight pruning of obvious false positives
apt-file search --package-only --regexp
'^/(sbin|bin|lib|lib32|lib64|libx32)/*'
Lintian, when run on a suitably new system (such as within a resolute
build environment), will provide some errors related to usr-merge. an
example of a Lintian error from busybox
E: busybox-static: aliased-location [bin/]
E: busybox-static: aliased-location [bin/static-sh]
Please evaluate the follow packages for any issues dictated in dep17.
If any package below is not a part of the Kernel set, please let me
know and I'll file separate bugs for those packages (a bunch are
nvidia based, and I'm not sure who is owning them)
[0] https://dep-team.pages.debian.net/deps/dep17/
alsa-driver
fabric-manager-570
fabric-manager-580
fabric-manager-590
linux
linux-firmware-xilinx-ap1302
linux-firmware-xilinx-vcu
linux-realtime
linux-restricted-modules
linux-restricted-modules-aws
linux-restricted-modules-azure
linux-restricted-modules-gcp
linux-restricted-modules-oracle
linux-restricted-signatures
linux-riscv
nouveau-firmware
nvidia-graphics-drivers-580
nvidia-graphics-drivers-580-server
nvidia-graphics-drivers-590
nvidia-graphics-drivers-590-server
nvidia-imex-570
nvidia-imex-580
nvidia-imex-590
nvidia-prime
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2139276/+subscriptions
[Bug 2141430] [NEW] Kernel trace found after boot
Public bug reported:
Feb 09 21:22:02 gmine kernel: ------------[ cut here ]------------
Feb 09 21:22:02 gmine kernel: WARNING: CPU: 0 PID: 11577 at fs/exec.c:118 path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Modules linked in: xt_recent snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp>
Feb 09 21:22:02 gmine kernel: ip_tables x_tables rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btintel btbcm btmtk uas hid_generic usb_storage>
Feb 09 21:22:02 gmine kernel: CPU: 0 UID: 1000 PID: 11577 Comm: Media Kdump: loaded Tainted: P O 6.17.0-14-generic #14-Ubuntu PREEMPT(voluntar>
Feb 09 21:22:02 gmine kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Feb 09 21:22:02 gmine kernel: Hardware name: Hewlett-Packard HP Compaq Elite 8300 SFF/3397, BIOS K01 v03.08 04/10/2019
Feb 09 21:22:02 gmine kernel: RIP: 0010:path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Code: 42 08 f6 40 58 02 74 22 b8 01 00 00 00 f6 42 10 04 75 0d 48 8b 42 08 0f b6 40 58 d0 e8 83 e0 01 5d 31 d2 31 ff c3 cc cc cc >
Feb 09 21:22:02 gmine kernel: RSP: 0018:ffffce9a563cbae8 EFLAGS: 00010246
Feb 09 21:22:02 gmine kernel: RAX: ffff8992c19f8800 RBX: 0000000000000001 RCX: ffff8992c6a8a780
Feb 09 21:22:02 gmine kernel: RDX: ffff8992c12db520 RSI: 0000000000000000 RDI: ffff8993145d9e80
Feb 09 21:22:02 gmine kernel: RBP: ffffce9a563cbae8 R08: 0000000000000000 R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 00007b8686bac000 R11: ffffce9a563cbba8 R12: 0000000000006000
Feb 09 21:22:02 gmine kernel: R13: 0000000000000002 R14: ffff8992c78bbc00 R15: ffff8993145d9e40
Feb 09 21:22:02 gmine kernel: FS: 00007b85f23fc6c0(0000) GS:ffff899631e7f000(0000) knlGS:0000000000000000
Feb 09 21:22:02 gmine kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 09 21:22:02 gmine kernel: CR2: 000057ae539b63e0 CR3: 00000002c80b4002 CR4: 00000000001726f0
Feb 09 21:22:02 gmine kernel: Call Trace:
Feb 09 21:22:02 gmine kernel: <TASK>
Feb 09 21:22:02 gmine kernel: do_mmap+0x2a6/0x680
Feb 09 21:22:02 gmine kernel: vm_mmap_pgoff+0x129/0x210
Feb 09 21:22:02 gmine kernel: ksys_mmap_pgoff+0x180/0x280
Feb 09 21:22:02 gmine kernel: __x64_sys_mmap+0x36/0x70
Feb 09 21:22:02 gmine kernel: x64_sys_call+0x20c0/0x2330
Feb 09 21:22:02 gmine kernel: do_syscall_64+0x81/0xb50
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? do_read_fault+0x10a/0x280
Feb 09 21:22:02 gmine kernel: ? do_fault+0x165/0x290
Feb 09 21:22:02 gmine kernel: ? pte_offset_map_rw_nolock+0x20/0xa0
Feb 09 21:22:02 gmine kernel: ? handle_pte_fault+0x141/0x1f0
Feb 09 21:22:02 gmine kernel: ? __handle_mm_fault+0x59d/0x720
Feb 09 21:22:02 gmine kernel: ? __seccomp_filter+0x45/0x5a0
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100
Feb 09 21:22:02 gmine kernel: ? irqentry_exit_to_user_mode+0x2d/0x1d0
Feb 09 21:22:02 gmine kernel: ? irqentry_exit+0x43/0x50
Feb 09 21:22:02 gmine kernel: ? exc_page_fault+0x90/0x1b0
Feb 09 21:22:02 gmine kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 09 21:22:02 gmine kernel: RIP: 0033:0x7b8689f32dec
Feb 09 21:22:02 gmine kernel: Code: 1e fa 41 f7 c1 ff 0f 00 00 75 33 55 48 89 e5 41 54 41 89 cc 53 48 89 fb 48 85 ff 74 41 45 89 e2 48 89 df b8 09 00 00 00 0f >
Feb 09 21:22:02 gmine kernel: RSP: 002b:00007b85f23f8230 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
Feb 09 21:22:02 gmine kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007b8689f32dec
Feb 09 21:22:02 gmine kernel: RDX: 0000000000000003 RSI: 0000000000005a00 RDI: 0000000000000000
Feb 09 21:22:02 gmine kernel: RBP: 00007b85f23f8240 R08: 000000000000003f R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000001
Feb 09 21:22:02 gmine kernel: R13: fffffffc00000000 R14: 00001c14023c7bd0 R15: 0000000000005a00
Feb 09 21:22:02 gmine kernel: </TASK>
Feb 09 21:22:02 gmine kernel: ---[ end trace 0000000000000000 ]---
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Feb 10 09:25:41 2026
InstallationDate: Installed on 2026-01-10 (31 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2019
dmi.bios.release: 3.8
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.08
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v03.08:bd04/10/2019:br3.8:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuE1W06US#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.product.sku: E1W06US#ABA
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141430
Title:
Kernel trace found after boot
Status in linux package in Ubuntu:
New
Bug description:
Feb 09 21:22:02 gmine kernel: ------------[ cut here ]------------
Feb 09 21:22:02 gmine kernel: WARNING: CPU: 0 PID: 11577 at fs/exec.c:118 path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Modules linked in: xt_recent snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp>
Feb 09 21:22:02 gmine kernel: ip_tables x_tables rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btintel btbcm btmtk uas hid_generic usb_storage>
Feb 09 21:22:02 gmine kernel: CPU: 0 UID: 1000 PID: 11577 Comm: Media Kdump: loaded Tainted: P O 6.17.0-14-generic #14-Ubuntu PREEMPT(voluntar>
Feb 09 21:22:02 gmine kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Feb 09 21:22:02 gmine kernel: Hardware name: Hewlett-Packard HP Compaq Elite 8300 SFF/3397, BIOS K01 v03.08 04/10/2019
Feb 09 21:22:02 gmine kernel: RIP: 0010:path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Code: 42 08 f6 40 58 02 74 22 b8 01 00 00 00 f6 42 10 04 75 0d 48 8b 42 08 0f b6 40 58 d0 e8 83 e0 01 5d 31 d2 31 ff c3 cc cc cc >
Feb 09 21:22:02 gmine kernel: RSP: 0018:ffffce9a563cbae8 EFLAGS: 00010246
Feb 09 21:22:02 gmine kernel: RAX: ffff8992c19f8800 RBX: 0000000000000001 RCX: ffff8992c6a8a780
Feb 09 21:22:02 gmine kernel: RDX: ffff8992c12db520 RSI: 0000000000000000 RDI: ffff8993145d9e80
Feb 09 21:22:02 gmine kernel: RBP: ffffce9a563cbae8 R08: 0000000000000000 R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 00007b8686bac000 R11: ffffce9a563cbba8 R12: 0000000000006000
Feb 09 21:22:02 gmine kernel: R13: 0000000000000002 R14: ffff8992c78bbc00 R15: ffff8993145d9e40
Feb 09 21:22:02 gmine kernel: FS: 00007b85f23fc6c0(0000) GS:ffff899631e7f000(0000) knlGS:0000000000000000
Feb 09 21:22:02 gmine kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 09 21:22:02 gmine kernel: CR2: 000057ae539b63e0 CR3: 00000002c80b4002 CR4: 00000000001726f0
Feb 09 21:22:02 gmine kernel: Call Trace:
Feb 09 21:22:02 gmine kernel: <TASK>
Feb 09 21:22:02 gmine kernel: do_mmap+0x2a6/0x680
Feb 09 21:22:02 gmine kernel: vm_mmap_pgoff+0x129/0x210
Feb 09 21:22:02 gmine kernel: ksys_mmap_pgoff+0x180/0x280
Feb 09 21:22:02 gmine kernel: __x64_sys_mmap+0x36/0x70
Feb 09 21:22:02 gmine kernel: x64_sys_call+0x20c0/0x2330
Feb 09 21:22:02 gmine kernel: do_syscall_64+0x81/0xb50
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? do_read_fault+0x10a/0x280
Feb 09 21:22:02 gmine kernel: ? do_fault+0x165/0x290
Feb 09 21:22:02 gmine kernel: ? pte_offset_map_rw_nolock+0x20/0xa0
Feb 09 21:22:02 gmine kernel: ? handle_pte_fault+0x141/0x1f0
Feb 09 21:22:02 gmine kernel: ? __handle_mm_fault+0x59d/0x720
Feb 09 21:22:02 gmine kernel: ? __seccomp_filter+0x45/0x5a0
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100
Feb 09 21:22:02 gmine kernel: ? irqentry_exit_to_user_mode+0x2d/0x1d0
Feb 09 21:22:02 gmine kernel: ? irqentry_exit+0x43/0x50
Feb 09 21:22:02 gmine kernel: ? exc_page_fault+0x90/0x1b0
Feb 09 21:22:02 gmine kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 09 21:22:02 gmine kernel: RIP: 0033:0x7b8689f32dec
Feb 09 21:22:02 gmine kernel: Code: 1e fa 41 f7 c1 ff 0f 00 00 75 33 55 48 89 e5 41 54 41 89 cc 53 48 89 fb 48 85 ff 74 41 45 89 e2 48 89 df b8 09 00 00 00 0f >
Feb 09 21:22:02 gmine kernel: RSP: 002b:00007b85f23f8230 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
Feb 09 21:22:02 gmine kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007b8689f32dec
Feb 09 21:22:02 gmine kernel: RDX: 0000000000000003 RSI: 0000000000005a00 RDI: 0000000000000000
Feb 09 21:22:02 gmine kernel: RBP: 00007b85f23f8240 R08: 000000000000003f R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000001
Feb 09 21:22:02 gmine kernel: R13: fffffffc00000000 R14: 00001c14023c7bd0 R15: 0000000000005a00
Feb 09 21:22:02 gmine kernel: </TASK>
Feb 09 21:22:02 gmine kernel: ---[ end trace 0000000000000000 ]---
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Feb 10 09:25:41 2026
InstallationDate: Installed on 2026-01-10 (31 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2019
dmi.bios.release: 3.8
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.08
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v03.08:bd04/10/2019:br3.8:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuE1W06US#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.product.sku: E1W06US#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141430/+subscriptions
Feb 09 21:22:02 gmine kernel: ------------[ cut here ]------------
Feb 09 21:22:02 gmine kernel: WARNING: CPU: 0 PID: 11577 at fs/exec.c:118 path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Modules linked in: xt_recent snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp>
Feb 09 21:22:02 gmine kernel: ip_tables x_tables rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btintel btbcm btmtk uas hid_generic usb_storage>
Feb 09 21:22:02 gmine kernel: CPU: 0 UID: 1000 PID: 11577 Comm: Media Kdump: loaded Tainted: P O 6.17.0-14-generic #14-Ubuntu PREEMPT(voluntar>
Feb 09 21:22:02 gmine kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Feb 09 21:22:02 gmine kernel: Hardware name: Hewlett-Packard HP Compaq Elite 8300 SFF/3397, BIOS K01 v03.08 04/10/2019
Feb 09 21:22:02 gmine kernel: RIP: 0010:path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Code: 42 08 f6 40 58 02 74 22 b8 01 00 00 00 f6 42 10 04 75 0d 48 8b 42 08 0f b6 40 58 d0 e8 83 e0 01 5d 31 d2 31 ff c3 cc cc cc >
Feb 09 21:22:02 gmine kernel: RSP: 0018:ffffce9a563cbae8 EFLAGS: 00010246
Feb 09 21:22:02 gmine kernel: RAX: ffff8992c19f8800 RBX: 0000000000000001 RCX: ffff8992c6a8a780
Feb 09 21:22:02 gmine kernel: RDX: ffff8992c12db520 RSI: 0000000000000000 RDI: ffff8993145d9e80
Feb 09 21:22:02 gmine kernel: RBP: ffffce9a563cbae8 R08: 0000000000000000 R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 00007b8686bac000 R11: ffffce9a563cbba8 R12: 0000000000006000
Feb 09 21:22:02 gmine kernel: R13: 0000000000000002 R14: ffff8992c78bbc00 R15: ffff8993145d9e40
Feb 09 21:22:02 gmine kernel: FS: 00007b85f23fc6c0(0000) GS:ffff899631e7f000(0000) knlGS:0000000000000000
Feb 09 21:22:02 gmine kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 09 21:22:02 gmine kernel: CR2: 000057ae539b63e0 CR3: 00000002c80b4002 CR4: 00000000001726f0
Feb 09 21:22:02 gmine kernel: Call Trace:
Feb 09 21:22:02 gmine kernel: <TASK>
Feb 09 21:22:02 gmine kernel: do_mmap+0x2a6/0x680
Feb 09 21:22:02 gmine kernel: vm_mmap_pgoff+0x129/0x210
Feb 09 21:22:02 gmine kernel: ksys_mmap_pgoff+0x180/0x280
Feb 09 21:22:02 gmine kernel: __x64_sys_mmap+0x36/0x70
Feb 09 21:22:02 gmine kernel: x64_sys_call+0x20c0/0x2330
Feb 09 21:22:02 gmine kernel: do_syscall_64+0x81/0xb50
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? do_read_fault+0x10a/0x280
Feb 09 21:22:02 gmine kernel: ? do_fault+0x165/0x290
Feb 09 21:22:02 gmine kernel: ? pte_offset_map_rw_nolock+0x20/0xa0
Feb 09 21:22:02 gmine kernel: ? handle_pte_fault+0x141/0x1f0
Feb 09 21:22:02 gmine kernel: ? __handle_mm_fault+0x59d/0x720
Feb 09 21:22:02 gmine kernel: ? __seccomp_filter+0x45/0x5a0
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100
Feb 09 21:22:02 gmine kernel: ? irqentry_exit_to_user_mode+0x2d/0x1d0
Feb 09 21:22:02 gmine kernel: ? irqentry_exit+0x43/0x50
Feb 09 21:22:02 gmine kernel: ? exc_page_fault+0x90/0x1b0
Feb 09 21:22:02 gmine kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 09 21:22:02 gmine kernel: RIP: 0033:0x7b8689f32dec
Feb 09 21:22:02 gmine kernel: Code: 1e fa 41 f7 c1 ff 0f 00 00 75 33 55 48 89 e5 41 54 41 89 cc 53 48 89 fb 48 85 ff 74 41 45 89 e2 48 89 df b8 09 00 00 00 0f >
Feb 09 21:22:02 gmine kernel: RSP: 002b:00007b85f23f8230 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
Feb 09 21:22:02 gmine kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007b8689f32dec
Feb 09 21:22:02 gmine kernel: RDX: 0000000000000003 RSI: 0000000000005a00 RDI: 0000000000000000
Feb 09 21:22:02 gmine kernel: RBP: 00007b85f23f8240 R08: 000000000000003f R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000001
Feb 09 21:22:02 gmine kernel: R13: fffffffc00000000 R14: 00001c14023c7bd0 R15: 0000000000005a00
Feb 09 21:22:02 gmine kernel: </TASK>
Feb 09 21:22:02 gmine kernel: ---[ end trace 0000000000000000 ]---
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Feb 10 09:25:41 2026
InstallationDate: Installed on 2026-01-10 (31 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2019
dmi.bios.release: 3.8
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.08
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v03.08:bd04/10/2019:br3.8:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuE1W06US#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.product.sku: E1W06US#ABA
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141430
Title:
Kernel trace found after boot
Status in linux package in Ubuntu:
New
Bug description:
Feb 09 21:22:02 gmine kernel: ------------[ cut here ]------------
Feb 09 21:22:02 gmine kernel: WARNING: CPU: 0 PID: 11577 at fs/exec.c:118 path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Modules linked in: xt_recent snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp>
Feb 09 21:22:02 gmine kernel: ip_tables x_tables rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btintel btbcm btmtk uas hid_generic usb_storage>
Feb 09 21:22:02 gmine kernel: CPU: 0 UID: 1000 PID: 11577 Comm: Media Kdump: loaded Tainted: P O 6.17.0-14-generic #14-Ubuntu PREEMPT(voluntar>
Feb 09 21:22:02 gmine kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Feb 09 21:22:02 gmine kernel: Hardware name: Hewlett-Packard HP Compaq Elite 8300 SFF/3397, BIOS K01 v03.08 04/10/2019
Feb 09 21:22:02 gmine kernel: RIP: 0010:path_noexec+0x46/0x50
Feb 09 21:22:02 gmine kernel: Code: 42 08 f6 40 58 02 74 22 b8 01 00 00 00 f6 42 10 04 75 0d 48 8b 42 08 0f b6 40 58 d0 e8 83 e0 01 5d 31 d2 31 ff c3 cc cc cc >
Feb 09 21:22:02 gmine kernel: RSP: 0018:ffffce9a563cbae8 EFLAGS: 00010246
Feb 09 21:22:02 gmine kernel: RAX: ffff8992c19f8800 RBX: 0000000000000001 RCX: ffff8992c6a8a780
Feb 09 21:22:02 gmine kernel: RDX: ffff8992c12db520 RSI: 0000000000000000 RDI: ffff8993145d9e80
Feb 09 21:22:02 gmine kernel: RBP: ffffce9a563cbae8 R08: 0000000000000000 R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 00007b8686bac000 R11: ffffce9a563cbba8 R12: 0000000000006000
Feb 09 21:22:02 gmine kernel: R13: 0000000000000002 R14: ffff8992c78bbc00 R15: ffff8993145d9e40
Feb 09 21:22:02 gmine kernel: FS: 00007b85f23fc6c0(0000) GS:ffff899631e7f000(0000) knlGS:0000000000000000
Feb 09 21:22:02 gmine kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 09 21:22:02 gmine kernel: CR2: 000057ae539b63e0 CR3: 00000002c80b4002 CR4: 00000000001726f0
Feb 09 21:22:02 gmine kernel: Call Trace:
Feb 09 21:22:02 gmine kernel: <TASK>
Feb 09 21:22:02 gmine kernel: do_mmap+0x2a6/0x680
Feb 09 21:22:02 gmine kernel: vm_mmap_pgoff+0x129/0x210
Feb 09 21:22:02 gmine kernel: ksys_mmap_pgoff+0x180/0x280
Feb 09 21:22:02 gmine kernel: __x64_sys_mmap+0x36/0x70
Feb 09 21:22:02 gmine kernel: x64_sys_call+0x20c0/0x2330
Feb 09 21:22:02 gmine kernel: do_syscall_64+0x81/0xb50
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? do_read_fault+0x10a/0x280
Feb 09 21:22:02 gmine kernel: ? do_fault+0x165/0x290
Feb 09 21:22:02 gmine kernel: ? pte_offset_map_rw_nolock+0x20/0xa0
Feb 09 21:22:02 gmine kernel: ? handle_pte_fault+0x141/0x1f0
Feb 09 21:22:02 gmine kernel: ? __handle_mm_fault+0x59d/0x720
Feb 09 21:22:02 gmine kernel: ? __seccomp_filter+0x45/0x5a0
Feb 09 21:22:02 gmine kernel: ? fdget_pos+0x11f/0x160
Feb 09 21:22:02 gmine kernel: ? ksys_lseek+0xa5/0xd0
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0
Feb 09 21:22:02 gmine kernel: ? do_syscall_64+0xb9/0xb50
Feb 09 21:22:02 gmine kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100
Feb 09 21:22:02 gmine kernel: ? irqentry_exit_to_user_mode+0x2d/0x1d0
Feb 09 21:22:02 gmine kernel: ? irqentry_exit+0x43/0x50
Feb 09 21:22:02 gmine kernel: ? exc_page_fault+0x90/0x1b0
Feb 09 21:22:02 gmine kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 09 21:22:02 gmine kernel: RIP: 0033:0x7b8689f32dec
Feb 09 21:22:02 gmine kernel: Code: 1e fa 41 f7 c1 ff 0f 00 00 75 33 55 48 89 e5 41 54 41 89 cc 53 48 89 fb 48 85 ff 74 41 45 89 e2 48 89 df b8 09 00 00 00 0f >
Feb 09 21:22:02 gmine kernel: RSP: 002b:00007b85f23f8230 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
Feb 09 21:22:02 gmine kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007b8689f32dec
Feb 09 21:22:02 gmine kernel: RDX: 0000000000000003 RSI: 0000000000005a00 RDI: 0000000000000000
Feb 09 21:22:02 gmine kernel: RBP: 00007b85f23f8240 R08: 000000000000003f R09: 0000000000000000
Feb 09 21:22:02 gmine kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000001
Feb 09 21:22:02 gmine kernel: R13: fffffffc00000000 R14: 00001c14023c7bd0 R15: 0000000000005a00
Feb 09 21:22:02 gmine kernel: </TASK>
Feb 09 21:22:02 gmine kernel: ---[ end trace 0000000000000000 ]---
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Feb 10 09:25:41 2026
InstallationDate: Installed on 2026-01-10 (31 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2019
dmi.bios.release: 3.8
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v03.08
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v03.08:bd04/10/2019:br3.8:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuE1W06US#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.product.sku: E1W06US#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141430/+subscriptions
[Bug 2141337] Re: kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
"ubuntu-bug linux-headers-6.19.0-3-generic
linux-headers-generic
linux-headers-generic-hwe-24.04
linux-generic
linux-generic-hwe-24.04
linux-image-6.19.0-3-generic" apport file
** Attachment added: "ubuntu-bug apport file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+attachment/5944755/+files/apport.linux-headers-6.19.0-3-generic.rrldnyws.apport
** Description changed:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
- linux-generic (v 6.19.0-3.3),
- linux-headers-6.19.0-3,
- linux-headers-6.19.0-3-generic,
- linux-image-6.19.0-3-generic,
- linux-modules-6.19.0-3-generic,
- linux-tools-6.19.0-3 (or linux-tools-6.19.0-3-generic, not sure)
-
- Since i rather cannot afford to nuke my laptop a third time now, that is
- unfortunately all the information i am able to give (i'm sorry). I hope
- this bug contribution is at all useful and that i did not make any
- mistakes here :]
+ linux-headers-6.19.0-3-generic
+ linux-headers-generic
+ linux-headers-generic-hwe-24.04
+ linux-generic
+ linux-generic-hwe-24.04
+ linux-image-6.19.0-3-generic
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141337
Title:
kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-headers-6.19.0-3-generic
linux-headers-generic
linux-headers-generic-hwe-24.04
linux-generic
linux-generic-hwe-24.04
linux-image-6.19.0-3-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+subscriptions
linux-headers-generic
linux-headers-generic-hwe-24.04
linux-generic
linux-generic-hwe-24.04
linux-image-6.19.0-3-generic" apport file
** Attachment added: "ubuntu-bug apport file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+attachment/5944755/+files/apport.linux-headers-6.19.0-3-generic.rrldnyws.apport
** Description changed:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
- linux-generic (v 6.19.0-3.3),
- linux-headers-6.19.0-3,
- linux-headers-6.19.0-3-generic,
- linux-image-6.19.0-3-generic,
- linux-modules-6.19.0-3-generic,
- linux-tools-6.19.0-3 (or linux-tools-6.19.0-3-generic, not sure)
-
- Since i rather cannot afford to nuke my laptop a third time now, that is
- unfortunately all the information i am able to give (i'm sorry). I hope
- this bug contribution is at all useful and that i did not make any
- mistakes here :]
+ linux-headers-6.19.0-3-generic
+ linux-headers-generic
+ linux-headers-generic-hwe-24.04
+ linux-generic
+ linux-generic-hwe-24.04
+ linux-image-6.19.0-3-generic
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141337
Title:
kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-headers-6.19.0-3-generic
linux-headers-generic
linux-headers-generic-hwe-24.04
linux-generic
linux-generic-hwe-24.04
linux-image-6.19.0-3-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+subscriptions
[Bug 2141337] Re: kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Terminal Output for sudo apt upgrade -y
** Attachment added: "Terminal output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+attachment/5944754/+files/terminalout-1.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141337
Title:
kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-headers-6.19.0-3-generic
linux-headers-generic
linux-headers-generic-hwe-24.04
linux-generic
linux-generic-hwe-24.04
linux-image-6.19.0-3-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+subscriptions
** Attachment added: "Terminal output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+attachment/5944754/+files/terminalout-1.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141337
Title:
kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-headers-6.19.0-3-generic
linux-headers-generic
linux-headers-generic-hwe-24.04
linux-generic
linux-generic-hwe-24.04
linux-image-6.19.0-3-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+subscriptions
[Bug 2141337] Re: kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
** Description changed:
+ [See comment for related Logs and Terminal output]
+
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-generic (v 6.19.0-3.3),
linux-headers-6.19.0-3,
linux-headers-6.19.0-3-generic,
linux-image-6.19.0-3-generic,
linux-modules-6.19.0-3-generic,
linux-tools-6.19.0-3 (or linux-tools-6.19.0-3-generic, not sure)
Since i rather cannot afford to nuke my laptop a third time now, that is
unfortunately all the information i am able to give (i'm sorry). I hope
this bug contribution is at all useful and that i did not make any
mistakes here :]
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141337
Title:
kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-generic (v 6.19.0-3.3),
linux-headers-6.19.0-3,
linux-headers-6.19.0-3-generic,
linux-image-6.19.0-3-generic,
linux-modules-6.19.0-3-generic,
linux-tools-6.19.0-3 (or linux-tools-6.19.0-3-generic, not sure)
Since i rather cannot afford to nuke my laptop a third time now, that
is unfortunately all the information i am able to give (i'm sorry). I
hope this bug contribution is at all useful and that i did not make
any mistakes here :]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+subscriptions
+ [See comment for related Logs and Terminal output]
+
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-generic (v 6.19.0-3.3),
linux-headers-6.19.0-3,
linux-headers-6.19.0-3-generic,
linux-image-6.19.0-3-generic,
linux-modules-6.19.0-3-generic,
linux-tools-6.19.0-3 (or linux-tools-6.19.0-3-generic, not sure)
Since i rather cannot afford to nuke my laptop a third time now, that is
unfortunately all the information i am able to give (i'm sorry). I hope
this bug contribution is at all useful and that i did not make any
mistakes here :]
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141337
Title:
kernel panic when upgrading to kernel 6.19.0-3.3 in kubuntu 26.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
[See comment for related Logs and Terminal output]
Starting System Configuration:
Kernel: Linux 6.18.0-9-generic (per fastfetch) or Ubuntu 6.18.0-9.9-generic 6.18.5 (per: cat /proc/version_signature)
OS: kubuntu 26.04 development release upgraded to status of Feb 08, 2026
Machine: Amd Ryzen 8840HS / Lenovo IdeaPad slim 3 14ahp10 per fastfetch (or 16ahp10 as per seller)
Issue reproduction:
1. Open Terminal in a system running kernel 6.18.0-9.9
1.5. Possibly important installed packages and modifications include: bleachbit (not used it once tho) and timeshift. Everything else is without sudo rights anyways (example: Krita).
2. Run command sudo apt update -y
3. Run command sudo apt-get upgrade -y
4. Shut down and boot system
Generalized: Updating to kernel 6.19.0-3.3 from 6.18.0-9 by means of software center or command line; applying changes during reboot.
Description:
During the upgrade to Kernel 6.19.0-3.3 the system spits out an Error, it may have been Error Code (1) but i do not recall it exactly; however reinstalling the grub (i checked it manually, too, it's the default one) did not resolve the issue, as a google result suggested, i still got the kernel panic.
Trying to boot from the GRUB advanced menu with an older kernel, as suggested at https://answers.launchpad.net/ubuntu/+question/823569, did not work as both times there WAS no older kernel available. I have not turned this feature off.
Affected were, as of CLI output, the following packages:
linux-generic (v 6.19.0-3.3),
linux-headers-6.19.0-3,
linux-headers-6.19.0-3-generic,
linux-image-6.19.0-3-generic,
linux-modules-6.19.0-3-generic,
linux-tools-6.19.0-3 (or linux-tools-6.19.0-3-generic, not sure)
Since i rather cannot afford to nuke my laptop a third time now, that
is unfortunately all the information i am able to give (i'm sorry). I
hope this bug contribution is at all useful and that i did not make
any mistakes here :]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141337/+subscriptions
[Bug 2139667] Re: [NEEDS PACKAGING] doca-ofed-25.10-dkms DKMS suite
** Description changed:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
-
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
-
- Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX platform: this is needed as customers using NVIDIA hardware can take advantage of custom, high performance drivers directly through Canonical apt system, without the need of downloading an external tarball to be manually installed on the target machines.
+ Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
+ platform: this is needed as customers using NVIDIA hardware can take
+ advantage of custom, high performance drivers directly through Canonical
+ apt system, without the need of downloading an external tarball to be
+ manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
-
[ Current Test Plan ]
- * Tested on
- * Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
- * Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
- * Questing 6.17.0-7-generic and 6.17.0-8-generic
+ * Tested on
+ * Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
+ * Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
+ * Questing 6.17.0-7-generic and 6.17.0-8-generic
- * Before upstreaming an update version of the repackaged kernel
+ * Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
-
[ Where problems could occur ]
- * No issues can be thought, as this is an extra package to be manually
+ * No issues can be thought, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
-
[ Other Info ]
- * The repackaging code is contained in the repository at the following
+ * The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
- * Examples of the repackaged DKMS can be found at the following private
+ * Examples of the repackaged DKMS can be found at the following private
PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Tested on
* Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
* Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
[ Where problems could occur ]
- * No issues can be thought, as this is an extra package to be manually
+ * No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following private
PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Tested on
* Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
* Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
- * Examples of the repackaged DKMS can be found at the following private
- PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
+ * Examples of the repackaged DKMS can be found at the following
+ personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] doca-ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Bug description:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Tested on
* Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
* Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
-
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
-
- Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX platform: this is needed as customers using NVIDIA hardware can take advantage of custom, high performance drivers directly through Canonical apt system, without the need of downloading an external tarball to be manually installed on the target machines.
+ Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
+ platform: this is needed as customers using NVIDIA hardware can take
+ advantage of custom, high performance drivers directly through Canonical
+ apt system, without the need of downloading an external tarball to be
+ manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
-
[ Current Test Plan ]
- * Tested on
- * Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
- * Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
- * Questing 6.17.0-7-generic and 6.17.0-8-generic
+ * Tested on
+ * Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
+ * Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
+ * Questing 6.17.0-7-generic and 6.17.0-8-generic
- * Before upstreaming an update version of the repackaged kernel
+ * Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
-
[ Where problems could occur ]
- * No issues can be thought, as this is an extra package to be manually
+ * No issues can be thought, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
-
[ Other Info ]
- * The repackaging code is contained in the repository at the following
+ * The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
- * Examples of the repackaged DKMS can be found at the following private
+ * Examples of the repackaged DKMS can be found at the following private
PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Tested on
* Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
* Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
[ Where problems could occur ]
- * No issues can be thought, as this is an extra package to be manually
+ * No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following private
PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Tested on
* Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
* Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
- * Examples of the repackaged DKMS can be found at the following private
- PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
+ * Examples of the repackaged DKMS can be found at the following
+ personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] doca-ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Bug description:
Support for doca-ofed-25.10 DKMS in Ubuntu Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family.
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Tested on
* Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
* Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
Подписаться на:
Комментарии (Atom)