[Kernel-packages] [Bug 2054190] Re: package linux-raspi-headers-5.15.0-1046 (not installed) failed to install/upgrade: »dpkg-deb --control«-Unterprozess gab den Fehlerwert 2 zurück
** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Invalid -- 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/2054190 Title: package linux-raspi-headers-5.15.0-1046 (not installed) failed to install/upgrade: »dpkg-deb --control«-Unterprozess gab den Fehlerwert 2 zurück Status in linux-raspi package in Ubuntu: Invalid Bug description: happened during distro upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-raspi-headers-5.15.0-1046 (not installed) ProcVersionSignature: Ubuntu 5.4.0-1101.113-raspi 5.4.257 Uname: Linux 5.4.0-1101-raspi armv7l ApportVersion: 2.20.11-0ubuntu82.5 Architecture: armhf CasperMD5CheckResult: unknown CloudArchitecture: armv7l CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Sat Feb 17 12:27:44 2024 ErrorMessage: »dpkg-deb --control«-Unterprozess gab den Fehlerwert 2 zurück ImageMediaBuild: 20220829.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-raspi Title: package linux-raspi-headers-5.15.0-1046 (not installed) failed to install/upgrade: »dpkg-deb --control«-Unterprozess gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to jammy on 2024-02-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2054190/+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 2054401] [NEW] package nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-545 package post-installation script subprocess returned error
Public bug reported: cant install nvidia driver. it works normally yesterday but today system cannot read my graphic card so i decided to reinstall the driver. after i deleted all the nvidia related packages and reinstall again, this error occurred and i cannot install the driver again. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 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: pass Date: Tue Feb 20 15:31:26 2024 ErrorMessage: installed nvidia-dkms-545 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-02-06 (14 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-545 Title: package nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-545 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-545 in Ubuntu. https://bugs.launchpad.net/bugs/2054401 Title: package nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-545 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: cant install nvidia driver. it works normally yesterday but today system cannot read my graphic card so i decided to reinstall the driver. after i deleted all the nvidia related packages and reinstall again, this error occurred and i cannot install the driver again. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 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: pass Date: Tue Feb 20 15:31:26 2024 ErrorMessage: installed nvidia-dkms-545 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-02-06 (14 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-545 Title: package nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-545 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-545/+bug/2054401/+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 2054394] [NEW] [RM RoM] linux-raspi (armhf)
Public bug reported: armhf is no longer a supported architecture for Raspberry Pi in Noble. Please remove armhf kernel binaries from Noble archive for linux-raspi and linux-meta-raspi. ** Affects: linux-meta-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-raspi (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Noble) Importance: Undecided Status: New ** Package changed: aac-tactics (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: linux-raspi (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-meta-raspi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - RM: linux-raspi [armhf] -- RoM; unsupported architecture + [RM RoM] linux-raspi (armhf) -- 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/2054394 Title: [RM RoM] linux-raspi (armhf) Status in linux-meta-raspi package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-meta-raspi source package in Noble: New Status in linux-raspi source package in Noble: New Bug description: armhf is no longer a supported architecture for Raspberry Pi in Noble. Please remove armhf kernel binaries from Noble archive for linux-raspi and linux-meta-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/2054394/+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 2054394] [NEW] RM: linux-raspi [armhf] -- RoM; unsupported architecture
You have been subscribed to a public bug: armhf is no longer a supported architecture for Raspberry Pi in Noble. Please remove armhf kernel binaries from Noble archive for linux-raspi and linux-meta-raspi. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- RM: linux-raspi [armhf] -- RoM; unsupported architecture https://bugs.launchpad.net/bugs/2054394 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054391] Re: Fix CPU thermal sensors enumeration
debdiff for Jammy. ** Patch added: "thermald_2.4.9-1ubuntu0.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2054391/+attachment/5747505/+files/thermald_2.4.9-1ubuntu0.5.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2054391 Title: Fix CPU thermal sensors enumeration Status in HWE Next: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Confirmed Bug description: [Impact] Some CPU sensors are not enumerated, this can make thermald deviates from the correct behavior of the CPU TDP. [Fix] Traverse all sensors under hwmon sysfs directory to make sure everything is enumerated. [Test] Check the output of thermald. Once the fix is in place, thermal zones that are previously omitted now shows up: [INFO]Zone 1: AMBF, Active:1 Bind:1 Sensor_cnt:1 [Where problems could occur] Since the new logic traverse the whole hwmon sysfs, the startup time can take slightly longer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054391/+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 2054391] [NEW] Fix CPU thermal sensors enumeration
Public bug reported: [Impact] Some CPU sensors are not enumerated, this can make thermald deviates from the correct behavior of the CPU TDP. [Fix] Traverse all sensors under hwmon sysfs directory to make sure everything is enumerated. [Test] Check the output of thermald. Once the fix is in place, thermal zones that are previously omitted now shows up: [INFO]Zone 1: AMBF, Active:1 Bind:1 Sensor_cnt:1 [Where problems could occur] Since the new logic traverse the whole hwmon sysfs, the startup time can take slightly longer. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: thermald (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: thermald (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-2050867 somerville ** Also affects: thermald (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu) Status: New => Fix Released ** Changed in: thermald (Ubuntu Jammy) Status: New => Confirmed ** Changed in: thermald (Ubuntu Jammy) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-2050867 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2054391 Title: Fix CPU thermal sensors enumeration Status in HWE Next: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Confirmed Bug description: [Impact] Some CPU sensors are not enumerated, this can make thermald deviates from the correct behavior of the CPU TDP. [Fix] Traverse all sensors under hwmon sysfs directory to make sure everything is enumerated. [Test] Check the output of thermald. Once the fix is in place, thermal zones that are previously omitted now shows up: [INFO]Zone 1: AMBF, Active:1 Bind:1 Sensor_cnt:1 [Where problems could occur] Since the new logic traverse the whole hwmon sysfs, the startup time can take slightly longer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054391/+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 2054374] [NEW] Lenovo Thinkbook 14-IML Elan Touchpad Not working
Public bug reported:
The touchpad in my laptop, Thinkbook 14-IML is not working. When i run the
acidump command the hardware is detected but the touchpad is not working, has
anybody faced this issue and if so can anyone tell me how to fix it?
My OS is Ubuntu 23.10
I expected my touchpad to work
It is not working
The hardware is fine as i have tested it with a windows os.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shrynshjn 1844 F wireplumber
/dev/snd/seq:shrynshjn 1823 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 10:02:38 2024
InstallationDate: Installed on 2023-08-04 (200 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:5415 IMC Networks Integrated Camera
Bus 001 Device 002: ID 04f3:0c4b Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 004: ID 0bda:c123 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=2963a34a-ac42-44e7-9ce6-aed4dbaa5237 ro i8042.nopnp=1 pci=nocrs 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-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-07 (105 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: CJCN41WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrCJCN41WW:bd03/13/2023:br1.41:efr1.34:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvr:skuLENOVO_MT_20RV_BU_idea_FM_LenovoThinkBook14-IML:
dmi.product.family: Lenovo ThinkBook 14-IML
dmi.product.name: 20RV
dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
dmi.product.version: Lenovo ThinkBook 14-IML
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054374
Title:
Lenovo Thinkbook 14-IML Elan Touchpad Not working
Status in linux package in Ubuntu:
New
Bug description:
The touchpad in my laptop, Thinkbook 14-IML is not working. When i run the
acidump command the hardware is detected but the touchpad is not working, has
anybody faced this issue and if so can anyone tell me how to fix it?
My OS is Ubuntu 23.10
I expected my touchpad to work
It is not working
The hardware is fine as i have tested it with a windows os.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shrynshjn 1844 F wireplumber
/dev/snd/seq:shrynshjn 1823 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 10:02:38 2024
InstallationDate: Installed on 2023-08-04 (200 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:5415 IMC Networks Integrated Camera
Bus 001 Device 002: ID 04f3:0c4b Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 004: ID 0bda:c123 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=2963a34a-ac42-44e7-9ce6-aed4dbaa5237 ro i8042.nopnp=1 pci=nocrs 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-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-07 (105 days ago)
dmi.bios.date: 03/13/2023
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
** Description changed: [ Impact ] - * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. + * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] - * QA will run certification testing on the KD240 platform - * Normal certification testing will be run on all other certified platforms + * QA will run certification testing on the KD240 platform + * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] - * Private launchpad bugs that contain the regressions: + * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054297] Re: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
*** 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/2054297 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Ubuntu 22.04.4 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 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: pass Date: Mon Feb 19 10:16:57 2024 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2022-08-17 (550 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato 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/2054297/+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 2054362] Re: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) 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/2054362 Title: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: Issue found on B-hwe-5.4.0-173.191~18.04.1 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 So this is not a regression, but a new test case. Test log: Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' === Ftrace unit tests === + initialize_ftrace + disable_tracing + echo 0 + reset_tracer + echo nop + reset_trigger + [ -d events/synthetic ] ... + read line ... + read line ... + reset_events_filter + read line ... + reset_ftrace_filter + [ ! -f set_ftrace_filter ] + echo + grep -v ^# set_ftrace_filter + read t + disable_events + echo 0 + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] [1] Test failure of registering kprobe on non unique symbol + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc + SYMBOL=name_show + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms + [ 14 -le 1 ] + echo p:test_non_unique name_show [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 I think we're probably missing https://github.com/torvalds/linux/commit/b022f0c7e404887a7c5229788fc99eff9f9a80d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2054362/+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 2054366] [NEW] Fix backported kria device tree changes
Public bug reported: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain the regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: High Assignee: Portia Stephens (portias) Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain the regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Works great. Tested, and a lot simpler, because there are builds for
Jammy, Mantic and Noble.
The command log for the updated work-around using the "Backports build PPA"
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/ubuntu_/ {print $1}' | sed
's/bpool\/BOOT\/ubuntu_//g')
zfs import rpool/ROOT/ubuntu_$UUID
zfs import bpool/BOOT/ubuntu_$UUID
zfs mount -a
mount --make-private --rbind /dev /mnt/dev
mount --make-private --rbind /proc /mnt/proc
mount --make-private --rbind /sys /mnt/sys
mount --make-private --rbind /run /mnt/run
chroot /mnt /bin/bash --login
mount -a
# Add the "Backports build PPA" for Grub2 2.12
add-apt-repository ppa:ubuntu-uefi-team/backports-build
apt update
# Install the Grub2 packages
apt install grub-efi-amd64 grub-efi-amd64-signed
# This will pull in some needed depends of Grub2 2.12~rc1 from the Nolble Repo's
# Reinstall/configure grub
grub-install --target=x86_64-efi --efi-directory=/boot/efi \
--bootloader-id=ubuntu --recheck --no-floppy
# Update the intramfs images
update-intramfs -c -k all
# Change the repo sources back to Jammy
cp /etc/apt/sources.list.jammy /etc/apt/sources.list
apt update
# Test: (Skip if snapshots already exist...)
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204a
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204b
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204c
zfs list -t snapshot
# Output:
#NAME USED AVAIL REFER MOUNTPOINT
#bpool/BOOT/ubuntu_2nlhsy@20230204a 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204b 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204c 0B - 298M -
# Exit Gracefully:
exit
mount | grep -v zfs | tac | awk '/\/mnt/ {print $3}' | \
xargs -i{} umount -lf {}
zpool export -a
reboot
>>>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051999
Title:
Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
snapshot of bpool.
Status in grub2 package in Ubuntu:
Confirmed
Status in grub2-unsigned package in Ubuntu:
Confirmed
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
There is an upstream Bug with Grub where if you create snapshots of bpool, it
results in a non-booting System. The problem was found to be an upstream Bug
with Grub2:
https://savannah.gnu.org/bugs/index.php?64297
Multiple Ubuntu 22.04.3 Users Affected:
https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
https://ubuntuforums.org/showthread.php?t=2494957
Brought up as an issue at OpenZFS:
https://github.com/openzfs/zfs/issues/13873
If you look at this comment
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c
Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
to Grub2 2.06 so that Users are not caught of in this bug for or
currently supported LTS Release.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: grub-efi-amd64 2.06-2ubuntu14.4
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Thu Feb 1 16:40:28 2024
InstallationDate: Installed on 2021-09-23 (861 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: grub2-unsigned
UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2054212] Re: System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works)
Thanks for your testing. ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu) ** Summary changed: - System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works) + [amdgpu] No signal on one monitor in kernel 6.5 (but 6.2 works) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: Incomplete => New -- 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/2054212 Title: [amdgpu] No signal on one monitor in kernel 6.5 (but 6.2 works) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: I have been running with kernel 6.2 without any problems. However, when the system upgraded to kernel 6.5, the system boots, but the monitor connected via HDMI has no signal. The system seems to think everything is OK, there are no errors in the Xorg log, xrandr shows both displays, so does inxi -Fxxxrz. Both monitors are connected via the AMD Radeon RX 6600 graphics card, the LG using DisplayPort, the Benq using HDMI. The Benq monitor will show "No Signal Detected" when the system boots and I log into the desktop. The LG monitor shows the correct display. The Display app will show both monitors as present, it's just that nothing is actually sent via the cable to the monitor. So the monitor doesn't get any signal. If I connect the Benq via DisplayPort and the LG via HDMI, then the LG shows "No Signal Detected". Comparing the Xorg.0.log files from using kernel 6.2 and 6.5, I don't see any errors or indications why the HDMI output isn't sending data. I've attached a tar.gz file with the 6.2 and 6.5 kernel results for the Xorg.0.log, the output of "inxi -Fxxxrz" and "xrandr -q". My current work around is to boot into kernel 6.2, but I would like to see the new kernel functioning properly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Feb 17 17:09:53 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 6.2.0-39-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:8809] InstallationDate: Installed on 2015-08-11 (3112 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-18-generic root=UUID=e6fe56b0-c6a6-48fd-9203-44e7395670df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2604 dmi.board.asset.tag: Default string dmi.board.name: PRIME B550-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2604:bd02/25/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage
[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
Link to this bug, just for package 'nvidia-driver-390': https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/+bug/2051436, which is a duplicate of : https://bugs.launchpad.net/ubuntu/jammy/+source/nvidia-graphics- drivers-390/+bug/2028165 For nvidia-driver-390, there is another work-around now, credit to Daniel Letzeisen (dtl131) with builds for mantic & Jammy, that works with the 6.5.0 series kernels until the patch is released: >>> sudo add-apt-repository ppa:dtl131/nvidiaexp sudo apt update sudo apt install nvidia-drivers-390 >>> I tested it and confirm it installs builds, and work fine with 6.5.0-17. -- 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/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: Confirmed Status in gcc-defaults package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+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 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
Been using 22.04 with Nvidia 390 for a long time now with no issues. Suddenly, I ran into the dkms problem with a kernel upgrade, Thankfully, I found the solution is to lock my kernel at 6.12. Hopefully I don't have to keep it that way for long! -- 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/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: Confirmed Status in gcc-defaults package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+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 2054212] Re: System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works)
I did a fresh install on a partition, made sure the 6.5 kernel was installed, installed the gnome desktop and wayland, then did the following: 1. Booted into kernel 6.5 with Xfce (using Xorg). Result was identical to before, the DisplayPort monitor is shown, but no input detected by the HDMI port monitor. 2. Booted into kernel 6.5 with Gnome and Wayland. Result identical, the DisplayPort monitor is shown, but no input detected by the HDMI port monitor. 3. Booted into kernel 6.5 with Gnome and Xorg. Result identical, the DisplayPort monitor is shown, but no input detected by the HDMI port monitor. No errors are shown that I can see in the logs. The system acts like both screens and monitors are present, I can configure via the Display app as if both are there, but the HDMI monitor never receives a signal. Since the same issue also occurs with Gnome and Wayland, I think that the issue is not as likely to be with Xfce, Gnome, Xorg or Wayland. That leaves the kernel and its modules as the likely suspects. Are there other things you'd like me to try? -- 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/2054212 Title: System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works) Status in linux-hwe-6.5 package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I have been running with kernel 6.2 without any problems. However, when the system upgraded to kernel 6.5, the system boots, but the monitor connected via HDMI has no signal. The system seems to think everything is OK, there are no errors in the Xorg log, xrandr shows both displays, so does inxi -Fxxxrz. Both monitors are connected via the AMD Radeon RX 6600 graphics card, the LG using DisplayPort, the Benq using HDMI. The Benq monitor will show "No Signal Detected" when the system boots and I log into the desktop. The LG monitor shows the correct display. The Display app will show both monitors as present, it's just that nothing is actually sent via the cable to the monitor. So the monitor doesn't get any signal. If I connect the Benq via DisplayPort and the LG via HDMI, then the LG shows "No Signal Detected". Comparing the Xorg.0.log files from using kernel 6.2 and 6.5, I don't see any errors or indications why the HDMI output isn't sending data. I've attached a tar.gz file with the 6.2 and 6.5 kernel results for the Xorg.0.log, the output of "inxi -Fxxxrz" and "xrandr -q". My current work around is to boot into kernel 6.2, but I would like to see the new kernel functioning properly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Feb 17 17:09:53 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 6.2.0-39-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:8809] InstallationDate: Installed on 2015-08-11 (3112 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-18-generic root=UUID=e6fe56b0-c6a6-48fd-9203-44e7395670df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2604 dmi.board.asset.tag: Default string dmi.board.name: PRIME B550-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
confirmed on 5.15.0-92 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054339] [NEW] package nvidia-kernel-common-535 535.154.05-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvi
Public bug reported: 6.5.0-18-generic #18~22.04.1-Ubuntu Tried to uninstall and reinstall cuda 12.2. It seems to have reinstalled ok. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-common-535 535.154.05-0ubuntu0.22.04.1 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 wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Feb 19 18:11:18 2024 ErrorMessage: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-535 535.86.10-0ubuntu1 InstallationDate: Installed on 2023-08-01 (202 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-kernel-common-535 535.154.05-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-535 535.86.10-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (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-535 in Ubuntu. https://bugs.launchpad.net/bugs/2054339 Title: package nvidia-kernel-common-535 535.154.05-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-535 535.86.10-0ubuntu1 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: 6.5.0-18-generic #18~22.04.1-Ubuntu Tried to uninstall and reinstall cuda 12.2. It seems to have reinstalled ok. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-common-535 535.154.05-0ubuntu0.22.04.1 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 wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Feb 19 18:11:18 2024 ErrorMessage: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-535 535.86.10-0ubuntu1 InstallationDate: Installed on 2023-08-01 (202 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-kernel-common-535 535.154.05-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-535 535.86.10-0ubuntu1 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-535/+bug/2054339/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
This bug was fixed in the package livecd-rootfs - 2.765.39 --- livecd-rootfs (2.765.39) jammy; urgency=medium [ dann frazier ] * Use flock to avoid races with systemd-udevd that cause loop device partitions to briefly disappear. (LP: #2045586) -- Michael Hudson-Doyle Mon, 19 Feb 2024 09:25:09 +1300 ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: Fix Committed => 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Released Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
Releasing early as we're in the middle of a point-release. Autopkgtests look good, the actual testing will happen on the RCs. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Released Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2054296] Re: Don't restrict to linux-laptop
This bug was fixed in the package protection-domain-mapper - 1.0-4ubuntu3 --- protection-domain-mapper (1.0-4ubuntu3) noble; urgency=medium * Remove linux-laptop kernel restriction for pd-mapper.service (LP: #2054296). -- Juerg Haefliger Mon, 05 Feb 2024 17:39:46 +0100 ** Changed in: protection-domain-mapper (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: Fix Released Status in qrtr package in Ubuntu: Fix Released Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2054296] Re: Don't restrict to linux-laptop
This bug was fixed in the package qrtr - 1.0-2ubuntu2 --- qrtr (1.0-2ubuntu2) noble; urgency=medium * Remove linux-laptop kernel restriction for qrtr-ns.service (LP: #2054296). -- Juerg Haefliger Mon, 05 Feb 2024 17:08:34 +0100 ** Changed in: qrtr (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: Fix Committed Status in qrtr package in Ubuntu: Fix Released Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2054325] Re: nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched
The error occurred with a monitor that was in a low power state. Rebooting with the monitor powered on showed no issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054325 Title: nouveau :05:00.0: timeout on HiFive SiFive Unmatched Status in linux-riscv-6.5 package in Ubuntu: New Bug description: Booting the SiFive Unmatched no output on the monitor was shown. Zillions of messages like the following were written: [ +0.007867] [ cut here ] [ +0.13] nouveau :05:00.0: timeout [ +0.000374] WARNING: CPU: 2 PID: 2028 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a [nouveau] [ +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundc> [ +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW 6.5.0-17-generic #17.1.1~22.04.1-Ubuntu [ +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT) [ +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper] [ +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006843] ra : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006368] epc : 026becf8 ra : 026becf8 sp : ffc80172b6c0 [ +0.08] gp : 822603c8 tp : ffd89ae05100 t0 : 820bd738 [ +0.06] t1 : t2 : 2d2d2d2d2d2d2d2d s0 : ffc80172b720 [ +0.05] s1 : ffd887482000 a0 : a1 : [ +0.06] a2 : a3 : a4 : [ +0.06] a5 : a6 : a7 : [ +0.05] s2 : 0007 s3 : ffd89d6d19b8 s4 : 00020022 [ +0.06] s5 : 0046 s6 : 0046 s7 : [ +0.06] s8 : 1000 s9 : 1000 s10: ffc80172b9c8 [ +0.06] s11: ffd887144000 t3 : t4 : [ +0.06] t5 : t6 : ffc80172b4b8 [ +0.04] status: 00020100 badaddr: 0058 cause: 0003 [ +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau] [ +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau] [ +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau] [ +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e [nouveau] [ +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau] [ +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau] [ +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau] [ +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau] [ +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau] [ +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau] [ +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau] [ +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau] [ +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau] [ +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau] [ +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau] [ +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 [nouveau] [ +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm] [ +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper] [ +0.24] [] drm_gem_vmap+0x1e/0x40 [drm] [ +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm] [ +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm] [ +0.001034] [] drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 [drm_kms_helper] [ +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 [drm_kms_helper] [ +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 [drm_kms_helper] [ +0.000272] [] process_one_work+0x1f6/0x390 [ +0.24] [] worker_thread+0x8a/0x456 [ +0.11] [] kthread+0xc4/0xe4 [ +0.12] [] ret_from_fork+0xe/0x20 [ +0.14] ---[ end trace ]--- [ +0.133717] nouveau :05:00.0: timer: stalled at [ +0.007740] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic riscv64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Mon Feb 19 15:47:49 2024 SourcePackage: linux-riscv-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-6.5/+bug/2054325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-ibm/5.15.0.1048.44)
All autopkgtests for the newly accepted linux-meta-ibm (5.15.0.1048.44) for jammy have finished running. The following regressions have been reported in tests triggered by the package: wireguard/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-ibm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054296] Re: Don't restrict to linux-laptop
** Changed in: qrtr (Ubuntu) Status: New => Fix Committed ** Changed in: protection-domain-mapper (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: Fix Committed Status in qrtr package in Ubuntu: Fix Committed Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
Hello Steve, or anyone else affected, Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.765.39 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Committed Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2051468] Re: Fix snapcraftyaml.yaml for jammy:linux-raspi
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051468 Title: Fix snapcraftyaml.yaml for jammy:linux-raspi Status in linux package in Ubuntu: New Status in linux-raspi package in Ubuntu: Confirmed Status in linux source package in Jammy: New Status in linux-raspi source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The in-tree snapcraft.yaml is stale. It does not produce any functional kernel snap for jammy:linux-raspi. [Fix] Replace the stale snapcraft.yaml with a newly implemented one. [Testcase] Build a pi-kernel with the following command: [for arm64] $ snapcraft --use-lxd --build-for=arm64 for armhf] $ snapcraft --use-lxd --build-for=armhf Then, install it to Ubuntu Core 22 running on a raspi board. $ snap install --dangerous Please note you need "grade: dangerous" for replacing the kernel using the local snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051468/+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 2054325] [NEW] nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched
Public bug reported: Booting the SiFive Unmatched no output on the monitor was shown. Zillions of messages like the following were written: [ +0.007867] [ cut here ] [ +0.13] nouveau :05:00.0: timeout [ +0.000374] WARNING: CPU: 2 PID: 2028 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a [nouveau] [ +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundc> [ +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW 6.5.0-17-generic #17.1.1~22.04.1-Ubuntu [ +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT) [ +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper] [ +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006843] ra : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006368] epc : 026becf8 ra : 026becf8 sp : ffc80172b6c0 [ +0.08] gp : 822603c8 tp : ffd89ae05100 t0 : 820bd738 [ +0.06] t1 : t2 : 2d2d2d2d2d2d2d2d s0 : ffc80172b720 [ +0.05] s1 : ffd887482000 a0 : a1 : [ +0.06] a2 : a3 : a4 : [ +0.06] a5 : a6 : a7 : [ +0.05] s2 : 0007 s3 : ffd89d6d19b8 s4 : 00020022 [ +0.06] s5 : 0046 s6 : 0046 s7 : [ +0.06] s8 : 1000 s9 : 1000 s10: ffc80172b9c8 [ +0.06] s11: ffd887144000 t3 : t4 : [ +0.06] t5 : t6 : ffc80172b4b8 [ +0.04] status: 00020100 badaddr: 0058 cause: 0003 [ +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau] [ +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau] [ +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau] [ +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e [nouveau] [ +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau] [ +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau] [ +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau] [ +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau] [ +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau] [ +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau] [ +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau] [ +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau] [ +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau] [ +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau] [ +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau] [ +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 [nouveau] [ +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm] [ +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper] [ +0.24] [] drm_gem_vmap+0x1e/0x40 [drm] [ +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm] [ +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm] [ +0.001034] [] drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 [drm_kms_helper] [ +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 [drm_kms_helper] [ +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 [drm_kms_helper] [ +0.000272] [] process_one_work+0x1f6/0x390 [ +0.24] [] worker_thread+0x8a/0x456 [ +0.11] [] kthread+0xc4/0xe4 [ +0.12] [] ret_from_fork+0xe/0x20 [ +0.14] ---[ end trace ]--- [ +0.133717] nouveau :05:00.0: timer: stalled at [ +0.007740] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic riscv64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Mon Feb 19 15:47:49 2024 SourcePackage: linux-riscv-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug jammy riscv64 uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054325 Title: nouveau :05:00.0: timeout on HiFive SiFive Unmatched Status in linux-riscv-6.5 package in Ubuntu: New Bug description: Booting the SiFive Unmatched no output on the monitor was shown. Zillions of messages like the following were written: [ +0.007867] [ cut here ] [ +0.13] nouveau :05:00.0: timeout [ +0.000374] WARNING: CPU: 2 PID: 2028 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35
[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms
This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu1.3 --- firmware-sof (2.2.6-1ubuntu1.3) mantic; urgency=medium * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090 - Add Intel SOF2.7.2 topology files. * Update soundwire topology files for Intel RPL platforms. LP: #2044330 - Update v2.2.8 topology files for Intel RPL platforms -- You-Sheng Yang Wed, 15 Nov 2023 23:32:40 +0800 ** Changed in: firmware-sof (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2044330 Title: Update soundwire topology files for Intel RPL platforms Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Committed Status in firmware-sof source package in Mantic: Fix Released Bug description: [Impact] Old RPL soundwire topology files are found to be muted when doing audio capture on left channel. [Fix] The commit from https://github.com/thesofproject/sof-bin/ is required. * https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d (Update v2.2.8 topology files for Intel RPL platforms) [Test Case] Test audio functions on Dell MayaBay RTL platforms. [Where problems could occur] Most topology files for Intel RPL are updated. Need more confirmation on Intel RPL platforms. [Other info] Lunar is skipped, as it'll be EOL soon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+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 2042090] Update Released
The verification of the Stable Release Update for firmware-sof has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu1.3
---
firmware-sof (2.2.6-1ubuntu1.3) mantic; urgency=medium
* Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
- Add Intel SOF2.7.2 topology files.
* Update soundwire topology files for Intel RPL platforms. LP: #2044330
- Update v2.2.8 topology files for Intel RPL platforms
-- You-Sheng Yang Wed, 15 Nov 2023
23:32:40 +0800
** Changed in: firmware-sof (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2044330] Update Released
The verification of the Stable Release Update for firmware-sof has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2044330 Title: Update soundwire topology files for Intel RPL platforms Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Committed Status in firmware-sof source package in Mantic: Fix Released Bug description: [Impact] Old RPL soundwire topology files are found to be muted when doing audio capture on left channel. [Fix] The commit from https://github.com/thesofproject/sof-bin/ is required. * https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d (Update v2.2.8 topology files for Intel RPL platforms) [Test Case] Test audio functions on Dell MayaBay RTL platforms. [Where problems could occur] Most topology files for Intel RPL are updated. Need more confirmation on Intel RPL platforms. [Other info] Lunar is skipped, as it'll be EOL soon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+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 2051468] Re: Fix snapcraftyaml.yaml for jammy:linux-raspi
** Description changed: SRU Justification: + [Impact] - Impact: + The in-tree snapcraft.yaml is stale. It does not produce any functional kernel + snap for jammy:linux-raspi. - The in-tree snapcraft.yaml is stale. It does not produce any functional kernel - snap for jammy:linux-raspi. + [Fix] + Replace the stale snapcraft.yaml with a newly implemented one. - Fix: - Replace the stale snapcraft.yaml with a newly implemented one. + [Testcase] + Build a pi-kernel with the following command: - Testcase: + [for arm64] -Build a pi-kernel with the following command: + $ snapcraft --use-lxd --build-for=arm64 -[for arm64] + [for armhf] - $ snapcraft --use-lxd --build-for=arm64 + $ snapcraft --use-lxd --build-for=armhf -[for armhf] + Then, install it to Ubuntu Core 22 running on a raspi board. - $ snapcraft --use-lxd --build-for=armhf + $ snap install --dangerous -Then, install it to Ubuntu Core 22 running on a raspi board. - - $ snap install --dangerous - -Please note you need "grade: dangerous" for replacing -the kernel using the local snap. + Please note you need "grade: dangerous" for replacing + the kernel using the local snap. ** Description changed: SRU Justification: [Impact] - The in-tree snapcraft.yaml is stale. It does not produce any functional kernel - snap for jammy:linux-raspi. + The in-tree snapcraft.yaml is stale. It does not produce any functional kernel + snap for jammy:linux-raspi. [Fix] - Replace the stale snapcraft.yaml with a newly implemented one. + + Replace the stale snapcraft.yaml with a newly implemented one. [Testcase] - Build a pi-kernel with the following command: + Build a pi-kernel with the following command: - [for arm64] + [for arm64] - $ snapcraft --use-lxd --build-for=arm64 + $ snapcraft --use-lxd --build-for=arm64 - [for armhf] + for armhf] - $ snapcraft --use-lxd --build-for=armhf + $ snapcraft --use-lxd --build-for=armhf - Then, install it to Ubuntu Core 22 running on a raspi board. + Then, install it to Ubuntu Core 22 running on a raspi board. - $ snap install --dangerous + $ snap install --dangerous - Please note you need "grade: dangerous" for replacing - the kernel using the local snap. + Please note you need "grade: dangerous" for replacing + the kernel using the local snap. -- 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/2051468 Title: Fix snapcraftyaml.yaml for jammy:linux-raspi Status in linux package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Bug description: SRU Justification: [Impact] The in-tree snapcraft.yaml is stale. It does not produce any functional kernel snap for jammy:linux-raspi. [Fix] Replace the stale snapcraft.yaml with a newly implemented one. [Testcase] Build a pi-kernel with the following command: [for arm64] $ snapcraft --use-lxd --build-for=arm64 for armhf] $ snapcraft --use-lxd --build-for=armhf Then, install it to Ubuntu Core 22 running on a raspi board. $ snap install --dangerous Please note you need "grade: dangerous" for replacing the kernel using the local snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051468/+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 2054296] Re: Don't restrict to linux-laptop
This was done for mantic release due to lack of time, and inability to verify if unrestricted access will be harmful in any way to any generic implementations. I hope we have time to test that this doesn't cause any issues, or failed unit starts on Pi Desktop and Qemu Desktop systmes which are not qcom based and that the service exits gracefully. If not, we agree to add more targetted conditionals for example test for a certain sysfs path to exist that indicates that a given booted system has qrtr / protection-domain-mapper compatible support. Let's upload this, test how these units behave on Pi and Qemu, and if needed improve the systemd unit with more targetted conditionals. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2052783] Re: Cannot detect external storage with Ubuntu Core 20 on CM4
config.txt is missing the '[cm4]' section which loads the dwc2 overlay. Note that this is IO board specific as the USB controller lives on the IO board and not the CM4. It's not a kernel problem, the image is broken. ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- 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/2052783 Title: Cannot detect external storage with Ubuntu Core 20 on CM4 Status in linux-raspi package in Ubuntu: Invalid Bug description: External USB storage is not detected when running the beta Ubuntu Core 20 image [0] on CM4. Same happens with the armhf image. The issue has been discovered using Checkbox - the failing test is usb/storage-detect [1]. Step to reproduce: - Provision the CM4 with [0] - Plug a USB storage device - Check such device is recognized and listed under /dev/sd* The issue is not present when running Core 22 [2] instead. [0] http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-stable/current/ubuntu-core-20-arm64+raspi.img.xz [1] https://github.com/canonical/checkbox/blob/d070c640bccf664c0882583c1dc0d3a0d1fdb7b8/providers/base/units/usb/usb.pxu#L311 [2] http://cdimage.ubuntu.com/ubuntu-core/22/dangerous-stable/pending/ubuntu-core-22-arm64+raspi.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2052783/+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 2052873] Re: package linux-intel-iotg-tools-common 5.15.0-1046.52 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-b
*** This bug is a duplicate of bug 2048183 *** https://bugs.launchpad.net/bugs/2048183 ** This bug has been marked a duplicate of bug 2048183 Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2052873 Title: package linux-intel-iotg-tools-common 5.15.0-1046.52 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-92.102 Status in linux-intel-iotg package in Ubuntu: New Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-image-5.15.0-92-generic linux-modules-5.15.0-92-generic linux-modules-extra-5.15.0-92-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: linux-headers-6.5.0-17-generic linux-hwe-6.5-headers-6.5.0-17 linux-image-5.15.0-94-generic linux-image-6.5.0-17-generic linux-modules-5.15.0-94-generic linux-modules-6.5.0-17-generic linux-modules-extra-5.15.0-94-generic linux-modules-extra-6.5.0-17-generic linux-modules-nvidia-535-6.5.0-17-generic linux-objects-nvidia-535-6.5.0-17-generic linux-signatures-nvidia-6.5.0-17-generic The following packages will be upgraded: code libde265-0 linux-cloud-tools-common linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 linux-image-generic linux-image-generic-hwe-22.04 linux-intel-iotg-tools-common linux-libc-dev linux-modules-nvidia-535-generic-hwe-22.04 linux-tools-common 11 upgraded, 11 newly installed, 0 to remove and 0 not upgraded. 10 standard LTS security updates Need to get 100 MB/391 MB of archives. After this operation, 1,340 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://packages.microsoft.com/repos/code stable/main amd64 code amd64 1.86.1-1707298119 [99.8 MB] Get:2 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-intel-iotg-tools-common all 5.15.0-1047.53 [297 kB] Fetched 100 MB in 5s (21.3 MB/s) Preconfiguring packages ... (Reading database ... 264771 files and directories currently installed.) Preparing to unpack .../00-code_1.86.1-1707298119_amd64.deb ... Unpacking code (1.86.1-1707298119) over (1.86.0-1706698139) ... Preparing to unpack .../01-libde265-0_1.0.8-1ubuntu0.1_amd64.deb ... Unpacking libde265-0:amd64 (1.0.8-1ubuntu0.1) over (1.0.8-1) ... Preparing to unpack .../02-linux-cloud-tools-common_5.15.0-94.104_all.deb ... Unpacking linux-cloud-tools-common (5.15.0-94.104) over (5.15.0-92.102) ... Selecting previously unselected package linux-modules-6.5.0-17-generic. Preparing to unpack .../03-linux-modules-6.5.0-17-generic_6.5.0-17.17~22.04.1_am d64.deb ... Unpacking linux-modules-6.5.0-17-generic (6.5.0-17.17~22.04.1) ... Selecting previously unselected package linux-image-6.5.0-17-generic. Preparing to unpack .../04-linux-image-6.5.0-17-generic_6.5.0-17.17~22.04.1_amd6 4.deb ... Unpacking linux-image-6.5.0-17-generic (6.5.0-17.17~22.04.1) ... Selecting previously unselected package linux-modules-extra-6.5.0-17-generic. Preparing to unpack .../05-linux-modules-extra-6.5.0-17-generic_6.5.0-17.17~22.0
[Kernel-packages] [Bug 2052874] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common
*** This bug is a duplicate of bug 2048183 *** https://bugs.launchpad.net/bugs/2048183 Do not install package linux-intel-iotg-tools-common, it should not exist. You only want linux-tools-common. ** This bug has been marked a duplicate of bug 2048183 Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages -- 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/2052874 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1047.53 Status in linux package in Ubuntu: New Bug description: $ sudo apt install linux-intel-iotg-tools-common linux-tools-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: hwdata The following NEW packages will be installed: hwdata linux-intel-iotg-tools-common linux-tools-common 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 649 kB of archives. After this operation, 2,011 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://in.archive.ubuntu.com/ubuntu jammy/main amd64 hwdata all 0.357-1 [26.6 kB] Get:2 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-intel-iotg-tools-common all 5.15.0-1047.53 [297 kB] Get:3 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-common all 5.15.0-94.104 [326 kB] Fetched 649 kB in 2s (346 kB/s) Selecting previously unselected package hwdata. (Reading database ... 294862 files and directories currently installed.) Preparing to unpack .../hwdata_0.357-1_all.deb ... Unpacking hwdata (0.357-1) ... Selecting previously unselected package linux-intel-iotg-tools-common. Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1047.53_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1047.53) ... Selecting previously unselected package linux-tools-common. Preparing to unpack .../linux-tools-common_5.15.0-94.104_all.deb ... Unpacking linux-tools-common (5.15.0-94.104) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0 -94.104_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-io tg-tools-common 5.15.0-1047.53 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-tools-common_5.15.0-94.104_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: hwdata:amd64: Install linux-intel-iotg-tools-common:amd64: Install linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: boul-iisc 2492 F pulseaudio /dev/snd/pcmC0D0p: boul-iisc 2492 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Sun Feb 11 07:45:32 2024 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1047.53 InstallationDate: Installed on 2024-01-11 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=bb015bf7-1f70-468a-9510-ceb36baafb05 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1047.53 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01WV13 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd12/18/2023:br1.10:efr1.4:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn01WV13:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB:
[Kernel-packages] [Bug 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
** Tags added: kern-9233 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2053603] Re: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subp
/etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-18-generic Error! Could not locate dkms.conf file. File: /var/lib/dkms/amdgpu/6.2.4-1666569.22.04/source/dkms.conf does not exist. ...fail! -- 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/2053603 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: Invalid Bug description: Performed simple update & upgrade - issue encountered when processing: linux-headers-6.5.0-18-generic linux-headers-generic-hwe-22.04 linux-generic-hwe-22.04 linux-image-6.5.0-18-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-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 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 23:34:42 2024 ErrorMessage: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 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-hwe-6.5 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2053603/+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 2053603] Re: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subp
You have a broken and unusupported DKMS modules installed that breaks the kernel headers installation. Try: $ dkms remove amdgpu/6.2.4-1666569.22.04 ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Invalid -- 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/2053603 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: Invalid Bug description: Performed simple update & upgrade - issue encountered when processing: linux-headers-6.5.0-18-generic linux-headers-generic-hwe-22.04 linux-generic-hwe-22.04 linux-image-6.5.0-18-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-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 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 23:34:42 2024 ErrorMessage: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 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-hwe-6.5 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2053603/+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 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
** Tags added: kern-9232 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in linux-firmware package in Ubuntu: New Bug description: Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2053277/+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 2053147] Re: CONFIG_EFI_STUB support disabled since 6.5.0-1002.2
We do not support EFI with raspi hence it was turned off. It unnecessarily blows up the size of the kernel and enlarges its attack surface. ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- 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/2053147 Title: CONFIG_EFI_STUB support disabled since 6.5.0-1002.2 Status in linux-raspi package in Ubuntu: Invalid Bug description: Looks like since commmit 0d02ca7853f4e487ff8b912b0d1d43ceb31a528b (https://git.launchpad.net/ubuntu/+source/linux- raspi/commit/?h=applied/ubuntu/devel=0d02ca7853f4e487ff8b912b0d1d43ceb31a528b) The support for EFI in the kernel config was disabled with no mention of why: """ - [Config] raspi: Set EFI=n """ This disables support for CONFIG_EFI_STUB which means that the kernel cannot be loaded via EFI directly. Any reasons for this? We are booting RPI by setting u-boot to launch in EFI mode, which runs grub.efi and then we load our entries from there, but this totally breaks support for that. This worked until the previous kernel version with no issues that we could find. Is there anything we can do to revert this and re-enable this option int he kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2053147/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
This bug is awaiting verification that the linux-azure/5.15.0-1058.66 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-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053152 Title: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+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 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034983 [Description] When running UnixBench/shell1 cases, we observed high false sharing for accessing i_mmap against i_mmap_rwsem. The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid this false sharing problem. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): DNP Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: TBD Commit IDs: aee79d4e5271 fs/address_space: add alignment padding for i_map and i_mmap_rwsem to mitigate a false sharing. External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5159 Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8 https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
I could confirm that the patches are present in linux-bluefield and linux-raspi: 6e7ff802c7b10 and b4ebbcfebd4d3 ** Tags removed: verification-done-jammy-linux-azure verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-raspi ** Tags added: verification-done-jammy-linux-bluefield verification-done-jammy-linux-raspi verification-needed-jammy-linux-azure ** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
** Description changed: + [Impact] + Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz - ^ ^^^ + ^ ^^^ Looks wrong :) + + [Test Case] + + $ sudo apt install linux-tools-common + $ man usbip + No manual entry for usbip + + [Where Problems Could Occur] + + Manpage packaging change, no runtime impact expected. + + [Additional Description] + 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 + 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 + 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. ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** No longer affects: linux (Ubuntu Focal) ** Also affects: linux (Ubuntu Focal) 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/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Mantic: New Status in linux source package in Noble: Confirmed Bug description: [Impact] Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) [Test Case] $ sudo apt install linux-tools-common $ man usbip No manual entry for usbip [Where Problems Could Occur] Manpage packaging change, no runtime impact expected. [Additional Description] 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
[Kernel-packages] [Bug 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
Yes, is wrong. Thanks for the report! ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced Status in linux package in Ubuntu: Confirmed 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 2054296] Re: Don't restrict to linux-laptop
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Status update: https://lists.freedesktop.org/archives/dri-devel/2024-February/442066.html So once merged, the fix will need to be manually enabled by: FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER_CONDITION = "splash" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+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 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+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 2052662] Re: move_mount mediation does not detect if source is detached
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052662 Title: move_mount mediation does not detect if source is detached Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: Impact: In AppArmor mediation, detached mounts are appearing as / when applying mount mediation, which is incorrect and leads to bad AppArmor policy being generated. In addition, the move_mount mediation is not being advertised to userspace, which denies the applications the possibility to respond accordingly. Fix: Fixed upstream by commit 8026e40608b4d552216d2a818ca7080a4264bb44 by preventing move_mont from applying the attach_disconnected flag. Testcase: Check if move_mount file is available in securityfs: $ cat /sys/kernel/security/apparmor/features/mount/move_mount detached Run upstream AppArmor mount tests, which include move_mount mediation. https://gitlab.com/apparmor/apparmor/-/blob/master/tests/regression/apparmor/mount.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052662/+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 2053212] Re: Jammy update: v5.15.146 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053212 Title: Jammy update: v5.15.146 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.146 upstream stable release from git://git.kernel.org/ ARM: dts: dra7: Fix DRA7 L3 NoC node register size ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init reset: Fix crash when freeing non-existent optional resets s390/vx: fix save/restore of fpu kernel context wifi: iwlwifi: pcie: add another missing bh-disable for rxq->lock wifi: mac80211: mesh_plink: fix matches_local logic net/mlx5e: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list() net/mlx5e: fix a potential double-free in fs_udp_create_groups net/mlx5: Fix fw tracer first block check net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors net: sched: ife: fix potential use-after-free ethernet: atheros: fix a memleak in atl1e_setup_ring_resources net/rose: fix races in rose_kill_by_device() net: mana: select PAGE_POOL net: check vlan filter feature in vlan_vids_add_by_dev() and vlan_vids_del_by_dev() afs: Fix the dynamic root's d_delete to always delete unused dentries afs: Fix dynamic root lookup DNS check net: check dev->gso_max_size in gso_features_check() keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry keys, dns: Fix missing size check of V1 server-list header keys, dns: Fix size check of V1 server-list header afs: Fix overwriting of result of DNS query afs: Use refcount_t rather than atomic_t afs: Fix use-after-free due to get/remove race in volume tree ASoC: hdmi-codec: fix missing report for jack initial status i2c: aspeed: Handle the coalesced stop conditions with the start conditions. pinctrl: at91-pio4: use dedicated lock class for IRQ gpiolib: cdev: add gpio_device locking wrapper around gpio_ioctl() ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE drm/i915/mtl: limit second scaler vertical scaling in ver >= 14 drm/i915: Relocate intel_atomic_setup_scalers() drm/i915: Fix intel_atomic_setup_scalers() plane_state handling smb: client: fix NULL deref in asn1_ber_decoder() smb: client: fix OOB in smb2_query_reparse_point() interconnect: Treat xlate() returning NULL node as an error iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw Input: ipaq-micro-keys - add error handling for devm_kmemdup scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() iio: triggered-buffer: prevent possible freeing of wrong buffer ALSA: usb-audio: Increase delay in MOTU M quirk wifi: cfg80211: Add my certificate wifi: cfg80211: fix certs build to not depend on file order USB: serial: ftdi_sio: update Actisense PIDs constant names USB: serial: option: add Quectel EG912Y module support USB: serial: option: add Foxconn T99W265 with new baseline USB: serial: option: add Quectel RM500Q R13 firmware support Bluetooth: hci_event: Fix not checking if HCI_OP_INQUIRY has been sent Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE Input: soc_button_array - add mapping for airplane mode button net: 9p: avoid freeing uninit memory in p9pdu_vreadf net: rfkill: gpio: set GPIO direction net: ks8851: Fix TX stall caused by TX buffer overrun dt-bindings: nvmem: mxs-ocotp: Document fsl,ocotp scsi: core: Always send batch on reset or error handling command tracing / synthetic: Disable events after testing in synth_event_gen_test_init() bus: ti-sysc: Flush posted write only after srst_udelay gpio: dwapb: mask/unmask IRQ when disable/enale it lib/vsprintf: Fix %pfwf when current node refcount == 0 KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy x86/alternatives: Sync core before enabling interrupts fuse: share lookup state between submount and its parent ksmbd: have a dependency on cifs ARC4 ksmbd: set epoch in create context v2 lease ksmbd: set v2 lease capability ksmbd: downgrade RWH lease caching state to RH for directory ksmbd: send v2 lease break
[Kernel-packages] [Bug 2054297] Re: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2054297 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Ubuntu 22.04.4 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 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: pass Date: Mon Feb 19 10:16:57 2024 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2022-08-17 (550 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato 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/2054297/+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 2054297] [NEW] package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Public bug reported: Ubuntu 22.04.4 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 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: pass Date: Mon Feb 19 10:16:57 2024 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2022-08-17 (550 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato 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/2054297 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Ubuntu 22.04.4 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 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: pass Date: Mon Feb 19 10:16:57 2024 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2022-08-17 (550 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato 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/2054297/+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 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
No PPC for raspi and oracle. ** Tags removed: verification-needed-focal-linux-oracle verification-needed-focal-linux-raspi ** Tags added: verification-done-focal-linux-oracle verification-done-focal-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+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 2054296] Re: Don't restrict to linux-laptop
** Patch added: "protection-domain-mapper_1.0-4ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+attachment/5747229/+files/protection-domain-mapper_1.0-4ubuntu3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2054296] [NEW] Don't restrict to linux-laptop
Public bug reported: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. ** Affects: protection-domain-mapper (Ubuntu) Importance: Undecided Status: New ** Affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Also affects: protection-domain-mapper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2054296] Re: Don't restrict to linux-laptop
** Patch added: "qrtr_1.0-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+attachment/5747228/+files/qrtr_1.0-2ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2051468] Re: Fix snapcraftyaml.yaml for jammy:linux-raspi
** Description changed: - jammy:linux-raspi has snapcraft.yaml. + SRU Justification: - This file was added more than a decade ago. It does not produce any - sensible kernel snap. + + Impact: + + The in-tree snapcraft.yaml is stale. It does not produce any functional kernel + snap for jammy:linux-raspi. + + Fix: + Replace the stale snapcraft.yaml with a newly implemented one. + + + Testcase: + +Build a pi-kernel with the following command: + +[for arm64] + + $ snapcraft --use-lxd --build-for=arm64 + +[for armhf] + + $ snapcraft --use-lxd --build-for=armhf + +Then, install it to Ubuntu Core 22 running on a raspi board. + + $ snap install --dangerous + +Please note you need "grade: dangerous" for replacing +the kernel using the local snap. -- 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/2051468 Title: Fix snapcraftyaml.yaml for jammy:linux-raspi Status in linux package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Bug description: SRU Justification: Impact: The in-tree snapcraft.yaml is stale. It does not produce any functional kernel snap for jammy:linux-raspi. Fix: Replace the stale snapcraft.yaml with a newly implemented one. Testcase: Build a pi-kernel with the following command: [for arm64] $ snapcraft --use-lxd --build-for=arm64 [for armhf] $ snapcraft --use-lxd --build-for=armhf Then, install it to Ubuntu Core 22 running on a raspi board. $ snap install --dangerous Please note you need "grade: dangerous" for replacing the kernel using the local snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051468/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
Verified on the OEM platform, and looks positive on my end. ** Tags added: verification-done-jammy-linux-firmware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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
