[Kernel-packages] [Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - OTG USB Not Working
Please run 'apport-collect 1973648' on the affected machine or - at a minimum - attach the output of 'dmesg' to the ticket. Also, what is the content of '/boot/firmware/config.txt'? ** Package changed: ubuntu => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1973648 Title: Raspberry Pi - Ubuntu Jammy - USB Not Working Status in linux-raspi package in Ubuntu: Incomplete Bug description: Hi Running RPI4B with Jammy and cannot get the USB Ports to work. uname -r output: 5.15.0-1006-raspi dmesg output: pi@raspberrypi:~$ sudo dmesg | grep dwc2 [ 1.842505] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [ 1.842665] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [ 1.895846] dwc2 fe98.usb: DWC OTG Controller [ 1.895873] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [ 1.895904] dwc2 fe98.usb: irq 21, io mem 0xfe98 [ 1.896089] usb usb3: Manufacturer: Linux 5.15.0-1006-raspi dwc2_hsotg In Raspbian Bullseye it works without issue. Output of uname -r 5.15.32-v7l+ dmesg output: pi@raspberrypi:~ $ sudo dmesg | grep dwc2 [ 6.571855] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [ 6.623458] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [ 6.745506] dwc2 fe98.usb: DWC OTG Controller [ 6.745560] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [ 6.745624] dwc2 fe98.usb: irq 36, io mem 0xfe98 [ 6.747266] usb usb3: Manufacturer: Linux 5.15.32-v7l+ dwc2_hsotg [ 7.182279] usb 3-1: new high-speed USB device number 2 using dwc2 [ 7.872295] usb 3-1.4: new full-speed USB device number 3 using dwc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1973648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973648] [NEW] Raspberry Pi - Ubuntu Jammy - OTG USB Not Working
You have been subscribed to a public bug: Hi Running RPI4B with Jammy and cannot get the USB Ports to work. uname -r output: 5.15.0-1006-raspi dmesg output: pi@raspberrypi:~$ sudo dmesg | grep dwc2 [ 1.842505] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [ 1.842665] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [ 1.895846] dwc2 fe98.usb: DWC OTG Controller [ 1.895873] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [ 1.895904] dwc2 fe98.usb: irq 21, io mem 0xfe98 [ 1.896089] usb usb3: Manufacturer: Linux 5.15.0-1006-raspi dwc2_hsotg In Raspbian Bullseye it works without issue. Output of uname -r 5.15.32-v7l+ dmesg output: pi@raspberrypi:~ $ sudo dmesg | grep dwc2 [ 6.571855] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [ 6.623458] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [ 6.745506] dwc2 fe98.usb: DWC OTG Controller [ 6.745560] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [ 6.745624] dwc2 fe98.usb: irq 36, io mem 0xfe98 [ 6.747266] usb usb3: Manufacturer: Linux 5.15.32-v7l+ dwc2_hsotg [ 7.182279] usb 3-1: new high-speed USB device number 2 using dwc2 [ 7.872295] usb 3-1.4: new full-speed USB device number 3 using dwc2 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment raspi -- Raspberry Pi - Ubuntu Jammy - OTG USB Not Working https://bugs.launchpad.net/bugs/1973648 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1971699] Re: disable Intel DMA remapping by default
A user has reported extensive performance issues with a Lenovo Thinkpad X1 Extreme Gen 2 laptop computer, in bug 1973434. The user reports video playback hangs, browser hangs and virtual machines hanging. Their dmesg indicates the system has 2x IOMMUs and there are 25 groups being configured. They tested "intel_iommu=off", and the performance issues are no longer seen. -- 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/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi Henning, That is great news that "intel_iommu=off" on the kernel command line did the trick. You can follow this bug to get updates on when we will be disabling IOMMU by default in the 5.15 kernel. It should be soon, the patches are already submitted, and reviewed by the kernel team. The next step is for the patch to be applied to the git tree and the next kernel update built. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699 I'll let you know once there is a kernel in -proposed with IOMMU disabled. The patches missed this current SRU cycle, and will be in the next one, so it might be in a few weeks / months time. Thanks, Matthew -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To
[Kernel-packages] [Bug 1973676] 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 1973676 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/1973676 Title: flickering and black screen from boot time, no more display after 22.04 upgrade Status in linux package in Ubuntu: Incomplete Bug description: On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading to 22.04 from 21.10, the display goes to some flickering lines in black and grey or colors (remember the artifacts on Amstrad CPC or C64 when loading from a tape? Same here...). After the initial grub menu, the kernel loads and boots. There are a few lines of log when the screen is in text mode. As soon as the plymouth screen comes in, the screen starts flickering massively. Nothing appeared on the screen except horizontal lines. I have an encrypted partition, so I type in the password and then the screen goes to flickering lines in color when Wayland starts. I tried different kernels: - 5.17.8: failed - 5.15.x: all failed (from Ubuntu 22.04) - 5.13.19: works and back to normal I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series I temporarily solved it by downgrading to 5.13.19 from ubuntu mainline on a newly updated ubuntu 22.04! But it seems the bug affects all the kernels. It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 Info: Description: Ubuntu 22.04 LTS Release: 22.04 linux-image-5.15.0-30-generic: Installed: 5.15.0-30.31 Candidate: 5.15.0-30.31 Version table: *** 5.15.0-30.31 500 500 http://au.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
done in Bug #1973676 Thanks Daniel -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973676] [NEW] flickering and black screen from boot time, no more display after 22.04 upgrade
Public bug reported: On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading to 22.04 from 21.10, the display goes to some flickering lines in black and grey or colors (remember the artifacts on Amstrad CPC or C64 when loading from a tape? Same here...). After the initial grub menu, the kernel loads and boots. There are a few lines of log when the screen is in text mode. As soon as the plymouth screen comes in, the screen starts flickering massively. Nothing appeared on the screen except horizontal lines. I have an encrypted partition, so I type in the password and then the screen goes to flickering lines in color when Wayland starts. I tried different kernels: - 5.17.8: failed - 5.15.x: all failed (from Ubuntu 22.04) - 5.13.19: works and back to normal I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series I temporarily solved it by downgrading to 5.13.19 from ubuntu mainline on a newly updated ubuntu 22.04! But it seems the bug affects all the kernels. It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 Info: Description:Ubuntu 22.04 LTS Release:22.04 linux-image-5.15.0-30-generic: Installed: 5.15.0-30.31 Candidate: 5.15.0-30.31 Version table: *** 5.15.0-30.31 500 500 http://au.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci.log" https://bugs.launchpad.net/bugs/1973676/+attachment/5590180/+files/lspci.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/1973676 Title: flickering and black screen from boot time, no more display after 22.04 upgrade Status in linux package in Ubuntu: New Bug description: On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading to 22.04 from 21.10, the display goes to some flickering lines in black and grey or colors (remember the artifacts on Amstrad CPC or C64 when loading from a tape? Same here...). After the initial grub menu, the kernel loads and boots. There are a few lines of log when the screen is in text mode. As soon as the plymouth screen comes in, the screen starts flickering massively. Nothing appeared on the screen except horizontal lines. I have an encrypted partition, so I type in the password and then the screen goes to flickering lines in color when Wayland starts. I tried different kernels: - 5.17.8: failed - 5.15.x: all failed (from Ubuntu 22.04) - 5.13.19: works and back to normal I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series I temporarily solved it by downgrading to 5.13.19 from ubuntu mainline on a newly updated ubuntu 22.04! But it seems the bug affects all the kernels. It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 Info: Description: Ubuntu 22.04 LTS Release: 22.04 linux-image-5.15.0-30-generic: Installed: 5.15.0-30.31 Candidate: 5.15.0-30.31 Version table: *** 5.15.0-30.31 500 500 http://au.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Team is working on getting the required GPU setup. -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921649] Re: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install.
Test kernel can be found here: https://people.canonical.com/~khfeng/lp1932069/ -- 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/1921649 Title: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install. Status in linux package in Ubuntu: Expired Bug description: Just installed Ubuntu 20.10 in a new Lenovo Ideapad S145 82DJBR and touchpad does not work. It's not detected as seen here: $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: netto 1359 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 17:30:14 2021 InstallationDate: Installed on 2021-03-20 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82DJ ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=8f45bc43-cd22-4cfa-83ee-4cb09fd58f0c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2020 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:br1.48:efr1.48:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 82DJ dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
Test kernel can be found here: https://people.canonical.com/~khfeng/lp1932069/ -- 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932069] Re: Touchpad not working at all
Test kernel can be found here: https://people.canonical.com/~khfeng/lp1932069/ -- 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/1932069 Title: Touchpad not working at all Status in linux package in Ubuntu: Confirmed Bug description: Notebook Lenovo BS-145 15 HL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cesar 1314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 16:36:11 2021 InstallationDate: Installed on 2021-06-15 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 005: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82HB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=UUID=2ff10f98-8e1f-42ac-98b7-284459b8d285 ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo BS145-15IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL: dmi.product.family: BS145-15IIL dmi.product.name: 82HB dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL dmi.product.version: Lenovo BS145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973610] 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973610] Re: Bluetooth will not stay on or connect to devices when on
For the USB dongle there are kernel messages: [ 34.065571] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 34.065744] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21e8.hcd' [ 34.065757] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21e8.hcd' ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973610] Re: Bluetooth will not stay on or connect to devices when on
We haven't had any bug reports like this that weren't hardware-specific. Maybe to avoid confusion here we should choose just one Bluetooth chip. Either the USB dongle (Broadcom Corp. BCM20702A0) or the internal chip (Intel AX210/AX211/AX411). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
The acpi_call is totally unnecessary. What's the purpose? For more powersaving? -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks. This means: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG 3005: BUG 3006: NO BUG There are only 5 patches between 3005 and 3006 so one of them is the problem. You can see the list of patches here: https://pastebin.canonical.com/p/TkvDGcfHWk/plain/ Only one of them seems related to sata which is "ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile" So maybe this is the one. Please test kernel 3007 from here: https://kernel.ubuntu.com/~kmously/kernel-kmously-3b63e74-Mkii/ If this fails, then this will be the last kernel we have to test. Please make sure you are running version 3007. Thanks -- 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965618] Re: linux-azure: Focal 5.4 arm64 support
The 5.4.0-1075-azure and newer kernels are broken in that the VM can easily panic when the Mellanox VF NIC is removed and added due to Azure host servicing events or the below manual "unbind/bind" test (here the GUID can be different in different VMs): for i in `seq 1 1000`; do cd /sys/bus/vmbus/drivers/hv_pci; echo abdc2107-402e-4704-8c88-c2b850696c3c > unbind; echo abdc2107-402e-4704-8c88-c2b850696c3c > bind; done A sample panic call-trace is: [ 107.359954] kernel BUG at /build/linux-azure-5.4-4I3kFs/linux-azure-5.4-5.4.0/mm/slub.c:4020! [ 107.363858] invalid opcode: [#1] SMP NOPTI [ 107.365870] CPU: 0 PID: 334 Comm: kworker/0:2 Not tainted 5.4.0-1077-azure #80~18.04.1-Ubuntu [ 107.369589] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 107.373811] Workqueue: events vmbus_onmessage_work [ 107.375909] RIP: 0010:kfree+0x1d2/0x240 … [ 107.413789] Call Trace: [ 107.414867] kobject_uevent_env+0x1b5/0x7e0 [ 107.416747] kobject_uevent+0xb/0x10 [ 107.418327] device_release_driver_internal+0x191/0x1c0 [ 107.420653] device_release_driver+0x12/0x20 [ 107.422523] bus_remove_device+0xe1/0x150 [ 107.424279] device_del+0x167/0x380 [ 107.425824] device_unregister+0x1a/0x60 [ 107.427536] vmbus_device_unregister+0x27/0x50 [ 107.429528] vmbus_onoffer_rescind+0x1d0/0x1f0 [ 107.431474] vmbus_onmessage+0x2c/0x70 [ 107.433104] vmbus_onmessage_work+0x22/0x30 [ 107.434919] process_one_work+0x209/0x400 [ 107.436661] worker_thread+0x34/0x40 It turns out there is a bug in https://git.launchpad.net/~canonical- kernel/ubuntu/+source/linux-azure/+git/bionic/commit/?id=16a3c750a78d8, which misses the second hunk of the upstream patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=877b911a5ba0. Please apply the below patch to fix the issue: --- a/drivers/pci/controller/pci-hyperv.c +++ b/drivers/pci/controller/pci-hyperv.c @@ -3653,7 +3653,7 @@ static int hv_pci_remove(struct hv_device *hdev) hv_put_dom_num(hbus->bridge->domain_nr); - free_page((unsigned long)hbus); + kfree(hbus); return ret; } BTW, please apply this patch as well (Note: this patch is not really required as it's only for error handling path, which is usually unlikely): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=42c3d41832ef4fcf60aaa6f748de01ad99572adf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1965618 Title: linux-azure: Focal 5.4 arm64 support Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] Focal linux-azure does not support arm64 [Fix] Backport/cherry-pick approximately 100 patches to support arm64 on hyperv [Where things could go wrong] A number of the patches reorganize hyperv CPU support. Therefore amd64 could be affected. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1965618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor
It looks like you have copied someone else's log from an unrelated bug? That shows bug 1717170 and bug 1965820. We don't need to discuss those here. -- 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/1970043 Title: [amdgpu] freeze occurs when wayland is connected to a second monitor Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I didn't encounter this bug with ubuntu 21.10 and when I tried to use x11 in 22.04 everything was fine, so it seems to be related to mutter42. And my computer is an amd 47 4800u machine and should only have one integrated graphics card ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 24 00:38:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973297] Re: HP Probook 450 G8 model T87 support in kernel
Please send the patch to alsa mailing list. -- 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/1973297 Title: HP Probook 450 G8 model T87 support in kernel Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP Probook 450 G8 model T87 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] Hewlett-Packard released this year new submodels for some G8 models of laptops and changed subsystem PCI ID for these new submodels. HP published special information about this in the next document: https://support.hp.com/us-en/document/ish_5789324-5789376-16 For example, even HP Probook 450 G8 model listed in sound/pci/hda/patch_realtek.c, in the laptop with recent T87 submodel audio/mic mute LEDs not working because of changed subsystem PCI ID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
David, please open a new bug for the above. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Half-related to this bug but worth mentioning it because it is certainly linked to it. On a HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), the trick with GRUB_CMDLINE_LINUX_DEFAULT. The problem is more serious here because the screen flickers and goes to black, purple, green, entirely, immediately after the boot (so basically when the kernel presumably changes the graphics mode) I tried different kernels: - 5.17.8: failed - 5.15.x: all failed (from Ubuntu 22.04) - 5.13.19: works and back to normal So the problem is > 5.13.x series -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967493] Re: pl2303 serial adapter not recognized
> If the issue still exist, please report this issue to linux- u...@vger.kernel.org, indicating the kernel version and attach the lsusb -v output for this device. Done: https://lore.kernel.org/linux- usb/cajixrzqf4a9-zkzdgwxicc_bpfdzve9qqgmkio7xestoxub...@mail.gmail.com/T/#u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1967493 Title: pl2303 serial adapter not recognized Status in linux-signed-hwe-5.13 package in Ubuntu: Incomplete Bug description: Hi After upgrading the Linux kernel from 5.11.0-27 to 5.13.0-37 a device that uses a pl2303 usb serial chip no longer works. This seems very similar to bug 1959110, and according to that it should be fixed, but somehow it's not. # uname -a Linux GAU23LD04 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # journalctl -b -k -g pl2303 -o cat usbcore: registered new interface driver pl2303 usbserial: USB Serial support registered for pl2303 pl2303 1-12:1.0: pl2303 converter detected pl2303 1-12:1.0: unknown device type, please report to linux-...@vger.kernel.org # udevadm info /sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 P: /devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 L: 0 E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 E: DEVTYPE=usb_interface E: PRODUCT=67b/2303/300 E: TYPE=0/0/0 E: INTERFACE=255/0/0 E: MODALIAS=usb:v067Bp2303d0300dc00dsc00dp00icFFisc00ip00in00 E: SUBSYSTEM=usb E: USEC_INITIALIZED=56177916 E: ID_VENDOR_FROM_DATABASE=Prolific Technology, Inc. E: ID_MODEL_FROM_DATABASE=PL2303 Serial Port E: ID_PATH=pci-:00:14.0-usb-0:12:1.0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_12_1_0 E: ID_MM_TTY_MANUAL_SCAN_ONLY=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1967493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error
** Changed in: juju Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error Status in OpenStack RabbitMQ Server Charm: Invalid Status in juju: In Progress Status in ubuntu-fan package in Ubuntu: New Bug description: Hi, Using manual provider on top of VMWare. Juju: 2.9.14 VM: Focal Containers: Bionic I've noticed that, in a given Focal host, 2x Bionic containers may have different behavior: one successfully completes cloud-init whereas the other fails. The failed container errors at "apt update" in cloud- init with: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Something wicked happened resolving 'PROXY_IP:' (-9 - Address family for hostname not supported) (Likely this is the line where it breaks: https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436) Failed container, full cloud-init-output.log: https://pastebin.canonical.com/p/hKNw49mvJP/ Successful container, full cloud-init-output.log: https://pastebin.canonical.com/p/P6MZdQPrWd/ Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/ I can see that, on the host, dnsmasq served the FAN IP to the broken container after the "apt-update" was called. - FAILED CONTAINER -: Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.198 00:16:3e:da:dd:c4 apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds. - SUCCESSFUL CONTAINER -: Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.253 00:16:3e:d7:6b:ef apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds. In the case of the Failed Container, the DHCPOFFER arrived 1s after the "apt update" was requested, whereas the Successful Container logged a DHCPOFFER 30s before the "apt update". To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
Thanks - I thought it was related - I have opened a new ticket: https://bugs.launchpad.net/ubuntu/+bug/1973648 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Released Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848831]
Is there an update to this? Did anybody get the AX200 card working in a x16 slot? I had no luck with kernel 5.16.12 (bullseye-backports) and firmware- iwlwifi 20210818-1 Thanks. -- 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/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi Status in Gaming Edition: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC uname -a Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The card is detected OK as dmesg shows, however the card's firmware fails immediately after loading (see dmesg output below) and wifi doesn't work at all. Big disappointment since the AX200 chip was supposed to be supported on 19.10. Ubuntu includes two ax200 firmware versions, version 48 loads by default in my system (and fails). I tried version 46 (by renaming the version 48 file) and it failed in the exact same manner $ ls /lib/firmware/iwlwifi-cc-* /lib/firmware/iwlwifi-cc-a0-46.ucode /lib/firmware/iwlwifi-cc-a0-48.ucode The card's Bluetooth functionality is also detected and it works fine. It's just the wifi FW loading what seems broken in ubuntu's 5.3 kernel. $ rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no ~$ dmesg | grep iwl [ 12.312443] iwlwifi :01:00.0: enabling device ( -> 0002) [ 12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM [ 12.321102] iwlwifi :01:00.0: Found debug configuration: 0 [ 12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [ 12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM [ 12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [ 13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired. [ 13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414910] iwlwifi :01:00.0: Status: 0x, count: 6 [ 13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0 [ 13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0 [ 13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2 [ 13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1 [ 13.414917] iwlwifi :01:00.0: 0x1000 | data2 [ 13.414917] iwlwifi :01:00.0: 0xF000 | data3 [ 13.414918] iwlwifi :01:00.0: 0x | beacon time [ 13.414919] iwlwifi :01:00.0: 0x795F | tsf low [ 13.414919] iwlwifi :01:00.0: 0x | tsf hi [ 13.414920] iwlwifi :01:00.0: 0x | time gp1 [ 13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2 [ 13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type [ 13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major [ 13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor [ 13.414923] iwlwifi :01:00.0: 0x0340 | hw version [ 13.414924] iwlwifi :01:00.0: 0x18C89000 | board version [ 13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd [ 13.414925] iwlwifi :01:00.0: 0x0002 | isr0 [ 13.414926] iwlwifi :01:00.0: 0x | isr1 [ 13.414926] iwlwifi :01:00.0: 0x08F2 | isr2 [ 13.414927] iwlwifi :01:00.0: 0x00CC | isr3 [ 13.414928] iwlwifi :01:00.0: 0x | isr4 [ 13.414928] iwlwifi :01:00.0: 0x | last cmd Id [ 13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event [ 13.414930] iwlwifi :01:00.0: 0x | l2p_control [ 13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration [ 13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match [ 13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel [ 13.414933] iwlwifi :01:00.0: 0x | timestamp [ 13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler [ 13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414975] iwlwifi :01:00.0: Status: 0x, count: 7 [ 13.414976] iwlwifi :01:00.0: 0x201000A3 | ADVANCED_SYSASSERT [ 13.414976] iwlwifi :01:00.0: 0x | umac branchlink1 [ 13.414977] iwlwifi :01:00.0:
[Kernel-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
for https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 i'm a bit lost! What do I have to do with the 3 available files? -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 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 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
I already tried to apply https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834 but this doesn't help. I also tried https://ubuntuforums.org/showthread.php?t=2474436 but doesn't help neither -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 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 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
here is the result of the journalctl ** Attachment added: "result of the journalctl command" https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+attachment/5590157/+files/journalctl.odt -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 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 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945011] Re: kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS partitions
I suggest retesting this based on the Jammy ISO. -- 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/1945011 Title: kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS partitions Status in linux package in Ubuntu: Confirmed Bug description: On this computer with ext4, FAT and NTFS partitions : I successfully booted from the Live CD of Ubuntu Desktop 21.10 (Impish Indri) beta with full graphics. I started the ubiquity graphical interface and successfully completed the first screens. But on the 'Updates and other software screen', after clicking on Continue, ubiquity does NOT show the next screen (which on previous versions was Partitioning). ubiquity seems to be blocked inside partman. I attach the partman log file. syslog contains following message : kernel BUG at fs/inode.c:1676! Notably, this kernel bug message is preceeded by 2 warnings : WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1610 blkdev_put+0x130/0x140 WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1576 __blkdev_put+0x1dc/0x1f0 Thanks in advance for investigating and correcting this issue. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6322 F pulseaudio /dev/snd/controlC1: ubuntu 6322 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 21:25:08 2021 IwConfig: lono wireless extensions. enp2s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuSKU:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog
I retested this today using my same failing VM. Test scenario: * hardware: kvm with windows 10 on disk, UEFI * boot Ubiquity ISO * "try ubuntu" * launch installer * press the "continue" button until one of the following happens: * "installation type" screen shows or * hang at the "updates and other software screen" - wait 1 minute and look for ntfsresize in process state 'D' Results: * Impish: 3/10 success rate ("installation type" screen reached) * Jammy: 10/10 success rate Based on this I consider this fixed in Jammy. ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: ntfs-3g (Ubuntu Jammy) Status: Confirmed => Invalid ** Changed in: ubiquity (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => Invalid ** Changed in: ntfs-3g (Ubuntu Kinetic) Status: Confirmed => Invalid ** Changed in: ubiquity (Ubuntu Kinetic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946828 Title: ntfsresize hang and call traces in syslog Status in linux package in Ubuntu: Invalid Status in ntfs-3g package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in ntfs-3g source package in Jammy: Invalid Status in ubiquity source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Status in ntfs-3g source package in Kinetic: Invalid Status in ubiquity source package in Kinetic: Invalid Bug description: Attempting to boot the impish final iso on my kvm VM setup with a windows 10 install on the virtual disk. The install process hangs at the "updates and other software" screen, apparently on a ntfsresize call. Mind you, this is before I have chosen disks to partition - I'm at the step where I can choose a Normal or Minimal installation. While this is not a 100% reproduction rate issue, the rate seems high - above 50% I would guess. If I try to quickly click thru the installer on boot it might be a little more likely. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4609 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 02:40:56 2021 IwConfig: lono wireless extensions. enp1s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973633] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590135/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590140/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590138/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590136/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590126/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590137/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590133/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1973633] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590132/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590131/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590141/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1973633] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590139/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590134/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590130/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590129/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590128/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590127/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590124/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590123/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590122/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590125/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
apport information ** Tags added: apport-collected jammy ** Description changed: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-05-08 (8 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-27-generic N/A + linux-backports-modules-5.15.0-27-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3 + Tags: jammy + Uname: Linux 5.15.0-27-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/28/2021 + dmi.bios.release: 1.5 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: E15CKAMS.105 + dmi.board.asset.tag: Default string + dmi.board.name: MS-15CK + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:1.0 + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 10 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: + dmi.product.family: Delta + dmi.product.name: Delta 15 A5EFK + dmi.product.sku: 15CK.1 + dmi.product.version: REV:1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590121/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in
[Kernel-packages] [Bug 1973633] 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 1973633 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Incomplete Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family:
[Kernel-packages] [Bug 1973633] [NEW] wrong acpi_call sent at boot, how to disable discrete graphic card?
Public bug reported: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: acpi graphics grub hybrid ** Attachment added: "outputs of 'cat /proc/version_signature', 'sudo lspci -vnvn', 'less /boot/grub/grub.cfg', 'sudo apt list | grep -i gpu', 'sh get-acpi-info.sh' (see https://launchpad.net/~hybrid-graphics-linux)" https://bugs.launchpad.net/bugs/1973633/+attachment/5590120/+files/version_lscpi_grub.sfg_aptlist_get-acpi-info.zip -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Incomplete Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional
[Kernel-packages] [Bug 1973626] [NEW] [BlueField] linux-libc-dev corresponding to the linux-image-5.4.0-1035-bluefield is not available
Public bug reported: linux-libc-dev corresponding to the linux-image-5.4.0-1035-bluefield is not available Here is the "linux-libc-dev" which is available on BlueField DPU: # dpkg --list linux-libc-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-- ii linux-libc-dev:arm64 5.4.0-110.124 arm64Linux Kernel Headers for development But this package is not in sync with linux-bluefield. Please provide corresponding "linux-libc-dev" with every SRU kernel. ** 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/1973626 Title: [BlueField] linux-libc-dev corresponding to the linux- image-5.4.0-1035-bluefield is not available Status in linux-bluefield package in Ubuntu: New Bug description: linux-libc-dev corresponding to the linux-image-5.4.0-1035-bluefield is not available Here is the "linux-libc-dev" which is available on BlueField DPU: # dpkg --list linux-libc-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-- ii linux-libc-dev:arm64 5.4.0-110.124 arm64Linux Kernel Headers for development But this package is not in sync with linux-bluefield. Please provide corresponding "linux-libc-dev" with every SRU kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1973626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
** Description changed: - State the component where the Bug is occuring: - kernel + SRU Justification: + == + + [Impact] + + * The kernel crashed under load with a null pointer issue in nfs code: + [556585.270959] Krnl Code:#: illegal + >0002: illegal +0004: illegal +0006: illegal +0008: illegal +000a: illegal +000c: illegal +000e: illegal + [556585.270967] Call Trace: + [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc]) + [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs] + [556585.271004] [<03ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs] + [556585.271014] [<03ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs] + [556585.271016] [<0028165944a8>] new_sync_write+0x118/0x1b0 + [556585.271017] [<002816594ee0>] vfs_write+0xb0/0x1b0 + [556585.271019] [<002816596a1e>] ksys_pwrite64+0x7e/0xc0 + [556585.271021] [<002816bb26b2>] system_call+0x2a6/0x2c8 + + * Several dumps were generated and shared with Canonical. + + * Analysis (done by kernel and SEG) point to refcount leaks fixed, + that are already fixed in the following commit/fix: + + [Fix] + + * ca05cbae2a0468e5d78e9b4605936a8bf5da328b ca05cbae2a04 "NFS: Fix up + nfs_ctx_key_to_expire()" + + [Test Case] + + * There is unfortunately no reproducer or trigger available for this + issue. + + * It just happens now and then under higher load. + + * A patched kernel (focal 5.4 and bionic 5.4-hwe) were created and + ran for more than a week in a special staging environment (at IBM) + without further crashes. + + * Hence the test and verification will be done by the IBM Z team. + + [Where problems could occur] + + * The inode handling can become broken, in case the changes + on the pointers are erroneous. + + * Problems with the authentication and/or the credentials could occur + due to the modifications in put_rpccred, rpc_cred and rpc_auth. + + * The expiration of the cached credentials could be harmed as well, + due to the changes in nfs_ctx_key_to_expire. + + * The different pointer arithmetic may cause further issues - wrong + or null pointer references. + + * Positive is that the original commit was brought upstream by nfs + experts. + + * A patched test kernel sustained day long runs under load in a staging + and test environment. + + * The author of the upstream commit/patch is well known in the NFS area. + + [Other] + + * The Salesforce Case Number 00334334 is associated with this bug. + + * Commit ca05cbae2a04 was upstream accepted with 5.16-rc1. + + * But commit ca05cbae2a04 was unfortunately not tagged as stable, + hence it was not picked automatically. + + * Since kinetic's (22.10) target kernel is 5.18, + it will have the patch included, + hence no dedicated PATCH request for kinetic. + + __ + + State the component where the Bug is occurring: + kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - - - Is the system sitting at a debugger (kdb, or xmon)? No - + - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - - - Are there any custom patches installed? Yes + - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - - - Is there any special hardware that may be relevant to this problem? Yes + - Is there any special hardware that may be relevant to this problem? Yes We are running with mlx (cloud network adapters) installed. - - - Is access information for the machine the problem was found on available? Yes - - - - Is the bug occuring in a userspace application? No - + - Is access information for the machine the problem was found on + available? Yes + + - Is the bug occuring in a userspace application? No - Was a stack trace produced? Yes This is what mention in first comment by @Boris Barth - - Did the system produce an Oops message on the console? Yes - [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP + [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP [556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth
Re: [Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi Matthew, Yes, that looks very good! have to dig a bit deeper and do some more actual work, but at the first glance I can do the things that I described above where impossible! Thanks a lot! I tried to build 5.17.7 with the 22.04 config and make olddefconfig and then bindeb-pkg, but it took extremely much longer than with the 20.10 config, and after about 2 hours i saw it still hanging on dpkg-deb for the dbg package and even half an hour later not finish. I will try again tonite, probably doing a full "mrproper" before and letting it run over night to see if it really hangs or just takes extremely long. Actually I cant imagine why a dpkg-deb should hang, but I also saw now clues what it could be. Cheers, Henning -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
[Kernel-packages] [Bug 1965241] Re: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
** Tags added: servcert-359 -- 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/1965241 Title: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973620] Re: prevent kernel panic with overlayfs + shiftfs
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Bug description: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973620] 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 1973620 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Impish) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973620] [NEW] prevent kernel panic with overlayfs + shiftfs
Public bug reported: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470
[Kernel-packages] [Bug 1973463] 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 1973463 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/1973463 Title: ZFS kernel null pointer dereference Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10
[Kernel-packages] [Bug 1973463] Re: ZFS kernel null pointer dereference
** Package changed: zfs-linux (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973463 Title: ZFS kernel null pointer dereference Status in linux package in Ubuntu: New Bug description: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1250.063198] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1250.063206] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1250.063211] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1250.063215] RDX: RSI: c1494df0 RDI: 0002 [ 1250.063218] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1250.063222]
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Sujith - Can you update this bug. -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973394] 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 1973394 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/1973394 Title: Can't find integrated camera in Ubuntu 22.04 on Lenovo Status in linux package in Ubuntu: Incomplete Bug description: Dual boot, Win 10 & Ubuntu 22.04. Camera works on Win but not discoverable on Ubuntu 22.04 Never any image or video in cheese F6 does not turn it on in Cheese. Used synaptic, nothing broken. Checked for driver, nothing available. Boot from USB (ie install iso) Cheese does not work in "try Ubuntu" mode, ie cheese cannot find camera. I have tried other programs that use the camera & none work. Looks like a driver is missing to me but I can't find one to add. I know the camera is there & working in Windows. Something is missing for it to work in Ubuntu 22.04 1)Ubuntu 22.04 LTS 2)Cheese 3)expected camera to open 4)Message "there was an error playing video from the webcam" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973394] Re: Can't find integrated camera in Ubuntu 22.04 on Lenovo
** Package changed: cheese (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973394 Title: Can't find integrated camera in Ubuntu 22.04 on Lenovo Status in linux package in Ubuntu: New Bug description: Dual boot, Win 10 & Ubuntu 22.04. Camera works on Win but not discoverable on Ubuntu 22.04 Never any image or video in cheese F6 does not turn it on in Cheese. Used synaptic, nothing broken. Checked for driver, nothing available. Boot from USB (ie install iso) Cheese does not work in "try Ubuntu" mode, ie cheese cannot find camera. I have tried other programs that use the camera & none work. Looks like a driver is missing to me but I can't find one to add. I know the camera is there & working in Windows. Something is missing for it to work in Ubuntu 22.04 1)Ubuntu 22.04 LTS 2)Cheese 3)expected camera to open 4)Message "there was an error playing video from the webcam" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1037.41 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-meta source package in Focal: Invalid Status in linux-meta-oem source package in Focal: In Progress 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 backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-meta source package in Jammy: In Progress Status in linux-meta-oem source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed
[Kernel-packages] [Bug 1973394] [NEW] Can't find integrated camera in Ubuntu 22.04 on Lenovo
You have been subscribed to a public bug: Dual boot, Win 10 & Ubuntu 22.04. Camera works on Win but not discoverable on Ubuntu 22.04 Never any image or video in cheese F6 does not turn it on in Cheese. Used synaptic, nothing broken. Checked for driver, nothing available. Boot from USB (ie install iso) Cheese does not work in "try Ubuntu" mode, ie cheese cannot find camera. I have tried other programs that use the camera & none work. Looks like a driver is missing to me but I can't find one to add. I know the camera is there & working in Windows. Something is missing for it to work in Ubuntu 22.04 1)Ubuntu 22.04 LTS 2)Cheese 3)expected camera to open 4)Message "there was an error playing video from the webcam" ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- Can't find integrated camera in Ubuntu 22.04 on Lenovo https://bugs.launchpad.net/bugs/1973394 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes (fheimes) ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968096 Title: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: State the component where the Bug is occuring: kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - Is there any special hardware that may be relevant to this problem? Yes We are running with mlx (cloud network adapters) installed. - Is access information for the machine the problem was found on available? Yes - Is the bug occuring in a userspace application? No - Was a stack trace produced? Yes This is what mention in first comment by @Boris Barth - Did the system produce an Oops message on the console? Yes [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP [556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac [556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls] [556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G DOE 5.4.0-90-generic #101-Ubuntu [556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR) [556585.270948] Krnl PSW : 0704d0018000 0002 (0x2) [556585.270951]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [556585.270953] Krnl GPRS: 03e010ebbcf8 0071c45e1ec0 [556585.270954] 002816f7b18c 0078dd36a4a0 00713a62f718 [556585.270955] 03e010ebbcf8 0068 0071c45e1ec0 [556585.270957]006090a12200 0c40 03ff80d6fb54 03e010ebbbf0 [556585.270959] Krnl Code:#: illegal >0002: illegal 0004: illegal 0006: illegal 0008: illegal 000a: illegal
[Kernel-packages] [Bug 1973610] [NEW] Bluetooth will not stay on or connect to devices when on
Public bug reported: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in bluez package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
v1 upstream got rejected, submitted v2 now https://lore.kernel.org/linux- bluetooth/20220516103329.516952-1-dimitri.led...@canonical.com/ -- 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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969432] Re: 5.17 kernel won't load mok, so it refused to load dkms signed by mok
** Description changed: + lp:1972802 + Steps to reproduce: 1. enroll mok, and use the mok to sign dkms 2. make sure secure boot is on, and boots with kernel 3. load the kernel by either modprobe or insmod. Expected: the kernel module can be loaded. Actually: the kernel module can't be loaded. Failed kernel: 5.17.0-1003-oem Passed kernel: 5.15.0-25-generic With 5.17 kernel, using command "dmesg | grep 509", I can't see the mok key. With 5.15 kernel above, I can see the mok key is loaded like: [0.896168] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [0.896283] integrity: Loaded X.509 cert 'ubuntu Secure Boot Module Signature key: 670bc7d76f65d9cfc786f5501de6af89bf3973e7' -- 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/1969432 Title: 5.17 kernel won't load mok, so it refused to load dkms signed by mok Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Bug description: lp:1972802 Steps to reproduce: 1. enroll mok, and use the mok to sign dkms 2. make sure secure boot is on, and boots with kernel 3. load the kernel by either modprobe or insmod. Expected: the kernel module can be loaded. Actually: the kernel module can't be loaded. Failed kernel: 5.17.0-1003-oem Passed kernel: 5.15.0-25-generic With 5.17 kernel, using command "dmesg | grep 509", I can't see the mok key. With 5.15 kernel above, I can see the mok key is loaded like: [0.896168] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [0.896283] integrity: Loaded X.509 cert 'ubuntu Secure Boot Module Signature key: 670bc7d76f65d9cfc786f5501de6af89bf3973e7' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
Thank you for your bug report. Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart, try to connect and share the 'journalctl -b 0' log from the system? It would also be worth trying if https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 makes a difference for you, could be the same issue with legacy server ** Changed in: wpa (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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 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 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
This is unrelated. Please open a new ticket. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Released Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
Hi Running RPI4B with Jammy and cannot get the USB Ports to work. uname -r output: 5.15.0-1006-raspi dmesg output: 1.842505] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.842665] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.895846] dwc2 fe98.usb: DWC OTG Controller [1.895873] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [1.895904] dwc2 fe98.usb: irq 21, io mem 0xfe98 [1.896089] usb usb3: Manufacturer: Linux 5.15.0-1006-raspi dwc2_hsotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Released Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [
[Kernel-packages] [Bug 1973574] 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/1973574 Title: The system has become much choppier and no audio is being heard Status in linux package in Ubuntu: Confirmed Bug description: The system has been getting choppy and the last upgrade is a failure.Also the sound is not coming even though the video is being played. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-110-generic 5.4.0-110.124 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 12:59:42 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-110-generic root=UUID=5b9e5e8a-d7f3-42fd-9895-dd751e39ce69 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-110-generic N/A linux-backports-modules-5.4.0-110-generic N/A linux-firmware 1.187.30 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970957] Re: suspend problem
X1 Carbon 6th Gen same problem. Running 22.04 MATE, so not using Wayland. Does not happen all the time, but very annoying. Please advise if you need any more information -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973574] Re: The system has become much choppier and no audio is being heard
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1973574 Title: The system has become much choppier and no audio is being heard Status in linux package in Ubuntu: Confirmed Bug description: The system has been getting choppy and the last upgrade is a failure.Also the sound is not coming even though the video is being played. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-110-generic 5.4.0-110.124 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 12:59:42 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-110-generic root=UUID=5b9e5e8a-d7f3-42fd-9895-dd751e39ce69 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-110-generic N/A linux-backports-modules-5.4.0-110-generic N/A linux-firmware 1.187.30 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922
** Tags added: verification-done-focal ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1958004] Re: intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1968892] Re: Micmute LED support for Zbook Fury 16 G9
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1969407] Re: DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1969771] Re: Fix beacon loss for rtl8821ce on certain platforms
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget:
[Kernel-packages] [Bug 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
Tested on hardware and run s2idle stress test 30 times OK. ** Tags added: verification-done-focal -- 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/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor
This looks like a related question https://github.com/micheleg/dash-to- dock/issues/1705 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1705 https://github.com/micheleg/dash-to-dock/issues/1705 -- 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/1970043 Title: [amdgpu] freeze occurs when wayland is connected to a second monitor Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I didn't encounter this bug with ubuntu 21.10 and when I tried to use x11 in 22.04 everything was fine, so it seems to be related to mutter42. And my computer is an amd 47 4800u machine and should only have one integrated graphics card ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 24 00:38:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Great! I'm just a regular user, but I think if you got it to work you don't need to install 22.04. Even if you do, you'll probably need these options in grub anyway. I am currently on 22.04 and I have to use "i915.enable_dc=0". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)
With input from our customer, I have created a very simple NPM project to test out the sound / virtual MIDI support: https://github.com/CircleCI-Public/midi-test I'm getting the expected failures with it on the latest 22.04 AMI, so I'll try the new kernel next. $ node . ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory MidiOutAlsa::initialize: error creating ALSA sequencer client object. ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory MidiInAlsa::initialize: error creating ALSA sequencer client object. ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory MidiOutAlsa::initialize: error creating ALSA sequencer client object. ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory MidiInAlsa::initialize: error creating ALSA sequencer client object. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1970586 Title: No sound support on Linux AWS kernel (but supported on GCP) Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Jammy: In Progress Bug description: In GCP images it is possible to create virtual MIDI devices and generally do stuff like audio routing, etc. At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of our customers use this functionality to test audio equipment in their CI runs. Unfortunately they cannot run their tests on our AWS based VMs, as there is no sound support compiled into the kernel on the AWS kernel and images. See the package listings for the other kernels for, e.g. the loopback driver: ``` linux-modules-extra-5.4.0-99-generic: /lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko linux-modules-extra-5.8.0-1031-oracle: /lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko linux-modules-extra-5.8.0-1032-gcp: /lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko ``` We would love to be able to install the sound drivers (especially snd- aloop) with the linux-modules-extra-aws package, but currently cannot, and obviously do not want to start running our own kernels, as then we lose the immediacy of kernel patches provided upstream by Canonical. You can see the difference in the GCP: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884 and AWS kernel: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu again there. The reasoning for the removal appears to be in this commit from 2016: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
there's a regression so change it to in-progress -- 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/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU Status in HWE Next: New Status in subiquity: Invalid 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 Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: In Progress 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 Impish: Fix Released Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: 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: Invalid Bug description: [Impact] A hardware partner discovered they were unable to install Ubuntu on some servers using VROC setups. They point to this issue involving DMAR that is blocking discovery of the VROC RAID devices: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45 `git bisect` points to this offending commit ee81ee84f873 ("PCI: vmd: Disable MSI-X remapping when possible"), which disables VMD MSI remapping. The IOMMU hardware blocks the compatibility format interrupt request because Interrupt Remapping Enable Status (IRES) and Extended Interrupt Mode Enable (EIME) are enabled. Please refer to section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d spec. To fix the issue, VMD driver still enables the interrupt remapping irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem enables the interrupt remapping. [Fix] 2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU [Test Plan] 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install affected Ubuntu release on the RAID10. 3. The system hangs at "Partitions formatting 33%". [Where problems could occur] The fix itself is a very small change to drivers/pci/controller/vmd.c and problems should not occur. The root cause was discovered by the hardware partner's engineers, who tested and submitted it upstream where it was accepted and landed in 5.16. That said, I doubt this will fix 18.04.6 as it would require a respin to get the patched kernel onto the ISO. 20.04 should pick it up in ISO in 20.04.5, so there could still be the initial issue since those ISOs would be lacking the patched kernel. [Other Info] As noted, this would need to not only land in the kernel but land in the kernel in the ISO to resolve the issue in the installation process. I'll bring this back as far as Focal with the expectation that while 20.04.4 is too late, it will be present using the GA kernel in 20.04.5 later on. * Original Bug Summary: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937295/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
I tried both option in grub. It works! 16 hours without freezing. Thank you very much. I also tried ubuntu 22.04 on usb stick and it freezes. So, should I install 22.04 with the workaround ? I think it is a problem with intel cpu. Complete ref is : Description: "Intel HD Graphics" Manufacturer: Intel(R) Corporation Version: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz "Intel Corp." -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
** Attachment added: "lspci-dell-latitude-7300.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590019/+files/lspci-dell-latitude-7300.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
** Attachment added: "cpuinfo-dell-latitude-7300.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590018/+files/cpuinfo-dell-latitude-7300.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
Same issue with Dell Latitude 7300. Device detection like disks fail, apparently randomly. Some media keys don't work, Wifi was OK. Previous kernel build is fine. -- 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/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940080] Re: ubuntu-kernel-selftests.ftrace hangs on riscv64
** Summary changed: - ubuntu-kernel-selftests.ftrace fails on riscv64 + ubuntu-kernel-selftests.ftrace hangs on riscv64 ** Tags added: sru-20220509 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940080 Title: ubuntu-kernel-selftests.ftrace hangs on riscv64 Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: Confirmed Bug description: 08/12 22:10:03 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 08/12 22:10:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 08/12 22:10:45 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 08/12 22:10:51 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 08/12 22:10:56 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 08/12 22:11:01 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 08/12 22:11:06 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 08/12 22:11:11 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 08/12 22:11:15 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 08/12 22:11:16 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNSUPPORTED] 08/12 22:11:20 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events[FAIL] 08/12 22:11:21 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [UNSUPPORTED] 08/12 22:11:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 08/12 22:11:34 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [PASS] 08/12 22:11:40 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 08/12 22:11:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 08/12 22:11:51 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] 08/12 22:11:58 DEBUG| utils:0153| [stdout] # [19] Test trace_printk from module [PASS] 08/12 22:12:15 DEBUG| utils:0153| [stdout] # [20] ftrace - function graph filters with stack tracer [PASS] 08/12 22:12:24 DEBUG| utils:0153| [stdout] # [21] ftrace - function graph filters [PASS] 08/12 22:12:35 DEBUG| utils:0153| [stdout] # [22] ftrace - function pid notrace filters [PASS] 08/12 22:12:46 DEBUG| utils:0153| [stdout] # [23] ftrace - function pid filters [PASS] 08/12 22:12:54 DEBUG| utils:0153| [stdout] # [24] ftrace - stacktrace filter command [PASS] 08/12 22:13:03 DEBUG| utils:0153| [stdout] # [25] ftrace - function trace with cpumask[PASS] 08/12 22:13:28 DEBUG| utils:0153| [stdout] # [26] ftrace - test for function event triggers [FAIL] 08/12 22:13:42 DEBUG| utils:0153| [stdout] # [27] ftrace - function trace on module [PASS] ** hang, whilst a lot more test cases are expected ** I.e. the next test case result should have been # [28] ftrace - function profiling Failure: # [10] Generic dynamic event - add/remove kprobe events [FAIL] # [26] ftrace - test for function event triggers [FAIL] nothing exciting in the dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965241] Re: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965241 Title: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. [Fix] These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp