[Kernel-packages] [Bug 2002381] Re: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle
This was requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view ** Changed in: linux-oracle (Ubuntu) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2002381 Title: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Focal: In Progress Bug description: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2002381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002381] Re: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle
LP #1925421 is the main arm64 enablement bug - this is just a follow-up -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2002381 Title: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Focal: In Progress Bug description: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2002381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002349] Re: Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic
The low screen resolution is because there is no graphics driver installed (properly). It looks like part of the nvidia-510 driver got partially(?) upgraded yesterday: 510.47.03-0ubuntu0.20.04.1 -> 510.108.03-0ubuntu0.20.04.1 but I can't tell if it's an Nvidia driver upgrade failure or the new kernel that has stopped the Nvidia driver from working. Either way, please try: sudo apt install --reinstall nvidia-dkms-510 or even try the latest driver: sudo apt install nvidia-driver-525 ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.15 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete -- 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/2002349 Title: Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic Status in linux-hwe-5.15 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2002349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002381] [NEW] arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle
Public bug reported: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: In Progress ** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2002381 Title: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Focal: In Progress Bug description: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2002381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002349] Re: Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic
** Summary changed: - Stuck at 640x480. No Nvidia driver anymore + Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic ** Package changed: ubuntu => linux-hwe-5.15 (Ubuntu) ** Changed in: linux-hwe-5.15 (Ubuntu) Status: Invalid => New -- 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/2002349 Title: Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic Status in linux-hwe-5.15 package in Ubuntu: New Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2002349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002349] [NEW] Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic
You have been subscribed to a public bug: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- Nvidia driver does not load after focal HWE kernel update 5.15.0-57.63~20.04.1-generic https://bugs.launchpad.net/bugs/2002349 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Thanks Jeremy, you help solved my issues with compiling the module with Laurent Pinchart modification. installing with modprobe, the dmesg shows: [103970.912878] usb 3-6: Found UVC 1.50 device ACER HD User Facing (0408:4035) [103970.912882] usb 3-6: Forcing UVC version to 1.0a [103970.949432] input: ACER HD User Facing: ACER HD Us as /devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input38 [103970.949630] usbcore: registered new interface driver uvcvideo Cheese video is working. BUT audio is NOT working. any idea ? -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 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 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
Debdiff for Jammy. ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2002373/+attachment/5640383/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.2.debdiff ** Tags added: oem-priority originate-from-232 stella -- 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 alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Jammy: Confirmed Status in alsa-ucm-conf source package in Kinetic: Confirmed Status in alsa-ucm-conf source package in Lunar: Confirmed 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
Debdiff for Kinetic. ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2002373/+attachment/5640382/+files/alsa-ucm-conf_1.2.6.3-1ubuntu2.1.debdiff -- 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 alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Jammy: Confirmed Status in alsa-ucm-conf source package in Kinetic: Confirmed Status in alsa-ucm-conf source package in Lunar: Confirmed 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/ubuntu/+source/alsa-ucm-conf/+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
Debdiff for Lunar. ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2002373/+attachment/5640378/+files/alsa-ucm-conf_1.2.6.3-1ubuntu3.debdiff -- 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 alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Jammy: Confirmed Status in alsa-ucm-conf source package in Kinetic: Confirmed Status in alsa-ucm-conf source package in Lunar: Confirmed 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/ubuntu/+source/alsa-ucm-conf/+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] [NEW] Mic Mute LED doesn't work on DMIC laptops
Public bug reported: [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. ** Affects: alsa-ucm-conf (Ubuntu) Importance: Medium Status: Confirmed ** Affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: alsa-ucm-conf (Ubuntu Kinetic) Importance: Medium Status: Confirmed ** Affects: alsa-ucm-conf (Ubuntu Lunar) Importance: Medium Status: Confirmed ** Package changed: linux (Ubuntu) => alsa-ucm-conf (Ubuntu) ** Also affects: alsa-ucm-conf (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: New => Confirmed ** Changed in: alsa-ucm-conf (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: New => Confirmed ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Jammy: Confirmed Status in alsa-ucm-conf source package in Kinetic: Confirmed Status in alsa-ucm-conf source package in Lunar: Confirmed 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/ubuntu/+source/alsa-ucm-conf/+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 1995894] Re: no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995894 Title: no HDMI sound output in 22.10 (works in 22.04.1 and kernel-6.1rc3) Status in linux package in Ubuntu: Expired Bug description: There is no sound output via HDMI on 22.10. It worked in 22.04.1 and it works in 22.10 when I installed kernel 6.1rc3. I think it has to do with the snd_hda_intel driver not attaching to Device-1: AMD Kabini HDMI/DP. Doesn't work on 22.10: # inxi -SMA System: Host: lubuntu Kernel: 5.19.0-21-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: N/A Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.19.0-21-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Works on 22.04.1: # inxi -SMA System: Host: lubuntu Kernel: 5.15.0-43-generic x86_64 bits: 64 Desktop: LXQt 0.17.1 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-43-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Works on 22.10 with kernel-6.1rc3: # inxi -SMA System: Host: me-aspiretc281 Kernel: 6.1.0-060100rc3-generic arch: x86_64 bits: 64 Desktop: LXQt v: 1.1.0 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: Acer model: Aspire TC-281 serial: DBE0E110018010680230A1 UEFI: American Megatrends v: R01-A2 date: 07/18/2017 Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 15h Audio driver: snd_hda_intel Sound Server-1: ALSA v: k6.1.0-060100rc3-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.58 running: yes ubuntu-bug thinks pulse-audio crashed but I don't know if that is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress 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-oem-5.14 source package in Focal: Fix Released 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: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
tested on 5.19.0-30-generic and 5.15.0-59-generic: Tx power table (channel 155) CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160
[Kernel-packages] [Bug 2002089] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640367/+files/PaInfo.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640368/+files/ProcCpuinfoMinimal.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640366/+files/Lsusb-v.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640375/+files/acpidump.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640374/+files/WifiSyslog.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640371/+files/ProcModules.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640372/+files/RfKill.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640373/+files/UdevDb.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640370/+files/ProcInterrupts.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640369/+files/ProcEnviron.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640363/+files/Lspci-vt.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640364/+files/Lsusb.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640365/+files/Lsusb-t.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640362/+files/Lspci.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640361/+files/CurrentDmesg.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 6.0.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 12/22/2022 dmi.bios.release: 0.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.55 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: dmi.product.family: Latitude dmi.product.name: Precision 3480 dmi.product.sku: 0C02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Re: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
apport information ** Tags added: apport-collected jammy ** Description changed: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1216 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-01-05 (5 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 + IwConfig: + lono wireless extensions. + + enp0s31f6 no wireless extensions. + + wwan0 no wireless extensions. + MachineType: Dell Inc. Precision 3480 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-6.0.0-1010-oem N/A + linux-backports-modules-6.0.0-1010-oem N/A + linux-firmware 20220329.git681281e4-0ubuntu3.7 + Tags: jammy + Uname: Linux 6.0.0-1010-oem x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 12/22/2022 + dmi.bios.release: 0.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 0.6.55 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.ec.firmware.release: 0.0 + dmi.modalias: dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02: + dmi.product.family: Latitude + dmi.product.name: Precision 3480 + dmi.product.sku: 0C02 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2002089/+attachment/5640360/+files/AlsaInfo.txt -- 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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1216 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-05 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Precision 3480 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.0.0-1010-oem N/A linux-backports-modules-6.0.0-1010-oem N/A linux-firmware
[Kernel-packages] [Bug 2002368] 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/2002368 Title: apt-get build-dep linux doesn't work Status in linux package in Ubuntu: Confirmed Bug description: Hello, on my power9 system apt-get build-dep linux doesn't work: [sarnold@fitzhume:/tmp/linux-6.1.4] 20s $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy [sarnold@fitzhume:/tmp/linux-6.1.4] $ uname -a Linux fitzhume 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:55:27 UTC 2022 ppc64le ppc64le ppc64le GNU/Linux [sarnold@fitzhume:/tmp/linux-6.1.4] $ sudo apt-get build-dep linux Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: builddeps:linux : Depends: dh-systemd but it is not installable E: Unable to correct problems, you have held broken packages. [sarnold@fitzhume:/tmp/linux-6.1.4] 100 $ sudo apt show dh-systemd N: Unable to locate package dh-systemd N: Unable to locate package dh-systemd E: No packages found [sarnold@fitzhume:/tmp/linux-6.1.4] 100 $ Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic ppc64le NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-53-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Tue Jan 10 03:17:07 2023 InstallationDate: Installed on 2020-04-22 (992 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta ppc64el (20200409) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' PciMultimedia: ProcEnviron: LC_TIME=C TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=ae696e02-a663-4de9-9fad-e6c99cc2f07b ro nvme_core.default_ps_max_latency_us=0 ProcLoadAvg: 0.40 0.26 0.13 1/445 169755 ProcLocks: 1: FLOCK ADVISORY WRITE 127565 103:02:656379 0 EOF 2: POSIX ADVISORY WRITE 5125 00:19:1957 0 EOF 3: POSIX ADVISORY WRITE 3716 103:02:655956 0 EOF 4: FLOCK ADVISORY WRITE 1241 00:19:1191 0 EOF ProcSwaps: Filename TypeSizeUsed Priority /swap.img file 4194240 8192 -2 ProcVersion: Linux version 5.15.0-53-generic (buildd@bos02-ppc64el-005) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #59-Ubuntu SMP Mon Oct 17 18:55:27 UTC 2022 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-08 (154 days ago) VarLogDump_list: total 0 acpidump: cpu_cores: Number of cores present = 8 cpu_coreson: Number of cores online = 8 cpu_dscr: DSCR is 16 cpu_freq: min: 3.774 GHz (cpu 0) max: 3.774 GHz (cpu 10) avg: 3.774 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: AceLan Kao (acelankao) => (unassigned) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches fixed the isue https://patchwork.freedesktop.org/series/110693/ [Test] Verified on the machine which can reproduce the issue. [Where problems may occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002368] [NEW] apt-get build-dep linux doesn't work
Public bug reported: Hello, on my power9 system apt-get build-dep linux doesn't work: [sarnold@fitzhume:/tmp/linux-6.1.4] 20s $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy [sarnold@fitzhume:/tmp/linux-6.1.4] $ uname -a Linux fitzhume 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:55:27 UTC 2022 ppc64le ppc64le ppc64le GNU/Linux [sarnold@fitzhume:/tmp/linux-6.1.4] $ sudo apt-get build-dep linux Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: builddeps:linux : Depends: dh-systemd but it is not installable E: Unable to correct problems, you have held broken packages. [sarnold@fitzhume:/tmp/linux-6.1.4] 100 $ sudo apt show dh-systemd N: Unable to locate package dh-systemd N: Unable to locate package dh-systemd E: No packages found [sarnold@fitzhume:/tmp/linux-6.1.4] 100 $ Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic ppc64le NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-53-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Tue Jan 10 03:17:07 2023 InstallationDate: Installed on 2020-04-22 (992 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta ppc64el (20200409) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' PciMultimedia: ProcEnviron: LC_TIME=C TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=ae696e02-a663-4de9-9fad-e6c99cc2f07b ro nvme_core.default_ps_max_latency_us=0 ProcLoadAvg: 0.40 0.26 0.13 1/445 169755 ProcLocks: 1: FLOCK ADVISORY WRITE 127565 103:02:656379 0 EOF 2: POSIX ADVISORY WRITE 5125 00:19:1957 0 EOF 3: POSIX ADVISORY WRITE 3716 103:02:655956 0 EOF 4: FLOCK ADVISORY WRITE 1241 00:19:1191 0 EOF ProcSwaps: Filename TypeSizeUsed Priority /swap.img file 4194240 8192 -2 ProcVersion: Linux version 5.15.0-53-generic (buildd@bos02-ppc64el-005) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #59-Ubuntu SMP Mon Oct 17 18:55:27 UTC 2022 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-08 (154 days ago) VarLogDump_list: total 0 acpidump: cpu_cores: Number of cores present = 8 cpu_coreson: Number of cores online = 8 cpu_dscr: DSCR is 16 cpu_freq: min: 3.774 GHz (cpu 0) max: 3.774 GHz (cpu 10) avg: 3.774 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug jammy ppc64el uec-images -- 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/2002368 Title: apt-get build-dep linux doesn't work Status in linux package in Ubuntu: New Bug description: Hello, on my power9 system apt-get build-dep linux doesn't work: [sarnold@fitzhume:/tmp/linux-6.1.4] 20s $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy [sarnold@fitzhume:/tmp/linux-6.1.4] $ uname -a Linux fitzhume 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:55:27 UTC 2022 ppc64le ppc64le ppc64le GNU/Linux [sarnold@fitzhume:/tmp/linux-6.1.4] $ sudo apt-get build-dep linux
[Kernel-packages] [Bug 1986378] Re: linux-headers make kernel script fails with fatal error: classmap.h: No such file or directory
same bug on Ubuntu 22.10 5.19.0-1011-raspi #18-Ubuntu SMP PREEMPT Thu Dec 15 11:27:47 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986378 Title: linux-headers make kernel script fails with fatal error: classmap.h: No such file or directory Status in linux package in Ubuntu: Confirmed Bug description: It looks like in most Ubuntu Linux kernel, building kernel scripts in /usr/scr/linux-headers-$(uname -r)/ fails with classmap.h missing. The security/selinux/include/ headers are not included in /usr/src to be packaged in linux-source-x.xx_xxx.deb package. CONFIG_SECURITY_SELINUX is enabled. lab@test-server:/usr/src/linux-headers-5.15.0-43-generic$ zgrep CONFIG_SECURITY_SELINUX /boot/config-$(uname -r) CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y # CONFIG_SECURITY_SELINUX_DISABLE is not set CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9 CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256 lab@test-server:/usr/src/linux-headers-5.15.0-43-generic$ sudo make scripts [sudo] password for lab: SYNCinclude/config/auto.conf.cmd HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACCscripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf 6^[[18~ HOSTCC scripts/genksyms/genksyms.o YACCscripts/genksyms/parse.tab.[ch] HOSTCC scripts/genksyms/parse.tab.o LEX scripts/genksyms/lex.lex.c HOSTCC scripts/genksyms/lex.lex.o HOSTLD scripts/genksyms/genksyms HOSTCC scripts/selinux/genheaders/genheaders scripts/selinux/genheaders/genheaders.c:18:10: fatal error: classmap.h: No such file or directory 18 | #include "classmap.h" | ^~~~ compilation terminated. make[3]: *** [scripts/Makefile.host:95: scripts/selinux/genheaders/genheaders] Error 1 make[2]: *** [scripts/Makefile.build:548: scripts/selinux/genheaders] Error 2 make[1]: *** [scripts/Makefile.build:548: scripts/selinux] Error 2 make: *** [Makefile:1209: scripts] Error 2 lab@test-server:/usr/src/linux-headers-5.15.0-43-generic$ lab@test-server:~$ uname -a Linux test-server 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lab@test-server:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename:jammy lab@test-server:~$ cat /proc/version_signature Ubuntu 5.15.0-43.46-generic 5.15.39 Should security/selinux/include/ headers be shipped in /usr/src/ as part of linux-source-x.xx.x_.deb or is there other proper workaround for this issue? I've tried with the following kernels: Ubuntu 20.04 5.4.0-120-generic amd64 kernel Ubuntu 20.04 5.4.0-64-generic arm64 kernel Ubuntu 22.04 5.15.0-43-generic amd64 kernel Ubuntu 20.04 custom build arm64 Ubuntu-unstable-5.17.0-6.6 from Ubuntu-unstable kernel tree An old Debian Bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988367 where they have a fix to copy the selinux headers to /usr/src to ship https://github.com/ilbers/isar/pull/67 https://github.com/ilbers/isar/pull/67/commits/7818e4f5e7495961c172511648476f5bf1c2e0fc Thanks - Jiandi --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Aug 9 12:12 seq crw-rw+ 1 root audio 116, 33 Aug 9 12:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-09 (3 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=e3d8adf4-67b0-4bac-8472-7eaebbb8cb7d ro transparent_hugepage=madvise console=tty0
[Kernel-packages] [Bug 2000909] Re: Microphone mute LED not working as expected after pressing the mic mute hotkey
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2000909 Title: Microphone mute LED not working as expected after pressing the mic mute hotkey Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Mic mute LED can't be toggled by the state of the mic-mute hotkey. [Fix] Create a new fixup to address the dual codec problem on particular platforms. [Test Case] Use the following command and check there's no duplicate mixer with the same name `Capture Switch`, `Capture Volume` $amixer controls [Where problems could occur] The commit only applies dual codec fixup on particular affected models. Should be no regression problem or any side effect to generic platforms. == original bug report == [Summary] Microphone mute LED won't turn on when pressing it [Steps to reproduce] 1. Press microphone mute hotkey [Expected result] LED turn on/off [Actual result] LED has no function when pressing the key [Failure rate] 3/3 [Additional information] CID: 202210-30776 SKU: QUKLA4-DVT1-C2-UBT Image: canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-quilladin+X64 system-manufacturer: Dell Inc. system-product-name: Latitude 3440 bios-version: 0.1.7 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a1] (rev 04) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 6.0.0-1006-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID
In linux/lunar version 6.1.0-11.11, linux-unstable after v6.1-rc1, linux-oem-6.1/jammy version 6.1.0-1004.4. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid -- 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/1998885 Title: Add additional Mediatek MT7922 BT device ID Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux/5.15.0-59.65 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 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems
[Kernel-packages] [Bug 1993563] Re: support for same series backports versioning numbers
This bug is awaiting verification that the linux/5.15.0-59.65 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 -- 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991951] Re: RCU stalls
This bug is awaiting verification that the linux/5.15.0-59.65 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 -- 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/1991951 Title: RCU stalls Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: our RCU Stall Timeouts are different to upstream defaults; with regular one 3x longer; and expedited one 1000x shorter. not sure why. Let's harmonize on 60 & 0, which is 60 for regular ones that are set on most architectures; and upstream default for the expedited ones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
This bug is awaiting verification that the linux/5.15.0-59.65 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 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded
[Kernel-packages] [Bug 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
This bug is awaiting verification that the linux/5.15.0-59.65 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 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/1989944 Title: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Fix Committed Bug description: [SRU Justification] == Impact == We applied a set of patches early as the upstreaming got delayed. The patch now is in upstream linux. Since it differs somewhat from the patch we carry and in order to get potential security and other updates right, we want to replace the SAUCE patch by its upstream counterpart. == Fix == “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” == Testcase == Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 1983143) == Regression Potential == Previously working external connections might no longer work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989990] Re: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence
This bug is awaiting verification that the linux/5.15.0-59.65 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 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/1989990 Title: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target after link down event if the number of queues have changed post link down. [Fix] Following upstream patch set helps address the issue. 1. nvmet: Expose max queues to configfs https://git.infradead.org/nvme.git/commit/2c4282742d049e2a5ab874e2b359a2421b9377c2 2. nvme-tcp: Handle number of queue changes https://git.infradead.org/nvme.git/commit/516204e486a19d03962c2757ef49782e6c1cacf4 3. nvme-rdma: Handle number of queue changes https://git.infradead.org/nvme.git/commit/e800278c1dc97518eab1970f8f58a5aad52b0f86 The patch in Point 2 above helps address the failure to reconnect in NVMe TCP scenario. Also, following patch addresses error code parsing issue in the reconnect sequence. nvme-fabrics: parse nvme connect Linux error codes https://git.infradead.org/nvme.git/commit/ec9e96b5230148294c7abcaf3a4c592d3720b62d [Test Plan] 1. Boot into Ubuntu 22.04 kernel without fix. 2. Establish connection to NVMe TCP target. 3. Toggle NIC link and bring link up after 10 seconds. When the NIC link is down, on the target increase the number of queues assigned to the controller. 4. Observe that connection to target is lost and after link comes up, controller from host tries to re-establish connection. 5. With patch, reconnection succeeds with higher number of queues [Where problems could occur] Regression risk is low to medium. [Other Info] Test Kernel Source https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1989990_nvme_tcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux/5.15.0-59.65 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 -- 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/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed 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 source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux/5.15.0-59.65 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 verification-needed-jammy -- 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/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress 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-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux/5.15.0-59.65 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 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
This bug is awaiting verification that the linux/5.15.0-59.65 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 verification-needed-jammy -- 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/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002361] [NEW] allow per-net notifier to follow netdev into namespace
Public bug reported: * Explain the bug(s) There is possible deadlock during reload mlxsw into initial netns made possible by commit: 328fbe747ad4 ("net: Close race between {un, }register_netdevice_notifier() and setup_net()/cleanup_net()"). * Brief explanation of fixes Introduce dev_net variant that is basically per-net notifier with an extension that re-registers the per-net notifier upon netdev namespace change. Basically the per-net notifier follows the netdev into namespace. * How to test # chroot /host nsenter -t 1 -n devlink dev reload ${port} netns ${NS} * What it could break none ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2002361 Title: allow per-net notifier to follow netdev into namespace Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) There is possible deadlock during reload mlxsw into initial netns made possible by commit: 328fbe747ad4 ("net: Close race between {un, }register_netdevice_notifier() and setup_net()/cleanup_net()"). * Brief explanation of fixes Introduce dev_net variant that is basically per-net notifier with an extension that re-registers the per-net notifier upon netdev namespace change. Basically the per-net notifier follows the netdev into namespace. * How to test # chroot /host nsenter -t 1 -n devlink dev reload ${port} netns ${NS} * What it could break none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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:
[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress 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-oem-5.14 source package in Focal: Fix Released 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: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1983656 Title: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500 Status in linux package in Ubuntu: Fix Committed 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: BugLink: https://bugs.launchpad.net/bugs/1983656 [Impact] Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in 5.15.0-41-generic and did not resolve the issue. The following conditions are required to trigger the bug: - A port VLAN must be assigned by the host - The MTU must be set >1500 by the guest There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be used without these patches. [Fix] iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but on the previous ice driver, it was decremented by VLAN_HLEN to make some space to fit the VLAN header. This doesn't happen on iavf, and we end up trying to use a packet size larger than IAVF_MAX_RXBUFFER, causing the IAVF_ERR_PARAM error. The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to max_mtu received from the PF via GET_VF_RESOURCES msg. Also pick up a necessary commit for i40e to announce the correct maximum packet size by GET_VF_RESOURCES msg. This has been fixed by the following commits: commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef Author: Michal Jaron Date: Tue Sep 13 15:38:35 2022 +0200 Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames Link: https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef commit 372539def2824c43b6afe2403045b140f65c5acc Author: Michal Jaron Date: Tue Sep 13 15:38:36 2022 +0200 Subject: i40e: Fix VF set max MTU size Link: https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc A test kernel is available in the following ppa: https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742 If you install the test kernel to a compute host and VM, when you attach a VF and set the MTU to 9000, it succeeds, and traffic can flow. [Test Plan] Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port vlan: Openstack works, as does creating a VM directly with uvtool/libvirt. $ uvt-kvm create focal-test release=focal Using the document to understand SRIOV basics in the link below https://www.intel.com/content/www/us/en/developer/articles/technical/configure- sr-iov-network-virtual-functions-in-linux-kvm.html The following command show all the bus info for all the network devices $ lshw -c network -businfo Choose one, as shown below pci@:17:01.4 ens2f0v4 networkEthernet Adaptive Virtual Function We can then add the following into the XML definition via “virsh edit focal-test” Then we stop and start the VM via "virsh shutdown focal-test" and then "virsh start focal-test". We can then login to the VM using the command below $ uvt-kvm ssh focal-test Once you have logged in, run the following ip parameters $ sudo ip a a 192.168.1.7/24 dev enp7s0 $
[Kernel-packages] [Bug 1988461] Re: intel_pmc_core not load on Raptor Lake
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1988461 Title: intel_pmc_core not load on Raptor Lake 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: Won't Fix 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: [SRU Justification] [Impact] Missing kernel pmc sysfs interface in /sys/kernel/debug/pmc_core. [Fix] Two commits for kernel version older than v6.0-rc3, and one for otherwise. [Test Case] $ ls /sys/kernel/debug/pmc_core [Where problems could occur] No. [Other Info] RPL-S is supported since oem-5.17, so unstable/oem-6.0/kinetic/oem-5.17 are affected. oem-5.17/oem-6.0 are skipped here for they have been applied manually. == original bug description == [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1988711 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [IMPACT/Justification] There are numerous bug fixes included in the more recent version of lpfc That Broadcom has asked to pull into Jammy and Kinetic to better support customers in the field who are using the GA kernel and cant or wont move to the HWE kernels. These all are limited to the lpfc driver itself, no patches to core code are requested. [FIX] A few of these were already landed in Jammy, and all but 6 (ones landed in 6.0 upstream) were already in Kinetic. b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5 b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into lpfc_sli_prep_abort_xri() ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved configuration ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in queuecommand after VMID 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in XMIT_ELS_RSP64_CX iocb f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in lpfc_nvme_cancel_iocb() 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for aborted NVMe cmds 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after starget_to_rport() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path refactoring 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in lpfc_ct_reject_event() a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol independent ed913cf4a533 scsi: lpfc: Commonize VMID code location fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3 a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for NVMe I/O e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric parameters dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link() 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in rscn_recovery_check() 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event() ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() 775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call 92bd903da12b scsi: lpfc: Fix additional reference counting in lpfc_bsg_rport_els() db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line 646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() 3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in lpfc_sli_prep_wqe() a346f28ad231 scsi: lpfc: Remove unneeded variable 66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches 4af4d0e2ea94 scsi: lpfc: Update
[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid 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 Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress 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 Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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/1990920 Title: Fix resume on AMD platforms when TBT monitor is plugged 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-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: 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 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 Bug description: [Impact] When TBT monitor is connected to AMD platform, system resume will hit stack corruption or BUG_ON() macro. [Fix] Revert the offending commit and handle MST properly. [Test] The system can resume normally and no more kernel splat. [Where problems could occur] The new logic is restriced to MST hub, so normal DP/HDMI usage should be unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-raspi source package in Kinetic: Fix Released Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 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 Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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 1993315] Re: md: Replace snprintf with scnprintf
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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 1993148] Re: Support Icicle Kit reference design v2022.10
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993715] Re: AMD Cezanne takes 5 minutes to wake up from suspend
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1993715 Title: AMD Cezanne takes 5 minutes to wake up from suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid 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: [SRU Justification] [Impact] AMD Cezanne takes 5 minutes to wake up from suspend. [Fix] A fix originated from AMD is being proposed to upstream mailing list. [Test Case] $ rtcwake -m mem -s 10 [Where problems could occur] This patch fixes the issue we had, but maybe there are still some other corner cases that can cause similar problems. [Other Info] The problematic commit landed in v5.19-rc1, so kernels >= v5.19 are nominated for fix. == original bug description == [Summary] rtcwake may be blocked for 5 minutes. Model name: AMD Ryzen 5 7530U with Radeon Graphics CPU family: 25 Model: 80 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 Stepping: 0 [Reproduce Steps] 1. $ rtcwake -m mem -s 10 2. The device takes 5 minutes to resume [Results] Expected: Should resume after 10 seconds Actual: System stays asleep for 5 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993563] Re: support for same series backports versioning numbers
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- 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 1995957] Re: Add cs35l41 firmware loading support
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1995957 Title: Add cs35l41 firmware loading support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New 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: Won't Fix Status in linux-firmware 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-firmware 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] Speakers on some laptops are rather quiet even with max volume. [Fix] Loading firmware to make cs35l41 speaker amplifier really work. [Test] With the fix applied, the speaker has become really loud as intended. [Where problems could occur] Most commits are refactoring codes on both ASoC and HDA parts, so things can be missed. Other than that, the change is strictly limited to cs35l41, so the regression scope is rather narrow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm verification-needed-kinetic -- 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/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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 1996536] Re: selftests/.../nat6to4 breaks the selftests build
This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux-ibm -- 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/1996536 Title: selftests/.../nat6to4 breaks the selftests build Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Unused test program tools/testing/selftests/net/bpf/nat6to4 cannot easily be built in the standard Ubuntu kernel build environment. The "tools/testing/selftests/" are not built at all by Ubuntu kernel package builds, but are part of my build-test workflow, which is interrupted by this breakage. This mainline bpf selftest (nat6to4) requires additional package dependencies not satisfied by the Ubuntu kernel Build-depends and unsatisfiable when cross compilers are installed. Disable it to allow the rest of selftests/ to build. [Impact] * No impact on Ubuntu kernel package builds. [Test Case] * Allows internal (manual) testing of the `fakeroot debian/rules compileselftests` build target. [Regression Potential] * None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
First, enable source code repositories, then fetch the source code with the following in terminal apt-get source linux-modules-extra-$(uname -r) Then navigate to the /drivers/media/usb/uvc directory and rename the uvcdriver.c to uvcdriver.old, choose open directory in terminal then wget https://raw.githubusercontent.com/Giuliano69/uvc_driver-for-Quanta- HD-User-Facing-0x0408-0x4035-/main/uvc_driver.c make -j4 -C /lib/modules/$(uname -r)/build M=$(pwd) modules sudo cp uvcvideo.ko /lib/modules/$(uname -r)/kernel/drivers/media/usb/uvc/ Then see if it works -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 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 Tags: jammy Uname: Linux
[Kernel-packages] [Bug 2002358] [NEW] Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version?
Public bug reported: Now and then I have the problem, that the screen turns off after seconds of keyboard or mouse inactivity. I think that it changes with kernel versions but I'm not 100% sure that kernel version is the cause. The annoying bug is present for some time then it's gone, and after a while, the problem is back. Two days ago following packages were installed or updated, since then the problem is there again: Install: linux-hwe-5.15-headers-5.15.0-57:amd64 (5.15.0-57.63~20.04.1, automatic), linux-image-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-headers-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-extra-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), update-manager-core:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-libc-dev:amd64 (5.4.0-135.152, 5.4.0-136.153), libcurl4:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libksba8:amd64 (1.3.5-2ubuntu0.20.04.1, 1.3.5-2ubuntu0.20.04.2), update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-image-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), gir1.2-nautilus-3.0:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), linux-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), libfabric1:amd64 (1.6.2-3, 1.6.2-3ubuntu0.1), nautilus:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), libnautilus-extension1a:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), python3-update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), nautilus-data:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), curl:amd64 (7.68.0-1ubuntu2.14, 7 .68.0-1ubuntu2.15), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15) Today I figured out that xset -dpms solves the problem but xset s off does not. In gnome-control-center -> Power I have the following settings: Power Saving: Blank Screen -> 15 minutes ( Selecting Never doesn't change anything.) Suspend & Power Button: Automatic Suspend: On, Delay 15 minutes Power Button Action: Power off I'm using Description:Ubuntu 20.04.5 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 22:47:36 2023 InstallationDate: Installed on 2022-01-01 (372 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2002358 Title: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version? Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Now and then I have the problem, that the screen turns off after seconds of keyboard or mouse inactivity. I think that it changes with kernel versions but I'm not 100% sure that kernel version is the cause. The annoying bug is present for some time then it's gone, and after a while, the problem is back. Two days ago following packages were installed or updated, since then the problem is there again: Install: linux-hwe-5.15-headers-5.15.0-57:amd64 (5.15.0-57.63~20.04.1, automatic), linux-image-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-headers-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-extra-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic), linux-modules-5.15.0-57-generic:amd64 (5.15.0-57.63~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), update-manager-core:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-libc-dev:amd64 (5.4.0-135.152, 5.4.0-136.153), libcurl4:amd64 (7.68.0-1ubuntu2.14, 7.68.0-1ubuntu2.15), libksba8:amd64 (1.3.5-2ubuntu0.20.04.1, 1.3.5-2ubuntu0.20.04.2), update-manager:amd64 (1:20.04.10.10, 1:20.04.10.11), linux-image-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), gir1.2-nautilus-3.0:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), linux-generic-hwe-20.04:amd64 (5.15.0.56.62~20.04.22, 5.15.0.57.63~20.04.23), libfabric1:amd64 (1.6.2-3, 1.6.2-3ubuntu0.1), nautilus:amd64 (1:3.36.3-0ubuntu1.20.04.1, 1:3.36.3-0ubuntu1.20.04.2), libnautilus-extension1a:amd64
[Kernel-packages] [Bug 2002353] 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 2002353 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/2002353 Title: Problem with Goodix i2c touch screen Status in linux package in Ubuntu: Incomplete Bug description: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002356] 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/2002356 Title: linux-image-5.19.0-28-generic update breaks touchpad driver Status in linux package in Ubuntu: Confirmed Bug description: The Ubuntu kernel update from linux-image-5.19.0-26-generic to linux- image-5.19.0-28-generic breaks the touchpad driver on my Lenovo Ideapad Flex 5. Rolling back the kernel to the -26 version fixes the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-28-generic 5.19.0-28.29 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cvpsmith 104660 F wireplumber /dev/snd/controlC0: cvpsmith 104660 F wireplumber /dev/snd/seq:cvpsmith 104658 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:52:40 2023 InstallationDate: Installed on 2022-12-21 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82R9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=f743c272-eda9-4ec5-b814-0c2a3552abce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: JCCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ALC7 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrJCCN27WW:bd03/04/2022:br1.27:efr1.24:svnLENOVO:pn82R9:pvrIdeaPadFlex514ALC7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ALC7:skuLENOVO_MT_82R9_BU_idea_FM_IdeaPadFlex514ALC7: dmi.product.family: IdeaPad Flex 5 14ALC7 dmi.product.name: 82R9 dmi.product.sku: LENOVO_MT_82R9_BU_idea_FM_IdeaPad Flex 5 14ALC7 dmi.product.version: IdeaPad Flex 5 14ALC7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002356] [NEW] linux-image-5.19.0-28-generic update breaks touchpad driver
Public bug reported: The Ubuntu kernel update from linux-image-5.19.0-26-generic to linux- image-5.19.0-28-generic breaks the touchpad driver on my Lenovo Ideapad Flex 5. Rolling back the kernel to the -26 version fixes the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-28-generic 5.19.0-28.29 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cvpsmith 104660 F wireplumber /dev/snd/controlC0: cvpsmith 104660 F wireplumber /dev/snd/seq:cvpsmith 104658 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:52:40 2023 InstallationDate: Installed on 2022-12-21 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82R9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=f743c272-eda9-4ec5-b814-0c2a3552abce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: JCCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ALC7 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrJCCN27WW:bd03/04/2022:br1.27:efr1.24:svnLENOVO:pn82R9:pvrIdeaPadFlex514ALC7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ALC7:skuLENOVO_MT_82R9_BU_idea_FM_IdeaPadFlex514ALC7: dmi.product.family: IdeaPad Flex 5 14ALC7 dmi.product.name: 82R9 dmi.product.sku: LENOVO_MT_82R9_BU_idea_FM_IdeaPad Flex 5 14ALC7 dmi.product.version: IdeaPad Flex 5 14ALC7 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kinetic 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/2002356 Title: linux-image-5.19.0-28-generic update breaks touchpad driver Status in linux package in Ubuntu: Confirmed Bug description: The Ubuntu kernel update from linux-image-5.19.0-26-generic to linux- image-5.19.0-28-generic breaks the touchpad driver on my Lenovo Ideapad Flex 5. Rolling back the kernel to the -26 version fixes the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-28-generic 5.19.0-28.29 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cvpsmith 104660 F wireplumber /dev/snd/controlC0: cvpsmith 104660 F wireplumber /dev/snd/seq:cvpsmith 104658 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:52:40 2023 InstallationDate: Installed on 2022-12-21 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82R9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=f743c272-eda9-4ec5-b814-0c2a3552abce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: JCCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ALC7 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrJCCN27WW:bd03/04/2022:br1.27:efr1.24:svnLENOVO:pn82R9:pvrIdeaPadFlex514ALC7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ALC7:skuLENOVO_MT_82R9_BU_idea_FM_IdeaPadFlex514ALC7: dmi.product.family: IdeaPad Flex 5 14ALC7 dmi.product.name: 82R9
[Kernel-packages] [Bug 2002353] Re: Problem with Goodix i2c touch screen
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+attachment/5640275/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002353 Title: Problem with Goodix i2c touch screen Status in linux package in Ubuntu: New Bug description: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002353] [NEW] Problem with Goodix i2c touch screen
Public bug reported: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2002353/+attachment/5640273/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002353 Title: Problem with Goodix i2c touch screen Status in linux package in Ubuntu: New Bug description: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Hi All, Running the xiaomi notebook x15 pro here. Which comes with 4 speakers. The front firing sound bad, like 25% and downward do not make any sound. Anyone can help me out where to start? hdajackretask does not work / save upon reboot. Kinda struggeling with this one here... http://alsa-project.org/db/?f=e4477f3727b1df458e1647d10a48cba2f94b2112 -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in Linux: New Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan
[Kernel-packages] [Bug 2002347] [NEW] Focal update: v5.4.225 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.225 upstream stable release from git://git.kernel.org/ xfs: preserve rmapbt swapext block reservation from freed blocks xfs: rename xfs_bmap_is_real_extent to is_written_extent xfs: redesign the reflink remap loop to fix blkres depletion crash xfs: use MMAPLOCK around filemap_map_pages() xfs: preserve inode versioning across remounts xfs: drain the buf delwri queue before xfsaild idles phy: stm32: fix an error code in probe wifi: cfg80211: silence a sparse RCU warning wifi: cfg80211: fix memory leak in query_regdb_file() bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues HID: hyperv: fix possible memory leak in mousevsc_probe() net: gso: fix panic on frag_list with mixed head alloc types net: tun: Fix memory leaks of napi_get_frags bnxt_en: Fix possible crash in bnxt_hwrm_set_coal() bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer net: fman: Unregister ethernet device on removal capabilities: fix undefined behavior in bit shift for CAP_TO_MASK net: lapbether: fix issue of dev reference count leakage in lapbeth_device_event() hamradio: fix issue of dev reference count leakage in bpq_device_event() drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register() ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network can: af_can: fix NULL pointer dereference in can_rx_register() tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header dmaengine: pxa_dma: use platform_get_irq_optional dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove() drivers: net: xgene: disable napi when register irq failed in xgene_enet_open() perf stat: Fix printing os->prefix in CSV metrics output net: nixge: disable napi when enable interrupts failed in nixge_open() net/mlx5: Allow async trigger completion execution on single CPU systems net: cpsw: disable napi in cpsw_ndo_open() net: cxgb3_main: disable napi when bind qsets failed in cxgb_up() cxgb4vf: shut down the adapter when t4vf_update_port_info() failed in cxgb4vf_open() ethernet: s2io: disable napi when start nic failed in s2io_card_up() net: mv643xx_eth: disable napi when init rxq or txq failed in mv643xx_eth_open() ethernet: tundra: free irq when alloc ring failed in tsi108_open() net: macvlan: fix memory leaks of macvlan_common_newlink riscv: process: fix kernel info leakage arm64: efi: Fix handling of misaligned runtime regions and drop warning MIPS: jump_label: Fix compat branch range check mmc: cqhci: Provide helper for resetting both SDHCI and CQHCI mmc: sdhci-of-arasan: Fix SDHCI_RESET_ALL for CQHCI mmc: sdhci-tegra: Fix SDHCI_RESET_ALL for CQHCI ALSA: hda/ca0132: add quirk for EVGA Z390 DARK ALSA: hda: fix potential memleak in 'add_widget_node' ALSA: usb-audio: Add quirk entry for M-Audio Micro ALSA: usb-audio: Add DSD support for Accuphase DAC-60 vmlinux.lds.h: Fix placement of '.data..decrypted' section nilfs2: fix deadlock in nilfs_count_free_blocks() nilfs2: fix use-after-free bug of ns_writer on remount drm/i915/dmabuf: fix sg_table handling in map_dma_buf btrfs: selftests: fix wrong error check in btrfs_free_dummy_root() udf: Fix a slab-out-of-bounds write bug in udf_find_entry() can: j1939: j1939_send_one(): fix missing CAN header initialization cert host tools: Stop complaining about deprecated OpenSSL functions dmaengine: at_hdmac: Fix at_lli struct definition dmaengine: at_hdmac: Don't start transactions at tx_submit level dmaengine: at_hdmac: Fix completion of unissued descriptor in case of errors dmaengine: at_hdmac: Don't allow CPU to reorder channel enable dmaengine: at_hdmac: Fix impossible condition dmaengine: at_hdmac: Check return code of dma_async_device_register net: tun: call napi_schedule_prep() to ensure we own a napi x86/cpu: Restore AMD's DE_CFG MSR after resume ASoC: wm5102: Revert "ASoC: wm5102: Fix PM disable depth imbalance in wm5102_probe" ASoC: wm5110: Revert "ASoC: wm5110: Fix PM disable depth imbalance in wm5110_probe" ASoC: wm8997: Revert "ASoC: wm8997: Fix PM disable depth imbalance in wm8997_probe" ASoC: wm8962: Add an event handler for TEMP_HP and TEMP_SPK spi: intel: Fix the offset to get the 64K erase opcode ASoC: codecs: jz4725b: add missed Line In power control bit ASoC: codecs: jz4725b: fix reported volume for Master ctl ASoC: codecs: jz4725b: use right control for Capture Volume ASoC: codecs: jz4725b: fix capture selector naming selftests/futex: fix build for clang selftests/intel_pstate: fix build for ARCH=x86_64 NFSv4: Retry LOCK
[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- 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/1998885 Title: Add additional Mediatek MT7922 BT device ID Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 -- 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/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete 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: In Progress 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: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd
[Kernel-packages] [Bug 1995957] Re: Add cs35l41 firmware loading support
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1995957 Title: Add cs35l41 firmware loading support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New 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: Won't Fix Status in linux-firmware 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-firmware 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] Speakers on some laptops are rather quiet even with max volume. [Fix] Loading firmware to make cs35l41 speaker amplifier really work. [Test] With the fix applied, the speaker has become really loud as intended. [Where problems could occur] Most commits are refactoring codes on both ASoC and HDA parts, so things can be missed. Other than that, the change is strictly limited to cs35l41, so the regression scope is rather narrow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997944] Re: Soundwire support for the Intel RPL Gen platforms
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- 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/1997944 Title: Soundwire support for the Intel RPL Gen platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justfication] [Impact] Need soundwire support for the Intel RPL Gen platforms, specifically 0C10/0C4F/0C11. 0C40 added due to dependency. [Fix] Fixes from linux-next for v6.2, as well as those for firmware-sof and alsa-ucm-conf. [Test Case] All the fixes are currently packaged in experimental kernel/firmware PPAs. Install the latest ones and check audio functions. [Where problems could occur] Most of the patches add model information only, and they'd only take effect on platforms with the corresponding hardware pieces. [Other Info] Nominated for Unstable/Lunar and OEM-6.0. == original bug report == Include the support for Soundwire of RPL Gen platforms Related components/fixes: * kernel: * b07908ab26ce ALSA: hda: intel-dsp-config: Add RaptorLake PCI IDs * d608bc44181c ASoC: Intel: sof_sdw: Add support for SKU 0C10 product * 55fc03445e2c ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration * 880bf4b47fc1 ASoC: Intel: sof_sdw: Add support for SKU 0C40 product * 97b5fbf44c00 ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration * a9248c868c39 ASoC: Intel: sof_sdw: Add support for SKU 0C4F product * 6ad73a2b42ea ASoC: rt1318: Add RT1318 SDCA vendor-specific driver * 8c4b3a8ea2c0 ASoC: intel: sof_sdw: add rt1318 codec support. * d84e10da17e7 ASoC: Intel: sof_sdw: Add support for SKU 0C11 product * 0050e3d3d43d ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire
[Kernel-packages] [Bug 1997686] Re: Enable Intel FM350 wwan CCCI driver port logging
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- 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/1997686 Title: Enable Intel FM350 wwan CCCI driver port logging Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missed Modem Logging support. [Fix] Two upstream commits currently in linux-next for maybe v6.2. [Test Case] With corresponding libmbim fix in https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/161, $ mbimcli -d query-trace-config [Where problems could occur] This adds an logging channel that is only compiled when WWAN_DEBUGFS is on, and takes a specific command to enable logging. Should be no harm in general, and might have side-effects when turned on. [Other Info] This is not yet available in mainline kernel but in linux-next, so Unstable, Lunar and OEM-6.0 are all nominated for fix. == original bug report == To enable CCCI driver Modem Logging (MDL) Port for debugging purposes: https://patchwork.kernel.org/project/netdevbpf/patch/20221028153534.1789295-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- 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/1998882 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1026.27 --- linux-oem-5.17 (5.17.0-1026.27) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1026.27 -proposed tracker (LP: #2001046) * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x - drm/amd/pm: disable BACO entry/exit completely on several sienna cichlid cards - drm/amdgpu: disable BACO on special BEIGE_GOBY card - drm/amdgpu: disable BACO support on more cards - drm/amdgpu: make sure to init common IP before gmc * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long -- Timo Aaltonen Wed, 04 Jan 2023 11:37:57 +0200 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete 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: In Progress 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: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote:
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 -- 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/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards 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: Won't Fix 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 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: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is
[Kernel-packages] [Bug 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- 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/230 Title: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms Status in firmware-sof package in Ubuntu: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missing support for two additional product model of Intel RPL Gen Soundwire. [Fix] Two additional commits merged in upstream sof development repository on GitHub. [Test Case] Apply the two changes along with an alsa ucm conf fix, then perform audio automatic/manual checkbox tests. [Where problems could occur] New hardware. No known issue so far, but might have minor issues in the future. [Other Info] Nominated for U/L/OEM-6.0/OEM-6.1. Depending on fixes from bug 1997944. == original bug report == This is a follow-up to bug 1997944 that supports more RPL gen platforms. Staging fixes: * https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product") * https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1026.27 --- linux-oem-5.17 (5.17.0-1026.27) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1026.27 -proposed tracker (LP: #2001046) * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x - drm/amd/pm: disable BACO entry/exit completely on several sienna cichlid cards - drm/amdgpu: disable BACO on special BEIGE_GOBY card - drm/amdgpu: disable BACO support on more cards - drm/amdgpu: make sure to init common IP before gmc * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long -- Timo Aaltonen Wed, 04 Jan 2023 11:37:57 +0200 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards 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: Won't Fix 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 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: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000909] Re: Microphone mute LED not working as expected after pressing the mic mute hotkey
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1010.10 --- linux-oem-6.0 (6.0.0-1010.10) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1010.10 -proposed tracker (LP: #2001070) * Microphone mute LED not working as expected after pressing the mic mute hotkey (LP: #2000909) - ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230) - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product - SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product * Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards (LP: #2000110) - drm/amdgpu: disable BACO support on more cards * Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] (LP: #1999836) - drm/amd/display: No display after resume from WB/CB * Soundwire support for the Intel RPL Gen platforms (LP: #1997944) - ASoC: Intel: soc-acpi-intel-rpl-match: add rpl_sdca_3_in_1 support - ASoC: Intel: sof_sdw: Add support for SKU 0C10 product - ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C40 product - ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration - ASoC: Intel: sof_sdw: Add support for SKU 0C4F product - ASoC: rt1318: Add RT1318 SDCA vendor-specific driver - ASoC: intel: sof_sdw: add rt1318 codec support. - ASoC: Intel: sof_sdw: Add support for SKU 0C11 product - ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration - SAUCE: ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product - [Config] enable CONFIG_SND_SOC_RT1318_SDW * Add additional Mediatek MT7922 BT device ID (LP: #1998885) - Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 * Mute/mic LEDs no function on a HP platfrom (LP: #1998882) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686) - net: wwan: t7xx: use union to group port type specific data - net: wwan: t7xx: Add port for modem logging * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long * Add cs35l41 firmware loading support (LP: #1995957) - ALSA: hda/realtek: More robust component matching for CS35L41 -- Timo Aaltonen Wed, 04 Jan 2023 11:54:42 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 -- 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/2000909 Title: Microphone mute LED not working as expected after pressing the mic mute hotkey Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Mic mute LED can't be toggled by the state of the mic-mute hotkey. [Fix] Create a new fixup to address the dual codec problem on particular platforms. [Test Case] Use the following command and check there's no duplicate mixer with the same name `Capture Switch`, `Capture Volume` $amixer controls [Where problems could occur] The commit only applies dual codec fixup on particular affected models. Should be no regression problem or any side effect to generic platforms. == original bug report == [Summary] Microphone mute LED won't turn on when pressing it [Steps to reproduce] 1. Press microphone mute hotkey [Expected result] LED turn on/off [Actual result] LED has no function when pressing the key [Failure rate] 3/3 [Additional information] CID: 202210-30776 SKU: QUKLA4-DVT1-C2-UBT Image: canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-quilladin+X64 system-manufacturer: Dell Inc. system-product-name: Latitude 3440 bios-version: 0.1.7 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a1] (rev 04) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 6.0.0-1006-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4
** Tags added: verification-done-focal -- 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 1995453] Re: Add some ACPI device IDs for Intel HID device
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/1995453 Title: Add some ACPI device IDs for Intel HID device 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: 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 Committed 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: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic ** Tags added: kernel-spammed-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine.
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed 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 source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress 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-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9
This bug is awaiting verification that the linux/5.19.0-30.31 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/2001618 Title: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are not supported. test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to select_runtime err=-524 ... test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to select_runtime err=-524 ... test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed] Please find attachment for the complete test log. [Fix] * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg These patches can be cherry-picked into Kinetic kernel. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/ Steps: 1. Reboot with the patched kernel 2. Run: sudo dmesg -C sudo modprobe test_bpf sudo dmesg Tested with Power9 node baltar, with the patched kernel there will be no failure reported by the test_bpf: test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed] [Where problems could occur] This patchset just broaden the BPF operations support on ppc64, we might see some new failures when using these instruction somewhere in the future. Cascardo: The existing atomic operations may regress as well, since they now produce different code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp