[Kernel-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Actually the issue I'm thinking of might be fixed by https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2620 coming in mutter 46... If not already fixed in the kernel because it looks like this bug only affects jammy? -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2047780] Re: BlueZ release 5.71
The build is failing: https://launchpad.net/ubuntu/+source/bluez/5.71-0ubuntu1 But I don't know how to reproduce the failure. Certainly it builds on both noble and mantic, and installs, and works for me. Is this because Launchpad is using a focal toolchain? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2046224] Re: [amdgpu] Resolutions lower than max results in corrupted screen
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2693
https://gitlab.freedesktop.org/drm/amd/-/issues/2693
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2693
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Tags added: fixed-upstream regression-release
--
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/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-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/linux/+bug/2046224/+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 2047398] Re: Add missing RPL P/U CPU IDs
** Tags added: originate-from-2047480 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs 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 Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2042867] Re: Changing display resolution leads into black screen
SRU in bug 2046504
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042867
Title:
Changing display resolution leads into black screen
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Since updating into 23.10, when I change my build-in display from
2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen
black and unable to use.
The only resolution that works is the predefined one.
This bug wasn't present on the previous release, 23.04.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 6 19:37:48 2023
InstallationDate: Installed on 2023-05-05 (185 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
dmi.bios.date: 04/18/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UM5401QAB_UM5401QA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UM5401QAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UM5401QAB_UM5401QA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042867/+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 2046504] Re: Fix AMDGPU display on lower resolution modes
Sorry I didn't find bug 2042867 This bug is SRU for oem kernel. If set duplicated, its status can't be changed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Thinking about the most common cause of this error I've seen, can anyone with multiple monitors confirm that it happens more on monitors that the mouse pointer isn't on? -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2045992] Re: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot
kernel log ** Attachment added: "kernel log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045992/+attachment/5736178/+files/kern.log -- 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/2045992 Title: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot Status in linux package in Ubuntu: Confirmed Bug description: Apologies if what this post will entail is not the correct way to report a bug. This is my first time reporting one for a linux distro, and I'm more or less doing so based on information I was told while investigating a separate issue related to my audio devices. On boot, along with the error I was looking for, I noticed a number of UBSan errors pop up. I asked about them in a linux-related discord server and their first question was whether the kernel was compiled with Clang. Now, because I never mess with the kernel, I told them I wasn't sure. That was when they told me that it's a kernel bug that invoked undefined behavior and left my kernel in an erroneous state. Here are the errors in question: [ 5.036942] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4 [ 5.036951] index 2 is out of range for type 'ATOM_Tonga_MCLK_Dependency_Record [1]' [ 5.041843] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 [ 5.041852] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Because I'm not 100% sure what all goes into a bug report like this, I will be providing the output of lsb_release -rd, hyfetch, and creating a list of my system's specs in hopes that it will help provide some sort of clarity. lsb_release -rd Output: --- No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 Hyfetch Output: --- OS: Kubuntu 23.10 x86_64 Kernel: 6.5.0-14-generic Uptime: 28 mins Packages: 3 (pipx), 4178 (dpkg), 43 (flatpak), 24 (snap) Shell: fish 3.6.1 (yes I know it's deprecated but I prefer it over other shells) Resolution: 1920x1080, 1920x1080 DE: Plasma 5.27.8 [KF5 5.110.0] [Qt 5.15.10] (x11) WM: KWin System Specs: - CPU: AMD Ryzen 5 2600x GPU: Sapphire NITRO+ Radeon RX 570 MOBO: ASUS PRIME B450M-A II RAM: TEAMGROUP TUFF Gaming 2x8 GB at 2400 MHz PSU: Corsair RM850x (850W PSU) SSD: Western Digital Blue 1 TB SSD I'll be honest and say I'm not even sure if my system specs are required for a bug report like this, but just in case I figured I'd provide them anyway, as maybe it's a hardware-specific thing, or something specific to my system entirely. I'm not sure though. I also went ahead and included an attachment of the photo I took of the error itself, maybe it'll help in some way. I'm also unsure if there's a package related to this bug, or what that package would be. Sorry. As for the last two things stated in the guidelines for reporting a bug, what I expected to happen was to see the error about my USB device along with some of the general jargon that pops up on boot that I typically don't have to worry about. Instead what happened is that based on what someone else told me, I found a bug in my kernel, although I'm not knowledgeable enough to know if it's a serious bug, or something that's really not that big of a deal. I'll leave that one up to you guys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045992/+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 2045992] Re: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot
Lubuntu 22.04 with hwe linux-generic-hwe-22.04 (6.5.0.14.14~22.04.7) this is not affected with 6.2.0.39.40~22.04.16 hardware GA 970A-DS3P (bios version FD) video Baffin [Radeon RX 550 640SP / RX 560/560X] Mesa 23.2.1-1ubuntu3.1~22.04.1 ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045992/+attachment/5736177/+files/dmesg.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/2045992 Title: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot Status in linux package in Ubuntu: Confirmed Bug description: Apologies if what this post will entail is not the correct way to report a bug. This is my first time reporting one for a linux distro, and I'm more or less doing so based on information I was told while investigating a separate issue related to my audio devices. On boot, along with the error I was looking for, I noticed a number of UBSan errors pop up. I asked about them in a linux-related discord server and their first question was whether the kernel was compiled with Clang. Now, because I never mess with the kernel, I told them I wasn't sure. That was when they told me that it's a kernel bug that invoked undefined behavior and left my kernel in an erroneous state. Here are the errors in question: [ 5.036942] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4 [ 5.036951] index 2 is out of range for type 'ATOM_Tonga_MCLK_Dependency_Record [1]' [ 5.041843] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 [ 5.041852] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Because I'm not 100% sure what all goes into a bug report like this, I will be providing the output of lsb_release -rd, hyfetch, and creating a list of my system's specs in hopes that it will help provide some sort of clarity. lsb_release -rd Output: --- No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 Hyfetch Output: --- OS: Kubuntu 23.10 x86_64 Kernel: 6.5.0-14-generic Uptime: 28 mins Packages: 3 (pipx), 4178 (dpkg), 43 (flatpak), 24 (snap) Shell: fish 3.6.1 (yes I know it's deprecated but I prefer it over other shells) Resolution: 1920x1080, 1920x1080 DE: Plasma 5.27.8 [KF5 5.110.0] [Qt 5.15.10] (x11) WM: KWin System Specs: - CPU: AMD Ryzen 5 2600x GPU: Sapphire NITRO+ Radeon RX 570 MOBO: ASUS PRIME B450M-A II RAM: TEAMGROUP TUFF Gaming 2x8 GB at 2400 MHz PSU: Corsair RM850x (850W PSU) SSD: Western Digital Blue 1 TB SSD I'll be honest and say I'm not even sure if my system specs are required for a bug report like this, but just in case I figured I'd provide them anyway, as maybe it's a hardware-specific thing, or something specific to my system entirely. I'm not sure though. I also went ahead and included an attachment of the photo I took of the error itself, maybe it'll help in some way. I'm also unsure if there's a package related to this bug, or what that package would be. Sorry. As for the last two things stated in the guidelines for reporting a bug, what I expected to happen was to see the error about my USB device along with some of the general jargon that pops up on boot that I typically don't have to worry about. Instead what happened is that based on what someone else told me, I found a bug in my kernel, although I'm not knowledgeable enough to know if it's a serious bug, or something that's really not that big of a deal. I'll leave that one up to you guys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045992/+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 2045992] Re: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2045992 Title: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot Status in linux package in Ubuntu: Confirmed Bug description: Apologies if what this post will entail is not the correct way to report a bug. This is my first time reporting one for a linux distro, and I'm more or less doing so based on information I was told while investigating a separate issue related to my audio devices. On boot, along with the error I was looking for, I noticed a number of UBSan errors pop up. I asked about them in a linux-related discord server and their first question was whether the kernel was compiled with Clang. Now, because I never mess with the kernel, I told them I wasn't sure. That was when they told me that it's a kernel bug that invoked undefined behavior and left my kernel in an erroneous state. Here are the errors in question: [ 5.036942] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4 [ 5.036951] index 2 is out of range for type 'ATOM_Tonga_MCLK_Dependency_Record [1]' [ 5.041843] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 [ 5.041852] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Because I'm not 100% sure what all goes into a bug report like this, I will be providing the output of lsb_release -rd, hyfetch, and creating a list of my system's specs in hopes that it will help provide some sort of clarity. lsb_release -rd Output: --- No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 Hyfetch Output: --- OS: Kubuntu 23.10 x86_64 Kernel: 6.5.0-14-generic Uptime: 28 mins Packages: 3 (pipx), 4178 (dpkg), 43 (flatpak), 24 (snap) Shell: fish 3.6.1 (yes I know it's deprecated but I prefer it over other shells) Resolution: 1920x1080, 1920x1080 DE: Plasma 5.27.8 [KF5 5.110.0] [Qt 5.15.10] (x11) WM: KWin System Specs: - CPU: AMD Ryzen 5 2600x GPU: Sapphire NITRO+ Radeon RX 570 MOBO: ASUS PRIME B450M-A II RAM: TEAMGROUP TUFF Gaming 2x8 GB at 2400 MHz PSU: Corsair RM850x (850W PSU) SSD: Western Digital Blue 1 TB SSD I'll be honest and say I'm not even sure if my system specs are required for a bug report like this, but just in case I figured I'd provide them anyway, as maybe it's a hardware-specific thing, or something specific to my system entirely. I'm not sure though. I also went ahead and included an attachment of the photo I took of the error itself, maybe it'll help in some way. I'm also unsure if there's a package related to this bug, or what that package would be. Sorry. As for the last two things stated in the guidelines for reporting a bug, what I expected to happen was to see the error about my USB device along with some of the general jargon that pops up on boot that I typically don't have to worry about. Instead what happened is that based on what someone else told me, I found a bug in my kernel, although I'm not knowledgeable enough to know if it's a serious bug, or something that's really not that big of a deal. I'll leave that one up to you guys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045992/+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 2046504] Re: Fix AMDGPU display on lower resolution modes
Is there a reason why this hasn't been marked as a duplicate of bug 2042867? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 2046224] Re: [amdgpu] Resolutions lower than max results in corrupted screen
** No longer affects: xorg-server (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/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status in linux package in Ubuntu:
New
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-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/2046224/+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 2046504] Re: Fix AMDGPU display on lower resolution modes
It's already in mantic and 6.6: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/commit/?h=master- next=e21d1a38e83ce7f7f8d99c857b941b59c2ddc22f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 2046224] Re: [amdgpu] Resolutions lower than max results in corrupted screen
This issue should be fixed by commit [1],
it had been merged by mantic 6.5 kernel, and will be released in next update.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2de19022c5d7ff519dd5b9690f7713267bd1abfe
--
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/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status in linux package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-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/2046224/+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 2047780] Re: BlueZ release 5.71
> 34174 lines in this case is not plausibly reviewable. I typically use filterdiff to get the packaging changes, and review specific source files as necessary (including copyright changes in the diff, which can be important, even if you're just using a script for it). Thanks for your help here. I apologize for any undue stress. I will review this in the morning, unless someone else would like the opportunity to fix this sooner. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
It's usually Seb sponsoring these, but he's on vacation. To avoid any future complaints in case he's away again I will also include debdiffs in future. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Here's the debdiff. We don't usually use them for major updates though because of the size. 34174 lines in this case is not plausibly reviewable. ** Patch added: "bluez_5.71-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5736020/+files/bluez_5.71-0ubuntu1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2044554] Re: Turn off non-zynqmp arch support
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2047780] Re: BlueZ release 5.71
I very much dislike reviewing packages this way. For a package to be in the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz. I understand that it's a new upstream release, but that does not excuse the need for a debdiff, even if you *also* include these files. I'm uploading this as a courtesy to you and the Desktop Team. Please, don't do it like this again, as I will reject it. ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters
** Description changed: [IMPACT] This is requested by one of our larger server hardware partners and Broadcom to to update the bnxt_en network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic. The goal is to have these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN a19b4801457b bnxt_en: Event handler for Thermal event 3d9cf962067b bnxt_en: Use non-standard attribute to expose shutdown temperature cd13244f19eb bnxt_en: Expose threshold temperatures through hwmon 847da8b1178c bnxt_en: Modify the driver to use hwmon_device_register_with_info (*)a47f3b3992aa bnxt_en: Move hwmon functions into a dedicated file
[Kernel-packages] [Bug 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
** Description changed: [IMPACT] - This is requested by one of our larger server hardware partners and the - upstream (Broadcom) to update the bnxt network driver code to add some - bug fixes and support for the newer 5760X adapters into Mantic with the - goal of having these land in 22.04.4 HWE and the installer environment - via the HWE kernel. + This is requested by one of our larger server hardware partners and + Broadcom to to update the bnxt_en network driver code to add some bug + fixes and support for the newer 5760X adapters into Mantic. The goal is + to have these land in 22.04.4 HWE and the installer environment via the + HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN a19b4801457b bnxt_en: Event handler for Thermal
[Kernel-packages] [Bug 2045512] Re: UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.c:4062:31
*** This bug is a duplicate of bug 2037082 *** https://bugs.launchpad.net/bugs/2037082 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2045512 Title: UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.c:4062:31 Status in linux package in Ubuntu: Confirmed Bug description: [ 143.525500] [ 143.525913] UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.c:4062:31 [ 143.526327] index 1 is out of range for type 'SUPGIPCPU [1]' [ 143.526760] CPU: 0 PID: 1583 Comm: iprt-VBoxTscThr Tainted: G OE 6.5.0-13-generic #13-Ubuntu [ 143.526760] Hardware name: HP Victus by HP Laptop 16-e0xxx/88EB, BIOS F.15 08/10/2022 [ 143.526760] Call Trace: [ 143.526760] [ 143.526760] dump_stack_lvl+0x48/0x70 [ 143.526760] dump_stack+0x10/0x20 [ 143.526760] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 143.526764] supdrvTscMeasureDeltaOne+0x66f/0x7e0 [vboxdrv] [ 143.526797] supdrvTscDeltaThread+0x4c1/0x7c0 [vboxdrv] [ 143.526828] ? srso_alias_return_thunk+0x5/0x7f [ 143.526832] ? __pfx_rtThreadNativeMain+0x10/0x10 [vboxdrv] [ 143.526863] rtThreadMain+0x37/0x80 [vboxdrv] [ 143.526895] rtThreadNativeMain+0x1b/0x30 [vboxdrv] [ 143.526926] kthread+0xf2/0x120 [ 143.526929] ? __pfx_kthread+0x10/0x10 [ 143.526933] ret_from_fork+0x47/0x70 [ 143.526936] ? __pfx_kthread+0x10/0x10 [ 143.526939] ret_from_fork_asm+0x1b/0x30 [ 143.526943] [ 143.526945] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045512/+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 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
PR made for 6.5. 6.7 will have to wait until the Noble tree is merged with 6.7 mainline. -- 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/2045796 Title: Update bnxt with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Confirmed Bug description: [IMPACT] This is requested by one of our larger server hardware partners and the upstream (Broadcom) to update the bnxt network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic with the goal of having these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN"
[Kernel-packages] [Bug 1199253] Re: linux-ppc: 3.8.0-13.19 -proposed tracker
The platform is dedicated to protecting the security of its users by utilising cutting-edge technologies for optimisation. https://fun88chinhthuc.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ppc in Ubuntu. https://bugs.launchpad.net/bugs/1199253 Title: linux-ppc: 3.8.0-13.19 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-ppc package in Ubuntu: Invalid Status in linux-ppc source package in Raring: Fix Released Bug description: This bug is for tracking the 3.8.0-13.19 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 09. July 2013 08:02 UTC kernel-stable-master-bug:1199128 kernel-stable-Certification-testing-end:Wednesday, 10. July 2013 08:45 UTC kernel-stable-Security-signoff-end:Wednesday, 10. July 2013 08:45 UTC kernel-stable-Prepare-package-end:Wednesday, 10. July 2013 15:34 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 10. July 2013 15:34 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 10. July 2013 16:01 UTC kernel-stable-Verification-testing-start:Wednesday, 10. July 2013 17:01 UTC kernel-stable-Verification-testing-end:Wednesday, 10. July 2013 17:02 UTC kernel-stable-Regression-testing-start:Wednesday, 10. July 2013 17:02 UTC kernel-stable-Promote-to-updates-start:Friday, 26. July 2013 02:01 UTC kernel-stable-Regression-testing-end:Friday, 26. July 2013 02:01 UTC kernel-stable-Promote-to-updates-end:Monday, 29. July 2013 12:02 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Monday, 29. July 2013 14:12 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1199253/+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 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
** Description changed: [IMPACT] This is requested by one of our larger server hardware partners and the upstream (Broadcom) to update the bnxt network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic with the goal of having these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] - These are all in mainline and pick cleanly with the exception of the two - noted at the end of this section. + These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and + pick cleanly with the exception of the two noted at the end of this + section. For Mantic all are picked. For Noble, only the subset + currently in linux-next will be picked, depending on what happens in our + Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN a19b4801457b bnxt_en: Event handler for Thermal event 3d9cf962067b bnxt_en: Use non-standard attribute to expose shutdown temperature cd13244f19eb bnxt_en: Expose threshold temperatures through hwmon 847da8b1178c bnxt_en: Modify the
[Kernel-packages] [Bug 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
** Description changed: - These patches are needed on top of v6.7 to support Broadcom 5760X - Adapters. These patches currently reside in the net-next tree and will - be included in v6.8. + [IMPACT] - Prerequisite commits in net-next today: + This is requested by one of our larger server hardware partners and the + upstream (Broadcom) to update the bnxt network driver code to add some + bug fixes and support for the newer 5760X adapters into Mantic with the + goal of having these land in 22.04.4 HWE and the installer environment + via the HWE kernel. + Missing these patches will mean customers running this hardware will not + be able to use it with Ubuntu Server 22.04 LTS until the much later + 22.04.5 point release, setting up a months-long gap in support for these + adapters. + + [FIXES] + + These are all in mainline and pick cleanly with the exception of the two + noted at the end of this section. + + d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc + 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs + 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new + firmware interface + 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields + 30c0bb63c2ea bnxt_en: Support new firmware link parameters + cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic + a7445d69809f bnxt_en: Add support for new RX and TPA_START completion + types for P7 + 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). + c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. + 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions + 8243345bfaec bnxt_en: Refactor RSS capability fields + d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism + on P7 chips + d3c16475dc06 bnxt_en: Consolidate DB offset calculation + a432a45bdba4 bnxt_en: Define basic P7 macros + 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 + 08b386b132c6 bnxt_en: Fix backing store V2 logic + 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips + f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips + c09d22674b94 bnxt_en: Modify RX ring indexing logic. + 6d1add95536b bnxt_en: Modify TX ring indexing logic. + b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. + 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 + firmware calls + 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API + b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function + 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct + 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type + 76087d997a84 bnxt_en: Restructure context memory data structures + e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() + aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always + free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings - f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings + f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings + required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field + 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters + 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes + 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API + 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic + 94c89e73d377 bnxt_en: refactor speed independent ethtool modes + d6263677bb1b bnxt_en: support lane configuration via ethtool + ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode + fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event + 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI + 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices + c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" + cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs + e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN + a19b4801457b bnxt_en: Event handler for Thermal event + 3d9cf962067b bnxt_en: Use non-standard attribute to expose shutdown temperature + cd13244f19eb bnxt_en: Expose threshold temperatures through hwmon + 847da8b1178c bnxt_en: Modify the driver to use
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters and some bug fixes.
** Summary changed: - Add Support for Broadcom 5760X Network Controllers + Add Support for Broadcom 5760X Network adapters and some bug fixes. ** Summary changed: - Add Support for Broadcom 5760X Network adapters and some bug fixes. + Add Support for Broadcom 5760X Network adapters and some bug fixes ** Summary changed: - Add Support for Broadcom 5760X Network adapters and some bug fixes + Update bnxt with bug fixes and support for Broadcom 5760X network adapters -- 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/2045796 Title: Update bnxt with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Confirmed Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+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 2047853] Re: mlxbf_gige: replace SAUCE patch for RX race condition
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- 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/2047853 Title: mlxbf_gige: replace SAUCE patch for RX race condition Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] There is a SAUCE patch that addresses a mlxbf-gige RX race condition "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic" This SAUCE patch should be reverted and replaced with upstream content. [Fix] Bring in the following upstream commit from linux-next: "mlxbf_gige: fix receive packet race condition" [Test Case] Boot BF3 platform and ensure oob_net0 interface is up and has IP address Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls occur [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2047853/+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 2046434] Re: TPM2 Problem in 6.2.0 kernel
The error message I get is slightly different: " tpm_crb: probe of MSFT0101:00 failed with error 378 " As https://bugs.launchpad.net/bugs/2047692 was marked as duplicate of this ticket I'll add my original comment here, too - sorry if this breaks launchpad's rules. 6.2.0-39.40~22.04.1 includes upstream stable patchset 2023-10-10 (https://launchpad.net/bugs/2038969) with the TPM changes 'Disable RNG for all AMD fTPMs' and 'Add a helper for checking hwrng enabled'. This causes on some Intel devices that TPM does not work (in my case a Gigabyte Brix GB-BSi5-1135G7). Upstream discussed this issue in https://bugzilla.kernel.org/show_bug.cgi?id=217804 and a fix was found: https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8 (already linked by ~badsmoke in an earlier comment) ** Bug watch added: Linux Kernel Bug Tracker #217804 https://bugzilla.kernel.org/show_bug.cgi?id=217804 -- 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/2046434 Title: TPM2 Problem in 6.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: after updating to kernel 6.2.0-39 i`ve got a problem with TPM on variuos notebooks or desktops. I`ve got this error sudo dmesg |grep tpm [0.359797] tpm_tis NTC0702:00: 2.0 TPM (device-id 0xFC, rev-id 1) [0.372552] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead I havent this problem on previuos kernael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046434/+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 2047909] Re: Support standalone dkms source tree embedded in kernel source
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047909
Title:
Support standalone dkms source tree embedded in kernel source
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
2041800 and a last minute fix bug 2047899), we're to embed usbio-
drivers into oem-6.5 and remove it when all the bits are in position
under formal process.
While IPU6 drivers are still under development, all the related dkms
packages were prebuilt as linux-modules-{ipu6,ivsc}, and we're
expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
build` does not support this yet, so we are separating the mechanism
part here, and the usbio dkms source import in bug 2041800.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047909/+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 2047389] Re: Fix AMDGPU crash on 6.5 kernel
** Changed in: linux (Ubuntu Noble) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047389 Title: Fix AMDGPU crash on 6.5 kernel Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] AMD GPU crash with a message: " cp queue preemption timeout". [Fix] Disable MCBP(mid command buffer preemption) by default as old Mesa hangs with it. [Test] Tested on hardware, play web video for more than 1 hour OK. [Where problems could occur] It may break AMD GPU. This issue is only reproduced on v6.5+ kernel versions and fixes in v6.6, so SRU for oem-6.5, mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047389/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2045947] Re: spidev0 missing on raspberrypi5 on ubuntu 23.10 server and desktop version
** Description changed: + [Impact] + + /dev/spidev0 not present. + + [Test Case] + + 1) Add 'dtparam=spi=on' to /boot/firmware/config.txt. + 2) Boot fixed kernel. + 3) Verify /dev/spidev0 is present. + + [Fix] + + Enable CONFIG_DW_AXI_DMAC. + + [Where Problems Could Occur] + + A new kernel modules is loaded at boot so we could see hangs, freezes, + stack traces or any other buggy kernel code symptoms. + + [Original Description] + While trying to access spidev0 on ubuntu 23.10 server version for raspberrypi model 5 did not find spidev0. On further debugging with raspi team it was observed that DMA is not set. Link to the discussion: https://forums.raspberrypi.com/viewtopic.php?t=360436=25 ubuntu@ubuntu:~$ sudo modprobe configs ubuntu@ubuntu:~$ zcat /proc/config.gz | grep DW_AXI_DMAC # CONFIG_DW_AXI_DMAC is not set Details of platform used ubuntu@ubuntu:~$ ls -al /dev/spi* crw--- 1 root root 153, 0 Dec 7 16:14 /dev/spidev10.0 ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic ubuntu@ubuntu:~$ cat /etc/os-release PRETTY_NAME="Ubuntu 23.10" NAME="Ubuntu" VERSION_ID="23.10" VERSION="23.10 (Mantic Minotaur)" VERSION_CODENAME=mantic ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=mantic LOGO=ubuntu-logo ubuntu@ubuntu:~$ cat /proc/cpuinfo | grep Model Model : Raspberry Pi 5 Model B Rev 1.0 ** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Description changed: [Impact] /dev/spidev0 not present. + + [Fix] + + Enable CONFIG_DW_AXI_DMAC. [Test Case] 1) Add 'dtparam=spi=on' to /boot/firmware/config.txt. 2) Boot fixed kernel. 3) Verify /dev/spidev0 is present. - - [Fix] - - Enable CONFIG_DW_AXI_DMAC. [Where Problems Could Occur] A new kernel modules is loaded at boot so we could see hangs, freezes, stack traces or any other buggy kernel code symptoms. [Original Description] While trying to access spidev0 on ubuntu 23.10 server version for raspberrypi model 5 did not find spidev0. On further debugging with raspi team it was observed that DMA is not set. Link to the discussion: https://forums.raspberrypi.com/viewtopic.php?t=360436=25 ubuntu@ubuntu:~$ sudo modprobe configs ubuntu@ubuntu:~$ zcat /proc/config.gz | grep DW_AXI_DMAC # CONFIG_DW_AXI_DMAC is not set Details of platform used ubuntu@ubuntu:~$ ls -al /dev/spi* crw--- 1 root root 153, 0 Dec 7 16:14 /dev/spidev10.0 ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic ubuntu@ubuntu:~$ cat /etc/os-release PRETTY_NAME="Ubuntu 23.10" NAME="Ubuntu" VERSION_ID="23.10" VERSION="23.10 (Mantic Minotaur)" VERSION_CODENAME=mantic ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=mantic LOGO=ubuntu-logo ubuntu@ubuntu:~$ cat /proc/cpuinfo | grep Model Model : Raspberry Pi 5 Model B Rev 1.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2045947 Title: spidev0 missing on raspberrypi5 on ubuntu 23.10 server and desktop version Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Mantic: New Bug description: [Impact] /dev/spidev0 not present. [Fix] Enable CONFIG_DW_AXI_DMAC. [Test Case] 1) Add 'dtparam=spi=on' to /boot/firmware/config.txt. 2) Boot fixed kernel. 3) Verify /dev/spidev0 is present. [Where Problems Could Occur] A new kernel modules is loaded at boot so we could see hangs, freezes, stack traces or any other buggy kernel code symptoms. [Original Description] While trying to access spidev0 on ubuntu 23.10 server version for raspberrypi model 5 did not find spidev0. On further debugging with raspi team it was observed that DMA is not set. Link to the discussion: https://forums.raspberrypi.com/viewtopic.php?t=360436=25 ubuntu@ubuntu:~$ sudo modprobe configs ubuntu@ubuntu:~$ zcat /proc/config.gz | grep DW_AXI_DMAC # CONFIG_DW_AXI_DMAC is not set Details of platform used ubuntu@ubuntu:~$ ls -al /dev/spi* crw--- 1 root root 153, 0 Dec 7 16:14 /dev/spidev10.0 ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu
[Kernel-packages] [Bug 2038586] Re: Turning COMPAT_32BIT_TIME off on armhf
armhf is going to be dropped in 24.04 as a supported architecture for Pi. ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038586 Title: Turning COMPAT_32BIT_TIME off on armhf Status in linux package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Invalid Bug description: This will prevent existing armhf binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. Also note small inodes cannot be used by ext4. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038586/+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 2047924] [NEW] Jammy update: v6.1.68 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.68 upstream stable release
from git://git.kernel.org/
Linux 6.1.68
drm/i915: Skip some timing checks on BXT/GLK DSI transcoders
drm/i915/sdvo: stop caching has_hdmi_monitor in struct intel_sdvo
drm/i915/lvds: Use REG_BIT() & co.
drm/i915/display: Drop check for doublescan mode in modevalid
riscv: Kconfig: Add select ARM_AMBA to SOC_STARFIVE
netfilter: nft_set_pipapo: skip inactive elements during set walk
MIPS: Loongson64: Enable DMA noncoherent support
MIPS: Loongson64: Handle more memory types passed from firmware
MIPS: Loongson64: Reserve vgabios memory on boot
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
KVM: s390/mm: Properly reset no-dat
MIPS: kernel: Clear FPU states when setting up kernel threads
cifs: Fix flushing, invalidation and file size with FICLONE
cifs: Fix flushing, invalidation and file size with copy_file_range()
USB: gadget: core: adjust uevent timing on gadget unbind
x86/CPU/AMD: Check vendor in the AMD microcode callback
devcoredump: Send uevent once devcd is ready
serial: 8250_omap: Add earlycon support for the AM654 UART controller
serial: 8250: 8250_omap: Do not start RX DMA on THRI interrupt
serial: 8250: 8250_omap: Clear UART_HAS_RHR_IT_DIS bit
serial: sc16is7xx: address RX timeout interrupt errata
ARM: PL011: Fix DMA support
usb: typec: class: fix typec_altmode_put_partner to put plugs
smb: client: fix potential NULL deref in parse_dfs_referrals()
Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
cifs: Fix non-availability of dedup breaking generic/304
parport: Add support for Brainboxes IX/UC/PX parallel cards
serial: 8250_dw: Add ACPI ID for Granite Rapids-D UART
usb: gadget: f_hid: fix report descriptor allocation
drm/amdgpu: Update EEPROM I2C address for smu v13_0_0
drm/amdgpu: Add I2C EEPROM support on smu v13_0_6
drm/amdgpu: simplify amdgpu_ras_eeprom.c
drm/amdgpu: Return from switch early for EEPROM I2C address
drm/amdgpu: Remove second moot switch to set EEPROM I2C address
drm/amdgpu: Add support for RAS table at 0x4
drm/amdgpu: Decouple RAS EEPROM addresses from chips
drm/amdgpu: Remove redundant I2C EEPROM address
drm/amdgpu: Add EEPROM I2C address support for ip discovery
drm/amdgpu: Update ras eeprom support for smu v13_0_0 and v13_0_10
drm/amdgpu: correct the amdgpu runtime dereference usage count
drm/amd/amdgpu: Fix warnings in amdgpu/amdgpu_display.c
drm/amdgpu: fix memory overflow in the IB test
gpiolib: sysfs: Fix error handling on failed export
x86/sev: Fix kernel crash due to late update to read-only ghcb_version
perf: Fix perf_event_validate_size()
arm64: dts: mt8183: kukui: Fix underscores in node names
arm64: dts: mediatek: add missing space before {
parisc: Fix asm operand number out of range build error in bug table
parisc: Reduce size of the bug_table on 64-bit kernel by half
tracing: Stop current tracer when resizing buffer
tracing: Set actual size after ring buffer resize
ring-buffer: Force absolute timestamp on discard of event
LoongArch: BPF: Don't sign extend function return value
LoongArch: BPF: Don't sign extend memory load operand
misc: mei: client.c: fix problem of return '-EOVERFLOW' in mei_cl_write
misc: mei: client.c: return negative error code in mei_cl_write
hwtracing: hisi_ptt: Add dummy callback pmu::read()
coresight: etm4x: Remove bogous __exit annotation for some functions
coresight: etm4x: Make etm4_remove_dev() return void
binder: fix memory leaks of spam and pending work
arm64: dts: mediatek: mt8183-evb: Fix unit_address_vs_reg warning on ntc
arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
arm64: dts: mediatek: mt8195: Fix PM suspend/resume with venc clocks
arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
arm64: dts: mediatek: cherry: Fix interrupt cells for MT6360 on I2C7
arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells properties
arm64: dts: mediatek: mt7622: fix memory node warning check
md/raid6: use valid sector values to determine if an I/O should wait on the
reshape
powercap: DTPM: Fix missing cpufreq_cpu_put() calls
mm: fix oops when filemap_map_pmd() without prealloc_pte
hugetlb: fix null-ptr-deref in hugetlb_vma_lock_write
platform/surface: aggregator: fix recv_buf() return value
regmap: fix bogus error on regcache_sync success
r8169: fix rtl8125b PAUSE frames blasting when suspended
packet: Move reference count in packet_sock to atomic_long_t
tracing: Fix a
[Kernel-packages] [Bug 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
You shouldn't be commenting on closed bugs, your comments might go
unnoticed. Please open a new bug to report issues and/or requests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2017444
Title:
Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-firmware source package in Lunar:
Invalid
Bug description:
== SRU Justification ==
[Impact]
Some Atom based system cannot boot on kernel 6.2 because of atomisp
driver.
[Fix]
Disable the driver via config, suggested by the driver dev.
[Test]
Users confirmed disabling the config works.
[Where problems could occur]
The ISP camera dever worked on Linux. So disabling it shouldn't
introduce any surprise.
== Original Bug Report ==
Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any other
Kernel in 6.2 series or Kernel 6.3.0.
This bug affects all Intel Atom CPU computers in all Linux
distributions making impossible to install or boot to OS with kernel
6.2 or higher.
The bug is caused by Intel atomisp camera driver module which has
firmware missing: shisp_2401a_v21.bin. Missing firmware causes a
watchdog bug notice and Soft Lockup of boot sequence.
NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
The following persons are in charge of atomisp kernel development:
Hans de Goede (maintainer:STAGING - ATOMISP DRIVER)
Mauro Carvalho Chehab (maintainer:STAGING - ATOMISP
DRIVER)
Sakari Ailus (reviewer:STAGING - ATOMISP
DRIVER)
Greg Kroah-Hartman (supporter:STAGING SUBSYSTEM)
linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
linux-ker...@vger.kernel.org (open list)
April 29th Hans de Goede adviced me personally(
https://github.com/linux-surface/linux-surface/issues/1095 ), that
atomisp driver is still in development and should be disabled. By
disabling driver he meant disabling atomisp modules in kernel.
OLD SOLUTION FOR THIS BUG:
Copying (installing) firmware shisp_2401a0_v21.bin from:
https://github.com/intel-aero/meta-intel-aero-
base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin
to /lib/firmware will solve the bug (partially - it still gives error
messages - but at least the computer boots).**
(dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
attachments 9. and 10.)
(Another solution - which Manjaro kernel maintainer did - was to
disable atomisp and related modules).
Afterwards Intel Atom CPU computer will be able to boot with kernel
6.2.
DMESG.LOG OF KUBUNTU 23.04 LIVE USB AND MORE INFORMATION IN:
https://askubuntu.com/questions/1464926/not-able-to-boot-
kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu
The last stable Ubuntu Kernel Intel Atom CPU computer will boot with
is 6.1.25.
This bug was already in 5.19, as you can see from dmesg.logs. It
appears that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but
still the computer boots.
This bug is also reported in Manjaro ( " https://github.com/linux-
surface/linux-surface/issues/1095 ")and Arch Linux ("
https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
limited to Ubuntu Kernels.
This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
bugtracking system (" https://www.mail-archive.com/kernel-
packa...@lists.launchpad.net/msg501664.html ") with Bug number
#2015794.
Attachments:
1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.
2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
5. Video of boot sequence with Kernel 6.2.0-20.
6. uname-a.log of Kernel 6.1.25.
7. lspci-vvnn.log of Kernel 6.1.25.
8. version.log of Kernel 5.19.0-40.
9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**
P.S. The apport-collect data is from Kernel 5.19.0-40.
P.S.P.S I had difficulty determining Tags so they are to be changed by you.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017444/+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 2047780] Re: BlueZ release 5.71
** Attachment added: "bluez_5.71-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735865/+files/bluez_5.71-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Updated source files are attached above. And the source is in: https://git.launchpad.net/~bluetooth/bluez/log/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
** Attachment added: "bluez_5.71.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735864/+files/bluez_5.71.orig.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2041800] Re: [needs-packaging] usbio-drivers
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: Ubuntu Noble Importance: Wishlist Status: Fix Committed ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: Ubuntu Jammy Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041800 Title: [needs-packaging] usbio-drivers Status in Ubuntu: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in The Jammy Jellyfish: New Status in linux-oem-6.5 source package in Jammy: New Status in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice AIC This package provides kernel drivers for MIPI cameras through the Intel IPU6 on Intel MeteoLake platform with Lattice AIC. Upstream URL: https://github.com/intel/usbio-drivers Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms (to request usd-import after created) License: GPL v2 PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2041800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
verified linux-oem-6.5 version 6.5.0-1010.11
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support
verified linux-oem-6.5 version 6.5.0-1010.11
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038259
Title:
Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for FM101R-GL.
[Fix]
* commit 52480e1f1a25 ("USB: serial: option: add Fibocom to DELL custom modem
FM101R-GL"): in v6.6-rc7
* commit a1092619dd28 ("USB: serial: option: fix FM101R-GL defines"): in
v6.7-rc3
[Test Case]
1. check lsusb & dmesg output
```
$ lsusb
Bus 004 Device 002: ID 413c:8215 Dell Computer Corp. Fibocom FM101-GL Module
...
$ sudo dmesg
[8.460678] usbcore: registered new interface driver usbserial_generic
[8.460690] usbserial: USB Serial support registered for generic
[8.549734] usbcore: registered new interface driver option
[8.550108] usbserial: USB Serial support registered for GSM modem (1-port)
[8.550266] option 4-4:1.2: GSM modem (1-port) converter detected
[8.553584] usb 4-4: GSM modem (1-port) converter now attached to ttyUSB0
[8.556445] usbcore: registered new interface driver cdc_ncm
[8.601187] usbcore: registered new interface driver cdc_wdm
[9.059744] cdc_mbim 4-4:1.0: setting rx_max = 16384
[9.060079] cdc_mbim 4-4:1.0: cdc-wdm0: USB WDM device
[9.060338] wwan wwan0: port wwan0mbim0 attached
```
2. make sure ModemManager has probed it:
```
$ mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom
FM101-GL Module
```
[Where problems could occur]
New hardware, still under development. Maybe we'll have to
enable/patch for its vendor specific interface or so.
[Other Info]
The first patch is available for v6.6, and the second for v6.7. While
we're enabling it on linux-oem-6.5/jammy, nominate for linux/noble,
which is currently on v6.6, and linux-oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038259/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN
verified linux-oem-6.5 version 6.5.0-1010.11 ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043964 Title: New China SRRC compliance readiness check for Realtek WLAN 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: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2043964 [Impact] SRRC (State Radio Regulation of China) compliance readiness check for Realtek WLAN. [Fix] Capability for Realtek WiFi TX power tables load and report from RFE (RF front end) parameters is needed. Multiple commits from vanilla kernel. [Test Case] ``` $ sudo iw reg set CN # manually connect to 5G ap : center channel 155 bw 80 M $ sudo cat /sys/kernel/debug/ieee80211/phy0/rtw89/txpwr_table | grep -E 'MCS_2TX_80M_0|Regulatory' ``` The expected output s ``` Regulatory: CN MCS_2TX_80M_0 - NON_BF BF | 10, 9, dbm ``` And verification fail output: ``` Regulatory: CN MCS_2TX_80M_0 - NON_BF BF | 15, 10, dbm ``` [Where problems could occur] This updates the behaviors and constraints of radio device power transmission for rtw89 driver, and must be done for regulatory compliance. [Other Info] As needed for oem-6.5/jammy, nominate only for Noble and oem-6.5/jammy. == original bug report == New China SRRC compliance readiness check Proposed Change: - China SRRC updates the testing requirement for 2.4/5GHz, the major changes are the in-band RSE limit, and EIRP limits. - The SRRC updates impact both WLAN modules and platforms. The WLAN modules need to complete the new SRRC testing then platform can start to apply / renew the new SRRC cert. If platform took several WLAN modules but not all of the modules have completed the new SRRC testing updates, platform cannot renew/apply the new SRRC cert. - The platforms which apply/renew SRRC new standards need to ensure the TX power can meet the new RSE/EIRP limits. IHV confirmed below driver version can support these requirements. Realtek: The upstream driver can support SRRC compliance. https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340 [lore.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043964/+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 2047780] Re: BlueZ release 5.71
** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047301] Re: package linux-hwe-5.15-headers-5.15.0-91 (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg"
Extracting gnome-control-center-faces (1:3.36.5-0ubuntu4.1) to (1:3.36.5-0ubuntu4.1)... dpkg-deb (subprocess): extract archive component: lzma error: compressed data is corrupted [1mdpkg-deb: [0m [1;31merror: [0m subprocess returned error status 2 ** Changed in: linux-hwe-5.15 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2047301 Title: package linux-hwe-5.15-headers-5.15.0-91 (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg" in "/usr/share/pixmaps/faces/bicycle.jpg.dpkg-new": fine del file o dello stream inattesa Status in linux-hwe-5.15 package in Ubuntu: Triaged Bug description: i don't know why ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-hwe-5.15-headers-5.15.0-91 (not installed) ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Dec 24 10:47:38 2023 ErrorMessage: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg" in "/usr/share/pixmaps/faces/bicycle.jpg.dpkg-new": fine del file o dello stream inattesa InstallationDate: Installed on 2023-11-24 (30 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) 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.10 SourcePackage: linux-hwe-5.15 Title: package linux-hwe-5.15-headers-5.15.0-91 (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg" in "/usr/share/pixmaps/faces/bicycle.jpg.dpkg-new": fine del file o dello stream inattesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2047301/+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 2047301] Re: package linux-hwe-5.15-headers-5.15.0-91 (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg"
This looks more like a HW (disk) issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2047301 Title: package linux-hwe-5.15-headers-5.15.0-91 (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg" in "/usr/share/pixmaps/faces/bicycle.jpg.dpkg-new": fine del file o dello stream inattesa Status in linux-hwe-5.15 package in Ubuntu: Triaged Bug description: i don't know why ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-hwe-5.15-headers-5.15.0-91 (not installed) ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Dec 24 10:47:38 2023 ErrorMessage: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg" in "/usr/share/pixmaps/faces/bicycle.jpg.dpkg-new": fine del file o dello stream inattesa InstallationDate: Installed on 2023-11-24 (30 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) 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.10 SourcePackage: linux-hwe-5.15 Title: package linux-hwe-5.15-headers-5.15.0-91 (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/share/pixmaps/faces/bicycle.jpg" in "/usr/share/pixmaps/faces/bicycle.jpg.dpkg-new": fine del file o dello stream inattesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2047301/+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 2046547] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common
This is a dup of bug 2044003. -- 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/2046547 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1045.51 Status in linux package in Ubuntu: New Bug description: this happens when i try sudo apt install linux-tools-common ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: hwdata:amd64: Install linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr 968 F pulseaudio /dev/snd/pcmC0D0p: amr 968 F...m pulseaudio /dev/snd/seq:amr 965 f fluidsynth CRDA: N/A CasperMD5CheckResult: pass Date: Fri Dec 15 14:15:12 2023 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1045.51 InstallationDate: Installed on 2023-12-08 (6 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 80NT ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=bffe25dc-d460-4864-8139-25d9ea4308ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1045.51 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: CFCN21WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 5 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 500-15ISK dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrCFCN21WW(V1.03):bd08/10/2015:br1.21:efr1.21:svnLENOVO:pn80NT:pvrLenovoideapad500-15ISK:rvnLENOVO:rnLenovoideapad5:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad500-15ISK:skuLENOVO_MT_80NT_BU_idea_FM_Lenovoideapad500-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80NT dmi.product.sku: LENOVO_MT_80NT_BU_idea_FM_Lenovo ideapad 500-15ISK dmi.product.version: Lenovo ideapad 500-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046547/+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 2046940] Re: package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common
This is a dup of bug 2044003 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046940 Title: package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: I was just using my OS and this problem emerged on its own. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-6.2-tools-common (not installed) ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-nvidia-6.2-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Dec 18 14:43:27 2023 DpkgTerminalLog: Preparing to unpack .../linux-nvidia-6.2-tools-common_6.2.0-1003.3~22.04.1_all.deb ... Unpacking linux-nvidia-6.2-tools-common (6.2.0-1003.3~22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-nvidia-6.2-tools-common_6.2.0-1003.3~22.04.1_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 InstallationDate: Installed on 2023-07-23 (149 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-nvidia-6.2 Title: package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2046940/+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 2046608] Re: The fan of VisionFive2 still works after I power it off.
I doubt that this is a firmware issue. Reassigning to the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2046608
Title:
The fan of VisionFive2 still works after I power it off.
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
Invalid
Bug description:
The fan of VisionFive2 still works after I power it off.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.4
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
Date: Sat Dec 16 10:23:41 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.2
InstallationDate: Installed on 2023-09-19 (88 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64
(20231011)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 Silicon Motion, Inc. SM2263EN/SM2263XT
(DRAM-less) NVMe SSD Controllers
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS
802.11n Wireless Network Adapter
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 3, If 0, Class=Vendor Specific Class,
Driver=rtl8xxxu, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046608/+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 2047915] [NEW] Jammy update: v6.1.67 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.67 upstream stable release from git://git.kernel.org/ Linux 6.1.67 Revert "wifi: cfg80211: fix CQM for non-range use" ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2047915 Title: Jammy update: v6.1.67 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.67 upstream stable release from git://git.kernel.org/ Linux 6.1.67 Revert "wifi: cfg80211: fix CQM for non-range use" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2047915/+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 2047909] [NEW] Support standalone dkms source tree embedded in kernel source
Public bug reported:
For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
2041800 and a last minute fix bug 2047899), we're to embed usbio-drivers
into oem-6.5 and remove it when all the bits are in position under
formal process.
While IPU6 drivers are still under development, all the related dkms
packages were prebuilt as linux-modules-{ipu6,ivsc}, and we're
expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
build` does not support this yet, so we are separating the mechanism
part here, and the usbio dkms source import in bug 2041800.
** Affects: linux (Ubuntu)
Importance: High
Assignee: You-Sheng Yang (vicamo)
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: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Affects: linux (Ubuntu Noble)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Description changed:
For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
2041800 and a last minute fix bug 2047899), we're to embed usbio-drivers
into oem-6.5 and remove it when all the bits are in position under
formal process.
+
+ While IPU6 drivers are still under development, all the related dkms
+ packages were prebuilt as linux-modules-{ipu6,ivsc}, and we're
+ expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
+ build` does not support this yet, so we are separating the mechanism
+ part here, and the usbio dkms source import in bug 2041800.
** 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 Noble)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/2047909
Title:
Support standalone dkms source tree embedded in kernel source
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 Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
2041800 and a last minute fix bug 2047899), we're to embed usbio-
drivers into oem-6.5 and remove it when all the bits are in position
under formal process.
While IPU6 drivers are still under development, all the related dkms
packages were prebuilt as linux-modules-{ipu6,ivsc}, and we're
expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
build` does not support this yet, so we are separating the mechanism
part here, and the usbio dkms source import in bug 2041800.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047909/+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 2047885] Re: Reporting Bug
** Package changed: 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/2047885 Title: Reporting Bug Status in linux package in Ubuntu: New Bug description: After updating the ubuntu version to 22.4 , i am getting a problem of screen gliching and it doesn't showing screen clearly and also i am getting an error like failed to start http apache server. i hope you will solve my problem as soon as possible . THANK YOU ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: student1828 F pulseaudio /dev/snd/pcmC1D0p: student1828 F...m pulseaudio /dev/snd/controlC0: student1828 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 09:50:37 2024 InstallationDate: Installed on 2018-06-06 (2036 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP 245 G6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic root=UUID=d6a31861-740c-4ce5-87e8-73ec7211c1ee ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-91-generic N/A linux-backports-modules-5.15.0-91-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2024-01-02 (0 days ago) dmi.bios.date: 01/12/2018 dmi.bios.release: 15.21 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8324 dmi.board.vendor: Hewlett-Packard dmi.board.version: 22.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 22.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.21:bd01/12/2018:br15.21:efr22.25:svnHewlett-Packard:pnHP245G6NotebookPC:pvr:rvnHewlett-Packard:rn8324:rvr22.25:cvnHewlett-Packard:ct10:cvrChassisVersion:sku4AD35PA#ACJ: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G6 Notebook PC dmi.product.sku: 4AD35PA#ACJ dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047885/+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 2047908] [NEW] Jammy update: v6.1.66 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.66 upstream stable release from git://git.kernel.org/ Linux 6.1.66 iomap: update ki_pos a little later in iomap_dio_complete x86/apic/msi: Fix misconfigured non-maskable MSI quirk x86/xen: fix percpu vcpu_info allocation xen: simplify evtchn_do_upcall() call maze xen: Allow platform PCI interrupt to be shared r8169: fix deadlock on RTL8125 in jumbo mtu mode r8169: disable ASPM in case of tx timeout drm/amd/display: Fix MPCC 1DLUT programming drm/amd/display: Fix the delta clamping for shaper LUT drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut drm/amd/display: Expand kernel doc for DC mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled mmc: core: add helpers mmc_regulator_enable/disable_vqmmc drm/amd/pm: fix a memleak in aldebaran_tables_init iommu/vt-d: Make context clearing consistent with context mapping iommu/vt-d: Disable PCI ATS in legacy passthrough mode iommu/vt-d: Add device_block_translation() helper iommu/vt-d: Allocate pasid table in device probe path iommu/vt-d: Omit devTLB invalidation requests when TES=0 cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily cpufreq: imx6q: don't warn for disabling a non-existing frequency drm/amd/display: Guard against invalid RPTR/WPTR being set drm/amd/display: Restore rptr/wptr for DMCUB as workaround spi: Fix null dereference on suspend fbdev: stifb: Make the STI next font pointer a 32-bit signed offset PCI: qcom-ep: Add dedicated callback for writing to DBI2 registers octeontx2-af: Initialize 'cntr_val' to fix uninitialized symbol error PCI: Lengthen reset delay for VideoPropulsion Torrent QN16e card KVM: x86: Fix lapic timer interrupt lost after loading a snapshot. net: ravb: Keep reverse order of operations in ravb_remove() net: ravb: Stop DMA in case of failures on ravb_open() net: ravb: Start TX queues after HW initialization succeeded net: ravb: Make write access to CXR35 first before accessing other EMAC registers net: ravb: Use pm_runtime_resume_and_get() net: ravb: Check return value of reset_control_deassert() ravb: Fix races between ravb_tx_timeout_work() and net related ops r8169: prevent potential deadlock in rtl8169_close octeontx2-pf: Restore TC ingress police rules when interface is up octeontx2-af: Install TC filter rules in hardware based on priority octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64 net: stmmac: xgmac: Disable FPE MMC interrupts octeontx2-af: Fix possible buffer overflow selftests/net: mptcp: fix uninitialized variable warnings selftests/net: unix: fix unused variable compiler warning selftests/net: fix a char signedness issue selftests/net: ipsec: fix constant out of range uapi: propagate __struct_group() attributes to the container union dpaa2-eth: increase the needed headroom to account for alignment ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet usb: config: fix iteration issue in 'usb_get_bos_descriptor()' USB: core: Change configuration warnings to notices USB: xhci-plat: fix legacy PHY double init wifi: cfg80211: fix CQM for non-range use serial: sc16is7xx: add missing support for rs485 devicetree properties serial: sc16is7xx: Put IOControl register into regmap_volatile auxdisplay: hd44780: move cursor home after clear display command Input: xpad - add HyperX Clutch Gladiate Support btrfs: fix 64bit compat send ioctl arguments not initializing version member btrfs: make error messages more clear when getting a chunk map btrfs: send: ensure send_fd is writable btrfs: fix off-by-one when checking chunk map includes logical address btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod() btrfs: add dmesg output for first mount and last unmount of a filesystem parisc: Mark altinstructions read-only and 32-bit aligned parisc: Ensure 32-bit alignment on parisc unwind section parisc: Mark jump_table naturally aligned parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes parisc: Mark lock_aligned variables 16-byte aligned on SMP parisc: Use natural CPU alignment for bug_table parisc: Mark ex_table entries 32-bit aligned in uaccess.h parisc: Mark ex_table entries 32-bit aligned in assembly.h powerpc: Don't clobber f0/vs0 during fp|altivec register save KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers iommu/vt-d: Add MTL to quirk list to skip TE disabling bcache: revert replacing IS_ERR_OR_NULL with IS_ERR dma-buf: fix check in dma_resv_add_fence cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch()
[Kernel-packages] [Bug 2047698] Re: I have no audio.
What is the make and model of the machine? It seems to identify itself as "Default string". ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** 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/2047698 Title: I have no audio. Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: Audio isn't working, I have tried everything including this bug report. Still no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-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 Dec 29 13:58:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:2212] InstallationDate: Installed on 2023-12-28 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=b5301c3d-1b26-47f8-ad4f-90997f62a480 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd04/21/2023:br5.19:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 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-6.2/+bug/2047698/+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 2047885] [NEW] Reporting Bug
You have been subscribed to a public bug: After updating the ubuntu version to 22.4 , i am getting a problem of screen gliching and it doesn't showing screen clearly and also i am getting an error like failed to start http apache server. i hope you will solve my problem as soon as possible . THANK YOU ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: student1828 F pulseaudio /dev/snd/pcmC1D0p: student1828 F...m pulseaudio /dev/snd/controlC0: student1828 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 09:50:37 2024 InstallationDate: Installed on 2018-06-06 (2036 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP 245 G6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic root=UUID=d6a31861-740c-4ce5-87e8-73ec7211c1ee ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-91-generic N/A linux-backports-modules-5.15.0-91-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2024-01-02 (0 days ago) dmi.bios.date: 01/12/2018 dmi.bios.release: 15.21 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8324 dmi.board.vendor: Hewlett-Packard dmi.board.version: 22.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 22.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.21:bd01/12/2018:br15.21:efr22.25:svnHewlett-Packard:pnHP245G6NotebookPC:pvr:rvnHewlett-Packard:rn8324:rvr22.25:cvnHewlett-Packard:ct10:cvrChassisVersion:sku4AD35PA#ACJ: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G6 Notebook PC dmi.product.sku: 4AD35PA#ACJ dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Reporting Bug https://bugs.launchpad.net/bugs/2047885 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
