[Kernel-packages] [Bug 2002763] Re: Missing how to uninstall (back to generic kernel) in OEMKernel wiki
Dell Precision 5560 is managed by oem-somerville-pidgey-meta. Dell XPS 13 9310 is managed by oem-somerville-bulbasaur-meta. You can simply purge those Debian packages and then reboot the system to use the generic kernel. `sudo apt-get purge oem-somerville-pidgey-meta` or `sudo apt-get purge oem-somerville-bulbasaur-meta`. ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/2002763 Title: Missing how to uninstall (back to generic kernel) in OEMKernel wiki Status in linux-oem-5.10 package in Ubuntu: Invalid Bug description: In OEMKernel wiki(https://wiki.ubuntu.com/Kernel/OEMKernel), How to install is documented, but how to uninstall OEMKernel or back to the generic kernel? It's not documented. Maybe that's why this issue is fired: https://ubuntuforums.org/showthread.php?t=2470860 And I also take almost harf an hour to search and still cannot find how to back to the generic kernel. Here is my case: Confirmed with HighPoint just now, their Linux driver cann't support OEM Kernel currently. So I want to back to the generic kernel. But how? shoudn't be documented in Wiki? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/2002763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973257] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess
Encountered error while installing available upgrade for bcmwl package:
dpkg: error processing package bcmwl-kernel-source (--configure):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
Errors were encountered while processing:
bcmwl-kernel-source
E: Sub-process /usr/bin/dpkg returned an error code (1)
Some excerpts from the system and build info are listed below and the
make log is in the attachment.
System info:
Description: Ubuntu 20.04 LTS
Release: Pop!_OS
Kernel: Linux pop-os 5.17.5-76051705-generic
#202204271406~1653440576~20.04~6277a18-Ubuntu SMP PREEMPT Thu Ma x86_64 x86_64
x86_64 GNU/Linux
Building log:
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.17.5-76051705-generic
Building for architecture x86_64
Building initial module for 5.17.5-76051705-generic
ERROR (dkms apport): kernel package linux-headers-5.17.5-76051705-generic is
not supported
Error! Bad return status for module build on kernel: 5.17.5-76051705-generic
(x86_64)
** Attachment added: "bcmwl-6.30.223.271+bdcom_make.log"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1973257/+attachment/5642454/+files/bcmwl-6.30.223.271+bdcom_make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1973257
Title:
package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3 failed
to install/upgrade: installed bcmwl-kernel-source package post-
installation script subprocess returned error exit status 10
Status in bcmwl package in Ubuntu:
New
Bug description:
System info:
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Linux kot9ra-Air 5.17.7+ #2 SMP Fri May 13 05:27:24 BST 2022 x86_64 x86_64
x86_64 GNU/Linux
Building log:
Building for 5.17.7+
Building for architecture x86_64
Building initial module for 5.17.7+
ERROR (dkms apport): kernel package linux-headers-5.17.7+ is not supported
Error! Bad return status for module build on kernel: 5.17.7+ (x86_64)
Make.log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.17.7+ (x86_64)
Fri 13 May 05:44:12 BST 2022
make: Entering directory '/usr/src/linux-headers-5.17.7+'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:794:3:
note: in expansion of macro ‘WL_DBG’
794 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:795:2:
note: here
795 | default:
| ^~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:81:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.h:73: warning:
"isprint" redefined
73 | #define isprint(c) bcm_isprint(c)
|
In file included from ./include/linux/string_helpers.h:6,
from ./include/linux/seq_file.h:7,
from ./include/linux/seq_file_net.h:5,
from ./include/net/net_namespace.h:183,
from ./include/linux/netdevice.h:37,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:69,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27:
./include/linux/ctype.h:30: note: this is the location of the previous
definition
30 | #define isprint(c) ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0)
|
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/osl.h:79,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:28:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:36:
warning: passing argument 1 of ‘memcpy’ discards ‘const’ qualifier from pointer
target type [-Wdiscarded-qualifiers]
645 | bcopy(&wl->pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN);
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linux_osl.h:156:39:
note: in definition of macro ‘bcopy’
156 |
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
SRU submitted, thanks https://lists.ubuntu.com/archives/kernel-team/2023-January/136392.html ** Description changed: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] - Verified by Aaron Ma. + Verified by Aaron Ma and the bug reporter. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] Verified by Aaron Ma and the bug reporter. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install
Install alsa-ucm-conf version 1.2.6.3-1ubuntu1.3 on HP ZBook Studio G9 laptop, the mic default turned on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2001896 Title: sof-hda-dsp internal mic default off after fresh install Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Device with sof-hda-dsp sound card has internal mic off after fresh install [Test Plan] On the platform with sofhdadsp sound card 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal mic should be on by default [Where problems could occur] The change takes place on platform with sof-hda-dsp sound card, and it only be executed during boot sequence, it won't impact the stored state. However, it will change user default expectation after fresh installation. [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/259 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install
Install alsa-ucm-conf version 1.2.6.3-1ubuntu4 on HP ZBook Studio G9 laptop, the mic default turned on. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2001896 Title: sof-hda-dsp internal mic default off after fresh install Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Device with sof-hda-dsp sound card has internal mic off after fresh install [Test Plan] On the platform with sofhdadsp sound card 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal mic should be on by default [Where problems could occur] The change takes place on platform with sof-hda-dsp sound card, and it only be executed during boot sequence, it won't impact the stored state. However, it will change user default expectation after fresh installation. [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/259 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
Install alsa-ucm-conf version 1.2.6.3-1ubuntu4 on HP ZBook Studio G9 laptop, the mic mute led turned on after press the key. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
Install alsa-ucm-conf version 1.2.6.3-1ubuntu1.3 on HP ZBook Studio G9 laptop, the mic mute led turned on after press the key. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003282] [NEW] Unable to boot, amdgpu kernel panic
Public bug reported: When upgrading from 5.11.0-44 to any 5.13 or 5.15.0-5x kernel, loading the amdgpu module causes a kernel panic on boot. If I uninstall the linux-modules-extra package or blacklist the amdgpu module in modprobe.d, then I am able to boot. The kernel panic messages scroll a bit too fast for me to capture the output during boot. My graphics card is an AMG Vega 64. ``` Description:Ubuntu 20.04.5 LTS Release:20.04 ``` The crash is very similar to bug #1956473 and #1981883 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.15.0-58-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 18 22:06:59 2023 ProcEnviron: LANGUAGE=en_US TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: When upgrading from 5.11.0-44 to any 5.13 or 5.15.0-5x kernel, loading the amdgpu module causes a kernel panic on boot. If I uninstall the linux-modules-extra package or blacklist the amdgpu module in modprobe.d, then I am able to boot. The kernel panic messages scroll a bit too fast for me to capture the output during boot. ``` Description: Ubuntu 20.04.5 LTS Release: 20.04 ``` + + The crash is very similar to bug #1956473 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.15.0-58-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 18 22:06:59 2023 ProcEnviron: - LANGUAGE=en_US - TERM=rxvt-unicode-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + TERM=rxvt-unicode-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When upgrading from 5.11.0-44 to any 5.13 or 5.15.0-5x kernel, loading the amdgpu module causes a kernel panic on boot. If I uninstall the linux-modules-extra package or blacklist the amdgpu module in modprobe.d, then I am able to boot. The kernel panic messages scroll a bit too fast for me to capture the output during boot. + My graphics card is an AMG Vega 64. + ``` Description: Ubuntu 20.04.5 LTS Release: 20.04 ``` - The crash is very similar to bug #1956473 + The crash is very similar to bug #1956473 and #1981883 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.15.0-58-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 18 22:06:59 2023 ProcEnviron: LANGUAGE=en_US TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2003282 Title: Unable to boot, amdgpu kernel panic Status in linux-hwe-5.15 package in Ubuntu: New Bug description: When upgrading from 5.11.0-44 to any 5.13 or 5.15.0-5x kernel, loading the amdgpu module causes a kernel panic on boot. If I uninstall the linux-modules-extra package or blacklist the amdgpu module in modprobe.d, then I am able to boot. The kernel panic messages scroll a bit too fast for me to capture the output during boot. My graphics card is an AMG Vega 64. ``` Description: Ubuntu 20.04.5 LTS Release: 20.04 ``` The crash is very similar to bug #1956473 and #1981883 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.15.0-58-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 18 22:06:59 2023 ProcEnviron: LANGUAGE=en_US TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Sou
[Kernel-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
OK so you may or may not be commenting on the right bug. Assuming you are, we'll just ask you to test the proposed fix when it is built... ** Description changed: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] - ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN + No verifiable test case yet. Will ask the community for testing, and if + it fails then consider reverting the fix. [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. -- 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/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] No verifiable test case yet. Will ask the community for testing, and if it fails then consider reverting the fix. [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
That's probably not as good as sticking to nouveau because it will fall back to software rendering instead. But the third and best option is to install an Nvidia driver using the 'Additional Drivers' app. -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/2003031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4
A fix has been proposed for Lunar. https://lists.ubuntu.com/archives/kernel-team/2023-January/136387.html Since the Config management has change between series, a similar patch/fix needs to be added for Kinetic and Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990800 Title: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu This is a new test case from bug 1988809 Test failed with: Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: fib_nexthop_nongw.sh # Object "nexthop" is unknown, try "ip help". # Error: either "to" is duplicate, or "nhid" is a garbage. # TEST: nexthop: get route with nexthop without gw[FAIL] # TEST: nexthop: ping through nexthop without gw [FAIL] not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1 -- [Impact] When running kselftests on Bionic with a 5.4 kernel, it would fail because of no nexthop capability. [Fix] We query the ip command help to know whether it is implemented or not, and we skip or execute the test accordingly [Test Plan] Running the test script directly in Bionic will throw a Skip, while running it in Focal will throw the test result. [Where problems could ocurr] The regression potential for this is low. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995783] Re: Nightlight fails after suspend
** Tags added: nightlight -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1995783 Title: Nightlight fails after suspend Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Nightlight activates when turned on in settings but after closing the lid or otherwise suspending and then resuming power nightlight fails to change the color temperature. Settings still indicates that nightlight is on. If nightlight setting is cycled nightlight works again until the next suspend. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.154 Wed Jun 22 04:50:54 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 5 22:03:14 2022 DistUpgraded: 2022-10-29 22:31:31,858 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/390.154, 5.15.0-52-generic, x86_64: installed nvidia/390.154, 5.19.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:212b] NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:1247] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 635M [1043:212b] InstallationDate: Installed on 2019-01-15 (1390 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK Computer Inc. N55SL ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=47b67201-d4ee-44d7-adec-9d457d3c9b5c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-30 (6 days ago) dmi.bios.date: 10/24/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N55SL.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N55SL 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:bvnAmericanMegatrendsInc.:bvrN55SL.204:bd10/24/2012:br4.6:svnASUSTeKComputerInc.:pnN55SL:pvr1.0:rvnASUSTeKComputerInc.:rnN55SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku: dmi.product.family: N dmi.product.name: N55SL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 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/mutter/+bug/1995783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
** Changed in: linux-kvm (Ubuntu Lunar)
Status: New => Confirmed
** Changed in: linux-kvm (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1998244
Title:
kselftest net/fib_nexthop_nongw.sh fails
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Jammy:
New
Status in linux-kvm source package in Kinetic:
Confirmed
Status in linux-kvm source package in Lunar:
Confirmed
Bug description:
18272 03:33:07 DEBUG| Persistent state client._record_indent
now set to 2
18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
18275 03:33:07 WARNI| System python is too old, crash
handling disabled
18276 03:33:07 DEBUG| Running 'make run_tests -C net
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18277 03:33:07 DEBUG| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules
ARCH=x86 -C ../../../.. headers_install
18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18282 03:33:08 DEBUG| [stdout] TAP version 13
18283 03:33:08 DEBUG| [stdout] 1..1
18284 03:33:08 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type.
18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route
with nexthop without gw[ OK ]
18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through
nexthop without gw [FAIL]
18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net:
fib_nexthop_nongw.sh # exit=1
18291 03:33:18 DEBUG| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
--
SRU Justification:
[Impact]
* Without Kernel support for the Dummy net driver, it is not possible
to successfully run selftests that use it. This includes as per this
bug net/fib_nexthop_nongw.sh, but also could potentially include other
such as rtnetlink.sh, fib_rule_tests.sh, forwarding/* etc.
[Fix]
* Custom patch to enable CONFIG_DUMMY=m
[Test Plan]
* Before the fix, the net/fib_nexthop_nongw.sh script will fail in the
specific line which does
$ ip -n h1 link add name eth0 type dummy
Error: Unknown device type.
After the fix it does not fail.
[Where problems could occur]
* The regression can be considered as low, since we are adding
functionality not previously present.
[Other Info]
* There does not seem to be a historical reason for removing it from
linux-kvm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1998244/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003267 Title: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release Status in intel: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Description: Enable Intel_idle for eagle stream. Target Kernel: Backport to 5.15 Target Release: 22.04 Commit Ids: 7eac3bd38d18 intel_idle: Fix SPR C6 optimization (Merged in 5.18 kernel) 39c184a6a9a7 intel_idle: Fix the 'preferred_cstates' module parameter (Merged in 5.18 kernel) 03eb65224e57 cpuidle: intel_idle: Drop redundant backslash at line end (Merged in 5.18 kernel) 3a9cf77b60dc intel_idle: add core C6 optimization for SPR (Merged in 5.18 kernel) da0e58c038e6 intel_idle: add 'preferred_cstates' module argument (Merged in 5.18 kernel) 9edf3c0ffef0 intel_idle: add SPR support(Merged in 5.18 kernel) 1548fac47a11 intel_idle: make SPR C1 and C1E be independent (Merged in 6.0 kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986717] Re: [SRU]Update ice driver to support E823 devices
** Description changed: SRU Justification: - Impact: + [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. - Fix: - After talking with engineers upstream this should be the only patch needed to add the support that is missing in 5.4 + [Fix] e36aeec0f4e5 ice: add support for E823 devices + 5d9e618cbb54 ice: Add device ids for E822 devices - Testcase: - Load ice driver on system with E823 device present and ensure the device is seen by the system + [Testcase] + + Load ice driver on system with E823 device present and ensure the device + is seen by the system + + [Where problems could occur] + + The regression risk is low + Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 ** Description changed: SRU Justification: [Impact] - Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. + + Ice driver does not support E823 in 5.4. This was introduced in 5.7, + but is part of the Ice Lake D platform which is otherwise supported in + 5.4. One of the hardware vendors has requested that we update Ice in + 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low - Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 ** Description changed: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low + These patches did not cherry pick cleanly I had to make some changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 ** Description changed: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low - These patches did not cherry pick cleanly I had to make some changes. + These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 -- 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/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986717] Re: [SRU}Update ice driver to support E823 devices
** Summary changed: - Update ice driver to support E823 devices + [SRU}Update ice driver to support E823 devices ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Michael Reed (mreed8855) ** Summary changed: - [SRU}Update ice driver to support E823 devices + [SRU]Update ice driver to support E823 devices -- 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/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
@acelankao: Thanks very much! Confirmed that your test kernel fixes the screen blanking problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Triaged Bug description: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] Verified by Aaron Ma. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Description changed: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] - + Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support ** Description changed: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: - ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h - dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 - 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough - 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs - 83959ce5204a scsi: mpi3mr: Add support for PEL commands - eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands - 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header - a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands - 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support + f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 + 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough + 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs + 43ca11005098 scsi: mpi3mr: Add support for PEL commands + 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands + f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header + f5e6d5a34376 scsi: mpi3mr: Add support for driver commands + 4268fa751365 scsi: mpi3mr: Add bsg device support + 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc + 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings + 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes + e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes + bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails + a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() + 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR + 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset + 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s - Thanks, - Sumit [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] - Moderate to low regression risk for the kernel as most changes are in the driver + + Moderate to low regression risk for the kernel as most changes are in + the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support -- 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/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr:
[Kernel-packages] [Bug 2003267] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2003267 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003267 Title: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Description: Enable Intel_idle for eagle stream. Target Kernel: Backport to 5.15 Target Release: 22.04 Commit Ids: 7eac3bd38d18 intel_idle: Fix SPR C6 optimization (Merged in 5.18 kernel) 39c184a6a9a7 intel_idle: Fix the 'preferred_cstates' module parameter (Merged in 5.18 kernel) 03eb65224e57 cpuidle: intel_idle: Drop redundant backslash at line end (Merged in 5.18 kernel) 3a9cf77b60dc intel_idle: add core C6 optimization for SPR (Merged in 5.18 kernel) da0e58c038e6 intel_idle: add 'preferred_cstates' module argument (Merged in 5.18 kernel) 9edf3c0ffef0 intel_idle: add SPR support(Merged in 5.18 kernel) 1548fac47a11 intel_idle: make SPR C1 and C1E be independent (Merged in 6.0 kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003267 Title: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release Status in intel: Fix Released Status in linux package in Ubuntu: New Bug description: Description: Enable Intel_idle for eagle stream. Target Kernel: Backport to 5.15 Target Release: 22.04 Commit Ids: 7eac3bd38d18 intel_idle: Fix SPR C6 optimization (Merged in 5.18 kernel) 39c184a6a9a7 intel_idle: Fix the 'preferred_cstates' module parameter (Merged in 5.18 kernel) 03eb65224e57 cpuidle: intel_idle: Drop redundant backslash at line end (Merged in 5.18 kernel) 3a9cf77b60dc intel_idle: add core C6 optimization for SPR (Merged in 5.18 kernel) da0e58c038e6 intel_idle: add 'preferred_cstates' module argument (Merged in 5.18 kernel) 9edf3c0ffef0 intel_idle: add SPR support(Merged in 5.18 kernel) 1548fac47a11 intel_idle: make SPR C1 and C1E be independent (Merged in 6.0 kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002748] Re: Unable to handle page fault under heavy M.2 load
A backup (rsync) ran again and crashed: [16096.851781] usb 2-1: reset SuperSpeed USB device number 3 using xhci_hcd [16096.875912] usb 2-1: LPM exit latency is zeroed, disabling LPM. [20421.689261] perf: interrupt took too long (6260 > 6216), lowering kernel.perf_event_max_sample_rate to 31750 [145901.879732] BUG: unable to handle page fault for address: d824fa40 [145901.879789] #PF: supervisor read access in kernel mode [145901.879820] #PF: error_code(0x) - not-present page [145901.879849] PGD 721a15067 P4D 721a15067 PUD 721a17067 PMD 0 [145901.879885] Oops: [#1] SMP PTI [145901.879907] CPU: 2 PID: 846408 Comm: rsync Tainted: G OE 5.15.0-57-generic #63-Ubuntu [145901.879957] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 1.23 04/08/2021 [145901.879996] RIP: 0010:do_dentry_open+0xc8/0x390 [145901.880029] Code: 00 20 0f 85 07 02 00 00 66 2d 00 40 66 a9 00 b0 75 07 81 4b 44 00 80 00 00 49 8b 84 24 68 01 00 00 48 85 c0 0f 84 54 01 00 00 <48> 8b 38 e8 30 a3 e0 ff 84 c0 0f 84 44 01 00 00 49 8b 84 24 68 01 [145901.880124] RSP: 0018:a67d8301fc50 EFLAGS: 00010282 [145901.880154] RAX: d824fa40 RBX: 96e32f006100 RCX: 0002 [145901.880192] RDX: 41ed RSI: 0002 RDI: 96e318380c8c [145901.880230] RBP: a67d8301fc80 R08: 96e318623060 R09: 96e208cd6600 [145901.880268] R10: 0001 R11: 32336372 R12: 96e2020a0ee0 [145901.880306] R13: R14: 96e32f006110 R15: 96e32f006100 [145901.880344] FS: 7f0f8e4ef740() GS:96ea5fd0() knlGS: [145901.880388] CS: 0010 DS: ES: CR0: 80050033 [145901.880420] CR2: d824fa40 CR3: 00012f55 CR4: 00350ee0 [145901.880458] Call Trace: [145901.880474] [145901.880490] vfs_open+0x2d/0x40 [145901.880513] do_open+0x20d/0x470 [145901.880535] path_openat+0x112/0x2b0 [145901.880557] ? evm_inode_setattr+0x2d/0xf0 [145901.880584] do_filp_open+0xb2/0x160 [145901.880607] ? __check_object_size+0x1d/0x30 [145901.880634] do_sys_openat2+0x9f/0x160 [145901.880659] __x64_sys_openat+0x55/0x90 [145901.880683] do_syscall_64+0x59/0xc0 [145901.880706] ? do_syscall_64+0x69/0xc0 [145901.880729] ? exit_to_user_mode_prepare+0x37/0xb0 [145901.880758] ? syscall_exit_to_user_mode+0x27/0x50 [145901.880786] ? __x64_sys_newfstatat+0x1c/0x30 [145901.880813] ? do_syscall_64+0x69/0xc0 [145901.880835] ? do_syscall_64+0x69/0xc0 [145901.880857] ? do_syscall_64+0x69/0xc0 [145901.880879] entry_SYSCALL_64_after_hwframe+0x61/0xcb [145901.880910] RIP: 0033:0x7f0f8e60bbcc [145901.880932] Code: 24 18 31 c0 41 83 e2 40 75 44 89 f0 25 00 00 41 00 3d 00 00 41 00 74 36 44 89 c2 4c 89 ce bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 48 8b 54 24 18 64 48 2b 14 25 28 00 00 00 [145901.881025] RSP: 002b:7fff5c804d30 EFLAGS: 0287 ORIG_RAX: 0101 [145901.881066] RAX: ffda RBX: RCX: 7f0f8e60bbcc [145901.881103] RDX: 00090800 RSI: 7fff5c806ff0 RDI: ff9c [145901.881141] RBP: 7fff5c806ff0 R08: 00090800 R09: 7fff5c806ff0 [145901.881179] R10: R11: 0287 R12: 55ac421173f0 [145901.881216] R13: 7fff5c806ff0 R14: 0001 R15: 55ac421173f0 [145901.881255] [145901.881269] Modules linked in: tcp_diag udp_diag inet_diag cpuid xt_nat xt_tcpudp veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc rdma_ucm ib_uverbs rdma_cm iw_cm ib_cm ib_core nvme_fabrics overlay bonding tls binfmt_misc intel_rapl_msr intel_rapl_common intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc intel_telemetry_core mei_hdcp x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nls_iso8859_1 kvm rapl intel_cstate input_leds joydev ee1004 mei_me r8125(OE) mei mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr ramoops pstore_blk pstore_zone reed_solomon efi_pstore nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_ pq [145901.881363] libcrc32c raid0 multipath linear i915 i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec raid1 xhci_pci crct10dif_pclmul rc_core sdhci_pci nvme i2c_i801 cqhci crc32_pclmul ghash_clmulni_intel aesni_intel i2c_smbus crypto_simd sdhci nvme_core drm cryptd xhci_pci_renesas intel_lpss_pci intel_lpss ahci idma64 libahci video pinctrl_geminilake [145901.881978] CR2: d824fa40 [145901.882000] ---[ end trace 69c48397b099b00e ]--- [145902.109279] RIP: 0010:do_dentry_open+0xc8/0x390 [145902.109325] Code: 00 20 0f 85 07 02 00 00 66 2d 00 40 66 a9 00 b0 75 07
[Kernel-packages] [Bug 2003270] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003270 Title: No WiFi networks found in visible networks list. Status in linux package in Ubuntu: Confirmed Bug description: When I turn on the laptop, the WiFi is connected, few seconds later it disconnects and can't find any WiFi network in visible networks list. Description: Ubuntu 22.04.1 LTS Release: 22.04 I can't use WiFi for this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grugel 1943 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 19 03:19:40 2023 InstallationDate: Installed on 2022-10-16 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=3afe5789-9b65-48e6-b0f9-7e4c7c157b8b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2021 dmi.bios.release: 2.33 dmi.bios.vendor: LENOVO dmi.bios.version: ALCN33WW(V2.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IWL dmi.ec.firmware.release: 2.33 dmi.modalias: dmi:bvnLENOVO:bvrALCN33WW(V2.10):bd06/23/2021:br2.33:efr2.33:svnLENOVO:pn81N7:pvrLenovoIdeaPadS340-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IWL:skuLENOVO_MT_81N7_BU_idea_FM_IdeaPadS340-14IWL: dmi.product.family: IdeaPad S340-14IWL dmi.product.name: 81N7 dmi.product.sku: LENOVO_MT_81N7_BU_idea_FM_IdeaPad S340-14IWL dmi.product.version: Lenovo IdeaPad S340-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org
Were these git commands useful? -- 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/1998643 Title: smartpqi: Update 22.04 driver to latest kernel.org Status in linux package in Ubuntu: Incomplete Bug description: There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [impact] This patches correct some bugs and add support for more PCI devices. Also, the in-box driver is largely out-of-date with kernel.org. [fix] Applying these patches (along with the patches noted below) bring smartpqi up to date with our OOB driver and kernel.org. Both have been tested. [Test Plan] Our OOB driver has undergone extensive testing by our test team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003270] [NEW] No WiFi networks found in visible networks list.
Public bug reported: When I turn on the laptop, the WiFi is connected, few seconds later it disconnects and can't find any WiFi network in visible networks list. Description:Ubuntu 22.04.1 LTS Release:22.04 I can't use WiFi for this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grugel 1943 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 19 03:19:40 2023 InstallationDate: Installed on 2022-10-16 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=3afe5789-9b65-48e6-b0f9-7e4c7c157b8b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2021 dmi.bios.release: 2.33 dmi.bios.vendor: LENOVO dmi.bios.version: ALCN33WW(V2.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IWL dmi.ec.firmware.release: 2.33 dmi.modalias: dmi:bvnLENOVO:bvrALCN33WW(V2.10):bd06/23/2021:br2.33:efr2.33:svnLENOVO:pn81N7:pvrLenovoIdeaPadS340-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IWL:skuLENOVO_MT_81N7_BU_idea_FM_IdeaPadS340-14IWL: dmi.product.family: IdeaPad S340-14IWL dmi.product.name: 81N7 dmi.product.sku: LENOVO_MT_81N7_BU_idea_FM_IdeaPad S340-14IWL dmi.product.version: Lenovo IdeaPad S340-14IWL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Image from my laptop's monitor." https://bugs.launchpad.net/bugs/2003270/+attachment/5642359/+files/Image.jpg -- 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/2003270 Title: No WiFi networks found in visible networks list. Status in linux package in Ubuntu: New Bug description: When I turn on the laptop, the WiFi is connected, few seconds later it disconnects and can't find any WiFi network in visible networks list. Description: Ubuntu 22.04.1 LTS Release: 22.04 I can't use WiFi for this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grugel 1943 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 19 03:19:40 2023 InstallationDate: Installed on 2022-10-16 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=3afe5789-9b65-48e6-b0f9-7e4c7c157b8b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.b
[Kernel-packages] [Bug 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
** Description changed:
18272 03:33:07 DEBUG| Persistent state client._record_indent
now set to 2
- 18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
- 18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700
seconds
- 18275 03:33:07 WARNI| System python is too old, crash
handling disabled
- 18276 03:33:07 DEBUG| Running 'make run_tests -C net
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
- 18277 03:33:07 DEBUG| [stdout] make: Entering
directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
- 18278 03:33:07 DEBUG| [stdout] make
--no-builtin-rules ARCH=x86 -C ../../../.. headers_install
- 18279 03:33:07 DEBUG| [stdout] make[1]: Entering
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
- 18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
- 18281 03:33:08 DEBUG| [stdout] make[1]: Leaving
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
- 18282 03:33:08 DEBUG| [stdout] TAP version 13
- 18283 03:33:08 DEBUG| [stdout] 1..1
- 18284 03:33:08 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
- 18285 03:33:08 DEBUG| [stdout] # Error: Unknown
device type.
- 18286 03:33:08 DEBUG| [stdout] # Cannot find device
"eth0"
- 18287 03:33:08 DEBUG| [stdout] # Cannot find device
"eth0"
- 18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get
route with nexthop without gw[ OK ]
- 18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping
through nexthop without gw [FAIL]
- 18290 03:33:18 DEBUG| [stdout] not ok 1 selftests:
net: fib_nexthop_nongw.sh # exit=1
- 18291 03:33:18 DEBUG| [stdout] make: Leaving
directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
+ 18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
+ 18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
+ 18275 03:33:07 WARNI| System python is too old, crash
handling disabled
+ 18276 03:33:07 DEBUG| Running 'make run_tests -C net
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
+ 18277 03:33:07 DEBUG| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
+ 18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules
ARCH=x86 -C ../../../.. headers_install
+ 18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
+ 18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
+ 18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
+ 18282 03:33:08 DEBUG| [stdout] TAP version 13
+ 18283 03:33:08 DEBUG| [stdout] 1..1
+ 18284 03:33:08 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
+ 18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type.
+ 18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
+ 18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
+ 18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route
with nexthop without gw[ OK ]
+ 18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through
nexthop without gw [FAIL]
+ 18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net:
fib_nexthop_nongw.sh # exit=1
+ 18291 03:33:18 DEBUG| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
+
+ --
+
+ SRU Justification:
+
+ [Impact]
+
+ * Without Kernel support for the Dummy net driver, it is not possible to
+ successfully run selftests that use it. This includes as per this bug
+ net/fib_nexthop_nongw.sh, but also could potentially include other such
+ as rtnetlink.sh, fib_rule_tests.sh, forwarding/* etc.
+
+ [Fix]
+
+ * Custom patch to enable CONFIG_DUM
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Description changed: + SRU Justification: + + [Impact] + Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support - Thanks, Sumit + + [Test Plan] + + [Where problems could occur] + [Other Info] ** Description changed: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit [Test Plan] + 1. Install and boot kernel + 2. Run basic I/O tests + [Where problems could occur] + + [Other Info] + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support -- 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/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
** Also affects: linux-kvm (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1998244
Title:
kselftest net/fib_nexthop_nongw.sh fails
Status in linux-kvm package in Ubuntu:
New
Status in linux-kvm source package in Jammy:
New
Status in linux-kvm source package in Kinetic:
New
Status in linux-kvm source package in Lunar:
New
Bug description:
18272 03:33:07 DEBUG| Persistent state client._record_indent
now set to 2
18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
18275 03:33:07 WARNI| System python is too old, crash
handling disabled
18276 03:33:07 DEBUG| Running 'make run_tests -C net
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18277 03:33:07 DEBUG| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules
ARCH=x86 -C ../../../.. headers_install
18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18282 03:33:08 DEBUG| [stdout] TAP version 13
18283 03:33:08 DEBUG| [stdout] 1..1
18284 03:33:08 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type.
18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route
with nexthop without gw[ OK ]
18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through
nexthop without gw [FAIL]
18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net:
fib_nexthop_nongw.sh # exit=1
18291 03:33:18 DEBUG| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
--
SRU Justification:
[Impact]
* Without Kernel support for the Dummy net driver, it is not possible
to successfully run selftests that use it. This includes as per this
bug net/fib_nexthop_nongw.sh, but also could potentially include other
such as rtnetlink.sh, fib_rule_tests.sh, forwarding/* etc.
[Fix]
* Custom patch to enable CONFIG_DUMMY=m
[Test Plan]
* Before the fix, the net/fib_nexthop_nongw.sh script will fail in the
specific line which does
$ ip -n h1 link add name eth0 type dummy
Error: Unknown device type.
After the fix it does not fail.
[Where problems could occur]
* The regression can be considered as low, since we are adding
functionality not previously present.
[Other Info]
* There does not seem to be a historical reason for removing it from
linux-kvm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1998244/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001703] Re: Update the NVIDIA drivers 2023/01
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.78.01-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-525 (525.78.01-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #2001703). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. -- Alberto Milone Wed, 04 Jan 2023 16:52:53 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2001703 Title: Update the NVIDIA drivers 2023/01 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Fixed a regression that prevented the G-SYNC/G-SYNC Compatible Visual Indicator from being displayed when running Vulkan X11 applications. - Fixed a bug where usage of VK_KHR_present_id could cause applications to crash with Xid 32 errors. - Fixed excess CPU usage in hybrid graphics configurations where an external display is connected to an NVIDIA discrete GPU and configured as a PRIME Display Offload sink (also known as "Reverse Prime"). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001703] Re: Update the NVIDIA drivers 2023/01
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.78.01-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-525 (525.78.01-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2001703). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. -- Alberto Milone Wed, 04 Jan 2023 16:50:08 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2001703 Title: Update the NVIDIA drivers 2023/01 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Fixed a regression that prevented the G-SYNC/G-SYNC Compatible Visual Indicator from being displayed when running Vulkan X11 applications. - Fixed a bug where usage of VK_KHR_present_id could cause applications to crash with Xid 32 errors. - Fixed excess CPU usage in hybrid graphics configurations where an external display is connected to an NVIDIA discrete GPU and configured as a PRIME Display Offload sink (also known as "Reverse Prime"). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001703] Re: Update the NVIDIA drivers 2023/01
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.78.01-0ubuntu0.22.10.1 --- nvidia-graphics-drivers-525 (525.78.01-0ubuntu0.22.10.1) kinetic; urgency=medium * New upstream release (LP: #2001703). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. -- Alberto Milone Wed, 04 Jan 2023 16:47:46 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2001703 Title: Update the NVIDIA drivers 2023/01 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Fixed a regression that prevented the G-SYNC/G-SYNC Compatible Visual Indicator from being displayed when running Vulkan X11 applications. - Fixed a bug where usage of VK_KHR_present_id could cause applications to crash with Xid 32 errors. - Fixed excess CPU usage in hybrid graphics configurations where an external display is connected to an NVIDIA discrete GPU and configured as a PRIME Display Offload sink (also known as "Reverse Prime"). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003244] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003244 Title: Epson ET-2760 Scanner not recognised Status in linux package in Ubuntu: Confirmed Bug description: xsane 0.999, no devices available simple scan 3.28.0, no scanner available ET-2760 is connected by USB and powered on waiting for commands. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-202-generic 4.15.0-202.213 ProcVersionSignature: Ubuntu 4.15.0-202.213-generic 4.15.18 Uname: Linux 4.15.0-202-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-202-generic. ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1301 F pulseaudio /dev/snd/controlC1: david 1301 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1458a102,00100302' Controls : 56 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Date: Wed Jan 18 11:04:47 2023 HibernationDevice: RESUME=UUID=2f2eab9a-deae-4432-bfd7-fa2308bd0e30 InstallationDate: Installed on 2018-06-02 (1690 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-202-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-202-generic N/A linux-backports-modules-4.15.0-202-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2020-10-04 (835 days ago) dmi.bios.date: 04/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002206] Re: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg
Uploading updated dmesg. External monitor was connected to USB-C at 47s, system sleep at 58s, monitor unplugged at 64s, system wake-up at 68s. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002206/+attachment/5642326/+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/2002206 Title: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: After disconnecting an external monitor from a Thunderbolt 4 (USB-C) port *while the system is asleep*, after wake-up the system keeps on randomly freezing for 1-2 seconds. Every freeze is accompanied by an "Enabling HDA controller" kernel message: [54984.259832] nvidia :01:00.0: Enabling HDA controller [55008.355784] nvidia :01:00.0: Enabling HDA controller [55044.771722] nvidia :01:00.0: Enabling HDA controller [55069.859682] nvidia :01:00.0: Enabling HDA controller [55096.547622] nvidia :01:00.0: Enabling HDA controller [55122.243581] nvidia :01:00.0: Enabling HDA controller [55146.339543] nvidia :01:00.0: Enabling HDA controller [55168.579505] nvidia :01:00.0: Enabling HDA controller [55199.491437] nvidia :01:00.0: Enabling HDA controller Rebooting or restarting Xorg "fixes" the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: socwatch2_15 vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: me 2469 F pulseaudio /dev/snd/controlC0: me 2469 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 7 12:19:39 2023 InstallationDate: Installed on 2022-08-31 (128 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04f2:b74f Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 06cb:00f9 Synaptics, Inc. Bus 001 Device 007: ID 8087:0033 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 21DE001QMH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro pci=nommconf PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2022 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N3JET28W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21DE001QMH dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN3JET28W(1.12):bd10/18/2022:br1.12:efr1.8:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5: dmi.product.family: ThinkPad X1 Extreme Gen 5 dmi.product.name: 21DE001QMH dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5 dmi.product.version: ThinkPad X1 Extreme Gen 5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003244] [NEW] Epson ET-2760 Scanner not recognised
Public bug reported: xsane 0.999, no devices available simple scan 3.28.0, no scanner available ET-2760 is connected by USB and powered on waiting for commands. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-202-generic 4.15.0-202.213 ProcVersionSignature: Ubuntu 4.15.0-202.213-generic 4.15.18 Uname: Linux 4.15.0-202-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-202-generic. ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1301 F pulseaudio /dev/snd/controlC1: david 1301 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1458a102,00100302' Controls : 56 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Date: Wed Jan 18 11:04:47 2023 HibernationDevice: RESUME=UUID=2f2eab9a-deae-4432-bfd7-fa2308bd0e30 InstallationDate: Installed on 2018-06-02 (1690 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-202-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-202-generic N/A linux-backports-modules-4.15.0-202-generic N/A linux-firmware 1.173.21 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2020-10-04 (835 days ago) dmi.bios.date: 04/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/2003244 Title: Epson ET-2760 Scanner not recognised Status in linux package in Ubuntu: New Bug description: xsane 0.999, no devices available simple scan 3.28.0, no scanner available ET-2760 is connected by USB and powered on waiting for commands. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-202-generic 4.15.0-202.213 ProcVersionSignature: Ubuntu 4.15.0-202.213-generic 4.15.18 Uname: Linux 4.15.0-202-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-202-generic. ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1301 F pulseaudio /dev/snd/controlC1: david 1301 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1458a102,00100302' Controls : 56 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Date: Wed Jan 18 11:04:47 2023 HibernationDevice: RESUME=UUID=2f2eab9a-deae-4432-bfd7-fa2308bd0e30 InstallationDate: Installed on 2018-06-02 (1690 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-202-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-202-generic N/A linux-backports-modules-4.15.0-202-generic N/A linux-firmware
[Kernel-packages] [Bug 2002206] Re: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg
Removing "pci=nommconf" results in "Enabling HDA controller" no longer being logged. However, the freezing is still there. Is there any kernel debug flag that I can set to help debug this further? -- 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/2002206 Title: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: After disconnecting an external monitor from a Thunderbolt 4 (USB-C) port *while the system is asleep*, after wake-up the system keeps on randomly freezing for 1-2 seconds. Every freeze is accompanied by an "Enabling HDA controller" kernel message: [54984.259832] nvidia :01:00.0: Enabling HDA controller [55008.355784] nvidia :01:00.0: Enabling HDA controller [55044.771722] nvidia :01:00.0: Enabling HDA controller [55069.859682] nvidia :01:00.0: Enabling HDA controller [55096.547622] nvidia :01:00.0: Enabling HDA controller [55122.243581] nvidia :01:00.0: Enabling HDA controller [55146.339543] nvidia :01:00.0: Enabling HDA controller [55168.579505] nvidia :01:00.0: Enabling HDA controller [55199.491437] nvidia :01:00.0: Enabling HDA controller Rebooting or restarting Xorg "fixes" the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: socwatch2_15 vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: me 2469 F pulseaudio /dev/snd/controlC0: me 2469 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 7 12:19:39 2023 InstallationDate: Installed on 2022-08-31 (128 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04f2:b74f Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 06cb:00f9 Synaptics, Inc. Bus 001 Device 007: ID 8087:0033 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 21DE001QMH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro pci=nommconf PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2022 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N3JET28W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21DE001QMH dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN3JET28W(1.12):bd10/18/2022:br1.12:efr1.8:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5: dmi.product.family: ThinkPad X1 Extreme Gen 5 dmi.product.name: 21DE001QMH dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5 dmi.product.version: ThinkPad X1 Extreme Gen 5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
I have blacklisted this now using: sudo vim /etc/modprobe.d/blacklist-nouveau.conf adding: blacklist nouveau options nouveau modeset=0 -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/2003031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install
Hello Kai-Chuan, or anyone else affected, Accepted alsa-ucm-conf into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2001896 Title: sof-hda-dsp internal mic default off after fresh install Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Device with sof-hda-dsp sound card has internal mic off after fresh install [Test Plan] On the platform with sofhdadsp sound card 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal mic should be on by default [Where problems could occur] The change takes place on platform with sof-hda-dsp sound card, and it only be executed during boot sequence, it won't impact the stored state. However, it will change user default expectation after fresh installation. [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/259 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
Hello Kai-Heng, or anyone else affected, Accepted alsa-ucm-conf into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001896] Re: sof-hda-dsp internal mic default off after fresh install
Hello Kai-Chuan, or anyone else affected, Accepted alsa-ucm-conf into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2001896 Title: sof-hda-dsp internal mic default off after fresh install Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Device with sof-hda-dsp sound card has internal mic off after fresh install [Test Plan] On the platform with sofhdadsp sound card 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal mic should be on by default [Where problems could occur] The change takes place on platform with sof-hda-dsp sound card, and it only be executed during boot sequence, it won't impact the stored state. However, it will change user default expectation after fresh installation. [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/259 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2001896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
Hello Kai-Heng, or anyone else affected, Accepted alsa-ucm-conf into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
I'm seeing this as well. Some information that may help. I found the problem with 5.4.0-137. I found that when looking at tcpdump on the guest and the bridge I can see ARP requests on both interfaces. On the guest I can see it responding to the ARP request, however I don't see the ARP response on the bridge interface. I booted back to 5.4.0-126 with Xen and everything is fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Summary changed: - [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support + [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support -- 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/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888018] Re: nvme0 does not resume from standby
Happens the same to my laptop: Ubuntu 22.04, Samsung NVME AMD 5700U... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1888018 Title: nvme0 does not resume from standby Status in linux-signed package in Ubuntu: Confirmed Bug description: This new laptop has a Samsung NVME SSD. The SSD (or the SSD controller) sometimes fails to resume from standby. The probability of this goes up with the time the laptop is on standby & I have to save all files when I put the laptop on standby at the end of the day as most likely it won't resume successfully. When I try & resume, normally the laptop appears to resume, I can unlock the screen but there's no disk access. Any programs that were in memory when I suspended the laptop are OK but everything else fails with an I/O error. The syslog includes entries like the following. nvme nvme0: Device not ready: aborting reset nvme nvme0: Removing after probe failure status: -19 Sometimes the first of these is repeated. Here is the relevant line from lspci. 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ uname -a Linux orion 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1888018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888018] Re: nvme0 does not resume from standby
$lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ uname -a Linux ciampix-lap2022 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1888018 Title: nvme0 does not resume from standby Status in linux-signed package in Ubuntu: Confirmed Bug description: This new laptop has a Samsung NVME SSD. The SSD (or the SSD controller) sometimes fails to resume from standby. The probability of this goes up with the time the laptop is on standby & I have to save all files when I put the laptop on standby at the end of the day as most likely it won't resume successfully. When I try & resume, normally the laptop appears to resume, I can unlock the screen but there's no disk access. Any programs that were in memory when I suspended the laptop are OK but everything else fails with an I/O error. The syslog includes entries like the following. nvme nvme0: Device not ready: aborting reset nvme nvme0: Removing after probe failure status: -19 Sometimes the first of these is repeated. Here is the relevant line from lspci. 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ uname -a Linux orion 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1888018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888018] Re: nvme0 does not resume from standby
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1888018 Title: nvme0 does not resume from standby Status in linux-signed package in Ubuntu: Confirmed Bug description: This new laptop has a Samsung NVME SSD. The SSD (or the SSD controller) sometimes fails to resume from standby. The probability of this goes up with the time the laptop is on standby & I have to save all files when I put the laptop on standby at the end of the day as most likely it won't resume successfully. When I try & resume, normally the laptop appears to resume, I can unlock the screen but there's no disk access. Any programs that were in memory when I suspended the laptop are OK but everything else fails with an I/O error. The syslog includes entries like the following. nvme nvme0: Device not ready: aborting reset nvme nvme0: Removing after probe failure status: -19 Sometimes the first of these is repeated. Here is the relevant line from lspci. 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ uname -a Linux orion 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1888018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
IIRC I tried to install it from source back then, but had missing build dependencies (or versions) which were not in the package repositories. I could be wrong, though. -- 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/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
Hmm, currently when connecting it via blueman it automatically connects with the last used profile. I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it seems to have A2DP there. But as soon as I change my Mic Input Device to my headphones it changes to "Headset Head Unit (HSP/HFP codec mSBC)". If try to change the profile back to the A2DP sink my input device is also switched back to my internal Laptop Mic. I'm not sure anymore if the A2DP sink was always there or if came back with a recent OS update (Linux Mint 21.1) - I'm also not sure if bluez 5.65 can fix this behavior. Is there a more or less easy way I can test this on my machine? Maybe just clone it from the GitHub repo, checkout 5.65, compile and install it? Or do I need additional steps? -- 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/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976227] Re: No sound on asus M7400QC
I have exactly the same problem. The "knock knock" sound on Windows occurs when you come back to Windows after having boot on Linux. If you reboot twice on Windows, the sound go back to normal. -- 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/1976227 Title: No sound on asus M7400QC Status in linux package in Ubuntu: Confirmed Bug description: I have an ASUS M7400QC with dualboot Ubuntu 22 and Windows 11, and sometimes there is only a knock-knock sound on Windows and no sound at all on Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nghianv1615 F pulseaudio /dev/snd/pcmC1D0p: nghianv1615 F...m pulseaudio /dev/snd/controlC0: nghianv1615 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 30 15:11:03 2022 InstallationDate: Installed on 2022-05-30 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M7400QC_M7400QC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=0851dac0-250a-432f-b067-dc4590b9730b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M7400QC.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M7400QC 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.:bvrM7400QC.307:bd03/07/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopM7400QC_M7400QC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM7400QC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop M7400QC_M7400QC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => ChengEn, Du (chengendu) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => ChengEn, Du (chengendu) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => ChengEn, Du (chengendu) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => ChengEn, Du (chengendu) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => ChengEn, Du (chengendu) ** Tags added: bionic focal jammy kinetic lunar sts -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux source package in Lunar: In Progress Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19
fixed the version as -1ubuntu6~22.04.1 because it can't be bigger than in newer releases ** Changed in: zfs-linux (Ubuntu) Status: New => Incomplete ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: zfs-linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2003174 Title: zfs-dkms fails to build on jammy with linux 5.19 Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Jammy: In Progress Bug description: [Impact] zfs-dkms fails to build on jammy with the latest linux hwe 5.19: *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 [Test case] $ sudo apt install zfs-dkms [Fix] The most reliable fix is probably to move to the same version that is available in kinetic, since there's no significant ABI change in this way we should be able to support both 5.15 and 5.19 kernels. [Regression potential] We may experience zfs regressions if there's a format/ABI incompatibility with volumes created with the previous version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003222] [NEW] Subiquity crash on Lenovo X13s because UEFI variables not supported
Public bug reported:
The following crash occurs in curtin.
The device does not provide access to UEFI variables at runtime.
The error from efibootmgr should only result in a warning and not stop
the installation process.
finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL:
installing grub to target devices
finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL:
configuring target system bootloader
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL:
curtin command curthooks
Traceback (most recent call last):
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/curthooks.py",
line 1903, in curthooks
builtin_curthooks(cfg, target, state)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/curthooks.py",
line 1868, in builtin_curthooks
setup_grub(cfg, target, osfamily=osfamily,
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/curthooks.py",
line 818, in setup_grub
efi_orig_output = util.get_efibootmgr(target)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/util.py", line 967, in
get_efibootmgr
stdout, _ = in_chroot.subp(['efibootmgr', '-v'], capture=True)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/util.py", line 787, in
subp
return subp(*args, **kwargs)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/util.py", line 275, in
subp
return _subp(*args, **kwargs)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/util.py", line 139, in
_subp
raise ProcessExecutionError(stdout=out, stderr=err,
curtin.util.ProcessExecutionError: Unexpected error while running
command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/target',
'efibootmgr', '-v']
Exit code: 2
Reason: -
Stdout: ''
Stderr: EFI variables are not supported on this system.
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/target',
'efibootmgr', '-v']
Exit code: 2
Reason: -
Stdout: ''
Stderr: EFI variables are not supported on this system.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "log-x13s-20230118-151800.tgz"
https://bugs.launchpad.net/bugs/2003222/+attachment/5642257/+files/log-x13s-20230118-151800.tgz
** Package changed: linux-riscv (Ubuntu) => subiquity (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2003222
Title:
Subiquity crash on Lenovo X13s because UEFI variables not supported
Status in subiquity package in Ubuntu:
New
Bug description:
The following crash occurs in curtin.
The device does not provide access to UEFI variables at runtime.
The error from efibootmgr should only result in a warning and not stop
the installation process.
finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL:
installing grub to target devices
finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL:
configuring target system bootloader
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL:
curtin command curthooks
Traceback (most recent call last):
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/curthooks.py",
line 1903, in curthooks
builtin_curthooks(cfg, target, state)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/curthooks.py",
line 1868, in builtin_curthooks
setup_grub(cfg, target, osfamily=osfamily,
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/commands/curthooks.py",
line 818, in setup_grub
efi_orig_output = util.get_efibootmgr(target)
File
"/snap/subiquity/4236/lib/python3.8/site-packages/curtin/util.py", line 967, in
get_efibootmgr
stdout, _ = in_ch
[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993315 Title: md: Replace snprintf with scnprintf Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of characters generated from the given input, which could cause the expression “200 – len” to wrap around to a large positive number. Fix this by using scnprintf() instead, which returns the actual number of characters written into the buffer. [ 1513.267938] [ cut here ] [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 vsnprintf+0x2c8/0x510 [ 1513.267944] Modules linked in: [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure #90~18.04.1-Ubuntu [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510 <-snip-> [ 1513.267982] Call Trace: [ 1513.267986] snprintf+0x45/0x70 [ 1513.267990] ? disk_name+0x71/0xa0 [ 1513.267993] dump_zones+0x114/0x240 [raid0] [ 1513.267996] ? _cond_resched+0x19/0x40 [ 1513.267998] raid0_run+0x19e/0x270 [raid0] [ 1513.268000] md_run+0x5e0/0xc50 [ 1513.268003] ? security_capable+0x3f/0x60 [ 1513.268005] do_md_run+0x19/0x110 [ 1513.268006] md_ioctl+0x195e/0x1f90 [ 1513.268007] blkdev_ioctl+0x91f/0x9f0 [ 1513.268010] block_ioctl+0x3d/0x50 [ 1513.268012] do_vfs_ioctl+0xa9/0x640 [ 1513.268014] ? __fput+0x162/0x260 [ 1513.268016] ksys_ioctl+0x75/0x80 [ 1513.268017] __x64_sys_ioctl+0x1a/0x20 [ 1513.268019] do_syscall_64+0x5e/0x200 [ 1513.268021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43 [Where things could go wrong] This seems unlikely to cause a regression [Other Info] SF: #00346036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003203] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003203 Title: Bluetooth dont work Status in linux package in Ubuntu: Confirmed Bug description: На ноутбуке Honor magicbook 14 не работает блютуз. Когда я включаю его, ничего не происходит. Также замечу, что присутсвует проблема с Wifi, поскольку подключается не ко всем точкам доступа (На некоторых точках доступа происходит подключение, но интернет отсутсвует). Предполагаю, что это связано, поскольку модуль в ноутбуке Honor совмещенный Na noutbuke Honor magicbook 14 ne rabotayet blyutuz. Kogda ya vklyuchayu yego, nichego ne proiskhodit. Takzhe zamechu, chto prisutsvuyet problema s Wifi, poskol'ku podklyuchayetsya ne ko vsem tochkam dostupa (Na nekotorykh tochkakh dostupa proiskhodit podklyucheniye, no internet otsutsvuyet). Predpolagayu, chto eto svyazano, poskol'ku modul' v noutbuke Honor sovmeshchennyy Bluetooth does not work on Honor magicbook 14 laptop. When I turn it on, nothing happens. I also note that there is a problem with Wifi, because it does not connect to all access points (Some access points connect, but there is no Internet). I assume that this is due, since the module in the Honor laptop is combined ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 16:26:50 2023 InstallationDate: Installed on 2023-01-07 (10 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HONOR NMH-WCX9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=0c859c0d-59a0-4885-af2a-ee0fb7cf0f9d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2021 dmi.bios.release: 1.8 dmi.bios.vendor: HONOR dmi.bios.version: 1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NMH-WCX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1060 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1060 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHONOR:bvr1.08:bd12/29/2021:br1.8:efr1.8:svnHONOR:pnNMH-WCX9:pvrM1060:rvnHONOR:rnNMH-WCX9-PCB:rvrM1060:cvnHONOR:ct10:cvrM1060:skuC233: dmi.product.family: HONOR MagicBook dmi.product.name: NMH-WCX9 dmi.product.sku: C233 dmi.product.version: M1060 dmi.sys.vendor: HONOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003203] Re: Bluetooth dont work
This device 0489:e0e1 is not supported by Linux kernel yet. A patch to drivers/bluetooth/btusb.c is needed to add this specific device. -- 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/2003203 Title: Bluetooth dont work Status in linux package in Ubuntu: New Bug description: На ноутбуке Honor magicbook 14 не работает блютуз. Когда я включаю его, ничего не происходит. Также замечу, что присутсвует проблема с Wifi, поскольку подключается не ко всем точкам доступа (На некоторых точках доступа происходит подключение, но интернет отсутсвует). Предполагаю, что это связано, поскольку модуль в ноутбуке Honor совмещенный Na noutbuke Honor magicbook 14 ne rabotayet blyutuz. Kogda ya vklyuchayu yego, nichego ne proiskhodit. Takzhe zamechu, chto prisutsvuyet problema s Wifi, poskol'ku podklyuchayetsya ne ko vsem tochkam dostupa (Na nekotorykh tochkakh dostupa proiskhodit podklyucheniye, no internet otsutsvuyet). Predpolagayu, chto eto svyazano, poskol'ku modul' v noutbuke Honor sovmeshchennyy Bluetooth does not work on Honor magicbook 14 laptop. When I turn it on, nothing happens. I also note that there is a problem with Wifi, because it does not connect to all access points (Some access points connect, but there is no Internet). I assume that this is due, since the module in the Honor laptop is combined ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 16:26:50 2023 InstallationDate: Installed on 2023-01-07 (10 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HONOR NMH-WCX9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=0c859c0d-59a0-4885-af2a-ee0fb7cf0f9d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2021 dmi.bios.release: 1.8 dmi.bios.vendor: HONOR dmi.bios.version: 1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NMH-WCX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1060 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1060 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHONOR:bvr1.08:bd12/29/2021:br1.8:efr1.8:svnHONOR:pnNMH-WCX9:pvrM1060:rvnHONOR:rnNMH-WCX9-PCB:rvrM1060:cvnHONOR:ct10:cvrM1060:skuC233: dmi.product.family: HONOR MagicBook dmi.product.name: NMH-WCX9 dmi.product.sku: C233 dmi.product.version: M1060 dmi.sys.vendor: HONOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003203] [NEW] Bluetooth dont work
Public bug reported: На ноутбуке Honor magicbook 14 не работает блютуз. Когда я включаю его, ничего не происходит. Также замечу, что присутсвует проблема с Wifi, поскольку подключается не ко всем точкам доступа (На некоторых точках доступа происходит подключение, но интернет отсутсвует). Предполагаю, что это связано, поскольку модуль в ноутбуке Honor совмещенный Na noutbuke Honor magicbook 14 ne rabotayet blyutuz. Kogda ya vklyuchayu yego, nichego ne proiskhodit. Takzhe zamechu, chto prisutsvuyet problema s Wifi, poskol'ku podklyuchayetsya ne ko vsem tochkam dostupa (Na nekotorykh tochkakh dostupa proiskhodit podklyucheniye, no internet otsutsvuyet). Predpolagayu, chto eto svyazano, poskol'ku modul' v noutbuke Honor sovmeshchennyy Bluetooth does not work on Honor magicbook 14 laptop. When I turn it on, nothing happens. I also note that there is a problem with Wifi, because it does not connect to all access points (Some access points connect, but there is no Internet). I assume that this is due, since the module in the Honor laptop is combined ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 16:26:50 2023 InstallationDate: Installed on 2023-01-07 (10 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HONOR NMH-WCX9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=0c859c0d-59a0-4885-af2a-ee0fb7cf0f9d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2021 dmi.bios.release: 1.8 dmi.bios.vendor: HONOR dmi.bios.version: 1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NMH-WCX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1060 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1060 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHONOR:bvr1.08:bd12/29/2021:br1.8:efr1.8:svnHONOR:pnNMH-WCX9:pvrM1060:rvnHONOR:rnNMH-WCX9-PCB:rvrM1060:cvnHONOR:ct10:cvrM1060:skuC233: dmi.product.family: HONOR MagicBook dmi.product.name: NMH-WCX9 dmi.product.sku: C233 dmi.product.version: M1060 dmi.sys.vendor: HONOR ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003203 Title: Bluetooth dont work Status in linux package in Ubuntu: New Bug description: На ноутбуке Honor magicbook 14 не работает блютуз. Когда я включаю его, ничего не происходит. Также замечу, что присутсвует проблема с Wifi, поскольку подключается не ко всем точкам доступа (На некоторых точках доступа происходит подключение, но интернет отсутсвует). Предполагаю, что это связано, поскольку модуль в ноутбуке Honor совмещенный Na noutbuke Honor magicbook 14 ne rabotayet blyutuz. Kogda ya vklyuchayu yego, nichego ne proiskhodit. Takzhe zamechu, chto prisutsvuyet problema s Wifi, poskol'ku podklyuchayetsya ne ko vsem tochkam dostupa (Na nekotorykh tochkakh dostupa proiskhodit podklyucheniye, no internet otsutsvuyet). Predpolagayu, chto eto svyazano, poskol'ku modul' v noutbuke Honor sovmeshchennyy Bluetooth does not work on Honor magicbook 14 laptop. When I turn it on, nothing happens. I also note that there is a problem with Wifi, because it does not connect to all access points (Some access points connect, but there is no Internet). I assume that this is due, since the module in the Honor laptop is combined ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 16:26:50 2023 InstallationDate: Installed on 2023-01-07 (10 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HONOR NMH-WCX9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic r
[Kernel-packages] [Bug 1956821] Re: System hangs on reboot and shutdown
And I with 5.14.0-1056-oem Several process cannot get stopped including systemd -- also sd_[something] I get an injunction to do: echo 0 > /proc/sys/kernel/hung_task_timeout_secs but I understand it is only to silence the warning... -- 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/1956821 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic, the system cannot be powered down or rebooted, just hangs indefinitely. A screenshot with the final screen is shown here: https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff I can restore the previous behavior (i.e. a correct shutdown) with choosing the previous kernel in the grub menu on boot. Is there anything I can do to provide more information and debug this further? My system information: Description: Ubuntu 21.10 Release: 21.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petr 1146 F pulseaudio /dev/snd/controlC0: petr 1146 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-07 (62 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgxubuntu-root ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 ACN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996092] Re: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204, 4.15.0-194.205, 4.15.0-196.207)
Thank's Kai-Heng Feng. I know that but if I upgrade ubuntu it could brick MacBook boot and i will never boot again (without hardware repair). But your proposal give me an idea: kernel upgrade without system upgrade. So, I look for and install newer kernel and it works !!! (sudo dpkg -i *.deb) NOTE: 5.4.0-135.152 kernel is used in ubuntu 20.04 http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-5.4.0-135_5.4.0-135.152_all.deb http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-5.4.0-135-generic_5.4.0-135.152_amd64.deb http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-modules-5.4.0-135-generic_5.4.0-135.152_amd64.deb http://security.ubuntu.com/ubuntu/pool/main/l/linux-signed/linux-image-5.4.0-135-generic_5.4.0-135.152_amd64.deb http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-modules-extra-5.4.0-135-generic_5.4.0-135.152_amd64.deb ALTHOUGH, MY POST wanted to report that issue with the latest kernel patches in linux-image-4.15.0-xxx kernel series and if you should consider some patch regression about that. -- 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/1996092 Title: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) Status in linux package in Ubuntu: Confirmed Bug description: I have old MacBook with broken main Graphic Controller (a well-known hardware issue https://discussions.apple.com/thread/251049873 ). So I switch to use Integrated Graphics Controller. I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot (freeze during boot). I looked for latest updated packages and I found: linux-image-4.15.0-192-generic 4.15.0-192.203 amd64 => linux-image-4.15.0-193-generic 4.15.0-193.204 amd64 So, MacBook boots linux-image-4.15.0-192-generic correctly, but it doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205, 4.15.0-196.207) I could not find which change is included in newer kernels that did this issue. How could I support about this issue? PD: Added bellow some additional information and attached 'lspci-vnvn.log' file $ sudo lshw macbookpro description: Notebook product: MacBookPro8,2 (System SKU#) vendor: Apple Inc. ... lspci-vnvn.log 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [106b:00dc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
Rafael, I can't seem to find a way to reproduce the bug with the headphones I do have. Can you outline the steps (and the model of headphones) you are using? -- 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/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003181] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003181 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Just removed my W10 OS and installed Ubuntu, but touchpas is not working at all. I hva to use a mouse. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vento 6868 F pulseaudio /dev/snd/controlC1: vento 6868 F pulseaudio /dev/snd/controlC0: vento 6868 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 11:08:48 2023 InstallationDate: Installed on 2023-01-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Laptop 15s-eq1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=fd36a505-829c-4c29-a762-f4e5a6ac6d53 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2021 dmi.bios.release: 15.42 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.20 dmi.modalias: dmi:bvnAMI:bvrF.42:bd05/13/2021:br15.42:efr37.20:svnHP:pnHPLaptop15s-eq1xxx:pvr:rvnHP:rn8707:rvr37.20:cvnHP:ct10:cvrChassisVersion:sku1E6T2EA#ABF: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq1xxx dmi.product.sku: 1E6T2EA#ABF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003181] [NEW] Touchpad not detected
Public bug reported: Just removed my W10 OS and installed Ubuntu, but touchpas is not working at all. I hva to use a mouse. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vento 6868 F pulseaudio /dev/snd/controlC1: vento 6868 F pulseaudio /dev/snd/controlC0: vento 6868 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 11:08:48 2023 InstallationDate: Installed on 2023-01-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Laptop 15s-eq1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=fd36a505-829c-4c29-a762-f4e5a6ac6d53 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2021 dmi.bios.release: 15.42 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.20 dmi.modalias: dmi:bvnAMI:bvrF.42:bd05/13/2021:br15.42:efr37.20:svnHP:pnHPLaptop15s-eq1xxx:pvr:rvnHP:rn8707:rvr37.20:cvnHP:ct10:cvrChassisVersion:sku1E6T2EA#ABF: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq1xxx dmi.product.sku: 1E6T2EA#ABF dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003181 Title: Touchpad not detected Status in linux package in Ubuntu: New Bug description: Just removed my W10 OS and installed Ubuntu, but touchpas is not working at all. I hva to use a mouse. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vento 6868 F pulseaudio /dev/snd/controlC1: vento 6868 F pulseaudio /dev/snd/controlC0: vento 6868 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 11:08:48 2023 InstallationDate: Installed on 2023-01-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Laptop 15s-eq1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=fd36a505-829c-4c29-a762-f4e5a6ac6d53 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2021 dmi.bios.release: 15.42 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.20 dmi.modalias: dmi:bvnAMI:bvrF.42:bd05/13/2021:br15.42:efr37.20:svnHP:pnHPLaptop15s-eq1xxx:pvr:rvnHP:rn8707:rvr37.20:cvnHP:ct10:cvrChassisVersion:sku1E6T2EA#ABF: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq1xxx dmi.product.sku: 1E6T2EA#ABF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1806488 Title: Support non-strict iommu mode on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Released Status in linux-aws source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: Invalid Status in linux source package in Jammy: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Fix Committed Bug description: [Impact] The Intel IOMMU driver provides an option for strict mode. When disabled, batching of IOTLB flush operations is permitted, allowing the user to trade-off isolation for improved performance. Ubuntu's kernel currently lacks a parity for this feature for ARM. There's a significant performance gain to be had by removing the need to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25% performance gain w/ fio reads on a single NVMe device. This mode of operation is available for x86 via the "intel_iommu=strict" parameter. Upstream now exposes an equivalent feature for ARM platforms via the "iommu.strict=[0|1]" parameter, while retaining the default strict-enabled mode. [Test Case] Run fio with the following config before and after applying the patches and collection IOPS count. Run again after applying the patches. Finally, run a 3rd time after adding iommu.strict=0 to the kernel commandline. Performance should not regress after the update. Performance should further improve after adding iommu.strict=0 - but if it doesn't for some reason, that is not a regression. $ cat fio.rc [global] rw=read direct=1 ioengine=libaio iodepth=2048 numjobs=10 bs=4k group_reporting=1 group_reporting=1 cpumask=0xff runtime=100 loops = 1 [job1] filename=/dev/nvme0n1 [Fix] 44f6876a00e83 iommu/arm-smmu: Support non-strict mode b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode 9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode 68a6efe86f6a1 iommu: Add "iommu.strict" command line option 2da274cdf998a iommu/dma: Add support for non-strict mode 07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook 85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap() [Regression Risk] Most of these patches are specific to ARM, and have been regression tested on both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)" 2 patches do touch arch-indep code however: > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option Adds a new command line option and sets an attribute that iommu drivers can optionally react to. Doesn't change default behavior. > 2da274cdf998a iommu/dma: Add support for non-strict mode This driver is only built for arm64 and ppc64el (determined by looking at the build logs). Most of this patch only changes behavior in the non-default (and new) iommu.strict=0 case. The exception, which is called out in the commit message, is this hunk: - WARN_ON(iommu_unmap(domain, dma_addr, size) != size); + WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size); + if (!cookie->fq_domain) + iommu_tlb_sync(domain); In the default case, where fq_domain will be NULl, we are now factoring iommu_unmap() into: iommu_unmap_fast() iommu_tlb_sync() Looking at the source to iommu_unmap() confirms that this is functionally equivalent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kern
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be 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-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic
[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991366 Title: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Some Dell laptops where booting with Thunderbolt/USB4 devices connected the BIOS leaves some of the PCIe devices unconfigured. The kernel message shows "No bus number available for hot-added bridge". The connected devices can't be found. [Fix] Current linux PCI distribute the "spare" resources between hotplug ports on hot-add but have not done that upon the initial scan. The patches make the initial root bus scan path to do the same. The additional patches are just a small cleanups that can be applied separately too. [Test] 1. Power on the machine with Thunderbolt/USB4 devices connected. 2. Check the kernel message to see if "No bus number available for hot-added bridge" shows up or not. 3. Check if the Thunderbolt/USB4 devices works or not. [Where problems could occur] The patches only apply the same procedures on initial root bus scan which was not done. If the BIOS configures the PCI correctly, everything is OK. It only takes effect for the BIOS w/ unconfigured PCIe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991608 Title: TEE Support for CCP driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missing support for of AMD Secure Processor device for PCI ID 0x14CA. [Fix] A patch is being proposed in upstream and CC-ed stable. [Test Case] Without a proper fix, following error appears in dmesg: ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed [Where problems could occur] This adds a new driver data entry to support ccp device that provides both sev and tee feature at the same time. [Other Info] While this is proposed to stable 5.15+, all kernels >= 5.15 are nominated for fix. == original bug description == Client and datacenter Zen4 SOC same PCI-ID but offer different functionality from the PSP. Genoa offers SEV, Client part offers TEE. This patch fixes an ERR level message and CCP driver functionality not working. ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed https://lore.kernel.org/linux- crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991974] Re: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1991974 Title: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] AMD Yellow Carp system hang on HDMI plug in/out over dock station. [Fix] 5 patches from mainline kernel v5.16 to be backported. [Test Case] Plug and unplug HDMI cable connected external monitor on a docking station connected to HP Lockheed platform to try trigger system hang. [Where problems could occur] This series tries to address null state of MST link encoder, and no know fix commits for them ever since till current mainline HEAD. [Other Info] While this is already available in v5.16 kernel and on, only 5.15 and oem-5.14 are nominated for fix. == original bug description == In order to resolve system hang during docking scenario with HDMI plug in/out, these patches are needed into hwe-5.15. v5.16 43dc2ad5 drm/amd/display: Fix MST link encoder availability check e3ab29aa drm/amd/display: Fix for link encoder access for MST 7fb52632 drm/amd/display: FEC configuration for dpia links ed0ffb5d drm/amd/display: FEC configuration for dpia links in MST mode c9beecc5 drm/amd/display: Add work around for tunneled MST To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993315 Title: md: Replace snprintf with scnprintf Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of characters generated from the given input, which could cause the expression “200 – len” to wrap around to a large positive number. Fix this by using scnprintf() instead, which returns the actual number of characters written into the buffer. [ 1513.267938] [ cut here ] [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 vsnprintf+0x2c8/0x510 [ 1513.267944] Modules linked in: [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure #90~18.04.1-Ubuntu [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510 <-snip-> [ 1513.267982] Call Trace: [ 1513.267986] snprintf+0x45/0x70 [ 1513.267990] ? disk_name+0x71/0xa0 [ 1513.267993] dump_zones+0x114/0x240 [raid0] [ 1513.267996] ? _cond_resched+0x19/0x40 [ 1513.267998] raid0_run+0x19e/0x270 [raid0] [ 1513.268000] md_run+0x5e0/0xc50 [ 1513.268003] ? security_capable+0x3f/0x60 [ 1513.268005] do_md_run+0x19/0x110 [ 1513.268006] md_ioctl+0x195e/0x1f90 [ 1513.268007] blkdev_ioctl+0x91f/0x9f0 [ 1513.268010] block_ioctl+0x3d/0x50 [ 1513.268012] do_vfs_ioctl+0xa9/0x640 [ 1513.268014] ? __fput+0x162/0x260 [ 1513.268016] ksys_ioctl+0x75/0x80 [ 1513.268017] __x64_sys_ioctl+0x1a/0x20 [ 1513.268019] do_syscall_64+0x5e/0x200 [ 1513.268021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43 [Where things could go wrong] This seems unlikely to cause a regression [Other Info] SF: #00346036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
This bug is awaiting verification that the linux-aws/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Confirmed Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19
debdiff in attach (that doesn't change anything, it's basically a resync of the same version in kinetic, recompiled with the jammy toolchain). With this applied I was able to successfully run ubuntu_zfs_smoke_test and ubuntu_zfs_stress both on 5.15 and 5.19. ** Patch added: "jammy-zfs-dkms-resync-with-kinetic.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+attachment/5642192/+files/jammy-zfs-dkms-resync-with-kinetic.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2003174 Title: zfs-dkms fails to build on jammy with linux 5.19 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] zfs-dkms fails to build on jammy with the latest linux hwe 5.19: *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 [Test case] $ sudo apt install zfs-dkms [Fix] The most reliable fix is probably to move to the same version that is available in kinetic, since there's no significant ABI change in this way we should be able to support both 5.15 and 5.19 kernels. [Regression potential] We may experience zfs regressions if there's a format/ABI incompatibility with volumes created with the previous version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003174] [NEW] zfs-dkms fails to build on jammy with linux 5.19
Public bug reported: [Impact] zfs-dkms fails to build on jammy with the latest linux hwe 5.19: *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 [Test case] $ sudo apt install zfs-dkms [Fix] The most reliable fix is probably to move to the same version that is available in kinetic, since there's no significant ABI change in this way we should be able to support both 5.15 and 5.19 kernels. [Regression potential] We may experience zfs regressions if there's a format/ABI incompatibility with volumes created with the previous version. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2003174 Title: zfs-dkms fails to build on jammy with linux 5.19 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] zfs-dkms fails to build on jammy with the latest linux hwe 5.19: *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 [Test case] $ sudo apt install zfs-dkms [Fix] The most reliable fix is probably to move to the same version that is available in kinetic, since there's no significant ABI change in this way we should be able to support both 5.15 and 5.19 kernels. [Regression potential] We may experience zfs regressions if there's a format/ABI incompatibility with volumes created with the previous version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
