[Kernel-packages] [Bug 2036149] Re: BlueZ release 5.70
** Changed in: bluez (Ubuntu) Milestone: None => ubuntu-24.01 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2036149 Title: BlueZ release 5.70 Status in bluez package in Ubuntu: In Progress Bug description: Update to BlueZ 5.70 (or later) in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2036149/+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 2013325] Re: net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels (TXTIME rel returned '', expected 'OK')
j/starfive-6.2.0-1008.9~22.04.1: Case ICMPv4 - TXTIME rel returned '', expected 'OK' Case UDPv6 - TXTIME rel returned '', expected 'OK' Case ICMPv6 - TXTIME rel returned '', expected 'OK' Case RAWv6 - TXTIME rel returned '', expected 'OK' ** Tags added: jammy sru-20231002 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2013325 Title: net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels (TXTIME rel returned '', expected 'OK') Status in ubuntu-kernel-tests: New Status in linux-allwinner package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux-starfive package in Ubuntu: New Status in linux-allwinner source package in Kinetic: New Status in linux-riscv source package in Kinetic: New Status in linux-starfive source package in Kinetic: New Bug description: Issue found on Kinetic 5.19 RISCV kernels: * kinetic/linux-allwinner/5.19.0-1009.9 # selftests: net: cmsg_time.sh # Case UDPv4 - TXTIME rel returned '', expected 'OK' # Case ICMPv4 - TXTIME rel returned '', expected 'OK' # Case UDPv6 - TXTIME rel returned '', expected 'OK' # Case ICMPv6 - TXTIME rel returned '', expected 'OK' # Case RAWv6 - TXTIME rel returned '', expected 'OK' # FAIL - 5/36 cases failed not ok 1 selftests: net: cmsg_time.sh # exit=1 * kinetic/linux-riscv/5.19.0-1015.16 # selftests: net: cmsg_time.sh # Case ICMPv4 - TXTIME rel returned '', expected 'OK' # Case UDPv6 - TXTIME rel returned '', expected 'OK' # Case ICMPv6 - TXTIME rel returned '', expected 'OK' # Case RAWv6 - TXTIME rel returned '', expected 'OK' # FAIL - 4/36 cases failed not ok 1 selftests: net: cmsg_time.sh # exit=1 * kinetic/linux-starfive/5.19.0-1014.16 # selftests: net: cmsg_time.sh # Case UDPv4 - TXTIME rel returned '', expected 'OK' # Case ICMPv4 - TXTIME rel returned '', expected 'OK' # Case UDPv6 - TXTIME rel returned '', expected 'OK' # Case ICMPv6 - TXTIME rel returned '', expected 'OK' # Case RAWv6 - TXTIME rel returned '', expected 'OK' # FAIL - 5/36 cases failed not ok 1 selftests: net: cmsg_time.sh # exit=1 This is only affecting RISCV64 kernels, it does not affect kinetic generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2013325/+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 2036577] Re: [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec.
Closing lunar as invalid. This has nothing to do with the 'lunar' package, and if the intention is to fix in the Lunar series, it should no longer be needed and we should target for newer releases. ** Changed in: lunar (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036577 Title: [Mediatek] mt8195-demo: Fix hardware watchdog reset at boot time around 10 sec. Status in linux package in Ubuntu: Incomplete Status in lunar package in Ubuntu: Invalid Bug description: [Impact] hardware reset during boot time. [Fix] Compare to generic kernel config for arm64 file: arch/arm64/configs/defconfig The CONFIG_MEDIATEK_WATCHDOG should be enabled "built-in" in generic kernel settings. CONFIG_MEDIATEK_WATCHDOG=y I've discovered that the module mtk_wdt.ko (CONFIG_MEDIATEK_WATCHDOG) must be set as built-in to prevent the system from encountering a hardware reset during the boot process. I've tried building it as a module and installing it into initrd, and I've also attempted to set softdep for it. However, I still can't find it being probed in the initcall debug dump. The system also reboots around 10 seconds into the boot time. After setting CONFIG_MEDIATEK_WATCHDOG=y, the hardware reset issue was resolved and the system was able to boot into the console. [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036577/+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 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU
The required patches are in 6.5.7 and 6.5.8 stable kernels, so Mantic will soon include the fix. ** Changed in: linux (Ubuntu Mantic) Status: In Progress => 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/2038981 Title: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] With ADM 6300 GPU, there is no external output when plug in a DP monitor after the monitor went to sleep [Fix] Mario provides a patch to fix the issue https://patchwork.kernel.org/project/linux-usb/list/?series=790399 And also below commit is required 134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port [Test case] 1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card 2. Unplug the DP cable and wait the monitor sleeps 3. Plug in the DP cable again and it should wake up the monitor correctly and output the screen to the monitor [Where problems could occur] The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, and UCSI patch try to set the correct power supply scope which should do no harm to the existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038981/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Thanks for investigating this, Cascardo. I agree that option 3 is likely
the best path forward, either via changing our kernel config defaults or
adjusting the sysctl defaults via the procps package. For reference the
adjustable sysctl setting is vm.mmap_rnd_compat_bits.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Incomplete
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 2036149] Re: BlueZ release 5.70
** Changed in: bluez (Ubuntu) Status: Triaged => In Progress ** Tags added: noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2036149 Title: BlueZ release 5.70 Status in bluez package in Ubuntu: In Progress Bug description: Update to BlueZ 5.70 (or later) in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2036149/+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 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- 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/2038981 Title: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] With ADM 6300 GPU, there is no external output when plug in a DP monitor after the monitor went to sleep [Fix] Mario provides a patch to fix the issue https://patchwork.kernel.org/project/linux-usb/list/?series=790399 And also below commit is required 134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port [Test case] 1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card 2. Unplug the DP cable and wait the monitor sleeps 3. Plug in the DP cable again and it should wake up the monitor correctly and output the screen to the monitor [Where problems could occur] The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, and UCSI patch try to set the correct power supply scope which should do no harm to the existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038981/+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 2033150] Re: USB Hub devices aren't recognized properly in 6.2.0-26
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2033150 Title: USB Hub devices aren't recognized properly in 6.2.0-26 Status in linux package in Ubuntu: Expired Bug description: It took some time to realize, but my powered USB hubs no longer lit up (they have indicators for what is plugged in). Flash drives would work, but then I noticed ADB and fastboot would intermittently fail and not function quite properly. Attempted to update to the latest versions did not fix. Rolling back to kernel 6.2.0-25 however all the sudden made all my USB problems go away. My webcams were recognized again (didn't realize at first they weren't working), ADB works reliably again, etc. I'm not sure what information would be helpful in diagnosing this, let me know what I could pull or do that would help. Obviously it's easy enough to go between the two kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033150/+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 2040948] Re: USB stick can't be detected
** Also affects: linux-signed-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2040948
Title:
USB stick can't be detected
Status in linux-signed-hwe-5.15 package in Ubuntu:
New
Status in linux-signed-oem-6.1 package in Ubuntu:
New
Bug description:
[Summary]
During SRU testing, I found some of devices failed to run the usb
test, when I re-plugged the usb stick, it can be detected, but after
rebooting, usb stick is gone again.
I did some further checks and found that If I power cycle the device,
it can be detected again.
It seems to happen on the device plugged with a Sandisk usb stick.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Thu Oct 26 10:37:58 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
InstallationDate: Installed on 2023-09-04 (51 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-oem-6.1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2040948/+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 2040948] Re: USB stick can't be detected
** Tags added: cert-sru
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2040948
Title:
USB stick can't be detected
Status in linux-signed-oem-6.1 package in Ubuntu:
New
Bug description:
[Summary]
During SRU testing, I found some of devices failed to run the usb
test, when I re-plugged the usb stick, it can be detected, but after
rebooting, usb stick is gone again.
I did some further checks and found that If I power cycle the device,
it can be detected again.
It seems to happen on the device plugged with a Sandisk usb stick.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Thu Oct 26 10:37:58 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
InstallationDate: Installed on 2023-09-04 (51 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-oem-6.1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.1/+bug/2040948/+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 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU
** Tags added: originate-from-2033246 -- 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/2038981 Title: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] With ADM 6300 GPU, there is no external output when plug in a DP monitor after the monitor went to sleep [Fix] Mario provides a patch to fix the issue https://patchwork.kernel.org/project/linux-usb/list/?series=790399 And also below commit is required 134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port [Test case] 1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card 2. Unplug the DP cable and wait the monitor sleeps 3. Plug in the DP cable again and it should wake up the monitor correctly and output the screen to the monitor [Where problems could occur] The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, and UCSI patch try to set the correct power supply scope which should do no harm to the existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038981/+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 2040948] [NEW] USB stick can't be detected
Public bug reported:
[Summary]
During SRU testing, I found some of devices failed to run the usb test,
when I re-plugged the usb stick, it can be detected, but after
rebooting, usb stick is gone again.
I did some further checks and found that If I power cycle the device, it
can be detected again.
It seems to happen on the device plugged with a Sandisk usb stick.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Thu Oct 26 10:37:58 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
InstallationDate: Installed on 2023-09-04 (51 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-oem-6.1
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-signed-oem-6.1 (Ubuntu)
Importance: Medium
Assignee: Kai-Heng Feng (kaihengfeng)
Status: New
** Tags: amd64 apport-bug jammy package-from-proposed
** Changed in: linux-signed-oem-6.1 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-signed-oem-6.1 (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2040948
Title:
USB stick can't be detected
Status in linux-signed-oem-6.1 package in Ubuntu:
New
Bug description:
[Summary]
During SRU testing, I found some of devices failed to run the usb
test, when I re-plugged the usb stick, it can be detected, but after
rebooting, usb stick is gone again.
I did some further checks and found that If I power cycle the device,
it can be detected again.
It seems to happen on the device plugged with a Sandisk usb stick.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Thu Oct 26 10:37:58 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
InstallationDate: Installed on 2023-09-04 (51 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-oem-6.1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.1/+bug/2040948/+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 2037224] Re: Multiple RTL8851BE BT stability issues
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.2
---
linux-firmware (20230919.git3672ccab-0ubuntu2.2) mantic; urgency=medium
* Multiple RTL8851BE BT stability issues (LP: #2037224)
- rtl_bt: Update RTL8851B BT USB firmware to 0x048A_D230
-- Juerg Haefliger Tue, 10 Oct 2023
11:48:12 +0200
** Changed in: linux-firmware (Ubuntu)
Status: Fix Committed => Fix Released
--
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/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are multiple stability issues for RTL8851B.
Issue-1:
After disabling BT and leaving it idle for a period, manually turning on the
RTL8851BE will fail.
Issue-2:
Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
either failure to read device descriptors:
usb 1-14: device descriptor read/64, error -71
or tx command timeout:
Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout
[Fix]
Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
0x048A_D230").
[Test Case]
$ checkbox-cli run
com.canonical.plainbox::suspend/suspend_advanced_auto
[Where problems could occur]
This updates opaque firmware blobs, so it could bring further stability issues
and/or power consumption changes.
[Other Info]
While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
and mantic are nominated for fix.
= original bug report ==
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2040657 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: jammy ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: Incomplete Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 1782934] Re: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic
This bug is over 5 years old now so it would probably be helpful to get a fresh bug report from 22.04 if you're experiencing something similar. Please run: ubuntu-bug linux -- 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/1782934 Title: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic Status in linux package in Ubuntu: Confirmed Bug description: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post- install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic (edited to add: this SHOULD have read '4.15.0-29-generic'). Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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 2040120] Re: Kernel configs deviate from generic kernel
** Changed in: linux-gke (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2040120 Title: Kernel configs deviate from generic kernel Status in linux-gke package in Ubuntu: Incomplete Status in linux-gke source package in Jammy: Confirmed Bug description: After doing the config to annotation migration it became apparent that during previous cranks generic kernel configs were not correctly updated in the derivative linux-gke kernel. For the time being, the gke annotations file has been updated to match the configs prior to annotation migrations. These configs should be evaluated and updated in linux-gke to match the generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2040120/+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 2034705] Re: efivar fails to read variables
Upstream has accepted the patch and added it to the v6.5 stable series. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.5.9&id=63565e1cbfb59da059dd322054840eb6a0019e65 ** Changed in: linux-meta (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034705 Title: efivar fails to read variables Status in efivar package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: In Progress Bug description: On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel 6.5.0-2-generic we see this output: root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/ AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c root@ubuntu-server:/var# efivar -l efivar: error listing variables: Function not implemented root@ubuntu-server:/var# efibootmgr -v EFI variables are not supported on this system. Expected behavior would be to display the variables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
I am able to connect with the unifying receiver which is good enough for now. It'd still be nice for regular bluetooth to work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: New Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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
Re: [Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Thank you so much Quinten and every helper ! I have Ubuntu 22.04 on Lenovo V15 G4 When patching it returns "*can't find file to patch at input line 15* *From 7a62c5f716bb3a0dd119d6a6eb5994d906ffbb32 Mon Sep 17 00:00:00 2001From: Hans de Goede >Date: Mon, 16 Oct 2023 22:40:47 +0200Subject: [PATCH] i8259 hack allow mapping of legacy IRQs with NULL PICSigned-off-by: Hans de Goede >--- arch/x86/kernel/i8259.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)diff --git a/arch/x86/kernel/i8259.c b/arch/x86/kernel/i8259.cindex 30a55207c000..e34b2c884d70 100644--- a/arch/x86/kernel/i8259.c+++ b/arch/x86/kernel/i8259.c*" which is strange as line 15 reads (in red in the file) "*@@ -394,7 +394,7 @@ static int legacy_pic_probe(void)"* On Wed, 25 Oct 2023 at 20:26, Quinten Van Ginderen < 2034...@bugs.launchpad.net> wrote: > Hi Endre, > > I have kinda made progress in regards of being able to patch and install > a kernel. > > First i'ill walk you through my assumptions, > > 1) you have the laptop and installed a debian/ubuntu based distro but the > keyboard and touchpad don't work. > 2) there is at least 64Gb of disk space available > 3) you have the option of using the root user. > > so first off. > Download the patch from above. > https://bugzilla.kernel.org/attachment.cgi?id=305236 > run uname -r, this will return your kernel version, download the closest > matching version to that version from kernel.org, but remeber only > download later versions, so you are not using a version older than your > current kernel. > > then run sudo apt install build-essential libncurses5-dev libssl-dev > flex libelf-dev bc bison gcc make dwarves zstd > > then unzip the downloaded kernel and enter it as root. > appply the patch by running the following as roon in the unzipped kernel > directory: patch -p1 < path_to_patchfile > > it will return something notifying it's ready. > > then copy over the latest kernel config to the unzipped kernel this can > be found in the /boot directory mine is /boot/config-6.1.59 for example. > this is beceause i patched up the old kernel to this one. cp -r > /boot/.conf .config replace latestkernel with the one you > find in /boot > > then run make menuconfig as the root in the unzipped kernel. > immediatly just hit save and exit > > run the following 2 lines as the root user in the unzipped kernel > individually :) (been there done that) > > scripts/config --disable SYSTEM_TRUSTED_KEYS > scripts/config --disable SYSTEM_REVOCATION_KEYS > > then run make -j 16 > > and just hit enter whenever it prompts something, oh and get a coffee or > a tea this is going to take a while :)) > > when it completes, run as root in the unzipped kernel: make modules_install > should'nt take too long > whenever it completes run make install > let it complete, > congrats kernel installed, > run; update-grub > verify that the version of the kernel is somewhere in it's output. > > reboot, and pray. > if it boots up, run a uname -r, try it with the laptop's builtin keyboard. > > if you've made it this far congrats. > you have now patched and installed a kernel. > > above works on any distro i've tried. (zorin16 debian12 ubuntu2204) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2034477 > > Title: > Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop > > Status in ideapad-laptop: > New > Status in libinput package in Ubuntu: > Confirmed > Status in linux-signed-hwe-6.2 package in Ubuntu: > Confirmed > Status in linux-signed-oem-6.5 package in Ubuntu: > Confirmed > Status in Fedora: > New > > Bug description: > Hello. > > Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was > installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) > laptop and it was noticed that keyboard, touchpad and microphone are > not working. The keyboard and touchpad work fine in BIOS setup and > till GRUB (command line). It was found that when external devices such > as keyboard, mouse and microphone are connected through USB and 3.5 > jack, respectively, these work just fine. To confirm these are not > hardware problems, Microsoft Windows 11 (Home) was installed in > another disk partition and observed all these working alright. Hence a > bug is being reported to draw attention of the concerned team and I > request them to refer this issue and do the needful at the earliest. > > Regards, > Pradip Kumar Das > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 > ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 > Uname: Linux 6.2.0-32-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Wed Sep 6 08:04:42 2023 > InstallationDate: Installed on 2023-08-14 (22 days ago) > InstallationMedia: Ubuntu 22.
[Kernel-packages] [Bug 2039409] Re: System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039409 Title: System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: System consistently freezes requiring hard reset every few hours. Syslog gives this message at the time of the crash: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-d7iZ5S/linux- hwe-6.2-6.2.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 21:38:57 2023 InstallationDate: Installed on 2021-05-15 (883 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-28 (322 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039409/+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 2039409] Re: System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code
I have a similar crash with Ubuntu 22.04, running
`vmlinuz-6.1.0-1024-oem` (from pkg `linux-oem-22.04d`).
Oct 25 14:11:46 mandeep-pf3xfcj3 kernel: UBSAN: array-index-out-of-bounds in
/build/linux-oem-6.1-CvRDkF/linux-oem-6.1-6.1.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39
Oct 25 14:11:46 mandeep-pf3xfcj3 kernel: index 512 is out of range for type
'iwl_txq *[512]'
...
...
Oct 25 14:12:10 mandeep-pf3xfcj3 kernel: rcu: INFO: rcu_preempt detected
expedited stalls on CPUs/tasks: { 7- } 5346 jiffies s: 781 root: 0x80/.
Oct 25 14:12:10 mandeep-pf3xfcj3 kernel: rcu: blocking rcu_node structures
(internal RCU debug):
...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039409
Title:
System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code
Status in linux-signed-hwe-6.2 package in Ubuntu:
Confirmed
Bug description:
System consistently freezes requiring hard reset every few hours.
Syslog gives this message at the time of the crash:
UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-d7iZ5S/linux-
hwe-6.2-6.2.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 21:38:57 2023
InstallationDate: Installed on 2021-05-15 (883 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: Upgraded to jammy on 2022-11-28 (322 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039409/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Actually after opening this bug I decided to try my MX master 3S with bluetooth mode and that's not detected either. I also tried a pair of airpods and those are not seen. the weird part is that I am actively using some samsung galaxy buds with this laptop via bluetooth and they work. So perhaps there's something generally wrong with bluetooth discovery on my laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: New Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] [NEW] bluez does not detect Logitech Pebble M350, no option to connect
Public bug reported: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: New Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
** Changed in: gnome-shell
Status: Unknown => 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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2040526] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2040526 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- 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/2040526 Title: Backport RDMA DMABUF Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: SRU Justification: [Impact] * From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] * Testing instructions are outlined in the SF case and has been tested on in house hardware and externally by Nvidia. [Where problems could occur?] * This introduces new code paths so regression potential should be low. [Other Info] * SF#00370664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040526/+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 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- 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/1743427 Title: Black screen with iMac 2011 and ATI Radeon 6970M Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu 16.04 through 17.10, when I boot the screen is black, ping and ssh to the host does not work, and the fan is running. Same problem with kernel 4.14 and 4.15RC7. WORKAROUND: Use kernel parameter: nomodeset --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1756 F pulseaudio /dev/snd/controlC1: christian 1756 F pulseaudio DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/storage-swap InstallationDate: Installed on 2018-01-15 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) MachineType: Apple Inc. iMac12,2 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/storage-root ro rootflags=subvol=@ nomodeset ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM121.88Z.004D.B00.1708080012 dmi.board.name: Mac-942B59F58194171B dmi.board.vendor: Apple Inc. dmi.board.version: iMac12,2 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B59F58194171B dmi.modalias: dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B: dmi.product.family: iMac dmi.product.name: iMac12,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743427/+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 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- 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/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* disp
[Kernel-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- 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/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* disp
[Kernel-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- 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/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* disp
[Kernel-packages] [Bug 1024507] Re: 1002:9488 [iMac11, 2] 12.10 quantal boots to black screen on iMac
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- 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/1024507 Title: 1002:9488 [iMac11,2] 12.10 quantal boots to black screen on iMac Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Running 12.10, updated today, on iMac 11,2 (mid 2010) with AMD Radeon 4670. Using kernel radeon driver (lsmod shows it running). Normal boot results in black screen. Ctl-Alt-Del reboots; indicating that system did boot. This appears to be a regression in the kernel, similar to bug 597070 (ubuntu 11.04 - used fglrx to get video to work) and to bug 863969 (ubuntu 11.10 - where an upgrade to the 3.2 kernel seemed to improve video detection). Suspend and resume does not work either, not turning off the system, only the video, and resuming to a black screen. I think the problem is in KMS, because the black screen happens even if I boot into text mode and using nomodeset fixes it. Hence filing this against xorg but expect it to go to kernel developers. WORKAROUND: Use kernel parameter nomodeset. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.3-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jul 13 19:12:16 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV730 XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b6] InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120509) MachineType: Apple Inc. iMac11,2 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: vmlinuz-3.5.0-4-generic root=UUID=268e7eb7-d871-478c-a906-b719eea881ea ro nosplash nomodeset initrd=EFI\ubuntu\initrd.img-3.5.0-4-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM112.88Z.0057.B01.1112090906 dmi.board.name: Mac-F2238AC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2238AC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM112.88Z.0057.B01.1112090906:bd12/09/11:svnAppleInc.:pniMac11,2:pvr1.0:rvnAppleInc.:rnMac-F2238AC8:rvr:cvnAppleInc.:ct13:cvrMac-F2238AC8: dmi.product.name: iMac11,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-3 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1024507/+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 1782934] Re: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic
ah damned - wifi does not work with 6.2.0-26. I guess I have to sell this device to a windows user, this tends to cost too much time getting this back to work :/ -- 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/1782934 Title: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic Status in linux package in Ubuntu: Confirmed Bug description: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post- install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic (edited to add: this SHOULD have read '4.15.0-29-generic'). Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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 2040526] Re: Backport RDMA DMABUF
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Description changed: SRU Justification: [Impact] - From Nvidia: + *From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] - Testing instructions are outlined in the SF case and has been tested on + *Testing instructions are outlined in the SF case and has been tested on in house hardware and externally by Nvidia. [Where problems could occur?] - This introduces new code paths so regression potential should be low. + *This introduces new code paths so regression potential should be low. [Other Info] - SF#00370664 + + *SF#00370664 ** Description changed: SRU Justification: [Impact] - *From Nvidia: + * From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] - *Testing instructions are outlined in the SF case and has been tested on - in house hardware and externally by Nvidia. + * Testing instructions are outlined in the SF case and has been tested + on in house hardware and externally by Nvidia. [Where problems could occur?] - *This introduces new code paths so regression potential should be low. + * This introduces new code paths so regression potential should be low. [Other Info] - *SF#00370664 + * SF#00370664 -- 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/2040526 Title: Backport RDMA DMABUF Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: SRU Justification: [Impact] * From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists
[Kernel-packages] [Bug 1782934] Re: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic
Additional information: 6.2.0-34 and -35 does not work 6.2.0-26 works well. If you need additional information or if I should create a new bug ticket, please let me know. lshw -C display shows: product: Skylake GT2 [HD Graphics 520] Version: 07 configuration: depth=32 resolution=3200,1800 while I am logged in with the working 6.2.0-26 kernel. -- 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/1782934 Title: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic Status in linux package in Ubuntu: Confirmed Bug description: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post- install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic (edited to add: this SHOULD have read '4.15.0-29-generic'). Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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 2040526] Re: Backport RDMA DMABUF
** Description changed: SRU Justification: [Impact] From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ - The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: + The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] Testing instructions are outlined in the SF case and has been tested on - local hardware and also by Nvidia. + in house hardware and externally by Nvidia. [Where problems could occur?] This introduces new code paths so regression potential should be low. [Other Info] SF#00370664 -- 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/2040526 Title: Backport RDMA DMABUF Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Bug description: SRU Justification: [Impact] From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] Testing instructions are outlined in the SF case and has been tested on in house hardware and externally by Nvidia. [Where problems could occur?] This introduces new code paths so regression potential should be low. [Other Info] SF#00370664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040526/+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 2040652] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2040652 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2040652 Title: megaraid_sas: DMA errors detected during IO operations Status in linux package in Ubuntu: Incomplete Bug description: system config: - SMC server (super micro server) - Ubuntu 22.04 LTS OS - Aero iMR storage controller Issue: Recently, we have encountered DMA errors in the Aero iMR controller, a lighter version of the Aero MR controller. The firmware of Aero iMR utilizes host memory for its operations, with BIOS setting aside 128MB of host memory for the Aero iMR PCI device. The OS is then instructed to reserve this address in its IVRS table. Despite this reservation, we are experiencing DMA errors when the firmware performs DMA operations on this allocated host memory. We are investigating the cause of these errors and need ubuntu OS team assistance on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040652/+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 2040526] Re: Backport RDMA DMABUF
** Description changed: SRU Justification: [Impact] From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference + https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ + The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: + "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] Testing instructions are outlined in the SF case and has been tested on local hardware and also by Nvidia. [Where problems could occur?] This introduces new code paths so regression potential should be low. [Other Info] SF#00370664 -- 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/2040526 Title: Backport RDMA DMABUF Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Bug description: SRU Justification: [Impact] From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] Testing instructions are outlined in the SF case and has been tested on local hardware and also by Nvidia. [Where problems could occur?] This introduces new code paths so regression potential should be low. [Other Info] SF#00370664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040526/+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 2040526] Re: Backport DMABUF functionality
** Description changed: SRU Justification: [Impact] - Backport RDMA DMABUF functionality + Backport RDMA DMABUF - Nvidia is working on a high performance networking solution with real + From Nvidia: + + "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not - execute these new code paths. + execute these new code paths." - * First 3 patches adds a new api to the RDMA subsystem that allows drivers to get a pinned dmabuf memory - region without requiring an implementation of the move_notify callback. - + Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ - - * The remaining patches add support for DMABUF when creating a devx umem. devx umems - are quite similar to MR's execpt they cannot be revoked, so this uses the - dmabuf pinned memory flow. Several mlx5dv flows require umem and cannot - work with MR. - - https://lore.kernel.org/all/0-v1-bd147097458e+ede- - umem_dmabuf_...@nvidia.com/ + https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ [Test Plan] - SW Configuration: - • Download CUDA 12.2 run file (https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=runfile_local) - • Install using kernel-open i.e. #sh ./cuda_12.2.2_535.104.05_linux.run -m=kernel-open - • Clone perftest from https://github.com/linux-rdma/perftest. - • cd perftest - • export LD_LIBRARY_PATH=/usr/local/cuda-12.2/lib64:$LD_LIBRARY_PATH - • export LIBRARY_PATH=/usr/local/cuda-12.2/lib64:$LIBRARY_PATH - • run: ./autogen.sh ; ./configure CUDA_H_PATH=/usr/local/cuda/include/cuda.h; make - - # Start Server - $ ./ib_write_bw -d mlx5_2 -F --use_cuda=0 --use_cuda_dmabuf - - #Start Client - $ ./ib_write_bw -d mlx5_3 -F --use_cuda=1 --use_cuda_dmabuf localhost + Testing instructions are outlined in the SF case and has been tested on + local hardware and also by Nvidia. [Where problems could occur?] + + This introduces new code paths so regression potential should be low. + + [Other Info] + SF#00370664 ** Description changed: SRU Justification: [Impact] - - Backport RDMA DMABUF From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ [Test Plan] Testing instructions are outlined in the SF case and has been tested on local hardware and also by Nvidia. [Where problems could occur?] This introduces new code paths so regression potentia
[Kernel-packages] [Bug 2040652] [NEW] megaraid_sas: DMA errors detected during IO operations
Public bug reported: system config: - SMC server (super micro server) - Ubuntu 22.04 LTS OS - Aero iMR storage controller Issue: Recently, we have encountered DMA errors in the Aero iMR controller, a lighter version of the Aero MR controller. The firmware of Aero iMR utilizes host memory for its operations, with BIOS setting aside 128MB of host memory for the Aero iMR PCI device. The OS is then instructed to reserve this address in its IVRS table. Despite this reservation, we are experiencing DMA errors when the firmware performs DMA operations on this allocated host memory. We are investigating the cause of these errors and need ubuntu OS team assistance on this. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040652 Title: megaraid_sas: DMA errors detected during IO operations Status in linux package in Ubuntu: New Bug description: system config: - SMC server (super micro server) - Ubuntu 22.04 LTS OS - Aero iMR storage controller Issue: Recently, we have encountered DMA errors in the Aero iMR controller, a lighter version of the Aero MR controller. The firmware of Aero iMR utilizes host memory for its operations, with BIOS setting aside 128MB of host memory for the Aero iMR PCI device. The OS is then instructed to reserve this address in its IVRS table. Despite this reservation, we are experiencing DMA errors when the firmware performs DMA operations on this allocated host memory. We are investigating the cause of these errors and need ubuntu OS team assistance on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040652/+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 2032535] Re: [Google_Puff] Screen blank crashes system
I just wanted to wrap up a loose thread. I upgraded my system to ubuntu 23.10 (not a fresh install) and after the upgrade I no longer have this issue. The system blanks the screen perfectly. Thanks for taking the time to help troubleshoot. -- 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/2032535 Title: [Google_Puff] Screen blank crashes system Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
New info: I realised this is something related to my integrated graphic
in my laptop (AMD Radeon graphic integrated). So, if I launch Firefox,
Steam etc. with my dedicated graphic (AMD Radeon RX 5600m), works
perfectly, no issues.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi Endre, I have kinda made progress in regards of being able to patch and install a kernel. First i'ill walk you through my assumptions, 1) you have the laptop and installed a debian/ubuntu based distro but the keyboard and touchpad don't work. 2) there is at least 64Gb of disk space available 3) you have the option of using the root user. so first off. Download the patch from above. https://bugzilla.kernel.org/attachment.cgi?id=305236 run uname -r, this will return your kernel version, download the closest matching version to that version from kernel.org, but remeber only download later versions, so you are not using a version older than your current kernel. then run sudo apt install build-essential libncurses5-dev libssl-dev flex libelf-dev bc bison gcc make dwarves zstd then unzip the downloaded kernel and enter it as root. appply the patch by running the following as roon in the unzipped kernel directory: patch -p1 < path_to_patchfile it will return something notifying it's ready. then copy over the latest kernel config to the unzipped kernel this can be found in the /boot directory mine is /boot/config-6.1.59 for example. this is beceause i patched up the old kernel to this one. cp -r /boot/.conf .config replace latestkernel with the one you find in /boot then run make menuconfig as the root in the unzipped kernel. immediatly just hit save and exit run the following 2 lines as the root user in the unzipped kernel individually :) (been there done that) scripts/config --disable SYSTEM_TRUSTED_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS then run make -j 16 and just hit enter whenever it prompts something, oh and get a coffee or a tea this is going to take a while :)) when it completes, run as root in the unzipped kernel: make modules_install should'nt take too long whenever it completes run make install let it complete, congrats kernel installed, run; update-grub verify that the version of the kernel is somewhere in it's output. reboot, and pray. if it boots up, run a uname -r, try it with the laptop's builtin keyboard. if you've made it this far congrats. you have now patched and installed a kernel. above works on any distro i've tried. (zorin16 debian12 ubuntu2204) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in libinput package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Status in linux-signed-oem-6.5 package in Ubuntu: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2040526] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2040526 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2040526 Title: Backport DMABUF functionality Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: [Impact] Backport RDMA DMABUF functionality Nvidia is working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths. * First 3 patches adds a new api to the RDMA subsystem that allows drivers to get a pinned dmabuf memory region without requiring an implementation of the move_notify callback. https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ * The remaining patches add support for DMABUF when creating a devx umem. devx umems are quite similar to MR's execpt they cannot be revoked, so this uses the dmabuf pinned memory flow. Several mlx5dv flows require umem and cannot work with MR. https://lore.kernel.org/all/0-v1-bd147097458e+ede- umem_dmabuf_...@nvidia.com/ [Test Plan] SW Configuration: • Download CUDA 12.2 run file (https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=runfile_local) • Install using kernel-open i.e. #sh ./cuda_12.2.2_535.104.05_linux.run -m=kernel-open • Clone perftest from https://github.com/linux-rdma/perftest. • cd perftest • export LD_LIBRARY_PATH=/usr/local/cuda-12.2/lib64:$LD_LIBRARY_PATH • export LIBRARY_PATH=/usr/local/cuda-12.2/lib64:$LIBRARY_PATH • run: ./autogen.sh ; ./configure CUDA_H_PATH=/usr/local/cuda/include/cuda.h; make # Start Server $ ./ib_write_bw -d mlx5_2 -F --use_cuda=0 --use_cuda_dmabuf #Start Client $ ./ib_write_bw -d mlx5_3 -F --use_cuda=1 --use_cuda_dmabuf localhost [Where problems could occur?] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040526/+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 2040526] [NEW] Backport DMABUF functionality
Public bug reported: SRU Justification: [Impact] Backport RDMA DMABUF functionality Nvidia is working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths. * First 3 patches adds a new api to the RDMA subsystem that allows drivers to get a pinned dmabuf memory region without requiring an implementation of the move_notify callback. https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ * The remaining patches add support for DMABUF when creating a devx umem. devx umems are quite similar to MR's execpt they cannot be revoked, so this uses the dmabuf pinned memory flow. Several mlx5dv flows require umem and cannot work with MR. https://lore.kernel.org/all/0-v1-bd147097458e+ede- umem_dmabuf_...@nvidia.com/ [Test Plan] SW Configuration: • Download CUDA 12.2 run file (https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=runfile_local) • Install using kernel-open i.e. #sh ./cuda_12.2.2_535.104.05_linux.run -m=kernel-open • Clone perftest from https://github.com/linux-rdma/perftest. • cd perftest • export LD_LIBRARY_PATH=/usr/local/cuda-12.2/lib64:$LD_LIBRARY_PATH • export LIBRARY_PATH=/usr/local/cuda-12.2/lib64:$LIBRARY_PATH • run: ./autogen.sh ; ./configure CUDA_H_PATH=/usr/local/cuda/include/cuda.h; make # Start Server $ ./ib_write_bw -d mlx5_2 -F --use_cuda=0 --use_cuda_dmabuf #Start Client $ ./ib_write_bw -d mlx5_3 -F --use_cuda=1 --use_cuda_dmabuf localhost [Where problems could occur?] ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/2040526 Title: Backport DMABUF functionality Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: [Impact] Backport RDMA DMABUF functionality Nvidia is working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths. * First 3 patches adds a new api to the RDMA subsystem that allows drivers to get a pinned dmabuf memory region without requiring an implementation of the move_notify callback. https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ * The remaining patches add support for DMABUF when creating a devx umem. devx umems are quite similar to MR's execpt they cannot be revoked, so this uses the dmabuf pinned memory flow. Several mlx5dv flows require umem and cannot work with MR. https://lore.kernel.org/all/0-v1-bd147097458e+ede- umem_dmabuf_...@nvidia.com/ [Test Plan] SW Configuration: • Download CUDA 12.2 run file (https:/
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
SRU v2: https://lists.ubuntu.com/archives/kernel- team/2023-October/146475.html (mantic) ** Description changed: [SRU Justification] == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. + + The Intel IPU6 camera drivers are not yet all upstreamed yet. So far + Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are + in v6.6 already, and IPU6 ISYS is under upstream review. More components + to come according to Intel. + + These two fixes are therefore for related components for not-yet fully + upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. -- 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/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux source package in Mantic: In Progress Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be
[Kernel-packages] [Bug 2040521] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2040521 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2040521 Title: USB ethernet port fails after reconnect Status in linux package in Ubuntu: Incomplete Bug description: When using a Dell dock WB19TB on Ubuntu 20.04, the ethernet port fails to work after the dock is disconnected and reconnected. One way to make it work again is to remove then reload the r8153_ecm module or to restart the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040521/+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 2040522] [NEW] gVNIC DQO-QPL feature
Public bug reported: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * All cherry-picks from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * All cherry-picks from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+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 2040521] [NEW] USB ethernet port fails after reconnect
Public bug reported: When using a Dell dock WB19TB on Ubuntu 20.04, the ethernet port fails to work after the dock is disconnected and reconnected. One way to make it work again is to remove then reload the r8153_ecm module or to restart the machine. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl with example of this error occurring" https://bugs.launchpad.net/bugs/2040521/+attachment/5713218/+files/journalctl -- 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/2040521 Title: USB ethernet port fails after reconnect Status in linux package in Ubuntu: New Bug description: When using a Dell dock WB19TB on Ubuntu 20.04, the ethernet port fails to work after the dock is disconnected and reconnected. One way to make it work again is to remove then reload the r8153_ecm module or to restart the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040521/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi Quinten, I would do another try on the Ubuntu 22.04.3, but I am not sure if I have downloaded earlier the right kernel source. Could you send the link to the one you used? What anout the .config file. Did you made the config as described earlier? So no stock config, just running the make menuconfig and that is all? Any specific thing you did differently than above? Thanks Endre -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in libinput package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Status in linux-signed-oem-6.5 package in Ubuntu: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2019000] Re: Use new annotations model
This bug is awaiting verification that the linux-gke/5.15.0-1046.51 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-gke' to 'verification-done-jammy- linux-gke'. If the problem still exists, change the tag 'verification- needed-jammy-linux-gke' to 'verification-failed-jammy-linux-gke'. 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-gke-v2 verification-needed-jammy-linux-gke -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: New Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: New Status in linux source package in Kinetic: Confirmed Status in linux-gcp source package in Kinetic: Invalid Status in linux-kvm source package in Kinetic: Invalid Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 2034705] Re: efivar fails to read variables
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034705 Title: efivar fails to read variables Status in efivar package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: In Progress Bug description: On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel 6.5.0-2-generic we see this output: root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/ AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c root@ubuntu-server:/var# efivar -l efivar: error listing variables: Function not implemented root@ubuntu-server:/var# efibootmgr -v EFI variables are not supported on this system. Expected behavior would be to display the variables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support
Seems the applied patch (upstream commit 52480e1f1a259) has something wrong and a fix is coming: https://lore.kernel.org/linux- usb/tyzpr02mb508845bad7936a62a105ce5d89...@tyzpr02mb5088.apcprd02.prod.outlook.com/ -- 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/2038259 Title: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: Required fix: https://lore.kernel.org/linux- usb/20230901093610.67438-1-puliang...@fibocom.com To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038259/+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 2040120] Re: Kernel configs deviate from generic kernel
This bug is awaiting verification that the linux-gke/5.15.0-1046.51 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-gke' to 'verification-done-jammy- linux-gke'. If the problem still exists, change the tag 'verification- needed-jammy-linux-gke' to 'verification-failed-jammy-linux-gke'. 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-gke-v2 verification-needed-jammy-linux-gke -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2040120 Title: Kernel configs deviate from generic kernel Status in linux-gke package in Ubuntu: Incomplete Status in linux-gke source package in Jammy: New Bug description: After doing the config to annotation migration it became apparent that during previous cranks generic kernel configs were not correctly updated in the derivative linux-gke kernel. For the time being, the gke annotations file has been updated to match the configs prior to annotation migrations. These configs should be evaluated and updated in linux-gke to match the generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2040120/+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 2034705] Re: efivar fails to read variables
Subiquity users trying to install 23.10 on Apple hardware (amd64) have been running into problems as well because of this issue. Thank you Heinrich for sending the patch upstream! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2034705 Title: efivar fails to read variables Status in efivar package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: In Progress Bug description: On riscv64 StarFive VisionFive 2 with U-Boot v2023.10-rc4 and kernel 6.5.0-2-generic we see this output: root@ubuntu-server:/var# ls /sys/firmware/efi/efivars/ AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c root@ubuntu-server:/var# efivar -l efivar: error listing variables: Function not implemented root@ubuntu-server:/var# efibootmgr -v EFI variables are not supported on this system. Expected behavior would be to display the variables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2039405] Re: Unable to power off the system with MTL CPU
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039405 Title: Unable to power off the system with MTL CPU Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] The commit introduced from v6.4 leads to the power off issue 45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible [Fix] The problematic commit has been reverted since v6.6 fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible" [Test case] 1. Power up the MTL system 2. Power off the system and make sure it shutdown correctly [Where problems could occur] From the origin commit log, revert the commit may have a protential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039405/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
** 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => 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/2038611
Title:
drop all references to is_rust_module.sh in kernels >= 6.5
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a reference of it in debian.master/reconstruct and
that generates the following warning during the build:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or
directory
[Fix]
Drop the reference to is_rust_module.sh from reconstruct to prevent
unnecessary warnings during the build.
[Test case]
The following command ran from the kernel source directory is enough
to trigger the warning:
$ fakeroot debian/rules clean
[Regression potential]
This change is affecting only our packaging. The change is trivial but
it might affect our kernel build process in case of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611/+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 2038522] Re: disable shiftfs
** Changed in: linux (Ubuntu Mantic) Status: Triaged => 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/2038522 Title: disable shiftfs Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Fix Committed Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0
** 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2035123
Title:
scripts/pahole-flags.sh change return to exit 0
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
Triaged
Status in linux source package in Jammy:
Fix Committed
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2035123
[Impact]
When building the Jammy linux-bluefield kernel tree on a system
without pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
scripts/pahole-flags.sh attempts to return from an if statement that
is not within a function, and generates a warning.
The fix is straightforward, changing return to an exit 0.
--- a/scripts/pahole-flags.sh
+++ b/scripts/pahole-flags.sh
@@ -4,7 +4,7 @@
extra_paholeopt=
if ! [ -x "$(command -v ${PAHOLE})" ]; then
- return
+ exit 0
fi
[Testcase]
Clone the linux-bluefield kernel tree and build it on a arm64 system without
pahole installed.
A test kernel is available with the fix applied in:
https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test
Both linux-bluefield and ubuntu-jammy build correctly.
[Fix]
This was fixed by Linus Torvalds in the following merge commit:
commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Merge: bfc484fe6abb 84882cf72cd7
Author: Linus Torvalds
Date: Tue Nov 2 06:20:58 2021 -0700
Subject: Merge tag 'net-next-for-5.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Note, the original commit does not have the fix included:
commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
Author: Jiri Olsa
Date: Fri Oct 29 14:57:29 2021 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8
The Ubuntu kernel cherry-picked the original commit and did not pick up the
silent fix made in the merge commit. Submitting the silent fix as a SAUCE
patch
with changelog describing the change.
Note: I know SAUCE patches are bad, but in this scenario, to revert
the initial commit and re-apply the fixed version would require us to
revert two additional dependency commits, making six patches to
review, vs, a one line change in a SAUCE commit that has a real
changelog entry.
[Where problems could occur]
The Ubuntu kernel is built with pahole enabled, and requires pahole to
be installed as a build dependency. It is extremely unlikely that any
users are disabling pahole at build time, apart from linux-bluefield
engineers.
If a regression were to occur, engineers would see errors during build
time about scripts/pahole-flags.sh not executing properly.
[Other info]
Linus remarked about the issue in the following lkml discussion:
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/
This was silently Incorporated into the linux-stable commit:
commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
From: Jiri Olsa
Date: Sun, 4 Sep 2022 15:19:00 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
intermittent behaviour still present in 6.5.0-10 .. just installed .. but
disconnects are less frequent.
audio drop-outs are frequent.. tracks play normally with linux-image-6.5.0-5 ..
manually marked .. to prevent removal..
--
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/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a 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.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
** Summary changed:
- bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC)
+ bluetooth connections are unstable with linux-image-6.5.0-6-generic and above
(MANTIC)
--
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/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a 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.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svn
[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infinite systemd loop when power off the machine with multiple MD
RAIDs
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The system with multiple MD RAIDs sometimes hangs while rebooting, that's
because of the systemd can't stop and close the MD disk.
[Fix]
This commit fixes the issue, and this issue has been introduced by
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed")
after v6.0
https://patchwork.kernel.org/project/linux-
raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/
[Test case]
1. Reboot the system with multiple MD RAIDs at least 10 times.
2. Make sure the system can reboot successfully every time.
3. You should not see error messages like below.
[ 205.360738] systemd-shutdown[1]: Stopping MD devices.
[ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
[ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
[ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
[ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
[ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127,
ignoring: Input/output error
[ 205.404975] md: md127 stopped.
[ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
[ 205.770179] md: md126: resync interrupted.
[ 205.776258] md126: detected capacity change from 1900396544 to 0
[ 205.783349] md: md126 stopped.
[ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
[ 205.862435] md: md126 stopped.
[ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125,
ignoring: Input/output error
[ 205.872845] block device autoloading is deprecated and will be removed.
[ 205.880955] md: md125 stopped.
[ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
[ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or
resource busy
[ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
[ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or
resource busy
[ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
[ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or
resource busy
[ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
[Where problems could occur]
It fixes the data race issue, should not introduce any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
#17 This issue is specific to AMD Navi3x dGPU; please open separate issue for your problem. -- 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/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => 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/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Fix Committed Bug description: [SRU Justification] [Impact] IOMMU related peripherals cannot work. [Fix] CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency. [Test Case] build test. this is the first step to enable the platform on generic kernel. to fully enable the platform, there are some modifications still needed, so only the build test is performed at this stage. [Where problems could occur] to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be built-in. the risk would be low because it's not used by default and it needs the driver to allocate by demand. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady- IR/Test-installation-of-Linux-distributions?lang=en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036587/+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 2037273] Re: Realtek 8852CE WiFi 6E country code udpates
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037273
Title:
Realtek 8852CE WiFi 6E country code udpates
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing WiFi 6G band for interested countries.
[Fix]
Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43").
[Test Case]
Use `iw list` to check if 6G bands are then enabled.
[Where problems could occur]
This enables corresponding 6G bands for rtw89 driven devices. There
should be no other side effects.
[Other Info]
Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable
is skipped.
= original bug report ==
Proposed fix:
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43") and is in v6.6-rc1 now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037273/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
This bug is awaiting verification that the linux-gcp/6.5.0-1008.8 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-mantic-linux-gcp' to 'verification-done-mantic- linux-gcp'. If the problem still exists, change the tag 'verification- needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'. 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-mantic-linux-gcp-v2 verification-needed-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2037224] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.2 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-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. 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.
--
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/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Committed
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are multiple stability issues for RTL8851B.
Issue-1:
After disabling BT and leaving it idle for a period, manually turning on the
RTL8851BE will fail.
Issue-2:
Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
either failure to read device descriptors:
usb 1-14: device descriptor read/64, error -71
or tx command timeout:
Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout
[Fix]
Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
0x048A_D230").
[Test Case]
$ checkbox-cli run
com.canonical.plainbox::suspend/suspend_advanced_auto
[Where problems could occur]
This updates opaque firmware blobs, so it could bring further stability issues
and/or power consumption changes.
[Other Info]
While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
and mantic are nominated for fix.
= original bug report ==
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
Stuck on Recovering Journal (clean) after upgrading to Ubuntu 22.04.4 LTS I have a NVIDIA Corporation GA104GL [RTX A4000] (rev a1) Kernal: 6.2.0-35-generic. -- 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/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2037224] Re: Multiple RTL8851BE BT stability issues
The verification-done* tags are used by the SRU process only, to track
verification of a package in the official Ubuntu proposed pocket once
completed according to a Test Plan agreed by the SRU team. Please do not
use this tag unless this process has been followed. Since
20230919.git3672ccab-0ubuntu2.2 has never been published by Ubuntu, this
is impossible, so I'm removing the tag.
** Tags removed: verification-done-mantic
--
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/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Committed
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are multiple stability issues for RTL8851B.
Issue-1:
After disabling BT and leaving it idle for a period, manually turning on the
RTL8851BE will fail.
Issue-2:
Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
either failure to read device descriptors:
usb 1-14: device descriptor read/64, error -71
or tx command timeout:
Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout
[Fix]
Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
0x048A_D230").
[Test Case]
$ checkbox-cli run
com.canonical.plainbox::suspend/suspend_advanced_auto
[Where problems could occur]
This updates opaque firmware blobs, so it could bring further stability issues
and/or power consumption changes.
[Other Info]
While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
and mantic are nominated for fix.
= original bug report ==
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 1979298] Re: Installing nvidia-driver-510-server removes nvidia-cuda-dev
This seems to have been resolved using nvidia-driver-525-server. Thanks! ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510-server in Ubuntu. https://bugs.launchpad.net/bugs/1979298 Title: Installing nvidia-driver-510-server removes nvidia-cuda-dev Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Released Bug description: On Ubuntu 22.04, installing first `nvidia-cuda-dev` and then `nvidia- driver-510-server` leads to `nvidia-cuda-dev` being removed (or at least most packages it installed). The other way the same happens too - installing `nvidia-driver-510-server` first and then `nvidia-cuda- dev` removes stuff from the driver. I guess this is related to https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda- toolkit/+bug/1963976 but I'm not sure if it's the same. Is there any workaround for this? I need both packages - `nvidia-cuda- dev` for `ffmpeg` to run (which is compiled with nvidia support) and `nvidia-driver-510-server` so that the card is actually used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510-server/+bug/1979298/+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 2030494] Re: Keyboard inoperative on MacBook Pro11, 3 (Intel Core i7-4850HQ)
A complete re-install with 22.04.3 (kernel 6.2.0-35) solved it too. -- 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/2030494 Title: Keyboard inoperative on MacBook Pro11,3 (Intel Core i7-4850HQ) Status in linux package in Ubuntu: Confirmed Bug description: The laptop has full disk encryption. Entering the encryption password is not possible, as neither the built in keyboard nor an external keyboard works. I currently run kernel 5.19.0-42, which still works. Kernel versions starting from 5.19.0-43, including 6.x, contain the bug. Currently available on my machine are: linux-image-5.15.0-78-generic linux-image-5.19.0-35-generic linux-image-5.19.0-42-generic linux-image-6.2.0-26-generic MacBook Pro 11,3 (late 2013) with processor Intel Core i7-4850HQ CPU @ 2.30GHz × 8, graphics GeForce GT 750M/PCIe/SSE2, OS Ubuntu 22.04.03 LTS --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gaele 4369 F pulseaudio /dev/snd/controlC0: gaele 4369 F pulseaudio /dev/snd/controlC2: gaele 4369 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-04 (687 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Apple Inc. MacBookPro11,3 NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.17 Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 04/11/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0146.B00.180438 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0146.B00.180438:bd04/11/2018:br0.1:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030494/+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 2039437] Re: linux-tools- should provide linux-tools
** Also affects: linux-meta-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2039437 Title: linux-tools- should provide linux-tools Status in linux-meta-raspi package in Ubuntu: New Status in linux-meta-raspi source package in Focal: New Status in linux-meta-raspi source package in Jammy: New Status in linux-meta-raspi source package in Lunar: New Status in linux-meta-raspi source package in Mantic: New Bug description: [Impact] Missing 'Provides: linux-tools', results in: $ sudo apt install linux-tools Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-tools is a virtual package provided by: linux-tools-virtual-hwe-22.04-edge 6.5.0.9.11 linux-tools-virtual-hwe-22.04 6.5.0.9.11 linux-tools-virtual 6.5.0.9.11 linux-tools-generic-hwe-22.04-edge 6.5.0.9.11 linux-tools-generic-hwe-22.04 6.5.0.9.11 linux-tools-generic 6.5.0.9.11 You should explicitly select one to install. E: Package 'linux-tools' has no installation candidate The above should list linux-tools-raspi on ARM. [Fix] Add 'Provides: linux-tools' and 'Provides: linux-cloud-tools' to all meta packages that are missing them. [Test Case] See [Impact] above. The list of installation candidates should show the fixed meta package name. [Regression Potential] Can't think of any problems this might cause. Most meta packages are correct and we would have noticed issues by now (I hope). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/2039437/+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 2019000] Re: Use new annotations model
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: New Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: New Status in linux source package in Kinetic: Confirmed Status in linux-gcp source package in Kinetic: Invalid Status in linux-kvm source package in Kinetic: Invalid Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
The fact that the kernel built and it's in -proposed means the bug is verified. ** Tags removed: verification-needed-lunar-linux-kvm ** Tags added: verification-done-lunar-linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Committed Status in linux-kvm source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039575] Re: [UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes.
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
--
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/2039575
Title:
[UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of
exactly 4096 bytes.
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
New
Bug description:
Bug description by Nils H.:
Overview:
The following line in the SMC stats code (net/smc/smc_stats.h) caught my
attention when using a payload of exactly 4096 bytes:
#define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
} \
while (0)
With l = 4096, _pos evaluates to -1.
Checking with the following uperf profile:
# cat rr1c-4kx4k---1.xml
smcd stats output:
# smcd -d stats reset
SMC-D Connections Summary
Total connections handled 2
SMC connections 2 (client 2, server 0)
v1 0
v2 2
Handshake errors 0 (client 0, server 0)
Avg requests per SMC conn14.0
TCP fallback 0 (client 0, server 0)
RX Stats
Data transmitted (Bytes) 5796 (5.796K)
Total requests9
Buffer full 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 0 0 2 0 0 0 1
Reqs8 0 0 0 0 0 0 0
TX Stats
Data transmitted (Bytes) 9960 (9.960K)
Total requests 19
Buffer full 0 (0.00%)
Buffer full (remote) 0 (0.00%)
Buffer too small 0 (0.00%)
Buffer too small (remote) 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 2 0 0 0 0 0 0
Reqs 18 0 0 0 0 0 0 1
Extras
Special socket calls 0
cork0
nodelay 0
sendpage0
splice 0
urgent data 0
Instead of including the payload in the wrong >512KB buckets, output should
be to have 19 reqs in the 8KB buckets for TX stats and 9 reqs in the 8KB bucket
for RX stats.
Repro:
0. Install uperf.
1. Reset SMC-D stats on client and server.
2. Start uperf at server side: "uperf -vs".
3. Update profile with remote IP (server IP) and start uperf at client:
"uperf -vai 5 -m rr1c-4kx4k---1.xml" (uperf profile, see above)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2039575/+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 2037403] Re: PCI BARs larger than 128GB are disabled
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Okay so far i tested: debian12 on kernel 6.1.59 zorinos 16 on kernel 5.15.136 ubuntu 22.04.3 on kernel 6.5.3 All of the above configs work, if patched. stability was not tested because of lack of time. But i would guess it's stable enough. Happy patching :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in libinput package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Status in linux-signed-oem-6.5 package in Ubuntu: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 1991725] Re: fails to sign kernel modules
This issue is still valid in Ubuntu 23.04 with the virtualbox-dkms package. See bug report https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1992673 marked as a duplicate of this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Kinetic: Fix Released Bug description: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. 8. Run "sudo apt install bcmwl-kernel-source". 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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 2029899] Re: Update firmware for hwe-6.2/oem-6.5 kernel migrations
verified linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.22 ** Tags added: verification-done-jammy -- 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/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. [Where problems could occur] These firmware blobs are only referenced in the new hwe/oem kernels, and shall not have side effect. [Other Info] While there is no hwe/oem kernel planned for Lunar, so only Jammy is nominated for fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029899/+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
