[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
Enable the impish-proposed on the Dell machine with has the USB 4050 audio codec, $apt-get update;$apt install alsa-ucm-conf, now the 1.2.4-2ubuntu6 is installed, reboot the machine, open the gnome-sound- setting, we could see the speaker, headset and lineout from the UI, and all of them could work correctly. Verification done for Impish. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
@Seb, You are right, the Jammy has the alsa-ucm-conf-2.6.3, and the fix is already in the v2.6.3, no need to apply SRU patch to Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961850] Re: [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap
Since the patch got upstream with 5.16, I think it needs to be applied to Impish/5.13 and jammy/5.15, too. ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1961850 Title: [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: s390/pci: move pseudo-MMIO to prevent MIO overlap Symptom: On some configurations of z15 LPARs having an ISM device attached may cause other PCI devices like NVMes or RoCEs to be unusable and fail to probe. An error message in the kernel log indicates that a PCI memory BAR could not be assigned. Problem: On z15 with the enhanced PCI memory I/O instructions (MIO) ISM devices still rely on the classic PCI instructions which used pseud-MMIO addresses created by Linux. These addresses can conflict with the firmware created MIO addresses which is detected by the Linux PCI resource allocation code which then prevents probing of the device even though technically the address conflict would not cause issues. Solution: Use disjunct ranges for Linux generated pseudo-MMIO and firmware provided MIO addresses. Reproduction: On an LPAR with a lot of PCI devices and in particular many ISM devices the conflict is more likely. It is however unclear how to provoke a conflict without special firmware. The fix was and will be tested on a known affected system. Upstream-ID: 52d04d408185b7aa47628d2339c28ec70074e0ae Distros: Ubuntu 20.04 and higher Preventive:yes Author:Niklas Schnelle Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961746] Re: assertion triggered in link_enc_cfg_validate in amdgpu on resume from s2idle
Correct: Impish 5.13 kernel is not affected by this issue as that assertion doesn't even exist. ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: In Progress => 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/1961746 Title: assertion triggered in link_enc_cfg_validate in amdgpu on resume from s2idle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux 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.14 source package in Jammy: Invalid Bug description: The following WARNING shows up on resume from s2idle on HP Z13/Z16: [ 136.701141] [ cut here ] [ 136.701146] WARNING: CPU: 0 PID: 1630 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_enc_cfg.c:588 link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701417] Modules linked in: hid_logitech_hidpp hid_logitech_dj michael_mic rfcomm snd_usb_audio snd_usbmidi_lib cmac algif_hash r8153_ecm algif_skcipher qrtr_mhi r8152 af_alg cdc_mbim cdc_wdm cdc_ncm cdc_ether usbnet joydev mii intel_rapl_msr intel_rapl_common bnep edac_mce_amd snd_acp6x_pdm_dma snd_soc_dmic snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine qrtr ns snd_ctl_led ath11k_pci ath11k snd_hda_codec_realtek nls_iso8859_1 qmi_helpers snd_hda_codec_generic amdgpu mac80211 kvm iommu_v2 gpu_sched drm_ttm_helper snd_hda_codec_hdmi btusb crct10dif_pclmul ttm btrtl thinkpad_acpi ghash_clmulni_intel uvcvideo btbcm snd_seq_midi btintel snd_hda_intel nvram videobuf2_vmalloc snd_seq_midi_event snd_intel_dspcfg aesni_intel drm_kms_helper videobuf2_memops snd_intel_sdw_acpi bluetooth videobuf2_v4l2 videobuf2_common think_lmi crypto_simd cec input_leds snd_hda_codec videodev cryptd platform_profile usbhid efi_pstore ecdh_generic serio_raw rapl cfg80211 wmi_bmof [ 136.701485] firmware_attributes_class ecc ledtrig_audio mc rc_core snd_rawmidi snd_hda_core snd_pci_acp6x snd_hwdep i2c_algo_bit fb_sys_fops mhi snd_seq syscopyarea snd_pcm sysfillrect libarc4 sysimgblt snd_rn_pci_acp3x snd_seq_device snd_pci_acp3x snd_timer ccp snd soundcore hid_sensor_accel_3d hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mac_hid amd_pmc industrialio acpi_tad sch_fq_codel msr parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_sensor_hub hid_generic crc32_pclmul psmouse nvme i2c_piix4 nvme_core xhci_pci amd_sfh xhci_pci_renesas wmi i2c_hid_acpi video i2c_hid hid [ 136.701526] CPU: 0 PID: 1630 Comm: Xorg Not tainted 5.14.0-1022-oem #24-Ubuntu [ 136.701530] Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET11WQ (0.11 ) 01/14/2022 [ 136.701532] RIP: 0010:link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701930] Code: 83 7d 10 00 74 24 0f b6 83 e0 01 00 00 49 83 c4 01 44 39 e0 7f d4 45 84 ff 74 0f 80 7d 8b 00 74 09 0f b6 45 90 44 20 f0 75 04 <0f> 0b 31 c0 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4d c8 [ 136.701933] RSP: 0018:a7c28284f980 EFLAGS: 00010246 [ 136.701936] RAX: RBX: 8e9304ac RCX: [ 136.701937] RDX: 0201 RSI: a7c28284f8b8 RDI: 8e930a628000 [ 136.701939] RBP: a7c28284f9f8 R08: 0014 R09: 8e937ad0 [ 136.701940] R10: 0031 R11: R12: 0001 [ 136.701941] R13: 8e934a160800 R14: R15: 0001 [ 136.701942] FS: 7f546a3a4a40() GS:8e9a5da0() knlGS: [ 136.701944] CS: 0010 DS: ES: CR0: 80050033 [ 136.701945] CR2: 7f70efb5f500 CR3: 0001100f6000 CR4: 00750ef0 [ 136.701947] PKRU: 5554 [ 136.701948] Call Trace: [ 136.701950] [ 136.701953] link_enc_cfg_link_encs_assign+0x1c9/0x3b0 [amdgpu] [ 136.702129] dc_validate_global_state+0x57/0x330 [amdgpu] [ 136.702310] ? drm_modeset_lock+0x8e/0xb0 [drm] [ 136.702357] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 [ 136.702366] amdgpu_dm_atomic_check+0x8e2/0xef0 [amdgpu] [ 136.702558] ? __slab_alloc+0x20/0x40 [ 136.702562] ? __kmalloc_track_caller+0x1aa/0x490 [ 136.702565] ? amdgpu_dm_connector_atomic_duplicate_state+
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
Yes, please use the upstream version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958004] Re: intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-February/128255.html (jammy) ** Description changed: + [SRU Justfication] + + + [Impact] + + Intel iommu was turned on by default in mainline build v5.15.5 or jammy + -generic kernel 5.15.0-12.12. This would breaks IPU6. + + [ 6.681241] intel-ipu6 intel-ipu: IPU driver version 1.0 + [ 7.056166] DMAR: DRHD: handling fault status reg 2 + [ 7.056169] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault + addr 0x11b1d4000 [fault reason 0x06] PTE Read access is not set + [ 7.056421] DMAR: DRHD: handling fault status reg 2 + [ 7.056422] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault + addr 0x3fff000 [fault reason 0x06] PTE Read access is not set + [ 7.056456] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 + [ 7.056637] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 + [ 7.056652] DMAR: DRHD: handling fault status reg 2 + [ 7.056653] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault + addr 0x3fff000 [fault reason 0x06] PTE Read access is not set + [ 7.056882] DMAR: DRHD: handling fault status reg 2 + [ 8.197149] intel-ipu6-isys intel-ipu6-isys0: isys port open ready + failed -16 + [ 8.197157] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16 + [ 10.201677] intel-ipu6-isys intel-ipu6-isys0: Device release time out + -16 + [ 10.240523] intel-ipu6-isys intel-ipu6-isys0: Clearing old context + + [Fix] + + Use IOMMU passthrough mode for IPU6 as it has its own iommu hardware. + + [Test Case] + + Apply the fix and kernel should print a new info line: + + Passthrough IOMMU for integrated Intel IPU + + and IPU6 camera should continue to work without intel_iommu=off + work-around. + + [Where problems could occur] + + No. That's what it should have been done. + + [Other Info] + + This only affects kernel >= 5.15, so only Jammy is nominated. + + Intel IPU6 driver has been proposed for Jammy for hwe-5.15 migration in + bug 1955383 + (https://lists.ubuntu.com/archives/kernel-team/2021-December/126749.html). + The port for 5.17 unstable would be filed soon. Still under discussion. + + While there is no plan for Intel to upstream Intel IPU6 driver before + kernel camera API is out, these extra prerequisite patches will only be + staged in a separate patches folder in the upstream repository. + + == original bug description == + Intel iommu was turned on by default in mainline build v5.15.5 or jammy -generic kernel 5.15.0-12.12. This would breaks IPU6 leaving error messages: [6.681241] intel-ipu6 intel-ipu: IPU driver version 1.0 [7.056166] DMAR: DRHD: handling fault status reg 2 [7.056169] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 0x11b1d4000 [fault reason 0x06] PTE Read access is not set [7.056421] DMAR: DRHD: handling fault status reg 2 [7.056422] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 0x3fff000 [fault reason 0x06] PTE Read access is not set [7.056456] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [7.056637] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [7.056652] DMAR: DRHD: handling fault status reg 2 [7.056653] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 0x3fff000 [fault reason 0x06] PTE Read access is not set [7.056882] DMAR: DRHD: handling fault status reg 2 [8.197149] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16 [8.197157] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16 [ 10.201677] intel-ipu6-isys intel-ipu6-isys0: Device release time out -16 [ 10.240523] intel-ipu6-isys intel-ipu6-isys0: Clearing old context ... This can be worked-around with intel_iommu=off. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: - + DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (26 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.25+staging.42 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-2017-generic root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash
[Kernel-packages] [Bug 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Thanks for the bug report. bluez has not changed at all since 2022-01-13 so the problem isn't going to be that. Next I would usually blame the kernel but that hasn't changed since 2022-01-27. I don't see anything in comment #2 related to Bluetooth either (maybe pipewire?). Can you provide more of the log? ** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in Ubuntu: Incomplete Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 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.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Can you please also attach dmesg under mainline kernel 5.15? -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961823] Re: [RTL8822BE] Bluetooth adapter not found
** Summary changed: - Bluetooth button off and doesn't work + [RTL8822BE] Bluetooth adapter not found ** Package changed: bluez (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961823 Title: [RTL8822BE] Bluetooth adapter not found Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Bluetooth button off and doesn't work the massage that show me when i open the setting " No Bluetooth Found plug in a dongle to use Bluetooth " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 21:08:36 2022 InstallationDate: Installed on 2022-02-17 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da1xxx dmi.product.sku: 6EX79EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep
It looks like the amdgpu kernel driver encountered errors while entering sleep: Feb 22 06:01:35 day-oper kernel: amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x11665a680 flags=0x0070] Feb 22 06:01:35 day-oper kernel: amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x11665a720 flags=0x0070] Feb 22 06:01:35 day-oper kernel: amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x11665a690 flags=0x0070] Feb 22 06:01:35 day-oper kernel: amdgpu :00:01.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x11665a730 flags=0x0070] Although I'm not sure if that's really relevant. ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => New -- 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/1961608 Title: [amdgpu] Screen freeze after wake from sleep Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Any time the computer sleeps, and I wake it the screen backlight turns on but nothing appears. This has been occurring since upgrading to Kernel 5.11-44. I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 without issues. I have tried multiple 5.13 releases and none of them handle sleep and wakeup successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 11:13:07 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2022-01-02 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958004] Re: intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958004 Title: intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 Status in linux package in Ubuntu: In Progress Bug description: Intel iommu was turned on by default in mainline build v5.15.5 or jammy -generic kernel 5.15.0-12.12. This would breaks IPU6 leaving error messages: [6.681241] intel-ipu6 intel-ipu: IPU driver version 1.0 [7.056166] DMAR: DRHD: handling fault status reg 2 [7.056169] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 0x11b1d4000 [fault reason 0x06] PTE Read access is not set [7.056421] DMAR: DRHD: handling fault status reg 2 [7.056422] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 0x3fff000 [fault reason 0x06] PTE Read access is not set [7.056456] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [7.056637] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [7.056652] DMAR: DRHD: handling fault status reg 2 [7.056653] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 0x3fff000 [fault reason 0x06] PTE Read access is not set [7.056882] DMAR: DRHD: handling fault status reg 2 [8.197149] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16 [8.197157] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16 [ 10.201677] intel-ipu6-isys intel-ipu6-isys0: Device release time out -16 [ 10.240523] intel-ipu6-isys intel-ipu6-isys0: Clearing old context ... This can be worked-around with intel_iommu=off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (26 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.25+staging.42 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-2017-generic root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-2017.17~20.04.1+lp1955383.2-generic 5.15.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-2017-generic N/A linux-backports-modules-5.15.0-2017-generic N/A linux-firmware 1.187.25+staging.42 Tags: third-party-packages focal Uname: Linux 5.15.0-2017-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect
** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => New -- 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/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961855] Re: Fix With 20.04d kernel and WX3200, unit freezes on resume
** Tags added: oem-priority originate-from-1952981 somerville
--
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/1961855
Title:
Fix With 20.04d kernel and WX3200, unit freezes on resume
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]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
* PPC64LE hardware does not support ASPM at a hardware level.
CONFIG_PCIEASPM is often disabled on these architectures.
* Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe
subsystem disables it
Check with the PCIe subsystem to see that ASPM has been enabled
or not.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend&resume machine
3. check if machine could resume successfully
[Where problems could occur]
Low, just disable AMDGPU ASPM if system doesn't enable it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1961855/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961855] [NEW] Fix With 20.04d kernel and WX3200, unit freezes on resume
Public bug reported:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
* PPC64LE hardware does not support ASPM at a hardware level.
CONFIG_PCIEASPM is often disabled on these architectures.
* Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe
subsystem disables it
Check with the PCIe subsystem to see that ASPM has been enabled
or not.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend&resume machine
3. check if machine could resume successfully
[Where problems could occur]
Low, just disable AMDGPU ASPM if system doesn't enable it.
** 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)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => koba (kobako)
--
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/1961855
Title:
Fix With 20.04d kernel and WX3200, unit freezes on resume
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]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
* PPC64LE hardware does not support ASPM at a hardware level.
CONFIG_PCIEASPM is often disabled on these architectures.
* Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe
subsystem disables it
Check with the PCIe subsystem to see that ASPM has been enabled
or not.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend&resume machine
3. check if machine could resume successfully
[Where problems could occur]
Low, just disable AMDGPU ASPM if system doesn't enable it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961855/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] Re: bcmwl does not build with Kernel 5.17
This is my attempt at getting around the warning message, but clearly, more work will need to be done to update the driver for post-5.17. With just the following part of the patch the driver builds and runs fine on kernel 5.17-rc5. diff -Npaur a/src/wl/sys/wl_linux.c b/src/wl/sys/wl_linux.c --- a/src/wl/sys/wl_linux.c 2015-09-18 18:47:30.0 -0400 +++ b/src/wl/sys/wl_linux.c 2022-02-22 13:49:55.219274100 -0500 @@ -73,6 +74,10 @@ #error "No support for Kernel Rev <= 2.4.5, As the older kernel revs doesn't support Tasklets" #endif +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5, 17, 0)) +#define PDE_DATA pde_data +#endif + #include #include #include ** Patch removed: "Updated patch which allows compile but still causes a warning" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562822/+files/0030-add-support-for-Linux-5.17.patch ** Patch added: "0030-add-support-for-Linux-5.17.patch" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562847/+files/0030-add-support-for-Linux-5.17.patch ** Summary changed: - bcmwl does not build with Kernel 5.17 + bcmwl builds with Kernel 5.17 w/ one small patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl builds with Kernel 5.17 w/ one small patch Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961850] [NEW] [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap
Public bug reported: Description: s390/pci: move pseudo-MMIO to prevent MIO overlap Symptom: On some configurations of z15 LPARs having an ISM device attached may cause other PCI devices like NVMes or RoCEs to be unusable and fail to probe. An error message in the kernel log indicates that a PCI memory BAR could not be assigned. Problem: On z15 with the enhanced PCI memory I/O instructions (MIO) ISM devices still rely on the classic PCI instructions which used pseud-MMIO addresses created by Linux. These addresses can conflict with the firmware created MIO addresses which is detected by the Linux PCI resource allocation code which then prevents probing of the device even though technically the address conflict would not cause issues. Solution: Use disjunct ranges for Linux generated pseudo-MMIO and firmware provided MIO addresses. Reproduction: On an LPAR with a lot of PCI devices and in particular many ISM devices the conflict is more likely. It is however unclear how to provoke a conflict without special firmware. The fix was and will be tested on a known affected system. Upstream-ID: 52d04d408185b7aa47628d2339c28ec70074e0ae Distros: Ubuntu 20.04 and higher Preventive:yes Author:Niklas Schnelle Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-196506 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-196506 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961850 Title: [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap Status in linux package in Ubuntu: New Bug description: Description: s390/pci: move pseudo-MMIO to prevent MIO overlap Symptom: On some configurations of z15 LPARs having an ISM device attached may cause other PCI devices like NVMes or RoCEs to be unusable and fail to probe. An error message in the kernel log indicates that a PCI memory BAR could not be assigned. Problem: On z15 with the enhanced PCI memory I/O instructions (MIO) ISM devices still rely on the classic PCI instructions which used pseud-MMIO addresses created by Linux. These addresses can conflict with the firmware created MIO addresses which is detected by the Linux PCI resource allocation code which then prevents probing of the device even though technically the address conflict would not cause issues. Solution: Use disjunct ranges for Linux generated pseudo-MMIO and firmware provided MIO addresses. Reproduction: On an LPAR with a lot of PCI devices and in particular many ISM devices the conflict is more likely. It is however unclear how to provoke a conflict without special firmware. The fix was and will be tested on a known affected system. Upstream-ID: 52d04d408185b7aa47628d2339c28ec70074e0ae Distros: Ubuntu 20.04 and higher Preventive:yes Author:Niklas Schnelle Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961850] [NEW] [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap
You have been subscribed to a public bug: Description: s390/pci: move pseudo-MMIO to prevent MIO overlap Symptom: On some configurations of z15 LPARs having an ISM device attached may cause other PCI devices like NVMes or RoCEs to be unusable and fail to probe. An error message in the kernel log indicates that a PCI memory BAR could not be assigned. Problem: On z15 with the enhanced PCI memory I/O instructions (MIO) ISM devices still rely on the classic PCI instructions which used pseud-MMIO addresses created by Linux. These addresses can conflict with the firmware created MIO addresses which is detected by the Linux PCI resource allocation code which then prevents probing of the device even though technically the address conflict would not cause issues. Solution: Use disjunct ranges for Linux generated pseudo-MMIO and firmware provided MIO addresses. Reproduction: On an LPAR with a lot of PCI devices and in particular many ISM devices the conflict is more likely. It is however unclear how to provoke a conflict without special firmware. The fix was and will be tested on a known affected system. Upstream-ID: 52d04d408185b7aa47628d2339c28ec70074e0ae Distros: Ubuntu 20.04 and higher Preventive:yes Author:Niklas Schnelle Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-196506 severity-high targetmilestone-inin--- -- [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap https://bugs.launchpad.net/bugs/1961850 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Start-Date: 2022-02-21 01:16:18 Commandline: apt -y upgrade Requested-By: tps (1000) Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1, 97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf-nobfd0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), systemd-container:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libqmi-proxy:amd64 (1.30.2-1, 1.30.4-1), gir1.2-snapd-1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), systemd-timesyncd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libpam-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libarchive13:amd64 (3.5.2-1, 3.5.2-1ubuntu1), openmpi-bin:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), libbinutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libfwupd2:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libsnapd-glib1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), openmpi-common:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), liblvm2cmd2.03:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libsystemd0:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libsystemd0:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), binutils-x86-64-linux-gnu:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libnss-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), lvm2:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libnss-mymachines:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), dmsetup:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), python3-pil.imagetk:amd64 (9.0.0-1, 9.0.1-1), libhypre-2.22.1:amd64 (2.22.1-6, 2.22.1-7), libdevmapper-event1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils-common:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libqmi-glib5:amd64 (1.30.2-1, 1.30.4-1), python3-pil:amd64 (9.0.0-1, 9.0.1-1), libopenmpi3:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), systemd-sysv:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libfwupdplugin5:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libdevmapper1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), fwupd:amd64 (1.7.4-1ubuntu1, 1.7.5-3) End-Date: 2022-02-21 01:18:20 Start-Date: 2022-02-21 01:18:24 Commandline: apt -y dist-upgrade Requested-By: tps (1000) Install: libnfsidmap1:amd64 (1:2.6.1-1~exp1ubuntu1, automatic) Upgrade: nfs-common:amd64 (1:1.3.4-6ubuntu1, 1:2.6.1-1~exp1ubuntu1) Remove: libnfsidmap2:amd64 (0.25-6build1) End-Date: 2022-02-21 01:18:28 Start-Date: 2022-02-22 07:07:20 Commandline: apt -y upgrade Requested-By: tps (1000) Install: polkitd:amd64 (0.105-32, automatic), pkexec:amd64 (0.105-32, automatic) Upgrade: libpolkit-agent-1-0:amd64 (0.105-31.1, 0.105-32), libsmartcols1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), debconf-i18n:amd64 (1.5.79, 1.5.79ubuntu1), apt:amd64 (2.3.15, 2.3.15build1), packagekit-tools:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libxcb-image0:amd64 (0.4.0-1build2, 0.4.0-2), zfs-zed:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libpipewire-0.3-common:amd64 (0.3.45-1, 0.3.47-1ubuntu1), zfs-initramfs:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libaom3:amd64 (3.2.0-2, 3.3.0-1), libjpeg-turbo8:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libjpeg-turbo8:i386 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libnvpair3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), grub-pc-bin:amd64 (2.06-2ubuntu4, 2.06-2ubuntu5), libapt-pkg6.0:amd64 (2.3.15, 2.3.15build1), libuutil3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), debconf:amd64 (1.5.79, 1.5.79ubuntu1), libmount1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libmount1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libzpool5linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), system-config-printer-udev:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), pipewire:amd64 (0.3.45-1, 0.3.47-1ubuntu1), libqpdf28:amd64 (10.5.0-1, 10.6.2-1), gir1.2-packagekitglib-1.0:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), util-linux:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libjpeg-turbo-progs:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), fdisk:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libfdisk1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), system-config-printer-common:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), eject:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), packagekit:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libturbojpeg:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libuuid1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libuuid1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), make:amd64 (4.3-4ubuntu2, 4.3-4.1build1), uuid-runtime:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), grub-efi-amd64-signed:amd64 (1.177+2.06-2ubuntu4, 1.178+2.06-2ubuntu5), libjpeg-turbo8-dev:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libpolkit-gobject-1-0:amd64 (0.105-31.1, 0.105-32), gir1.2-polkit-1.0:amd64 (0.105-31.1, 0.105-32), libpackagekit-glib2-18:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), pipewire-bin:amd64 (0.3.45-1, 0.3.47-1ubuntu1), system-config-printer:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), grub-efi-amd64-bin:a
[Kernel-packages] [Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects
Public bug reported: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 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.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in bluez package in Ubuntu: New Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 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.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage notifications about this
[Kernel-packages] [Bug 1958410] Re: bytcr_rt5640 sound not working with kernel >= 5.13
Also affects my Archos Cesium 90 with the same basic specification I found booting back to the 5.11 kernel in grub after the 5.13 kernel upgrade while returning audio had pitch shifted the audio very low and caused slow video playback The only current solution I have is to install the generic 5.4 kernel and remove the HWE packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958410 Title: bytcr_rt5640 sound not working with kernel >= 5.13 Status in linux-meta-hwe-5.13 package in Ubuntu: Confirmed Bug description: Using the built in speakers on a Linx 1010b. The 5.11 kernel works fine, but 5.13 and 5.14 fail. The card, when working is seen in alsa-info as bytcrrt5640,bytcr- rt5640, whereas in the later (hwe-20.04-edge, oem-20.04d) kernels where it fails, it is seen as "rt5640,sof-bytcht rt5640" When failing, speaker-test, spd-say, and most other sound sources seem to get 'sunk', and the level meter on the pulse mixer shows activity. FWIW "espeak-ng hello" blocks on the broken setup. I confess I'm not actually using the linux-meta-hwe-5.13 as it is unavailable in LinuxMint. I am using linux-generic-hwe-20.04-edge, which AFAICT pulls in the same kernels. apt policy pointed me to report here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1958410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] Re: bcmwl does not build with Kernel 5.17
This happens because of https://github.com/torvalds/linux/commit/adeef3e32146a8d2a73c399dc6f5d76a449131b1 netdev->dev_addr is a const now... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961844] [NEW] 'Microsoft Touchpad' not detected in 'Maingear Vector Pro MG-VCP17I-3070' in kernel 5.4.0-99-generic
Public bug reported: I installed dual system (Window 10 and Ubuntu 18.04) on my MAINGEAR Vector Pro MG-VCP17I-3070 laptop. However, the touchpad worked in Window 10, but not in Ubuntu 18.04. I tried both 'xinput list' and 'cat /proc/bus/input/devices', but 'touchpad 'is not both of them. Window 10 shows that the manufacturer of the touchpad is Microsoft. The attached file is the result of 'cat /proc/bus/input/devices' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-99-generic 5.4.0-99.112~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 13:35:47 2022 InstallationDate: Installed on 2022-02-21 (1 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1961844/+attachment/5562823/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1961844 Title: 'Microsoft Touchpad' not detected in 'Maingear Vector Pro MG- VCP17I-3070' in kernel 5.4.0-99-generic Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: I installed dual system (Window 10 and Ubuntu 18.04) on my MAINGEAR Vector Pro MG-VCP17I-3070 laptop. However, the touchpad worked in Window 10, but not in Ubuntu 18.04. I tried both 'xinput list' and 'cat /proc/bus/input/devices', but 'touchpad 'is not both of them. Window 10 shows that the manufacturer of the touchpad is Microsoft. The attached file is the result of 'cat /proc/bus/input/devices' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-99-generic 5.4.0-99.112~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 13:35:47 2022 InstallationDate: Installed on 2022-02-21 (1 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1961844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] Re: bcmwl does not build with Kernel 5.17
(Worth noting that is a warning, and the network still works.) ** Patch removed: "Fix PDE_DATA change in 5.17" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562741/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] Re: bcmwl does not build with Kernel 5.17
** Patch added: "Updated patch which allows compile but still causes a warning" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562822/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] Re: bcmwl does not build with Kernel 5.17
This is the kernel issue I get with the expanded patch. [7.508238] [ cut here ] [7.508239] netdevice: wlp3s0: Incorrect netdev->dev_addr [7.508257] WARNING: CPU: 3 PID: 1710 at net/core/dev_addr_lists.c:517 dev_addr_check.cold+0x65/0x9f [7.508267] Modules linked in: cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common joydev mei_hdcp mei_pxp x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_cirrus snd_hda_codec_generic applesmc snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi btusb snd_hda_codec btrtl snd_hda_core kvm_intel btbcm btintel snd_hwdep btmtk snd_pcm kvm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event ecc rapl wl(POE) snd_rawmidi input_leds snd_seq bcm5974 intel_cstate snd_seq_device sbs snd_timer apple_mfi_fastcharge cfg80211 snd mei_me acpi_als industrialio_triggered_buffer efi_pstore mei kfifo_buf soundcore sbshc industrialio apple_gmux mac_hid apple_bl sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zzstd(OE) zlua(OE) zcommon(POE) znvpair(POE) zavl(POE) icp(POE) spl(OE) hid_apple hid_generic uas ax88179_178a usbhid usbnet usb_storage hid mii [7.508367] nouveau mxm_wmi wmi i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd cec nvme rc_core nvme_core i2c_i801 thunderbolt drm i2c_smbus lpc_ich xhci_pci xhci_pci_renesas video [7.508399] CPU: 3 PID: 1710 Comm: NetworkManager Tainted: P OE 5.17.0-051700rc5-generic #202202202230 [7.508403] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663, BIOS 432.60.3.0.0 10/27/2021 [7.508405] RIP: 0010:dev_addr_check.cold+0x65/0x9f [7.508411] Code: 01 e8 9e 2b f6 ff 0f 0b 49 c7 c4 81 9e 83 aa 80 3b 00 75 30 48 c7 c6 8c 9e 83 aa 4c 89 e2 48 c7 c7 90 5c 8d aa e8 7a 2b f6 ff <0f> 0b e9 8d c8 d5 ff 4c 8b 24 c5 a0 c5 52 aa eb d4 49 c7 c4 81 9e [7.508414] RSP: 0018:bb2287f5b380 EFLAGS: 00010282 [7.508417] RAX: RBX: 98f4810dd000 RCX: 0027 [7.508419] RDX: 98f7ef2e0988 RSI: 0001 RDI: 98f7ef2e0980 [7.508422] RBP: bb2287f5b390 R08: 0003 R09: fffd4a88 [7.508424] R10: R11: 0001 R12: aa7e7338 [7.508425] R13: c12fa460 R14: 0001 R15: 98f4810dd000 [7.508428] FS: 7f579d7664c0() GS:98f7ef2c() knlGS: [7.508431] CS: 0010 DS: ES: CR0: 80050033 [7.508433] CR2: 560784eca498 CR3: 00010bc26006 CR4: 001706e0 [7.508436] Call Trace: [7.508438] [7.508443] __dev_open+0x45/0x1c0 [7.508451] ? nvme_pci_setup_prps+0xe5/0x340 [nvme] [7.508459] __dev_change_flags+0x1a3/0x220 [7.508465] ? wlc_iovar_check+0x152/0x21b [wl] [7.508548] dev_change_flags+0x26/0x60 [7.508553] do_setlink+0x28a/0xc60 [7.508560] ? __nla_parse+0x25/0x30 [7.508566] ? cpumask_next+0x23/0x30 [7.508572] ? __nla_validate_parse+0x4c/0x1a0 [7.508577] ? inet6_set_link_af+0x4e/0xb0 [7.508583] __rtnl_newlink+0x61a/0xa20 [7.508589] ? skb_free_head+0x68/0x80 [7.508595] ? kfree+0xab/0x410 [7.508600] ? __kmalloc_node_track_caller+0x1cd/0x3e0 [7.508605] ? cpumask_next_and+0x24/0x30 [7.508610] ? update_sg_lb_stats+0x78/0x560 [7.508623] ? kmem_cache_alloc_trace+0x1a6/0x320 [7.508627] rtnl_newlink+0x49/0x70 [7.508632] rtnetlink_rcv_msg+0x16e/0x3f0 [7.508637] ? rtnl_calcit.isra.0+0x130/0x130 [7.508641] netlink_rcv_skb+0x55/0x100 [7.508647] rtnetlink_rcv+0x15/0x20 [7.508651] netlink_unicast+0x232/0x340 [7.508655] netlink_sendmsg+0x25e/0x4d0 [7.508659] sock_sendmsg+0x65/0x70 [7.508665] sys_sendmsg+0x24e/0x290 [7.508669] ? import_iovec+0x31/0x40 [7.508672] ? sendmsg_copy_msghdr+0x7b/0xa0 [7.508679] ___sys_sendmsg+0x81/0xc0 [7.508685] ? rtnl_unlock+0xe/0x10 [7.508689] ? kfree+0xab/0x410 [7.508692] ? addrconf_sysctl_forward+0xbc/0xd0 [7.508697] ? __fget_light+0xa3/0x120 [7.508702] __sys_sendmsg+0x62/0xb0 [7.508709] __x64_sys_sendmsg+0x1d/0x20 [7.508714] do_syscall_64+0x5c/0xc0 [7.508717] ? syscall_exit_to_user_mode+0x27/0x50 [7.508722] ? __do_sys_gettid+0x1b/0x20 [7.508728] ? do_syscall_64+0x69/0xc0 [7.508731] ? __rseq_handle_notify_resume+0x2d/0xd0 [7.508736] ? exit_to_user_mode_loop+0x10d/0x160 [7.508742] ? exit_to_user_mode_prepare+0x37/0xb0 [7.508746] ? syscall_exit_to_user_mode+0x27/0x50 [7.508750] ? __x64_sys_close+0x11/0x40 [7.508754] ? do_syscall_64+0x69/0xc0 [7.508756] ? do_syscall_64+0x69/0xc0 [7.508759] ? do_syscall_64+0x69/0xc0 [7.508761] ? do_syscall_6
[Kernel-packages] [Bug 1957807] Re: Fix ct_state nat matching and nat action not being executed
This bug was fixed in the package linux-bluefield - 5.4.0-1028.31
---
linux-bluefield (5.4.0-1028.31) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1028.31 -proposed tracker (LP:
#1959252)
* Support CIFS for CUDA (LP: #1958299)
- [Config] bluefield: CONFIG_CIFS=m
- [Config] bluefield: Additional config options for CIFS
* Fix ct_state nat matching and nat action not being executed (LP: #1957807)
- net: zero-initialize tc skb extension on allocation
- net/sched: Extend qdisc control block with tc control block
- net/sched: flow_dissector: Fix matching on zone id for invalid conns
- net: openvswitch: Fix matching zone id for invalid conns arriving from tc
- net: openvswitch: Fix ct_state nat flags for conns arriving from tc
* Fix sprintf usage that may lead to buffer overflow (LP: #1959119)
- SAUCE: Fix references to sprintf that may cause buffer overflow
[ Ubuntu: 5.4.0-100.113 ]
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix t
[Kernel-packages] [Bug 1959119] Re: Fix sprintf usage that may lead to buffer overflow
This bug was fixed in the package linux-bluefield - 5.4.0-1028.31
---
linux-bluefield (5.4.0-1028.31) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1028.31 -proposed tracker (LP:
#1959252)
* Support CIFS for CUDA (LP: #1958299)
- [Config] bluefield: CONFIG_CIFS=m
- [Config] bluefield: Additional config options for CIFS
* Fix ct_state nat matching and nat action not being executed (LP: #1957807)
- net: zero-initialize tc skb extension on allocation
- net/sched: Extend qdisc control block with tc control block
- net/sched: flow_dissector: Fix matching on zone id for invalid conns
- net: openvswitch: Fix matching zone id for invalid conns arriving from tc
- net: openvswitch: Fix ct_state nat flags for conns arriving from tc
* Fix sprintf usage that may lead to buffer overflow (LP: #1959119)
- SAUCE: Fix references to sprintf that may cause buffer overflow
[ Ubuntu: 5.4.0-100.113 ]
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix t
[Kernel-packages] [Bug 1958299] Re: Support CIFS for CUDA
This bug was fixed in the package linux-bluefield - 5.4.0-1028.31
---
linux-bluefield (5.4.0-1028.31) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1028.31 -proposed tracker (LP:
#1959252)
* Support CIFS for CUDA (LP: #1958299)
- [Config] bluefield: CONFIG_CIFS=m
- [Config] bluefield: Additional config options for CIFS
* Fix ct_state nat matching and nat action not being executed (LP: #1957807)
- net: zero-initialize tc skb extension on allocation
- net/sched: Extend qdisc control block with tc control block
- net/sched: flow_dissector: Fix matching on zone id for invalid conns
- net: openvswitch: Fix matching zone id for invalid conns arriving from tc
- net: openvswitch: Fix ct_state nat flags for conns arriving from tc
* Fix sprintf usage that may lead to buffer overflow (LP: #1959119)
- SAUCE: Fix references to sprintf that may cause buffer overflow
[ Ubuntu: 5.4.0-100.113 ]
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix t
[Kernel-packages] [Bug 1910928] Re: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
** Changed in: linux (Ubuntu) Status: Expired => 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/1910928 Title: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL Status in linux package in Ubuntu: Confirmed Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:26:49:C4:B9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:19913 acl:0 sco:0 events:3169 errors:0 TX bytes:770617 acl:0 sco:0 commands:3167 errors:0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
Hi, Chao. For the 5.15 kernel can we use the upstream version that landed in 5.16? bf9167a8b40c HID: intel-ish-hid: fix module device-id handling 64355db3caf6 mod_devicetable: fix kdocs for ishtp_device_id fa443bc3c1e4 HID: intel-ish-hid: add support for MODULE_DEVICE_TABLE() f155dfeaa4ee platform/x86: isthp_eclite: only load for matching devices 7b6bf51de974 platform/x86: Add Intel ishtp eclite driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Maybe unset INTEL_IOMMU_DEFAULT_ON -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
** Bug watch added: Linux Kernel Bug Tracker #197029 https://bugzilla.kernel.org/show_bug.cgi?id=197029 -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
So, now I could find a little more detail about my issue: I tested with other mainline kernel from 5.15 series and the problem started with 5.15.5 And it is also present on 5.15.10 and 5.15.24 (thats what I have also tested) STR works with 5.15.0, 5.15.3, 5.15.4 (thats what I have tested) After knowing the version I could find this on the net: https://www.reddit.com/r/pop_os/comments/radfeg/psa_kernel_5155_and_intel_6th_gen_cpus_issue_with/ And so after adding intel_iommu=off as kernel option STR works also with linux-image-5.15.0-18-generic -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect
Right now I'm using OEM kernel and everything works well. -- 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/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect
My screen looks like this: https://postimg.cc/Tp2LJB4N The right side of the screen changes very quickly. Sometimes it is black and sometimes it looks like the rest of the screen. -- 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/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
So, now I could find a little more detail about my issue: I tested with other mainline kernel from 5.15 series and the problem started with 5.15.5 And it is also present on 5.15.10 and 5.15.24 (thats what I have also tested) STR works with 5.15.0, 5.15.3, 5.15.4 (thats what I have tested) -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect
Attached journal.txt. ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+attachment/5562797/+files/journalctl.txt -- 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/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.4-2ubuntu6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Today I also tested with linux-image-5.15.0-18-generic but the problem still persists. Anything else I can test? -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961823] [NEW] Bluetooth button off and doesn't work
Public bug reported: Bluetooth button off and doesn't work the massage that show me when i open the setting " No Bluetooth Found plug in a dongle to use Bluetooth " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 21:08:36 2022 InstallationDate: Installed on 2022-02-17 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da1xxx dmi.product.sku: 6EX79EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961823 Title: Bluetooth button off and doesn't work Status in bluez package in Ubuntu: New Bug description: Bluetooth button off and doesn't work the massage that show me when i open the setting " No Bluetooth Found plug in a dongle to use Bluetooth " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth 5.53-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 21:08:36 2022 InstallationDate: Installed on 2022-02-17 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da1xxx dmi.product.sku: 6EX79EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked:
[Kernel-packages] [Bug 1958328] Re: thermald package 1.9.1 causes CPU throttling problems
I need to update this issue. Version 2.4.8 of thermald does NOT fix this issue. This is not a hardware issue per se because under Windows, this throttling does not occur. (Under Windows, the machine is able to run a bit hotter and without throttling.) I speculate that Dell has written drivers for Windows that are able to call API's into the Dell BIOS and management hardware to manage thermal, power, and fan attributes, and Dell has chosen to not write kernel drivers, update existing kernel drivers, or even just provide API documentation so that someone else in the Open Source community can write those drivers. My hope is that Canonical, with its relationship with Dell, will be able to get this information so that SOMEBODY (either within or outside of Canonical) is able to fix this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1958328 Title: thermald package 1.9.1 causes CPU throttling problems Status in thermald package in Ubuntu: In Progress Bug description: There have been many reports of improper CPU throttling on Intel CPUs to the point of making machines completely unusable. See for example: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU- Throttling-Issue-on- Linux/td-p/7959019/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEtZS09TQk43Qk02UjY0fDgxMjgyMDl8U1VCU0NSSVBUSU9OU3xoSw The latest thermald version, 2.4.8, does not have this issue. Thermald versions prior to 2.4.8 do have this issue. See: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-Throttling-Issue-on-Linux/m-p/8128282/highlight/true#M39400 The version of thermald should be updated to 2.4.8, or the code that fixes this issue in 2.4.8 should be backported to the thermald versions in current Ubuntu versions. https://github.com/intel/thermal_daemon/tree/v2.4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1958328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
** Changed in: linux (Ubuntu Impish)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
In Progress
Status in linux source package in Jammy:
In Progress
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US q
[Kernel-packages] [Bug 1961819] [NEW] CT: Offload only ASSURED connections
Public bug reported: * Explain the feature Assured connections are those connections which deemed of "higher quality" and less like to expire than non-assured connections, as they passed some stricter rule (e.g in udp reply + connection lasting more than 2 seconds). This feature offloads only those connections. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a short UDP connection (< 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 1 -u Run longer UDP connection (> 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 10 -u With the above commit quick lived UDP connections (< 2 seconds) will not be offloaded to the flow table as can be checked by cat /proc/net/nf_conntrack | grep -i offload while connections lasting more than 2 seconds (and of course double sided) will be offloaded. * What it could break. NA ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1961819 Title: CT: Offload only ASSURED connections Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the feature Assured connections are those connections which deemed of "higher quality" and less like to expire than non-assured connections, as they passed some stricter rule (e.g in udp reply + connection lasting more than 2 seconds). This feature offloads only those connections. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a short UDP connection (< 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 1 -u Run longer UDP connection (> 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 10 -u With the above commit quick lived UDP connections (< 2 seconds) will not be offloaded to the flow table as can be checked by cat /proc/net/nf_conntrack | grep -i offload while connections lasting more than 2 seconds (and of course double sided) will be offloaded. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1961819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
** Description changed:
+ [SRU justification]
+
+ Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
+ We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
+
+ Fix: Move the following modules from linux-modules-extra into linux-modules:
+ - bochs-drm (though a bit aged, this was the predecessor of qemu)
+ - cirrus (this is a standard emulated gfx card, might not give the best
+performance but better than nothing)
+ - virtio-gpu (KVM)
+ - vmwgfx (VMWare)
+ - drm-xen-front (Xen)
+
+ Testcase: Check linux-modules for the mentioned modules.
+
+ Regression Potential: There should be no change noticeable. Users with
+ linux-modules-extra installed will see no difference and those without
+ have additional drivers. Maybe this shows as moving from low-resolution
+ graphics to higher ones which maybe perform less.
+
+ --- Original Description ---
+
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to keep
it installed and updated. The only way to do so conveniently is to
install linux-image-generic, which also pulls in linux-firmware, which
is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-team/2022-February/128103.html
and https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying problem
and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Ph
[Kernel-packages] [Bug 1961815] [NEW] ftbfs with linux 5.16+
Public bug reported: ftbfs with linux 5.16+ https://github.com/tseliot/nvidia-graphics-drivers/issues/44 Due to changes in the kernel w.r.t. stdarg.h and stddef.h includes. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1961815 Title: ftbfs with linux 5.16+ Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Bug description: ftbfs with linux 5.16+ https://github.com/tseliot/nvidia-graphics-drivers/issues/44 Due to changes in the kernel w.r.t. stdarg.h and stddef.h includes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1961815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959102] Re: Kernel fails to boot in ScalingStack
Verified that the virtio_pci module is present in the modules package. ** 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-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1959102 Title: Kernel fails to boot in ScalingStack Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: New Status in linux-raspi source package in Focal: Fix Committed Status in linux-raspi source package in Impish: Fix Committed Status in linux-raspi source package in Jammy: Fix Released Bug description: [ Impact ] The raspi kernel fails to boot in ScalingStack which is our OpenStack cluster for running ADT/autopkgtest tests. [ Test Case ] Boot a VM in ScalingStack, install raspi kernel, reboot. VM won't come back. [ Fix ] Enable VIRTIO PCI driver. ScalingStack uses virtio so the guest kernel needs to support that. [ Where Problems Could Occur ] New module means new code which could trigger kernel problems when loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1959102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] Re: bcmwl does not build with Kernel 5.17
The attachment "Fix PDE_DATA change in 5.17" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961801] [NEW] bcmwl does not build with Kernel 5.17
Public bug reported: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Patch added: "Fix PDE_DATA change in 5.17" https://bugs.launchpad.net/bugs/1961801/+attachment/5562741/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927076] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2022-02-22 09:29 EDT--- (In reply to comment #32) > Marking as "incomplete" while waiting for input from Power MMU experts. Adding a couple of developers from MM team to review... -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Triaged
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Status: New => Triaged
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Stefan Bader (smb)
--
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/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Triaged
Status in linux source package in Impish:
Triaged
Status in linux source package in Jammy:
In Progress
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.b
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Power cable unplug also did the trick 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Had a similar issue on a 20.04 install today after updating to 5.14. Woke it up from suspend on 5.10.0-1057-oem. Rebooted once (some screen issues that turned out to be the screen), installed updates via update- manager, rebooted using the new 5.14.0-1024-oem kernel and it just hung. Black screen, blinking cursor. I noticed that the lenovo splash screen did not come up after selecting the 5.14 kernel in grub. It does with 5.10. Going back to 5.10 works as before. I have a kern.log saved from the before and after the update, but do I need to make sure it is sanitized for secure boot keys and such? Also, it should be noted that it is a dual GPU system with an intel and nvidia. -- 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/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
Marking as "incomplete" while waiting for input from Power MMU experts. ** Changed in: ubuntu-power-systems 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961793] [NEW] Focal update: upstream stable patchset 2022-02-22
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 2022-02-22 from git://git.kernel.org/ ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-5.14 (Ubuntu Focal) 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/1961793 Title: Focal update: upstream stable patchset 2022-02-22 Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.14 source package in Focal: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-02-22 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1961793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961588] Re: Tweak realtime-related config options in Jammy realtime kernel
** Description changed: Config options below are useful for Realtime users: 1. CONFIG_WQ_POWER_EFFICIENT_DEFAULT disabled: energy saving is not that important for Realtime workload but locality of any workqueues (thus - waking up only local CPU). + cache locality and maybe lower latencies) is. 2. CONFIG_TIMERLAT_TRACER and CONFIG_OSNOISE_TRACER enabled: for debugging latency issues. 3. CONFIG_BLK_CGROUP_IOLATENCY enabled: for users wanting to have guarantees on IO latencies. 4. CONFIG_IRQ_TIME_ACCOUNTING enabled: for fine granularity task IRQ accounting. -- 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/1961588 Title: Tweak realtime-related config options in Jammy realtime kernel Status in linux package in Ubuntu: In Progress Bug description: Config options below are useful for Realtime users: 1. CONFIG_WQ_POWER_EFFICIENT_DEFAULT disabled: energy saving is not that important for Realtime workload but locality of any workqueues (thus cache locality and maybe lower latencies) is. 2. CONFIG_TIMERLAT_TRACER and CONFIG_OSNOISE_TRACER enabled: for debugging latency issues. 3. CONFIG_BLK_CGROUP_IOLATENCY enabled: for users wanting to have guarantees on IO latencies. 4. CONFIG_IRQ_TIME_ACCOUNTING enabled: for fine granularity task IRQ accounting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961789] [NEW] "ponteiro e tela travaram, não consegui ter acesso a nada do notebook" nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Estava acessando o meu endereço de e-mail e havia deixado o visual studio code e libreOffice Writer em aberto. Quando tentei abrir um e-mail, travou o ponteiro do mouse e a tela travou juntamente. Não consegui ter acesso a anda do notebook, não consegui nem desligar ele. Ficou ligado a noite toda, pela manhã eu vi que ele tinha descarregado e coloquei na carga e consegui ligar ele, e aparentemente voltou ao normal. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.14.0-1024-oem Date: Tue Feb 22 09:47:57 2022 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-kernel-source-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2022-02-03 (19 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 440.100-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1961789 Title: "ponteiro e tela travaram, não consegui ter acesso a nada do notebook" nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Estava acessando o meu endereço de e-mail e havia deixado o visual studio code e libreOffice Writer em aberto. Quando tentei abrir um e-mail, travou o ponteiro do mouse e a tela travou juntamente. Não consegui ter acesso a anda do notebook, não consegui nem desligar ele. Ficou ligado a noite toda, pela manhã eu vi que ele tinha descarregado e coloquei na carga e consegui ligar ele, e aparentemente voltou ao normal. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.14.0-1024-oem Date: Tue Feb 22 09:47:57 2022 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-kernel-source-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2022-02-03 (19 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 440.100-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1961789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961790] 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/1961790 Title: mt7601u 3-9:1.0: Error: TSSI upper saturation Status in linux package in Ubuntu: Confirmed Bug description: [15531.889284] mt7601u 3-9:1.0: Error: TSSI upper saturation [15535.921129] mt7601u 3-9:1.0: Error: TSSI upper saturation [15539.954309] mt7601u 3-9:1.0: Error: TSSI upper saturation [15543.986344] mt7601u 3-9:1.0: Error: TSSI upper saturation [15548.018315] mt7601u 3-9:1.0: Error: TSSI upper saturation [15552.053733] mt7601u 3-9:1.0: Error: TSSI upper saturation [15556.081540] mt7601u 3-9:1.0: Error: TSSI upper saturation [15560.115421] mt7601u 3-9:1.0: Error: TSSI upper saturation [15564.148377] mt7601u 3-9:1.0: Error: TSSI upper saturation [15568.177533] mt7601u 3-9:1.0: Error: TSSI upper saturation [15572.210772] mt7601u 3-9:1.0: Error: TSSI upper saturation [15576.240488] mt7601u 3-9:1.0: Error: TSSI upper saturation In my entire dmesg and every ttyN ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-30-lowlatency 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasdi 1778 F pulseaudio /dev/snd/controlC2: vasdi 1778 F pulseaudio /dev/snd/controlC1: vasdi 1778 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 22 16:13:26 2022 InstallationDate: Installed on 2014-11-12 (2658 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-lowlatency root=UUID=a519f3f5-89a4-46a6-978a-ea1ff8a21258 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-lowlatency N/A linux-backports-modules-5.13.0-30-lowlatency N/A linux-firmware1.201.4 RfKill: 2: phy2: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (129 days ago) dmi.bios.date: 03/23/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/23/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961790] [NEW] mt7601u 3-9:1.0: Error: TSSI upper saturation
Public bug reported: [15531.889284] mt7601u 3-9:1.0: Error: TSSI upper saturation [15535.921129] mt7601u 3-9:1.0: Error: TSSI upper saturation [15539.954309] mt7601u 3-9:1.0: Error: TSSI upper saturation [15543.986344] mt7601u 3-9:1.0: Error: TSSI upper saturation [15548.018315] mt7601u 3-9:1.0: Error: TSSI upper saturation [15552.053733] mt7601u 3-9:1.0: Error: TSSI upper saturation [15556.081540] mt7601u 3-9:1.0: Error: TSSI upper saturation [15560.115421] mt7601u 3-9:1.0: Error: TSSI upper saturation [15564.148377] mt7601u 3-9:1.0: Error: TSSI upper saturation [15568.177533] mt7601u 3-9:1.0: Error: TSSI upper saturation [15572.210772] mt7601u 3-9:1.0: Error: TSSI upper saturation [15576.240488] mt7601u 3-9:1.0: Error: TSSI upper saturation In my entire dmesg and every ttyN ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-30-lowlatency 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasdi 1778 F pulseaudio /dev/snd/controlC2: vasdi 1778 F pulseaudio /dev/snd/controlC1: vasdi 1778 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 22 16:13:26 2022 InstallationDate: Installed on 2014-11-12 (2658 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-lowlatency root=UUID=a519f3f5-89a4-46a6-978a-ea1ff8a21258 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-lowlatency N/A linux-backports-modules-5.13.0-30-lowlatency N/A linux-firmware1.201.4 RfKill: 2: phy2: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (129 days ago) dmi.bios.date: 03/23/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/23/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1961790 Title: mt7601u 3-9:1.0: Error: TSSI upper saturation Status in linux package in Ubuntu: Confirmed Bug description: [15531.889284] mt7601u 3-9:1.0: Error: TSSI upper saturation [15535.921129] mt7601u 3-9:1.0: Error: TSSI upper saturation [15539.954309] mt7601u 3-9:1.0: Error: TSSI upper saturation [15543.986344] mt7601u 3-9:1.0: Error: TSSI upper saturation [15548.018315] mt7601u 3-9:1.0: Error: TSSI upper saturation [15552.053733] mt7601u 3-9:1.0: Error: TSSI upper saturation [15556.081540] mt7601u 3-9:1.0: Error: TSSI upper saturation [15560.115421] mt7601u 3-9:1.0: Error: TSSI upper saturation [15564.148377] mt7601u 3-9:1.0: Error: TSSI upper saturation [15568.177533] mt7601u 3-9:1.0: Error: TSSI upper saturation [15572.210772] mt7601u 3-9:1.0: Error: TSSI upper saturation [15576.240488] mt7601u 3-9:1.0: Error: TSSI upper saturation In my entire dmesg and every ttyN ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-30-lowlatency 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasdi 1778 F pulseaudio /dev/snd/controlC2: vasdi 1778 F pulseaudio /dev/snd/controlC1: vasdi 1778 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 22 16:13:26 2022 InstallationDate: Installed on 2014-11-12 (2658 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-lowlatency root=UUID=a519f3f5-89a4-46a6-978a-ea1ff8a21258 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-re
[Kernel-packages] [Bug 1922406]
(In reply to pepito from comment #29) > Note: I *did* get this working by downgrading the kernel to 5.11 and > renaming the .pnvm file, but I don't want to be stuck on such an old kernel. > I was expecting everything to "just work" after I upgraded to the 5.16 > kernel. Currently I am using 5.14.18 and it does not have this problem. 5.11 had it. Later if I upgrade to 5.16, I will let you know if it happens again. -- 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922406]
I'm getting the same error but with the recent kernel version 5.16.9, and the workaround of renaming the .pnvm file does not work. I can see from the dmesg log that it tries loading the -67.ucode firmware (which gives the same timeout error reported by others; see below), and I've tried renaming every version after -59 as well as the .pnvm file to force it to use the -59 firmware (which is the version Intel provides on their website), but I still get the timeout error in dmesg: > Timeout waiting for PNVM load! > Failed to start RT ucode: -110 Note: I *did* get this working by downgrading the kernel to 5.11 and renaming the .pnvm file, but I don't want to be stuck on such an old kernel. I was expecting everything to "just work" after I upgraded to the 5.16 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] Re: Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
The package in bionic-proposed has been verified by an user
with access to the relevant device; 2 interfaces up/running.
# apt install linux-firmware
...
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64
linux-firmware all 1.173.21 [74.8 MB]
...
Setting up linux-firmware (1.173.21) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-99-generic
# reboot
...
$ dmesg|grep ' ice '
[4.073233] ice :98:00.0: The driver for the device detected a newer
version of the NVM image than expected. Please install the most recent version
of the network driver.
[4.084040] ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a
0.0.0 build 0x391f7640
[4.372182] ice :98:00.0: The DDP package was successfully loaded: ICE
OS Default Package version 1.3.4.0
[4.384818] ice :98:00.0: DCB is enabled in the hardware, max number of
TCs supported on this port are 8
[4.385116] ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[4.408390] ice :98:00.1: The driver for the device detected a newer
version of the NVM image than expected. Please install the most recent version
of the network driver.
[4.418878] ice :98:00.1: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a
0.0.0 build 0x391f7640
[4.419766] ice :98:00.1: DDP package already present on device: ICE OS
Default Package version 1.3.4.0
[4.432550] ice :98:00.1: DCB is enabled in the hardware, max number of
TCs supported on this port are 8
[4.432834] ice :98:00.1: FW LLDP is disabled, DCBx/LLDP in SW mode.
[4.460921] ice :98:00.1 enp152s0f1: renamed from eth1
[4.488092] ice :98:00.0 enp152s0f0: renamed from eth0
[6.521594] ice :98:00.1 enp152s0f1: changed MTU to 9000
[6.530894] ice :98:00.0 enp152s0f0: changed MTU to 9000
[6.993224] ice :98:00.1 enp152s0f1: NIC Link is up 25 Gbps, Requested
FEC: RS-FEC, FEC: FC-FEC/BASE-R, Autoneg: False, Flow Control: None
[6.996340] ice :98:00.0 enp152s0f0: already using mac 3c:ec:ef:79:7a:f6
[7.128953] ice :98:00.0 enp152s0f0: NIC Link is up 25 Gbps, Requested
FEC: RS-FEC, FEC: FC-FEC/BASE-R, Autoneg: False, Flow Control: None
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961771] Re: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961771 Title: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy Status in linux package in Ubuntu: Confirmed Bug description: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961771] 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 1961771 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/1961771 Title: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
Many thanks for the fix! Is there any chance we'll see this backported to hirsute? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-sig
[Kernel-packages] [Bug 1961771] [NEW] Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy
Public bug reported: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. ** Affects: linux (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/1961771 Title: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy Status in linux package in Ubuntu: New Bug description: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep
Yes, I agree that this is similar to bug 1958778. Differences: I have not confirmed the behavior when an external monitor is attached, and this issue arose before upgrading to kernel 5.13. I know I used 5.11-40 successfully, and believe I might have had 5.11-41 or 5.11-42, which worked, but certainly 5.11-44 did not. -- 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/1961608 Title: [amdgpu] Screen freeze after wake from sleep Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Any time the computer sleeps, and I wake it the screen backlight turns on but nothing appears. This has been occurring since upgrading to Kernel 5.11-44. I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 without issues. I have tried multiple 5.13 releases and none of them handle sleep and wakeup successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 11:13:07 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2022-01-02 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+attachment/5562681/+files/lspci.txt -- 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/1961608 Title: [amdgpu] Screen freeze after wake from sleep Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Any time the computer sleeps, and I wake it the screen backlight turns on but nothing appears. This has been occurring since upgrading to Kernel 5.11-44. I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 without issues. I have tried multiple 5.13 releases and none of them handle sleep and wakeup successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 11:13:07 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2022-01-02 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+attachment/5562680/+files/prevboot.txt -- 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/1961608 Title: [amdgpu] Screen freeze after wake from sleep Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Any time the computer sleeps, and I wake it the screen backlight turns on but nothing appears. This has been occurring since upgrading to Kernel 5.11-44. I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 without issues. I have tried multiple 5.13 releases and none of them handle sleep and wakeup successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 11:13:07 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2022-01-02 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961596] Re: Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor
Thanks for the solution. I removed "nomodeset" from grub config and now it detects external monitor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1961596 Title: Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor Status in linux-hwe-5.11 package in Ubuntu: Invalid Bug description: Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)" $ lspci | grep -E 'VGA|Display' 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05) $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa/X.org (0x) Device: llvmpipe (LLVM 12.0.0, 256 bits) (0x) Version: 21.2.6 Accelerated: no Video memory: 31887MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits) OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.2.6 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.1 Mesa 21.2.6 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 14:42:46 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.13.0-28-generic, x86_64: installed evdi, 1.9.1, 5.13.0-30-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8784] InstallationDate: Installed on 2021-03-03 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook Fury 15 G7 Mobile Workstation ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgubuntu-root ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2021 dmi.bios.release: 4.1 dmi.bios.vendor: HP dmi.bios.version: S92 Ver. 01.04.01 dmi.board.name: 8783 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3D.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.61 dmi.modalias: dmi:bvnHP:bvrS92Ver.01.04.01:bd01/05/2021:br4.1:efr22.61:svnHP:pnHPZBookFury15G7MobileWorkstation:pvr:sku26F75AV:rvnHP:rn8783:rvrKBCVersion16.3D.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Fury 15 G7 Mobile Workstation dmi.product.sku: 26F75AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1961596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961764] [NEW] Touchpad stops working after it has been left unused for awhile
Public bug reported: Touchpad stops working after it has been left unused for awhile for example when I go for some work and I set my laptop to sleeping position and after it my touchpad goes stuck when I try to reuse it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 15:20:37 2022 InstallationDate: Installed on 2021-06-03 (264 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961764 Title: Touchpad stops working after it has been left unused for awhile Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Touchpad stops working after it has been left unused for awhile for example when I go for some work and I set my laptop to sleeping position and after it my touchpad goes stuck when I try to reuse it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 15:20:37 2022 InstallationDate: Installed on 2021-06-03 (264 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943353] Re: kernel hang at resuming from s2idle on AMD Barcelo platform with SATA attached
closing, reopen if it's still a valid case with patches ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Incomplete => 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/1943353 Title: kernel hang at resuming from s2idle on AMD Barcelo platform with SATA attached 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: Invalid Bug description: On AMD Barcelo CRB platform, BIOS RLD-1005B_AB 06/30/2021, starting from v5.14-rc1 kernel that put system to deep sleep than v5.13, cannot wake from s2idle, fan spinning, debug LED EEFC0300, BLK LED blinking. This, as long as one sata device is attached, no matter it was boot from sata or nvme root partition, it will all be affected. Public bug filed at https://bugzilla.kernel.org/show_bug.cgi?id=214365 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1410 F pulseaudio /dev/snd/controlC2: ubuntu 1410 F pulseaudio /dev/snd/controlC0: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux (not installed) ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9002-oem root=UUID=bac31a43-d46f-43f7-8eb0-87b96dbf0a61 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9002.2+staging.19-oem 5.14.0 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.14.0-9002-oem N/A linux-backports-modules-5.14.0-9002-oem N/A linux-firmware 1.187.16+staging.16 RfKill: Tags: focal Uname: Linux 5.14.0-9002-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:sku123456789:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956239] Re: ipu6: TGL: himx11b1: failed to find sensor
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Invalid => Won't Fix -- 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/1956239 Title: ipu6: TGL: himx11b1: failed to find sensor Status in linux package in Ubuntu: Incomplete 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: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Incomplete Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: On oem-5.13 kernels, this happens only on warm boots: [6.129618] intel_ulpss 3-6:1.0: intel_ulpss_i2c_start i2c start failed len:-1 id:0 0 [6.373718] hm11b1 i2c-HIMX11B1:00: failed to find sensor: -5 [6.373806] hm11b1: probe of i2c-HIMX11B1:00 failed with error -5 But on oem-5.14 kernels proposed in bug 1955383, this fails always. -- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2085 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 3 12:03:29 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X103 InstallationDate: Installed on 2021-12-17 (17 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 9420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem root=UUID=1660e296-b95f-47c2-abb2-bac15dd92b62 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-1012-oem N/A linux-backports-modules-5.13.0-1012-oem N/A linux-firmware 1.187.24+staging.39 SourcePackage: linux-oem-5.13 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2021 dmi.bios.release: 89.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.5.23 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.5.23:bd01/25/2021:br89.5:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 9420 dmi.product.sku: 0A32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951055] Re: Reinstate ACPI S5 for reboot
** 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/1951055 Title: Reinstate ACPI S5 for reboot 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] On some systems, Intel WiFi device may stop working after reboot. [Fix] Use ACPI S5 for reboot. [Test] 2000 times of reboot stress, and Intel WiFi continues work on affected system. [Where problems could occur] There was a bug introduced by this patch, but the user didn't want to find the root cause. Since we have more control on Ubuntu kernel, we'll fix the root cause properly this time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961120] Re: SFH sensors are not working on some AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => 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/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: In Progress 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] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] The SRU contains two fixes: 1. increasing sensor command timeout from from 80 to 160. 2. using first valid 15 bits only ALS max illuminance values. [Test] This is requested by AMD. This was also verified by an AMD's engineer on CRB. [Where problems could occur] Low. The patches only increase timeout value and discard an invalid bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961119] Re: Lower the volume of expected s0i3 WARN_ON
** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => 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/1961119 Title: Lower the volume of expected s0i3 WARN_ON Status in HWE Next: In Progress 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] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] Print a shorter message warning instead: "Watermarks table not configured properly by SMU". The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] Low. This only changes the behavors of message printing There are no functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] dcn31_init_hw+0x465/0x8e0 [amdgpu] dc_set_power_state+0x113/0x160 [amdgpu] dm_resume+0x2b5/0x610 [amdgpu] amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] amdgpu_device_resume+0xd9/0x210 [amdgpu] amdgpu_pmops_resume+0x1d/0x40 [amdgpu] pci_pm_resume+0x5b/0x90 ? pci_pm_thaw+0x80/0x80 dpm_run_callback+0x52/0x160 device_resume+0xdd/0x1e0 async_resume+0x1f/0x60 async_run_entry_fn+0x33/0x120 process_one_work+0x236/0x420 worker_thread+0x34/0x410 ? process_one_work+0x420/0x420 kthread+0x12f/0x150 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 ---[ end trace 71d329758d0428b2 ]--- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:105 dcn31_smu_send_msg_with_param+0x56/0x130 [amdgpu] Module
[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
** 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
uploaded to impish and focal now -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
If I read correctly the upstream history the changes are in 2.6.3 just slightly refactored to merge files right? ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
** Tags added: originate-from-1961382 sutton -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released 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: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 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.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.p
[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Bug description: [Impact] If any sub-test in this icmp_redirect.sh is failing but not expected to fail. The script will complain: ./icmp_redirect.sh: line 72: [: 1: unary operator expected This is because when the sub-test is not expected to fail, we won't pass any value for the xfail local variable in log_test() and thus it's empty. Fix this by passing 0 as the 4th variable to log_test() for non-xfail cases. This issue can be found on our KVM kernel with SRU tests, they're failing because of missing some kernel configs. [Fix] * 39d8622c72 "selftests: icmp_redirect: pass xfail=0 to log_test()" This patch can be cherry-picked into all of the affected kernels. [Test Plan] Run the patched icmp_redirect.sh script with a KVM kernel (e.g. F/kvm), and this "unary operator expected" error message should no longer exist. [Where problems could occur] Change limited to test script, it won't have any impact to real kernel function. And this issue is most likely specific to KVM kernels. == Original Bug Report == icmp_redirect from selftect is failing on F/kvm 5.4.0-1045.47 # selftests: net: icmp_redirect.sh # # ### # Legacy routing # ### # # TEST: IPv4: redirect exception [ OK ] # TEST: IPv6: redirect exception [ OK ] # TEST: IPv4: redirect exception plus mtu [ OK ] # TEST: IPv6: redirect exception plus mtu [ OK ] # TEST: IPv4: routing reset [ OK ] # TEST: IPv6: routing reset [ OK ] # TEST: IPv4: mtu exception [ OK ] # TEST: IPv6: mtu exception [ OK ] # TEST: IPv4: mtu exception plus redirect [ OK ] # TEST: IPv6: mtu exception plus redirect [XFAIL] # # ### # Legacy routing with VRF # ### # # Error: Unknown device type. # Cannot find device "red" # Error: argument "red" is wrong: Invalid VRF # # Error: argument "red" is wrong: Invalid VRF # # Cannot find device "red" # Cannot find device "red" # Error: argument "red" is wrong: Not a valid VRF name # # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception plus mtu [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception plus mtu [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: routing reset [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: routing reset [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: mtu exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: mtu exception [XFAIL] # Error: argument "red" is wrong: Invalid V
[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7
Thanks for looking into that Hui. I have checked that with the user who experience it - you are right, the mic was working fine *without* the need to install firmware-sof-signed. Regarding firmware: what do you mean by "original sof-firmware" in this context? Do you need dmesg from vanilla focal or from focal with the sof firmware from impish shipping in linux-firmware? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1959681 Title: mic not working on HP-EliteBook-830-G7 Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Bug description: There is no audio input from the built-in mic available on Bionic & Focal on certain intel audio hw (00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8]) despite trying different kernel cmdline options (snd_hda_intel.dmic_detect=0 or snd_intel_dspcfg.dsp_driver=1). The behavior was similar on Bionic and Focal - no mic listed in alsa/pulseaudio mixers. Additionally the following can be found in the kernel log: sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver sof-audio-pci :00:1f.3: enabling device ( -> 0002) sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found The situation is different on impish - on this release the mic is available out of the box. I made a simple test of overwriting sof files inside Focal's linux- firmware package with the contents of firmware-sof-signed package from impish finding it solved the issue without any trace of errors in the logs. The same approach did not work on Bionic (despite similar kernel versions used in both 5.4.0) - due to HWE). These are some excerpts from Bionic launching impish SOF firmware: sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0 sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel sof-audio-pci :00:1f.3: firmware boot complete sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0 sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled [ Test Plan ] 1. Launch Ubuntu desktop on affected hardware. 2. Open audio mixer (e.g. pulsemixer). 3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo). Expected result: Built-in mic is available for use. Actual result: Built-in mic is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961646] Re: On AMD platforms s2idle may not work w/o proper FW
PPA https://launchpad.net/~vicamo/+archive/ubuntu/ppa-amd-no-s2idle- without-lps0 needs verification. -- 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/1961646 Title: On AMD platforms s2idle may not work w/o proper FW Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: It was raised because of a community member using a Lenovo platform having very odd s2idle failures. It was later debugged that it was caused by them choosing "Linux" mode in Lenovo BIOS setup rather than "Windows" mode and then choosing "s2idle" in /sys/power/mem_sleep. - In "Linux" mode there is both "deep" and "s2idle" offered in /sys/power/mem_sleep. - In "Windows" mode there is only "s2idle" offered in /sys/power/mem_sleep. That is by default no matter if the OEM offers S3 or S2idle /sys/power/mem_sleep will contain "s2idle", but on AMD platforms "s2idle" only works if the hardware has been configured properly by the firmware. The outward indications of this being configured properly are the FADT low power idle bit being set and the uPEP ACPI device being populated, which is what this patch now checks for. So now if a user has the firmware of the machine configured for S3 then they will only see "deep" on AMD systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961746] Re: assertion triggered in link_enc_cfg_validate in amdgpu on resume from s2idle
** 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.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Tags added: amd oem-priority originate-from-1961611 -- 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/1961746 Title: assertion triggered in link_enc_cfg_validate in amdgpu on resume from s2idle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: Invalid Bug description: The following WARNING shows up on resume from s2idle on HP Z13/Z16: [ 136.701141] [ cut here ] [ 136.701146] WARNING: CPU: 0 PID: 1630 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_enc_cfg.c:588 link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701417] Modules linked in: hid_logitech_hidpp hid_logitech_dj michael_mic rfcomm snd_usb_audio snd_usbmidi_lib cmac algif_hash r8153_ecm algif_skcipher qrtr_mhi r8152 af_alg cdc_mbim cdc_wdm cdc_ncm cdc_ether usbnet joydev mii intel_rapl_msr intel_rapl_common bnep edac_mce_amd snd_acp6x_pdm_dma snd_soc_dmic snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine qrtr ns snd_ctl_led ath11k_pci ath11k snd_hda_codec_realtek nls_iso8859_1 qmi_helpers snd_hda_codec_generic amdgpu mac80211 kvm iommu_v2 gpu_sched drm_ttm_helper snd_hda_codec_hdmi btusb crct10dif_pclmul ttm btrtl thinkpad_acpi ghash_clmulni_intel uvcvideo btbcm snd_seq_midi btintel snd_hda_intel nvram videobuf2_vmalloc snd_seq_midi_event snd_intel_dspcfg aesni_intel drm_kms_helper videobuf2_memops snd_intel_sdw_acpi bluetooth videobuf2_v4l2 videobuf2_common think_lmi crypto_simd cec input_leds snd_hda_codec videodev cryptd platform_profile usbhid efi_pstore ecdh_generic serio_raw rapl cfg80211 wmi_bmof [ 136.701485] firmware_attributes_class ecc ledtrig_audio mc rc_core snd_rawmidi snd_hda_core snd_pci_acp6x snd_hwdep i2c_algo_bit fb_sys_fops mhi snd_seq syscopyarea snd_pcm sysfillrect libarc4 sysimgblt snd_rn_pci_acp3x snd_seq_device snd_pci_acp3x snd_timer ccp snd soundcore hid_sensor_accel_3d hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mac_hid amd_pmc industrialio acpi_tad sch_fq_codel msr parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_sensor_hub hid_generic crc32_pclmul psmouse nvme i2c_piix4 nvme_core xhci_pci amd_sfh xhci_pci_renesas wmi i2c_hid_acpi video i2c_hid hid [ 136.701526] CPU: 0 PID: 1630 Comm: Xorg Not tainted 5.14.0-1022-oem #24-Ubuntu [ 136.701530] Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET11WQ (0.11 ) 01/14/2022 [ 136.701532] RIP: 0010:link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701930] Code: 83 7d 10 00 74 24 0f b6 83 e0 01 00 00 49 83 c4 01 44 39 e0 7f d4 45 84 ff 74 0f 80 7d 8b 00 74 09 0f b6 45 90 44 20 f0 75 04 <0f> 0b 31 c0 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4d c8 [ 136.701933] RSP: 0018:a7c28284f980 EFLAGS: 00010246 [ 136.701936] RAX: RBX: 8e9304ac RCX: [ 136.701937] RDX: 0201 RSI: a7c28284f8b8 RDI: 8e930a628000 [ 136.701939] RBP: a7c28284f9f8 R08: 0014 R09: 8e937ad0 [ 136.701940] R10: 0031 R11: R12: 0001 [ 136.701941] R13: 8e934a160800 R14: R15: 0001 [ 136.701942] FS: 7f546a3a4a40() GS:8e9a5da0() knlGS: [ 136.701944] CS: 0010 DS: ES: CR0: 80050033 [ 136.701945] CR2: 7f70efb5f500 CR3: 0001100f6000 CR4: 00750ef0 [ 136.701947] PKRU: 5554 [ 136.70
[Kernel-packages] [Bug 1961746] 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 1961746 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/1961746 Title: assertion triggered in link_enc_cfg_validate in amdgpu on resume from s2idle Status in linux package in Ubuntu: Incomplete Bug description: The following WARNING shows up on resume from s2idle on HP Z13/Z16: [ 136.701141] [ cut here ] [ 136.701146] WARNING: CPU: 0 PID: 1630 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_enc_cfg.c:588 link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701417] Modules linked in: hid_logitech_hidpp hid_logitech_dj michael_mic rfcomm snd_usb_audio snd_usbmidi_lib cmac algif_hash r8153_ecm algif_skcipher qrtr_mhi r8152 af_alg cdc_mbim cdc_wdm cdc_ncm cdc_ether usbnet joydev mii intel_rapl_msr intel_rapl_common bnep edac_mce_amd snd_acp6x_pdm_dma snd_soc_dmic snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine qrtr ns snd_ctl_led ath11k_pci ath11k snd_hda_codec_realtek nls_iso8859_1 qmi_helpers snd_hda_codec_generic amdgpu mac80211 kvm iommu_v2 gpu_sched drm_ttm_helper snd_hda_codec_hdmi btusb crct10dif_pclmul ttm btrtl thinkpad_acpi ghash_clmulni_intel uvcvideo btbcm snd_seq_midi btintel snd_hda_intel nvram videobuf2_vmalloc snd_seq_midi_event snd_intel_dspcfg aesni_intel drm_kms_helper videobuf2_memops snd_intel_sdw_acpi bluetooth videobuf2_v4l2 videobuf2_common think_lmi crypto_simd cec input_leds snd_hda_codec videodev cryptd platform_profile usbhid efi_pstore ecdh_generic serio_raw rapl cfg80211 wmi_bmof [ 136.701485] firmware_attributes_class ecc ledtrig_audio mc rc_core snd_rawmidi snd_hda_core snd_pci_acp6x snd_hwdep i2c_algo_bit fb_sys_fops mhi snd_seq syscopyarea snd_pcm sysfillrect libarc4 sysimgblt snd_rn_pci_acp3x snd_seq_device snd_pci_acp3x snd_timer ccp snd soundcore hid_sensor_accel_3d hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mac_hid amd_pmc industrialio acpi_tad sch_fq_codel msr parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_sensor_hub hid_generic crc32_pclmul psmouse nvme i2c_piix4 nvme_core xhci_pci amd_sfh xhci_pci_renesas wmi i2c_hid_acpi video i2c_hid hid [ 136.701526] CPU: 0 PID: 1630 Comm: Xorg Not tainted 5.14.0-1022-oem #24-Ubuntu [ 136.701530] Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET11WQ (0.11 ) 01/14/2022 [ 136.701532] RIP: 0010:link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701930] Code: 83 7d 10 00 74 24 0f b6 83 e0 01 00 00 49 83 c4 01 44 39 e0 7f d4 45 84 ff 74 0f 80 7d 8b 00 74 09 0f b6 45 90 44 20 f0 75 04 <0f> 0b 31 c0 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4d c8 [ 136.701933] RSP: 0018:a7c28284f980 EFLAGS: 00010246 [ 136.701936] RAX: RBX: 8e9304ac RCX: [ 136.701937] RDX: 0201 RSI: a7c28284f8b8 RDI: 8e930a628000 [ 136.701939] RBP: a7c28284f9f8 R08: 0014 R09: 8e937ad0 [ 136.701940] R10: 0031 R11: R12: 0001 [ 136.701941] R13: 8e934a160800 R14: R15: 0001 [ 136.701942] FS: 7f546a3a4a40() GS:8e9a5da0() knlGS: [ 136.701944] CS: 0010 DS: ES: CR0: 80050033 [ 136.701945] CR2: 7f70efb5f500 CR3: 0001100f6000 CR4: 00750ef0 [ 136.701947] PKRU: 5554 [ 136.701948] Call Trace: [ 136.701950] [ 136.701953] link_enc_cfg_link_encs_assign+0x1c9/0x3b0 [amdgpu] [ 136.702129] dc_validate_global_state+0x57/0x330 [amdgpu] [ 136.702310] ? drm_modeset_lock+0x8e/0xb0 [drm] [ 136.702357] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 [ 136.702366] amdgpu_dm_atomic_check+0x8e2/0xef0 [amdgpu] [ 136.702558] ? __slab_alloc+0x20/0x40 [ 136.702562] ? __kmalloc_track_caller+0x1aa/0x490 [ 136.702565] ? amdgpu_dm_connector_atomic_duplicate_state+0x2a/0xd0 [amdgpu] [ 136.702735] drm_atomic_check_only+0x5a5/0x8c0 [drm] [ 136.702760] drm_atomic_commit+0x18/0x50 [drm] [ 136.702779] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [ 136.702803] drm_mode_setcrtc+0x1fb/0x7b0 [drm] [ 136.702846] ? drm_mode_getcrtc+0x190/0x190 [drm] [ 136.70288
[Kernel-packages] [Bug 1961746] [NEW] assertion triggered in link_enc_cfg_validate in amdgpu on resume from s2idle
Public bug reported: The following WARNING shows up on resume from s2idle on HP Z13/Z16: [ 136.701141] [ cut here ] [ 136.701146] WARNING: CPU: 0 PID: 1630 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_enc_cfg.c:588 link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701417] Modules linked in: hid_logitech_hidpp hid_logitech_dj michael_mic rfcomm snd_usb_audio snd_usbmidi_lib cmac algif_hash r8153_ecm algif_skcipher qrtr_mhi r8152 af_alg cdc_mbim cdc_wdm cdc_ncm cdc_ether usbnet joydev mii intel_rapl_msr intel_rapl_common bnep edac_mce_amd snd_acp6x_pdm_dma snd_soc_dmic snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine qrtr ns snd_ctl_led ath11k_pci ath11k snd_hda_codec_realtek nls_iso8859_1 qmi_helpers snd_hda_codec_generic amdgpu mac80211 kvm iommu_v2 gpu_sched drm_ttm_helper snd_hda_codec_hdmi btusb crct10dif_pclmul ttm btrtl thinkpad_acpi ghash_clmulni_intel uvcvideo btbcm snd_seq_midi btintel snd_hda_intel nvram videobuf2_vmalloc snd_seq_midi_event snd_intel_dspcfg aesni_intel drm_kms_helper videobuf2_memops snd_intel_sdw_acpi bluetooth videobuf2_v4l2 videobuf2_common think_lmi crypto_simd cec input_leds snd_hda_codec videodev cryptd platform_profile usbhid efi_pstore ecdh_generic serio_raw rapl cfg80211 wmi_bmof [ 136.701485] firmware_attributes_class ecc ledtrig_audio mc rc_core snd_rawmidi snd_hda_core snd_pci_acp6x snd_hwdep i2c_algo_bit fb_sys_fops mhi snd_seq syscopyarea snd_pcm sysfillrect libarc4 sysimgblt snd_rn_pci_acp3x snd_seq_device snd_pci_acp3x snd_timer ccp snd soundcore hid_sensor_accel_3d hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mac_hid amd_pmc industrialio acpi_tad sch_fq_codel msr parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_sensor_hub hid_generic crc32_pclmul psmouse nvme i2c_piix4 nvme_core xhci_pci amd_sfh xhci_pci_renesas wmi i2c_hid_acpi video i2c_hid hid [ 136.701526] CPU: 0 PID: 1630 Comm: Xorg Not tainted 5.14.0-1022-oem #24-Ubuntu [ 136.701530] Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET11WQ (0.11 ) 01/14/2022 [ 136.701532] RIP: 0010:link_enc_cfg_validate+0x1f6/0x240 [amdgpu] [ 136.701930] Code: 83 7d 10 00 74 24 0f b6 83 e0 01 00 00 49 83 c4 01 44 39 e0 7f d4 45 84 ff 74 0f 80 7d 8b 00 74 09 0f b6 45 90 44 20 f0 75 04 <0f> 0b 31 c0 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4d c8 [ 136.701933] RSP: 0018:a7c28284f980 EFLAGS: 00010246 [ 136.701936] RAX: RBX: 8e9304ac RCX: [ 136.701937] RDX: 0201 RSI: a7c28284f8b8 RDI: 8e930a628000 [ 136.701939] RBP: a7c28284f9f8 R08: 0014 R09: 8e937ad0 [ 136.701940] R10: 0031 R11: R12: 0001 [ 136.701941] R13: 8e934a160800 R14: R15: 0001 [ 136.701942] FS: 7f546a3a4a40() GS:8e9a5da0() knlGS: [ 136.701944] CS: 0010 DS: ES: CR0: 80050033 [ 136.701945] CR2: 7f70efb5f500 CR3: 0001100f6000 CR4: 00750ef0 [ 136.701947] PKRU: 5554 [ 136.701948] Call Trace: [ 136.701950] [ 136.701953] link_enc_cfg_link_encs_assign+0x1c9/0x3b0 [amdgpu] [ 136.702129] dc_validate_global_state+0x57/0x330 [amdgpu] [ 136.702310] ? drm_modeset_lock+0x8e/0xb0 [drm] [ 136.702357] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 [ 136.702366] amdgpu_dm_atomic_check+0x8e2/0xef0 [amdgpu] [ 136.702558] ? __slab_alloc+0x20/0x40 [ 136.702562] ? __kmalloc_track_caller+0x1aa/0x490 [ 136.702565] ? amdgpu_dm_connector_atomic_duplicate_state+0x2a/0xd0 [amdgpu] [ 136.702735] drm_atomic_check_only+0x5a5/0x8c0 [drm] [ 136.702760] drm_atomic_commit+0x18/0x50 [drm] [ 136.702779] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [ 136.702803] drm_mode_setcrtc+0x1fb/0x7b0 [drm] [ 136.702846] ? drm_mode_getcrtc+0x190/0x190 [drm] [ 136.702880] drm_ioctl_kernel+0xae/0xf0 [drm] [ 136.702901] drm_ioctl+0x257/0x410 [drm] [ 136.702939] ? drm_mode_getcrtc+0x190/0x190 [drm] [ 136.702980] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [ 136.703135] __x64_sys_ioctl+0x91/0xc0 [ 136.703141] do_syscall_64+0x3b/0xc0 [ 136.703147] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 136.703152] RIP: 0033:0x7f546a70450b [ 136.703154] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 136.703156] RSP: 002b:7fff039684f8 EFLAGS: 0246 ORIG_RAX: 0010 [ 136.703159] RAX: ffda RBX: 7fff03968530 RCX: 7f546a70450b [ 136.703160] RDX: 7fff03968530 RSI: c06864a2 RDI: 000c [ 136.703161] RBP: c06864a2 R08: R09: 55d0e925e820 [ 136.703162] R10: R11: 0246 R12: 0
[Kernel-packages] [Bug 1961739] Re: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
** Description changed: - With bug 1957026, suspend/resume using rtc and power button work as - expected, but PS/2 or USB keyboard still do not work well as an wakeup - source. + With bug 1957026 and bug 1960434, suspend/resume using rtc and power + button work as expected, but PS/2 or USB keyboard still do not work well + as an wakeup source. ** Description changed: With bug 1957026 and bug 1960434, suspend/resume using rtc and power button work as expected, but PS/2 or USB keyboard still do not work well - as an wakeup source. + as an wakeup source. This focus on fixes for PS/2. -- 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/1961739 Title: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: Invalid Bug description: With bug 1957026 and bug 1960434, suspend/resume using rtc and power button work as expected, but PS/2 or USB keyboard still do not work well as an wakeup source. This focus on fixes for PS/2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
