[Kernel-packages] [Bug 2030525] Re: Installation support for SMARC RZ/G2L platform
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2030525 Title: Installation support for SMARC RZ/G2L platform Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Fix Committed Bug description: Dear Maintainer The Ubuntu installation on Renesas RZ/G2L platform board is failing due to the following configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n10339 The configuration CONFIG_RESET_RZG2L_USBPHY_CTRL=y is required to allow the installation on Renesas SMARC platform. Alternatively, the module "reset-rzg2l-usbphy-ctrl.ko" to be added in the inside installer initrd. This change is required on Lunar and Jammy versions as well. Please update once the changes merged to test them on Renesas SMARC RZ/G2L platform. Best Regards John To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030525/+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 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
@phil As I said above for me it mostly was "I'm sure some change was expected, but so much?". It has various benefits as gladly outlined by Dimitri, fixing many issues, but coming at a price tag. Seeing how big the price tag is for small size, high density cases I consider it potentially too much for some. As I said in my report "This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected." so a way forward IMHO would be: 1. We leave mantic as is 2. We certainly need a release notes entry that explains the pros/cons that led to the decision 3. kernel can continue to optimize this case (see all the discussions/suggestions above already) 4. towards 24.04 4a) if this is received well, keep it 4b) if our decision was good, but not accounting for too many use-cases that we can't fix otherwise reconsider having a reduced kernel in 24.04 That would mostly an ask to the kernel team (but needs CPC to ensure it is correct e.g. in making it clear which images change due to that and which won't as they were already based on -generic). Phil/Xnox - what do you think about that approach? -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+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 2027779] Re: Second screen over usb-c stopped working after update
[Expired for linux-hwe-5.19 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.19 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2027779 Title: Second screen over usb-c stopped working after update Status in linux-hwe-5.19 package in Ubuntu: Expired Bug description: Hello, I recently got an update on my system which wrecked havoc on my display drivers. I cannot use a second monitor now any more through usb-c. When I plug in the screen nothing happens. I have verified whether there is any hardware failure (screen, cable, usb-c converter, usb-c ports on the laptop) and they all seem to be fine. I suspect it's this update which caused it: Start-Date: 2023-07-12 06:21:02 Commandline: /usr/bin/unattended-upgrade Upgrade: ghostscript-x:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9-common:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), ghostscript:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3) End-Date: 2023-07-12 06:21:02 Start-Date: 2023-07-12 06:21:04 Commandline: /usr/bin/unattended-upgrade Upgrade: libllvm15:amd64 (1:15.0.7-0ubuntu0.22.04.1, 1:15.0.7-0ubuntu0.22.04.2) End-Date: 2023-07-12 06:21:04 Could you please have a look and let me know if there is any workaround. This sets me back hours in investigation time... Regards, Hendrik ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 08:24:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:230e] InstallationDate: Installed on 2023-06-19 (24 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 21HDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=280c519f-c813-4a8e-8b21-28d80f5dbd8d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: N3QET32W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21HDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN3QET32W(1.32):bd05/09/2023:br1.32:efr1.6:svnLENOVO:pn21HDCTO1WW:pvrThinkPadT14Gen4:rvnLENOVO:rn21HDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21HD_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21HDCTO1WW dmi.product.sku: LENOVO_MT_21HD_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2027779/+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 2035299] Re: dell-uart-backlight fails to communicate with the scalar IC somtimes.
** Tags added: oem-priority originate-from-2033577 somerville
--
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/2035299
Title:
dell-uart-backlight fails to communicate with the scalar IC somtimes.
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:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
Boots up the system and sometimes we can see below messages and that leads to
backlight driver doesn't get loaded.
[ 86.424880] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 86.603936] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[ 87.596047] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 87.775209] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[Fix]
After applying this patch, it appears that the read() command sometimes fails
to receive a response, even when increasing the retry times. This could be due
to our use of a spin lock to lock the UART port in the read() function,
preventing us from calling read() immediately after a write() function.
fbf84fb368923 ("UBUNTU: SAUCE: platform/x86: dell-uart-backlight:
replace chars_in_buffer() with flush_chars()")
To fix this we only need a small delay after the write() function to
make it has time to clear its buffer.
[Test case]
1. Add dell_uart_backlight.dyndbg="+pt" to the kernel cmdline
2. Boots up the system and check dmesg
3. Make sure there is no dell_uart_backlight rx NULL message in dmesg
4. Try to unload/reload dell_uart_backlight couple times and check dmesg again
[Where problems could occur]
sleep for 1ms is pretty short that it's not possible to lead to messages loss.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2035299/+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 2035299] [NEW] dell-uart-backlight fails to communicate with the scalar IC somtimes.
Public bug reported:
[Impact]
Boots up the system and sometimes we can see below messages and that leads to
backlight driver doesn't get loaded.
[ 86.424880] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 86.603936] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[ 87.596047] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 87.775209] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[Fix]
After applying this patch, it appears that the read() command sometimes fails
to receive a response, even when increasing the retry times. This could be due
to our use of a spin lock to lock the UART port in the read() function,
preventing us from calling read() immediately after a write() function.
fbf84fb368923 ("UBUNTU: SAUCE: platform/x86: dell-uart-backlight:
replace chars_in_buffer() with flush_chars()")
To fix this we only need a small delay after the write() function to
make it has time to clear its buffer.
[Test case]
1. Add dell_uart_backlight.dyndbg="+pt" to the kernel cmdline
2. Boots up the system and check dmesg
3. Make sure there is no dell_uart_backlight rx NULL message in dmesg
4. Try to unload/reload dell_uart_backlight couple times and check dmesg again
[Where problems could occur]
sleep for 1ms is pretty short that it's not possible to lead to messages loss.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Mantic)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
--
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/2035299
Title:
dell-uart-backlight fails to communicate with the scalar IC somtimes.
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:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
Boots up the system and sometimes we can see below messages and that leads to
backlight driver doesn't get loaded.
[ 86.424880] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 86.603936] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[ 87.596047] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 87.775209] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[Fix]
After applying this patch, it appears that the read() command sometimes fails
to receive a response, even when increasing the retry times. This could be due
to our use of a spin lock to lock the UART port in the read() function,
preventing us from calling read() immediately after a write() function.
fbf84fb368923 ("UBUNTU: SAUCE: platform/x86: dell-uart-backlight:
replace chars_in_buffer() with flush_chars()")
To fix this we only need a small delay after the write() function to
make it has time to clear its buffer.
[Test case]
1. Add dell_uart_backlight.dyndbg="+pt" to the kernel cmdline
2. Boots up the system and check dmesg
3. Make sure there is no dell_uart_backlight rx NULL message in dmesg
4. Try to unload/reload dell_uart_backlight couple times and check dmesg again
[Where problems could occur]
sleep for 1ms is pretty short that it's not possible to lead to messages loss.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- 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/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed 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] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+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 2032767] Re: Fix ACPI TAD on some Intel based systems
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- 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/2032767 Title: Fix ACPI TAD on some Intel based systems Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed 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] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+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 2033025] Re: Fix numerous AER related issues
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- 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/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid 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] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034491/+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 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
Hi Kevin, have you used perf and analyze the flamegraph? -- 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/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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 2035285] Re: nft cannot load certain rulesets after kernel upgrade
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: nftables (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset'
command will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes
0 drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing
or denying certain packages in their firewall, for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035285/+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 2035285] 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 2035285
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
** Changed in: linux (Ubuntu Lunar)
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/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset'
command will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes
0 drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing
or denying certain packages in their firewall, for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035285/+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 2035285] Re: nft cannot load certain rulesets after kernel upgrade
** Also affects: nftables (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/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset'
command will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes
0 drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing
or denying certain packages in their firewall, for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035285/+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 2035285] Re: nft cannot load certain rulesets after kernel upgrade
Upstream nftables commits below apply cleanly on 1.0.6 (lunar upstream
version) and produce the correct results.
784597a4ed63b9decb10d74fdb49a1b021e22728
27c753e4a8d4744f479345e3f5e34cafef751602
3975430b12d97c92cdf03753342f2269153d5624
--
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/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
New
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset'
command will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes
0 drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing
or denying certain packages in their firewall, for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035285/+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 2035285] [NEW] nft cannot load certain rulesets after kernel upgrade
Public bug reported:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16, 192.168.13.0/24
} counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset' command
will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes 0
drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing or
denying certain packages in their firewall, for example.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Won't Fix
** Affects: nftables (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Won't Fix
** Affects: nftables (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Won't Fix
** Affects: nftables (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
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/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
New
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
[Kernel-packages] [Bug 2035283] Re: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035283 Title: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: trying to install gpr driver for nvidia gtx460 on a HPE DL380 G9 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2 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 DKMSKernelVersion: 6.2.0-32-generic Date: Tue Sep 12 16:44:16 2023 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.157-0ubuntu0.22.04.2:/var/lib/dkms/nvidia/390.157/build/nvidia/nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2023-09-11 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageVersion: 390.157-0ubuntu0.22.04.2 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035283/+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 2035283] [NEW] nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build
Public bug reported: trying to install gpr driver for nvidia gtx460 on a HPE DL380 G9 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2 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 DKMSKernelVersion: 6.2.0-32-generic Date: Tue Sep 12 16:44:16 2023 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.157-0ubuntu0.22.04.2:/var/lib/dkms/nvidia/390.157/build/nvidia/nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2023-09-11 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageVersion: 390.157-0ubuntu0.22.04.2 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035283 Title: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: trying to install gpr driver for nvidia gtx460 on a HPE DL380 G9 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2 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 DKMSKernelVersion: 6.2.0-32-generic Date: Tue Sep 12 16:44:16 2023 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.157-0ubuntu0.22.04.2:/var/lib/dkms/nvidia/390.157/build/nvidia/nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2023-09-11 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageVersion: 390.157-0ubuntu0.22.04.2 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.157-0ubuntu0.22.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035283/+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] 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 2035123 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/2035123 Title: scripts/pahole-flags.sh needs upstream fix Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: Triaged Status in linux source package in Jammy: Triaged Status in linux-bluefield source package in Jammy: Triaged Bug description: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. 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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
I tested the changes today and was able to successfully run enclave in debug mode. Thanks a lot Tim. -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 needs upstream fix
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Triaged -- 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/2035123 Title: scripts/pahole-flags.sh needs upstream fix Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: Triaged Status in linux source package in Jammy: Triaged Status in linux-bluefield source package in Jammy: Triaged Bug description: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. 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 2035123] Re: scripts/pahole-flags.sh needs upstream fix
It appears that Linus applied a fix for this directly in a merge commit: https://github.com/torvalds/linux/commits/fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4 When the change with this bug was backported to stable, the fix was squashed. But we appear to have cherry-picked the version from mainline instead of the one from stable which had the bug. ** Changed in: linux-bluefield (Ubuntu) Status: New => Triaged -- 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 needs upstream fix Status in linux-bluefield package in Ubuntu: Triaged Bug description: When doing a kernel make in our Jammy repo we notice the follow error being emitted: ./scripts/pahole-flags.sh: line 7: return: can only `return' from a function or sourced script It appears that while the Jammy baseline is 5.15.99 (as per the top-level Makefile) the file scripts/pahole-flags.sh is out of date with upstream 5.15.99 The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by making this change: 7c7 < return --- > exit 0 This seems like a simple fix, but not sure who should be fixing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+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 2035163] Re: Avoid address overwrite in kernel_connect
** No longer affects: linux-gke (Ubuntu Focal) ** No longer affects: linux-gke (Ubuntu Mantic) ** No longer affects: linux-gke (Ubuntu Lunar) -- 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: Invalid Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gke 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: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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 2035133] Re: linux-libc-dev:i386 is not produced anymore
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => 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/2035133 Title: linux-libc-dev:i386 is not produced anymore Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On Bionic, after i386 and other architectures were dropped from building, linux-libc-dev:i386 stopped being produced. That stills needs to be produced for userspace multi-arch support. Otherwise installing newer linux-libc-dev binaries will remove the i386 version of it, as they need to be the same version. [Test case] Install linux-libc-dev and linux-libc-dev:i386 prepared by the same source package. [Potential regression] Packages may fail to build or different config options may be enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035133/+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 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
$ uname -a Linux p5q3 6.5.1-060501-generic #202309020842 SMP PREEMPT_DYNAMIC Sat Sep 2 08:48:34 UTC 2023 x86_64 x86_64 x86_64 GNU/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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
$ LC_ALL=C apport-collect 2035278 dpkg-query: no packages found matching linux ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring
[Kernel-packages] [Bug 2035278] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700424/+files/ProcEnviron.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test
[Kernel-packages] [Bug 2035278] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700421/+files/ProcCpuinfoMinimal.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802]
[Kernel-packages] [Bug 2035278] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700422/+files/ProcEnviron.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
$ LC_ALL=C sudo apport-collect 2035278 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Please open this authorization page: (https://launchpad.net/+authorize-token?oauth_token=1JKJCS3jh98tTWrGqK0T_permission=DESKTOP_INTEGRATION) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 693, in check_end_user_authorization credentials.exchange_request_token_for_access_token(self.web_root) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 240, in exchange_request_token_for_access_token response, content = _http_post(url, headers, params) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 110, in _http_post raise HTTPError(response, content) lazr.restfulclient.errors.HTTPError: HTTP Error 401: Unauthorized Response headers: --- content-length: 57 content-security-policy: frame-ancestors 'self'; content-type: text/plain;charset=utf-8 date: Tue, 12 Sep 2023 19:04:34 GMT server: gunicorn status: 401 strict-transport-security: max-age=15552000 vary: Cookie,Authorization www-authenticate: OAuth realm="https://api.launchpad.net; x-content-type-options: nosniff x-content-type-warning: guessed from content x-frame-options: SAMEORIGIN x-launchpad-revision: 32eed776db4e1fe74faaa77122cde19862d565ac x-powered-by: Zope (www.zope.org), Python (www.python.org) x-request-id: 8f3cf56b-0b3f-4b30-9544-3c107b80469b x-vcs-revision: 32eed776db4e1fe74faaa77122cde19862d565ac x-xss-protection: 1; mode=block --- Response body: --- b'Request token has not yet been reviewed. Try again later.' --- During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 598, in sys.exit(UserInterface.run_argv()) File "/usr/lib/python3/dist-packages/apport/ui.py", line 966, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 780, in run_update_report if not self.crashdb.can_update(self.args.update_report): File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 586, in can_update bug = self.launchpad.bugs[crash_id] ^^ File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 170, in launchpad self.__launchpad = Launchpad.login_with( ^ File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in login_with return cls._authorize_token_and_login( ^^^ File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 451, in _authorize_token_and_login credentials = authorization_engine(credentials, credential_store) ^^^ File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 627, in __call__ self.make_end_user_authorize_token(credentials, request_token_string) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 718, in make_end_user_authorize_token self.wait_for_end_user_authorization(credentials) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 712, in wait_for_end_user_authorization self.check_end_user_authorization(credentials) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 705, in check_end_user_authorization raise EndUserNoAuthorization(e.content) launchpadlib.credentials.EndUserNoAuthorization: b'Request token has not yet been reviewed. Try again later.' ** Description changed: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100
[Kernel-packages] [Bug 2035278] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700423/+files/ProcCpuinfoMinimal.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802]
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035278/+attachment/5700420/+files/lspci-vvnn.log ** Description changed: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 10.525206] [drm] ib test on ring 0 succeeded in 0 usecs [ 10.525224] [drm] ib test on ring 3 succeeded in 0
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035278/+attachment/5700419/+files/syslog -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Confirmed Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded
[Kernel-packages] [Bug 2035278] 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 2035278 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Incomplete Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035278/+attachment/5700418/+files/dmesg -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Incomplete Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in
[Kernel-packages] [Bug 2035278] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700417/+files/ProcCpuinfoMinimal.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: Incomplete Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802]
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
apport information ** Description changed: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 10.525206] [drm] ib test on ring 0 succeeded in 0 usecs [ 10.525224] [drm] ib test on ring 3 succeeded in 0 usecs [ 11.200641] [drm] ib test on ring 5 succeeded [ 11.201298] [drm] Radeon Display Connectors [ 11.201300] [drm]
[Kernel-packages] [Bug 2035278] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700414/+files/ProcCpuinfoMinimal.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: New Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm]
[Kernel-packages] [Bug 2035278] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700415/+files/ProcEnviron.txt -- 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/2035278 Title: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios Status in linux package in Ubuntu: New Bug description: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5
[Kernel-packages] [Bug 2035278] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700413/+files/ProcCpuinfoMinimal.txt ** Description changed: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 10.525206] [drm] ib test on ring 0 succeeded in 0 usecs [ 10.525224] [drm] ib test on ring 3
[Kernel-packages] [Bug 2035278] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035278/+attachment/5700412/+files/ProcCpuinfoMinimal.txt ** Description changed: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 10.525206] [drm] ib test on ring 0 succeeded in 0 usecs [ 10.525224] [drm] ib test on ring 3
[Kernel-packages] [Bug 2035278] Re: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
apport information ** Tags added: apport-collected lunar wayland-session ** Description changed: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 10.525206] [drm] ib test on ring 0 succeeded in 0 usecs [ 10.525224] [drm] ib test on ring 3 succeeded in 0 usecs [ 11.200641] [drm] ib test on ring 5 succeeded [ 11.201298]
[Kernel-packages] [Bug 2035278] [NEW] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios
Public bug reported: Since Linux 6.5.x: [ 10.275589] [ 10.275594] fbcon: Taking over console [ 10.275598] UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.275603] index 1 is out of range for type 'UCHAR [1]' [ 10.275607] CPU: 3 PID: 320 Comm: systemd-udevd Not tainted 6.5.1-060501-generic #202309020842 [ 10.275609] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.275611] Call Trace: [ 10.275614] [ 10.275616] dump_stack_lvl+0x48/0x70 [ 10.275622] dump_stack+0x10/0x20 [ 10.275625] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.275629] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.275737] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.275816] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.275914] radeon_pm_init+0xd0/0x100 [radeon] [ 10.276013] rv770_init+0x1fa/0x3d0 [radeon] [ 10.276110] radeon_device_init+0x540/0xa90 [radeon] [ 10.276187] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.276265] drm_dev_register+0x10e/0x240 [drm] [ 10.276347] radeon_pci_probe+0xec/0x180 [radeon] [ 10.276423] local_pci_probe+0x47/0xb0 [ 10.276427] pci_call_probe+0x55/0x190 [ 10.276429] pci_device_probe+0x84/0x120 [ 10.276432] really_probe+0x1c7/0x410 [ 10.276435] __driver_probe_device+0x8c/0x180 [ 10.276437] driver_probe_device+0x24/0xd0 [ 10.276440] __driver_attach+0x10b/0x210 [ 10.276442] ? __pfx___driver_attach+0x10/0x10 [ 10.276444] bus_for_each_dev+0x8d/0xf0 [ 10.276448] driver_attach+0x1e/0x30 [ 10.276450] bus_add_driver+0x127/0x240 [ 10.276453] driver_register+0x5e/0x130 [ 10.276456] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.276531] __pci_register_driver+0x62/0x70 [ 10.276535] radeon_module_init+0x4c/0xff0 [radeon] [ 10.276610] do_one_initcall+0x5e/0x340 [ 10.276620] do_init_module+0x68/0x260 [ 10.276624] load_module+0xba1/0xcf0 [ 10.276627] ? find_vmap_area+0x42/0x70 [ 10.276632] __do_sys_init_module+0x1a7/0x1e0 [ 10.276635] ? __do_sys_init_module+0x1a7/0x1e0 [ 10.276638] __x64_sys_init_module+0x1a/0x30 [ 10.276641] do_syscall_64+0x5c/0x90 [ 10.276644] ? do_syscall_64+0x68/0x90 [ 10.276646] ? exit_to_user_mode_prepare+0x30/0xb0 [ 10.276650] ? irqentry_exit_to_user_mode+0x17/0x20 [ 10.276653] ? irqentry_exit+0x43/0x50 [ 10.276655] ? exc_page_fault+0x94/0x1b0 [ 10.276657] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.276661] RIP: 0033:0x7f3969d1ed8e [ 10.276682] Code: 48 8b 0d 8d 70 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5a 70 0d 00 f7 d8 64 89 01 48 [ 10.276684] RSP: 002b:7ffee1310ae8 EFLAGS: 0246 ORIG_RAX: 00af [ 10.276688] RAX: ffda RBX: 5560681b9790 RCX: 7f3969d1ed8e [ 10.276689] RDX: 7f396a015458 RSI: 00441061 RDI: 7f3967de0010 [ 10.276691] RBP: 7f396a015458 R08: 00261000 R09: [ 10.276692] R10: 00015221 R11: 0246 R12: 0002 [ 10.276694] R13: 5560681bcff0 R14: R15: 5560681be500 [ 10.276696] [ 10.276716] [ 10.277624] [drm] radeon: dpm initialized [ 10.279186] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 10.280149] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 10.293073] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 10.293688] radeon :01:00.0: WB enabled [ 10.293693] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 10.293695] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 10.293951] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 10.294075] radeon :01:00.0: radeon: MSI limited to 32-bit [ 10.294142] radeon :01:00.0: radeon: using MSI. [ 10.294170] [drm] radeon: irq initialized. [ 10.340209] [drm] ring test on 0 succeeded in 1 usecs [ 10.340218] [drm] ring test on 3 succeeded in 2 usecs [ 10.524802] [drm] ring test on 5 succeeded in 1 usecs [ 10.524808] [drm] UVD initialized successfully. [ 10.525029] snd_hda_intel :01:00.1: bound :01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 10.525206] [drm] ib test on ring 0 succeeded in 0 usecs [ 10.525224] [drm] ib test on ring 3 succeeded in 0 usecs [ 11.200641] [drm] ib test on ring 5 succeeded [ 11.201298] [drm] Radeon Display Connectors [ 11.201300] [drm] Connector 0: [ 11.201301] [drm] HDMI-A-1 [ 11.201302] [drm] HPD2 [ 11.201303] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [ 11.201305] [drm] Encoders: [
[Kernel-packages] [Bug 2033735] Re: [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
When I boot with Intel dynamic graphics, the NVidia GPU seems to be not
detected: Ubuntu drivers does not offer to add any proprietary driver.
--
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/2033735
Title:
[mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi,
Legion laptop with Nvidia.
- Nouveau : no hdmi
- Nvidia 535 dynamic graphics : no HDMI (screen not detected)
- Nvidia 535 discrete graphics : HDMI is detected
So I suppose this bug to be linked to Intel GPU.
All was ok with previous 6.3 kernel.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fthx 3395 F wireplumber
/dev/snd/controlC1: fthx 3395 F wireplumber
/dev/snd/seq:fthx 3390 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-09-15 (723 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
Tags: mantic wayland-session
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/10/2023
dmi.bios.release: 1.54
dmi.bios.vendor: LENOVO
dmi.bios.version: J2CN54WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 5 Pro 16IAH7H
dmi.ec.firmware.release: 1.54
dmi.modalias:
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
dmi.product.family: Legion 5 Pro 16IAH7H
dmi.product.name: 82RF
dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
dmi.product.version: Legion 5 Pro 16IAH7H
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+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 2035235] [NEW] package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: my laptop is a dual booot , once during windows 11 update the default boot allowed the ubuntu boot which probably corrupted the kernel , i can log into the old kernal but cannot delete the corrupted kernal . ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libssh2-1:amd64: Install libaria2-0:amd64: Install aria2:amd64: Install mainline:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kanna 1466 F wireplumber /dev/snd/controlC1: kanna 1466 F wireplumber /dev/snd/seq:kanna 1463 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Sep 13 00:19:29 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-06-30 (73 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: AFTERSHOCK PC GM6PX7X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=8b190114-bfae-4f94-a9d5-3e07cd531385 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: dkms Title: package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.06AFT02 dmi.board.asset.tag: Standard dmi.board.name: GM6PX7X dmi.board.vendor: AFTERSHOCK PC dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.06AFT02:bd02/10/2023:br5.27:efr0.29:svnAFTERSHOCKPC:pnGM6PX7X:pvrStandard:rvnAFTERSHOCKPC:rnGM6PX7X:rvrStandard:cvnStandard:ct10:cvrStandard:sku0001: dmi.product.family: RPL dmi.product.name: GM6PX7X dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: AFTERSHOCK PC ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2035235 Title: package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: my laptop is a dual booot , once during windows 11 update the default boot allowed the ubuntu boot which probably corrupted the kernel , i can log into the old kernal but cannot delete the corrupted kernal . ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libssh2-1:amd64: Install libaria2-0:amd64: Install aria2:amd64: Install mainline:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kanna 1466 F wireplumber /dev/snd/controlC1: kanna 1466 F wireplumber /dev/snd/seq:kanna 1463 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Sep 13 00:19:29 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-06-30 (73 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: AFTERSHOCK PC GM6PX7X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=8b190114-bfae-4f94-a9d5-3e07cd531385 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: dkms Title: package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.06AFT02 dmi.board.asset.tag: Standard dmi.board.name: GM6PX7X dmi.board.vendor: AFTERSHOCK PC dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type:
[Kernel-packages] [Bug 2034607] Re: Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
Please see the post I just made here:
https://stackoverflow.com/questions/77090823/linux-kernel-overcommit-
support-isnt-working-properly-cannot-access-all-memory
If this is a bug, it's in the linux-kernel, not just Ubuntu as RHEL and
Fedora have the same behavior.
Feel free to close this.
Thamks,
Gene
--
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/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
than
// 1/2 of the pool
[Kernel-packages] [Bug 2035229] 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 2035229 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/2035229 Title: Yoga370 - stylus battery level no longer displaying Status in linux package in Ubuntu: Incomplete Bug description: Description: Linux Mint 21 Release: 21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info:
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
This bug was fixed in the package glibc - 2.35-0ubuntu3.3 --- glibc (2.35-0ubuntu3.3) jammy; urgency=medium * Drop SVE patches due to kernal-related performance regression * Fix the armhf stripping exception for ld.so (LP: #1927192) glibc (2.35-0ubuntu3.2) jammy; urgency=medium * d/rules.d/debhelper.mk: fix permissions of libc.so (LP: #1989082) * Cherry-picks from upstream: - d/p/lp1999551/*: arm64 memcpy optimization (LP: #1999551) - d/p/lp1995362*.patch: Fix ldd segfault with missing libs (LP: #1995362) - d/p/lp2007796*: Fix missing cancellation point in pthread (LP: #2007796) - d/p/lp2007599*: add new tunables for s390x (LP: #2007599) - d/p/lp2011421/*: Fix crash on TDX-enabled platforms (LP: #2011421) - d/p/lp1992159*: Fix socket.h headers for non-GNU compilers (LP: #1992159) -- Simon Chopin Wed, 26 Jul 2023 10:27:54 +0200 ** Changed in: glibc (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: New Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+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 2011421] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: New Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+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 2035229] [NEW] Yoga370 - stylus battery level no longer displaying
Public bug reported: Description:Linux Mint 21 Release:21 (21.1) Power Manager 1.26.0 Power management daemon cat /proc/version_signature > version.log = Ubuntu 5.15.0-83.92-generic 5.15.116 On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management applet (Power Manager 1.26.0 Power management daemon) in panel does not display any item listed as stylus, including not displaying its battery level (does function in kernel 5.15.0-82-generic). ubuntu-bug linux - *** Problem in linux-image-5.15.0-83-generic The problem cannot be reported: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. === SYSTEM INFORMATION [code] System: Kernel: 5.15.0-83-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0 wm: Compiz dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 20JH002KRT v: Thinkpad YOGA 370 serial: Chassis: type: 31 serial: Mobo: LENOVO model: 20JH002KRT v: 0B98417 WIN serial: UEFI: LENOVO v: R0HET57W (1.37 ) date: 10/20/2020 Battery: ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/51.0 Wh (81.9%) volts: 17.0 min: 15.2 model: Celxpert 01AV434 serial: status: Charging CPU: Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 3076 high: 3087 min/max: 400/3100 cores: 1: 3085 2: 3087 3: 3082 4: 3050 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 04f2:b5ce Display: x11 server: X.Org v: 1.21.1.4 compositor: Compiz v: 0.9.14.1 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 166 diag: 337mm (13.3") OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-83-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: no Sound Server-3: PipeWire v: 0.3.79 running: yes Network: Device-1: Intel Ethernet I219-V vendor: Lenovo ThinkPad X1 Carbon 5th Gen driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd IF: wlp4s0 state: up mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b Report: hciconfig ID: hci0 rfk-id: 2 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 100 Drives: Local Storage: total: 356.23 GiB used: 148.32 GiB (41.6%) ID-1: /dev/mmcblk0 model: SDU1 size: 117.75 GiB serial: ID-2: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 194.84 GiB used: 125.36 GiB (64.3%) fs: ext4 dev: /dev/nvme0n1p6 ID-2: /boot/efi size: 500 MiB used: 48.7 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile USB: Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 Device-1: 1-5:2 info: Alcor Micro AU9540 Smartcard Reader type: Smart Card driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 058f:9540 Device-2: 1-7:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b Device-3: 1-8:4 info: Chicony Integrated Camera type: Video driver: uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 04f2:b5ce Device-4: 1-9:5 info: Validity Sensors type: driver: usbfs rev: 2.0 speed: 12 Mb/s chip-ID: 138a:0097 Device-5: 1-10:6 info: Wacom Pen and multitouch sensor type: HID driver: usbhid,wacom rev: 2.0 speed: 12 Mb/s chip-ID: 056a:509c Hub-2: 2-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003 Sensors: System Temperatures: cpu: 56.0 C mobo: N/A Fan Speeds (RPM): fan-1: 2606 Repos: Packages: 3131 apt: 3108 flatpak: 23 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/alessandro-strada-google-drive-ocamlfuse-beta-jammy.list 1: deb http:
[Kernel-packages] [Bug 2033097] Re: hwe kernel packages install nvidia driver 535.54 when only 535.86 is available
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules-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-restricted-modules-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033097 Title: hwe kernel packages install nvidia driver 535.54 when only 535.86 is available Status in linux-restricted-modules-hwe-6.2 package in Ubuntu: Confirmed Bug description: In Ubuntu 22.04, when trying to use the hwe kernel with the pre-built nvidia 535 drivers, the linux-modules-nvidia-535-generic-hwe-22.04 package installs the 535.54.03 version, but everything else is using 535.86.01. > apt show linux-modules-nvidia-535-generic-hwe-22.04 | grep -i provides Provides: nvidia-dkms-535 (= 535.54.03-0ubuntu0.22.04.1), nvidia-prebuilt-kernel Can this package be updated to use 535.86? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.2/+bug/2033097/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Description changed: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] - User tested. + User test results pending, but its a fix commit so should likely be + applied regardless. [Regression Potential] SGX could continue to fail. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
Was the cause of this ever determined? I am seeing something similar on some of my systems. Times are usually around 1s, sometimes slightly higher. # uname -r 4.15.0-193-generic # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:144 69349171178307 8:128 4718621058 8:112 4604996397 8:96 4625378704 8:80 4873085108 8:64 3777190161 8:48 4749702443 8:32 8346248400 8:16 9260262419 8:0 154939957376379 real0m1.03s user0m0.00s sys 0m1.03s -- 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/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- 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/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Description changed: + SRU Justification + + [Impact] + In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. + + [Test Plan] + + User tested. + + [Regression Potential] + + SGX could continue to fail. -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User tested. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034745] 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 2034745 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User tested. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Package changed: linux-azure (Ubuntu) => linux (Ubuntu) -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User tested. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
Please try the referenced kernel jammy- azure-5.15.0-1049.56~lp2034745.1.tgz with the fix commit. Note that this kernel is not signed for a UEFI secure boot environment. ** Attachment added: "Test kernel" https://kernel.ubuntu.com/~rtg/jammy-sgx-xsave-lp2034745/5.15.0-1049.56~lp2034745.1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux-azure package in Ubuntu: New Bug description: In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034745/+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 2003674] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2023-09-12 10:27 EDT--- FYI: the commits are available through 6.6-rc1 now. -- 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/2003674 Title: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Feature Description: Enable KVM and QEMU for AP passthrough to Secure Execution guests. This includes setup, configuration and teardown of AP related resources. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003674/+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 2035213] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035213 Title: package linux-tools-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 Status in linux package in Ubuntu: Confirmed Bug description: I had installed perf from intel (linux-intel-iotg-tools-common", when I tried to run it, I received a message saying that I had to install linux-tools-common. Tried to, and received the following error message: (Brazil Portuguese): linux-hwe-6.2-tools-6.2.0-32: Depends: libcap2 (>= 1:2.10) mas a 1:2.44-1ubuntu0.22.04.1 está instalada Depends: libpci3 (>= 1:3.5.1) mas a 1:3.7.0-6 está instalada Depends: libudev1 (>= 183) mas a 249.11-0ubuntu3.9 está instalada Depends: zlib1g (>= 1:1.2.3.3) mas a 1:1.2.11.dfsg-2ubuntu9.2 está instalada Depends: linux-tools-common mas não está instalado ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) 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 AptOrdering: linux-tools-common:amd64: Install linux-hwe-6.2-tools-6.2.0-32:amd64: Install linux-tools-6.2.0-32-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 12 10:58:03 2023 DpkgTerminalLog: A preparar para desempacotar .../linux-tools-common_5.15.0-83.92_all.deb ... A descompactar linux-tools-common (5.15.0-83.92) ... [1mdpkg:[0m erro ao processar o arquivo /var/cache/apt/archives/linux-tools-common_5.15.0-83.92_all.deb (--unpack): a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 ErrorMessage: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 InstallationDate: Installed on 2023-02-27 (196 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=89702d3d-e1f1-4798-a6e8-ea9fc5c70121 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2108 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E/BR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2108:bd04/14/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035213/+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 2035214] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035214 Title: repeated error appear Status in linux package in Ubuntu: Confirmed Bug description: bluetooth.service: Two services allocated for the same bus name org.bluez, refusing operation. Ubuntu 6.2.0-32.32-generic 6.2.16 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mamdouh2968 F pipewire mamdouh2973 F wireplumber /dev/snd/seq:mamdouh2968 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 18:04:03 2023 InstallationDate: Installed on 2023-05-15 (120 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 21AJS1KU00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=60e6334d-3490-41e8-aab4-6190f637ccf1 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.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2023 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET16W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AJS1KU00 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: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN3MET16W(1.15):bd06/25/2023:br1.15:efr1.10:svnLENOVO:pn21AJS1KU00:pvrThinkPadT14Gen3:rvnLENOVO:rn21AJS1KU00:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AJ_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AJS1KU00 dmi.product.sku: LENOVO_MT_21AJ_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035214/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
** Package changed: linux-signed-azure-5.15 (Ubuntu) => linux-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux-azure package in Ubuntu: New Bug description: In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034745/+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 2035214] [NEW] repeated error appear
Public bug reported: bluetooth.service: Two services allocated for the same bus name org.bluez, refusing operation. Ubuntu 6.2.0-32.32-generic 6.2.16 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mamdouh2968 F pipewire mamdouh2973 F wireplumber /dev/snd/seq:mamdouh2968 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 18:04:03 2023 InstallationDate: Installed on 2023-05-15 (120 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 21AJS1KU00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=60e6334d-3490-41e8-aab4-6190f637ccf1 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.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2023 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET16W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AJS1KU00 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: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN3MET16W(1.15):bd06/25/2023:br1.15:efr1.10:svnLENOVO:pn21AJS1KU00:pvrThinkPadT14Gen3:rvnLENOVO:rn21AJS1KU00:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AJ_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AJS1KU00 dmi.product.sku: LENOVO_MT_21AJ_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035214 Title: repeated error appear Status in linux package in Ubuntu: New Bug description: bluetooth.service: Two services allocated for the same bus name org.bluez, refusing operation. Ubuntu 6.2.0-32.32-generic 6.2.16 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mamdouh2968 F pipewire mamdouh2973 F wireplumber /dev/snd/seq:mamdouh2968 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 18:04:03 2023 InstallationDate: Installed on 2023-05-15 (120 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 21AJS1KU00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=60e6334d-3490-41e8-aab4-6190f637ccf1 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.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2023 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET16W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AJS1KU00 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: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN3MET16W(1.15):bd06/25/2023:br1.15:efr1.10:svnLENOVO:pn21AJS1KU00:pvrThinkPadT14Gen3:rvnLENOVO:rn21AJS1KU00:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AJ_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AJS1KU00 dmi.product.sku: LENOVO_MT_21AJ_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 2035213] [NEW] package linux-tools-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools
Public bug reported: I had installed perf from intel (linux-intel-iotg-tools-common", when I tried to run it, I received a message saying that I had to install linux-tools-common. Tried to, and received the following error message: (Brazil Portuguese): linux-hwe-6.2-tools-6.2.0-32: Depends: libcap2 (>= 1:2.10) mas a 1:2.44-1ubuntu0.22.04.1 está instalada Depends: libpci3 (>= 1:3.5.1) mas a 1:3.7.0-6 está instalada Depends: libudev1 (>= 183) mas a 249.11-0ubuntu3.9 está instalada Depends: zlib1g (>= 1:1.2.3.3) mas a 1:1.2.11.dfsg-2ubuntu9.2 está instalada Depends: linux-tools-common mas não está instalado ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) 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 AptOrdering: linux-tools-common:amd64: Install linux-hwe-6.2-tools-6.2.0-32:amd64: Install linux-tools-6.2.0-32-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 12 10:58:03 2023 DpkgTerminalLog: A preparar para desempacotar .../linux-tools-common_5.15.0-83.92_all.deb ... A descompactar linux-tools-common (5.15.0-83.92) ... [1mdpkg:[0m erro ao processar o arquivo /var/cache/apt/archives/linux-tools-common_5.15.0-83.92_all.deb (--unpack): a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 ErrorMessage: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 InstallationDate: Installed on 2023-02-27 (196 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=89702d3d-e1f1-4798-a6e8-ea9fc5c70121 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2108 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E/BR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2108:bd04/14/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035213 Title: package linux-tools-common (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/acpidbg', que também está no pacote linux-intel-iotg-tools-common 5.15.0-1038.43 Status in linux package in Ubuntu: New Bug description: I had installed perf from intel (linux-intel-iotg-tools-common", when I tried to run it, I received a message saying that I had to install linux-tools-common. Tried to, and received the following error message: (Brazil Portuguese): linux-hwe-6.2-tools-6.2.0-32: Depends: libcap2 (>= 1:2.10) mas a 1:2.44-1ubuntu0.22.04.1 está instalada Depends: libpci3 (>= 1:3.5.1) mas a 1:3.7.0-6 está instalada Depends: libudev1 (>= 183) mas a 249.11-0ubuntu3.9 está instalada Depends: zlib1g (>= 1:1.2.3.3) mas a 1:1.2.11.dfsg-2ubuntu9.2 está instalada Depends: linux-tools-common mas não está instalado ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) 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 AptOrdering:
[Kernel-packages] [Bug 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
** Description changed: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f dmesg: Sep 08 10:51:39 : [ cut here ] Sep 08 10:51:39 : NETDEV WATCHDOG: eno2 (r8169): transmit queue 0 timed out Sep 08 10:51:39 : WARNING: CPU: 10 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230 - Sep 08 10:51:39 : Modules linked in: rfcomm xt_CHECKSUM nvme_fabrics nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo cmac algif_hash algif_skc> - Sep 08 10:51:39 : typec_ucsi btintel spi_nor hid_multitouch mei_pxp mei_hdcp kvm iwlmvm typec ee1004 mtd intel_rapl_msr snd_seq_midi btmtk i915 btrf> - Sep 08 10:51:39 : asus_wmi ledtrig_audio sparse_keymap platform_profile hid_generic uas usbhid usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidi> + Sep 08 10:51:39 : Modules linked in: rfcomm xt_CHECKSUM nvme_fabrics nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo cmac algif_hash algif_skci + pher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_c + onntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat sunrpc nf_tables nfnetlink binfmt_misc dm_crypt nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic snd_sof + _pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd + _sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmae + ngine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_tcc_cooling x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep btusb btrtl uc + si_ccg snd_pcm cmdlinepart btbcm kvm_intel + Sep 08 10:51:39 : typec_ucsi btintel spi_nor hid_multitouch mei_pxp mei_hdcp kvm iwlmvm typec ee1004 mtd intel_rapl_msr snd_seq_midi btmtk i915 btrfs + mac80211 snd_seq_midi_event irqbypass bluetooth snd_rawmidi rapl blake2b_generic drm_buddy libarc4 snd_seq ttm intel_cstate xor mfd_aaeon snd_seq_device ecdh_gene + ric asus_nb_wmi input_leds iwlwifi joydev raid6_pq processor_thermal_device_pci_legacy ecc wmi_bmof mxm_wmi snd_timer drm_display_helper processor_thermal_device s + nd r8169 cec processor_thermal_rfim i2c_i801 rc_core cfg80211 spi_intel_pci i2c_nvidia_gpu processor_thermal_mbox soundcore spi_intel i2c_ccgx_ucsi realtek intel_l + pss_pci mei_me i2c_algo_bit i2c_smbus processor_thermal_rapl intel_lpss mei intel_rapl_common idma64 intel_pch_thermal intel_soc_dts_iosf int3403_thermal int3400_t + hermal int340x_thermal_zone acpi_thermal_rel acpi_tad acpi_pad asus_wireless mac_hid nvidia_uvm(POE) sch_fq_codel pstore_blk ramoops pstore_zone reed_solomon efi_p + store xfs libcrc32c wacom hid_asus + Sep 08 10:51:39 : asus_wmi ledtrig_audio sparse_keymap platform_profile hid_generic uas usbhid usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidia + (POE) crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 aesni_intel drm_kms_helper nvme crypto_simd cryptd drm nvme_co + re serio_raw ahci i2c_hid_acpi syscopyarea nvme_common libahci i2c_hid sysfillrect xhci_pci sysimgblt xhci_pci_renesas hid video wmi pinctrl_cannonlake overlay ipt + able_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables coretemp msr parport_pc ppdev lp parport ip_tables x_tables autofs4 Sep 08 10:51:39 : CPU: 10 PID: 0 Comm: swapper/10 Tainted: P OE 6.2.0-32-generic #32~22.04.1-Ubuntu Sep 08 10:51:39 : Hardware name: ASUSTeK COMPUTER INC. ROG Strix G731GW_G731GW/G731GW, BIOS G731GW.309 01/29/2021 Sep 08 10:51:39 : RIP: 0010:dev_watchdog+0x21f/0x230 - Sep 08 10:51:39 : Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 66 83 78 01 01 e8 56 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 08 4f 84 91 48 89 c2 e8 61 df 2b ff> + Sep 08 10:51:39 : Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 66 83 78 01 01 e8 56 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 08 4f 84 91 48 89 c2 e8 61 df 2b ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 Sep 08 10:51:39 : RSP: 0018:ace9c0378e70 EFLAGS: 00010246 Sep 08 10:51:39 : RAX: RBX: 9944cf17c4c8 RCX: Sep 08 10:51:39 :
[Kernel-packages] [Bug 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
unfortunately I don't have that right now. And when network is dead apport-collect won't work. But I added some trace info from dmseg, hope that will help a little. ** Description changed: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f + + dmesg: + + Sep 08 10:51:39 : [ cut here ] + Sep 08 10:51:39 : NETDEV WATCHDOG: eno2 (r8169): transmit queue 0 timed out + Sep 08 10:51:39 : WARNING: CPU: 10 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : Modules linked in: rfcomm xt_CHECKSUM nvme_fabrics nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo cmac algif_hash algif_skc> + Sep 08 10:51:39 : typec_ucsi btintel spi_nor hid_multitouch mei_pxp mei_hdcp kvm iwlmvm typec ee1004 mtd intel_rapl_msr snd_seq_midi btmtk i915 btrf> + Sep 08 10:51:39 : asus_wmi ledtrig_audio sparse_keymap platform_profile hid_generic uas usbhid usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidi> + Sep 08 10:51:39 : CPU: 10 PID: 0 Comm: swapper/10 Tainted: P OE 6.2.0-32-generic #32~22.04.1-Ubuntu + Sep 08 10:51:39 : Hardware name: ASUSTeK COMPUTER INC. ROG Strix G731GW_G731GW/G731GW, BIOS G731GW.309 01/29/2021 + Sep 08 10:51:39 : RIP: 0010:dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 66 83 78 01 01 e8 56 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 08 4f 84 91 48 89 c2 e8 61 df 2b ff> + Sep 08 10:51:39 : RSP: 0018:ace9c0378e70 EFLAGS: 00010246 + Sep 08 10:51:39 : RAX: RBX: 9944cf17c4c8 RCX: + Sep 08 10:51:39 : RDX: RSI: RDI: + Sep 08 10:51:39 : RBP: ace9c0378e98 R08: R09: + Sep 08 10:51:39 : R10: R11: R12: 9944cf17c000 + Sep 08 10:51:39 : R13: 9944cf17c41c R14: R15: + Sep 08 10:51:39 : FS: () GS:9953fdc8() knlGS: + Sep 08 10:51:39 : CS: 0010 DS: ES: CR0: 80050033 + Sep 08 10:51:39 : CR2: 24e000389000 CR3: 000d32e10002 CR4: 003706e0 + Sep 08 10:51:39 : Call Trace: + Sep 08 10:51:39 : + Sep 08 10:51:39 : ? show_regs+0x72/0x90 + Sep 08 10:51:39 : ? dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : ? __warn+0x8d/0x160 + Sep 08 10:51:39 : ? dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : ? report_bug+0x1bb/0x1d0 + Sep 08 10:51:39 : ? handle_bug+0x46/0x90 + Sep 08 10:51:39 : ? exc_invalid_op+0x19/0x80 + Sep 08 10:51:39 : ? asm_exc_invalid_op+0x1b/0x20 + Sep 08 10:51:39 : ? dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : ? __pfx_dev_watchdog+0x10/0x10 + Sep 08 10:51:39 : call_timer_fn+0x29/0x160 + Sep 08 10:51:39 : ? __pfx_dev_watchdog+0x10/0x10 + Sep 08 10:51:39 : __run_timers.part.0+0x1fb/0x2b0 + Sep 08 10:51:39 : ? ktime_get+0x43/0xc0 + Sep 08 10:51:39 : ? __pfx_tick_sched_timer+0x10/0x10 + Sep 08 10:51:39 : ? lapic_next_deadline+0x2c/0x50 + Sep 08 10:51:39 : ? clockevents_program_event+0xb2/0x140 + Sep 08 10:51:39 : run_timer_softirq+0x2a/0x60 + Sep 08 10:51:39 : __do_softirq+0xda/0x330 + Sep 08 10:51:39 : ? hrtimer_interrupt+0x12b/0x250 + Sep 08 10:51:39 : __irq_exit_rcu+0xa2/0xd0 + Sep 08 10:51:39 : irq_exit_rcu+0xe/0x20 + Sep 08 10:51:39 : sysvec_apic_timer_interrupt+0x96/0xb0 + Sep 08 10:51:39 : + Sep 08 10:51:39 : + Sep 08 10:51:39 : asm_sysvec_apic_timer_interrupt+0x1b/0x20 + Sep 08 10:51:39 : RIP: 0010:cpuidle_enter_state+0xde/0x6f0 + Sep 08 10:51:39 : Code: 79 51 6f e8 a4 34 45 ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 52 13 44 ff 80 7d d0 00 0f 85 e8 00 00 00 fb 0f 1f 44 00 00> + Sep 08 10:51:39 : RSP: 0018:ace9c015fe28 EFLAGS: 0246 + Sep 08 10:51:39 : RAX: RBX: cce9bfc80100 RCX: + Sep 08 10:51:39 : RDX: 000a RSI: RDI: + Sep 08 10:51:39 : RBP: ace9c015fe78 R08: R09: + Sep 08 10:51:39 : R10: R11: R12: 922c2840 + Sep 08 10:51:39 : R13: 0004 R14: 0004 R15: 02c008948c36 + Sep 08 10:51:39 : ? cpuidle_enter_state+0xce/0x6f0 + Sep 08 10:51:39 : cpuidle_enter+0x2e/0x50 + Sep 08 10:51:39 : cpuidle_idle_call+0x14f/0x1e0 + Sep 08 10:51:39 :
[Kernel-packages] [Bug 1929030] Re: cheese image flickers
No longer occurred due to fix or new version. Marked as Invalid. ** 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/1929030 Title: cheese image flickers Status in linux package in Ubuntu: Invalid Bug description: Start cheese, the image on the screen flickers and I have a lot of messages: (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: code not implemented. Please file a bug at https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: ../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp: invalid video buffer received I don't know if the problem is due to cheese, starting cheese and doing 'ubuntu-bug cheese' the bug seems opened against linux package. note: problem occurs in both sessions Xorg and Wayland starting cheese as superuser the problem does not occurs the problem is described also in https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689 corrado@corrado-n3-ii-0501:~$ apt policy cheese cheese: Installed: 3.38.0-3 Candidate: 3.38.0-3 Version table: *** 3.38.0-3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-ii-0501:~$ ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu66 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 20 09:56:12 2021 InstallationDate: Installed on 2021-05-01 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501) MachineType: Dell Inc. Inspiron 3793 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu66 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1517 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-05-01 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3793 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session impish Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name:
[Kernel-packages] [Bug 2035210] [NEW] package linux-image-5.15.0-79-generic 5.15.0-79.86~20.04.2 failed to install/upgrade: installed linux-image-5.15.0-79-generic package pre-removal script subproces
Public bug reported: Error after restarting the system since the last update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-79-generic 5.15.0-79.86~20.04.2 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 8 11:03:07 2023 ErrorMessage: installed linux-image-5.15.0-79-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-21 (721 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-79-generic 5.15.0-79.86~20.04.2 failed to install/upgrade: installed linux-image-5.15.0-79-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-02-13 (211 days ago) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/2035210 Title: package linux-image-5.15.0-79-generic 5.15.0-79.86~20.04.2 failed to install/upgrade: installed linux-image-5.15.0-79-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Error after restarting the system since the last update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-79-generic 5.15.0-79.86~20.04.2 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 8 11:03:07 2023 ErrorMessage: installed linux-image-5.15.0-79-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-21 (721 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-79-generic 5.15.0-79.86~20.04.2 failed to install/upgrade: installed linux-image-5.15.0-79-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-02-13 (211 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2035210/+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 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1048.44)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1048.44) for jammy have finished running. The following regressions have been reported in tests triggered by the package: digimend-dkms/10-4 (amd64, arm64) dm-writeboost/unknown (amd64) v4l2loopback/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035128] Re: mlxbf-gige: Enable the OOB port in mlxbf_gige_open
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035128 Title: mlxbf-gige: Enable the OOB port in mlxbf_gige_open Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: New Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] At the moment, the OOB port is enabled in the mlxbf_gige_probe function. If the mlxbf_gige_open is not executed, this could cause pause frames to increase in the case where there is high backgroud traffic. This results in clogging the BMC port as well. [Fix] * Move enabling the OOB port to mlxbf_gige_open. [Test Case] * Main test for this bug: Check that the BMC is always pingable while pushing a BFB Other tests: * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Do the reboot test and powercycle test and check the oob_net0 interface again * Push BFB multiple times and make sure the OOB is up and running [Regression Potential] Since are moving code that hasn't moved since BF2, it is important to make sure that there is no regression. Make sure that the OOB interface is always up and pingable after the reboot test, the powercycle test and after pushing a BFB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035128/+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 2035204] [NEW] ext4 filesystem remounted read-only during larger transfers
Public bug reported: i'm reporting this here because the problem was solved when running a 5.15 or 5.19 kernel, but reappeared when trying 6.2 again. i therefore assume it might indeed point to a bug in the 6.2 kernel. i often do larger file transfers on a desktop machine currently running kubuntu 22.04.3 LTS with kubuntu backports and HWE kernel (low latency for audio recordings). a single recording session can be 20 GB, i'm rsyncing it from one partition to another on the same system. since a few weeks, i'm running into file system issues during these transfers: [15104.146766] Aborting journal on device md6-8. [15104.166906] EXT4-fs error (device md6): ext4_journal_check_start:83: comm rsync: Detected aborted journal [15104.695117] journal_release_journal_head: freeing b_frozen_data the device is then re-mounted read-only an rsync aborts. this happens out of nowhere after a few gigabytes of data and is not limited to a specific RAID device. i ran a complete long test with smartmontools on both disks, it didn't find any issues. after such an incident, e2fsck fixes the number of free inodes and blocks and it can be used again, until the next large file transfer. i ran memcheck86 and indeed found some tests were failing with one of my RAM modules, but removing the module didn't solve the issue. what actually solved it was using an older kernel version. i first tried 5.15 and am now using 5.19, i don't get read-only filesystems on large transfers with any of both. some additional info that might be relevant: - the filesystems are all on RAID 1 devices, ext4 and use fscrypt - the hardware on the affected machine is pretty dated (ASUS Z97-K mainboard, intel i5-4460 CPU 3.20 GHz, 8GB DDR3 RAM, NVIDIA GeForce GT 610), except for the hard drives ** Affects: linux-signed-lowlatency-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2035204 Title: ext4 filesystem remounted read-only during larger transfers Status in linux-signed-lowlatency-hwe-6.2 package in Ubuntu: New Bug description: i'm reporting this here because the problem was solved when running a 5.15 or 5.19 kernel, but reappeared when trying 6.2 again. i therefore assume it might indeed point to a bug in the 6.2 kernel. i often do larger file transfers on a desktop machine currently running kubuntu 22.04.3 LTS with kubuntu backports and HWE kernel (low latency for audio recordings). a single recording session can be 20 GB, i'm rsyncing it from one partition to another on the same system. since a few weeks, i'm running into file system issues during these transfers: [15104.146766] Aborting journal on device md6-8. [15104.166906] EXT4-fs error (device md6): ext4_journal_check_start:83: comm rsync: Detected aborted journal [15104.695117] journal_release_journal_head: freeing b_frozen_data the device is then re-mounted read-only an rsync aborts. this happens out of nowhere after a few gigabytes of data and is not limited to a specific RAID device. i ran a complete long test with smartmontools on both disks, it didn't find any issues. after such an incident, e2fsck fixes the number of free inodes and blocks and it can be used again, until the next large file transfer. i ran memcheck86 and indeed found some tests were failing with one of my RAM modules, but removing the module didn't solve the issue. what actually solved it was using an older kernel version. i first tried 5.15 and am now using 5.19, i don't get read-only filesystems on large transfers with any of both. some additional info that might be relevant: - the filesystems are all on RAID 1 devices, ext4 and use fscrypt - the hardware on the affected machine is pretty dated (ASUS Z97-K mainboard, intel i5-4460 CPU 3.20 GHz, 8GB DDR3 RAM, NVIDIA GeForce GT 610), except for the hard drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.2/+bug/2035204/+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 2031022] Re: Fix boot test warning for log_check "CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0"
Nothing special for azure, and I assume the source package was not built against the previous version, hence the verification is triggered again. ** Tags removed: verification-needed-focal-linux-azure ** Tags added: verification-done-focal-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031022 Title: Fix boot test warning for log_check "CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Bug description: SRU Justification [Impact] Gather Data Sampling, affecting Intel processors and assigned CVE-2022-40982 introduced this warning.The fix is on microcode, but part of the mitigation on the kernel side is to detect if the microcode update is not there and disable AVX in case it's supported. This needed some reshuffle during initialization so that turning off AVX was possible without it being too late, which also moved the FPU initialization. See commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.252=6e60443668978131a442df485db3deccb31d5651 This causes the following warning during boot: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0 Logs: 154609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.438234] [ cut here ] 154709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.439198] get of unsupported state 154809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.439206] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0 154909:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Modules linked in: 155009:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-158-lowlatency #175-Ubuntu 155109:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 155209:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RIP: 0010:get_xsave_addr+0x98/0xb0 155309:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Code: 7e ff ff ff 48 83 c4 08 5b 5d c3 80 3d ed d8 bc 01 00 75 ae 48 c7 c7 52 76 51 9a 89 75 f4 c6 05 da d8 bc 01 01 e8 1a c8 a7 00 <0f> 0b 8b 75 f4 eb 91 31 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 155409:02:40 INFO | Aug 10 09:01:05 akis systemd-udevd[3200]: enp58s0np0: Process '/usr/bin/killall -SIGHUP irqbalance' failed with exit code 1. 155509:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RSP: :9ac03e80 EFLAGS: 00010282 155609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RAX: RBX: 9ae47180 RCX: 00032109e11a 155709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RDX: 0018 RSI: 9bd8c620 RDI: 0246 155809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] RBP: 9ac03e90 R08: 9bd8c620 R09: 74726f707075736e 155909:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] R10: 74726f707075736e R11: 6574617473206465 R12: 9ae47040 156009:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] R13: 0246 R14: 5a1c7469 R15: 5a1d7ee0 156109:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] FS: () GS:a0840040() knlGS: 156209:02:40 INFO | Aug 10 09:01:05 akis systemd[1]: Starting Load Kernel Module pstore_zone... 156309:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CS: 0010 DS: ES: CR0: 80050033 156409:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] CR2: a146f000 CR3: 00802c80a001 CR4: 007200b0 156509:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] DR0: DR1: DR2: 156609:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] DR3: DR6: fffe0ff0 DR7: 0400 156709:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] Call Trace: 156809:02:40 INFO | Aug 10 09:01:05 akis kernel: [ 13.440197] ? show_regs.cold+0x1a/0x1f 156909:02:40 INFO | Aug
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
We might need this:
commit 416c6d01244ecbf0abfdb898fd091b50ef951b48
Author: Alan Maguire
Date: Wed Aug 2 08:39:06 2023 +0100
selftests/bpf: fix static assert compilation issue for test_cls_*.c
commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE")
--
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/2035181
Title:
Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
New
Bug description:
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
2 errors generated.
make[1]: *** [Makefile:470:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.o]
Error 1
make: *** [Makefile:171: all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2035181/+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 2035181] Re: Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
bisect between -83 and -85 suggests that:
17e95e1a51d798696a62769c26a12fb16c9ac881 is the first bad commit
commit 17e95e1a51d798696a62769c26a12fb16c9ac881
Author: Andrii Nakryiko
Date: Mon May 8 23:55:02 2023 -0700
libbpf: fix offsetof() and container_of() to work with CO-RE
BugLink: https://bugs.launchpad.net/bugs/2032689
[ Upstream commit bdeeed3498c7871c17465bb4f11d1bc67f9098af ]
It seems like __builtin_offset() doesn't preserve CO-RE field
relocations properly. So if offsetof() macro is defined through
__builtin_offset(), CO-RE-enabled BPF code using container_of() will be
subtly and silently broken.
To avoid this problem, redefine offsetof() and container_of() in the
form that works with CO-RE relocations more reliably.
Fixes: 5fbc220862fc ("tools/libpf: Add offsetof/container_of macro in
bpf_helpers.h")
Reported-by: Lennart Poettering
Signed-off-by: Andrii Nakryiko
Acked-by: Yonghong Song
Link: https://lore.kernel.org/r/20230509065502.2306180-1-and...@kernel.org
Signed-off-by: Alexei Starovoitov
Signed-off-by: Sasha Levin
Signed-off-by: Kamal Mostafa
Signed-off-by: Stefan Bader
tools/lib/bpf/bpf_helpers.h | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
$ git bisect log
git bisect start
# bad: [bcea2f888a5b1ffaa03951efa43840e10f1bda66] UBUNTU: Ubuntu-5.15.0-85.95
git bisect bad bcea2f888a5b1ffaa03951efa43840e10f1bda66
# good: [294374341c622e5c2ffd15712cadabe0dd9865f1] UBUNTU: Ubuntu-5.15.0-83.92
git bisect good 294374341c622e5c2ffd15712cadabe0dd9865f1
# bad: [c57a826d3343214967f1b09cac263004d6bbc240] arm64: dts: qcom: Drop
unneeded extra device-specific includes
git bisect bad c57a826d3343214967f1b09cac263004d6bbc240
# good: [2ba31156e2f29be421a3d38c49efb071af327810] cgroup: Do not corrupt task
iteration when rebinding subsystem
git bisect good 2ba31156e2f29be421a3d38c49efb071af327810
# good: [1d4a282191f29ae9d50b936902a88829cd8b0169] rcutorture: Correct name of
use_softirq module parameter
git bisect good 1d4a282191f29ae9d50b936902a88829cd8b0169
# bad: [eced7b1344d4d34b2012095f21a8433c326ba80d] bpf: Fix bpf socket lookup
from tc/xdp to respect socket VRF bindings
git bisect bad eced7b1344d4d34b2012095f21a8433c326ba80d
# bad: [9f49a01dcfe9610da203312a25136dd6ec390cc1] regulator: core: Streamline
debugfs operations
git bisect bad 9f49a01dcfe9610da203312a25136dd6ec390cc1
# good: [3e348272984fc81fa850326aa722e5b63520d40b] wifi: ath9k: fix AR9003 mac
hardware hang check register offset calculation
git bisect good 3e348272984fc81fa850326aa722e5b63520d40b
# good: [3f64b9b253e3200c56d725676b110c47b8e2c52d] sctp: add
bpf_bypass_getsockopt proto callback
git bisect good 3f64b9b253e3200c56d725676b110c47b8e2c52d
# bad: [cc12b4a5c0bb03dc94e113e2be6d01d1d57c22cc] spi: dw: Round of n_bytes to
power of 2
git bisect bad cc12b4a5c0bb03dc94e113e2be6d01d1d57c22cc
# bad: [e340c66481d14e4534ef03f543e1188d31c0f617] bpf: Don't EFAULT for
{g,s}setsockopt with wrong optlen
git bisect bad e340c66481d14e4534ef03f543e1188d31c0f617
# bad: [17e95e1a51d798696a62769c26a12fb16c9ac881] libbpf: fix offsetof() and
container_of() to work with CO-RE
git bisect bad 17e95e1a51d798696a62769c26a12fb16c9ac881
# first bad commit: [17e95e1a51d798696a62769c26a12fb16c9ac881] libbpf: fix
offsetof() and container_of() to work with CO-RE
Reverting 17e95e1a51d798696a62769c26a12fb16c9ac881 can make this work
again.
--
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/2035181
Title:
Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
New
Bug description:
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at
[Kernel-packages] [Bug 2035192] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035192 Title: One of 2 screens appears fussy with leftover startup info. Status in linux package in Ubuntu: Confirmed Bug description: On startup the left of my two screens (DP1.2 connected) appears fussy, although not unreadable the font is not distinct. Furthermore, the computer start up logo - in this case "intel nuc" remains in the middle of the left screen. It always seems to be one screen that goes "off focus" and usually the left which is the screen connected to the computer while the other one is daisy chained off it. It only occurs occasionally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-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: KDE Date: Tue Sep 12 09:55:36 2023 DistUpgraded: 2023-05-22 17:44:59,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:3024] InstallationDate: Installed on 2023-02-27 (196 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems NUC12WSHi5 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-22 (112 days ago) dmi.bios.date: 07/18/2022 dmi.bios.release: 5.26 dmi.bios.vendor: Intel Corp. dmi.bios.version: WSADL357.0085.2022.0718.1739 dmi.board.name: NUC12WSBi5 dmi.board.vendor: Intel Corporation dmi.board.version: M46425-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWSADL357.0085.2022.0718.1739:bd07/18/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-302:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-302:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000: dmi.product.family: WS dmi.product.name: NUC12WSHi5 dmi.product.sku: NUC12WSHi5000 dmi.product.version: M46655-302 dmi.sys.vendor: Intel(R) Client Systems 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/2035192/+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 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1117.110)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1117.110) for focal have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) systemd/245.4-4ubuntu3.22 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035192] Re: One of 2 screens appears fussy with leftover startup info.
Also if the leftover startup image is when KDE should be displaying then you should log that as a bug against KDE or Kwin. -- 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/2035192 Title: One of 2 screens appears fussy with leftover startup info. Status in linux package in Ubuntu: New Bug description: On startup the left of my two screens (DP1.2 connected) appears fussy, although not unreadable the font is not distinct. Furthermore, the computer start up logo - in this case "intel nuc" remains in the middle of the left screen. It always seems to be one screen that goes "off focus" and usually the left which is the screen connected to the computer while the other one is daisy chained off it. It only occurs occasionally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-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: KDE Date: Tue Sep 12 09:55:36 2023 DistUpgraded: 2023-05-22 17:44:59,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:3024] InstallationDate: Installed on 2023-02-27 (196 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems NUC12WSHi5 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-22 (112 days ago) dmi.bios.date: 07/18/2022 dmi.bios.release: 5.26 dmi.bios.vendor: Intel Corp. dmi.bios.version: WSADL357.0085.2022.0718.1739 dmi.board.name: NUC12WSBi5 dmi.board.vendor: Intel Corporation dmi.board.version: M46425-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWSADL357.0085.2022.0718.1739:bd07/18/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-302:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-302:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000: dmi.product.family: WS dmi.product.name: NUC12WSHi5 dmi.product.sku: NUC12WSHi5000 dmi.product.version: M46655-302 dmi.sys.vendor: Intel(R) Client Systems 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/2035192/+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 2035192] Re: One of 2 screens appears fussy with leftover startup info.
This sounds like a consequence of a common problem with Intel graphics -- the kernel occasionally misdetects the screen resolution. It's not a big deal if only the startup animations are affected but let us know if you have similar problems on the desktop (such as when resuming from sleep). ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- 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/2035192 Title: One of 2 screens appears fussy with leftover startup info. Status in linux package in Ubuntu: New Bug description: On startup the left of my two screens (DP1.2 connected) appears fussy, although not unreadable the font is not distinct. Furthermore, the computer start up logo - in this case "intel nuc" remains in the middle of the left screen. It always seems to be one screen that goes "off focus" and usually the left which is the screen connected to the computer while the other one is daisy chained off it. It only occurs occasionally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-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: KDE Date: Tue Sep 12 09:55:36 2023 DistUpgraded: 2023-05-22 17:44:59,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:3024] InstallationDate: Installed on 2023-02-27 (196 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems NUC12WSHi5 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-22 (112 days ago) dmi.bios.date: 07/18/2022 dmi.bios.release: 5.26 dmi.bios.vendor: Intel Corp. dmi.bios.version: WSADL357.0085.2022.0718.1739 dmi.board.name: NUC12WSBi5 dmi.board.vendor: Intel Corporation dmi.board.version: M46425-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWSADL357.0085.2022.0718.1739:bd07/18/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-302:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-302:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000: dmi.product.family: WS dmi.product.name: NUC12WSHi5 dmi.product.sku: NUC12WSHi5000 dmi.product.version: M46655-302 dmi.sys.vendor: Intel(R) Client Systems 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/2035192/+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 2035192] [NEW] One of 2 screens appears fussy with leftover startup info.
You have been subscribed to a public bug: On startup the left of my two screens (DP1.2 connected) appears fussy, although not unreadable the font is not distinct. Furthermore, the computer start up logo - in this case "intel nuc" remains in the middle of the left screen. It always seems to be one screen that goes "off focus" and usually the left which is the screen connected to the computer while the other one is daisy chained off it. It only occurs occasionally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-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: KDE Date: Tue Sep 12 09:55:36 2023 DistUpgraded: 2023-05-22 17:44:59,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:3024] InstallationDate: Installed on 2023-02-27 (196 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Intel(R) Client Systems NUC12WSHi5 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-22 (112 days ago) dmi.bios.date: 07/18/2022 dmi.bios.release: 5.26 dmi.bios.vendor: Intel Corp. dmi.bios.version: WSADL357.0085.2022.0718.1739 dmi.board.name: NUC12WSBi5 dmi.board.vendor: Intel Corporation dmi.board.version: M46425-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWSADL357.0085.2022.0718.1739:bd07/18/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-302:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-302:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000: dmi.product.family: WS dmi.product.name: NUC12WSHi5 dmi.product.sku: NUC12WSHi5000 dmi.product.version: M46655-302 dmi.sys.vendor: Intel(R) Client Systems 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 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug kubuntu lunar performance ubuntu -- One of 2 screens appears fussy with leftover startup info. https://bugs.launchpad.net/bugs/2035192 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/6.2.0.1013.13)
All autopkgtests for the newly accepted linux-meta-azure (6.2.0.1013.13) for lunar have finished running. The following regressions have been reported in tests triggered by the package: rapiddisk/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure/6.2.0-1013.13)
All autopkgtests for the newly accepted linux-restricted-modules-azure (6.2.0-1013.13) for lunar have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525-server/525.125.06-0ubuntu0.23.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/6.2.0-1013.13)
All autopkgtests for the newly accepted linux-restricted-modules-azure (6.2.0-1013.13) for lunar have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525-server/525.125.06-0ubuntu0.23.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2019299] Autopkgtest regression report (linux-restricted-modules-azure/6.2.0-1013.13)
All autopkgtests for the newly accepted linux-restricted-modules-azure (6.2.0-1013.13) for lunar have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525-server/525.125.06-0ubuntu0.23.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2019299 Title: standardise ancillary naming to simplify backporting Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: In Progress Bug description: There is no requirement for the directories in debian/ancillary to match the naming of the contained packages. Simplify maintenance by pivoting to using the name of these package in the main kernel in all cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2019299/+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 2035189] [NEW] Remove from the archive, unmaintained upstream
Public bug reported: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. WIP: Need to remove the driver from the system so that the kernel default (nouveau) is used instead, by modifying ubuntu-drivers? ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: Remove from the archive, unmaintained upstream Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. WIP: Need to remove the driver from the system so that the kernel default (nouveau) is used instead, by modifying ubuntu-drivers? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/+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 2033159] Re: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic
Reinstalled kernel 6.2.0-26-generic, it started working again while the kernel 6.2.0-32-generic, not working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033159 Title: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy linux-image-6.2.0-26-generic linux-image-6.2.0-26-generic: Installed: 6.2.0-26.26~22.04.1 Candidate: 6.2.0-26.26~22.04.1 Table version: *** 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status $ lspci 02:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) $ lshw -c network *-network NOT CLAIMED description: Network controller product: Wireless-AC 9260 vendor: Intel Corporation $ uname -a Linux Linux 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux works only with desktop GNOME. No work desktop LXQt ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Aug 26 17:00:59 2023 InstallationDate: Installed on 2022-05-28 (454 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) 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/ubuntu/+source/linux-hwe-6.2/+bug/2033159/+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 2033159] Re: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic
:~$ apt-cache policy linux-hwe-6.2 kernel-testing--linux-hwe-6.2--full--generic: Installed: (none) Candidate: (none) Version table: linux-hwe-6.2-source-6.2.0: Installed: (none) Candidate: (none) Version table: linux-hwe-6.2-tools-host: Installed: (none) Candidate: 6.2.0-32.32~22.04.1 Version table: 6.2.0-32.32~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-31.31~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-25.25~22.04.2 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages kernel-testing--linux-hwe-6.2--full--preferred: Installed: (none) Candidate: (none) Version table: linux-hwe-6.2-headers-6.2.0-25: Installed: (none) Candidate: 6.2.0-25.25~22.04.2 Version table: 6.2.0-25.25~22.04.2 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-headers-6.2.0-26: Installed: (none) Candidate: 6.2.0-26.26~22.04.1 Version table: 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-headers-6.2.0-31: Installed: (none) Candidate: 6.2.0-31.31~22.04.1 Version table: 6.2.0-31.31~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-headers-6.2.0-32: Installed: (none) Candidate: 6.2.0-32.32~22.04.1 Version table: 6.2.0-32.32~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-tools-common: Installed: (none) Candidate: 6.2.0-32.32~22.04.1 Version table: 6.2.0-32.32~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-31.31~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-25.25~22.04.2 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-cloud-tools-common: Installed: (none) Candidate: 6.2.0-32.32~22.04.1 Version table: 6.2.0-32.32~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-31.31~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 6.2.0-25.25~22.04.2 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-tools: Installed: (none) Candidate: (none) Version table: kernel-testing--linux-hwe-6.2--modules-extra--virtual: Installed: (none) Candidate: (none) Version table: linux-hwe-6.2-cloud-tools-6.2.0-25: Installed: (none) Candidate: 6.2.0-25.25~22.04.2 Version table: 6.2.0-25.25~22.04.2 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-cloud-tools-6.2.0-26: Installed: (none) Candidate: 6.2.0-26.26~22.04.1 Version table: 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages linux-hwe-6.2-cloud-tools-6.2.0-31: Installed: (none) Candidate:
[Kernel-packages] [Bug 2033531] Re: Azure: net: mana: Fix MANA VF unload when hardware is unresponsive
This bug is awaiting verification that the linux-azure/5.15.0-1048.55
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-azure-v2
verification-needed-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2033531
Title:
Azure: net: mana: Fix MANA VF unload when hardware is unresponsive
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-azure source package in Lunar:
Fix Committed
Bug description:
SRU Justification
[Impact]
MSFT has requested to backport commit
a7dfeda6fdeccab4c7c3dce9a72c4262b9530c80 ('net: mana: Fix MANA VF
unload when hardware is unresponsive').
When unloading the MANA driver, mana_dealloc_queues() waits for the MANA
hardware to complete any inflight packets and set the pending send count
to zero. But if the hardware has failed, mana_dealloc_queues()
could wait forever.
[Test Plan]
Microsoft tested. Commit upstream since 6.5
[Regression Potential]
The MANA driver may not shut down correctly.
[Other Info]
SF: #00367140
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2033531/+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 2034747] Re: Azure: Fix Infiniband identifier order
This bug is awaiting verification that the linux-azure/5.15.0-1048.55
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-azure-v2
verification-needed-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2034747
Title:
Azure: Fix Infiniband identifier order
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Bug description:
SRU Justification
[Impact]
Commit ad95515bf1d391326b362d8b0c1e6e3bd74046b6 ('RDMA/mana_ib: Add a
driver for Microsoft Azure Network Adapter') is part of the MANA
Infiniband backport. However, a commit was missed that updated the
'enum rdma_driver_id' list of identifiers. Since these are order and
value specific user space applications are not able to correctly
identify the MANA RDMA driver.
[Test Plan]
MSFT tested.
[Regression Potential]
Existing applications don't work with MANA RDMA anyway, so there is no
regression potential.
[Other Info]
SF: #00368017
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034747/+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 2034277] Re: Azure: net: mana: Add page pool for RX buffers
This bug is awaiting verification that the linux-azure/5.15.0-1048.55 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+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 2033159] Re: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic
** No longer affects: linux-signed-hwe-6.2 (Ubuntu) ** Changed in: linux-hwe-6.2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033159 Title: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy linux-image-6.2.0-26-generic linux-image-6.2.0-26-generic: Installed: 6.2.0-26.26~22.04.1 Candidate: 6.2.0-26.26~22.04.1 Table version: *** 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status $ lspci 02:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) $ lshw -c network *-network NOT CLAIMED description: Network controller product: Wireless-AC 9260 vendor: Intel Corporation $ uname -a Linux Linux 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux works only with desktop GNOME. No work desktop LXQt ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Aug 26 17:00:59 2023 InstallationDate: Installed on 2022-05-28 (454 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) 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/ubuntu/+source/linux-hwe-6.2/+bug/2033159/+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 2035181] Re: Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035181 Title: Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: New Bug description: Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04 This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84 is a security cycle, in which the ubuntu_bpf test was not triggered there) Test build failed with: CLNG-BPF [test_maps] test_btf_map_in_map.o CLNG-BPF [test_maps] test_btf_newkv.o CLNG-BPF [test_maps] test_btf_nokv.o CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o CLNG-BPF [test_maps] test_cgroup_link.o CLNG-BPF [test_maps] test_check_mtu.o CLNG-BPF [test_maps] test_cls_redirect.o make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' progs/test_cls_redirect.c:90:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv4.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note: expanded from macro 'offsetof' #define offsetof(type, member) ((unsigned long)&((type *)0)->member) ^ progs/test_cls_redirect.c:95:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv6.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note: expanded from macro 'offsetof' #define offsetof(type, member) ((unsigned long)&((type *)0)->member) ^ 2 errors generated. make[1]: *** [Makefile:470: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.o] Error 1 make: *** [Makefile:171: all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2035181/+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 2033159] Re: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic
no network with kernel 6.2.0-32-generic $ apt-cache policy linux-signed-hwe-6.2 N: Unable to find package linux-signed-hwe-6.2 N: Could not find any packages via glob "linux-signed-hwe-6.2" N: Could not find any package via regular expression "linux-signed-hwe-6.2" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033159 Title: Intel AC 9260 no wifi networks with kernel 6.2.0-26-generic Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy linux-image-6.2.0-26-generic linux-image-6.2.0-26-generic: Installed: 6.2.0-26.26~22.04.1 Candidate: 6.2.0-26.26~22.04.1 Table version: *** 6.2.0-26.26~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status $ lspci 02:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) $ lshw -c network *-network NOT CLAIMED description: Network controller product: Wireless-AC 9260 vendor: Intel Corporation $ uname -a Linux Linux 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux works only with desktop GNOME. No work desktop LXQt ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Aug 26 17:00:59 2023 InstallationDate: Installed on 2022-05-28 (454 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) 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/ubuntu/+source/linux-hwe-6.2/+bug/2033159/+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 2035182] [NEW] Touchpad events recognized, but mousepointer does not move
Public bug reported: I did the debuggin like on the website: https://wiki.ubuntu.com/DebuggingTouchpadDetection I attached the file. 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: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 09:22:46 2023 InstallationDate: Installed on 2020-12-21 (994 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-06-01 (468 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "evteest" https://bugs.launchpad.net/bugs/2035182/+attachment/5700191/+files/evtest -- 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/2035182 Title: Touchpad events recognized, but mousepointer does not move Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I did the debuggin like on the website: https://wiki.ubuntu.com/DebuggingTouchpadDetection I attached the file. 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: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 09:22:46 2023 InstallationDate: Installed on 2020-12-21 (994 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-06-01 (468 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2035182/+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 2032173] Re: Ubuntu 22.04.3 LTS: Kernel 5.15.0-79-generic fails to boot
Has been resolved with 5.15.0-83-generic -- 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/2032173 Title: Ubuntu 22.04.3 LTS: Kernel 5.15.0-79-generic fails to boot Status in linux package in Ubuntu: Confirmed Bug description: After installing the new 5.15.0-79 kernel image, my ThinkPad L490 fails to start. A normal boot just gives me a blank screen, when I boot in recovery mode it hangs at: "EFI stub: UEFI Secure boot is enabled". Editing the kernel entry in grub as suggested here https://wiki.ubuntu.com/DebuggingKernelBoot does not yield any more info. Starting with 5.15.0-78 works without issues. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-78-generic 5.15.0-78.85 ProcVersionSignature: Ubuntu 5.15.0-78.85-generic 5.15.99 Uname: Linux 5.15.0-78-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: csteuer1874 F pulseaudio /dev/snd/controlC0: csteuer1874 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Aug 21 09:39:05 2023 InstallationDate: Installed on 2020-12-18 (975 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20Q5002DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-78-generic root=/dev/mapper/vgxubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-78-generic N/A linux-backports-modules-5.15.0-78-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.17 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-25 (361 days ago) dmi.bios.date: 02/17/2020 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET39W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q5002DGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.14 dmi.modalias: dmi:bvnLENOVO:bvrR0ZET39W(1.17):bd02/17/2020:br1.17:efr1.14:svnLENOVO:pn20Q5002DGE:pvrThinkPadL490:rvnLENOVO:rn20Q5002DGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q5_BU_SMB_FM_ThinkPadL490: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q5002DGE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032173/+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 2035163] Re: Avoid address overwrite in kernel_connect
** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gke (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-gke (Ubuntu Mantic) Status: New => Invalid -- 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: Invalid Status in linux-gcp source package in Focal: New Status in linux-gke source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gke source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gke source package in Lunar: Invalid Status in linux-gcp source package in Mantic: New Status in linux-gke source package in Mantic: Invalid Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
** Changed in: linux (Ubuntu) Status: Invalid => In Progress -- 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indicated by the following commit. d25ceb926436 KVM: x86/mmu: Track the number of TDP MMU pages, but not the actual pages While this patch doesn't modify the triggering logic, it replaces the problematic section with a more reliable approach while keeping the original logic unchanged. If the issue persists, it should not result in any memory access problems. We also requested the customer to set up a test environment and simulate a workload similar to the production environment. The patch worked well and did not introduce any adverse effects. [Test Plan] Reproducing the issue has proven to be challenging. Simulating heavy live
[Kernel-packages] [Bug 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Medium => High -- 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indicated by the following commit. d25ceb926436 KVM: x86/mmu: Track the number of TDP MMU pages, but not the actual pages While this patch doesn't modify the triggering logic, it replaces the problematic section with a more reliable approach while keeping the original logic unchanged. If the issue persists, it should not result in any memory access problems. We also requested the customer to set up a test environment and simulate a workload similar to the production environment. The patch worked well
[Kernel-packages] [Bug 2031057] Re: [EHL] Screen flickering when the setup is in multiple monitors with mirror mode output
customer verified 5.15.0-1039.45 kernel in -proposed and solved their issue. ** Tags removed: verification-needed-jammy-linux-intel-iotg ** Tags added: verification-done-jammy-linux-intel-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2031057 Title: [EHL] Screen flickering when the setup is in multiple monitors with mirror mode output Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Summary] Display is flickering in Mirror mode and below 30 Hz refresh rate [Steps to reproduce] 1. Install Ubuntu Desktop 22.04.2 2. Boot to desktop 3. Connect 2 FHD monitors to DP ports and HDMI port 4. Change to Mirror Mode. 5. Change back to Joint Mode and change refresh rate to 30 Hz (or below) [Expected result] 1. Display on both DP and HDMI show correctly on Mirror mode 2. Display on both DP and HDMI show correctly on refresh rate below 30Hz [Actual result] 1. Display Flicker on display in Mirror Mode. 2. Display Flicker on display when select 30 Hz on refresh rate [Failure rate] 100% [Additional information] bios-version: V1.11 CPU: Intel(R) Celeron(R) N6210 @ 1.20GHz (Elkhart Lake) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 4555 (rev 01) kernel-version: 5.15.0-1027-intel-iotg Note: Single mode does not have this issue. LP: #2020412 LP: #2031056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2031057/+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 2035166] 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 2035166 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: In Progress Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indicated by the following commit. d25ceb926436 KVM: x86/mmu: Track the number of TDP MMU pages, but not the actual
[Kernel-packages] [Bug 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: In Progress Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indicated by the following commit. d25ceb926436 KVM: x86/mmu: Track the number of TDP MMU pages, but not the actual pages While this patch doesn't modify the triggering logic, it replaces the problematic section with a more reliable approach while keeping the original logic unchanged. If the issue persists, it should not result in any memory access problems. We also requested the customer to set up a test environment and simulate a workload similar to the production environment. The patch worked well and did not introduce any adverse effects. [Test Plan]
[Kernel-packages] [Bug 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
Please provide logs from when the problem occurs: apport-collect 2034916 ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034916 Title: NIC RTL8168 randomly disconnected from pci bus Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2034916/+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
