[Kernel-packages] [Bug 1954746] 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/1954746 Title: ASIX AX88179 compatible USB adapter not working Status in linux package in Ubuntu: Confirmed Bug description: Upon inserting the USB device errors can be found in dmesg. (see below) The current result: USB adapter is no longer working The expected result: USB adapter should work properly Please also note that this is my first bug report here. [ 5667.499655] ax88179_178a 2-1.3:2.0 eth0: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.541257] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541264] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.541268] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541445] ax88179_178a 2-1.3:2.1 eth1: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.585338] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.585345] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.585350] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5668.066721] usb 2-1.3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd [ 5668.237190] usb 2-1.3: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 2.00 [ 5668.237196] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5668.237199] usb 2-1.3: Product: AX88179A [ 5668.237203] usb 2-1.3: Manufacturer: ASIX [ 5668.237205] usb 2-1.3: SerialNumber: 000CFBDD [ 5668.915280] ax88179_178a 2-1.3:1.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0040: -32 [ 5669.227298] ax88179_178a 2-1.3:1.0 eth0: register 'ax88179_178a' at usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, f8:e4:3b:0c:fb:dd [ 5669.285419] ax88179_178a 2-1.3:1.0 enxf8e43b0cfbdd: renamed from eth0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arno 1964 F pulseaudio /dev/snd/controlC1: arno 1964 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 08:14:34 2021 HibernationDevice: RESUME=UUID=67bde916-af41-4b15-bcb4-599116d67df7 InstallationDate: Installed on 2018-05-18 (1306 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-21 (387 days ago) dmi.bios.date: 05/25/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.1:bd05/25/2021:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949063] Re: Add F81966 watchdog support
Hi All, I only see linux/5.11.0-43 in -proposed. I did not see 5.11.0-44 in -proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1949063 Title: Add F81966 watchdog support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.11 source package in Focal: Fix Committed Status in linux-hwe-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.11 source package in Hirsute: Invalid Status in linux-hwe-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-hwe-5.11 source package in Impish: Invalid Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-hwe-5.11 source package in Jammy: Invalid Status in linux-hwe-5.13 source package in Jammy: Invalid Bug description: [Impact] f71808e_wdt watchdog driver can't recognize F81966 chip. [Fix] AAEON provides a patch to add the ID. https://www.spinics.net/lists/kernel/msg4147351.html [Test] Testing was done on the Aaeon SSE-OPTI [Where problems could occur] Simply adding one ID, should not introduce any regressions. [Misc] This patch is for ODM project and need this to be included as soon as possible, so we submit this patch as a sauce patch before upstream merges it. BTW, Jammy already included this commit when the patch was submitted for the SRU the first time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954746] [NEW] ASIX AX88179 compatible USB adapter not working
Public bug reported: Upon inserting the USB device errors can be found in dmesg. (see below) The current result: USB adapter is no longer working The expected result: USB adapter should work properly Please also note that this is my first bug report here. [ 5667.499655] ax88179_178a 2-1.3:2.0 eth0: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.541257] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541264] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.541268] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541445] ax88179_178a 2-1.3:2.1 eth1: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.585338] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.585345] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.585350] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5668.066721] usb 2-1.3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd [ 5668.237190] usb 2-1.3: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 2.00 [ 5668.237196] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5668.237199] usb 2-1.3: Product: AX88179A [ 5668.237203] usb 2-1.3: Manufacturer: ASIX [ 5668.237205] usb 2-1.3: SerialNumber: 000CFBDD [ 5668.915280] ax88179_178a 2-1.3:1.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0040: -32 [ 5669.227298] ax88179_178a 2-1.3:1.0 eth0: register 'ax88179_178a' at usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, f8:e4:3b:0c:fb:dd [ 5669.285419] ax88179_178a 2-1.3:1.0 enxf8e43b0cfbdd: renamed from eth0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arno 1964 F pulseaudio /dev/snd/controlC1: arno 1964 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 08:14:34 2021 HibernationDevice: RESUME=UUID=67bde916-af41-4b15-bcb4-599116d67df7 InstallationDate: Installed on 2018-05-18 (1306 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-21 (387 days ago) dmi.bios.date: 05/25/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.1:bd05/25/2021:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "dmesg screenshot" https://bugs.launchpad.net/bugs/1954746/+attachment/5547460/+files/dmesg.png -- 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/1954746 Title: ASIX AX88179 compatible USB adapter not working Status in linux package in Ubuntu: Confirmed Bug description: Upon inserting the USB device errors can be found in dmesg. (see below) The current result: USB adapter is no longer working The expected result: USB adapter should work properly Please also note that this is my first bug report here. [ 5667.499655] ax88179_178a 2-1.3:2.0 eth0: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.541257] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541264] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0001: -19 [ 5667.541268] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.541445] ax88179_178a 2-1.3:2.1 eth1: unregister 'ax88179_178a' usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 5667.585338] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index 0x0002: -19 [ 5667.585345] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write reg index
[Kernel-packages] [Bug 1951424] Re: No audio after install ubuntu 21.10 on Acer swift 3
Any workaround available to fix this bug? Or I have to wait until next linux-image package update? -- 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/1951424 Title: No audio after install ubuntu 21.10 on Acer swift 3 Status in linux package in Ubuntu: Confirmed Bug description: dmesg shows below errors: (see intel-sdw lines) [3.428920] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [3.461588] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [3.482055] sof-audio-pci-intel-tgl :00:1f.3: No SoundWire machine driver found [3.482059] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [3.482061] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.482066] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [3.584389] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 1:6:0-18fab [3.584392] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [3.586144] intel-sdw intel-sdw.0: Bus clash for control word [3.586147] intel-sdw intel-sdw.0: Bus clash for data word [3.586169] intel-sdw intel-sdw.1: Bus clash for control word [3.586171] intel-sdw intel-sdw.1: Bus clash for data word [3.586227] intel-sdw intel-sdw.0: Bus clash for control word [3.586230] intel-sdw intel-sdw.1: Bus clash for control word [3.586275] intel-sdw intel-sdw.0: Bus clash for control word [3.586279] intel-sdw intel-sdw.1: Bus clash for control word [3.586342] intel-sdw intel-sdw.0: Bus clash for control word [3.586346] intel-sdw intel-sdw.1: Bus clash for control word [3.586395] intel-sdw intel-sdw.0: Bus clash for control word [3.586398] intel-sdw intel-sdw.1: Bus clash for control word [3.593087] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [3.610615] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [3.640221] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.640226] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.640228] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.640229] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [3.640230] snd_hda_codec_realtek ehdaudio0D0:inputs: [3.688338] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten [3.688344] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten [3.688440] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten [3.688444] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten [3.688447] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten [3.688450] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten [3.688452] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten [3.688456] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten [3.688460] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten [3.688463] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten [3.688468] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten [3.688471] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten [3.688475] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten [3.688482] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3 [3.688483] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4 [3.688484] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 5 [3.688485] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 6 [3.688486] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 7 [3.688487] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8 [3.707637] input: sof-hda-dsp Front Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [3.707683] input: sof-hda-dsp HDMI/DP,pcm=3 as
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1011.11)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1011.11) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944411] Re: ubuntu_bpf: build failure with kernel 5.13
This issue does not exist anymore, it's now failing with bug 1954743 ** Changed in: linux (Ubuntu) Status: Expired => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: Expired => Invalid ** Changed in: ubuntu-kernel-tests Status: Invalid => Fix Released ** Changed in: linux (Ubuntu Impish) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944411 Title: ubuntu_bpf: build failure with kernel 5.13 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: We get this failure with the ubuntu_bpf 12test886 Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' 12887 libbpf: elf: skipping unrecognized data section(5) .rodata.str1.1 12888 libbpf: elf: skipping unrecognized data section(5) .rodata.str1.1 12889 libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 12890 libbpf: elf: skipping unrecognized data section(7) .rodata.str1.1 12891 libbpf: elf: skipping unrecognized data section(8) .rodata.cst16 12892 libbpf: elf: skipping unrecognized data section(8) .rodata.str1.1 12893 libbpf: elf: skipping unrecognized data section(7) .rodata.str1.1 12894 libbpf: elf: skipping unrecognized data section(8) .rodata.str1.1 12895 libbpf: elf: skipping unrecognized data section(7) .maps.btf_map 12896 libbpf: elf: skipping unrecognized data section(7) .maps.btf_map_legacy 12897 libbpf: elf: skipping unrecognized data section(8) .rodata.str1.1 12898 libbpf: elf: skipping unrecognized data section(27) .rodata.str1.1 12899 libbpf: elf: skipping unrecognized data section(15) .rodata.str1.1 12900 libbpf: elf: skipping unrecognized data section(5) .rodata.cst16 12901 libbpf: elf: skipping unrecognized data section(27) .rodata.str1.1 12902 libbpf: elf: skipping unrecognized data section(4) .rodata.str1.1 12903 libbpf: elf: skipping unrecognized data section(7) .rodata.str1.1 12904 /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c: In function ‘test_ringbuf’: 12905 /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:105:35: error: ‘skel->maps.ringbuf’ is a pointer; did you mean to use ‘->’? 12906 105 | rb_fd = skel->maps.ringbuf.map_fd; 12907 | ^ 12908 | -> 12909 make[1]: *** [Makefile:456: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ringbuf.test.o] Error 1 12910 make: *** [Makefile:159: all] Error 2 12911 21:28:05 INFO | END ERRORubuntu_bpf.setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954743] 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 1954743 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/1954743 Title: ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue spotted on 5.13.0-22-generic and other cloud variants, it's not a regression. Test build failed with: CLNG-BPF [test_maps] test_xdp_noinline.o CLNG-BPF [test_maps] test_xdp_redirect.o CLNG-BPF [test_maps] test_xdp_vlan.o CLNG-BPF [test_maps] test_xdp_with_cpumap_helpers.o CLNG-BPF [test_maps] test_xdp_with_devmap_helpers.o CLNG-BPF [test_maps] trace_printk.o CLNG-BPF [test_maps] trigger_bench.o CLNG-BPF [test_maps] udp_limit.o CLNG-BPF [test_maps] xdp_dummy.o CLNG-BPF [test_maps] xdp_redirect_map.o CLNG-BPF [test_maps] xdp_tx.o CLNG-BPF [test_maps] xdping_kern.o GEN-SKEL [test_progs] atomic_bounds.skel.h GEN-SKEL [test_progs] atomics.skel.h GEN-SKEL [test_progs] bind4_prog.skel.h GEN-SKEL [test_progs] bind6_prog.skel.h GEN-SKEL [test_progs] bind_perm.skel.h GEN-SKEL [test_progs] bpf_cubic.skel.h make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 libbpf: ELF relo #0 in section #15 has unexpected type 2 in /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.o Error: failed to link '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22 (-22) make[1]: *** [Makefile:456: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.skel.h] Error 234 make: *** [Makefile:159: all] Error 2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 14 05:33 seq crw-rw 1 root audio 116, 33 Dec 14 05:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDmesg: Date: Tue Dec 14 06:41:46 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:br1.8:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:sku: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1954743/+subscriptions --
[Kernel-packages] [Bug 1954743] Re: ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22
** Tags added: sru-20211129 ** Summary changed: - ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22 + ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22) -- 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/1954743 Title: ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue spotted on 5.13.0-22-generic and other cloud variants, it's not a regression. Test build failed with: CLNG-BPF [test_maps] test_xdp_noinline.o CLNG-BPF [test_maps] test_xdp_redirect.o CLNG-BPF [test_maps] test_xdp_vlan.o CLNG-BPF [test_maps] test_xdp_with_cpumap_helpers.o CLNG-BPF [test_maps] test_xdp_with_devmap_helpers.o CLNG-BPF [test_maps] trace_printk.o CLNG-BPF [test_maps] trigger_bench.o CLNG-BPF [test_maps] udp_limit.o CLNG-BPF [test_maps] xdp_dummy.o CLNG-BPF [test_maps] xdp_redirect_map.o CLNG-BPF [test_maps] xdp_tx.o CLNG-BPF [test_maps] xdping_kern.o GEN-SKEL [test_progs] atomic_bounds.skel.h GEN-SKEL [test_progs] atomics.skel.h GEN-SKEL [test_progs] bind4_prog.skel.h GEN-SKEL [test_progs] bind6_prog.skel.h GEN-SKEL [test_progs] bind_perm.skel.h GEN-SKEL [test_progs] bpf_cubic.skel.h make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 libbpf: ELF relo #0 in section #15 has unexpected type 2 in /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.o Error: failed to link '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22 (-22) make[1]: *** [Makefile:456: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.skel.h] Error 234 make: *** [Makefile:159: all] Error 2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 14 05:33 seq crw-rw 1 root audio 116, 33 Dec 14 05:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDmesg: Date: Tue Dec 14 06:41:46 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:br1.8:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:sku: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1954743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954743] [NEW] ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22
Public bug reported: Issue spotted on 5.13.0-22-generic and other cloud variants, it's not a regression. Test build failed with: CLNG-BPF [test_maps] test_xdp_noinline.o CLNG-BPF [test_maps] test_xdp_redirect.o CLNG-BPF [test_maps] test_xdp_vlan.o CLNG-BPF [test_maps] test_xdp_with_cpumap_helpers.o CLNG-BPF [test_maps] test_xdp_with_devmap_helpers.o CLNG-BPF [test_maps] trace_printk.o CLNG-BPF [test_maps] trigger_bench.o CLNG-BPF [test_maps] udp_limit.o CLNG-BPF [test_maps] xdp_dummy.o CLNG-BPF [test_maps] xdp_redirect_map.o CLNG-BPF [test_maps] xdp_tx.o CLNG-BPF [test_maps] xdping_kern.o GEN-SKEL [test_progs] atomic_bounds.skel.h GEN-SKEL [test_progs] atomics.skel.h GEN-SKEL [test_progs] bind4_prog.skel.h GEN-SKEL [test_progs] bind6_prog.skel.h GEN-SKEL [test_progs] bind_perm.skel.h GEN-SKEL [test_progs] bpf_cubic.skel.h make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 libbpf: ELF relo #0 in section #15 has unexpected type 2 in /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.o Error: failed to link '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22 (-22) make[1]: *** [Makefile:456: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_cubic.skel.h] Error 234 make: *** [Makefile:159: all] Error 2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 14 05:33 seq crw-rw 1 root audio 116, 33 Dec 14 05:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDmesg: Date: Tue Dec 14 06:41:46 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:br1.8:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:sku: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.13 amd64 apport-bug impish ubuntu-bpf uec-images ** Tags added: 5.13 ubuntu-bpf ** Also affects: ubuntu-kernel-tests 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/1954743 Title: ubuntu_bpf failed to build on Impish (Error: failed to link .../linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: Issue spotted on 5.13.0-22-generic and other cloud variants, it's not a regression. Test build failed with: CLNG-BPF [test_maps] test_xdp_noinline.o CLNG-BPF [test_maps] test_xdp_redirect.o CLNG-BPF [test_maps] test_xdp_vlan.o CLNG-BPF [test_maps] test_xdp_with_cpumap_helpers.o CLNG-BPF [test_maps] test_xdp_with_devmap_helpers.o CLNG-BPF [test_maps] trace_printk.o CLNG-BPF [test_maps] trigger_bench.o CLNG-BPF [test_maps] udp_limit.o CLNG-BPF [test_maps] xdp_dummy.o
[Kernel-packages] [Bug 1953223] Re: USB device is not detected during boot, again
If mainline kernel doesn't work, I am working on a similar case that may help your case too. -- 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/1953223 Title: USB device is not detected during boot, again Status in linux package in Ubuntu: Confirmed Bug description: I have an ethernet adapter (ASIX Electronics Corp. AX88179 Gigabit Ethernet) attached to a USB-C port of my laptop. After update to kernel 5.4.0-90-generic it stopped working again. Same problem with 5.4.0-91-generic. Detaching and reattaching the adapter doesn't help, but after suspend and resume it starts working again, until the next boot. I had the same problem earlier and it was fixed here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 , but the bug got reintroduced in kernel 5.4.0-90-generic most likely due to this patch: * Fix cold plugged USB device on certain PCIe USB cards (LP: #1945211) - Revert "UBUNTU: SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub"" I'm running Ubuntu 20.04. USB2 ports work without problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jttoivon 2745 F pipewire-media- /dev/snd/controlC0: jttoivon 2745 F pipewire-media- /dev/snd/seq:jttoivon 2744 F pipewire CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 4 12:46:18 2021 InstallationDate: Installed on 2020-01-23 (680 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP ZBook Studio G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=c6b19f0f-68ff-4d8c-985a-c3ed88345389 ro quiet splash resume=UUID=f25913ea-6478-45dc-8f64-ea5d721a8f25 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.16.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.4C.00 dmi.chassis.asset.tag: 5CD9495R4G dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.16.00:bd04/22/2021:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.4C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2ZC51EA#AK8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953223] Re: USB device is not detected during boot, again
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.16-rc5/amd64/ Headers are not needed. -- 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/1953223 Title: USB device is not detected during boot, again Status in linux package in Ubuntu: Confirmed Bug description: I have an ethernet adapter (ASIX Electronics Corp. AX88179 Gigabit Ethernet) attached to a USB-C port of my laptop. After update to kernel 5.4.0-90-generic it stopped working again. Same problem with 5.4.0-91-generic. Detaching and reattaching the adapter doesn't help, but after suspend and resume it starts working again, until the next boot. I had the same problem earlier and it was fixed here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 , but the bug got reintroduced in kernel 5.4.0-90-generic most likely due to this patch: * Fix cold plugged USB device on certain PCIe USB cards (LP: #1945211) - Revert "UBUNTU: SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub"" I'm running Ubuntu 20.04. USB2 ports work without problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jttoivon 2745 F pipewire-media- /dev/snd/controlC0: jttoivon 2745 F pipewire-media- /dev/snd/seq:jttoivon 2744 F pipewire CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 4 12:46:18 2021 InstallationDate: Installed on 2020-01-23 (680 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP ZBook Studio G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=c6b19f0f-68ff-4d8c-985a-c3ed88345389 ro quiet splash resume=UUID=f25913ea-6478-45dc-8f64-ea5d721a8f25 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.16.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.4C.00 dmi.chassis.asset.tag: 5CD9495R4G dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.16.00:bd04/22/2021:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.4C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2ZC51EA#AK8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
** Tags added: originate-from-1952194 ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => 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/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952403] Re: Realtek 8822CE wireless card fails to work after laptop discharge in sleep
This is more likely to be a PCI or ACPI issue. Maybe the ACPI power
resources for the card was turned off?
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.16-rc5/amd64/
Headers are not needed.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1952403
Title:
Realtek 8822CE wireless card fails to work after laptop discharge in
sleep
Status in linux package in Ubuntu:
Incomplete
Bug description:
I own an Asus TUF A15 FA506IV laptop with Ubuntu 21.10. After putting
it to sleep it discharged. Turning it back on the Wireless cards
doesn't work.
This is what I found in the logs that could help:
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:311] info: Store:
POWER_RESUMED
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:312] info: Store:
SET_SUSPEND_STATUS true
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:313] info:
[DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Nov 24 15:25:56 Zveri2 kernel: [21587.358139] rtw_8822ce :03:00.0: start
vif 80:30:49:cc:98:0f on port 0
Nov 24 15:25:56 Zveri2 charon: 01[KNL] interface wlp3s0 activated
Nov 24 15:25:56 Zveri2 NetworkManager[1059]: [1637760356.4839]
manager: NetworkManager state is now CONNECTED_LOCAL
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:489] info:
NetworkStatus: Network check failed {
Nov 24 15:25:56 Zveri2 krunner[16146]: "error": "Failed to fetch"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:490] info: Network
status check {
Nov 24 15:25:56 Zveri2 krunner[16146]: "elapsed_time_ms": 999784,
Nov 24 15:25:56 Zveri2 krunner[16146]: "navigator_online": false,
Nov 24 15:25:56 Zveri2 krunner[16146]: "api_test": "offline"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
After this I am getting the following trace:
Nov 24 15:26:05 Zveri2 kernel: [21596.291200] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Nov 24 15:26:05 Zveri2 kernel: [21596.291287] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Nov 24 15:26:05 Zveri2 kernel: [21596.291365] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Nov 24 15:26:05 Zveri2 kernel: [21596.291484] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Nov 24 15:26:05 Zveri2 kernel: [21596.291570] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[5]
Nov 24 15:26:05 Zveri2 kernel: [21596.291651] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[6]
Nov 24 15:26:06 Zveri2 krunner[16146]: [11/24/21, 15:26:06:125] info:
[NETWORK-CONNECTIVITY] Failed to establish a connection after 10 attempt(s).
Nov 24 15:26:07 Zveri2 kernel: [21598.291806] rtw_8822ce :03:00.0: failed
to poll offset=0x5 mask=0x2 value=0x0
Nov 24 15:26:07 Zveri2 kernel: [21598.292047] [ cut here
]
Nov 24 15:26:07 Zveri2 kernel: [21598.292049] failed to read DBI register,
addr=0x0719
Nov 24 15:26:07 Zveri2 kernel: [21598.292082] WARNING: CPU: 2 PID: 17826 at
drivers/net/wireless/realtek/rtw88/pci.c:1310 rtw_dbi_read8.constprop.0+0x
aa/0xc0 [rtw88_pci]
Nov 24 15:26:07 Zveri2 kernel: [21598.292096] Modules linked in:
nf_conntrack_netlink xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE)
xfrm_user
xfrm_algo vboxdrv(OE) rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack
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 nfnetlink bridge stp llc
cmac algif_hash algif_skcipher overlay af_alg bnep binfmt_misc zfs(PO) zu
nicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O)
intel_rapl_msr intel_rapl_common joydev snd_hda_codec_realtek snd_hda_code
c_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel edac_mce_amd
snd_intel_dspcfg snd_intel_sdw_acpi uvcvideo snd_hda_codec rtw88_8822ce rtw88_88
22c videobuf2_vmalloc snd_hda_core kvm_amd snd_hwdep rtw88_pci btusb
videobuf2_memops snd_pcm btrtl rtw88_core videobuf2_v4l2 btbcm videobuf2_common
k
vm btintel snd_seq_midi bluetooth videodev snd_seq_midi_event ecdh_generic
nls_iso8859_1 mc mac80211 rapl ecc snd_rawmidi input_leds
Nov 24 15:26:07 Zveri2 kernel: [21598.292174] serio_raw efi_pstore wmi_bmof
hid_multitouch snd_seq k10temp snd_seq_device cfg80211 snd_timer ucsi_ccg
snd snd_rn_pci_acp3x libarc4 ccp snd_pci_acp3x soundcore ucsi_acpi
typec_ucsi typec asus_wireless mac_hid nvidia_uvm(POE) sch_fq_codel msr
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic
xor zstd_compress raid6_pq libcrc32c dm_crypt hid_logitech_hidpp
hid_logitech_dj nvidia_drm(POE) nvidia_modeset(POE) usbhid nvidia(POE)
hid_generic amdgpu mfd_aaeon asus_wmi sparse_keymap iommu_v2 gpu_sched
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
For those who are affected by this issue, here's a kernel with fix [1]: https://people.canonical.com/~khfeng/8821ce-rx-aspm/ [1] https://lkml.org/lkml/2021/12/14/13 -- 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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 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 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949079] Re: linux-gcp: ubuntu_ltp_controllers reports broken tests
Hello Tim, this bug title says it's for ubuntu_ltp_controllers, however the bug description and the attachment is for ubuntu_kernel_selftests. So I am not sure which one you're referring to in this case. I am going to close this bug. Please feel free to open a new one. Thanks Sam ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux-gcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1949079 Title: linux-gcp: ubuntu_ltp_controllers reports broken tests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Bug description: What is the difference between failed and broken ? I don't really know what is wrong with this test, but I do see some build failures in the attached log: 00:32:18 DEBUG| [stderr] libbpf: ELF relo #0 in section #15 has unexpected type 2 in /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/bpf_cubic.o 00:32:18 DEBUG| [stderr] Error: failed to link '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/bpf_cubic.o': Unknown error -22 (-22) 00:32:18 DEBUG| [stdout] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf' 00:32:18 DEBUG| [stderr] make[1]: *** [Makefile:456: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/bpf_cubic.skel.h] Error 234 00:32:18 DEBUG| [stderr] make: *** [Makefile:159: all] Error 2 00:32:18 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954611] Re: Let VMD follow host bridge PCIe settings
Test on the laptop which embedded this nvme card, update to 5.14.0-1011.11. No AER error in kernel log. -- 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/1954611 Title: Let VMD follow host bridge PCIe settings Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some platforms have endless AER message floods kernel log, slows done disk I/O. [Fix] Honor BIOS settings to disable AER for Intel VMD. [Test] Use dmesg to check kernel log, no more AER message since AER is disabled. [Where problem could occur] The patch copies PCIe settings from host bridge, so some PCIe features will be disabled as a result. This may not be desirable for some users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944411] Re: ubuntu_bpf: build failure with kernel 5.13
** Also affects: ubuntu-kernel-tests 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/1944411 Title: ubuntu_bpf: build failure with kernel 5.13 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Expired Status in linux source package in Impish: Expired Bug description: We get this failure with the ubuntu_bpf 12test886 Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' 12887 libbpf: elf: skipping unrecognized data section(5) .rodata.str1.1 12888 libbpf: elf: skipping unrecognized data section(5) .rodata.str1.1 12889 libbpf: elf: skipping unrecognized data section(6) .rodata.str1.1 12890 libbpf: elf: skipping unrecognized data section(7) .rodata.str1.1 12891 libbpf: elf: skipping unrecognized data section(8) .rodata.cst16 12892 libbpf: elf: skipping unrecognized data section(8) .rodata.str1.1 12893 libbpf: elf: skipping unrecognized data section(7) .rodata.str1.1 12894 libbpf: elf: skipping unrecognized data section(8) .rodata.str1.1 12895 libbpf: elf: skipping unrecognized data section(7) .maps.btf_map 12896 libbpf: elf: skipping unrecognized data section(7) .maps.btf_map_legacy 12897 libbpf: elf: skipping unrecognized data section(8) .rodata.str1.1 12898 libbpf: elf: skipping unrecognized data section(27) .rodata.str1.1 12899 libbpf: elf: skipping unrecognized data section(15) .rodata.str1.1 12900 libbpf: elf: skipping unrecognized data section(5) .rodata.cst16 12901 libbpf: elf: skipping unrecognized data section(27) .rodata.str1.1 12902 libbpf: elf: skipping unrecognized data section(4) .rodata.str1.1 12903 libbpf: elf: skipping unrecognized data section(7) .rodata.str1.1 12904 /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c: In function ‘test_ringbuf’: 12905 /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:105:35: error: ‘skel->maps.ringbuf’ is a pointer; did you mean to use ‘->’? 12906 105 | rb_fd = skel->maps.ringbuf.map_fd; 12907 | ^ 12908 | -> 12909 make[1]: *** [Makefile:456: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ringbuf.test.o] Error 1 12910 make: *** [Makefile:159: all] Error 2 12911 21:28:05 INFO | END ERRORubuntu_bpf.setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 903999] Re: Thinkpad X120e doesn't suspend/resume
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/903999
Title:
Thinkpad X120e doesn't suspend/resume
Status in linux package in Ubuntu:
Expired
Status in linux source package in Precise:
Won't Fix
Bug description:
Suspend/resume doesn't seem to work, I tried running the script specified in:
https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting
The first says it couldn't sleep, and the second test takes the laptop into a
blank screen which I can't recover from (that's usually what happens when I try
to resume).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-4-generic-pae 3.2.0-4.10
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic-pae 3.2.0-rc5
Uname: Linux 3.2.0-4-generic-pae i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.90-0ubuntu1
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: beuno 1638 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xf0244000 irq 44'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 5
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'SB'/'HDA ATI SB at 0xf024 irq 16'
Mixer name : 'Conexant CX20582 (Pebble)'
Components : 'HDA:14f15066,17aa21df,00100302'
Controls : 8
Simple ctrls : 5
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Dec 13 20:13:16 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: LENOVO 05962RU
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic-pae
root=UUID=c9ef48cc-ddc5-4873-ac9b-2a14fe2329d3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-4-generic-pae N/A
linux-backports-modules-3.2.0-4-generic-pae N/A
linux-firmware 1.62
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2011-12-10 (3 days ago)
dmi.bios.date: 08/25/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8FET31WW (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 05962RU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8FET31WW(1.15):bd08/25/2011:svnLENOVO:pn05962RU:pvrThinkPadX120e:rvnLENOVO:rn05962RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 05962RU
dmi.product.version: ThinkPad X120e
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903999/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918110] Re: overlay_map.dtb is in wrong location
** No longer affects: linux-raspi (Ubuntu) ** No longer affects: linux-raspi (Ubuntu Focal) ** No longer affects: linux-raspi (Ubuntu Groovy) ** No longer affects: linux-raspi (Ubuntu Hirsute) ** Changed in: flash-kernel (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1918110 Title: overlay_map.dtb is in wrong location Status in flash-kernel package in Ubuntu: Fix Released Status in flash-kernel source package in Focal: Confirmed Status in flash-kernel source package in Groovy: Won't Fix Status in flash-kernel source package in Hirsute: Fix Released Bug description: overlay_map.dtb is supposed to be located in /boot/firmware/overlays and *not* in /boot/firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1918110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-azure (Ubuntu Hirsute)
** No longer affects: cloud-init (Ubuntu Hirsute)
** No longer affects: cloud-init (Ubuntu)
** Project changed: cloud-init => ubuntu-translations
** No longer affects: ubuntu-translations
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Hirsute:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Hirsute) ** No longer affects: udev (Ubuntu) ** No longer affects: udev (Ubuntu Hirsute) -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Hot removal of disks under kvm on s390 does not result in the kernel removing the block device, which can lead to hung tasks and other issues. [Test Plan] See steps to reproduce the bug in the original description below. To test, execute these steps and confirm that the block device gets removed as expected. [Where problems could occur] The fix is a revert of the changes which introduced this regression. The original commit was a removal of supposedly unused code, but it seems a mistake was made in the logic around unregistering of disks. Reverting the changes could have potential to introduce bugs related to other virt devices, especially if it interacts badly with subsequent driver changes. However, the patch reverted cleanly, and reverting restores the code to the state which has been working well in previous kernels and seems like the lowest risk option until a proper fix is available upstream. --- Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
[Kernel-packages] [Bug 1954611] Re: Let VMD follow host bridge PCIe settings
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1954611 Title: Let VMD follow host bridge PCIe settings Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some platforms have endless AER message floods kernel log, slows done disk I/O. [Fix] Honor BIOS settings to disable AER for Intel VMD. [Test] Use dmesg to check kernel log, no more AER message since AER is disabled. [Where problem could occur] The patch copies PCIe settings from host bridge, so some PCIe features will be disabled as a result. This may not be desirable for some users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
** Tags added: oem-priority originate-from-1947298 somerville ** Description changed: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] + Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low -- 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/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953286] Re: Add support for NVIDIA EC backlight
Test on specific DDS panel machine with 5.14.0-1011.11, brightness can be adjusted. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1953286 Title: Add support for NVIDIA EC backlight Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some system equipped with NVIDIA GFX cannot change screen brightness. [Fix] Add new way to change brightness. [Test] After the fix is applied, there's a new backlight sysfs "nvidia_wmi_ec_backlight" can change the screen brightness. [Where problems could occur] The driver relies on BIOS to behave correctly. If the BIOS lies or has a bug, the new backlight interface will overtake other backlight interfaces. It's rather unlikely though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941665] Re: Intel AX201 8086:7af0 subsys 8086:4070 hardware reset periodically: FW error in SYNC CMD UNKNOWN
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1941665
Title:
Intel AX201 8086:7af0 subsys 8086:4070 hardware reset periodically: FW
error in SYNC CMD UNKNOWN
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Impish:
Triaged
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
After applied patches from bug 1933938 to enable AX201 on ADL platforms,
some of them may still fail to functioning stably due to fw error when
LARI_CONFIG_CHANGE command is sent. With CONFIG_IWLWIFI_DEBUG turned on,
following error appears:
iwlwifi :00:14.3: iwl_mvm_lari_cfg sending LARI_CONFIG_CHANGE,
config_bitmap=0x8, oem_11ax_allow_bitmap=0xf
iwlwifi :00:14.3: iwl_trans_txq_send_hcmd_sync Attempting to send
sync command UNKNOWN
iwlwifi :00:14.3: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE
for command UNKNOWN
Then begin FW error, hardware reset.
[Fix]
Commit 54b4fda5a761 ("iwlwifi: mvm: Read acpi dsm to get unii4
enable/disable bitmap") is required to fix this issue. The other commit
is pulled in for dependency.
[Test Case]
Install a prebuilt kernel with these fixes, put DUT under idle for 5
mins and check if there is still firmware error messages.
[Where problems could occur]
There is little chance that it can ever go wrong judging from the
simplexity of the two commits.
[Other Info]
While the two patches have already been included in mainline and
therefore Ubuntu unstable, only oem-5.13 and impish are nominated.
== original bug report ==
After applied patches from bug 1933938 to enable AX201 on ADL
platforms, some of them may still fail to functioning stably due to fw
error when LARI_CONFIG_CHANGE command is sent. With
CONFIG_IWLWIFI_DEBUG turned on, following error appears:
iwlwifi :00:14.3: iwl_mvm_lari_cfg sending LARI_CONFIG_CHANGE,
config_bitmap=0x8, oem_11ax_allow_bitmap=0xf
iwlwifi :00:14.3: iwl_trans_txq_send_hcmd_sync Attempting to send sync
command UNKNOWN
iwlwifi :00:14.3: iwl_trans_txq_send_hcmd_sync Setting HCMD_ACTIVE for
command UNKNOWN
Then begin FW error, hardware reset:
[ 12.469094] kernel: RIP: 0033:0x7f8de181612d
[ 12.469097] kernel: Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 ca ee
ff ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48>
3d 00 f0 ff ff 77 2f 44
89 c7 48 89 44 24 08 e8 fe ee ff ff 48
[ 12.469099] kernel: RSP: 002b:7fff1de04900 EFLAGS: 0293 ORIG_RAX:
002e
[ 12.469102] kernel: RAX: ffda RBX: 5622f7660880 RCX:
7f8de181612d
[ 12.469103] kernel: RDX: RSI: 7fff1de04950 RDI:
000c
[ 12.469104] kernel: RBP: 7fff1de04950 R08: R09:
[ 12.469105] kernel: R10: 0001 R11: 0293 R12:
5622f7660880
[ 12.469106] kernel: R13: 7fff1de04b08 R14: 7fff1de04afc R15:
[ 13.170483] kernel: iwlwifi :00:14.3: Microcode SW error detected.
Restarting 0x0.
[ 13.170580] kernel: iwlwifi :00:14.3: Start IWL Error Log Dump:
[ 13.170581] kernel: iwlwifi :00:14.3: Transport status: 0x004B,
valid: 6
[ 13.170582] kernel: iwlwifi :00:14.3: Loaded firmware version:
64.97bbee0a.0 so-a0-hr-b0-64.ucode
[ 13.170583] kernel: iwlwifi :00:14.3: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
[ 13.170584] kernel: iwlwifi :00:14.3: 0x02F0 |
[Kernel-packages] [Bug 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954728] [NEW] Fix No Screen after login to Desktop on sku with 3840x2400 panel
Public bug reported: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Description changed: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] - Defeatur the underrun feature for intel display gen13+. + Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@nemodot it's been said that the fix should be in the next kernel
release. in the meantime if you use apt to keep your system (which
*buntu does by default) up to date you can use 'sudo apt-mark hold
' on the known good kernel packages to prevent apt from
removing the ones you want.
--
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/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
Confirmed
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
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: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
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.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Hey guys, sorry to interrupt. When could I expect this fix to be
available. Im on Ubuntu 21.10 and have to manually select kernel 5.11 so
it wont kernel panic on me, and it's slowly getting displaced by newer
versions that are broken for me.
--
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/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
Confirmed
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
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: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
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.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954469] Re: KVM Bus Lock Debug Exception
in linux 5.13 e8ea85fb2 KVM: X86: Add support for the emulation of DR6_BUS_LOCK bit 76ea438b4 KVM: X86: Expose bus lock debug exception to guest qemu 6.1 06e878b41 target/i386: Add bus lock debug exception support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954469 Title: KVM Bus Lock Debug Exception Status in linux package in Ubuntu: Fix Released Bug description: A bus lock is acquired either through split locked access to writeback (WB) memory or by using locks to uncacheable (UC) memory. This is typically > 1000 cycles slower than atomic operation within a cache line. It also disrupts performance on other cores (which must wait for the bus lock to be released before their memory operations). Bus lock debug exception is a sub-feature of bus lock detection. It is an ability to notify the kernel by an #DB trap after the instruction acquires a bus lock when CPL>0. This allows the kernel to enforce user application throttling or mitigations. A logical processor can be configured to generate a debug exception (#DB) following acquisition of a bus lock. Software enables those debug exceptions by setting bit 2 of the IA32_DEBUGCTL MSR. The CPU enumerates this feature using CPUID.(EAX=7, ECX=0).ECX[24]. A debug exception due to acquistion of a bus lock is reported as a trap following execution of the instruction acquiring the bus lock. The processor identifies such debug exceptions using bit 11 of DR6: delivery of a bus-lock #DB clears DR6[11]. Linux 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953286] Re: Add support for NVIDIA EC backlight
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1953286 Title: Add support for NVIDIA EC backlight Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some system equipped with NVIDIA GFX cannot change screen brightness. [Fix] Add new way to change brightness. [Test] After the fix is applied, there's a new backlight sysfs "nvidia_wmi_ec_backlight" can change the screen brightness. [Where problems could occur] The driver relies on BIOS to behave correctly. If the BIOS lies or has a bug, the new backlight interface will overtake other backlight interfaces. It's rather unlikely though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11
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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
In Progress
Status in linux-firmware source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] On ADL platform, I+N sku, get the cpufreq errors during boot-up, [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) The commit has been landed on mainline since v5.15-rc1. [Test Case] 1. boot-up the machine. 2. check dmesg if the cpufreq error is presented. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954611] Re: Let VMD follow host bridge PCIe settings
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954611 Title: Let VMD follow host bridge PCIe settings Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some platforms have endless AER message floods kernel log, slows done disk I/O. [Fix] Honor BIOS settings to disable AER for Intel VMD. [Test] Use dmesg to check kernel log, no more AER message since AER is disabled. [Where problem could occur] The patch copies PCIe settings from host bridge, so some PCIe features will be disabled as a result. This may not be desirable for some users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954612] Re: alsa/hda: the microphone can't be detected on a couple of lenovo machines
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954612 Title: alsa/hda: the microphone can't be detected on a couple of lenovo machines Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] We plug a microphone in the audio jack, but the driver can't detect the microphone and we try to record sound via this mic, can't record any sound. [Fix] Backport one patch from upstream. [Test] Booting the patched kernel, open the gnome-sound-setting, plug a microphone, we could see the system detect the microphone, and use this mic to record sound, the sound is recorded successfully. [Where problems could occur] The change only applies to the specific machines with those SSIDs, it will not introduce regression on other machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11
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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954716] [NEW] rpi nfsroot vers=4 not supported anymore?
Public bug reported: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in linux-raspi package in Ubuntu: New Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1129.142 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.
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-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-4.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1952234
Title:
linux-azure: add Icelake servers support in no-HWP mode to
cpufreq/intel_pstate driver
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux-azure-4.15 source package in Hirsute:
Invalid
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-azure-4.15 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting with the AH2020 Azure host build, Hyper-V is virtualizing
some registers that provide information about the CPU frequency. The
registers are read-only in a guest VM, so the guest can see the
frequency, but cannot make any modifications.
This feature also requires that the VM Configuration Version be 9.2 or
later, which means it needs to be a new VM type, such as the just
introduced Dv5/Ev5 series, and the new M832v2 VMs.
Within the Linux VM, the presence of the feature is indicated by the
“aperfmperf” flag in the “lscpu” flags output (or in the flags field
in /proc/cpuinfo).
It turns out there is a Linux kernel limitation when running on the
new Intel IceLake processors used for the Dv5/Ev5 series. Upstream
commit fbdc21e9b038 was added to provide IceLake support in the 5.14
kernel.
Microsoft has asked to backport fbdc21e9b038 commit to all supported
kernels.
[Test Plan]
Run Intel IceLake based VM and check the "aperfmperf" flag in the
"lscpu" flags output.
Without the patch the intel_pstate directory is missing from
/sys/devices/system/cpu/ and /sys/devices/system/cpu/cpufreq/ is
empty.
[Where problems could occur]
* intel_pstate driver is always used on Intel IceLake based VMs
without checking for presence of "aperfmperf" CPU flag.
* In earlier (5.4 and 4.15) linux-azure kernels when intel_pstate
driver is used it is in "active" mode instead of "passive" one (as
reported by "cat /sys/devices/system/cpu/intel_pstate/status", also
"cat /sys/devices/system/cpu/cpufreq/policy0/scaling_driver" returns
"intel_pstate" instead of "intel_cpufreq" which is the expected
behavior when in "active" mode).
If a consistent behavior across all kernel versions is desired commit
33aa46f252c7 ("cpufreq: intel_pstate: Use passive mode by default
without HWP") from the upstream should probably also be backported.
* /sys/devices/system/cpu/cpufreq/policy*/scaling_{min,max}_freq files
can be modified and the values reported by kernel will no longer match
the values used by hardware.
[Other Info]
None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952234/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
Which kernel version? I think I targeted all effected kernels already, but I could be wrong. -- 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/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module
** No longer affects: linux-aws (Ubuntu Bionic) ** Changed in: linux-aws (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Status in linux-aws source package in Hirsute: Confirmed Status in linux-aws source package in Impish: Confirmed Status in linux-aws source package in Jammy: Confirmed Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module
** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux-aws (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New -- 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/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: New Status in linux-aws source package in Hirsute: New Status in linux-aws source package in Impish: New Status in linux-aws source package in Jammy: Confirmed Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954709] 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/1954709 Title: Desktop freezes Status in linux package in Ubuntu: Confirmed Bug description: Dmesg is showing error like: [38788.569852] traps: chrome[67234] trap invalid opcode ip:563f6e3411cf sp:7ffc8aa52b50 error:0 in chrome[563f69764000+8936000] [39342.613678] BUG: kernel NULL pointer dereference, address: 00c8 [39342.613682] #PF: supervisor read access in kernel mode [39342.613684] #PF: error_code(0x) - not-present page [39342.613685] PGD 0 P4D 0 [39342.613686] Oops: [#1] SMP NOPTI [39342.613688] CPU: 6 PID: 3578 Comm: codium Tainted: GW 5.13.0-22-generic #22-Ubuntu [39342.613690] Hardware name: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY/G513QY, BIOS G513QY.316 11/29/2021 [39342.613691] RIP: 0010:iommu_get_dma_domain+0xd/0x20 [39342.613695] Code: 5c 31 c0 41 5d 5d c3 31 c0 c3 4c 89 ee 4c 89 e7 e8 48 d8 ff ff 41 5c 41 5d 5d c3 66 90 0f 1f 44 00 00 55 48 8b 87 c8 02 00 00 <48> 8b 80 c8 00 00 00 48 89 e5 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 and [39342.614166] CR2: 00c8 [39342.614167] ---[ end trace 09dc7239d253ac8b ]--- [39342.777369] RIP: 0010:iommu_get_dma_domain+0xd/0x20 [39342.777389] Code: 5c 31 c0 41 5d 5d c3 31 c0 c3 4c 89 ee 4c 89 e7 e8 48 d8 ff ff 41 5c 41 5d 5d c3 66 90 0f 1f 44 00 00 55 48 8b 87 c8 02 00 00 <48> 8b 80 c8 00 00 00 48 89 e5 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 [39342.777392] RSP: 0018:a3e380eb7930 EFLAGS: 00010282 [39342.777396] RAX: RBX: RCX: [39342.777397] RDX: 1000 RSI: fe3fd000 RDI: 9707816070c8 [39342.777398] RBP: a3e380eb7970 R08: R09: edd704c3f340 [39342.777399] R10: a3e380eb7b50 R11: R12: 9707816070c8 [39342.777400] R13: 1000 R14: fe3fd000 R15: 9707816070c8 [39342.777402] FS: () GS:970a8e78() knlGS: [39342.777403] CS: 0010 DS: ES: CR0: 80050033 [39342.777404] CR2: 00c8 CR3: 00018140e000 CR4: 00750ee0 [39342.777406] PKRU: 5554 [39342.777409] Fixing recursive fault but reboot is needed! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sami 1227 F pulseaudio /dev/snd/controlC1: sami 1227 F pulseaudio CasperMD5CheckResult: pass Date: Mon Dec 13 23:07:26 2021 InstallationDate: Installed on 2021-10-12 (62 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.73 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.316:bd11/29/2021:br5.19:efr0.73:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954709] [NEW] Desktop freezes
Public bug reported: Dmesg is showing error like: [38788.569852] traps: chrome[67234] trap invalid opcode ip:563f6e3411cf sp:7ffc8aa52b50 error:0 in chrome[563f69764000+8936000] [39342.613678] BUG: kernel NULL pointer dereference, address: 00c8 [39342.613682] #PF: supervisor read access in kernel mode [39342.613684] #PF: error_code(0x) - not-present page [39342.613685] PGD 0 P4D 0 [39342.613686] Oops: [#1] SMP NOPTI [39342.613688] CPU: 6 PID: 3578 Comm: codium Tainted: GW 5.13.0-22-generic #22-Ubuntu [39342.613690] Hardware name: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY/G513QY, BIOS G513QY.316 11/29/2021 [39342.613691] RIP: 0010:iommu_get_dma_domain+0xd/0x20 [39342.613695] Code: 5c 31 c0 41 5d 5d c3 31 c0 c3 4c 89 ee 4c 89 e7 e8 48 d8 ff ff 41 5c 41 5d 5d c3 66 90 0f 1f 44 00 00 55 48 8b 87 c8 02 00 00 <48> 8b 80 c8 00 00 00 48 89 e5 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 and [39342.614166] CR2: 00c8 [39342.614167] ---[ end trace 09dc7239d253ac8b ]--- [39342.777369] RIP: 0010:iommu_get_dma_domain+0xd/0x20 [39342.777389] Code: 5c 31 c0 41 5d 5d c3 31 c0 c3 4c 89 ee 4c 89 e7 e8 48 d8 ff ff 41 5c 41 5d 5d c3 66 90 0f 1f 44 00 00 55 48 8b 87 c8 02 00 00 <48> 8b 80 c8 00 00 00 48 89 e5 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 [39342.777392] RSP: 0018:a3e380eb7930 EFLAGS: 00010282 [39342.777396] RAX: RBX: RCX: [39342.777397] RDX: 1000 RSI: fe3fd000 RDI: 9707816070c8 [39342.777398] RBP: a3e380eb7970 R08: R09: edd704c3f340 [39342.777399] R10: a3e380eb7b50 R11: R12: 9707816070c8 [39342.777400] R13: 1000 R14: fe3fd000 R15: 9707816070c8 [39342.777402] FS: () GS:970a8e78() knlGS: [39342.777403] CS: 0010 DS: ES: CR0: 80050033 [39342.777404] CR2: 00c8 CR3: 00018140e000 CR4: 00750ee0 [39342.777406] PKRU: 5554 [39342.777409] Fixing recursive fault but reboot is needed! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sami 1227 F pulseaudio /dev/snd/controlC1: sami 1227 F pulseaudio CasperMD5CheckResult: pass Date: Mon Dec 13 23:07:26 2021 InstallationDate: Installed on 2021-10-12 (62 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.73 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.316:bd11/29/2021:br5.19:efr0.73:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1954709 Title: Desktop freezes Status in linux package in Ubuntu: New Bug description: Dmesg is showing error like: [38788.569852] traps: chrome[67234] trap invalid opcode ip:563f6e3411cf sp:7ffc8aa52b50 error:0 in chrome[563f69764000+8936000] [39342.613678] BUG: kernel NULL pointer dereference, address: 00c8 [39342.613682] #PF: supervisor read access in kernel mode [39342.613684] #PF: error_code(0x) - not-present page [39342.613685] PGD 0 P4D 0 [39342.613686] Oops: [#1] SMP NOPTI [39342.613688] CPU: 6 PID: 3578 Comm: codium Tainted: GW 5.13.0-22-generic
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Moving to zfs 2.1.1 (from Debian) seems to fix the problem. [Regression potential] It is a major zfs update so we may introduce zfs regressions, but it seems sane to be aligned with the upstream zfs version. Also the zfs smoke tests passed across all architectures, so moving to this new version seems the right thing to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954703] [NEW] Bionic update: upstream stable patchset 2021-12-13
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-13 Ported from the following upstream stable releases: v4.14.256, v4.19.218 from git://git.kernel.org/ xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay binder: use euid from cred instead of using task Input: elantench - fix misreporting trackpoint coordinates Input: i8042 - Add quirk for Fujitsu Lifebook T725 libata: fix read log timeout value ocfs2: fix data corruption on truncate mmc: dw_mmc: Dont wait for DRTO on Write RSP error parisc: Fix ptrace check on syscall return tpm: Check for integer overflow in tpm2_map_response_body() media: ite-cir: IR receiver stop working after receive overflow ALSA: ua101: fix division by zero at probe ALSA: 6fire: fix control and bulk message timeouts ALSA: line6: fix control and interrupt message timeouts ALSA: synth: missing check for possible NULL after the call to kstrdup ALSA: timer: Fix use-after-free problem ALSA: timer: Unconditionally unlink slave instances, too x86/irq: Ensure PI wakeup handler is unregistered before module unload cavium: Return negative value when pci_alloc_irq_vectors() fails scsi: qla2xxx: Fix unmap of already freed sgl cavium: Fix return values of the probe function sfc: Don't use netif_info before net_device setup hyperv/vmbus: include linux/bitops.h mmc: winbond: don't build on M68K bpf: Prevent increasing bpf_jit_limit above max xen/netfront: stop tx queues during live migration spi: spl022: fix Microwire full duplex mode watchdog: Fix OMAP watchdog early handling vmxnet3: do not stop tx queues after netif_device_detach() btrfs: fix lost error handling when replaying directory deletes hwmon: (pmbus/lm25066) Add offset coefficients regulator: s5m8767: do not use reset value as DVS voltage if GPIO DVS is disabled regulator: dt-bindings: samsung,s5m8767: correct s5m8767,pmic-buck-default-dvs-idx property EDAC/sb_edac: Fix top-of-high-memory value for Broadwell/Haswell mwifiex: fix division by zero in fw download path ath6kl: fix division by zero in send path ath6kl: fix control-message timeout ath10k: fix control-message timeout ath10k: fix division by zero in send path PCI: Mark Atheros QCA6174 to avoid bus reset rtl8187: fix control-message timeouts evm: mark evm_fixmode as __ro_after_init wcn36xx: Fix HT40 capability for 2Ghz band mwifiex: Read a PCI register after writing the TX ring write pointer libata: fix checking of DMA state wcn36xx: handle connection loss indication RDMA/qedr: Fix NULL deref for query_qp on the GSI QP signal: Remove the bogus sigkill_pending in ptrace_stop signal/mips: Update (_save|_restore)_fp_context to fail with -EFAULT power: supply: max17042_battery: Prevent int underflow in set_soc_threshold power: supply: max17042_battery: use VFSOC for capacity when no rsns powerpc/85xx: Fix oops when mpc85xx_smp_guts_ids node cannot be found serial: core: Fix initializing and restoring termios speed ALSA: mixer: oss: Fix racy access to slots ALSA: mixer: fix deadlock in snd_mixer_oss_set_volume xen/balloon: add late_initcall_sync() for initial ballooning done PCI: aardvark: Do not clear status bits of masked interrupts PCI: aardvark: Do not unmask unused interrupts PCI: aardvark: Fix return value of MSI domain .alloc() method PCI: aardvark: Read all 16-bits from PCIE_MSI_PAYLOAD_REG quota: check block number when reading the block in quota file quota: correct error number in free_dqentry() pinctrl: core: fix possible memory leak in pinctrl_enable() iio: dac: ad5446: Fix ad5622_write() return value USB: serial: keyspan: fix memleak on probe errors USB: iowarrior: fix control-message timeouts Bluetooth: sco: Fix lock_sock() blockage by memcpy_from_msg() Bluetooth: fix use-after-free error in lock_sock_nested() platform/x86: wmi: do not fail if disabling fails MIPS: lantiq: dma: add small delay after reset MIPS: lantiq: dma: reset correct number of channel locking/lockdep: Avoid RCU-induced noinstr fail smackfs: Fix use-after-free in netlbl_catmap_walk() x86: Increase exception stack sizes mwifiex: Run SET_BSS_MODE when changing from P2P to STATION vif-type mwifiex: Properly initialize private structure on interface type changes media: mt9p031: Fix corrupted frame after restarting stream media: netup_unidvb: handle interrupt properly according to the firmware media: uvcvideo: Set capability in s_param media: s5p-mfc: fix possible null-pointer dereference in s5p_mfc_probe() media: s5p-mfc: Add checking to s5p_mfc_probe(). media: mceusb:
[Kernel-packages] [Bug 1944005] Re: System Lockup during failover
*** This bug is a duplicate of bug 1944586 *** https://bugs.launchpad.net/bugs/1944586 Dulicate of bug which is now fixed in stable https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944586/comments/8 ** This bug has been marked a duplicate of bug 1944586 kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47" -- 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/1944005 Title: System Lockup during failover Status in linux package in Ubuntu: Incomplete Status in multipath-tools package in Ubuntu: Confirmed Bug description: When testing failover for configured multipath devices, I am seeing some nodes lock up and become unresponsive. These nodes have frozen consoles, but can be pinged. So some of the network stack is functional, but ssh is not possible to them. 1) 20.04 focal 2) 0.8.3-1ubuntu2 3) multipathing failover would be successful across all nodes and the nodes would continue to be responsive 4) some of the nodes lock up when attempting to failover and cannot be reached via ssh or console Here is the ubuntu-bug output: https://pastebin.canonical.com/p/6MyWBggtS2/ Here is the kern.log: https://pastebin.canonical.com/p/rG42gzXG9X/ Here is the syslog: https://pastebin.canonical.com/p/C99ZprphZn/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
Hi, today happened again: ... [443206.333008] NETDEV WATCHDOG: laneth (ax88179_178a): transmit queue 0 timed out [443206.333112] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x267/0x270 ... At least didn't happened more often since I've updated the kernel. -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08:
[Kernel-packages] [Bug 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954692] Re: Reconsider compressed kernels on arm64
My side question is what prevents arm64 from having the amd64 approach where AFAIUI the image is compressed but starts with a small stub that decompresses it. -- 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/1954692 Title: Reconsider compressed kernels on arm64 Status in linux package in Ubuntu: Triaged Bug description: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954692] [NEW] Reconsider compressed kernels on arm64
Public bug reported: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954692 Title: Reconsider compressed kernels on arm64 Status in linux package in Ubuntu: Triaged Bug description: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
Moving to Debian zfs 2.1.1 + applying the debdiff in attach seems to fix the problem. ** Patch added: "zfs-update-to-2.1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5547343/+files/zfs-update-to-2.1.1.debdiff ** Description changed: + [Impact] + Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. + + [Test case] + + On s390x install the latest 5.15 Jammy kernel and run: + apt install zfs-dkms + + [Fix] + + Moving to zfs 2.1.1 (from Debian) seems to fix the problem. + + [Regression potential] + + It is a major zfs update so we may introduce zfs regressions, but it + seems sane to be aligned with the upstream zfs version. Also the zfs + smoke tests passed across all architectures, so moving to this new + version seems the right thing to do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Moving to zfs 2.1.1 (from Debian) seems to fix the problem. [Regression potential] It is a major zfs update so we may introduce zfs regressions, but it seems sane to be aligned with the upstream zfs version. Also the zfs smoke tests passed across all architectures, so moving to this new version seems the right thing to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] [NEW] jammy 5.15 soft lockup when zfs.ko is loaded on s390x
Public bug reported: Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954473] Re: KVM Shared Virtual Memory (SVM)
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.19 timeframe. Target Ubuntu 23.04. Platform is Sapphire Rapids -- 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/1954473 Title: KVM Shared Virtual Memory (SVM) Status in linux package in Ubuntu: Incomplete Bug description: SVM is short for shared virtual memory. This task is aiming at enabling SVM support for assigned devices on KVM. Example: assign a GPU from host to guest, the application program running in guest could share its virtual memory address to the assigned device. Latest update: extend the vIOMMU in QEMU to support SVM feature. 1. Description of the Technology. SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows sharing application virtual address space with the I/O device. The feature works with the PCI sig Process Address Space ID (PASID). SVM has the following benefits: • Programmer gets a consistent view of memory across host application and device • Efficient access to data, avoiding pining or copying overheads 2. Use cases that is important for this technology (aka, why is this technology needed). Intel has multiple IPs that would support SVM, and the usage in guest is also a demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to benefit from its advantages. 3. General design description (components modified: kvm, qemu-kvm, driver, libvirt (and other userland libraries)) Modified components would include: qemu-kvm, vfio driver, iommu driver Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume
bah, still no fix over a year later
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718761
Title:
It's not possible to use OverlayFS (mount -t overlay) to stack
directories on a ZFS volume
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
-- Configuration
# echo -e $(grep VERSION= /etc/os-release)\\nSIGNATURE=\"$(cat
/proc/version_signature)\"
VERSION="16.04.3 LTS (Xenial Xerus)"
SIGNATURE="Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17"
# dpkg --list | grep zfs
ii libzfs2linux0.6.5.6-0ubuntu18
ii zfs-doc 0.6.5.6-0ubuntu18
ii zfs-initramfs 0.6.5.6-0ubuntu18
ii zfs-zed 0.6.5.6-0ubuntu18
ii zfsutils-linux 0.6.5.6-0ubuntu18
-- Fault: Creating an overlay of multiple directories on a ZFS volume
does not work
# df /var/tmp
Filesystem Type 1K-blocks Used Available Use% Mounted on
tank07/var/tmp zfs 129916288 128 129916160 1% /var/tmp
# mkdir /var/tmp/{lower,middle,upper,workdir,overlay}
# mount -t overlay overlay
-olowerdir=/var/tmp/middle:/var/tmp/lower,upperdir=/var/tmp/upper,workdir=/var/tmp/workdir
/var/tmp/overlay
mount: wrong fs type, bad option, bad superblock on overlay,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
# dmesg|tail -1
[276328.438284] overlayfs: filesystem on '/var/tmp/upper' not supported as
upperdir
-- Control test 1: Creating an overlay of multiple directories on
another filesystem works
# df /tmp
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 1048576 133492915084 13% /tmp
# mkdir /tmp/{lower,middle,upper,workdir,overlay}
# mount -t overlay overlay
-olowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir
/tmp/overlay
# mount | grep overlay
overlay on /tmp/overlay type overlay
(rw,relatime,lowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir)
-- Control test 2: Creating an overlay using AuFS works on ZFS volume
and elsewhere
# mount -t aufs -obr=/tmp/lower:/tmp/middle:/tmp/upper:/tmp/workdir none
/tmp/overlay
# mount -t aufs
-obr=/var/tmp/lower:/var/tmp/middle:/var/tmp/upper:/var/tmp/workdir none
/var/tmp/overlay
# mount | grep aufs
none on /var/tmp/overlay type aufs (rw,relatime,si=9ead1ecae778b250)
none on /tmp/overlay type aufs (rw,relatime,si=9ead1ec9257d1250)
-- Remark
While the use of AuFS can be used as a workaround in the above scenario, AuFS
in turn will not work with [fuse.]glusterfs mounts (this has been documented
elsewhere). Given that OverlayFS is part of the (upstream) kernel and Ubuntu
now officially supports ZFS, the above should be fixed.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 18 16:12 seq
crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lspci: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: Red Hat KVM
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine:
BOOT_IMAGE=/ROOT/ubuntu1604@/boot/vmlinuz-4.10.0-35-generic
root=ZFS=tank07/ROOT/ubuntu1604 ro
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-35-generic N/A
linux-backports-modules-4.10.0-35-generic N/A
linux-firmware 1.157.12
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.10.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.9.1-5.el7_3.3
dmi.chassis.type: 1
dmi.chassis.vendor: Red Hat
dmi.chassis.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.9.1-5.el7_3.3:bd04/01/2014:svnRedHat:pnKVM:pvrRHEL7.3.0PC(i440FX+PIIX,1996):cvnRedHat:ct1:cvrRHEL7.3.0PC(i440FX+PIIX,1996):
dmi.product.name: KVM
dmi.product.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
dmi.sys.vendor: Red Hat
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 18 16:12 seq
crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
[Kernel-packages] [Bug 1954471] Re: KVM AIA Work Dispatch Instructions
Thanks for correcting pkg names. No upstream commits yet. Target Linux TBD. Platform is Sapphire Rapids -- 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/1954471 Title: KVM AIA Work Dispatch Instructions Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Bug description: AIA has 3 sub features: AIA User Interrupts AIA User Wait Instructions AIA Work Dispatch Instructions AIA User Wait Instructions was merged for SNR in Kernel 5.4/Qemu4.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954472] Re: KVM Scalable I/O Virtualization
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.18 timeframe. Target Ubuntu 22.10. Platform is Sapphire Rapids -- 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/1954472 Title: KVM Scalable I/O Virtualization Status in linux package in Ubuntu: Incomplete Bug description: Core OS/ VMM device virtualization framework extended to support Scalable IOV; OS/ VMM support for Scalable IOV IOMMU extensions; PASID translation support; existing device frameworks extended to support Scalable IOV; converged SW arch as prescribed by spec Improved performance and lower complexity for software utilizing PCIe devices in virtualized environments Software Benefits: Broad range of usages, e.g. security, comms, server graphics Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954474] Re: KVM notify VM Exit
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.17 timeframe. Target Ubuntu 22.04. Platform is Sapphire Rapids -- 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/1954474 Title: KVM notify VM Exit Status in linux package in Ubuntu: Incomplete Bug description: A VMM can enable notification VM exits to occur if no interrupt windows occur in VMX non-root operation for a specified amount of time (notify window). KVM Enabling: enable bit 31 of secondary processor-based excution control. enable notification VM exit (exit reason 75) handler. expose a module param to configure notify window and disable/enable VM notify. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954465] Re: KVM AIA User IPI
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.18 timeframe. Target Ubuntu 22.10. Platform is Sapphire Rapids. -- 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/1954465 Title: KVM AIA User IPI Status in linux package in Ubuntu: Incomplete Bug description: SENDUIPI is a new ring-3 instruction that sending IPI notification between ring 3 software. It uses a data structure (table) owned and managed by ring 0 OS. Ring 3 software can choose which table entry to invoke. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954463] Re: KVM ROP Control-Flow Enforcement Tech (CET)
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.18 timeframe. Target Ubuntu 22.10. Platform is Sapphire Rapids. -- 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/1954463 Title: KVM ROP Control-Flow Enforcement Tech (CET) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: Control-Flow Enforcement Tech (CET) What is Intel CET: Control-flow Enforcement Technology (CET) provides protection against return/jump-oriented programming (ROP) attacks. It can be implemented to protect both the kernel and applications. In the first phase, only the user-mode protection is implemented on the 64-bit kernel. However, 32-bit applications are supported under the compatibility mode. CET includes shadow stack (SHSTK) and indirect branch tracking (IBT). The SHSTK is a secondary stack allocated from memory. The processor automatically pushes/pops a secure copy to the SHSTK every return address and, by comparing the secure copy to the program stack copy, verifies function returns are as intended. The IBT verifies all indirect CALL/JMP targets are intended and marked by the compiler with 'ENDBR' op codes. Why need this technology(CET VMX): CET also can provide ROP attack in guest OS with VMX HW support. This will enhance platform security in Cloud computing, it's meaningful for Cloud service providers. Key change in kvm: To enable KVM based CET feature for guest OS, we need to : 1) Expose the features(CET SHSTK/IBT) to guest OS via CPUID report. 2) Enable xsaves/xrstors support for guest OS. 3) Fix xsaves/xrstors issue in existing KVM code. 4) Enabled CET states loading in guest entry/exit. 5) Add CET VMX related definitions. Key change in Qemu-kvm: expose CET related CPUID and xsaves/xrstors support to guest. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954464] Re: kvm SPR support for AMX
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.18 timeframe. Target Ubuntu 22.04. Platform is Sapphire Rapids. -- 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/1954464 Title: kvm SPR support for AMX Status in linux package in Ubuntu: Incomplete Bug description: AMX (including XFD): AMX (Advance Matrix eXtensions) is a new programming paradigm for direct matrix operations. TMUL (TILE Matrix mULtiply unit) is the multiply accelerator. XFD (Extended Feature Disable) is an XSAVE extension mechanism for those features with large XSAVE storage context, that enables the OS not pre-allocate the space initially. AMX is the first one using XFD feature. Use cases: Deep learning inference and training (CNN, DNN), other data analytics and machine learning apps, HPC SGEMM Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954466] Re: KVM Protection Keys for Supervisor Pages (PKS)
Thanks for correcting pkg names. No upstream commits yet. Target Linux 5.19 timeframe. Target Ubuntu 23.04. Platform is Sapphire Rapids -- 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/1954466 Title: KVM Protection Keys for Supervisor Pages (PKS) Status in linux package in Ubuntu: Incomplete Bug description: SKX introduced the Protection Key for User Pages (PKU) feature enabling fast, thread-specific manipulation of permission restrictions on user pages. SPR introduced Protection Key for Supervisor Pages(PKS), a new feature that extends the Protection Key architecture to support thread-specific permission restrictions on supervisor pages. This important feature enables enhanced access control on memory, and brings more valid usage model. Generally PKS enables protections on 'domains' of supervisor pages to limit supervisor mode access to pages beyond the normal paging protections(U/S, R/W, P). PKS works in a similar fashion to user space pkeys, PKU. As with PKU, supervisor pkeys are checked in addition to normal paging protections and Access or Writes can be disabled via a MSR update without TLB flushes when permissions change. PKS virtualization enabling should base on existing PKU code. Major works: CPUID exposure New CR4 bit exposure New VMCS fields enabling IA32_PKRS saving/restoring #GP handling Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
Hi - do you have timelines for when this will be integrated into the generic 20.04? I have some customers asking about it. Thanks Mark -- 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/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
Out of curiosity, I tried reverting this fix in /lib/udev/rules.d/71-nvidia.rules -- and it still works, no freeze on the login screen. So I guess my problem was fixed by something else after all, maybe the driver update itself. Or I was lucky to avoid the race condition... who knows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1949026 Title: System hangs on purple screen Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Bug description: [Impact] * In some race condition, the GDM starts before gdm-udev rule be applied. * That's because somehow the nvidia driver takes more times to do the runtime resume. Thus, apply the workaround to postpone to enable RTD3. [Test Plan] 1. In problematic machine, warn/cold boot the system. 2.1 System hangs on GDM login shell 2.2 After apply this patch, the system can enter the login screen. [Where problems could occur] * Postpone to enable RTD3 when binding driver should not impact the functionality since the power consumption usually not be consider in booting stage. --- We are facing an issue that GDM starts with Wayland instead of Xorg, despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics. The issue happens because gdm-disable-wayland is executed after GDM has started. The reason why the udev rules takes so long is because the the runtime suspended NVIDIA GFX takes more than 1 second to runtime resume, hence the driver starts the probing routine rather late. The proper solution is to impose a barrier like systemd-udev-settle.service before GDM, but limits to the GFX device only to avoid waiting for all udev rules are finished. Since such mechanism isn't available right now, workaround the issue by enabling runtime PM after driver is bound to avoid the runtime resume delay, and hope GDM always starts after the probing is done. Please backport below patch to supported nvidia-drivers: https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
My old work laptop is kinda old junk now, I installed Fedora on it for
some other testing. I'll try and get this tested in the next few days,
but I need get Ubuntu onto it first.
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
@Colin, how about some verification? ;-)
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
SRU: https://lists.ubuntu.com/archives/kernel-
team/2021-December/126484.html (oem-5.13,oem-5.14,impish,jammy)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
+
+ [Fix]
+
+ Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
+ failures on certain AMD laptops") from v5.16-rc5.
+
+ [Test Case]
+
+ Run checkbox suspend/resume tests on battey:
+
+ $ checkbox-cli run \
+
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
+
+ [Where problems could occur]
+
+ This shortens AMD PMC communication poll delay to a half of the original
+ value. While we don't have much information about the exact value range
+ allowed, the side effect couldn't be evaluated practically. This change
+ was ACKed by AMD developers and has been marked cc stable, we'll
+ probably bump into it anyway.
+
+ [Other Info]
+
+ This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
+ skipped here.
+
+ == original bug report ==
+
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
--
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/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954533] Re: Hirsute update: upstream stable patchset 2021-12-10
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954533 Title: Hirsute update: upstream stable patchset 2021-12-10 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-10 Ported from the following upstream stable releases: v5.10.80, v5.14.19 v5.14.20 from git://git.kernel.org/ Note: This patch set includes patches from v5.10.80 and v5.14.19. v5.14.20 was comprised entirely of a handful of reverts to patches we never carried in Hirsute. xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay usb: xhci: Enable runtime-pm by default on AMD Yellow Carp platform Input: iforce - fix control-message timeout Input: elantench - fix misreporting trackpoint coordinates Input: i8042 - Add quirk for Fujitsu Lifebook T725 libata: fix read log timeout value ocfs2: fix data corruption on truncate scsi: core: Remove command size deduction from scsi_setup_scsi_cmnd() scsi: qla2xxx: Fix kernel crash when accessing port_speed sysfs file scsi: qla2xxx: Fix use after free in eh_abort path mmc: mtk-sd: Add wait dma stop done flow mmc: dw_mmc: Dont wait for DRTO on Write RSP error exfat: fix incorrect loading of i_blocks for large files parisc: Fix set_fixmap() on PA1.x CPUs parisc: Fix ptrace check on syscall return tpm: Check for integer overflow in tpm2_map_response_body() firmware/psci: fix application of sizeof to pointer crypto: s5p-sss - Add error handling in s5p_aes_probe() media: rkvdec: Do not override sizeimage for output format media: ite-cir: IR receiver stop working after receive overflow media: rkvdec: Support dynamic resolution changes media: ir-kbd-i2c: improve responsiveness of hauppauge zilog receivers media: v4l2-ioctl: Fix check_ext_ctrls ALSA: hda/realtek: Fix mic mute LED for the HP Spectre x360 14 ALSA: hda/realtek: Add a quirk for HP OMEN 15 mute LED ALSA: hda/realtek: Add quirk for Clevo PC70HS ALSA: hda/realtek: Headset fixup for Clevo NH77HJQ ALSA: hda/realtek: Add a quirk for Acer Spin SP513-54N ALSA: hda/realtek: Add quirk for ASUS UX550VE ALSA: hda/realtek: Add quirk for HP EliteBook 840 G7 mute LED ALSA: ua101: fix division by zero at probe ALSA: 6fire: fix control and bulk message timeouts ALSA: line6: fix control and interrupt message timeouts ALSA: usb-audio: Line6 HX-Stomp XL USB_ID for 48k-fixed quirk ALSA: usb-audio: Add registration quirk for JBL Quantum 400 ALSA: hda: Free card instance properly at probe errors ALSA: synth: missing check for possible NULL after the call to kstrdup ALSA: timer: Fix use-after-free problem ALSA: timer: Unconditionally unlink slave instances, too ext4: fix lazy initialization next schedule time computation in more granular unit ext4: ensure enough credits in ext4_ext_shift_path_extents ext4: refresh the ext4_ext_path struct after dropping i_data_sem. fuse: fix page stealing x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c x86/cpu: Fix migration safety with X86_BUG_NULL_SEL x86/irq: Ensure PI wakeup handler is unregistered before module unload ASoC: soc-core: fix null-ptr-deref in snd_soc_del_component_unlocked() ALSA: hda/realtek: Fixes HP Spectre x360 15-eb1xxx speakers cavium: Return negative value when pci_alloc_irq_vectors() fails scsi: qla2xxx: Return -ENOMEM if kzalloc() fails scsi: qla2xxx: Fix unmap of already freed sgl mISDN: Fix return values of the probe function cavium: Fix return values of the probe function sfc: Export fibre-specific supported link modes sfc: Don't use netif_info before net_device setup hyperv/vmbus: include linux/bitops.h ARM: dts: sun7i: A20-olinuxino-lime2: Fix ethernet phy-mode reset: socfpga: add empty driver allowing consumers to probe mmc: winbond: don't build on M68K drm: panel-orientation-quirks: Add quirk for Aya Neo 2021 fcnal-test: kill hanging ping/nettest binaries on cleanup bpf: Define bpf_jit_alloc_exec_limit for arm64 JIT bpf: Prevent increasing bpf_jit_limit above max gpio: mlxbf2.c: Add check for bgpio_init failure xen/netfront: stop tx queues during live migration nvmet-tcp:
[Kernel-packages] [Bug 1952785] Re: Hirsute update: upstream stable patchset 2021-11-30
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952785 Title: Hirsute update: upstream stable patchset 2021-11-30 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-30 Ported from the following upstream stable releases: v5.10.77, v5.14.16 v5.10.78, v5.14.17 v5.10.79, v5.14.18 from git://git.kernel.org/ ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned ARM: 9134/1: remove duplicate memcpy() definition ARM: 9138/1: fix link warning with XIP + frame-pointer ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype ARM: 9141/1: only warn about XIP address when not compile testing ext4: fix possible UAF when remounting r/o a mmp-protected file system usbnet: sanity check for maxpacket usbnet: fix error return code in usbnet_probe() Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" pinctrl: amd: disable and mask interrupts on probe ata: sata_mv: Fix the error handling of mv_chip_id() nfc: port100: fix using -ERRNO as command type mask net/tls: Fix flipped sign in tls_err_abort() calls mmc: vub300: fix control-message timeouts mmc: cqhci: clear HALT state after CQE enable mmc: mediatek: Move cqhci init behind ungate clock mmc: dw_mmc: exynos: fix the finding clock sample value mmc: sdhci: Map more voltage level to SDHCI_POWER_330 mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit ocfs2: fix race between searching chunks and release journal_head from buffer_head nvme-tcp: fix H2CData PDU send accounting (again) cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() cfg80211: fix management registrations locking net: lan78xx: fix division by zero in send path mm, thp: bail out early in collapse_file for writeback page drm/amdgpu: fix out of bounds write cgroup: Fix memory leak caused by missing cgroup_bpf_offline riscv, bpf: Fix potential NULL dereference tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function bpf: Fix potential race in tail call compatibility check bpf: Fix error usage of map_fd and fdget() in generic_map_update_batch() IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields IB/hfi1: Fix abba locking issue with sc_disable() nvmet-tcp: fix data digest pointer calculation nvme-tcp: fix data digest pointer calculation nvme-tcp: fix possible req->offset corruption octeontx2-af: Display all enabled PF VF rsrc_alloc entries. RDMA/mlx5: Set user priority for DCT arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node reset: brcmstb-rescal: fix incorrect polarity of status bit regmap: Fix possible double-free in regcache_rbtree_exit() net: batman-adv: fix error handling net-sysfs: initialize uid and gid before calling net_ns_get_ownership cfg80211: correct bridge/4addr mode check net: Prevent infinite while loop in skb_tx_hash() RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string gpio: xgs-iproc: fix parsing of ngpios property nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST mlxsw: pci: Recycle received packet upon allocation failure net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent net: nxp: lpc_eth.c: avoid hang when bringing interface down net/tls: Fix flipped sign in async_wait.err assignment phy: phy_ethtool_ksettings_get: Lock the phy for consistency phy: phy_ethtool_ksettings_set: Move after phy_start_aneg phy: phy_start_aneg: Add an unlocked version phy: phy_ethtool_ksettings_set: Lock the PHY while changing settings sctp: use init_tag from inithdr for ABORT chunk sctp: fix the processing for INIT_ACK chunk sctp: fix the processing for COOKIE_ECHO chunk sctp: add vtag check in sctp_sf_violation sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_ootb lan743x: fix endianness when accessing descriptors KVM: s390: clear kicked_mask before sleeping again KVM: s390:
[Kernel-packages] [Bug 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
This affects kernel >= 5.11. ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954633 Title: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: kernel: amd_pmc AMDI0005:00: SMU response timed out kernel: amd_pmc AMDI0005:00: suspend failed kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns -110 kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110 kernel: PM: noirq suspend of devices failed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
In Progress
Status in linux-firmware source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954612] Re: alsa/hda: the microphone can't be detected on a couple of lenovo machines
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid -- 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/1954612 Title: alsa/hda: the microphone can't be detected on a couple of lenovo machines Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] We plug a microphone in the audio jack, but the driver can't detect the microphone and we try to record sound via this mic, can't record any sound. [Fix] Backport one patch from upstream. [Test] Booting the patched kernel, open the gnome-sound-setting, plug a microphone, we could see the system detect the microphone, and use this mic to record sound, the sound is recorded successfully. [Where problems could occur] The change only applies to the specific machines with those SSIDs, it will not introduce regression on other machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] On ADL platform, I+N sku, get the cpufreq errors during boot-up, [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) The commit has been landed on mainline since v5.15-rc1. [Test Case] 1. boot-up the machine. 2. check dmesg if the cpufreq error is presented. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953286] Re: Add support for NVIDIA EC backlight
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1953286 Title: Add support for NVIDIA EC backlight Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some system equipped with NVIDIA GFX cannot change screen brightness. [Fix] Add new way to change brightness. [Test] After the fix is applied, there's a new backlight sysfs "nvidia_wmi_ec_backlight" can change the screen brightness. [Where problems could occur] The driver relies on BIOS to behave correctly. If the BIOS lies or has a bug, the new backlight interface will overtake other backlight interfaces. It's rather unlikely though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945348] Re: Yellow Carp S0i3 stability fix
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945348 Title: Yellow Carp S0i3 stability fix Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8. [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 [Fix] The patch fixes this by forcing exit gfxoff for sdma resume. The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519) [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware. = original descriptions = A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures. It will manifest as: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947092] Re: Headphone microphone not working on particular Dell laptops
came via upstream stable update ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1947092 Title: Headphone microphone not working on particular Dell laptops Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] The Dell Latitude 5430 series with Realtek audio codec ALC3254 fail to detect the headphone microphone and thus unable to do recording. [Fix] The realtek audio quirk ALC269_FIXUP_DELL4_MIC_NO_PRESENCE is required since the NID used for headphone microphone should be 0x1b instead of 0x1a, which is used for former ALC225/295 variants. [Test Case] 1. Plug in the headphone microphone on the particular Dell Latitude 5430 laptop 2. Make sure it's detected in Audio Settings. (pulseaudio) 3. Record the sound via the headphone microphone and check the recorded content. [Where problems could occur] No. Since the audio quirk only affect the machine with particular subsystem ID. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1947092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954611] Re: Let VMD follow host bridge PCIe settings
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1954611 Title: Let VMD follow host bridge PCIe settings Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Some platforms have endless AER message floods kernel log, slows done disk I/O. [Fix] Honor BIOS settings to disable AER for Intel VMD. [Test] Use dmesg to check kernel log, no more AER message since AER is disabled. [Where problem could occur] The patch copies PCIe settings from host bridge, so some PCIe features will be disabled as a result. This may not be desirable for some users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => New ** Changed in: linux (Ubuntu Jammy) Status: New => 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/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: In Progress Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] 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 1954646 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: In Progress Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.42.46~20.04.20)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.42.46~20.04.20) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.13 (s390x, ppc64el, amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954463] 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 1954463 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/1954463 Title: KVM ROP Control-Flow Enforcement Tech (CET) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: Control-Flow Enforcement Tech (CET) What is Intel CET: Control-flow Enforcement Technology (CET) provides protection against return/jump-oriented programming (ROP) attacks. It can be implemented to protect both the kernel and applications. In the first phase, only the user-mode protection is implemented on the 64-bit kernel. However, 32-bit applications are supported under the compatibility mode. CET includes shadow stack (SHSTK) and indirect branch tracking (IBT). The SHSTK is a secondary stack allocated from memory. The processor automatically pushes/pops a secure copy to the SHSTK every return address and, by comparing the secure copy to the program stack copy, verifies function returns are as intended. The IBT verifies all indirect CALL/JMP targets are intended and marked by the compiler with 'ENDBR' op codes. Why need this technology(CET VMX): CET also can provide ROP attack in guest OS with VMX HW support. This will enhance platform security in Cloud computing, it's meaningful for Cloud service providers. Key change in kvm: To enable KVM based CET feature for guest OS, we need to : 1) Expose the features(CET SHSTK/IBT) to guest OS via CPUID report. 2) Enable xsaves/xrstors support for guest OS. 3) Fix xsaves/xrstors issue in existing KVM code. 4) Enabled CET states loading in guest entry/exit. 5) Add CET VMX related definitions. Key change in Qemu-kvm: expose CET related CPUID and xsaves/xrstors support to guest. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.13 (Ubuntu Impish) ** No longer affects: linux-oem-5.13 (Ubuntu Jammy) ** No longer affects: linux-oem-5.14 (Ubuntu Impish) ** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => New ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- 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/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- 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/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] 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 1954646 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] [NEW] [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
Public bug reported: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1945164 sutton ** Tags added: oem-priority originate-from-1945164 sutton ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954473] Re: KVM Shared Virtual Memory (SVM)
** Tags added: intel-bug-december-2021 -- 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/1954473 Title: KVM Shared Virtual Memory (SVM) Status in linux package in Ubuntu: Incomplete Bug description: SVM is short for shared virtual memory. This task is aiming at enabling SVM support for assigned devices on KVM. Example: assign a GPU from host to guest, the application program running in guest could share its virtual memory address to the assigned device. Latest update: extend the vIOMMU in QEMU to support SVM feature. 1. Description of the Technology. SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows sharing application virtual address space with the I/O device. The feature works with the PCI sig Process Address Space ID (PASID). SVM has the following benefits: • Programmer gets a consistent view of memory across host application and device • Efficient access to data, avoiding pining or copying overheads 2. Use cases that is important for this technology (aka, why is this technology needed). Intel has multiple IPs that would support SVM, and the usage in guest is also a demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to benefit from its advantages. 3. General design description (components modified: kvm, qemu-kvm, driver, libvirt (and other userland libraries)) Modified components would include: qemu-kvm, vfio driver, iommu driver Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954469] Re: KVM Bus Lock Debug Exception
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one seems to refer to older qemu/kernel versions. Here you really need to specify what you'd need where - otherwise all we can do is consider that already fixed. TL;DR: linux 5.13 is in Ubuntu 21.10 [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Tags added: intel-bug-december-2021 -- 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/1954469 Title: KVM Bus Lock Debug Exception Status in linux package in Ubuntu: Fix Released Bug description: A bus lock is acquired either through split locked access to writeback (WB) memory or by using locks to uncacheable (UC) memory. This is typically > 1000 cycles slower than atomic operation within a cache line. It also disrupts performance on other cores (which must wait for the bus lock to be released before their memory operations). Bus lock debug exception is a sub-feature of bus lock detection. It is an ability to notify the kernel by an #DB trap after the instruction acquires a bus lock when CPL>0. This allows the kernel to enforce user application throttling or mitigations. A logical processor can be configured to generate a debug exception (#DB) following acquisition of a bus lock. Software enables those debug exceptions by setting bit 2 of the IA32_DEBUGCTL MSR. The CPU enumerates this feature using CPUID.(EAX=7, ECX=0).ECX[24]. A debug exception due to acquistion of a bus lock is reported as a trap following execution of the instruction acquiring the bus lock. The processor identifies such debug exceptions using bit 11 of DR6: delivery of a bus-lock #DB clears DR6[11]. Linux 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954465] Re: KVM AIA User IPI
** Tags added: intel-bug-december-2021 -- 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/1954465 Title: KVM AIA User IPI Status in linux package in Ubuntu: Incomplete Bug description: SENDUIPI is a new ring-3 instruction that sending IPI notification between ring 3 software. It uses a data structure (table) owned and managed by ring 0 OS. Ring 3 software can choose which table entry to invoke. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954468] Re: KVM Architectural LBRs
** Tags added: intel-bug-december-2021 -- 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/1954468 Title: KVM Architectural LBRs Status in linux package in Ubuntu: Incomplete Bug description: Architectural LBRs (Last Branch Records) Architectural LBRs (Last Branch Records) enable recording of software path history by logging taken branches and other control flow transfers within model-specific registers, and is inherited from legacy LBR. If CPUID.(EAX=07H, ECX=0):EDX[19] is set to 1, the processor supports Architectural LBRs. With VMCS support and XSAVE support, the KVM guests could also use ARCH LBR as well. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954463] Re: KVM ROP Control-Flow Enforcement Tech (CET)
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one also contains a reference to qemu changes. Therefore I'll add a src:qemu bug task. I have not found an upstream commit for "expose CET related CPUID and xsaves/xrstors support to guest" - the same as with the kernel changes, please refer to an upstream commit including the hash. There are a few xsaves changes in qemu 6.1 but none with your title, did you mean those? [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Incomplete ** Tags added: intel-bug-december-2021 -- 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/1954463 Title: KVM ROP Control-Flow Enforcement Tech (CET) Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: Control-Flow Enforcement Tech (CET) What is Intel CET: Control-flow Enforcement Technology (CET) provides protection against return/jump-oriented programming (ROP) attacks. It can be implemented to protect both the kernel and applications. In the first phase, only the user-mode protection is implemented on the 64-bit kernel. However, 32-bit applications are supported under the compatibility mode. CET includes shadow stack (SHSTK) and indirect branch tracking (IBT). The SHSTK is a secondary stack allocated from memory. The processor automatically pushes/pops a secure copy to the SHSTK every return address and, by comparing the secure copy to the program stack copy, verifies function returns are as intended. The IBT verifies all indirect CALL/JMP targets are intended and marked by the compiler with 'ENDBR' op codes. Why need this technology(CET VMX): CET also can provide ROP attack in guest OS with VMX HW support. This will enhance platform security in Cloud computing, it's meaningful for Cloud service providers. Key change in kvm: To enable KVM based CET feature for guest OS, we need to : 1) Expose the features(CET SHSTK/IBT) to guest OS via CPUID report. 2) Enable xsaves/xrstors support for guest OS. 3) Fix xsaves/xrstors issue in existing KVM code. 4) Enabled CET states loading in guest entry/exit. 5) Add CET VMX related definitions. Key change in Qemu-kvm: expose CET related CPUID and xsaves/xrstors support to guest. Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954464] Re: kvm SPR support for AMX
** Tags added: intel-bug-december-2021 -- 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/1954464 Title: kvm SPR support for AMX Status in linux package in Ubuntu: Incomplete Bug description: AMX (including XFD): AMX (Advance Matrix eXtensions) is a new programming paradigm for direct matrix operations. TMUL (TILE Matrix mULtiply unit) is the multiply accelerator. XFD (Extended Feature Disable) is an XSAVE extension mechanism for those features with large XSAVE storage context, that enables the OS not pre-allocate the space initially. AMX is the first one using XFD feature. Use cases: Deep learning inference and training (CNN, DNN), other data analytics and machine learning apps, HPC SGEMM Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954471] Re: KVM AIA Work Dispatch Instructions
Hi Paul, Bugs in launchpad are filed against source packages, and "src:kvm" doesn't exist for more than 8 years now :-) Instead you'd want to file it against the package the code is in, in your case most likely src:qemu [1] or src:linux [2]. Also you should talk about the target Ubuntu release you want the fix to be in. I assume from the type of bug that you want to feature request for the coming LTS Ubuntu 22.04 - but please clarify to be sure. Finally referencing to features/commits works much better if you could please include the hashes of the commits. Please consider doing so once they exist upstream. If they are not existing there someone needs to provide the patches upfront and convince the team that they are stable enough to be picked up. The referred kernel version is in the future, so that might be a normal bug for a new feature. I'll re-assign this to src:linux for now as your bug indicates that is the target. You opened a range of bugs in the same pass, other than most others - this one seems to refer to older qemu/kernel versions. Here you really need to specify what you'd need where - otherwise all we can do is consider that already fixed. TL;DR: qemu 4.2 is in Ubuntu 20.04 linux 5.4 is in Ubuntu 20.04 [1]: https://bugs.launchpad.net/ubuntu/+source/qemu [2]: https://bugs.launchpad.net/ubuntu/+source/linux ** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Fix Released ** Tags added: intel-bug-december-2021 -- 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/1954471 Title: KVM AIA Work Dispatch Instructions Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Bug description: AIA has 3 sub features: AIA User Interrupts AIA User Wait Instructions AIA Work Dispatch Instructions AIA User Wait Instructions was merged for SNR in Kernel 5.4/Qemu4.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954472] Re: KVM Scalable I/O Virtualization
** Tags added: intel-bug-december-2021 -- 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/1954472 Title: KVM Scalable I/O Virtualization Status in linux package in Ubuntu: Incomplete Bug description: Core OS/ VMM device virtualization framework extended to support Scalable IOV; OS/ VMM support for Scalable IOV IOMMU extensions; PASID translation support; existing device frameworks extended to support Scalable IOV; converged SW arch as prescribed by spec Improved performance and lower complexity for software utilizing PCIe devices in virtualized environments Software Benefits: Broad range of usages, e.g. security, comms, server graphics Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954466] Re: KVM Protection Keys for Supervisor Pages (PKS)
** Tags added: intel-bug-december-2021 -- 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/1954466 Title: KVM Protection Keys for Supervisor Pages (PKS) Status in linux package in Ubuntu: Incomplete Bug description: SKX introduced the Protection Key for User Pages (PKU) feature enabling fast, thread-specific manipulation of permission restrictions on user pages. SPR introduced Protection Key for Supervisor Pages(PKS), a new feature that extends the Protection Key architecture to support thread-specific permission restrictions on supervisor pages. This important feature enables enhanced access control on memory, and brings more valid usage model. Generally PKS enables protections on 'domains' of supervisor pages to limit supervisor mode access to pages beyond the normal paging protections(U/S, R/W, P). PKS works in a similar fashion to user space pkeys, PKU. As with PKU, supervisor pkeys are checked in addition to normal paging protections and Access or Writes can be disabled via a MSR update without TLB flushes when permissions change. PKS virtualization enabling should base on existing PKU code. Major works: CPUID exposure New CR4 bit exposure New VMCS fields enabling IA32_PKRS saving/restoring #GP handling Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954474] Re: KVM notify VM Exit
** Tags added: intel-bug-december-2021 -- 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/1954474 Title: KVM notify VM Exit Status in linux package in Ubuntu: Incomplete Bug description: A VMM can enable notification VM exits to occur if no interrupt windows occur in VMX non-root operation for a specified amount of time (notify window). KVM Enabling: enable bit 31 of secondary processor-based excution control. enable notification VM exit (exit reason 75) handler. expose a module param to configure notify window and disable/enable VM notify. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954472] 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 1954472 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/1954472 Title: KVM Scalable I/O Virtualization Status in linux package in Ubuntu: Incomplete Bug description: Core OS/ VMM device virtualization framework extended to support Scalable IOV; OS/ VMM support for Scalable IOV IOMMU extensions; PASID translation support; existing device frameworks extended to support Scalable IOV; converged SW arch as prescribed by spec Improved performance and lower complexity for software utilizing PCIe devices in virtualized environments Software Benefits: Broad range of usages, e.g. security, comms, server graphics Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954473] 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 1954473 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/1954473 Title: KVM Shared Virtual Memory (SVM) Status in linux package in Ubuntu: Incomplete Bug description: SVM is short for shared virtual memory. This task is aiming at enabling SVM support for assigned devices on KVM. Example: assign a GPU from host to guest, the application program running in guest could share its virtual memory address to the assigned device. Latest update: extend the vIOMMU in QEMU to support SVM feature. 1. Description of the Technology. SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows sharing application virtual address space with the I/O device. The feature works with the PCI sig Process Address Space ID (PASID). SVM has the following benefits: • Programmer gets a consistent view of memory across host application and device • Efficient access to data, avoiding pining or copying overheads 2. Use cases that is important for this technology (aka, why is this technology needed). Intel has multiple IPs that would support SVM, and the usage in guest is also a demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to benefit from its advantages. 3. General design description (components modified: kvm, qemu-kvm, driver, libvirt (and other userland libraries)) Modified components would include: qemu-kvm, vfio driver, iommu driver Target Linux 5.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954474] 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 1954474 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/1954474 Title: KVM notify VM Exit Status in linux package in Ubuntu: Incomplete Bug description: A VMM can enable notification VM exits to occur if no interrupt windows occur in VMX non-root operation for a specified amount of time (notify window). KVM Enabling: enable bit 31 of secondary processor-based excution control. enable notification VM exit (exit reason 75) handler. expose a module param to configure notify window and disable/enable VM notify. Target Linux 5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954469] [NEW] KVM Bus Lock Debug Exception
You have been subscribed to a public bug: A bus lock is acquired either through split locked access to writeback (WB) memory or by using locks to uncacheable (UC) memory. This is typically > 1000 cycles slower than atomic operation within a cache line. It also disrupts performance on other cores (which must wait for the bus lock to be released before their memory operations). Bus lock debug exception is a sub-feature of bus lock detection. It is an ability to notify the kernel by an #DB trap after the instruction acquires a bus lock when CPL>0. This allows the kernel to enforce user application throttling or mitigations. A logical processor can be configured to generate a debug exception (#DB) following acquisition of a bus lock. Software enables those debug exceptions by setting bit 2 of the IA32_DEBUGCTL MSR. The CPU enumerates this feature using CPUID.(EAX=7, ECX=0).ECX[24]. A debug exception due to acquistion of a bus lock is reported as a trap following execution of the instruction acquiring the bus lock. The processor identifies such debug exceptions using bit 11 of DR6: delivery of a bus-lock #DB clears DR6[11]. Linux 5.13 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- KVM Bus Lock Debug Exception https://bugs.launchpad.net/bugs/1954469 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
