[Kernel-packages] [Bug 2054172] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2054172 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: always showing pop up problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 17 07:59:17 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-08-18 (182 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2054172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
I can confirm this issue on Ubuntu 23.10 x86_64 6.5.0-17-generic, with Seagate Mobile HDD ST1000LM035-1RK172 (LCM2). When I switched back to kernel 6.5.0-15, that strange "click" noise disappeared. To set the older kernel as default, please refer to this link below: https://askubuntu.com/questions/216398/set-older-kernel-as-default-grub- entry/1000735#1000735 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: After the last kernel upgrade, I noticed that, in the S.M.A.R.T. monitor, parameter ID 192 "Power Off Retract Count" increased every time I turned off the system. I also noticed the "click" of the head parking when shutting down the computer. By restarting the computer with previous kernel version (6.5.0-15.15~22.04.1) the issue didn't happen, so I assume it's a kernel bug, that causes it to shut down the computer before hard drive is deactivated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Feb 13 16:35:55 2024 InstallationDate: Installed on 2020-10-02 (1228 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-11 (550 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054116] Re: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post-installation script subproce
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054116 Title: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post- installation script subprocess returned error exit status 139 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: No more details. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 16 15:00:47 2024 DuplicateSignature: package:linux-image-6.5.0-18-generic:6.5.0-18.18~22.04.1 Setting up linux-image-6.5.0-18-generic (6.5.0-18.18~22.04.1) ... Segmentation fault (core dumped) dpkg: error processing package linux-image-6.5.0-18-generic (--configure): installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139 ErrorMessage: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2024-02-11 (4 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2054116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054116] Re: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post-installation script subproce
Hello Andrew, this is confusing, based on the segfault from the maintainer scripts, I was expecting to see more evidence of memory failure or disk failure in your logs, but they look reasonable enough. It might still be worth running memtest86 overnight or over the weekend, just to be sure. Thanks ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054116 Title: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post- installation script subprocess returned error exit status 139 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: No more details. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 16 15:00:47 2024 DuplicateSignature: package:linux-image-6.5.0-18-generic:6.5.0-18.18~22.04.1 Setting up linux-image-6.5.0-18-generic (6.5.0-18.18~22.04.1) ... Segmentation fault (core dumped) dpkg: error processing package linux-image-6.5.0-18-generic (--configure): installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139 ErrorMessage: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2024-02-11 (4 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-18-generic package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2054116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054172] [NEW] package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit statu
Public bug reported: always showing pop up problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 17 07:59:17 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-08-18 (182 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2054172 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: always showing pop up problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 17 07:59:17 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-08-18 (182 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2054172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053155] Re: Add DPLL and syncE support
** Description changed:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL subsystem in the Linux kernel provides a general interface for
configuring devices that use any kind of Digital PLL. This subsystem is
designed to manage the clock signal synchronization of a device with an
external clock signal.
* Explain the bug(s)
We need to support mlx5 SyncE feature. The following patches are needed.
[net-next,v8,0/9] Create common DPLL configuration API
[net-next,v8,1/9] dpll: documentation on DPLL subsystem interface
[net-next,v8,2/9] dpll: spec: Add Netlink spec in YAML
[net-next,v8,3/9] dpll: core: Add DPLL framework base functions
[net-next,v8,4/9] dpll: netlink: Add DPLL framework base functions
[net-next,v8,5/9] netdev: expose DPLL pin handle for netdevice
[net-next,v8,6/9] ice: add admin commands to access cgu configuration
[net-next,v8,7/9] ice: implement dpll interface to control cgu
[net-next,v8,8/9] ptp_ocp: implement DPLL ops
[net-next,v8,9/9] mlx5: Implement SyncE support using DPLL infrastructure
https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedore...@linux.dev/
* Brief explanation of fixes
We identify several dependent patches, especially related to netlink gap
between current master-next.
We cherry-pick/backport series of patches related to netlink.
* How to test
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--dump device-get
ex:
root@bfqa-dell013-roy-oob:~/mlnx-ofa_kernel-4.0# /root/tools-net/ynl/cli.py
--spec ~/netlink/specs/dpll.yaml --dump device-get
[{'clock-id': 5237736944144095348,
- 'id': 0,
- 'lock-status': 'unlocked',
- 'mode': 'manual',
- 'mode-supported': ['manual'],
- 'module-name': 'mlx5_core',
- 'type': 'eec'}]
-
+ 'id': 0,
+ 'lock-status': 'unlocked',
+ 'mode': 'manual',
+ 'mode-supported': ['manual'],
+ 'module-name': 'mlx5_core',
+ 'type': 'eec'}]
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--do pin-get
ex:
root@bfqa-dell013-roy-oob:~# /root/tools-net/ynl/cli.py --spec
~/netlink/specs/dpll.yaml --dump pin-get
[{'capabilities': 4,
- 'clock-id': 5237736944144095348,
- 'id': 0,
- 'module-name': 'mlx5_core',
- 'parent-device': [{'direction': 'input',
- 'parent-id': 0,
- 'state': 'disconnected'}],
- 'phase-adjust-max': 0,
- 'phase-adjust-min': 0,
- 'type': 'synce-eth-port'},
- {'capabilities': 4,
- 'clock-id': 5237736944144095348,
- 'id': 1,
- 'module-name': 'mlx5_core',
- 'parent-device': [{'direction': 'input',
- 'parent-id': 0,
- 'state': 'disconnected'}],
- 'phase-adjust-max': 0,
- 'phase-adjust-min': 0,
- 'type': 'synce-eth-port'}]
+ 'clock-id': 5237736944144095348,
+ 'id': 0,
+ 'module-name': 'mlx5_core',
+ 'parent-device': [{'direction': 'input',
+ 'parent-id': 0,
+ 'state': 'disconnected'}],
+ 'phase-adjust-max': 0,
+ 'phase-adjust-min': 0,
+ 'type': 'synce-eth-port'},
+ {'capabilities': 4,
+ 'clock-id': 5237736944144095348,
+ 'id': 1,
+ 'module-name': 'mlx5_core',
+ 'parent-device': [{'direction': 'input',
+ 'parent-id': 0,
+ 'state': 'disconnected'}],
+ 'phase-adjust-max': 0,
+ 'phase-adjust-min': 0,
+ 'type': 'synce-eth-port'}]
+ * detect whether your device supports DPLL/SyncE
+ root@bfqa-dell013-roy-oob:~/linux-bluefield-jammy# mlxreg -d 03:00.0
--reg_name MCAM --get -i "access_reg_group=2,feature_group=0"
+ Field Name| Data
+ ===
+ access_reg_group | 0x0002
+ feature_group | 0x
+ mng_access_reg_cap_mask[0]| 0x0004
+ mng_access_reg_cap_mask[1]| 0x0060 --> must see 6
+
+ OR,
+ $ mlxfwmanager
+ showing “Enhanced-SyncE & PTP GM support”,
* list of patches applied to 5.15 jammy
based on
911f816f4c04 mlxbf_gige: fix receive packet race condition
we applied the following
83a11d94c436 UBUNTU: SAUCE: fix build error after resv_start_op
036b2fecd315 genetlink: allow families to use split ops directly
9f40a82f73ea genetlink: inline old iteration helpers
d8ae137b98fc genetlink: use iterator in the op to policy map dumping
095792a3a723 genetlink: add iterator for walking family ops
764747ba0085 genetlink: limit the use of validation workarounds to old ops
35b95f016392 genetlink: inline genl_get_cmd()
c448680485e6 genetlink: support split policies in ctrl_dumppolicy_put_op()
a17efffb8ce8 genetlink: add policies for both doit and dumpit in
ctrl_dumppolicy_start()
82af441de2fa genetlink:
[Kernel-packages] [Bug 2053148] Re: Pull request: address GPIO initialization regression on Grace systems
This bug is awaiting verification that the linux- nvidia-6.5/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-done-jammy-linux-nvidia-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed-jammy-linux-nvidia-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 verification-needed-jammy-linux-nvidia-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053148 Title: Pull request: address GPIO initialization regression on Grace systems Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: The tegra186_gpio_is_accessible() function incorrectly declares GPIO lines that have only one of TEGRA186_GPIO_SCR_SEC_REN _or_ TEGRA186_GPIO_SCR_SEC_WEN set as being inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2053148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054107] Re: Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy
Not entirely sure what happened but I updated the firmware on my laptop and tried again and it worked. So not sure what the problem was, but doesn't seem to be a bug. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054107 Title: Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy Status in linux package in Ubuntu: Invalid Bug description: This morning, I installed the 6.5.0-18 updates on my Jammy system and rebooted. After rebooting, I'm unable to boot from my encrypted SSD. It reports that my passphrase is incorrect. Reverting back to 6.5.0-17 doesn't have this problem. ii linux-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.5-headers-6.5.0-18 6.5.0-18.18~22.04.1 all Header files related to Linux kernel version 6.5.0 ii linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.046.5.0.18.18~22.04.10 amd64Generic Linux kernel image ii linux-modules-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053280] Re: System randomly freezing and coming back seconds after
There is some extra logs I can send to help in the diagnostic? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053280 Title: System randomly freezing and coming back seconds after Status in linux package in Ubuntu: New Bug description: Randomly all the system (the mouse pointer included) freezes and after some seconds it unfreeze, this happens each a couple of minutes, I don't saw any pattern, nor any strange messages on dmesg. When I boot to the kernel 6.2 everything is normal. uname -a Linux PC 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I am using Linux Mint, but the link in the kernel package manager for bug reports brought me here lsb_release -rd Description: Linux Mint 21.3 Release: 21.3 fabio@PC:~$ cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" fabio@PC:~$ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=21.3 DISTRIB_CODENAME=virginia DISTRIB_DESCRIPTION="Linux Mint 21.3 Virginia" fabio@PC:~$ cat /etc/os-release NAME="Linux Mint" VERSION="21.3 (Virginia)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Linux Mint 21.3" VERSION_ID="21.3" HOME_URL="https://www.linuxmint.com/; SUPPORT_URL="https://forums.linuxmint.com/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/; PRIVACY_POLICY_URL="https://www.linuxmint.com/; VERSION_CODENAME=virginia UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052861] Re: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10
** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2052861 Title: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10 Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Mantic: In Progress Bug description: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10 I've got one of the PCIe NVME extension HATs for rpi 5 [1] and installed a functioning NVME drive Samsung SM961. Tried to boot it first with an image of RaspberryPI OS from sd-card. Upon boot, the nvme drive was detected and I could mount it and perform some IO: > uname -a Linux raspberrypi 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux > lspci -nnk :00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport :01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801] Kernel driver in use: nvme 0001:00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 0001:01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 dmesg logs of rpios will be attached, but there is nothing suspicious. Then I've tried to run Ubuntu 23.10 and reimaged the sd-card with "Ubuntu Server 23.10 (64-bit) (released 2023-10-12). Upon boot, the drive didn't show up: > lspci -nnk 00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 Checked for updates and there was a newer kernel available, thus I've upgraded: > apt update > apt list --upgradable ... linux-image-raspi/mantic-updates,mantic-security 6.5.0.1010.11 arm64 [upgradable from: 6.5.0.1005.6] After reboot, the nvme still didn't show up. Full dmesg log is attached, but in essence the pcie driver is having troubles to enumerate one for devices on the bus: [0.00] Booting Linux on physical CPU 0x00 [0x414fd0b1] [0.00] Linux version 6.5.0-1010-raspi (buildd@bos03-arm64-017) (aarch64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41) #13-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 18 09:08:04 UTC 2024 (Ubuntu 6.5.0-1010.13-raspi 6.5.8) ... [2.612956] brcm-pcie 100011.pcie: link down [2.617719] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [2.624391] pci :00:00.0: PCI bridge to [bus 01] ... [2.876967] brcm-pcie 100012.pcie: link up, 5.0 GT/s PCIe x4 (!SSC) [2.883637] pci :01:00.0: [1de4:0001] type 00 class 0x02 ... After digging a bit, I found a discussion on the Raspberry's kernel github [2]: - a bug was introduced sometime in 6.2.x [3] - a fix landed in 6.6.x [4] - it boils down to a misused `readw_` instead of `readl_` in the pcie-brcmstb driver This made me think that given that the upcoming 24.04 is going to be on 6.7 or 6.8 kernel, the fix might be already there. So I grabbed a build of the "6.7.0-1001.1"[5] kernel from the "Noble Proposed" and installed it on the Mantic on my sd-card. After reboot, the nvme drive was discovered and proper driver was loaded: > uname -a Linux pi 6.7.0-1001-raspi #1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 25 12:28:01 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux > lspci -nnk :00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport :01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801] Kernel driver in use: nvme Kernel modules: nvme 0001:00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 0001:01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 > dmesg ... [2.221266] brcm-pcie 100011.pcie: link up, 5.0 GT/s PCIe x1 (!SSC) [2.227947] pci :01:00.0: [144d:a804] type 00 class 0x010802 [2.234031] pci :01:00.0: reg 0x10: [mem 0x1b-0x1b3fff 64bit] [2.241396] pci :01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at :00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) ... [2.334202] nvme nvme0: pci function
[Kernel-packages] [Bug 2048951] Re: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux-image-6.5.0-18-generic (linux-image-generic-hwe-22.04)
** Summary changed: - NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04) + Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux-image-6.5.0-18-generic (linux-image-generic-hwe-22.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
I can confirm that booting with "apparmor=0" added to kernel command line works around the issue. This host runs lxd containers, so from the security standpoint running it without apparmor is not acceptable. However this proves there is an apparmor bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Package changed: linux-meta-hwe-6.5 (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Attachment added: "Screenshot 2024-02-16 at 13.42.06.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746725/+files/Screenshot%202024-02-16%20at%2013.42.06.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Attachment added: "Screenshot 2024-02-16 at 13.43.11.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746726/+files/Screenshot%202024-02-16%20at%2013.43.11.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Attachment added: "Screenshot 2024-02-16 at 13.39.07.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746724/+files/Screenshot%202024-02-16%20at%2013.39.07.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Attachment added: "Screenshot 2024-02-16 at 13.35.42.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746723/+files/Screenshot%202024-02-16%20at%2013.35.42.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Attachment added: "Screenshot 2024-02-16 at 13.32.35.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746722/+files/Screenshot%202024-02-16%20at%2013.32.35.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** Attachment added: "Screenshot 2024-02-16 at 13.29.01.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746721/+files/Screenshot%202024-02-16%20at%2013.29.01.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
I was able to disable mode switch and record a video with the kernel attempting to output the oops. It seems to be an issue with apparmor. The text I manually recovered from the video: --- BUG: kernel NULL pointer dereference, address: 0008 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page P?D 0 P4D 0 Ooops: [#1] PREEMPT SMP WDPTI ... Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? do_user_addr_fault+0x31d/0x6b0 ? exc_page_fault+0x83/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? find_attach+0x11a/0x5e0 ? d_namespace_path_constprop.0+0xa3/0x310 profile_transition+0x5e0/0x910 apparmor_bprm_creds_for_exec+0x3b9/0xc00 security_bprm_creds_for_exec+0x2e/0x50 bprm_execve.part.0+0x12f/0x250 bprm_execve+0x5d/0xa0 do_execveat_common.isra.0+0x1a9/0x260 __x64_sys_execve+0x87/0x60 do_syscall_64+0x58/0x?0 ? syscall_exit_to_user_mode+0x37/0x60 ? do_syscall_64+0x67/0x90 entry_SYSCALL_64_after_hwframe+0x6r/0xd8 --- I will also attach screenshots from the video -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054155] [NEW] Add BPF kernel module to 20.04 and 22.04 images
Public bug reported: LXD image provided in the ubuntu: remotes do not contain BPF kernel module. BPF module is present in the stock linux-generic versions of the kernel package but *-kvm kernel does not appear to be built with it -- this is a request for its inclusion. Repro: --- 1. Deploy a 20.04 or 22.04 release image (ubuntu:focal or ubuntu:jammy should suffice) VM on LXD (not container) 2. Observe uname -r to see that the -kvm variant of the ubuntu kernel is running 3. Check to see if BPFilter module is available: # find /lib/modules/$(uname -r)/ -type f -name '*bpfilter.ko' There are use cases where the BPF module is still used and it may be a while before users are able to transition to 24.04+ which I understand transitions to using the generic kernel. ** Affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-meta-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-meta-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-meta-kvm (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2054155 Title: Add BPF kernel module to 20.04 and 22.04 images Status in linux-meta-kvm package in Ubuntu: New Status in linux-meta-kvm source package in Focal: New Status in linux-meta-kvm source package in Jammy: New Bug description: LXD image provided in the ubuntu: remotes do not contain BPF kernel module. BPF module is present in the stock linux-generic versions of the kernel package but *-kvm kernel does not appear to be built with it -- this is a request for its inclusion. Repro: --- 1. Deploy a 20.04 or 22.04 release image (ubuntu:focal or ubuntu:jammy should suffice) VM on LXD (not container) 2. Observe uname -r to see that the -kvm variant of the ubuntu kernel is running 3. Check to see if BPFilter module is available: # find /lib/modules/$(uname -r)/ -type f -name '*bpfilter.ko' There are use cases where the BPF module is still used and it may be a while before users are able to transition to 24.04+ which I understand transitions to using the generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/2054155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051720]
I have the same issue as Nickolas, turning off the computer does not help. The device is also the same: Intel AX200 8087:0029. Mine is on a desktop motherboard. $ uname -r 6.7.4-arch1-1 $ lsusb | grep -i bluetooth Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth $ journalctl -b | grep -E -i bluetooth Feb 15 09:06:07 home bluetoothd[948]: Bluetooth management interface 1.22 initialized Feb 15 09:06:07 home systemd[1]: Started Bluetooth service. Feb 15 09:06:07 home systemd[1]: Reached target Bluetooth Support. Feb 15 09:06:07 home NetworkManager[1027]: [1707980767.6232] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so) Feb 15 09:06:08 home kernel: Bluetooth: hci0: Reading Intel version command failed (-110) Feb 15 09:06:08 home kernel: Bluetooth: hci0: command 0xfc05 tx timeout Same error was present on 6.7.3 and 6.7.2. I believe 6.6.9 was the last version where it worked fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
Still reproducible with 6.5.0-18-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054107] [NEW] Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy
Public bug reported: This morning, I installed the 6.5.0-18 updates on my Jammy system and rebooted. After rebooting, I'm unable to boot from my encrypted SSD. It reports that my passphrase is incorrect. Reverting back to 6.5.0-17 doesn't have this problem. ii linux-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.5-headers-6.5.0-18 6.5.0-18.18~22.04.1 all Header files related to Linux kernel version 6.5.0 ii linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.046.5.0.18.18~22.04.10 amd64Generic Linux kernel image ii linux-modules-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054107 Title: Unable to boot with encrypted drive with linux-image-6.5.0-18-generic on Jammy Status in linux package in Ubuntu: New Bug description: This morning, I installed the 6.5.0-18 updates on my Jammy system and rebooted. After rebooting, I'm unable to boot from my encrypted SSD. It reports that my passphrase is incorrect. Reverting back to 6.5.0-17 doesn't have this problem. ii linux-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-22.04 6.5.0.18.18~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.5-headers-6.5.0-18 6.5.0-18.18~22.04.1 all Header files related to Linux kernel version 6.5.0 ii linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.046.5.0.18.18~22.04.10 amd64Generic Linux kernel image ii linux-modules-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-18-generic 6.5.0-18.18~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
** Also affects: linux-oracle-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oracle-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oracle-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oracle-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oracle (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oracle-6.5 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oracle-6.5 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oracle-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-6.5 package in Ubuntu: Invalid Status in linux-oracle source package in Jammy: Invalid Status in linux-oracle-6.5 source package in Jammy: Fix Committed Status in linux-oracle source package in Mantic: Fix Committed Status in linux-oracle-6.5 source package in Mantic: Invalid Status in linux-oracle source package in Noble: In Progress Status in linux-oracle-6.5 source package in Noble: Invalid Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
Hi Sergio. I re-uploaded the patches with DEP-3 headers (Origin and Bug). Please see comment#7~9. Thanks~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
** Patch added: "jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5746640/+files/jammy.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
** Patch added: "mantic.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5746639/+files/mantic.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
** Patch added: "noble.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5746638/+files/noble.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)
This bug was fixed in the package linux-ibm - 6.8.0-1001.1 --- linux-ibm (6.8.0-1001.1) noble; urgency=medium * noble/linux-ibm: 6.8.0-1001.1 -proposed tracker (LP: #2052778) * Packaging resync (LP: #1786013) - debian.ibm/dkms-versions -- update from kernel-versions (main/d2024.02.07) * Miscellaneous Ubuntu changes - [packaging] update rust, clang and bindgen build-deps - [Config] updateconfigs following 6.8.0-7.7 rebase [ Ubuntu: 6.8.0-7.7 ] * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691) * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate ima_filter_rule from security_audit_rule - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure management of the sock security - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data structure. - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions with stacked LSMs - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in security_audit_rule_match - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx hook - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob in audit_context - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in security_ipc_getsecid - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM data - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in security_current_getsecid - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in security_inode_getsecid - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in audit_names - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new security_cred_getlsmblob LSM hook - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data from secid to lsmblob - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for audit data - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM context releaser - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in security_secid_to_secctx - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in security_lsmblob_to_secctx - SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in security_inode_getsecctx - SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in security_dentry_init_security - SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM: security_lsmblob_to_secctx module selection - SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp structure - SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple records in an audit_buffer - SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for multiple task security contexts - SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: multiple subject lsm values for netlabel - SAUCE: apparmor4.0.0 [26/87]: LSM stacking v39: Audit: Add record for multiple object contexts - SAUCE: apparmor4.0.0 [27/87]: LSM stacking v39: LSM: Remove unused lsmcontext_init() - SAUCE: apparmor4.0.0 [28/87]: LSM stacking v39: LSM: Improve logic in security_getprocattr - SAUCE: apparmor4.0.0 [29/87]: LSM stacking v39: LSM: secctx provider check on release - SAUCE: apparmor4.0.0 [31/87]: LSM stacking v39: LSM: Exclusive secmark usage - SAUCE: apparmor4.0.0 [32/87]: LSM stacking v39: LSM: Identify which LSM handles the context string - SAUCE: apparmor4.0.0 [33/87]: LSM stacking v39: AppArmor: Remove the exclusive flag - SAUCE: apparmor4.0.0 [34/87]: LSM stacking v39: LSM: Add mount opts blob size tracking - SAUCE: apparmor4.0.0 [35/87]: LSM stacking v39: LSM: allocate mnt_opts blobs instead of module specific data - SAUCE: apparmor4.0.0 [36/87]: LSM stacking v39: LSM: Infrastructure management of the key security blob - SAUCE: apparmor4.0.0 [37/87]: LSM stacking v39: LSM: Infrastructure management of the mnt_opts security blob - SAUCE: apparmor4.0.0 [38/87]: LSM stacking v39: LSM: Correct handling of ENOSYS in inode_setxattr - SAUCE: apparmor4.0.0 [39/87]: LSM stacking v39: LSM: Remove lsmblob scaffolding - SAUCE: apparmor4.0.0 [40/87]: LSM stacking v39: LSM: Allow reservation of netlabel - SAUCE: apparmor4.0.0 [41/87]: LSM stacking v39: LSM: restrict security_cred_getsecid() to a single LSM - SAUCE: apparmor4.0.0 [42/87]: LSM stacking v39: Smack: Remove LSM_FLAG_EXCLUSIVE - SAUCE: apparmor4.0.0 [43/87]: LSM stacking v39: UBUNTU: SAUCE: apparmor4.0.0
[Kernel-packages] [Bug 2054094] [NEW] linux-tools-common: man page of usbip[d] is misplaced
Public bug reported: Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced Status in linux package in Ubuntu: New Bug description: Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
Fix upstream as of v6.7-rc1. ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053251 Title: performance: Scheduler: ratelimit updating of load_avg Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2040026 [Description] Improve cache bouncing on tg->load_avg [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Sapphire Rapids Date HW is expected at Canonical: Component(s): Perf-Scalability Scheduler [Software Information] Target Version: 24.04 Target Kernel: TBD Commit IDs: 1528c661c24b sched/fair: Ratelimit update to tg->load_avg External Links: [Business Justification] [Testing guidance] [External ID] LFE-7154 Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0 https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
